Re: *nntp-log* differences between M-g and g

[Simon Josefsson <jas@extundo.com>]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

>>>>>> In <m3vf9ex17z.fsf@water.tss.usg.edu> Mark Plaksin wrote:
>
>> What's the difference between g in the Group buffer and M-g?  I know that g
>> will check all groups at the current level and M-g only checks the current
>> group, but if I set nntp-record-commands to t *nntp-log* shows different
>> commands depending on which keys I hit:
>
>> M-g:
>> 20050130T123715.889 news.gmane.org GROUP gmane.emacs.sources
>
>> g:
>> 20050130T123735.896 news.gmane.org GROUP gmane.emacs.sources
>> 20050130T123736.181 news.gmane.org LIST ACTIVE gmane.emacs.sources
>> 20050130T123736.317 news.gmane.org GROUP gmane.emacs.sources
>
> It is natural if the `nntp-marks-is-evil' variable is nil (which
> is the default).  This feature is described briefly in the
> GNUS-NEWS file as follows:
>
> --8<---------------cut here---------------start------------->8---
> ** The nntp back end store article marks in `~/News/marks'.
>
> The directory can be changed using the (customizable) variable
> `nntp-marks-directory', and marks can be disabled using the (back
> end) variable `nntp-marks-is-evil'.  The advantage of this is that
> you can copy `~/News/marks' (using rsync, scp or whatever) to another
> Gnus installation, and it will realize what articles you have read
> and marked.  The data in `~/News/marks' has priority over the same
> data in `~/.newsrc.eld'.
> --8<---------------cut here---------------end--------------->8---

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?

My NNTP juju is weak though.