unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
	Daniel Pettersson <daniel@dpettersson.net>
Cc: 57905@debbugs.gnu.org
Subject: bug#57905: [PATCH] Fix eshell directory and executable completion on action t
Date: Sun, 18 Sep 2022 17:31:01 -0700	[thread overview]
Message-ID: <e90504aa-bd9c-3696-32a2-ccd1dc53a7cc@gmail.com> (raw)
In-Reply-To: <87a66x55hy.fsf@gnus.org>

On 9/18/2022 3:41 AM, Lars Ingebrigtsen wrote:
> Daniel Pettersson <daniel@dpettersson.net> writes:
> 
>> This issue is not present with one completion as further down the call
>> stack `completion-file-name-table' is called with action t, which concates
>> completion string directory with completion candidate.
>>
>> Possible solution:
> 
> Hm...  I'm not that familiar with how this works in eshell myself;
> perhaps Jim has some comments -- added to the CCs.

With the caveats that I don't know much about pcomplete (maybe someone 
who does would have something interesting to say about this patch?) and 
that I haven't built Emacs with the patch, I think the logic here makes 
sense.

Some regression tests would be nice though. I've been trying to add 
tests as I go through various parts of Eshell, but I haven't looked much 
at the "interactive" bits like em-cmpl.el yet. 'eshell-test/forward-arg' 
in test/lisp/eshell/eshell-tests.el might make for an ok basis to adapt 
into some completion tests (which could probably then go into 
.../em-cmpl-tests.el).

That said, I wouldn't object to merging this without regression tests; 
it doesn't seem fair to me to expect patch authors to write tests when 
the component they're patching doesn't have tests in the first place. :)





  reply	other threads:[~2022-09-19  0:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17 22:55 bug#57905: [PATCH] Fix eshell directory and executable completion on action t Daniel Pettersson
2022-09-18  7:40 ` Eli Zaretskii
2022-09-18 10:41 ` Lars Ingebrigtsen
2022-09-19  0:31   ` Jim Porter [this message]
2022-09-19  8:22     ` Lars Ingebrigtsen
2022-09-19 20:27       ` Daniel Pettersson
2022-09-19 20:35         ` Lars Ingebrigtsen

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=e90504aa-bd9c-3696-32a2-ccd1dc53a7cc@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=57905@debbugs.gnu.org \
    --cc=daniel@dpettersson.net \
    --cc=larsi@gnus.org \
    /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).