Re: nntp-record-commands is named badly; nnbackend-debug is needed

[Ted Zlatanov <tzz@lifelogs.com>]

On Wed, 18 May 2011 05:33:06 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> `nntp-record-commands' should be called "nntp-debug" or "nntp-verbose"
TZ> similar to the other backends.

TZ> In fact all the backends should have a nnbackend-debug nnvoo variable
TZ> and respect it uniformly.  Right now that's done per backend which leads
TZ> to the situation above.  But it should also work for mail-sources, how
TZ> would that work?

TZ> Let me know if this makes sense and what I can do to implement it.

How about a `gnus-network-debug' variable that is a list of '(imap nntp)
for instance?  Here's a working macro.

#+begin_src lisp
(defvar gnus-network-debug '(nntp))

(defmacro nnoo-debug (token text &rest arguments)
  `(when (memq ',token gnus-network-debug)
     (with-current-buffer (get-buffer-create ,(format "*%s-debug*" token))
       (insert (format ,text ,@arguments)))))

(defmacro nntp-debug (text &rest arguments)
  `(nnoo-debug nntp ,text ,@arguments))

(defmacro nnimap-debug (text &rest arguments)
  `(nnoo-debug nnimap ,text ,@arguments))

(nntp-debug "hello\n")

#+end_src

I think that's much better than the current "hunt for *-debug variables
all over the place" setup.

Ted