From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: GnuTLS per-connection variables (was: server-local variables)
Date: Tue, 15 Nov 2016 10:02:10 -0500 [thread overview]
Message-ID: <87fumsyefh.fsf_-_@lifelogs.com> (raw)
In-Reply-To: 87shqu5fcl.fsf@gmx.de
On Mon, 14 Nov 2016 15:02:50 +0100 Michael Albinus <michael.albinus@gmx.de> wrote:
MA> finally, I've committed a patch to master implementing connection-local
MA> variables. For details, see
MA> (info "(elisp)Connection Local Variables")
Looks great, thank you.
I looked at migrating gnutls.el to use this new facility. I have some
questions (and maybe Lars and others can add more).
* how will users see and configure the settings per class?
* how will users select the class per server? The NSM may be useful
here, since it already does some per-connection checks and storage.
* how to migrate users from the current defcustoms in
(customize-group 'gnutls) to this new system? Do we support both for
some time?
Thanks
Ted
next prev parent reply other threads:[~2016-11-15 15:02 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
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 ` Ted Zlatanov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fumsyefh.fsf_-_@lifelogs.com \
--to=tzz@lifelogs.com \
--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 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.