Re: zsh funcs

Re: zsh funcs

[Vinnie Shelton]

Somewhere between 3.0.0 and 3.0.1-test3, my namedir function (can't
remember the attribution, sorry) stopped working:

  # Shorten the current directory to a ~ name
  # (Only works as a zsh function)
 
  $1=$PWD
  : ~$1

It used to name the current directory; now it outputs this error:

zsh: no such file or directory: tf=/vobs/devel/shared/hsd100/testfiles

Vin Shelton

Re: zsh funcs

[Zefram]

>  $1=$PWD
>  : ~$1

This should be

eval $1=\$PWD
: ~$1

-zefram

Re: zsh funcs

[Vinnie Shelton]

zefram@dcs.warwick.ac.uk said:
> This should be

> eval $1=\$PWD : ~$1

> -zefram 

Thanks, but why is this necessary?  Was the change in behavior intentional?

--vin

Re: zsh funcs

[Zoltan Hidvegi]

> zefram@dcs.warwick.ac.uk said:
> > This should be
> 
> > eval $1=\$PWD : ~$1
> 
> > -zefram 
> 
> Thanks, but why is this necessary?  Was the change in behavior intentional?

I would not say that it was intentional.  I always thought that eval is
necessary for that.  In addvars() there is an explicite singsub() call to
substitute the left-hand-side of an assignment which is now only used to
substitute the index of the assignment.  The change was that the lexer
gives the assignment token only if a word of the form number=value or
name=value or name[index]=value appears in command position where name has
only alphanumeric characters and underscores and starts with a letter or an
underscore.  This fixes problems with 1foo=bar assignments.

Zoltan