>>>>> In Katsumi Yamaoka wrote: >>>>>> In 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. 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.