From: Aaron Schrab <aaron@schrab.com>
To: Jacob Gelbman <gelbman@gmail.com>
Cc: Daniel Shahaf <d.s@daniel.shahaf.name>, zsh-workers@zsh.org
Subject: Re: Completion script for the ctags program
Date: Wed, 3 Mar 2021 18:28:50 -0500 [thread overview]
Message-ID: <YEAbslNIzMH1LyPf@pug.qqx.org> (raw)
In-Reply-To: <D1EF8EAB-E50F-4E69-832F-E7B2CE7CD852@gmail.com>
At 16:08 -0600 03 Mar 2021, Jacob Gelbman <gelbman@gmail.com> wrote:
>Just I don’t think it should add all the options that it could be
>because it would make the output too long to read. I can’t think of
>another command that has options like this,
One example would be ack (AKA ack-grep) which also has options for quite
a few programming languages. Although in its case there isn't any
common prefix for the options to turn on a language; it's just options
like `ack --python`. It also supports options like `ack --nopython` to
disable languages.
The completion for that *does* include all of those options. Yes, all of
that does make it quite verbose, but that can also be the case even
without that type of dynamic option names (I'm mainly thinking of curl
here). I still think that having the completion options actually usable
as-is is still better than requiring the user to edit the completion
results. It would likely be even better in this case if the language
portion could be treated more as the argument to an option, and so the
language list would only be presented after the prefix was already
selected.
But I'd also say that even a completion script which generates those
options in need of editing would still be an improvement over nothing.
next prev parent reply other threads:[~2021-03-03 23:29 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 3:11 Jacob Gelbman
2021-02-23 10:11 ` Peter Stephenson
2021-02-23 22:20 ` Oliver Kiddle
2021-02-23 22:45 ` Bart Schaefer
2021-02-23 23:51 ` Oliver Kiddle
2021-02-24 0:52 ` Bart Schaefer
2021-02-24 13:47 ` Daniel Shahaf
2021-02-23 23:05 ` Mikael Magnusson
2021-02-23 21:39 ` Oliver Kiddle
2021-02-24 4:45 ` Jacob Gelbman
2021-02-24 7:20 ` Jacob Gelbman
2021-02-24 9:26 ` Peter Stephenson
2021-02-24 14:24 ` Daniel Shahaf
2021-02-24 18:58 ` Jacob Gelbman
2021-02-24 19:01 ` Bart Schaefer
2021-03-03 20:02 ` Daniel Shahaf
2021-03-03 20:39 ` Jacob Gelbman
2021-03-03 21:40 ` Peter Stephenson
2021-03-03 22:06 ` Daniel Shahaf
2021-03-03 22:08 ` Jacob Gelbman
2021-03-03 23:28 ` Aaron Schrab [this message]
2021-03-03 23:43 ` Daniel Shahaf
2021-03-03 23:35 ` Daniel Shahaf
2021-03-07 19:18 ` Jacob Gelbman
2021-03-07 21:42 ` Daniel Shahaf
2021-03-07 21:57 ` Jacob Gelbman
2021-03-07 22:10 ` Daniel Shahaf
2021-03-11 16:15 ` Daniel Shahaf
2021-03-11 17:08 ` Jacob Gelbman
2021-03-20 1:43 ` Lawrence Velázquez
2021-03-27 16:14 ` Lawrence Velázquez
2021-03-27 20:43 ` Daniel Shahaf
2021-03-28 23:29 ` Oliver Kiddle
2021-03-29 8:54 ` Peter Stephenson
2021-03-29 15:07 ` EOL normalization? (Was: Completion script for the ctags program) Lawrence Velázquez
2021-03-29 15:34 ` Daniel Shahaf
2021-03-29 15:41 ` Lawrence Velázquez
2021-02-24 21:54 ` Completion script for the ctags program dana
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=YEAbslNIzMH1LyPf@pug.qqx.org \
--to=aaron@schrab.com \
--cc=d.s@daniel.shahaf.name \
--cc=gelbman@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).