From: sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor])
Cc: emacs-devel@gnu.org,
Tramp Developers <tramp-devel@mail.freesoftware.fsf.org>
Subject: Re: Tramp and file-name-handler-alist
Date: Thu, 24 Oct 2002 11:20:30 +0200 [thread overview]
Message-ID: <y9ln0p4b3c1.fsf@sams.informatik.uni-tuebingen.de> (raw)
In-Reply-To: <nq4rbvlrjt.fsf@alcatel.de> (Michael Albinus's message of "09 Oct 2002 14:34:14 +0200")
>>>>> "Michael" == Michael Albinus <Michael.Albinus@alcatel.de> writes:
Michael> So it would be desirable to have a more general possibility deciding a
Michael> file-name-handler. Perfect would be an extension to
Michael> file-name-handler-alist, which doesn't allow a regexp only but also a
Michael> function for decision. Something like
Michael> ; forward to Ange-FTP or EFS
Michael> ((tramp-ftp-file-name-p . tramp-ftp-file-name-handler)
Michael> ; the rest of the pack
Michael> (tramp-file-name-p . tramp-file-name-handler)
Michael> ("\\`/:" . file-name-non-special))
Michael> For backward compatibility reasons, this wouldn't be a short term
Michael> solution. With the current interface, I see 2 possible approaches:
Michael> - Do it within tramp-file-name-handler. The filename is analyzed, and
Michael> then the respective handler for a method is launched. This handler
Michael> calls the respective primitive functions related to the method.
Michael> The disadvantage is, that tramp-file-name-handler is called with
Michael> different paramter lists for the primitives, and sometimes even the
Michael> filename isn't part of.
Michael> - Replace find-file-name-handler by an own implementation. In case of
Michael> Tramp file names it returns the handler related to actual method,
Michael> otherwise it calls the original find-file-name-handler.
Michael> Are there other possibilities to solve the problem? And which approach
Michael> is to prefer?
I've always argued for putting a meta-mechanism on top of
Tramp/EFS/ange-ftp, which would have a compositional way of specifying
how file-name handlers are assembled, and which includes a way of
using predicates in the manner described.
I do think that distinguishing remote file names from local ones
syntactically is a good thing, but once that distinction is made (and
it can be made in `file-name-handler-alist'), we'd be home-free.
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
next prev parent reply other threads:[~2002-10-24 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 12:34 Tramp and file-name-handler-alist Michael Albinus
2002-10-24 9:20 ` Michael Sperber [Mr. Preprocessor] [this message]
2002-10-27 10:46 ` Michael Albinus
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=y9ln0p4b3c1.fsf@sams.informatik.uni-tuebingen.de \
--to=sperber@informatik.uni-tuebingen.de \
--cc=emacs-devel@gnu.org \
--cc=tramp-devel@mail.freesoftware.fsf.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 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.