From: Dave Love <d.love@dl.ac.uk>
Cc: ding@gnus.org
Subject: Re: (concat "/dir/name/" "foo") --> (expand-file-name "foo" "/dir/name/")
Date: Mon, 16 Oct 2000 19:12:18 +0100 [thread overview]
Message-ID: <200010161812.TAA25555@djlvig.dl.ac.uk> (raw)
In-Reply-To: <m3r95kzboy.fsf@multivac.student.cwru.edu>
>>>>> "PJ" == Paul Jarc <prj@po.cwru.edu> writes:
PJ> It depends on the contents of "file-name". If it might contain
PJ> something that really needs to be normalized, then it should be
PJ> handed to expand-file-name. If it should be interpreted
PJ> literally, then expand-file-name might do something unintended.
PJ> Consider, e.g., "foo/../bar", where foo is a symlink.
I don't understand this. One of the points about expand-file-name is
that it gets to do magic depending on the file name. I have changed
such uses of `concat' where I've found it in the sources and I'd need
some convincing that that's wrong, as well as a contribution to the
Lisp manual.
PJ> I think file-name-as-directory and directory-file-name are
PJ> idempotent on all platforms, although they aren't documented as
PJ> such, AFAICT.
I'm not sure why that's relevant, but even if it's generally true in
the absence of handlers -- I don't know -- I don't think you can say
what a random handler might do, e.g. for remote files on an arbitrary
system.
next prev parent reply other threads:[~2000-10-16 18:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-13 20:55 Kai Großjohann
2000-10-13 21:13 ` Paul Jarc
2000-10-13 22:19 ` Kai Großjohann
2000-10-16 18:12 ` Dave Love [this message]
2000-10-16 20:39 ` Paul Jarc
2000-10-16 22:36 ` Daniel Pittman
2000-10-18 17:55 ` Dave Love
2000-10-18 21:35 ` Paul Jarc
2000-10-22 16:00 ` Dave Love
2000-10-22 18:10 ` Paul Jarc
2000-10-22 18:51 ` Kai Großjohann
2000-10-23 0:45 ` Paul Jarc
2000-10-23 7:52 ` Kai Großjohann
2000-10-23 15:29 ` Paul Jarc
2000-10-19 1:11 ` Daniel Pittman
2000-10-22 16:02 ` Dave Love
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200010161812.TAA25555@djlvig.dl.ac.uk \
--to=d.love@dl.ac.uk \
--cc=ding@gnus.org \
/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.
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 NNTP newsgroup(s).