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

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (Emacs bug Tracking System)
To: Sebastien Mondet <sebastien.mondet <at> gmail.com>
Subject: bug#5134 closed by Chong Yidong <cyd <at> stupidchicken.com> (Re:
 $PATH with double slashes parsing bug)
Date: Sun, 06 Dec 2009 19:15:19 +0000

[Message part 1 (text/plain, inline)]

This is an automatic notification regarding your bug report
which was filed against the emacs package:

#5134: $PATH with double slashes parsing bug

It has been closed by Chong Yidong <cyd <at> stupidchicken.com>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Chong Yidong <cyd <at> stupidchicken.com> by
replying to this email.


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

[Message part 3 (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 4 (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 5 (text/html, inline)]

Previous Next

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