zsh: update grmlzshrc to latest grml-etc-core version

[grml.org.git] / zsh / grmlzshrc.html

diff --git a/zsh/grmlzshrc.html b/zsh/grmlzshrc.html
index 41f924d..e7b7a53 100644 (file)
--- a/zsh/grmlzshrc.html
+++ b/zsh/grmlzshrc.html
@@ -96,6 +96,17 @@ This variable contains the handler to be used by COMMAND_NOT_FOUND (see above)
 and defaults to "/usr/share/command-not-found/command-not-found".
 <p></p>
 </dd>
+<dt><b>GRML_NO_APT_ALIASES</b></dt><dd>
+A non-empty value inhibits the definition of apt-specific short aliases,
+such as ag, agi, ati etc.
+<p></p>
+</dd>
+<dt><b>GRML_NO_SMALL_ALIASES</b></dt><dd>
+A non-empty value inhibits the definition of 2-letter aliases such as da.
+ls, ll, la and other common ls-related aliases are exempt from this, as are
+the aliases inhibited by GRML_NO_APT_ALIASES.
+<p></p>
+</dd>
 <dt><b>GRMLSMALL_SPECIFIC</b></dt><dd>
 Set this to zero to remove items in zsh config, which do not work in
 grml-small.
@@ -175,6 +186,15 @@ zshs inherit the dirstack of the zsh that most recently updated
 <b>DIRSTACKFILE</b>.
 </p>
 <p>
+If you would like to <i>disable</i> the persistent dirstack feature altogether,
+you can do that by setting the boolean <i>enable</i> style to <i>false</i> in the
+right context (the default is <i>true</i>):
+
+</p>
+<pre>
+zstyle ':grml:chpwd:dirstack' enable false
+</pre>
+<p>
 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 <i>filter-on-load</i> boolean style (the default is
 zstyle ':grml:chpwd:dirstack' filter-on-load true
 </pre>
 <p>
-Setting the <i>filter-on-load</i> 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 <b>at</b> <b>that</b> <b>point</b>. 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 <i>filter-on-load</i> and <i>enable</i> 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 <b>at</b> <b>that</b> <b>point</b>.
+</p>
+<p>
+With respect to <i>filter-on-load</i>, the rule of thumb is: If you want to filter
+on load, setup everything in ".zshrc.pre" otherwise ".zshrc.local" works just
+as well.
 </p>
 <h2>DIRECTORY BASED PROFILES</h2>
 <p>
@@ -449,7 +473,7 @@ than zero, in which case <b>grml-large</b> is used. Lastly, if <i>$GRML_CHROOT</
 non-empty, <b>grml-chroot</b> is used.
 </p>
 <p>
-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 <i>prompt</i> utility:
 
 </p>
@@ -505,8 +529,9 @@ to: <b>'zsh: &lt;repository name&gt;'</b> via zsh's vcs_info.
 <h2>PERSISTENT HISTORY</h2>
 <p>
 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.
 </p>
 <h1>REFERENCE</h1>
 <h2>ENVIRONMENT VARIABLES</h2>