From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: emacs-devel@gnu.org
Subject: Re: exec-path "/:" prefix; file-name-handler-*; start-process
Date: Tue, 20 Aug 2002 10:55:00 +0200 [thread overview]
Message-ID: <vafit25ap0b.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0208200051450.28524-100000@hkn.eecs.berkeley.edu> (Karl Chen's message of "Tue, 20 Aug 2002 01:28:04 -0700 (PDT)")
Karl Chen <quarl@hkn.eecs.berkeley.edu> writes:
> Why does initializing `exec-path' need to prepend a "/:" to paths that
> "would otherwise be treated as magic" ?
> [emacs.c : decode_env_path ():
> ...
> tem = Ffind_file_name_handler (element, Qt);
> if (! NILP (tem))
> element = concat2 (build_string ("/:"), element);
> ...
> ]
>
> All single-directory (single slash) paths in PATH such as /bin turn
> into /:/bin. This may be the fault of sloppy regexes in
> ange-ftp. Seems like a dirty hack, having to say "this is a normal
> path."
Just a random thought on this: it's clearly useful that Ange-FTP
grabs filenames like these -- this enables user/host name
completion.
But now, Tramp takes over those files, and so in principle, one could
require the user to use "/ftp:foo" filenames when user/host name
completion is desired, so it might not be necessary anymore to have
Ange-FTP (or Tramp) grab filenames like "/foo".
I'm not sure what to do, though.
kai
--
A large number of young women don't trust men with beards. (BFBS Radio)
next prev parent reply other threads:[~2002-08-20 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 8:28 exec-path "/:" prefix; file-name-handler-*; start-process Karl Chen
2002-08-20 8:55 ` Kai Großjohann [this message]
2002-08-24 2:33 ` Richard Stallman
2002-08-24 10:31 ` Kai Großjohann
2002-08-25 5:27 ` Richard Stallman
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=vafit25ap0b.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).