Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: (concat "/dir/name/" "foo") --> (expand-file-name "foo" "/dir/name/")
Date: 14 Oct 2000 00:19:50 +0200	[thread overview]
Message-ID: <vafk8bco03d.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3r95kzboy.fsf@multivac.student.cwru.edu>

On 13 Oct 2000, Paul Jarc wrote:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>> In the Gnus source code, we often have constructs like this:
>> 
>>     (concat "/dir/name/" "file-name")
>> 
>> I think this should be replaced with:
>> 
>>     (expand-file-name "file-name" "/dir/name/")
>> 
>> What do you think?
> 
> It depends on the contents of "file-name".  If it might contain
> something that really needs to be normalized, then it should be
> handed to expand-file-name.  If it should be interpreted literally,
> then expand-file-name might do something unintended.  Consider,
> e.g., "foo/../bar", where foo is a symlink.

Ah.  Right.  Okay, I won't go into a frenzy to change all them concats
to expand-file-name, then :-)

Your comment about expanding a file name once and to reuse the
expanded file name also makes sense.  Hm.

kai
-- 
I like BOTH kinds of music.



  reply	other threads:[~2000-10-13 22:19 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 [this message]
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
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=vafk8bco03d.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --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).