From: "Stefan Monnier" <monnier+gnu/emacs@cs.yale.edu>
Cc: emacs-devel@gnu.org
Subject: Re: substitute-in-file-name and "$"
Date: Sun, 06 Jul 2003 17:55:54 -0400 [thread overview]
Message-ID: <200307062155.h66LttNa005822@rum.cs.yale.edu> (raw)
In-Reply-To: 5xd6gnxlp9.fsf@kfs2.cua.dk
> Richard Stallman <rms@gnu.org> writes:
>
> > What I'ld like to know: Is it a general rule, that
> > substitute-in-file-name can be called only once for a given file name?
> >
> > Yes, I think that is the idea. I will document that.
> >
> > Then it should be documented in the Elisp manual, and it is a bug in
> > PC-do-completion. Or is it a more general design problem?
> >
> > I think this is a bug in PC-do-completion. Would someone like
> > to fix it?
>
> I think ido could have similar problems related to completion (it must
> expand things like $DIR to be able to present the user with the possible
> completions in that directory). How do you suggest it is fixed?
>
> I see only one possibility -- perform the substitution to make the
> completion list, but don't substitute it in the actual file-name read
> (as it does now).
>
> Is that the correct approach?
The way read-file-name-internal does it, the filename is passed to
substitute-in-file-name (to get a filename that you can pass to file
operations) and before returning the result all $ are doubled (using
double_dollars in src/fileio.c).
But for ido you probably want to do it differently because you can't
wait for an explicit TAB or SPC from the user.
Problem is that it can be difficult to relate the output of
substitute-in-file-name to its input.
Stefan
prev parent reply other threads:[~2003-07-06 21:55 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
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 [this message]
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=200307062155.h66LttNa005822@rum.cs.yale.edu \
--to=monnier+gnu/emacs@cs.yale.edu \
--cc=emacs-devel@gnu.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.
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).