From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: substitute-in-file-name and "$"
Date: Sun, 06 Jul 2003 18:53:05 +0200 [thread overview]
Message-ID: <84y8zbzjf2.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: 200307061624.h66GO0G06676@raven.dms.auburn.edu
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> What if somebody has an environment variable FOO expanding to bar and
> another file named $FOO? Several operating systems, including GNU and
> Unix, allow people to essentially use any file names of their
> choosing, no matter how perverse. Programs have to be able to handle
> that, even though that might make life complicated.
IMHO, the best approach is to have substitute-in-file-name return
"$$" for dollar signs in file names and to have all file primitives
grok this notation.
However, it suffers from being backward-incompatible.
Maybe the primitives could grok single dollar signs, too, then the
incompatibility would be restricted to file names with two adjacent
dollar signs. Let's hope these are not too common.
--
~/.signature
next prev parent reply other threads:[~2003-07-06 16:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 16:44 substitute-in-file-name and "$" Michael Albinus
2003-07-05 18:29 ` Luc Teirlinck
2003-07-05 23:16 ` Michael Albinus
2003-07-05 23:58 ` Luc Teirlinck
2003-07-06 12:20 ` Kai Großjohann
2003-07-06 12:44 ` Miles Bader
2003-07-06 14:30 ` Michael Albinus
2003-07-06 16:24 ` Luc Teirlinck
2003-07-06 16:53 ` Kai Großjohann [this message]
2003-07-07 15:48 ` Michael Albinus
2003-07-06 0:07 ` Miles Bader
2003-07-06 12:07 ` Kim F. Storm
2003-07-06 14:37 ` Michael Albinus
2003-07-06 17:06 ` Stefan Monnier
2003-07-06 17:20 ` Stefan Monnier
2003-07-07 11:50 ` Michael Albinus
2003-07-07 14:34 ` Stefan Monnier
2003-07-07 16:10 ` Michael Albinus
2003-07-09 23:47 ` Richard Stallman
2003-07-07 3:39 ` Richard Stallman
2003-07-07 21:33 ` Kevin Rodgers
2003-07-08 20:02 ` Richard Stallman
2003-07-06 18:53 ` Richard Stallman
2003-07-06 23:46 ` Kim F. Storm
2003-07-06 21:55 ` Stefan Monnier
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=84y8zbzjf2.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.