From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Jim Porter <jporterbugs@gmail.com>, 65356@debbugs.gnu.org
Subject: bug#65356: 30.0.50; [wishlist] Support Tramp method, user name and host name completion in eshell
Date: Sat, 19 Aug 2023 21:14:18 +0200 [thread overview]
Message-ID: <87cyzilu9h.fsf@gmx.de> (raw)
In-Reply-To: <jwvil9aevfa.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 19 Aug 2023 14:37:49 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
Hi Stefan,
>> I gave it another try. There is a new user option pcomplete-remote-ignore.
>
> FWIW, `pcomplete` is a generic completion library for use when
> completing things like function/command calls where the things to be
> completely at point depend on the position of the argument and the
> command/function that is called.
>
> It was originally designed for Eshell where those functions/commands are
> actual commands in the host system, but it's also used for things like
> ERC where the commands have nothing to do with executables installed in
> your machine.
ERC should could set pcomplete-remote-ignore to t, as I have proposed
for shell buffers. Likely, even this isn't needed. The default (w/o my
patch) is to complete remote file names. This hasn't disturbed ERC until
now.
> In theory is could be used for completion in code buffers where it
> could provide specialized completion depending on the expected type of
> the argument being completed.
Hmm. Does it mean you agree with the patch, or not? My change should affect
only file name completion, any other completion should work as before.
> Stefan
Best regards, Michael.
next prev parent reply other threads:[~2023-08-19 19:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 18:01 bug#65356: 30.0.50; [wishlist] Support Tramp method, user name and host name completion in eshell Michael Albinus
2023-08-18 3:31 ` Jim Porter
2023-08-18 6:45 ` Michael Albinus
2023-08-18 11:43 ` Michael Albinus
2023-08-18 13:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 15:12 ` Michael Albinus
2023-08-18 22:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 3:26 ` Jim Porter
2023-08-19 17:48 ` Michael Albinus
2023-08-19 18:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 19:14 ` Michael Albinus [this message]
2023-08-20 0:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 7:50 ` Michael Albinus
2023-08-20 5:23 ` Jim Porter
2023-08-20 10:53 ` Michael Albinus
2023-08-23 0:30 ` Jim Porter
2023-08-23 7:56 ` Michael Albinus
2023-08-18 17:50 ` Michael Albinus
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=87cyzilu9h.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=65356@debbugs.gnu.org \
--cc=jporterbugs@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).