From 7621f9f5110f33a52256c30659935be0fbdbe889 Mon Sep 17 00:00:00 2001 From: Michael Prokop Date: Tue, 6 Dec 2011 14:30:33 +0100 Subject: [PATCH] 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 Acked-by: Christian Hofstaedtler Acked-by: Ulrich Dangel Signed-off-by: Michael Prokop --- doc/grmlzshrc.t2t | 5 +++++ etc/zsh/zshrc | 3 +++ 2 files changed, 8 insertions(+) diff --git a/doc/grmlzshrc.t2t b/doc/grmlzshrc.t2t index 3aae18f..22d4de2 100644 --- a/doc/grmlzshrc.t2t +++ b/doc/grmlzshrc.t2t @@ -379,6 +379,11 @@ A wildcard character never matches a leading '.'. : **nohup** Do not send the hangup signal (HUP:1) to running jobs when the shell exits. +: **nonomatch** +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 --- 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 -- 2.1.4