From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Bug in completion with curly braces?
Date: Mon, 23 Nov 2020 03:03:59 +0000 [thread overview]
Message-ID: <20201123030359.GA9114@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <CAH+w=7af7n8NH5b-8Vi2MUWAzbC7-=RQDLX1kCh1R58oMgTLUw@mail.gmail.com>
Bart Schaefer wrote on Sun, Nov 22, 2020 at 12:35:52 -0800:
> 1) _comp_options includes "NO_ignorebraces" so isset(IGNOREBRACES) is
> never true in zle_tricky.c:get_comp_string
I'm guessing that option is set so autoloaded completion functions have
predictable parsing, but that means completion code can't tell the value
of the option in the interactive environment.
In z-sy-h we solved this by declaring an assoc parameter and setting it
to the value of $options (or emulating that if zsh/parameter is
unavailable for some reason).
Sounds like a problem that would be useful to solve generically.
Cheers,
Daniel
next prev parent reply other threads:[~2020-11-23 3:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 1:50 Felipe Contreras
2020-11-20 2:52 ` Mikael Magnusson
2020-11-21 15:28 ` Daniel Shahaf
2020-11-21 21:08 ` Felipe Contreras
2020-11-21 22:32 ` Bart Schaefer
2020-11-22 0:37 ` Felipe Contreras
2020-11-22 2:28 ` Bart Schaefer
2020-11-22 2:58 ` Felipe Contreras
2020-11-22 20:35 ` Bart Schaefer
2020-11-22 21:20 ` Bart Schaefer
2020-11-23 3:03 ` Daniel Shahaf [this message]
2020-11-23 7:15 ` Bart Schaefer
2020-11-23 6:46 ` Felipe Contreras
2020-11-23 7:17 ` Bart Schaefer
2021-04-18 21:43 ` Bart Schaefer
2020-11-23 17:31 ` Bart Schaefer
2020-11-24 23:21 ` Oliver Kiddle
2020-11-25 5:06 ` Felipe Contreras
2021-12-02 19:45 ` PATCH: bashcompinit quoting (was Re: Bug in completion with curly braces?) Oliver Kiddle
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=20201123030359.GA9114@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=felipe.contreras@gmail.com \
--cc=schaefer@brasslantern.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).