From: Chong Yidong <cyd@stupidchicken.com>
To: rms@gnu.org
Cc: Michael Albinus <michael.albinus@gmx.de>, emacs-devel@gnu.org
Subject: Re: [david.reitter@gmail.com: file-remote-p malfunctions at site-start (file-name-handler-alist init)]
Date: Mon, 26 Mar 2007 00:40:25 -0400 [thread overview]
Message-ID: <87bqigk47a.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1HVgGG-00072V-J6@fencepost.gnu.org> (Richard Stallman's message of "Sun\, 25 Mar 2007 23\:52\:48 -0400")
> If a site-start.el file is created with the following contents:
>
> (print file-name-handler-alist)
> (print (file-remote-p "/ssh:dreitter@ssh:/home/dreitter/test2"))
>
> the output of the last expression is nil for me.
> It should (correctly) be non-nil.
>
> The reason for that is that `file-name-handler-alist' does not
> contain handlers for tramp file names when the site-start file is
> loaded - at a later point, the appropriate handlers are added.
This could conceivably be achieved by moving
tramp-register-file-name-handlers from after-init-hook to
before-init-hook. On the other hand, the risk of making a change to
the init sequence at this stage probably outweighs the marginal
benefit; I don't think the above is a very common scenario.
What do people think?
next prev parent reply other threads:[~2007-03-26 4:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 3:52 [david.reitter@gmail.com: file-remote-p malfunctions at site-start (file-name-handler-alist init)] Richard Stallman
2007-03-26 4:40 ` Chong Yidong [this message]
2007-03-26 13:14 ` Stefan Monnier
2007-03-26 13:37 ` Michael Albinus
2007-03-26 14:16 ` Chong Yidong
2007-03-26 14:44 ` Michael Albinus
2007-03-26 15:21 ` Stefan Monnier
2007-03-27 20:59 ` Chong Yidong
2007-03-31 18:47 ` Michael Albinus
2007-03-31 19:41 ` David Kastrup
2007-03-31 20:02 ` Pretest Chong Yidong
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=87bqigk47a.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=rms@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).