Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: problem with multicomp
- X-seq: zsh-workers 1898
- From: Zoltan Hidvegi <hzoli@xxxxxxxxxx>
- To: hzoli@xxxxxxxxxx (Zoltan Hidvegi)
- Subject: Re: problem with multicomp
- Date: Fri, 2 Aug 1996 20:19:55 +0200 (MET DST)
- Cc: carlos@xxxxxxxxxxxxxxxxxxxxx, zsh-workers@xxxxxxxxxxxxxxx
- In-reply-to: <199608021816.UAA05863@xxxxxxxxxxxxxxxxx> from Zoltan Hidvegi at "Aug 2, 96 08:16:14 pm"
- Organization: Dept. of Comp. Sci., Eotvos University, Budapest, Hungary
- Phone: (36 1)2669833 ext: 2667, home phone: (36 1) 2752368
> I'm sure that you set the nounset option. Try the patch below to
> multicomp. One may say that it is a bug to that nounset gives an error
> message when subscript is out of range bug as I know zsh always did that.
> The oldest version I have is zsh-2.6-beta13-hzoli13 does this.
I forgot the patch. Here it is.
Zoltan
--- Functions/multicomp 1996/05/02 22:57:04 2.0
+++ Functions/multicomp 1996/08/02 17:36:08
@@ -16,7 +16,7 @@
local pref head sofar origtop newtop globdir="(-/)" wild
setopt localoptions nullglob rcexpandparam globdots
-unsetopt markdirs globsubst shwordsplit
+unsetopt markdirs globsubst shwordsplit nounset
pref="${1}$2"
# Hack to allow programmable completion to select multicomp after a :
Messages sorted by:
Reverse Date,
Date,
Thread,
Author