unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 16026@debbugs.gnu.org, Stefan Monnier <monnier@IRO.UMontreal.CA>,
	Emacs developers <emacs-devel@gnu.org>
Subject: bug#16026: Connection specific settings and proxies
Date: Mon, 20 Feb 2017 17:01:10 +0100	[thread overview]
Message-ID: <m3r32svol5.fsf@stories> (raw)
In-Reply-To: <87d1enz4p2.fsf@gmx.de> (Michael Albinus's message of "Sun, 12 Feb 2017 18:42:17 +0100")

Michael Albinus <michael.albinus@gmx.de> writes:

>> 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 '(...))
>
> Well, I'm a little bit lost. What does the defgroup here? I understand
> that replaces what you have called initially an application, but I don't
> see what defcustoms shall be placed now under the defgroup
> hierarchy. Could you pls give an example?
>
> I also know that there are users reluctant to the customization
> machinery. Wouldn't we loose them?

Yeah, I think a special mode to tweak connection specific variables
would be better, perhaps...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2017-02-20 16:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7856.1385996719.10748.bug-gnu-emacs@gnu.org>
     [not found] ` <mailman.7856.1385996719.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-12-02 15:19   ` bug#16026: Gnus shouldn't use old connections Sebastien Vauban
2013-12-02 16:12     ` Stefan Monnier
2013-12-04 16:04       ` Ted Zlatanov
2017-01-25 16:55         ` Lars Ingebrigtsen
2017-01-25 18:26           ` Stefan Monnier
2017-01-30 20:12             ` Ted Zlatanov
2017-01-30 22:38               ` Stefan Monnier
2017-01-31 14:37                 ` Ted Zlatanov
2017-01-31 16:26                   ` Michael Albinus
2017-02-02  3:43                     ` bug#16026: Connection specific settings and proxies Lars Ingebrigtsen
2017-02-02 14:46                       ` Ted Zlatanov
2017-02-02 23:58                       ` Daniel McClanahan
     [not found]                       ` <87o9ykr6os.fsf@flea>
2017-02-03 15:37                         ` Michael Albinus
2017-02-06 15:22                           ` Ted Zlatanov
     [not found]                           ` <87k293ny36.fsf@flea>
2017-02-12 17:42                             ` Michael Albinus
     [not found]                             ` <87d1enz4p2.fsf@gmx.de>
2017-02-20 16:01                               ` Lars Ingebrigtsen [this message]

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=m3r32svol5.fsf@stories \
    --to=larsi@gnus.org \
    --cc=16026@debbugs.gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    --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).