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: bug#16026: Connection specific settings and proxies Date: Mon, 13 Feb 2017 10:54:59 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <8760kekrvw.fsf@flea> References: <86wqjnwa9u.fsf@somewhere.org> <871u1s38m3.fsf@flea.lifelogs.com> <877f5j2i67.fsf@gnus.org> <87a8a8paru.fsf@lifelogs.com> <87r33jnvn1.fsf@lifelogs.com> <87h94fqjq7.fsf@gmx.de> <87o9ykr6os.fsf@flea> <87mve3ffov.fsf__41803.1231420629$1486136780$gmane$org@gmx.de> <87k293ny36.fsf@flea> <87d1enz4p2.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 1487001320 17403 195.159.176.226 (13 Feb 2017 15:55:20 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 13 Feb 2017 15:55:20 +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 Mon Feb 13 16:55:16 2017 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 1cdIyB-0004J8-9t for ged-emacs-devel@m.gmane.org; Mon, 13 Feb 2017 16:55:15 +0100 Original-Received: from localhost ([::1]:57805 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cdIyH-0007cX-46 for ged-emacs-devel@m.gmane.org; Mon, 13 Feb 2017 10:55:21 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59714) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cdIy9-0007cI-By for emacs-devel@gnu.org; Mon, 13 Feb 2017 10:55:14 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cdIy6-00045H-Mv for emacs-devel@gnu.org; Mon, 13 Feb 2017 10:55:13 -0500 Original-Received: from [195.159.176.226] (port=44231 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cdIy6-00044N-Gb for emacs-devel@gnu.org; Mon, 13 Feb 2017 10:55:10 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cdIxy-0003Wp-1Q for emacs-devel@gnu.org; Mon, 13 Feb 2017 16:55:02 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 44 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:roOhOUOFTWzt8Br7jK6HL0EzQz4= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] 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:212339 Archived-At: On Sun, 12 Feb 2017 18:42:17 +0100 Michael Albinus wrote: MA> Ted Zlatanov writes: MA> Your proposal looks OK to me. U, Y and Z shall be regexps, X a symbol MA> (or also a regexp?). All of them shall be optional. >> >> Wonderful. I propose that the application should be a defgroup symbol, >> and every connection profile should be required to have a defgroup. >> >> That would give us an implicit connection profile hierarchy and a place >> to hook connection profile customizations at the UI level. >> >> So defining connection profiles would be something like this: >> >> (add-connection-profiles :user U :defgroup X :protocol Y :machine Z >> :profile 'UXYZ :vars '(...)) >> >> (add-connection-profiles :profile 'general :vars '(...)) MA> Well, I'm a little bit lost. What does the defgroup here? I understand MA> that replaces what you have called initially an application, but I don't MA> see what defcustoms shall be placed now under the defgroup MA> hierarchy. Could you pls give an example? It's just a categorization. It would simply be the defgroup of an existing application. That way you don't have to invent a new symbol for every application that wants to use a connection profile and has the defgroup declared already. For example, 'gnus for Gnus. So in `M-x customize-group Gnus' you would maybe see an extra button to list and modify the Gnus-specific connection profiles. Connection profiles without a defgroup (application) symbol belong to all applications. MA> I also know that there are users reluctant to the customization MA> machinery. Wouldn't we loose them? Customize wouldn't be required. It's just an easy way to connect the profile with other application-specific customizations, but users should be able to add or modify profiles directly. Does that make sense? Ted