unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
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 20:02:12 -0400	[thread overview]
Message-ID: <jwvbkf2egdd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87cyzilu9h.fsf@gmx.de> (Michael Albinus's message of "Sat, 19 Aug 2023 21:14:18 +0200")

> ERC should could set pcomplete-remote-ignore to t, as I have proposed

Not sure if ERC's pcomplete ever completes file names, to be honest.

>> 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.

Yes, it's OK.  I was just pointing out that pcomplete doesn't
specifically have anything to do with (completion of) file names, so the
new variable is not really relevant to "pcomplete proper" but only to
the set of defaults that are provided along with pcomplete.
The name might try and reflect that a bit more, e.g. by including
"file" somewhere.


        Stefan






  reply	other threads:[~2023-08-20  0:02 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
2023-08-20  0:02                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=jwvbkf2egdd.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=65356@debbugs.gnu.org \
    --cc=jporterbugs@gmail.com \
    --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).