From: Felipe Contreras <felipe.contreras@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Daniel Shahaf <d.s@daniel.shahaf.name>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Bug in completion with curly braces?
Date: Sat, 21 Nov 2020 18:37:51 -0600 [thread overview]
Message-ID: <CAMP44s3MSx6_Zkz-vwy4ayPr-9Zdg1M6xfcmALzVyqb01w2zBA@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7ZcJ67eq1cKuSDtb_XxOmcyuk2Esw1ebVSgGhXSAx1V9g@mail.gmail.com>
On Sat, Nov 21, 2020 at 4:33 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
> I even tried forcing "ignorebraces" to be on during completion, but
> the best that does (in combo with other changes to the compadd) is to
> convert the word on the line to be "stash@\{" which you don't want.
I don't want to provide "stash@\{0\}" because that's not what I want
to complete.
But if it's the only way completion can work, I think the completion
system should add it itself, even if I didn't provide it.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2020-11-22 0:38 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 [this message]
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
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=CAMP44s3MSx6_Zkz-vwy4ayPr-9Zdg1M6xfcmALzVyqb01w2zBA@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=d.s@daniel.shahaf.name \
--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).