"Elijah Newren via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes: > From: Elijah Newren <newren@xxxxxxxxx> > ... > The reason for showing the "|SPARSE" substring before other states is to > ... > The fact that sparsity isn't just cached metadata or additional > information is what leads us to show it more similarly to the > in-progress states, but the fact that sparsity is not transient like the > in-progress states might cause some users to want an abbreviated > notification of sparsity state or perhaps even be able to turn it off. > Allow GIT_PS1_COMPRESSSPARSESTATE to be set to request that it be > shortened to a single character ('?'), and GIT_PS1_OMITSPARSESTATE to be > set to request that sparsity state be omitted from the prompt entirely. Nicely explained. It somewhat feels a bit overkill to have two (i.e. compress vs omit) knobs---the other "semi-permanent" state that may be of interest but could become too noisy only have one knob that toggles between showing a short-and-non-intrusive sign and not showing anything at all with GIT_PS1_SHOWSTASHSTATE, and that smells like a better balance to me, but I dunno. Thanks. Will queue.