From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: [BUG]: nndiary backend
Date: Thu, 18 Mar 2004 08:38:52 +0900 [thread overview]
Message-ID: <b9yish3ujqr.fsf@jpl.org> (raw)
In-Reply-To: <plop874qsni05p.fsf@gnu-rox.org>
>>>>> In <plop874qsni05p.fsf@gnu-rox.org>
>>>>> Xavier Maillard <zedek@gnu-rox.org> wrote:
> Yo,
> I tried to use th nndiary backend to get reminded of meeting I could
> receive by mail.
> It sorta worked for the first entered nndiary but I can't enter my
> nndiary group anymore.
> Here is the backtrace:
> ,----
>| Debugger entered--Lisp error: (void-variable gnus-tmp-group)
>| (gnus-group-timestamp gnus-tmp-group)
>| (let ((time ...)) (if time (format-time-string "%a %d %b %H:%M" time)))
>| gnus-user-format-function-d([0 "" "" "05 Apr 2001 23:33:09 +0400" "" "" 0 0 "" nil])
[...]
>| gnus-summary-insert-line([0 "" "" "05 Apr 2001 23:33:09 +0400" "" "" 0 0 "" nil] 0 nil t 128 t nil "" nil 1)
>| gnus-update-summary-mark-positions()
>| gnus-summary-read-group-1("nndiary:diary" nil t nil nil nil)
>| gnus-summary-read-group("nndiary:diary" nil t nil nil nil nil)
>| gnus-group-read-group(nil t)
>| gnus-group-select-group(nil)
>| gnus-topic-select-group(nil)
>| call-interactively(gnus-topic-select-group)
> `----
You seem to have defined the gnus-user-format-function-d
function for the group buffer. Probably it comes from the
``Group Timestamp'' section in the Gnus manual and it may be
unable to be used in the summary buffer. There is a comment in
the gnus-diary.el file as follows:
;; Usage:
;; =====
;; 0/ Don't use any `gnus-user-format-function-[d|D]'. Gnus-Diary provides
;; both of these (sorry if you used them before).
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2004-03-17 23:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 22:22 Xavier Maillard
2004-03-17 23:38 ` Katsumi Yamaoka [this message]
2004-03-18 7:46 ` Xavier Maillard
2004-03-24 8:18 ` Kai Grossjohann
2004-05-16 14:31 ` 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=b9yish3ujqr.fsf@jpl.org \
--to=yamaoka@jpl.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).