From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: server-local variables Date: Tue, 01 Nov 2016 09:22:37 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87pomf5o82.fsf@lifelogs.com> References: <87r36x7kb9.fsf@gmx.de> <87wpgoofp3.fsf@lifelogs.com> <87mvhk4h9c.fsf@gmx.de> <87a8dk77do.fsf@lifelogs.com> <87zilk5jq3.fsf@gmx.de> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1478006725 2590 195.159.176.226 (1 Nov 2016 13:25:25 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 1 Nov 2016 13:25:25 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 01 14:25:16 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1Z3Z-0004kI-E6 for ged-emacs-devel@m.gmane.org; Tue, 01 Nov 2016 14:24:49 +0100 Original-Received: from localhost ([::1]:47937 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1Z3c-0000N4-4C for ged-emacs-devel@m.gmane.org; Tue, 01 Nov 2016 09:24:52 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41813) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1Z2c-0000Kr-Vs for emacs-devel@gnu.org; Tue, 01 Nov 2016 09:23:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c1Z2X-0004rF-7E for emacs-devel@gnu.org; Tue, 01 Nov 2016 09:23:50 -0400 Original-Received: from [195.159.176.226] (port=49681 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c1Z2X-0004pm-1M for emacs-devel@gnu.org; Tue, 01 Nov 2016 09:23:45 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1c1Z1v-0001T8-HC for emacs-devel@gnu.org; Tue, 01 Nov 2016 14:23:07 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 42 Original-X-Complaints-To: usenet@blaine.gmane.org X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never Cancel-Lock: sha1:vWdOjdF/lG1JyZE+L03Coe/6zAU= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:209057 Archived-At: On Mon, 31 Oct 2016 21:47:32 +0100 Michael Albinus wrote: MA> Ted Zlatanov writes: >> (with-process-classes temporary-sudo-override temporary-shell-override >> ansible-host-environment >> ...do something) >> >> It would take care of setting the connection-local variables inside the >> scope and unwinding them afterwards. MA> I see. The problem is unwinding the local variables; they could exist MA> already as local variables when entering the macro. But in general it MA> shall be possible, when implementing proper book-keeping. That would be great, thank you for considering it. MA> Btw, I wouldn't call it with-*process*-classes. server-local (or MA> connection-local) variables could be applied to any buffer with a remote MA> default-directory. Any name is fine with me. It's really a pattern match against some buffer characteristics and has a lot in common with file-and-dir-local variables (which pattern match against the file location). >> OK, please take a look at the GnuTLS glue code in gnutls.el and you'll >> see what I need from this facility. I'm happy to start using it there as >> soon as the API is solidified. I have a TODO item (discussed with Lars a >> few months ago) to implement something like this facility so it's great >> to see it's not an isolated need :) MA> I've looked shortly on this. Seems like you need a mechanism for MA> `gnutls-boot-parameters'. Yes, exactly. It needs to be flexible and augmentable to allow layering of GnuTLS options; currently it's pretty much the opposite. The GnuTLS priority strings, which are on the C side, have interesting parallels with your concept of classes that represent sets of parameters. Thanks Ted