From: Jim Porter <jporterbugs@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Michael Albinus <michael.albinus@gmx.de>
Cc: 65356@debbugs.gnu.org
Subject: bug#65356: 30.0.50; [wishlist] Support Tramp method, user name and host name completion in eshell
Date: Fri, 18 Aug 2023 20:26:54 -0700 [thread overview]
Message-ID: <ec2e5867-be57-7baa-16fc-628f7c0aa3dd@gmail.com> (raw)
In-Reply-To: <jwvo7j4f0gn.fsf-monnier+emacs@gnu.org>
On 8/18/2023 3:33 PM, Stefan Monnier via Bug reports for GNU Emacs, the
Swiss army knife of text editors wrote:
>> Yes. However, there is already another problem in shell-mode. My patch
>> completes only incomplete Tramp file names, like "/ss". Complete Tramp
>> file names are handled by pcomplete-dirs already. So we see in a *shell*
>> buffer, w/o my patch:
>
> Good point.
>
> Still, we have the problem that `pcomplete/<CMD>` should be used only
> for external commands (because they are independent from the language
> used to write the command, a.k.a the shell), but for things like `cd` we
> should be more precise to distinguish the completion rules for Eshell's
> `cd` from those of bash's `cd`.
That should be possible by defining 'pcomplete/eshell-mode/CMD', but
that runs into two issues: 1) it's annoying to manually write all of
these, and 2) there may be other contexts in Eshell we want to
tab-complete remote directories that aren't covered by the
command-specific Pcomplete functions like that.
(#1 should be fixable with a new version of 'eshell-eval-using-options',
but I haven't looked at that in much detail yet.)
next prev parent reply other threads:[~2023-08-19 3:26 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 [this message]
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
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=ec2e5867-be57-7baa-16fc-628f7c0aa3dd@gmail.com \
--to=jporterbugs@gmail.com \
--cc=65356@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--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).