From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: nntp-record-commands is named badly; nnbackend-debug is needed
Date: Tue, 31 May 2011 20:53:18 +0200 [thread overview]
Message-ID: <m3hb8aem75.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87ipsrp5ft.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> I am trying to avoid the annoyance of having a *-debug variable for each
> backend. My debug macro IMHO is an improvement over the current
> approach of "do whatever debugging, however you want" and is analogous
> to how `gnus-message' improves messaging for Gnus.
There's also some value to keeping things simple. The backend debugging
stuff isn't as pervasive as the `gnus-message' stuff, I think.
And the `gnus-message' thing is meant to be tweaked by the user, while
the debug thing isn't...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-05-31 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 10:33 Ted Zlatanov
2011-05-18 21:01 ` Ted Zlatanov
2011-05-30 18:31 ` Lars Magne Ingebrigtsen
2011-05-31 9:47 ` Ted Zlatanov
2011-05-31 18:53 ` Lars Magne Ingebrigtsen [this message]
2011-05-31 19:22 ` Ted Zlatanov
2011-05-31 19:27 ` Lars Magne Ingebrigtsen
2011-05-31 19:41 ` Ted Zlatanov
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=m3hb8aem75.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).