From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: (concat "/dir/name/" "foo") --> (expand-file-name "foo" "/dir/name/")
Date: 22 Oct 2000 20:45:01 -0400 [thread overview]
Message-ID: <m3r958mllo.fsf@multivac.student.cwru.edu> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "22 Oct 2000 20:51:04 +0200"
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> I have tried hard to come up with a reason why expand-file-name could
> fail to be idempotent, but I can't come up with a reason.
A mischevious, badly-written, or maybe just an unconventional handler
might give an expanded name that would, when re-expanded, give a
different name. But this probably doesn't happen in most normal
situations.
> But in any case, using concat to create a file name from a directory
> and a relative path name is not a good thing, I think.
Why not?
paul
next prev parent reply other threads:[~2000-10-23 0:45 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
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 [this message]
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=m3r958mllo.fsf@multivac.student.cwru.edu \
--to=prj@po.cwru.edu \
/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).