From 3dd6b29905c3b35191f5b474ab3bc667ee50556e Mon Sep 17 00:00:00 2001
From: Tomas Sedovic <tomas@sedovic.cz>
Date: Sat, 7 Jul 2012 13:48:05 +0200
Subject: [PATCH] Supress ZSH "no matches found" error

Fixes issue #39

ZSH's default globbing behaviour differs from Bash. If there is no
match, ZSH itself will print the error message.

This means that piping a commantd's STDERR to /dev/null will not
hide it.

By unsetting the NOMATCH option we get a behaviour similar to Bash.

Signed-off-by: Tomas Sedovic <tomas@sedovic.cz>
---
 nvm.sh | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/nvm.sh b/nvm.sh
index 448936b..f65f31f 100755
--- a/nvm.sh
+++ b/nvm.sh
@@ -10,6 +10,10 @@ if [ ! -d "$NVM_DIR" ]; then
     export NVM_DIR=$(cd $(dirname ${BASH_SOURCE[0]:-$0}) && pwd)
 fi
 
+# Make zsh glob matching behave same as bash
+# This fixes the "zsh: no matches found" errors
+unsetopt nomatch 2>/dev/null
+
 # Expand a version using the version cache
 nvm_version()
 {