zshrc: readd setopt nonomatch

This reverts 5e198dcbbd29464371bd7b2b110d26ad8fa44781
("zshrc: Don't unset `nomatch' anymore") again.

Whereas "setopt nomatch" would be the right[tm] thing to do, the
behaviour is annoying everyone used to other shells than Zsh. As
we used the nonomatch setting since ages to avoid confusion
especially amongst the users comming from Bash let's keep it that
way.

Acked-by: Alexander Wirt <formorer@grml.org>
Acked-by: Christian Hofstaedtler <ch@grml.org>
Acked-by: Ulrich Dangel <mru@grml.org>
Signed-off-by: Michael Prokop <mika@grml.org>

diff --git a/doc/grmlzshrc.t2t b/doc/grmlzshrc.t2t
index 3aae18f..22d4de2 100644 (file)
--- a/doc/grmlzshrc.t2t
+++ b/doc/grmlzshrc.t2t
@@ -379,6 +379,11 @@ A wildcard character never matches a leading '.'.
 : **nohup** <grml>
 Do not send the hangup signal (HUP:1) to running jobs when the shell exits.
 
+: **nonomatch** <grml>
+If a pattern for filename generation has no matches, do not print an error
+and leave it unchanged in the argument list. This also applies to file
+expansion of an initial `~' or `='.
+
 : **notify**
 Report the status of background jobs immediately, rather than waiting until
 just before printing a prompt.

diff --git a/etc/zsh/zshrc b/etc/zsh/zshrc
index fe5bb78..00cf7fe 100644 (file)
--- a/etc/zsh/zshrc
+++ b/etc/zsh/zshrc
@@ -288,6 +288,9 @@ setopt extended_glob
 # display PID when suspending processes as well
 setopt longlistjobs
 
+# try to avoid the 'zsh: no matches found...'
+setopt nonomatch
+
 # report the status of backgrounds jobs immediately
 setopt notify