+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 +setup via styles in the ':grml:chpwd:dirstack' context. +
++To use a function based filter set the filter style for that context to the +name of a function to call every time a directory name is to be added to the +persistent dirstack. If the function's return value signals success (ie. return +value "0"), the directory name is filtered out and not added to the +persistent stack. Example: + +
+
+function my_dirstack_filter() { [[ $1 == /tmp(|/*) ]] }
+zstyle ':grml:chpwd:dirstack' filter my_dirstack_filter
+
++The pattern based filter uses a list of patterns passed to the exclude +style in the aforementioned context. Each pattern is tested and the first that +matches will keep the directory name from being added to the persistent stack. +If none of the patterns matches, the name is added. example: + +
++zstyle ':grml:chpwd:dirstack' exclude "/tmp(|/*)" "$HOME/tmp(|/*)" ++
+The function based filter is more general, the pattern based filter easier to +set up. If both filter variants are used at the same time, the function based +filter will be executed before the pattern based one. +
++If you would like to apply your filters while loading the persistent +dirstack file, set the filter-on-load boolean style (the default is +false): + +
++zstyle ':grml:chpwd:dirstack' filter-on-load true ++
+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. +
If you need to perform certain actions each time you enter certain @@ -388,7 +473,7 @@ than zero, in which case grml-large is used. Lastly, if $GRML_CHROOTgrml-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:
@@ -444,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.