From: Augusto Stoffel <arstoffel@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57673@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#57673: [PATCH] Parse --help messages for pcomplete
Date: Sat, 10 Sep 2022 11:20:28 +0200 [thread overview]
Message-ID: <87zgf7egbn.fsf@gmail.com> (raw)
In-Reply-To: <8735d0wkf0.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 09 Sep 2022 19:02:27 +0200")
On Fri, 9 Sep 2022 at 19:02, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Augusto Stoffel <arstoffel@gmail.com> writes:
>
>> IIUC this package is like Python's
>> "native completion", i.e., it relies on sending "prefix\t\t" to the bash
>> process and hopes readline will do its thing.
>
> I see.
>
>> Exploiting bash could work nicely if it had a
>> please_complete_this_partial_command function, but this doesn't seem
>> possible. I might be wrong, though.
>
> I wondered whether we could use those files more directly -- executing
> them or something in the right context? (Like I said, I know nothing
> about how this works. 😀)
Yeah, I'm not sure either, but I would suspect the MELPA package
mentioned above didn't choose the hardest path gratuitously :-). It
would be good to hear from someone who knows for sure, though.
One additional advantage of parsing the help files which I didn't
mention before is that we get a modicum of self-documenting behavior,
since we can collect the argument descriptions. For example, while
completing you can remind yourself which switch is for recursive, -r or
-R.
next prev parent reply other threads:[~2022-09-10 9:20 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
2022-09-08 13:05 ` Augusto Stoffel
2022-09-09 17:02 ` Lars Ingebrigtsen
2022-09-10 9:20 ` Augusto Stoffel [this message]
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=87zgf7egbn.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=57673@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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).