From d5c57fe7a50f391c1c12a25e32d6e4139f63a977 Mon Sep 17 00:00:00 2001 From: Michael Prokop Date: Mon, 19 Jun 2017 11:27:59 +0200 Subject: [PATCH] zsh: update grmlzshrc to latest grml-etc-core version --- zsh/grmlzshrc.html | 43 ++++++++++++++++++++++++++++++++++--------- 1 file changed, 34 insertions(+), 9 deletions(-) diff --git a/zsh/grmlzshrc.html b/zsh/grmlzshrc.html index 41f924d..e7b7a53 100644 --- 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".

+
GRML_NO_APT_ALIASES
+A non-empty value inhibits the definition of apt-specific short aliases, +such as ag, agi, ati etc. +

+
+
GRML_NO_SMALL_ALIASES
+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. +

+
GRMLSMALL_SPECIFIC
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 DIRSTACKFILE.

+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.

DIRECTORY BASED PROFILES

@@ -449,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:

@@ -505,8 +529,9 @@ to: 'zsh: <repository name>' via zsh's vcs_info.

PERSISTENT HISTORY

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.

REFERENCE

ENVIRONMENT VARIABLES

-- 2.1.4