zsh-workers
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Bug in completion with curly braces?
Date: Thu, 19 Nov 2020 19:50:32 -0600	[thread overview]
Message-ID: <CAMP44s1suGkR83v82+C8xUUG3J8fwyuwPamujvRUPLcNyQdeJw@mail.gmail.com> (raw)

Hello,

While adding unquoted completions such as "stash@{0}" the completion
system gets confused while inside the curly braces.

For example, given:

  compadd -Q -- 'stash@{0}' 'stash@{1}'

The first completion correctly generates "stash@{", but the second one
generates curly braces, the third one does the same, and so on ad
infinitum.

I didn't specify file (-f) or any special completion, so why would zle
attempt curly brace expansion, especially if the words contain curly
braces, and the current character is a curly brace?

Here's a simple test:

----------------------------------------
#compdef foo

_foo () {
compadd -Q -- 'stash@{0}' 'stash@{1}'
}

_foo
----------------------------------------

Cheers.

-- 
Felipe Contreras


             reply	other threads:[~2020-11-20  1:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20  1:50 Felipe Contreras [this message]
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
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=CAMP44s1suGkR83v82+C8xUUG3J8fwyuwPamujvRUPLcNyQdeJw@mail.gmail.com \
    --to=felipe.contreras@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).