bug#5134: marked as done ($PATH with double slashes parsing bug)

[owner@emacsbugs.donarmstrong.com (Emacs bug Tracking System)]

[-- Attachment #1: Type: text/plain, Size: 864 bytes --]

Your message dated Sun, 06 Dec 2009 14:06:28 -0500
with message-id <87638jsz0r.fsf@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 owner@emacsbugs.donarmstrong.com
immediately.)


-- 
5134: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=5134
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 4326 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 504 bytes --]

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@gnu.org (maintainer of eshell) who told me that it
seems to be an Emacs issue.

Cheers,

Sebastien Mondet
http://seb.mondet.org

[-- Attachment #2.1.2: Type: text/html, Size: 770 bytes --]

[-- Attachment #3: Type: message/rfc822, Size: 1997 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: Sebastien Mondet <sebastien.mondet@gmail.com>
Cc: 5134-done@emacsbugs.donarmstrong.com
Subject: Re: $PATH with double slashes parsing bug
Date: Sun, 06 Dec 2009 14:06:28 -0500
Message-ID: <87638jsz0r.fsf@stupidchicken.com>

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