From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nntp-record-commands is named badly; nnbackend-debug is needed
Date: Tue, 31 May 2011 14:22:44 -0500 [thread overview]
Message-ID: <87oc2iad4r.fsf@lifelogs.com> (raw)
In-Reply-To: <m3hb8aem75.fsf@quimbies.gnus.org>
On Tue, 31 May 2011 20:53:18 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> 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.
LMI> There's also some value to keeping things simple. The backend debugging
LMI> stuff isn't as pervasive as the `gnus-message' stuff, I think.
True, but it's badly named and scattered all over the place as it is.
Do you think the situation will get better over time? I doubt it.
LMI> And the `gnus-message' thing is meant to be tweaked by the user, while
LMI> the debug thing isn't...
Every time someone has a bug report, we say "turn xyz-debug on, then..."
so obviously it's important to make it as easy as possible. It will
help the users and the developers to have just one variable to customize
instead of 5 or so.
Ted
next prev parent reply other threads:[~2011-05-31 19:22 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
2011-05-31 19:22 ` Ted Zlatanov [this message]
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=87oc2iad4r.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).