From: Lars Ingebrigtsen <larsi@gnus.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: 57673@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#57673: [PATCH] Parse --help messages for pcomplete
Date: Thu, 08 Sep 2022 14:39:22 +0200 [thread overview]
Message-ID: <877d2e3urp.fsf@gnus.org> (raw)
In-Reply-To: <87zgfagqfs.fsf@gmail.com> (Augusto Stoffel's message of "Thu, 08 Sep 2022 11:34:31 +0200")
Augusto Stoffel <arstoffel@gmail.com> writes:
> Find attached a “worse is better” approach for pcomplete, where we parse
> help messages to generate a list of completions.
Hm, interesting. Perhaps Stefan has comments here; added to the CCs.
> This is still a sketch. I've added pcomplete functions for a random
> selection of commands to see if this works reasonably, and I think it
> probably does. But in any case I don't think it would make sense to try
> and add completions as detailed as the ones bash provides; there is an
> awful lot of logic in the files under /usr/share/bash-completion and I
> don't think anyone would want to redo that work.
I'm wholly unfamiliar with how bash does completions. But is there any
reasonable way to reuse the bash completion framework here?
next prev parent reply other threads:[~2022-09-08 12:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 9:34 bug#57673: [PATCH] Parse --help messages for pcomplete Augusto Stoffel
2022-09-08 12:39 ` Lars Ingebrigtsen [this message]
2022-09-08 13:05 ` Augusto Stoffel
2022-09-09 17:02 ` Lars Ingebrigtsen
2022-09-10 9:20 ` Augusto Stoffel
2022-09-08 20:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-08 21:53 ` Augusto Stoffel
2022-09-09 2:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-10 9:45 ` Augusto Stoffel
2022-09-10 14:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-10 16:12 ` Augusto Stoffel
2022-09-14 19:15 ` Augusto Stoffel
2022-09-14 19:21 ` Lars Ingebrigtsen
2022-09-14 19:41 ` Augusto Stoffel
2022-09-14 19:48 ` Lars Ingebrigtsen
2022-09-14 19:57 ` Augusto Stoffel
2022-09-14 19:59 ` Lars Ingebrigtsen
2022-09-14 20:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-14 21:11 ` Lars Ingebrigtsen
2022-09-14 21:23 ` Augusto Stoffel
2022-09-14 21:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877d2e3urp.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=57673@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).