Go to the next summary line of an unread article (gnus-summary-next-unread-subject).

Go to the previous summary line of an unread article (gnus-summary-prev-unread-subject).

Ask for an article number or Message-ID, and then go to that article (gnus-summary-goto-article).

Ask for an article number and then go to the summary line of that article without displaying the article (gnus-summary-goto-subject).

If you issue one of the movement commands (like n) and there are no more unread articles after the current one, Gnus will offer to go to the next group. If this variable is t and the next group is empty, Gnus will exit summary mode and return to the group buffer. If this variable is neither t nor nil, Gnus will select the next group, no matter whether it has any unread articles or not. As a special case, if this variable is quietly, Gnus will select the next group without asking for confirmation. If this variable is almost-quietly, the same will happen only if you are located on the last article in the group. Finally, if this variable is slightly-quietly, the Z n command will go to the next group without confirmation. Also see Group Levels.

If non-nil, all the movement commands will try to go to the next article with the same subject as the current. (Same here might mean roughly equal. See gnus-summary-gather-subject-limit for details (see Customizing Threading).) If there are no more articles with the same subject, go to the first unread article.

This variable is not particularly useful if you use a threaded display.

If non-nil, all the ``unread'' movement commands will not proceed to the next (or previous) article if the current article is unread. Instead, they will choose the current article.

If non-nil, Gnus will keep the point in the summary buffer centered at all times. This makes things quite tidy, but if you have a slow network connection, or simply do not like this un-Emacsism, you can set this variable to nil to get the normal Emacs scrolling action. This will also inhibit horizontal re-centering of the summary buffer, which might make it more inconvenient to read extremely long threads.