From: Scott A Crosby <scrosby@cs.rice.edu>
Subject: Re: Bug in v5.10.6 under xemacs21 not generating the *Group*
Date: Wed, 25 Aug 2004 22:47:00 -0500 [thread overview]
Message-ID: <oyd7jrmftmz.fsf@bert.cs.rice.edu> (raw)
In-Reply-To: <b9yllg2hegt.fsf@jpl.org>
On Thu, 26 Aug 2004 10:31:46 +0900, Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>>>>> In <oyd1xhu2931.fsf@bert.cs.rice.edu>
>>>>>> Scott A Crosby <scrosby@cs.rice.edu> wrote:
>
>> Signaling: (wrong-type-argument sequencep nntp)
> [...]
>> eval((progn (insert (gnus-xmas-format "%s%s %s %s/%s: " ... ...
>> gnus-group-insert-group-line("nntp+news.rice.edu:rice.majors.cs"...
>
> [...]
>
>> This configuration is known-good for v5.8.8 which is what I used
>> until last night. I'm not subscribed, so please CC me on any replies.
>
> I guess there's something wrong in the `gnus-group-line-format'
> variable. What's the value you are using? Let us know the
> value for the `gnus-group-line-format-spec' variable as well if
> you don't use gnus-compile (which means the value is not
> compiled).
(setq gnus-group-line-format
"%M%S %P %6y/%-6t: %(%-40,40G%) %10n:%-10s\n")
I suspect its the %n or $s format character. I do not use
'gnus-compile. I will when this gets solved. I attach the value of
'gnus-group-line-format-spec at the end.
I've switched to the default 'gnus-group-line-format configuration
value ("%M%S%p%P%5y:%B%(%g%)%l %O\n") and the problem has disappeared.
> Otherwise, you may be able to solve it by evaluating the
> following Lisp form:
>
> (gnus-update-format-specifications t 'group)
I tried running this, it didn't help.
Thanks for the help.
Scott
***********************
`gnus-group-line-format-spec' is a variable declared in Lisp.
-- loaded from "gnus-spec"
Value: (progn (insert (gnus-xmas-format "%s%s %s %s/%s: " (char-to-string gnus-tmp-marked-mark) (char-to-string gnus-tmp-subscribed) gnus-group-indentation (let ((need (- 6 (gnus-correct-length gnus-tmp-number-of-unread)))) (if (> need 0) (concat (make-string need ?\ ) gnus-tmp-number-of-unread nil) gnus-tmp-number-of-unread)) (let* ((val (eval (int-to-string gnus-tmp-number-total))) (need (- 6 (gnus-correct-length val)))) (if (> need 0) (concat nil val (make-string need ?\ )) val)))) (gnus-put-text-property (point) (progn (insert (let* ((val (eval (if (> (gnus-correct-length gnus-tmp-qualified-group) 40) (gnus-correct-substring gnus-tmp-qualified-group 0 40) gnus-tmp-qualified-group))) (need (- 40 (gnus-correct-length val)))) (if (> need 0) (concat nil val (make-string need ?\ )) val))) (point)) gnus-mouse-face-prop gnus-mouse-face) (insert (gnus-xmas-format " %s:%s\n" (let ((need (- 10 (gnus-correct-length gnus-tmp-news-method)))) (if (> need 0) (concat (make-string need ?\ ) gnus-tmp-news-method nil) gnus-tmp-news-method)) (let ((need (- 10 (gnus-correct-length gnus-tmp-news-server)))) (if (> need 0) (concat nil gnus-tmp-news-server (make-string need ?\ )) gnus-tmp-news-server)))))
Documentation:
not documented as a variable.
**********************
next prev parent reply other threads:[~2004-08-26 3:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 21:37 Bug in v5.10.6 under xemacs21 not generating the *Group* buffer Scott A Crosby
[not found] ` <b9yllg2hegt.fsf@jpl.org>
2004-08-26 3:47 ` Scott A Crosby [this message]
2004-08-26 6:37 ` Bug in v5.10.6 under xemacs21 not generating the *Group* Katsumi Yamaoka
2004-08-26 6:49 ` Katsumi Yamaoka
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=oyd7jrmftmz.fsf@bert.cs.rice.edu \
--to=scrosby@cs.rice.edu \
/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).