From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: "Aaron Schrab" <aaron@schrab.com>, "Jacob Gelbman" <gelbman@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: Completion script for the ctags program
Date: Wed, 03 Mar 2021 23:43:36 +0000 [thread overview]
Message-ID: <a9ede188-6245-4872-a0b6-080d8bc3cf5b@www.fastmail.com> (raw)
In-Reply-To: <YEAbslNIzMH1LyPf@pug.qqx.org>
Aaron Schrab wrote on Wed, 03 Mar 2021 23:28 +00:00:
> 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).
FWIW:
% git -c <TAB>
zsh: do you wish to see all 288 possibilities (73 lines)?
That's basicaly a hardcoded list, though I think it does look in `git
config --list` too for wildcard instances and in-house options.
% rsync --<TAB>
zsh: do you wish to see all 450 possibilities (151 lines)?
Static list.
% git co <TAB>
zsh: do you wish to see all 605 possibilities (165 lines)?
Based on repository contents. Uses tags for sectioning.
% curl -<TAB>
zsh: do you wish to see all 661 possibilities (221 lines)?
Static list.
% gcc -<TAB>
zsh: do you wish to see all 2495 possibilities (833 lines)?
Static list. It's long because all -Wfoo/-fbar/-mbaz arguments are
treated as first-class options. I suppose that may want to be changed.
> 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.
That's what pws proposed and I independently implemented. Try the _f
function I posted.
There's --<lang>-foo options too (with the replaceable part first), and
there's «--foo-<lang> bar» as two words, but that's solvable.
> 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.
*nod*
Cheers,
Daniel
next prev parent reply other threads:[~2021-03-03 23:44 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
2021-03-03 23:43 ` Daniel Shahaf [this message]
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=a9ede188-6245-4872-a0b6-080d8bc3cf5b@www.fastmail.com \
--to=d.s@daniel.shahaf.name \
--cc=aaron@schrab.com \
--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).