From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: bug#16026: Connection specific settings and proxies
Date: Tue, 14 Feb 2017 10:01:58 -0500 [thread overview]
Message-ID: <87mvdoke8p.fsf@lifelogs.com> (raw)
In-Reply-To: 87r332xdyl.fsf@gmx.de
On Mon, 13 Feb 2017 17:17:22 +0100 Michael Albinus <michael.albinus@gmx.de> wrote:
MA> We shouldn't even call this "defgroup", but still "application". We
MA> might say then, if the application symbol is also an existing defgroup,
MA> then there will be bonus features in the customization. But it still
MA> shall work if a corresponding defgroup doesn't exist.
Yes, exactly.
MA> I'm still sorting out. Will try to puzzle an example in order to see how
MA> it goes. (And as usual, much to less time to spend)
OK, let me know. We can write some tests against the matcher when you're
ready to try it practically and to establish the API. Thanks for looking
at this, I am excited about it.
Ted
next prev parent reply other threads:[~2017-02-14 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7856.1385996719.10748.bug-gnu-emacs@gnu.org>
[not found] ` <86wqjnwa9u.fsf@somewhere.org>
[not found] ` <jwvfvqb1bhb.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <871u1s38m3.fsf@flea.lifelogs.com>
[not found] ` <877f5j2i67.fsf@gnus.org>
[not found] ` <jwvziif80c1.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <87a8a8paru.fsf@lifelogs.com>
[not found] ` <jwv8tpsi3ah.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <87r33jnvn1.fsf@lifelogs.com>
[not found] ` <87h94fqjq7.fsf@gmx.de>
2017-02-02 3:43 ` bug#16026: Connection specific settings and proxies Lars Ingebrigtsen
2017-02-02 14:46 ` Ted Zlatanov
2017-02-03 15:37 ` Michael Albinus
[not found] ` <87mve3ffov.fsf__41803.1231420629$1486136780$gmane$org@gmx.de>
2017-02-06 15:22 ` Ted Zlatanov
2017-02-12 17:42 ` Michael Albinus
2017-02-13 15:54 ` Ted Zlatanov
2017-02-13 16:17 ` Michael Albinus
2017-02-14 15:01 ` Ted Zlatanov [this message]
2017-02-19 16:26 ` Michael Albinus
2017-02-20 16:01 ` bug#16026: " Lars Ingebrigtsen
2017-02-02 23:58 ` Daniel McClanahan
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=87mvdoke8p.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 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).