From: Ulf Stegemann <ulf-killthis@zeitform.de>
Subject: Problem with gnus-group-mark-group
Date: Tue, 08 Mar 2005 17:42:04 +0100 [thread overview]
Message-ID: <zf.upnu0nm3x9f.fsf@zeitform.de> (raw)
XEmacs 21.4 (patch 17) "Jumbo Shrimp" [Lucid] (i686-pc-linux, Mule)
No Gnus v0.3
I recently switched form Gnus 5.10.6 to No Gnus 0.3 and encountered a problem
when hitting M-g in a summary buffer (gnus-summary-rescan-group) or the
group buffer (gnus-group-get-new-news-this-group).
Each M-g produces an additional group entry in the group buffer leaving the
existing one(s) borked ("no group on current line" when trying to enter).
I was able to identify gnus-group-mark-group as responsible for the faulty
behavior. The function changed significantly since 5.10.6 and replacing No
Gnus' gnus-group-mark-group with the v5.10.6 version apparently fixed the
problem.
Unfortunately, my lack of time (and sufficient lisp knowledge, probably)
let's me hesitate to further investigate this issue. Maybe there's someone
out there who knows what the reason for the described behavior is?
Ulf
next reply other threads:[~2005-03-08 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 16:42 Ulf Stegemann [this message]
2005-03-11 19:22 ` Reiner Steib
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=zf.upnu0nm3x9f.fsf@zeitform.de \
--to=ulf-killthis@zeitform.de \
/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).