From: Mikael Magnusson <email@example.com>
Subject: Re: PATCH: _brace_parameter: add (-)
Date: Sun, 3 Apr 2022 23:13:17 +0200 [thread overview]
Message-ID: <CAHYJk3SRcaKqtwedCEfMFsn4dqnnn5xNy7_HgbSSaxodiUQv5Q@mail.gmail.com> (raw)
On 4/3/22, Mikael Magnusson <firstname.lastname@example.org> wrote:
> I looked at adding fc -s which is probably not that hard, but I noticed
> that fc -e<tab> and fc -e <tab> both don't complete commands which it
> looks like they should.
> (the completer has -e+ which means it only expects -ecommand but in
> practice -e - also works, as well as the manpage listing it with the
> space when talking about -s.
This was just triple pebkac, I had this in .zhsrc to avoid getting my
entire history listed back to me by the fc tab completion:
zstyle ':completion:*:*:(history|fc):*' tag-order options -
Changed it to this, and all is well:
zstyle ':completion:*:*:(history|fc):*' tag-order '! events' -
zstyle ':completion:*:*:(history|fc):*' prefix-needed false
(and the second part was me misremembering which is which between -e-
and -e+ in _arguments specifications).
And finally I also missed the fact that dana already added -s.
next prev parent reply other threads:[~2022-04-03 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 3:29 [PATCH] Change documentation, dedication, loose ends dana
2022-04-03 9:23 ` PATCH: _brace_parameter: add (-) Mikael Magnusson
2022-04-03 21:13 ` Mikael Magnusson [this message]
2022-04-03 16:34 ` [PATCH] Change documentation, dedication, loose ends Bart Schaefer
2022-04-03 19:18 ` dana
2022-04-03 20:59 ` Mikael Magnusson
2022-04-08 19:29 ` dana
2022-04-10 21:20 ` Daniel Shahaf
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).