zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: Zsh will not parse an autoload function when it has short loops
Date: Fri, 28 Aug 2015 08:43:20 +0200	[thread overview]
Message-ID: <CAHYJk3T+57uLeS6u4tH92sZZc5QqmSztMZPd9eR5w9P9Tspjjw@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVD_zqcB3iWsU_6RzYEeOy8Kax8LFwE=sh36rAXVHgfo5Q@mail.gmail.com>

On Fri, Aug 28, 2015 at 8:39 AM, Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
> Hello
>
> I've created autoload function "bug" in /usr/share/zsh/.../functions, and
> when run, it gives:
>
> bug:9: parse error near `list[$i]'
>
> Adding echo's to the file and changing various things revealed no reaction.
> This means that the file isn't actually run by zsh - apparently the message
> comes from some initial parsing stage.
>
> Here is the file:
>
> emulate -L zsh
>
> setopt localoptions typesetsilent localtraps extendedglob shortloops
>
> while (( 1 )); do
>     # No influence, the code isn't run at all
>     # typeset -a VLIST_NONSELECTABLE_ELEMENTS
>     if [ ! -z "$VLIST_SEARCH_BUFFER" ]; then
>         [ "$#VLIST_NONSELECTABLE_ELEMENTS" -gt 0 ] && for i
> ("${(nO)VLIST_NONSELECTABLE_ELEMENTS[@]}") list[$i]=()
>     fi
>
> done

This is expected, the shortloops option affects parsing of files. As
you noticed the code is not run, only parsed, so therefore the setopt
shortloops inside the function has no effect, but you use shortloops
syntax which means it has to be on when you parse it. Long story
short: don't use shortloops syntax in portable code.

-- 
Mikael Magnusson


  reply	other threads:[~2015-08-28  6:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28  6:39 Sebastian Gniazdowski
2015-08-28  6:43 ` Mikael Magnusson [this message]
2015-08-28 16:29   ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHYJk3T+57uLeS6u4tH92sZZc5QqmSztMZPd9eR5w9P9Tspjjw@mail.gmail.com \
    --to=mikachu@gmail.com \
    --cc=sgniazdowski@gmail.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).