GNU bug report logs - #11601
gnus-tmp-group undocumented

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 11601 in the body.
You can then email your comments to 11601 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Dave Abrahams <dave <at> boostpro.com>
To: submit <at> debbugs.gnu.org (The Gnus Bugfixing Girls + Boys)
Subject: gnus-tmp-group undocumented
Date: Fri, 01 Jun 2012 13:38:59 -0400

I presume all of the gnus-tmp- stuff should be documented, or this one
should be changed to use some other mechanism.

,----[ (info "(gnus)Group Timestamp") ]
| File: gnus,  Node: Group Timestamp,  Next: File Commands,  Prev: Group Information,  Up: Misc Group Stuff
| 
| 2.18.3 Group Timestamp
| ----------------------
| 
| It can be convenient to let Gnus keep track of when you last read a
| group.  To set the ball rolling, you should add
| `gnus-group-set-timestamp' to `gnus-select-group-hook':
| 
|      (add-hook 'gnus-select-group-hook 'gnus-group-set-timestamp)
| 
|    After doing this, each time you enter a group, it'll be recorded.
| 
|    This information can be displayed in various ways--the easiest is to
| use the `%d' spec in the group line format:
| 
|      (setq gnus-group-line-format
|            "%M\%S\%p\%P\%5y: %(%-40,40g%) %d\n")
| 
|    This will result in lines looking like:
| 
|      *        0: mail.ding                                19961002T012943
|               0: custom                                   19961002T012713
| 
|    As you can see, the date is displayed in compact ISO 8601 format.
| This may be a bit too much, so to just display the date, you could say
| something like:
| 
|      (setq gnus-group-line-format
|            "%M\%S\%p\%P\%5y: %(%-40,40g%) %6,6~(cut 2)d\n")
| 
|    If you would like greater control of the time format, you can use a
| user-defined format spec.  Something like the following should do the
| trick:
| 
|      (setq gnus-group-line-format
|            "%M\%S\%p\%P\%5y: %(%-40,40g%) %ud\n")
|      (defun gnus-user-format-function-d (headers)
|        (let ((time (gnus-group-timestamp gnus-tmp-group)))
|          (if time
|              (format-time-string "%b %d  %H:%M" time)
|            "")))
| 
`----




Ma Gnus v0.6
GNU Emacs 24.0.94.1 (x86_64-apple-darwin11.4.0, Carbon Version 1.6.0 AppKit 1138.47)
 of 2012-05-24 on pluto.luannocracy.com
200 news.gmane.org InterNetNews NNRP server INN 2.5.1 ready (posting ok)
101 Capability list:
VERSION 2
IMPLEMENTATION INN 2.5.1
AUTHINFO USER
HDR
LIST ACTIVE ACTIVE.TIMES DISTRIB.PATS HEADERS NEWSGROUPS OVERVIEW.FMT
OVER
POST
READER
STARTTLS
.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com

Message #8 received at 11601 <at> debbugs.gnu.org (full text, mbox):

From: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
To: Dave Abrahams <dave <at> boostpro.com>
Cc: 11601 <at> debbugs.gnu.org
Subject: Re: bug#11601: gnus-tmp-group undocumented
Date: Mon, 11 Jun 2012 23:14:18 +0200

Dave Abrahams <dave <at> boostpro.com> writes:

> I presume all of the gnus-tmp- stuff should be documented, or this one
> should be changed to use some other mechanism.

I've now added the following to that section in the manual:

---
To see what variables are dynamically bound (like
@code{gnus-tmp-group}), you have to look at the source code.  The
variable names aren't guaranteed to be stable over Gnus versions,
either.


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

Message #15 received at 11601 <at> debbugs.gnu.org (full text, mbox):

From: Dave Abrahams <dave <at> boostpro.com>
To: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
Cc: 11601 <at> debbugs.gnu.org
Subject: Re: bug#11601: gnus-tmp-group undocumented
Date: Tue, 12 Jun 2012 10:56:32 -0400

on Mon Jun 11 2012, Lars Magne Ingebrigtsen <larsi-AT-gnus.org> wrote:

> Dave Abrahams <dave <at> boostpro.com> writes:
>
>> I presume all of the gnus-tmp- stuff should be documented, or this one
>> should be changed to use some other mechanism.
>
> I've now added the following to that section in the manual:
>
> ---
> To see what variables are dynamically bound (like
> @code{gnus-tmp-group}), you have to look at the source code.  The
> variable names aren't guaranteed to be stable over Gnus versions,
> either.

You're actually recommending a customization in the manual that relies
on implementation details?  In fact... is there any way to write a
useful gnus-user-format-function-* that doesn't rely on implementation
details?  This just doesn't seem right.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com

Message #18 received at 11601 <at> debbugs.gnu.org (full text, mbox):

From: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
To: Dave Abrahams <dave <at> boostpro.com>
Cc: 11601 <at> debbugs.gnu.org
Subject: Re: bug#11601: gnus-tmp-group undocumented
Date: Wed, 20 Jun 2012 19:12:01 +0200

Dave Abrahams <dave <at> boostpro.com> writes:

> You're actually recommending a customization in the manual that relies
> on implementation details?

Yes.

> In fact... is there any way to write a useful
> gnus-user-format-function-* that doesn't rely on implementation
> details?

Nope.

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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.