GNU bug report logs - #5134
$PATH with double slashes parsing bug

Previous Next

Package: emacs;

Reported by: Sebastien Mondet <sebastien.mondet <at> gmail.com>

Date: Sun, 6 Dec 2009 12:55:05 UTC

Severity: normal

Done: Chong Yidong <cyd <at> stupidchicken.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (Emacs bug Tracking System)
To: Chong Yidong <cyd <at> stupidchicken.com>
Subject: bug#5134: marked as done ($PATH with double slashes parsing bug)
Date: Sun, 06 Dec 2009 19:15:18 +0000
[Message part 1 (text/plain, inline)]
Your message dated Sun, 06 Dec 2009 14:06:28 -0500
with message-id <87638jsz0r.fsf <at> stupidchicken.com>
and subject line Re: $PATH with double slashes parsing bug
has caused the Emacs bug report #5134,
regarding $PATH with double slashes parsing bug
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact help-debbugs <at> gnu.org
immediately.)


-- 
5134: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=5134
Emacs Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Sebastien Mondet <sebastien.mondet <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: $PATH with double slashes parsing bug
Date: Sun, 6 Dec 2009 13:53:21 +0100
[Message part 3 (text/plain, inline)]
Hi,

I discovered this strange behavior of eshell in emacs 23.1.1 (on MacOSX and
Debian Lenny, both built from source, launched with '-q').

It seems that the presence of two slashes ("//") in a path breaks the
search:

Example:

~ $ export PATH=/usr//bin
~ $ which m4
which: no m4 in (/usr//bin)
~ $ export PATH=/usr/bin
~ $ which m4
/usr/bin/m4
~ $


I mailed this to johnw <at> gnu.org (maintainer of eshell) who told me that it
seems to be an Emacs issue.

Cheers,

Sebastien Mondet
http://seb.mondet.org
[Message part 4 (text/html, inline)]
[Message part 5 (message/rfc822, inline)]
From: Chong Yidong <cyd <at> stupidchicken.com>
To: Sebastien Mondet <sebastien.mondet <at> gmail.com>
Cc: 5134-done <at> debbugs.gnu.org
Subject: Re: $PATH with double slashes parsing bug
Date: Sun, 06 Dec 2009 14:06:28 -0500
> I discovered this strange behavior of eshell in emacs 23.1.1 (on MacOSX and
> Debian Lenny, both built from source, launched with '-q').
>
> It seems that the presence of two slashes ("//") in a path breaks the
> search:
>
> Example:
>
> ~ $ export PATH=/usr//bin
> ~ $ which m4
> which: no m4 in (/usr//bin)
> ~ $ export PATH=/usr/bin
> ~ $ which m4
> /usr/bin/m4
> ~ $

I can reproduce it in the Emacs 23.1 release.  The bug already seems to
be fixed in the repository (to be 23.2).  Thanks for the bug report,
though.

This bug report was last modified 15 years and 169 days ago.

Previous Next


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