From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: "O. simplex" <ordinatio.simplex@protonmail.ch>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Solution: Bu report - unix/_gpg completion broken
Date: Sat, 6 Jun 2020 08:19:09 +0000 [thread overview]
Message-ID: <20200606081909.33d488c5@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <M7YSmAUEta0Gj8cEz4B9Gn5KKAunBIeatP3PsxZ68C1YOpcag2nmBp-uirDw9qmL9UZ90zKlkVMJ8FmGFrLmbl3R40U4r-wT5ktHeAwIZrg=@protonmail.ch>
O. simplex wrote on Sat, 06 Jun 2020 06:38 +0000:
> Sorry, there is some time since my report.
>
> The error is caused because i set shfileexpansion.
>
> Steps after run % zsh -f:
> % autoload -U compinit
> % compinit
> % # if I try gpg aucompletion now, will work as expected
> % # so you was right
> % # now the detail in my personal config
> % setopt shfileexpansion
> % # if I try now, the error ( _gpg:176: \[]*} not found ) will appear
>
> Since I removed the option shfileexpansion from my zshrc, and gpg completion worked as expected.
Thanks. This should fix it:
diff --git a/Completion/compinit b/Completion/compinit
index f0f8421df..f4ff270f7 100644
--- a/Completion/compinit
+++ b/Completion/compinit
@@ -159,6 +159,7 @@ _comp_options=(
NO_shglob
NO_warnnestedvar
NO_warncreateglobal
+ NO_shfileexpansion
)
# And this one should be `eval'ed at the beginning of every entry point
next prev parent reply other threads:[~2020-06-06 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 1:42 O. simplex
2020-05-15 5:21 ` Solution: " O. simplex
2020-05-15 8:53 ` Daniel Shahaf
[not found] ` <Ww4N4kk6TH_2Cp6_B0A709kTrD8LonXJPl6qmAAx75k0eQ7OczWUSwo7LCJOnXJm-nyuAVtdf8HOIGGb0krLeM0Z_fRWy723j1XTVA6vgek=@protonmail.ch>
2020-06-06 6:38 ` O. simplex
2020-06-06 8:19 ` Daniel Shahaf [this message]
2020-06-09 23:07 ` Oliver Kiddle
2020-06-10 13:44 ` Daniel Shahaf
2020-06-23 21:23 ` SH_FILE_EXPANSION broken with process substitution Oliver Kiddle
2020-06-24 10:28 ` Peter Stephenson
2020-06-24 10:46 ` Peter Stephenson
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=20200606081909.33d488c5@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=ordinatio.simplex@protonmail.ch \
--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).