From d5c57fe7a50f391c1c12a25e32d6e4139f63a977 Mon Sep 17 00:00:00 2001
From: Michael Prokop
+If you would like to disable the persistent dirstack feature altogether, +you can do that by setting the boolean enable style to false in the +right context (the default is true): + +
++zstyle ':grml:chpwd:dirstack' enable false ++
It is possible to apply a filter to the names of directories that will be committed to the persistent dirstack file. There are two ways to configure this filter: A general function based filter and a pattern based filter. Both are @@ -217,12 +237,16 @@ dirstack file, set the filter-on-load boolean style (the default is zstyle ':grml:chpwd:dirstack' filter-on-load true
-Setting the filter-on-load needs to be done in ".zshrc.pre" because the -style needs to be set when the main setup is executing! The other styles do not -have this limitation, but the initial filtering will obviously be done using -the filters that are configured at that point. The rule of thumb -is: If you want to filter on load, setup everything in ".zshrc.pre" otherwise -".zshrc.local" works just as well. +Setting the filter-on-load and enable styles needs to be done in +".zshrc.pre" because the styles need to be set when the main setup is +executing! The other styles do not have this limitation, but enabling the +system as well as the initial filtering will obviously be done using settings +and filters that are configured at that point. +
++With respect to filter-on-load, the rule of thumb is: If you want to filter +on load, setup everything in ".zshrc.pre" otherwise ".zshrc.local" works just +as well.
@@ -449,7 +473,7 @@ than zero, in which case grml-large is used. Lastly, if $GRML_CHROOT non-empty, grml-chroot is used.
-As usual, with promtinit themes, the user may switch to a different theme using +As usual, with promptinit themes, the user may switch to a different theme using the prompt utility:
@@ -505,8 +529,9 @@ to: 'zsh: <repository name>' via zsh's vcs_info.If you got commands you consider important enough to be included in every -shell's history, you can put them into ~/.important_commands and they will be -available via the usual history lookup widgets. +shell's history, you can put them into $GRML_IMPORTANT_COMMANDS (which defaults +for backward compatibility to ~/.important_commands) and they will be available +via the usual history lookup widgets.