From: "Darren/Torin/Who Ever..." <torin@daft.com>
Subject: user summary line format not being called with headers
Date: 02 Jun 1997 03:20:14 -0700 [thread overview]
Message-ID: <87n2p92tn1.fsf@perv.daft.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
My gnus-user-format-function in gnus-summary-line-format seems to be
called with null headers.
Note the following line that says "Error" from the " *Message-Log*"
buffer:
>No more unread articles (Type n for nnmh:lists.soft.gnus [5])
>
>Retrieving newsgroup: nnmh:lists.soft.gnus...
>Error in summary date () line format: (error Specified time is not representable)
>Fetching headers for nnmh:lists.soft.gnus...
>Fetching headers for nnmh:lists.soft.gnus...done
>Scoring...
>Scoring...done
>Sorting threads...
>Sorting threads...done
>Generating summary...
>Generating summary...done
BTW, the entire header looks like: "[0 0 0 ]" when I print it out.
So, it appears to be an array from somewhere.
This comes from the following user-format:
>"%U%R %6,6uD %5,5N %I%(%[%4L: %-20,20uB%]%) %s\n"
set from gnus-summary-format-hook. And the gnus-user-format-function-D
is:
>(defun gnus-user-format-function-D (header)
> "Return a prettified date based on age (uses relevant-date)"
> (let (date-header)
> (condition-case err
> (progn
> (setq date-header (mail-header-date header))
> (relevant-date (gnus-encode-date date-header)))
> (error (message "Error in summary date (%s) line format: %s" date-header err) ""))))
and finally, relevant-date is:
>(defun relevant-date (date) "\
>Format DATE based on age from current time
>where date is emacs-time cons (hiword loword) and time is
>Within the day - hh:mm
>Within the week - ddd
>Within the last six months - MMM DD
>Older than six months - YY MMM"
> (let* ((time (gnus-time-minus (current-time) date))
> (seconds (+ (* (car time) 65536) (cadr time))))
> (cond ((> seconds 15768000) ; half a year
> (format-time-string "%y %b" date))
> ((> seconds 604800) ; one week
> (format-time-string "%b %e" date))
> ((> seconds 86400) ; one day
> (format-time-string "%a" date))
> (t
> (format-time-string "%k:%M" date)))))
and finally the version of gnus:
>Gnus v5.4.55; nntp 5.0; nnmh 1.0
Any ideas? If no answers are forthcoming, I'll probably slog through
the code. I just want to see if I'm doing something obvious wrong.
(Like header *will* be passed as a null once, get used to it.)
- --
<torin@daft.com> <http://www.daft.com/~torin> <torin@debian.org> <torin@io.com>
Darren Stalder/2608 Second Ave, @282/Seattle, WA 98121-1212/USA/+1-800-921-4996
@ Do you have your clothes on? I probably don't. Take yours off. Feel better. @
@ Sysadmin, webweaver, postmaster for hire. C/Perl/CGI programmer and tutor. @
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQCVAwUBM5Keao4wrq++1Ls5AQHVXAP/W6/AQFqYjKsJZr+i3uEgzje61fpEMlq3
8DIr9JSxKLUHsRSzRhIjIIuePQXZIORTfdcaLGDnnLGNd2ceLrhzYFUL5rC5OoAS
+kFzzbFQyGXGaG6b4+7mcfO9WuksmfdzmxOmVMtc1xqj+4gCiVZHsgloEEo1wNtA
FVcKAvVOxlk=
=d+MO
-----END PGP SIGNATURE-----
next reply other threads:[~1997-06-02 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-06-02 10:20 Darren/Torin/Who Ever... [this message]
1997-06-06 3:24 ` Lars Magne Ingebrigtsen
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=87n2p92tn1.fsf@perv.daft.com \
--to=torin@daft.com \
/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).