From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: schwab@suse.de, npostavs@gmail.com, 36502@debbugs.gnu.org,
monnier@iro.umontreal.ca, dan@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 [thread overview]
Message-ID: <83v9w73gb5.fsf@gnu.org> (raw)
In-Reply-To: <E1hlicA-0001Tf-Ex@fencepost.gnu.org> (message from Richard Stallman on Thu, 11 Jul 2019 19:36:38 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: eliz@gnu.org, dan@dpsutton.com, npostavs@gmail.com,
> 36502@debbugs.gnu.org, monnier@iro.umontreal.ca,
> schwab@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.
next prev parent reply other threads:[~2019-07-12 6:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 16:48 bug#36502: 27.0.50; infinite loop in file-name-case-insensitive-p Daniel Sutton
2019-07-04 18:08 ` Ken Brown
[not found] ` <CAMfzp7bhcmeY7QP4-ALfmBE4OojJthcYEVLR79zj-FrGx5s+WA@mail.gmail.com>
2019-07-05 1:32 ` Ken Brown
[not found] ` <CAMfzp7brsFLdpi04pDAL+O_yVuF7=EERzinVBKoQyTaLUtgwDA@mail.gmail.com>
[not found] ` <CAMfzp7Y=wA8_V=Tvm1iOtyXM-kqKZyx41Q4phJfnwmygHhJWLA@mail.gmail.com>
2019-07-05 3:05 ` bug#36502: Fwd: " Daniel Sutton
2019-07-06 12:49 ` Ken Brown
2019-07-06 13:27 ` Noam Postavsky
2019-07-06 15:38 ` Ken Brown
2019-07-06 16:14 ` Eli Zaretskii
2019-07-07 14:09 ` Ken Brown
2019-07-07 14:37 ` Eli Zaretskii
2019-07-07 19:30 ` Ken Brown
2019-07-08 12:25 ` Eli Zaretskii
2019-07-08 13:36 ` Ken Brown
2019-07-08 13:59 ` Eli Zaretskii
2019-07-08 15:17 ` Ken Brown
2019-07-08 16:44 ` Ken Brown
2019-07-08 17:23 ` Eli Zaretskii
2019-07-10 21:57 ` Ken Brown
2019-07-11 23:36 ` Richard Stallman
2019-07-12 6:41 ` Eli Zaretskii [this message]
2019-07-12 20:18 ` Ken Brown
2019-07-15 13:39 ` Ken Brown
2019-07-19 7:00 ` Eli Zaretskii
2019-07-20 9:19 ` Eli Zaretskii
2019-07-20 14:27 ` Ken Brown
2019-07-20 15:52 ` Eli Zaretskii
2019-07-21 2:32 ` Paul Eggert
2019-07-21 14:21 ` Eli Zaretskii
2019-07-21 14:30 ` Ken Brown
2019-07-22 2:16 ` Ken Brown
2019-07-24 21:36 ` Paul Eggert
2019-07-24 22:47 ` Ken Brown
2019-07-26 11:04 ` Andy Moreton
2019-07-08 14:37 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83v9w73gb5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36502@debbugs.gnu.org \
--cc=dan@dpsutton.com \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@gmail.com \
--cc=rms@gnu.org \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).