From: Ralf Angeli <dev.null@iwi.uni-sb.de>
Subject: Re: *nntp-log* differences between M-g and g
Date: Wed, 02 Feb 2005 09:00:28 +0100 [thread overview]
Message-ID: <ctq19v$e2k$1@sea.gmane.org> (raw)
In-Reply-To: <b9ymzup69x0.fsf@jpl.org>
* Katsumi Yamaoka (2005-01-31) writes:
> The reason two GROUP commands issued when typing `g' is that
> nntp.el provides the `nntp-request-update-info' function which
> returns non-nil. Because of this,
> gnus-get-unread-articles-in-group calls nntp-request-group which
> issues the GROUP command by way of gnus-activate-group. I think
> to issue those commands is of no use to manage the nntp marks.
> The patch below avoids those futilities. Could anyone test it?
> I hope the people who are using the nntp marks in daily life
> test it.
I've been using this since you posted the patch and haven't
encountered any problems.
Before I patched the sources I did a `cvs up'. After installing Gnus
there were some groups which showed up with unread articles although
they were marked as read before. This problem went away after using
`c' on those groups. As I updated the sources before applying the
patch, I don't know if this oddity is a result of your patch or
another change.
--
Ralf
next prev parent reply other threads:[~2005-02-02 8:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 17:42 Mark Plaksin
2005-01-30 23:28 ` Katsumi Yamaoka
2005-01-30 23:50 ` Simon Josefsson
2005-01-31 0:04 ` Katsumi Yamaoka
2005-01-31 12:49 ` Katsumi Yamaoka
2005-01-31 22:09 ` Mark Plaksin
2005-02-01 11:30 ` Katsumi Yamaoka
2005-02-02 8:00 ` Ralf Angeli [this message]
2005-02-02 9:42 ` Simon Josefsson
2005-02-02 11:38 ` Katsumi Yamaoka
2005-02-03 0:39 ` Katsumi Yamaoka
2005-02-03 9:04 ` Ralf Angeli
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='ctq19v$e2k$1@sea.gmane.org' \
--to=dev.null@iwi.uni-sb.de \
--cc=angeli@iwi.uni-sb.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).