problem with multicomp

problem with multicomp

[Carlos Carvalho]

With pre5, I get this:

zsh%  cd mem/7/ar
zsh: sofar[2]: parameter not set

Also, I have autocd enabled, but multicomp doesn't get invoked when
press TAB.

On another issue, I missed the explanation about nocorrect now being a
builtin. Why is this so? This is inconsistent. The other modifiers
should then also be builtins. Also, if you use "noglob nocorrect etc."
it doesn't work, you have to do "nocorrect noglob etc.". I think it
should work, because noglob should work with anything, including
nocorrect.

Carlos

Re: problem with multicomp

[Zoltan Hidvegi]

> With pre5, I get this:
> 
> zsh%  cd mem/7/ar
> zsh: sofar[2]: parameter not set

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.

> Also, I have autocd enabled, but multicomp doesn't get invoked when
> press TAB.

Because multicomp does not work on words in command position I think.
compctl -C should be used for that.  See zshcompctl(1).

> On another issue, I missed the explanation about nocorrect now being a
> builtin. Why is this so? This is inconsistent. The other modifiers
> should then also be builtins. Also, if you use "noglob nocorrect etc."
> it doesn't work, you have to do "nocorrect noglob etc.". I think it
> should work, because noglob should work with anything, including
> nocorrect.

nocorrect is a reserved word and the other prefixes are builtins.
nocorrect must be recognized when parsing the input since spelling
correction is done during parsing so it cannot be a builtin.  Reserved
words are only recognized in command position or after other reserved words
(well I oversimplificated it) that's why noroccect must come before the
other modifiers.  For the parser noglob is the same as echo so if
echo nocorrect does not work, noglob nocorrect will not work either.  The
only way to change this is to make the other prefixes reserved words but
that would mean that foo=exec ; $foo something will not work.

Zoltan

Re: problem with multicomp

[Zoltan Hidvegi]

> 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 :

Re: problem with multicomp

[Zoltan Hidvegi]

> Zoltan Hidvegi (hzoli@cs.elte.hu) wrote on 2 August 1996 20:16:
>  >I'm sure that you set the nounset option.
> 
> Yes, this is the problem. Thanks. HOWEVER, if I do setopt|grep set it
> doesn't appear!! I haven't really followed the details of the NO_
> changes to the options, but if you're required to say setopt nounset
> for it to work, it should appear in setopt's listing.

setopt nounset is the same as unsetopt unset.  Try unsetopt|grep unset.

Zoltan

Re: problem with multicomp

[Zefram]

>Yes, this is the problem. Thanks. HOWEVER, if I do setopt|grep set it
>doesn't appear!!

The correct way to check for an option being set is `[[ -o name ]]`.
`[[ -o nounset ]]` still works, and means exactly the same thing it
used to.

-zefram

Re: problem with multicomp

[Carlos Carvalho]

Zoltan Hidvegi (hzoli@cs.elte.hu) wrote on 2 August 1996 20:16:
 >I'm sure that you set the nounset option.

Yes, this is the problem. Thanks. HOWEVER, if I do setopt|grep set it
doesn't appear!! I haven't really followed the details of the NO_
changes to the options, but if you're required to say setopt nounset
for it to work, it should appear in setopt's listing.

 >nocorrect is a reserved word and the other prefixes are builtins.

Convincing.

Carlos