Closed dc46and2 closed 2 years ago
Hmm, this behavior is very confusing, we should at least have them behave the same way (either add --ignore-submodules
to git diff
or, as suggested, remove from git status
).
The reason submodules are ignored is at least in part for performance reasons, see #102 for history.
Thoughts @sindresorhus?
I don't use submodules, so I don't have strong feelings about it. As long as it doesn't affect performance too much, I'm fine with including it.
General information
If
PURE_GIT_UNTRACKED_DIRTY=0
, then the prompt will show the repo is dirty if submodules are dirty. However, ifPURE_GIT_UNTRACKED_DIRTY=1
(the default), then dirty submodules are ignored. I would prefer that dirty submodules are never ignored.System report (output of
prompt_pure_system_report
):''
'$'
1.13.0
1.8.4
typeset -g PROMPT=$'%F{${prompt_pure_colors[path]}}%~%f %}%(12V.%F{$prompt_pure_colors[virtualenv]}%12v%f .)%(?.%F{$prompt_pure_colors[prompt:success]}.%F{$prompt_pure_colors[prompt:error]})$prompt_pure_state[prompt]}%f '
typeset -g -A prompt_pure_colors=( [execution_time]=yellow [git:action]=yellow [git:arrow]=cyan [git:branch]=242 [git:branchcached]=red [git:dirty]=218 [git:stash]=cyan [host]=242 [path]=blue [prompt:continuation]=242 [prompt:error]=red [prompt:success]=magena [user]=242 [user:root]=default [virtualenv]=242 )
export TERM=xterm-256color
export VIRTUAL_ENV_DISABLE_PROMPT=12
export CONDA_CHANGEPS1=no
Other information
This patch fixes the issue for me, but maybe there was a good reason you were ignoring submodules?