zsh-users
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Parse time options
Date: Wed, 17 Feb 2016 08:11:28 +0100	[thread overview]
Message-ID: <CAKc7PVCKJsi1UdsB46-kO0hmDnKusYAqQYXLKEVtmmPp4jHa3A@mail.gmail.com> (raw)
In-Reply-To: <160216110149.ZM31855@torch.brasslantern.com>

On 16 February 2016 at 20:01, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Feb 16, 11:36am, Sebastian Gniazdowski wrote:
> }
> } for i in "${STRESS_TEST_OPTIONS[@]}"; do
> }     setopt "$i"
> }     zcompile -R "$fname" 2>/dev/null
> }    unsetopt "$i"
> } done
>
> Presumably you're starting from a state where none of these options are
> set, so that it's correct to unsetopt them again?
>
> } This seems to work fine with NO_SHORT_LOOPS and IGNORE_BRACES. Is
> } there one other option that would break zcompile in case of some
> } forbidden (by the option) syntax? Except maybe for the CSH_* options.
>
> Well, there's NO_BARE_GLOB_QUAL, IGNORE_CLOSE_BRACES, MULTI_FUNC_DEF,
> maybe C_PRECEDENCES, possibly POSIX_IDENTIFIERS.

Thanks. In my "collection" (test collection) of 51 plugins I didn't
found one that wouldn't compile with the options:

https://asciinema.org/a/ana24je5nnvr8iy9wp8anmptg

However a simple test file revealed that indeed MULTI_FUNC_DEF can
make compilation fail. Couldn't construct test for NO_BARE_GLOB_QUAL
and C_PRECEDENCES, already am using IGNORE_CLOSE_BRACES, and
POSIX_IDENTIFIERS seems to not affect zcompile.

Best regards,
Sebastian Gniazdowski


      reply	other threads:[~2016-02-17  7:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 10:36 Sebastian Gniazdowski
2016-02-16 12:11 ` Sebastian Gniazdowski
2016-02-16 19:01   ` Bart Schaefer
2016-02-17  7:11     ` Sebastian Gniazdowski [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=CAKc7PVCKJsi1UdsB46-kO0hmDnKusYAqQYXLKEVtmmPp4jHa3A@mail.gmail.com \
    --to=sgniazdowski@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@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).