GNU bug report logs - #36502
27.0.50; infinite loop in file-name-case-insensitive-p

Previous Next

Package: emacs;

Reported by: Daniel Sutton <dan <at> dpsutton.com>

Date: Thu, 4 Jul 2019 16:53:02 UTC

Severity: normal

Found in version 27.0.50

Done: Ken Brown <kbrown <at> cornell.edu>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: rms <at> gnu.org
Cc: kbrown <at> cornell.edu, schwab <at> suse.de, npostavs <at> gmail.com, 36502 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca, dan <at> dpsutton.com
Subject: bug#36502: Fwd: bug#36502: 27.0.50; infinite loop in file-name-case-insensitive-p
Date: Fri, 12 Jul 2019 09:41:50 +0300
> From: Richard Stallman <rms <at> gnu.org>
> Cc: eliz <at> gnu.org, dan <at> dpsutton.com, npostavs <at> gmail.com,
> 	36502 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca,
> 	schwab <at> suse.de
> Date: Thu, 11 Jul 2019 19:36:38 -0400
> 
>   > (let ((default-directory "~foo"))
>   >    (expand-file-name "bar"))
>   > => "~foo/~foo/bar"
> 
> That is not right, but I think "~foo/bar" would be right.

No, I think this should yield an absolute file name starting with a
slash (on Posix systems).

>   > Part of what's confusing here is that file-name-absolute-p returns
>   > t on file names starting with "~", even though its doc string
>   > explicitly states that such a file name is not absolute.
> 
> This contradiction is not good.  But I would like to point out
> that, in a certain sesne, a name starting with ~ is absolute.
> It is not relative to the current directory.

It is only absolute if what follows ~ is a slash or a name of an
existing user.  I think we should fix the inconsistency in that
direction.




This bug report was last modified 5 years and 304 days ago.

Previous Next


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