From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org, Mark Plaksin <happy@mcplaksin.org>
Subject: Re: *nntp-log* differences between M-g and g
Date: Mon, 31 Jan 2005 09:04:29 +0900 [thread overview]
Message-ID: <b9yd5vmmpki.fsf@jpl.org> (raw)
In-Reply-To: <ilu1xc2xyr9.fsf@latte.josefsson.org>
>>>>> In <ilu1xc2xyr9.fsf@latte.josefsson.org> Simon Josefsson wrote:
> Why exactly does g have to issue two GROUP commands for the same
> group?
> And should 'g' really need to mess with the marks, except for
> extending the active range? Doesn't GROUP give Gnus enough
> information to do that?
That's a good point. It is just an item to which the nntp marks
should be improved.
next prev parent reply other threads:[~2005-01-31 0:04 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 [this message]
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
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=b9yd5vmmpki.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=happy@mcplaksin.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).