From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: server-local variables
Date: Mon, 31 Oct 2016 05:30:41 +0200 [thread overview]
Message-ID: <83mvhlp53y.fsf@gnu.org> (raw)
In-Reply-To: <87k2cp7f9b.fsf@gmx.de> (message from Michael Albinus on Sun, 30 Oct 2016 21:28:48 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: emacs-devel@gnu.org
> Date: Sun, 30 Oct 2016 21:28:48 +0100
>
> > Do these functions really have to live in files.el? They are used by
> > Tramp, don't they?
>
> Sure, Tramp (and ange-ftp, perhaps also url-handlers) will use them
> internally. But they shall also be good for other packages. Bug#24394
> discusses `shell-file-name' and `shell-command-switch'. Bug#3736
> discusses server-local settings for `null-device'. And in bug#18940 I've
> proposed server-local settings of `process-environment' (well, Stefan did
> object, but this was not discussed until its end, I believe).
>
> If you fear that it would inflate files.el too much, we could locate
> these functions in files-x.el.
My reasoning was that if this doesn't have to be preloaded, it should
live in a package that's most likely to be loaded when they are needed
anyway. I think Tramp is the likely user; I find it much harder to
imagine the others using it, but whenever I use a remote file name,
Tramp is auto-loaded, so Tramp sounds like a good place.
I don't object to files-x.el, if you think that is better.
next prev parent reply other threads:[~2016-10-31 3:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 18:39 server-local variables Michael Albinus
2016-10-30 20:08 ` Eli Zaretskii
2016-10-30 20:28 ` Michael Albinus
2016-10-31 3:30 ` Eli Zaretskii [this message]
2016-10-31 9:54 ` Michael Albinus
2016-10-31 11:17 ` Phil Sainty
2016-10-31 12:45 ` Óscar Fuentes
2016-10-31 15:42 ` Michael Albinus
2016-10-31 20:15 ` Phil Sainty
2016-10-31 13:43 ` Stefan Monnier
2016-10-31 16:30 ` Michael Albinus
2016-10-31 12:39 ` Ted Zlatanov
2016-10-31 13:36 ` Stefan Monnier
2016-10-31 21:03 ` Drew Adams
2016-11-01 2:08 ` Stefan Monnier
2016-11-01 5:08 ` Drew Adams
2016-10-31 16:26 ` Michael Albinus
2016-10-31 17:31 ` Ted Zlatanov
2016-10-31 20:47 ` Michael Albinus
2016-11-01 13:22 ` Ted Zlatanov
2016-11-14 14:02 ` Michael Albinus
2016-11-15 15:02 ` GnuTLS per-connection variables (was: server-local variables) Ted Zlatanov
2016-11-24 12:50 ` GnuTLS per-connection variables Michael Albinus
2016-11-29 16:07 ` Ted Zlatanov
2016-11-28 18:54 ` Michael Albinus
2016-12-05 15:09 ` Michael Albinus
2016-12-05 16:27 ` Ted Zlatanov
2016-12-05 16:49 ` 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
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=83mvhlp53y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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).