From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: server-local variables
Date: Mon, 31 Oct 2016 17:30:44 +0100 [thread overview]
Message-ID: <87ins84h1n.fsf@gmx.de> (raw)
In-Reply-To: <jwva8dkiqq1.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Mon, 31 Oct 2016 09:43:40 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> I do not want to restrict server-local variables to Tramp, even if there
>> isn't such other use case yet.
>
> I have the suspicion that if another user than Tramp ever comes along,
> it could have a really hard time using your API, because your API is
> designed very clearly from Tramp's point of view.
It fits Tramp's need, yes. But the design is a simple clone of
`dir-locals-set-class-variables', `dir-locals-set-directory-class' and
`hack-dir-local-variables-non-file-buffer'.
> I can agree that it might be desirable that this feature should be able
> to set non-Tramp variables on a per-host basis (e.g. shell-file-name,
> null-device, ...), but other than that I think it makes sense to add it
> as a Tramp-only API at least at first.
It would be easier for me, because I would have more control over it :-)
But I still believe there will be non-Tramp use cases. As already said,
ange-ftp comes to mind.
> Stefan
Best regards, Michael.
next prev parent reply other threads:[~2016-10-31 16: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
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 [this message]
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=87ins84h1n.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).