help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: zsh-workers@zsh.org
Subject: PATCH: _brace_parameter: add (-)
Date: Sun,  3 Apr 2022 11:23:28 +0200	[thread overview]
Message-ID: <20220403092328.25740-1-mikachu@gmail.com> (raw)
In-Reply-To: <6e5aae82-dc48-4763-953e-efb470508019@www.fastmail.com>

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.

 Completion/Zsh/Context/_brace_parameter | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Completion/Zsh/Context/_brace_parameter b/Completion/Zsh/Context/_brace_parameter
index e020e048ad..66be4f7cd8 100644
--- a/Completion/Zsh/Context/_brace_parameter
+++ b/Completion/Zsh/Context/_brace_parameter
@@ -156,7 +156,8 @@ if [[ $PREFIX = *'${('[^\)]# ]]; then
     "i:sort case-insensitively"
     "k:substitute keys of associative arrays"
     "L:lower case all letters"
-    "n:sort decimal integers numerically"
+    "n:sort positive decimal integers numerically"
+    "-:sort decimal integers numerically"
     "o:sort in ascending order (lexically if no other sort option)"
     "O:sort in descending order (lexically if no other sort option)"
     "P:use parameter value as name of parameter for redirected lookup"

  reply	other threads:[~2022-04-03  9:23 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 ` Mikael Magnusson [this message]
2022-04-03 21:13   ` PATCH: _brace_parameter: add (-) Mikael Magnusson
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

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220403092328.25740-1-mikachu@gmail.com \
    --to=mikachu@gmail.com \
    --cc=zsh-workers@zsh.org \


* 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).