zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh workers <zsh-workers@zsh.org>
Cc: Mikael Magnusson <mikachu@gmail.com>,
	Sebastian Gniazdowski <sgniazdowski@gmail.com>
Subject: Re: Zsh will not parse an autoload function when it has short loops
Date: Fri, 28 Aug 2015 09:29:17 -0700	[thread overview]
Message-ID: <150828092917.ZM6880@torch.brasslantern.com> (raw)
In-Reply-To: <CAHYJk3T+57uLeS6u4tH92sZZc5QqmSztMZPd9eR5w9P9Tspjjw@mail.gmail.com>

On Aug 28,  8:43am, Mikael Magnusson wrote:
} Subject: Re: Zsh will not parse an autoload function when it has short loo
}
} 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]'
} 
} This is expected, the shortloops option affects parsing of files.

There's a straightforward workaround for this:  Instead of

    autoload shortloopfn

use

    emulate zsh -c 'autoload shortloopfn'

then zsh emulation scope will be in effect when the function is called,
and everything will parse as expected during loading.

However, it appears "autoload +X" does not respect the emulation options
put into effect at the time the function was originally marked for
autoloading.  I can't decide whether that is a bug.  The reason that the
"autoload -c" trick works is because the function ends up being defined
approximately as

    shortloopfn() {
       emulate zsh	# "sticky emulation"
       autoload -X shortloopfn
    }

so the emulation is restored before the load, and obviously this is not
equivalent to "autoload +X" run explicitly.

-- 
Barton E. Schaefer


      reply	other threads:[~2015-08-28 16:29 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
2015-08-28 16:29   ` Bart Schaefer [this message]

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=150828092917.ZM6880@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=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).