GNU bug report logs - #1206
double slash // in read-shell-command completion

Previous Next

Package: emacs;

Reported by: Eli Zaretskii <eliz <at> gnu.org>

Date: Sun, 19 Oct 2008 15:30:03 UTC

Severity: minor

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #38 received at 1206-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Mauro Aranda <maurooaranda <at> gmail.com>
Cc: 1206-done <at> debbugs.gnu.org
Subject: Re: bug#1206: double slash // in read-shell-command completion
Date: Sat, 15 Feb 2025 17:34:18 +0200
> Date: Sat, 15 Feb 2025 10:33:59 -0300
> From: Mauro Aranda <maurooaranda <at> gmail.com>
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
>  >> From: Glenn Morris <rgm <at> gnu.org>
>  >> Cc: 1206 <at> debbugs.gnu.org
>  >> Date: Tue, 01 Mar 2011 23:14:15 -0500
>  >>
>  >>
>  >> Do you still see this? I don't think I do.
>  >
>  > No, but it still isn't right: it inserts an extra slash. That is, I
>  > get something like "d:/gnu/emacs-foo//lisp".  The extra slash in this
>  > situation is really not nice...
>  >
>  > This happens both with Emacs 23.3 RC1 and with the development trunk.
> 
> This is an old bug report you filed, that I used to be able to reproduce
> years ago when I was looking for old bugs to fix.
> 
> Thing is, I'm not able to reproduce it anymore.  I did this:
> 
> In a directory that looks like this:
> .
> ├── emacs
> │   ├── emacs-27
> │   │   ├── lisp
> │   ├── emacs-28
> │   │   ├── lisp
> │   ├── emacs-29
> │   │   ├── lisp
> 
> emacs -Q
> M-!
> ls ~/emacs/emacs-2/lisp
> Move point to the slash before "lisp".
> TAB
> 
> Emacs shows:
> 3 possible completions:
> emacs-27/
> emacs-28/
> emacs-29/
> 
> Select one and now the minibuffer shows:
> ~/emacs/emacs-27/lisp
> 
> 
> Emacs 28 shows the behavior you reported.  Then Emacs 29 showed: "No
> match", which is wrong.  But then, after the following commit, I can't
> reproduce it anymore:

Yes, this is now fixed in Emacs 30 (Emacs 29.4 is still wrong, albeit
in a different way).

So I'm closing this bug, thanks.  Good riddance!




This bug report was last modified 150 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.