3 @include gnus-overrides.texi
11 @documentencoding UTF-8
14 Copyright @copyright{} 1995-2012 Free Software Foundation, Inc.
17 Permission is granted to copy, distribute and/or modify this document
18 under the terms of the GNU Free Documentation License, Version 1.3 or
19 any later version published by the Free Software Foundation; with no
20 Invariant Sections, with the Front-Cover texts being ``A GNU Manual'',
21 and with the Back-Cover Texts as in (a) below. A copy of the license
22 is included in the section entitled ``GNU Free Documentation License''.
24 (a) The FSF's Back-Cover Text is: ``You have the freedom to copy and
25 modify this GNU manual. Buying copies from the FSF supports it in
26 developing GNU and promoting software freedom.''
32 \documentclass[twoside,a4paper,openright,11pt]{book}
33 \usepackage[latin1]{inputenc}
34 \usepackage{pagestyle}
37 \input{gnusconfig.tex}
39 \ifx\pdfoutput\undefined
41 \usepackage[pdftex,bookmarks,colorlinks=true]{hyperref}
49 % Adjust ../Makefile.in if you change the following line:
50 \newcommand{\gnusversionname}{Ma Gnus v0.2}
51 \newcommand{\gnuschaptername}{}
52 \newcommand{\gnussectionname}{}
54 \newcommand{\gnusbackslash}{/}
56 \newcommand{\gnusref}[1]{``#1'' on page \pageref{#1}}
57 \ifx\pdfoutput\undefined
58 \newcommand{\gnusuref}[1]{\gnustt{#1}}
60 \newcommand{\gnusuref}[1]{\href{#1}{\gnustt{#1}}}
62 \newcommand{\gnusxref}[1]{See ``#1'' on page \pageref{#1}}
63 \newcommand{\gnuspxref}[1]{see ``#1'' on page \pageref{#1}}
65 \newcommand{\gnuskindex}[1]{\index{#1}}
66 \newcommand{\gnusindex}[1]{\index{#1}}
68 \newcommand{\gnustt}[1]{{\gnusselectttfont{}#1}}
69 \newcommand{\gnuscode}[1]{\gnustt{#1}}
70 \newcommand{\gnusasis}[1]{\gnustt{#1}}
71 \newcommand{\gnusurl}[1]{\gnustt{#1}}
72 \newcommand{\gnuscommand}[1]{\gnustt{#1}}
73 \newcommand{\gnusenv}[1]{\gnustt{#1}}
74 \newcommand{\gnussamp}[1]{``{\fontencoding{OT1}\gnusselectttfont{}#1}''}
75 \newcommand{\gnuslisp}[1]{\gnustt{#1}}
76 \newcommand{\gnuskbd}[1]{`\gnustt{#1}'}
77 \newcommand{\gnuskey}[1]{`\gnustt{#1}'}
78 \newcommand{\gnusfile}[1]{`\gnustt{#1}'}
79 \newcommand{\gnusdfn}[1]{\textit{#1}}
80 \newcommand{\gnusi}[1]{\textit{#1}}
81 \newcommand{\gnusr}[1]{\textrm{#1}}
82 \newcommand{\gnusstrong}[1]{\textbf{#1}}
83 \newcommand{\gnusemph}[1]{\textit{#1}}
84 \newcommand{\gnusvar}[1]{{\fontsize{10pt}{10}\selectfont\textsl{\textsf{#1}}}}
85 \newcommand{\gnussc}[1]{\textsc{#1}}
86 \newcommand{\gnustitle}[1]{{\huge\textbf{#1}}}
87 \newcommand{\gnusversion}[1]{{\small\textit{#1}}}
88 \newcommand{\gnusauthor}[1]{{\large\textbf{#1}}}
89 \newcommand{\gnusresult}[1]{\gnustt{=> #1}}
90 \newcommand{\gnusacronym}[1]{\textsc{#1}}
91 \newcommand{\gnusemail}[1]{\textit{#1}}
93 \newcommand{\gnusbullet}{{${\bullet}$}}
94 \newcommand{\gnusdollar}{\$}
95 \newcommand{\gnusampersand}{\&}
96 \newcommand{\gnuspercent}{\%}
97 \newcommand{\gnushash}{\#}
98 \newcommand{\gnushat}{\symbol{"5E}}
99 \newcommand{\gnusunderline}{\symbol{"5F}}
100 \newcommand{\gnusnot}{$\neg$}
101 \newcommand{\gnustilde}{\symbol{"7E}}
102 \newcommand{\gnusless}{{$<$}}
103 \newcommand{\gnusgreater}{{$>$}}
104 \newcommand{\gnusbraceleft}{{$>$}}
105 \newcommand{\gnusbraceright}{{$>$}}
107 \newcommand{\gnushead}{\raisebox{-1cm}{\epsfig{figure=ps/gnus-head,height=1cm}}}
108 \newcommand{\gnusinteresting}{
109 \marginpar[\mbox{}\hfill\gnushead]{\gnushead}
112 \newcommand{\gnuscleardoublepage}{\ifodd\count0\mbox{}\clearpage\thispagestyle{empty}\mbox{}\clearpage\else\clearpage\fi}
114 \newcommand{\gnuspagechapter}[1]{
118 \newdimen{\gnusdimen}
121 \newcommand{\gnuschapter}[2]{
123 \ifdim \gnusdimen = 0pt\setcounter{page}{1}\pagestyle{gnus}\pagenumbering{arabic} \gnusdimen 1pt\fi
125 \renewcommand{\gnussectionname}{}
126 \renewcommand{\gnuschaptername}{#2}
127 \thispagestyle{empty}
129 \begin{picture}(500,500)(0,0)
130 \put(480,350){\makebox(0,0)[tr]{#1}}
131 \put(40,300){\makebox(500,50)[bl]{{\Huge\bf{#2}}}}
136 \newcommand{\gnusfigure}[3]{
138 \mbox{}\ifodd\count0\hspace*{-0.8cm}\else\hspace*{-3cm}\fi\begin{picture}(440,#2)
145 \newcommand{\gnusicon}[1]{
146 \marginpar[\mbox{}\hfill\raisebox{-1.5cm}{\epsfig{figure=ps/#1-up,height=1.5cm}}]{\raisebox{-1cm}{\epsfig{figure=ps/#1-up,height=1cm}}}
149 \newcommand{\gnuspicon}[1]{
150 \margindex{\epsfig{figure=#1,width=2cm}}
153 \newcommand{\gnusxface}[2]{
154 \margindex{\epsfig{figure=#1,width=1cm}\epsfig{figure=#2,width=1cm}}
157 \newcommand{\gnussmiley}[2]{
158 \margindex{\makebox[2cm]{\hfill\epsfig{figure=#1,width=0.5cm}\hfill\epsfig{figure=#2,width=0.5cm}\hfill}}
161 \newcommand{\gnusitemx}[1]{\mbox{}\vspace*{-\itemsep}\vspace*{-\parsep}\item#1}
163 \newcommand{\gnussection}[1]{
164 \renewcommand{\gnussectionname}{#1}
168 \newenvironment{codelist}%
173 \newenvironment{asislist}%
178 \newenvironment{kbdlist}%
184 \newenvironment{dfnlist}%
189 \newenvironment{stronglist}%
194 \newenvironment{samplist}%
199 \newenvironment{varlist}%
204 \newenvironment{emphlist}%
209 \newlength\gnusheadtextwidth
210 \setlength{\gnusheadtextwidth}{\headtextwidth}
211 \addtolength{\gnusheadtextwidth}{1cm}
213 \newpagestyle{gnuspreamble}%
218 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\mbox{}}\textbf{\hfill\roman{page}}}
222 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\roman{page}\hfill\mbox{}}}
231 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
233 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
238 \newpagestyle{gnusindex}%
243 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\gnuschaptername\hfill\arabic{page}}}}
247 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}
255 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
257 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
267 \makebox[12cm]{\hspace*{3.1cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{chapter}.\arabic{section}} \textbf{\gnussectionname\hfill\arabic{page}}}}}
271 \makebox[12cm]{\hspace*{-2.95cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}}
279 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
281 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
286 \pagenumbering{roman}
287 \pagestyle{gnuspreamble}
298 %\addtolength{\oddsidemargin}{-5cm}
299 %\addtolength{\evensidemargin}{-5cm}
301 \addtolength{\textheight}{2cm}
303 \gnustitle{\gnustitlename}\hfill\gnusversion{\gnusversionname}\\
306 \hspace*{0cm}\epsfig{figure=ps/gnus-big-logo,height=15cm}
309 \gnusauthor{by Lars Magne Ingebrigtsen}
316 \thispagestyle{empty}
324 @dircategory Emacs network features
326 * Gnus: (gnus). The newsreader Gnus.
335 @title Gnus Manual (DEVELOPMENT VERSION)
337 @ifclear WEBHACKDEVEL
341 @author by Lars Magne Ingebrigtsen
343 @vskip 0pt plus 1filll
351 @top The Gnus Newsreader
355 You can read news (and mail) from within Emacs by using Gnus. The news
356 can be gotten by any nefarious means you can think of---@acronym{NNTP}, local
357 spool or your mbox file. All at the same time, if you want to push your
360 @c Adjust ../Makefile.in if you change the following line:
361 This manual corresponds to Ma Gnus v0.2
376 Gnus is the advanced, self-documenting, customizable, extensible
377 unreal-time newsreader for GNU Emacs.
379 Oops. That sounds oddly familiar, so let's start over again to avoid
380 being accused of plagiarism:
382 Gnus is a message-reading laboratory. It will let you look at just
383 about anything as if it were a newsgroup. You can read mail with it,
384 you can browse directories with it, you can @code{ftp} with it---you
385 can even read news with it!
387 Gnus tries to empower people who read news the same way Emacs empowers
388 people who edit text. Gnus sets no limits to what the user should be
389 allowed to do. Users are encouraged to extend Gnus to make it behave
390 like they want it to behave. A program should not control people;
391 people should be empowered to do what they want by using (or abusing)
394 @c Adjust ../Makefile.in if you change the following line:
395 This manual corresponds to Ma Gnus v0.2
397 @heading Other related manuals
399 @item Message manual: Composing messages
400 @item Emacs-MIME: Composing messages; @acronym{MIME}-specific parts.
401 @item Sieve: Managing Sieve scripts in Emacs.
402 @item PGG: @acronym{PGP/MIME} with Gnus.
403 @item SASL: @acronym{SASL} authentication in Emacs.
409 * Starting Up:: Finding news can be a pain.
410 * Group Buffer:: Selecting, subscribing and killing groups.
411 * Summary Buffer:: Reading, saving and posting articles.
412 * Article Buffer:: Displaying and handling articles.
413 * Composing Messages:: Information on sending mail and news.
414 * Select Methods:: Gnus reads all messages from various select methods.
415 * Scoring:: Assigning values to articles.
416 * Searching:: Mail and News search engines.
417 * Various:: General purpose settings.
418 * The End:: Farewell and goodbye.
419 * Appendices:: Terminology, Emacs intro, @acronym{FAQ}, History, Internals.
420 * GNU Free Documentation License:: The license for this documentation.
421 * Index:: Variable, function and concept index.
422 * Key Index:: Key Index.
424 Other related manuals
426 * Message:(message). Composing messages.
427 * Emacs-MIME:(emacs-mime). Composing messages; @acronym{MIME}-specific parts.
428 * Sieve:(sieve). Managing Sieve scripts in Emacs.
429 * PGG:(pgg). @acronym{PGP/MIME} with Gnus.
430 * SASL:(sasl). @acronym{SASL} authentication in Emacs.
433 --- The Detailed Node Listing ---
437 * Finding the News:: Choosing a method for getting news.
438 * The Server is Down:: How can I read my mail then?
439 * Slave Gnusae:: You can have more than one Gnus active at a time.
440 * Fetching a Group:: Starting Gnus just to read a group.
441 * New Groups:: What is Gnus supposed to do with new groups?
442 * Changing Servers:: You may want to move from one server to another.
443 * Startup Files:: Those pesky startup files---@file{.newsrc}.
444 * Auto Save:: Recovering from a crash.
445 * The Active File:: Reading the active file over a slow line Takes Time.
446 * Startup Variables:: Other variables you might change.
450 * Checking New Groups:: Determining what groups are new.
451 * Subscription Methods:: What Gnus should do with new groups.
452 * Filtering New Groups:: Making Gnus ignore certain new groups.
456 * Group Buffer Format:: Information listed and how you can change it.
457 * Group Maneuvering:: Commands for moving in the group buffer.
458 * Selecting a Group:: Actually reading news.
459 * Subscription Commands:: Unsubscribing, killing, subscribing.
460 * Group Data:: Changing the info for a group.
461 * Group Levels:: Levels? What are those, then?
462 * Group Score:: A mechanism for finding out what groups you like.
463 * Marking Groups:: You can mark groups for later processing.
464 * Foreign Groups:: Creating and editing groups.
465 * Group Parameters:: Each group may have different parameters set.
466 * Listing Groups:: Gnus can list various subsets of the groups.
467 * Sorting Groups:: Re-arrange the group order.
468 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
469 * Browse Foreign Server:: You can browse a server. See what it has to offer.
470 * Exiting Gnus:: Stop reading news and get some work done.
471 * Group Topics:: A folding group mode divided into topics.
472 * Non-ASCII Group Names:: Accessing groups of non-English names.
473 * Misc Group Stuff:: Other stuff that you can to do.
477 * Group Line Specification:: Deciding how the group buffer is to look.
478 * Group Mode Line Specification:: The group buffer mode line.
479 * Group Highlighting:: Having nice colors in the group buffer.
483 * Topic Commands:: Interactive E-Z commands.
484 * Topic Variables:: How to customize the topics the Lisp Way.
485 * Topic Sorting:: Sorting each topic individually.
486 * Topic Topology:: A map of the world.
487 * Topic Parameters:: Parameters that apply to all groups in a topic.
491 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
492 * Group Information:: Information and help on groups and Gnus.
493 * Group Timestamp:: Making Gnus keep track of when you last read a group.
494 * File Commands:: Reading and writing the Gnus files.
495 * Sieve Commands:: Managing Sieve scripts.
499 * Summary Buffer Format:: Deciding how the summary buffer is to look.
500 * Summary Maneuvering:: Moving around the summary buffer.
501 * Choosing Articles:: Reading articles.
502 * Paging the Article:: Scrolling the current article.
503 * Reply Followup and Post:: Posting articles.
504 * Delayed Articles:: Send articles at a later time.
505 * Marking Articles:: Marking articles as read, expirable, etc.
506 * Limiting:: You can limit the summary buffer.
507 * Threading:: How threads are made.
508 * Sorting the Summary Buffer:: How articles and threads are sorted.
509 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
510 * Article Caching:: You may store articles in a cache.
511 * Persistent Articles:: Making articles expiry-resistant.
512 * Sticky Articles:: Article buffers that are not reused.
513 * Article Backlog:: Having already read articles hang around.
514 * Saving Articles:: Ways of customizing article saving.
515 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
516 * Article Treatment:: The article buffer can be mangled at will.
517 * MIME Commands:: Doing MIMEy things with the articles.
518 * Charsets:: Character set issues.
519 * Article Commands:: Doing various things with the article buffer.
520 * Summary Sorting:: Sorting the summary buffer in various ways.
521 * Finding the Parent:: No child support? Get the parent.
522 * Alternative Approaches:: Reading using non-default summaries.
523 * Tree Display:: A more visual display of threads.
524 * Mail Group Commands:: Some commands can only be used in mail groups.
525 * Various Summary Stuff:: What didn't fit anywhere else.
526 * Exiting the Summary Buffer:: Returning to the Group buffer,
527 or reselecting the current group.
528 * Crosspost Handling:: How crossposted articles are dealt with.
529 * Duplicate Suppression:: An alternative when crosspost handling fails.
530 * Security:: Decrypt and Verify.
531 * Mailing List:: Mailing list minor mode.
533 Summary Buffer Format
535 * Summary Buffer Lines:: You can specify how summary lines should look.
536 * To From Newsgroups:: How to not display your own name.
537 * Summary Buffer Mode Line:: You can say how the mode line should look.
538 * Summary Highlighting:: Making the summary buffer all pretty and nice.
542 * Choosing Commands:: Commands for choosing articles.
543 * Choosing Variables:: Variables that influence these commands.
545 Reply, Followup and Post
547 * Summary Mail Commands:: Sending mail.
548 * Summary Post Commands:: Sending news.
549 * Summary Message Commands:: Other Message-related commands.
550 * Canceling and Superseding::
554 * Unread Articles:: Marks for unread articles.
555 * Read Articles:: Marks for read articles.
556 * Other Marks:: Marks that do not affect readedness.
557 * Setting Marks:: How to set and remove marks.
558 * Generic Marking Commands:: How to customize the marking.
559 * Setting Process Marks:: How to mark articles for later processing.
563 * Customizing Threading:: Variables you can change to affect the threading.
564 * Thread Commands:: Thread based commands in the summary buffer.
566 Customizing Threading
568 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
569 * Filling In Threads:: Making the threads displayed look fuller.
570 * More Threading:: Even more variables for fiddling with threads.
571 * Low-Level Threading:: You thought it was over@dots{} but you were wrong!
575 * Uuencoded Articles:: Uudecode articles.
576 * Shell Archives:: Unshar articles.
577 * PostScript Files:: Split PostScript.
578 * Other Files:: Plain save and binhex.
579 * Decoding Variables:: Variables for a happy decoding.
580 * Viewing Files:: You want to look at the result of the decoding?
584 * Rule Variables:: Variables that say how a file is to be viewed.
585 * Other Decode Variables:: Other decode variables.
586 * Uuencoding and Posting:: Variables for customizing uuencoding.
590 * Article Highlighting:: You want to make the article look like fruit salad.
591 * Article Fontisizing:: Making emphasized text look nice.
592 * Article Hiding:: You also want to make certain info go away.
593 * Article Washing:: Lots of way-neat functions to make life better.
594 * Article Header:: Doing various header transformations.
595 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
596 * Article Button Levels:: Controlling appearance of buttons.
597 * Article Date:: Grumble, UT!
598 * Article Display:: Display various stuff---X-Face, Picons, Smileys, Gravatars
599 * Article Signature:: What is a signature?
600 * Article Miscellanea:: Various other stuff.
602 Alternative Approaches
604 * Pick and Read:: First mark articles and then read them.
605 * Binary Groups:: Auto-decode all articles.
607 Various Summary Stuff
609 * Summary Group Information:: Information oriented commands.
610 * Searching for Articles:: Multiple article commands.
611 * Summary Generation Commands::
612 * Really Various Summary Commands:: Those pesky non-conformant commands.
616 * Hiding Headers:: Deciding what headers should be displayed.
617 * Using MIME:: Pushing articles through @acronym{MIME} before reading them.
618 * Customizing Articles:: Tailoring the look of the articles.
619 * Article Keymap:: Keystrokes available in the article buffer.
620 * Misc Article:: Other stuff.
624 * Mail:: Mailing and replying.
625 * Posting Server:: What server should you post and mail via?
626 * POP before SMTP:: You cannot send a mail unless you read a mail.
627 * Mail and Post:: Mailing and posting at the same time.
628 * Archived Messages:: Where Gnus stores the messages you've sent.
629 * Posting Styles:: An easier way to specify who you are.
630 * Drafts:: Postponing messages and rejected messages.
631 * Rejected Articles:: What happens if the server doesn't like your article?
632 * Signing and encrypting:: How to compose secure messages.
636 * Server Buffer:: Making and editing virtual servers.
637 * Getting News:: Reading USENET news with Gnus.
638 * Using IMAP:: Reading mail from @acronym{IMAP}.
639 * Getting Mail:: Reading your personal mail with Gnus.
640 * Browsing the Web:: Getting messages from a plethora of Web sources.
641 * Other Sources:: Reading directories, files.
642 * Combined Groups:: Combining groups into one group.
643 * Email Based Diary:: Using mails to manage diary events in Gnus.
644 * Gnus Unplugged:: Reading news and mail offline.
648 * Server Buffer Format:: You can customize the look of this buffer.
649 * Server Commands:: Commands to manipulate servers.
650 * Example Methods:: Examples server specifications.
651 * Creating a Virtual Server:: An example session.
652 * Server Variables:: Which variables to set.
653 * Servers and Methods:: You can use server names as select methods.
654 * Unavailable Servers:: Some servers you try to contact may be down.
658 * NNTP:: Reading news from an @acronym{NNTP} server.
659 * News Spool:: Reading news from the local spool.
663 * Direct Functions:: Connecting directly to the server.
664 * Indirect Functions:: Connecting indirectly to the server.
665 * Common Variables:: Understood by several connection functions.
666 * NNTP marks:: Storing marks for @acronym{NNTP} servers.
670 * Mail in a Newsreader:: Important introductory notes.
671 * Getting Started Reading Mail:: A simple cookbook example.
672 * Splitting Mail:: How to create mail groups.
673 * Mail Sources:: How to tell Gnus where to get mail from.
674 * Mail Back End Variables:: Variables for customizing mail handling.
675 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
676 * Group Mail Splitting:: Use group customize to drive mail splitting.
677 * Incorporating Old Mail:: What about the old mail you have?
678 * Expiring Mail:: Getting rid of unwanted mail.
679 * Washing Mail:: Removing cruft from the mail you get.
680 * Duplicates:: Dealing with duplicated mail.
681 * Not Reading Mail:: Using mail back ends for reading other files.
682 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
686 * Mail Source Specifiers:: How to specify what a mail source is.
687 * Mail Source Customization:: Some variables that influence things.
688 * Fetching Mail:: Using the mail source specifiers.
690 Choosing a Mail Back End
692 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
693 * Babyl:: Babyl was used by older versions of Rmail.
694 * Mail Spool:: Store your mail in a private spool?
695 * MH Spool:: An mhspool-like back end.
696 * Maildir:: Another one-file-per-message format.
697 * Mail Folders:: Having one file for each group.
698 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
703 * Web Searches:: Creating groups from articles that match a string.
704 * RSS:: Reading RDF site summary.
705 * Customizing W3:: Doing stuff to Emacs/W3 from Gnus.
709 * Directory Groups:: You can read a directory as if it was a newsgroup.
710 * Anything Groups:: Dired? Who needs dired?
711 * Document Groups:: Single files can be the basis of a group.
712 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
713 * The Empty Backend:: The backend that never has any news.
717 * Document Server Internals:: How to add your own document types.
721 * Virtual Groups:: Combining articles from many groups.
725 * The NNDiary Back End:: Basic setup and usage.
726 * The Gnus Diary Library:: Utility toolkit on top of nndiary.
727 * Sending or Not Sending:: A final note on sending diary messages.
731 * Diary Messages:: What makes a message valid for nndiary.
732 * Running NNDiary:: NNDiary has two modes of operation.
733 * Customizing NNDiary:: Bells and whistles.
735 The Gnus Diary Library
737 * Diary Summary Line Format:: A nicer summary buffer line format.
738 * Diary Articles Sorting:: A nicer way to sort messages.
739 * Diary Headers Generation:: Not doing it manually.
740 * Diary Group Parameters:: Not handling them manually.
744 * Agent Basics:: How it all is supposed to work.
745 * Agent Categories:: How to tell the Gnus Agent what to download.
746 * Agent Commands:: New commands for all the buffers.
747 * Agent Visuals:: Ways that the agent may effect your summary buffer.
748 * Agent as Cache:: The Agent is a big cache too.
749 * Agent Expiry:: How to make old articles go away.
750 * Agent Regeneration:: How to recover from lost connections and other accidents.
751 * Agent and flags:: How the Agent maintains flags.
752 * Agent and IMAP:: How to use the Agent with @acronym{IMAP}.
753 * Outgoing Messages:: What happens when you post/mail something?
754 * Agent Variables:: Customizing is fun.
755 * Example Setup:: An example @file{~/.gnus.el} file for offline people.
756 * Batching Agents:: How to fetch news from a @code{cron} job.
757 * Agent Caveats:: What you think it'll do and what it does.
761 * Category Syntax:: What a category looks like.
762 * Category Buffer:: A buffer for maintaining categories.
763 * Category Variables:: Customize'r'Us.
767 * Group Agent Commands:: Configure groups and fetch their contents.
768 * Summary Agent Commands:: Manually select then fetch specific articles.
769 * Server Agent Commands:: Select the servers that are supported by the agent.
773 * Summary Score Commands:: Adding score entries for the current group.
774 * Group Score Commands:: General score commands.
775 * Score Variables:: Customize your scoring. (My, what terminology).
776 * Score File Format:: What a score file may contain.
777 * Score File Editing:: You can edit score files by hand as well.
778 * Adaptive Scoring:: Big Sister Gnus knows what you read.
779 * Home Score File:: How to say where new score entries are to go.
780 * Followups To Yourself:: Having Gnus notice when people answer you.
781 * Scoring On Other Headers:: Scoring on non-standard headers.
782 * Scoring Tips:: How to score effectively.
783 * Reverse Scoring:: That problem child of old is not problem.
784 * Global Score Files:: Earth-spanning, ear-splitting score files.
785 * Kill Files:: They are still here, but they can be ignored.
786 * Converting Kill Files:: Translating kill files to score files.
787 * Advanced Scoring:: Using logical expressions to build score rules.
788 * Score Decays:: It can be useful to let scores wither away.
792 * Advanced Scoring Syntax:: A definition.
793 * Advanced Scoring Examples:: What they look like.
794 * Advanced Scoring Tips:: Getting the most out of it.
798 * nnir:: Searching with various engines.
799 * nnmairix:: Searching with Mairix.
803 * What is nnir?:: What does nnir do.
804 * Basic Usage:: How to perform simple searches.
805 * Setting up nnir:: How to set up nnir.
809 * Associating Engines:: How to associate engines.
813 * Process/Prefix:: A convention used by many treatment commands.
814 * Interactive:: Making Gnus ask you many questions.
815 * Symbolic Prefixes:: How to supply some Gnus functions with options.
816 * Formatting Variables:: You can specify what buffers should look like.
817 * Window Layout:: Configuring the Gnus buffer windows.
818 * Faces and Fonts:: How to change how faces look.
819 * Compilation:: How to speed Gnus up.
820 * Mode Lines:: Displaying information in the mode lines.
821 * Highlighting and Menus:: Making buffers look all nice and cozy.
822 * Daemons:: Gnus can do things behind your back.
823 * Undo:: Some actions can be undone.
824 * Predicate Specifiers:: Specifying predicates.
825 * Moderation:: What to do if you're a moderator.
826 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
827 * Fuzzy Matching:: What's the big fuzz?
828 * Thwarting Email Spam:: Simple ways to avoid unsolicited commercial email.
829 * Spam Package:: A package for filtering and processing spam.
830 * The Gnus Registry:: A package for tracking messages by Message-ID.
831 * Other modes:: Interaction with other modes.
832 * Various Various:: Things that are really various.
836 * Formatting Basics:: A formatting variable is basically a format string.
837 * Mode Line Formatting:: Some rules about mode line formatting variables.
838 * Advanced Formatting:: Modifying output in various ways.
839 * User-Defined Specs:: Having Gnus call your own functions.
840 * Formatting Fonts:: Making the formatting look colorful and nice.
841 * Positioning Point:: Moving point to a position after an operation.
842 * Tabulation:: Tabulating your output.
843 * Wide Characters:: Dealing with wide characters.
847 * X-Face:: Display a funky, teensy black-and-white image.
848 * Face:: Display a funkier, teensier colored image.
849 * Smileys:: Show all those happy faces the way they were
851 * Picons:: How to display pictures of what you're reading.
852 * Gravatars:: Display the avatar of people you read.
853 * XVarious:: Other XEmacsy Gnusey variables.
857 * The problem of spam:: Some background, and some solutions
858 * Anti-Spam Basics:: Simple steps to reduce the amount of spam.
859 * SpamAssassin:: How to use external anti-spam tools.
860 * Hashcash:: Reduce spam by burning CPU time.
864 * Spam Package Introduction::
865 * Filtering Incoming Mail::
866 * Detecting Spam in Groups::
867 * Spam and Ham Processors::
868 * Spam Package Configuration Examples::
870 * Extending the Spam package::
871 * Spam Statistics Package::
873 Spam Statistics Package
875 * Creating a spam-stat dictionary::
876 * Splitting mail using spam-stat::
877 * Low-level interface to the spam-stat dictionary::
881 * XEmacs:: Requirements for installing under XEmacs.
882 * History:: How Gnus got where it is today.
883 * On Writing Manuals:: Why this is not a beginner's guide.
884 * Terminology:: We use really difficult, like, words here.
885 * Customization:: Tailoring Gnus to your needs.
886 * Troubleshooting:: What you might try if things do not work.
887 * Gnus Reference Guide:: Rilly, rilly technical stuff.
888 * Emacs for Heathens:: A short introduction to Emacsian terms.
889 * Frequently Asked Questions:: The Gnus FAQ
893 * Gnus Versions:: What Gnus versions have been released.
894 * Why?:: What's the point of Gnus?
895 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
896 * Conformity:: Gnus tries to conform to all standards.
897 * Emacsen:: Gnus can be run on a few modern Emacsen.
898 * Gnus Development:: How Gnus is developed.
899 * Contributors:: Oodles of people.
900 * New Features:: Pointers to some of the new stuff in Gnus.
904 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
905 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
906 * Red Gnus:: Third time best---Gnus 5.4/5.5.
907 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
908 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
909 * Oort Gnus:: It's big. It's far out. Gnus 5.10/5.11.
910 * No Gnus:: Very punny. Gnus 5.12/5.13
911 * Ma Gnus:: Celebrating 25 years of Gnus.
915 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
916 * Slow Terminal Connection:: You run a remote Emacs.
917 * Little Disk Space:: You feel that having large setup files is icky.
918 * Slow Machine:: You feel like buying a faster machine.
922 * Gnus Utility Functions:: Common functions and variable to use.
923 * Back End Interface:: How Gnus communicates with the servers.
924 * Score File Syntax:: A BNF definition of the score file standard.
925 * Headers:: How Gnus stores headers internally.
926 * Ranges:: A handy format for storing mucho numbers.
927 * Group Info:: The group info format.
928 * Extended Interactive:: Symbolic prefixes and stuff.
929 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
930 * Various File Formats:: Formats of files that Gnus use.
934 * Required Back End Functions:: Functions that must be implemented.
935 * Optional Back End Functions:: Functions that need not be implemented.
936 * Error Messaging:: How to get messages and report errors.
937 * Writing New Back Ends:: Extending old back ends.
938 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
939 * Mail-like Back Ends:: Some tips on mail back ends.
943 * Active File Format:: Information on articles and groups available.
944 * Newsgroups File Format:: Group descriptions.
948 * Keystrokes:: Entering text and executing commands.
949 * Emacs Lisp:: The built-in Emacs programming language.
955 @chapter Starting Gnus
958 If you haven't used Emacs much before using Gnus, read @ref{Emacs for
963 If your system administrator has set things up properly, starting Gnus
964 and reading news is extremely easy---you just type @kbd{M-x gnus} in
965 your Emacs. If not, you should customize the variable
966 @code{gnus-select-method} as described in @ref{Finding the News}. For a
967 minimal setup for posting should also customize the variables
968 @code{user-full-name} and @code{user-mail-address}.
970 @findex gnus-other-frame
971 @kindex M-x gnus-other-frame
972 If you want to start Gnus in a different frame, you can use the command
973 @kbd{M-x gnus-other-frame} instead.
975 If things do not go smoothly at startup, you have to twiddle some
976 variables in your @file{~/.gnus.el} file. This file is similar to
977 @file{~/.emacs}, but is read when Gnus starts.
979 If you puzzle at any terms used in this manual, please refer to the
980 terminology section (@pxref{Terminology}).
983 * Finding the News:: Choosing a method for getting news.
984 * The Server is Down:: How can I read my mail then?
985 * Slave Gnusae:: You can have more than one Gnus active at a time.
986 * New Groups:: What is Gnus supposed to do with new groups?
987 * Changing Servers:: You may want to move from one server to another.
988 * Startup Files:: Those pesky startup files---@file{.newsrc}.
989 * Auto Save:: Recovering from a crash.
990 * The Active File:: Reading the active file over a slow line Takes Time.
991 * Startup Variables:: Other variables you might change.
995 @node Finding the News
996 @section Finding the News
999 First of all, you should know that there is a special buffer called
1000 @code{*Server*} that lists all the servers Gnus knows about. You can
1001 press @kbd{^} from the Group buffer to see it. In the Server buffer,
1002 you can press @kbd{RET} on a defined server to see all the groups it
1003 serves (subscribed or not!). You can also add or delete servers, edit
1004 a foreign server's definition, agentize or de-agentize a server, and
1005 do many other neat things. @xref{Server Buffer}.
1006 @xref{Foreign Groups}. @xref{Agent Basics}.
1008 @vindex gnus-select-method
1010 The @code{gnus-select-method} variable says where Gnus should look for
1011 news. This variable should be a list where the first element says
1012 @dfn{how} and the second element says @dfn{where}. This method is your
1013 native method. All groups not fetched with this method are
1014 secondary or foreign groups.
1016 For instance, if the @samp{news.somewhere.edu} @acronym{NNTP} server is where
1017 you want to get your daily dosage of news from, you'd say:
1020 (setq gnus-select-method '(nntp "news.somewhere.edu"))
1023 If you want to read directly from the local spool, say:
1026 (setq gnus-select-method '(nnspool ""))
1029 If you can use a local spool, you probably should, as it will almost
1030 certainly be much faster. But do not use the local spool if your
1031 server is running Leafnode (which is a simple, standalone private news
1032 server); in this case, use @code{(nntp "localhost")}.
1034 @vindex gnus-nntpserver-file
1036 @cindex @acronym{NNTP} server
1037 If this variable is not set, Gnus will take a look at the
1038 @env{NNTPSERVER} environment variable. If that variable isn't set,
1039 Gnus will see whether @code{gnus-nntpserver-file}
1040 (@file{/etc/nntpserver} by default) has any opinions on the matter.
1041 If that fails as well, Gnus will try to use the machine running Emacs
1042 as an @acronym{NNTP} server. That's a long shot, though.
1044 @findex gnus-group-browse-foreign-server
1046 However, if you use one @acronym{NNTP} server regularly and are just
1047 interested in a couple of groups from a different server, you would be
1048 better served by using the @kbd{B} command in the group buffer. It will
1049 let you have a look at what groups are available, and you can subscribe
1050 to any of the groups you want to. This also makes @file{.newsrc}
1051 maintenance much tidier. @xref{Foreign Groups}.
1053 @vindex gnus-secondary-select-methods
1055 A slightly different approach to foreign groups is to set the
1056 @code{gnus-secondary-select-methods} variable. The select methods
1057 listed in this variable are in many ways just as native as the
1058 @code{gnus-select-method} server. They will also be queried for active
1059 files during startup (if that's required), and new newsgroups that
1060 appear on these servers will be subscribed (or not) just as native
1063 For instance, if you use the @code{nnmbox} back end to read your mail,
1064 you would typically set this variable to
1067 (setq gnus-secondary-select-methods '((nnmbox "")))
1070 Note: the @acronym{NNTP} back end stores marks in marks files
1071 (@pxref{NNTP marks}). This feature makes it easy to share marks between
1072 several Gnus installations, but may slow down things a bit when fetching
1073 new articles. @xref{NNTP marks}, for more information.
1076 @node The Server is Down
1077 @section The Server is Down
1078 @cindex server errors
1080 If the default server is down, Gnus will understandably have some
1081 problems starting. However, if you have some mail groups in addition to
1082 the news groups, you may want to start Gnus anyway.
1084 Gnus, being the trusting sort of program, will ask whether to proceed
1085 without a native select method if that server can't be contacted. This
1086 will happen whether the server doesn't actually exist (i.e., you have
1087 given the wrong address) or the server has just momentarily taken ill
1088 for some reason or other. If you decide to continue and have no foreign
1089 groups, you'll find it difficult to actually do anything in the group
1090 buffer. But, hey, that's your problem. Blllrph!
1092 @findex gnus-no-server
1093 @kindex M-x gnus-no-server
1095 If you know that the server is definitely down, or you just want to read
1096 your mail without bothering with the server at all, you can use the
1097 @code{gnus-no-server} command to start Gnus. That might come in handy
1098 if you're in a hurry as well. This command will not attempt to contact
1099 your primary server---instead, it will just activate all groups on level
1100 1 and 2. (You should preferably keep no native groups on those two
1101 levels.) Also @pxref{Group Levels}.
1105 @section Slave Gnusae
1108 You might want to run more than one Emacs with more than one Gnus at the
1109 same time. If you are using different @file{.newsrc} files (e.g., if you
1110 are using the two different Gnusae to read from two different servers),
1111 that is no problem whatsoever. You just do it.
1113 The problem appears when you want to run two Gnusae that use the same
1114 @file{.newsrc} file.
1116 To work around that problem some, we here at the Think-Tank at the Gnus
1117 Towers have come up with a new concept: @dfn{Masters} and
1118 @dfn{slaves}. (We have applied for a patent on this concept, and have
1119 taken out a copyright on those words. If you wish to use those words in
1120 conjunction with each other, you have to send $1 per usage instance to
1121 me. Usage of the patent (@dfn{Master/Slave Relationships In Computer
1122 Applications}) will be much more expensive, of course.)
1125 Anyway, you start one Gnus up the normal way with @kbd{M-x gnus} (or
1126 however you do it). Each subsequent slave Gnusae should be started with
1127 @kbd{M-x gnus-slave}. These slaves won't save normal @file{.newsrc}
1128 files, but instead save @dfn{slave files} that contain information only
1129 on what groups have been read in the slave session. When a master Gnus
1130 starts, it will read (and delete) these slave files, incorporating all
1131 information from them. (The slave files will be read in the sequence
1132 they were created, so the latest changes will have precedence.)
1134 Information from the slave files has, of course, precedence over the
1135 information in the normal (i.e., master) @file{.newsrc} file.
1137 If the @file{.newsrc*} files have not been saved in the master when the
1138 slave starts, you may be prompted as to whether to read an auto-save
1139 file. If you answer ``yes'', the unsaved changes to the master will be
1140 incorporated into the slave. If you answer ``no'', the slave may see some
1141 messages as unread that have been read in the master.
1148 @cindex subscription
1150 @vindex gnus-check-new-newsgroups
1151 If you are satisfied that you really never want to see any new groups,
1152 you can set @code{gnus-check-new-newsgroups} to @code{nil}. This will
1153 also save you some time at startup. Even if this variable is
1154 @code{nil}, you can always subscribe to the new groups just by pressing
1155 @kbd{U} in the group buffer (@pxref{Group Maintenance}). This variable
1156 is @code{ask-server} by default. If you set this variable to
1157 @code{always}, then Gnus will query the back ends for new groups even
1158 when you do the @kbd{g} command (@pxref{Scanning New Messages}).
1161 * Checking New Groups:: Determining what groups are new.
1162 * Subscription Methods:: What Gnus should do with new groups.
1163 * Filtering New Groups:: Making Gnus ignore certain new groups.
1167 @node Checking New Groups
1168 @subsection Checking New Groups
1170 Gnus normally determines whether a group is new or not by comparing
1171 the list of groups from the active file(s) with the lists of
1172 subscribed and dead groups. This isn't a particularly fast method.
1173 If @code{gnus-check-new-newsgroups} is @code{ask-server}, Gnus will
1174 ask the server for new groups since the last time. This is both
1175 faster and cheaper. This also means that you can get rid of the list
1176 of killed groups (@pxref{Group Levels}) altogether, so you may set
1177 @code{gnus-save-killed-list} to @code{nil}, which will save time both
1178 at startup, at exit, and all over. Saves disk space, too. Why isn't
1179 this the default, then? Unfortunately, not all servers support this
1182 I bet I know what you're thinking now: How do I find out whether my
1183 server supports @code{ask-server}? No? Good, because I don't have a
1184 fail-safe answer. I would suggest just setting this variable to
1185 @code{ask-server} and see whether any new groups appear within the next
1186 few days. If any do, then it works. If none do, then it doesn't
1187 work. I could write a function to make Gnus guess whether the server
1188 supports @code{ask-server}, but it would just be a guess. So I won't.
1189 You could @code{telnet} to the server and say @code{HELP} and see
1190 whether it lists @samp{NEWGROUPS} among the commands it understands. If
1191 it does, then it might work. (But there are servers that lists
1192 @samp{NEWGROUPS} without supporting the function properly.)
1194 This variable can also be a list of select methods. If so, Gnus will
1195 issue an @code{ask-server} command to each of the select methods, and
1196 subscribe them (or not) using the normal methods. This might be handy
1197 if you are monitoring a few servers for new groups. A side effect is
1198 that startup will take much longer, so you can meditate while waiting.
1199 Use the mantra ``dingnusdingnusdingnus'' to achieve permanent bliss.
1202 @node Subscription Methods
1203 @subsection Subscription Methods
1205 @vindex gnus-subscribe-newsgroup-method
1206 What Gnus does when it encounters a new group is determined by the
1207 @code{gnus-subscribe-newsgroup-method} variable.
1209 This variable should contain a function. This function will be called
1210 with the name of the new group as the only parameter.
1212 Some handy pre-fab functions are:
1216 @item gnus-subscribe-zombies
1217 @vindex gnus-subscribe-zombies
1218 Make all new groups zombies (@pxref{Group Levels}). This is the
1219 default. You can browse the zombies later (with @kbd{A z}) and either
1220 kill them all off properly (with @kbd{S z}), or subscribe to them
1223 @item gnus-subscribe-randomly
1224 @vindex gnus-subscribe-randomly
1225 Subscribe all new groups in arbitrary order. This really means that all
1226 new groups will be added at ``the top'' of the group buffer.
1228 @item gnus-subscribe-alphabetically
1229 @vindex gnus-subscribe-alphabetically
1230 Subscribe all new groups in alphabetical order.
1232 @item gnus-subscribe-hierarchically
1233 @vindex gnus-subscribe-hierarchically
1234 Subscribe all new groups hierarchically. The difference between this
1235 function and @code{gnus-subscribe-alphabetically} is slight.
1236 @code{gnus-subscribe-alphabetically} will subscribe new groups in a strictly
1237 alphabetical fashion, while this function will enter groups into its
1238 hierarchy. So if you want to have the @samp{rec} hierarchy before the
1239 @samp{comp} hierarchy, this function will not mess that configuration
1240 up. Or something like that.
1242 @item gnus-subscribe-interactively
1243 @vindex gnus-subscribe-interactively
1244 Subscribe new groups interactively. This means that Gnus will ask
1245 you about @strong{all} new groups. The groups you choose to subscribe
1246 to will be subscribed hierarchically.
1248 @item gnus-subscribe-killed
1249 @vindex gnus-subscribe-killed
1250 Kill all new groups.
1252 @item gnus-subscribe-topics
1253 @vindex gnus-subscribe-topics
1254 Put the groups into the topic that has a matching @code{subscribe} topic
1255 parameter (@pxref{Topic Parameters}). For instance, a @code{subscribe}
1256 topic parameter that looks like
1262 will mean that all groups that match that regex will be subscribed under
1265 If no topics match the groups, the groups will be subscribed in the
1270 @vindex gnus-subscribe-hierarchical-interactive
1271 A closely related variable is
1272 @code{gnus-subscribe-hierarchical-interactive}. (That's quite a
1273 mouthful.) If this variable is non-@code{nil}, Gnus will ask you in a
1274 hierarchical fashion whether to subscribe to new groups or not. Gnus
1275 will ask you for each sub-hierarchy whether you want to descend the
1278 One common mistake is to set the variable a few paragraphs above
1279 (@code{gnus-subscribe-newsgroup-method}) to
1280 @code{gnus-subscribe-hierarchical-interactive}. This is an error. This
1281 will not work. This is ga-ga. So don't do it.
1284 @node Filtering New Groups
1285 @subsection Filtering New Groups
1287 A nice and portable way to control which new newsgroups should be
1288 subscribed (or ignored) is to put an @dfn{options} line at the start of
1289 the @file{.newsrc} file. Here's an example:
1292 options -n !alt.all !rec.all sci.all
1295 @vindex gnus-subscribe-options-newsgroup-method
1296 This line obviously belongs to a serious-minded intellectual scientific
1297 person (or she may just be plain old boring), because it says that all
1298 groups that have names beginning with @samp{alt} and @samp{rec} should
1299 be ignored, and all groups with names beginning with @samp{sci} should
1300 be subscribed. Gnus will not use the normal subscription method for
1301 subscribing these groups.
1302 @code{gnus-subscribe-options-newsgroup-method} is used instead. This
1303 variable defaults to @code{gnus-subscribe-alphabetically}.
1305 The ``options -n'' format is very simplistic. The syntax above is all
1306 that is supports -- you can force-subscribe hierarchies, or you can
1307 deny hierarchies, and that's it.
1309 @vindex gnus-options-not-subscribe
1310 @vindex gnus-options-subscribe
1311 If you don't want to mess with your @file{.newsrc} file, you can just
1312 set the two variables @code{gnus-options-subscribe} and
1313 @code{gnus-options-not-subscribe}. These two variables do exactly the
1314 same as the @file{.newsrc} @samp{options -n} trick. Both are regexps,
1315 and if the new group matches the former, it will be unconditionally
1316 subscribed, and if it matches the latter, it will be ignored.
1318 @vindex gnus-auto-subscribed-groups
1319 Yet another variable that meddles here is
1320 @code{gnus-auto-subscribed-groups}. It works exactly like
1321 @code{gnus-options-subscribe}, and is therefore really superfluous,
1322 but I thought it would be nice to have two of these. This variable is
1323 more meant for setting some ground rules, while the other variable is
1324 used more for user fiddling. By default this variable makes all new
1325 groups that come from mail back ends (@code{nnml}, @code{nnbabyl},
1326 @code{nnfolder}, @code{nnmbox}, @code{nnmh}, @code{nnimap}, and
1327 @code{nnmaildir}) subscribed. If you don't like that, just set this
1328 variable to @code{nil}.
1330 @vindex gnus-auto-subscribed-categories
1331 As if that wasn't enough, @code{gnus-auto-subscribed-categories} also
1332 allows you to specify that new groups should be subscribed based on the
1333 category their select methods belong to. The default is @samp{(mail
1334 post-mail)}, meaning that all new groups from mail-like backends
1335 should be subscribed automatically.
1337 New groups that match these variables are subscribed using
1338 @code{gnus-subscribe-options-newsgroup-method}.
1341 @node Changing Servers
1342 @section Changing Servers
1343 @cindex changing servers
1345 Sometimes it is necessary to move from one @acronym{NNTP} server to another.
1346 This happens very rarely, but perhaps you change jobs, or one server is
1347 very flaky and you want to use another.
1349 Changing the server is pretty easy, right? You just change
1350 @code{gnus-select-method} to point to the new server?
1354 Article numbers are not (in any way) kept synchronized between different
1355 @acronym{NNTP} servers, and the only way Gnus keeps track of what articles
1356 you have read is by keeping track of article numbers. So when you
1357 change @code{gnus-select-method}, your @file{.newsrc} file becomes
1360 @kindex M-x gnus-group-clear-data-on-native-groups
1361 @findex gnus-group-clear-data-on-native-groups
1362 You can use the @kbd{M-x gnus-group-clear-data-on-native-groups}
1363 command to clear out all data that you have on your native groups.
1366 @kindex M-x gnus-group-clear-data
1367 @findex gnus-group-clear-data
1368 Clear the data from the current group only---nix out marks and the
1369 list of read articles (@code{gnus-group-clear-data}).
1371 After changing servers, you @strong{must} move the cache hierarchy away,
1372 since the cached articles will have wrong article numbers, which will
1373 affect which articles Gnus thinks are read.
1374 @code{gnus-group-clear-data-on-native-groups} will ask you if you want
1375 to have it done automatically; for @code{gnus-group-clear-data}, you
1376 can use @kbd{M-x gnus-cache-move-cache} (but beware, it will move the
1377 cache for all groups).
1381 @section Startup Files
1382 @cindex startup files
1387 Most common Unix news readers use a shared startup file called
1388 @file{.newsrc}. This file contains all the information about what
1389 groups are subscribed, and which articles in these groups have been
1392 Things got a bit more complicated with @sc{gnus}. In addition to
1393 keeping the @file{.newsrc} file updated, it also used a file called
1394 @file{.newsrc.el} for storing all the information that didn't fit into
1395 the @file{.newsrc} file. (Actually, it also duplicated everything in
1396 the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
1397 files was the most recently saved, which enabled people to swap between
1398 @sc{gnus} and other newsreaders.
1400 That was kinda silly, so Gnus went one better: In addition to the
1401 @file{.newsrc} and @file{.newsrc.el} files, Gnus also has a file called
1402 @file{.newsrc.eld}. It will read whichever of these files that are most
1403 recent, but it will never write a @file{.newsrc.el} file. You should
1404 never delete the @file{.newsrc.eld} file---it contains much information
1405 not stored in the @file{.newsrc} file.
1407 @vindex gnus-save-newsrc-file
1408 @vindex gnus-read-newsrc-file
1409 You can turn off writing the @file{.newsrc} file by setting
1410 @code{gnus-save-newsrc-file} to @code{nil}, which means you can delete
1411 the file and save some space, as well as exiting from Gnus faster.
1412 However, this will make it impossible to use other newsreaders than
1413 Gnus. But hey, who would want to, right? Similarly, setting
1414 @code{gnus-read-newsrc-file} to @code{nil} makes Gnus ignore the
1415 @file{.newsrc} file and any @file{.newsrc-SERVER} files, which can be
1416 convenient if you use a different news reader occasionally, and you
1417 want to read a different subset of the available groups with that
1420 @vindex gnus-save-killed-list
1421 If @code{gnus-save-killed-list} (default @code{t}) is @code{nil}, Gnus
1422 will not save the list of killed groups to the startup file. This will
1423 save both time (when starting and quitting) and space (on disk). It
1424 will also mean that Gnus has no record of what groups are new or old,
1425 so the automatic new groups subscription methods become meaningless.
1426 You should always set @code{gnus-check-new-newsgroups} to @code{nil} or
1427 @code{ask-server} if you set this variable to @code{nil} (@pxref{New
1428 Groups}). This variable can also be a regular expression. If that's
1429 the case, remove all groups that do not match this regexp before
1430 saving. This can be useful in certain obscure situations that involve
1431 several servers where not all servers support @code{ask-server}.
1433 @vindex gnus-startup-file
1434 @vindex gnus-backup-startup-file
1435 @vindex version-control
1436 The @code{gnus-startup-file} variable says where the startup files are.
1437 The default value is @file{~/.newsrc}, with the Gnus (El Dingo) startup
1438 file being whatever that one is, with a @samp{.eld} appended.
1439 If you want to keep multiple numbered backups of this file, set
1440 @code{gnus-backup-startup-file}. It respects the same values as the
1441 @code{version-control} variable.
1443 @vindex gnus-save-newsrc-hook
1444 @vindex gnus-save-quick-newsrc-hook
1445 @vindex gnus-save-standard-newsrc-hook
1446 @code{gnus-save-newsrc-hook} is called before saving any of the newsrc
1447 files, while @code{gnus-save-quick-newsrc-hook} is called just before
1448 saving the @file{.newsrc.eld} file, and
1449 @code{gnus-save-standard-newsrc-hook} is called just before saving the
1450 @file{.newsrc} file. The latter two are commonly used to turn version
1451 control on or off. Version control is on by default when saving the
1452 startup files. If you want to turn backup creation off, say something like:
1455 (defun turn-off-backup ()
1456 (set (make-local-variable 'backup-inhibited) t))
1458 (add-hook 'gnus-save-quick-newsrc-hook 'turn-off-backup)
1459 (add-hook 'gnus-save-standard-newsrc-hook 'turn-off-backup)
1462 @vindex gnus-init-file
1463 @vindex gnus-site-init-file
1464 When Gnus starts, it will read the @code{gnus-site-init-file}
1465 (@file{.../site-lisp/gnus-init} by default) and @code{gnus-init-file}
1466 (@file{~/.gnus} by default) files. These are normal Emacs Lisp files
1467 and can be used to avoid cluttering your @file{~/.emacs} and
1468 @file{site-init} files with Gnus stuff. Gnus will also check for files
1469 with the same names as these, but with @file{.elc} and @file{.el}
1470 suffixes. In other words, if you have set @code{gnus-init-file} to
1471 @file{~/.gnus}, it will look for @file{~/.gnus.elc}, @file{~/.gnus.el},
1472 and finally @file{~/.gnus} (in this order). If Emacs was invoked with
1473 the @option{-q} or @option{--no-init-file} options (@pxref{Initial
1474 Options, ,Initial Options, emacs, The Emacs Manual}), Gnus doesn't read
1475 @code{gnus-init-file}.
1480 @cindex dribble file
1483 Whenever you do something that changes the Gnus data (reading articles,
1484 catching up, killing/subscribing groups), the change is added to a
1485 special @dfn{dribble buffer}. This buffer is auto-saved the normal
1486 Emacs way. If your Emacs should crash before you have saved the
1487 @file{.newsrc} files, all changes you have made can be recovered from
1490 If Gnus detects this file at startup, it will ask the user whether to
1491 read it. The auto save file is deleted whenever the real startup file is
1494 @vindex gnus-use-dribble-file
1495 If @code{gnus-use-dribble-file} is @code{nil}, Gnus won't create and
1496 maintain a dribble buffer. The default is @code{t}.
1498 @vindex gnus-dribble-directory
1499 Gnus will put the dribble file(s) in @code{gnus-dribble-directory}. If
1500 this variable is @code{nil}, which it is by default, Gnus will dribble
1501 into the directory where the @file{.newsrc} file is located. (This is
1502 normally the user's home directory.) The dribble file will get the same
1503 file permissions as the @file{.newsrc} file.
1505 @vindex gnus-always-read-dribble-file
1506 If @code{gnus-always-read-dribble-file} is non-@code{nil}, Gnus will
1507 read the dribble file on startup without querying the user.
1510 @node The Active File
1511 @section The Active File
1513 @cindex ignored groups
1515 When Gnus starts, or indeed whenever it tries to determine whether new
1516 articles have arrived, it reads the active file. This is a very large
1517 file that lists all the active groups and articles on the server.
1519 @vindex gnus-ignored-newsgroups
1520 Before examining the active file, Gnus deletes all lines that match the
1521 regexp @code{gnus-ignored-newsgroups}. This is done primarily to reject
1522 any groups with bogus names, but you can use this variable to make Gnus
1523 ignore hierarchies you aren't ever interested in. However, this is not
1524 recommended. In fact, it's highly discouraged. Instead, @pxref{New
1525 Groups} for an overview of other variables that can be used instead.
1528 @c @code{nil} by default, and will slow down active file handling somewhat
1529 @c if you set it to anything else.
1531 @vindex gnus-read-active-file
1533 The active file can be rather Huge, so if you have a slow network, you
1534 can set @code{gnus-read-active-file} to @code{nil} to prevent Gnus from
1535 reading the active file. This variable is @code{some} by default.
1537 Gnus will try to make do by getting information just on the groups that
1538 you actually subscribe to.
1540 Note that if you subscribe to lots and lots of groups, setting this
1541 variable to @code{nil} will probably make Gnus slower, not faster. At
1542 present, having this variable @code{nil} will slow Gnus down
1543 considerably, unless you read news over a 2400 baud modem.
1545 This variable can also have the value @code{some}. Gnus will then
1546 attempt to read active info only on the subscribed groups. On some
1547 servers this is quite fast (on sparkling, brand new INN servers that
1548 support the @code{LIST ACTIVE group} command), on others this isn't fast
1549 at all. In any case, @code{some} should be faster than @code{nil}, and
1550 is certainly faster than @code{t} over slow lines.
1552 Some news servers (old versions of Leafnode and old versions of INN, for
1553 instance) do not support the @code{LIST ACTIVE group}. For these
1554 servers, @code{nil} is probably the most efficient value for this
1557 If this variable is @code{nil}, Gnus will ask for group info in total
1558 lock-step, which isn't very fast. If it is @code{some} and you use an
1559 @acronym{NNTP} server, Gnus will pump out commands as fast as it can, and
1560 read all the replies in one swoop. This will normally result in better
1561 performance, but if the server does not support the aforementioned
1562 @code{LIST ACTIVE group} command, this isn't very nice to the server.
1564 If you think that starting up Gnus takes too long, try all the three
1565 different values for this variable and see what works best for you.
1567 In any case, if you use @code{some} or @code{nil}, you should definitely
1568 kill all groups that you aren't interested in to speed things up.
1570 Note that this variable also affects active file retrieval from
1571 secondary select methods.
1574 @node Startup Variables
1575 @section Startup Variables
1579 @item gnus-load-hook
1580 @vindex gnus-load-hook
1581 A hook run while Gnus is being loaded. Note that this hook will
1582 normally be run just once in each Emacs session, no matter how many
1583 times you start Gnus.
1585 @item gnus-before-startup-hook
1586 @vindex gnus-before-startup-hook
1587 A hook called as the first thing when Gnus is started.
1589 @item gnus-startup-hook
1590 @vindex gnus-startup-hook
1591 A hook run as the very last thing after starting up Gnus
1593 @item gnus-started-hook
1594 @vindex gnus-started-hook
1595 A hook that is run as the very last thing after starting up Gnus
1598 @item gnus-setup-news-hook
1599 @vindex gnus-setup-news-hook
1600 A hook that is run after reading the @file{.newsrc} file(s), but before
1601 generating the group buffer.
1603 @item gnus-check-bogus-newsgroups
1604 @vindex gnus-check-bogus-newsgroups
1605 If non-@code{nil}, Gnus will check for and delete all bogus groups at
1606 startup. A @dfn{bogus group} is a group that you have in your
1607 @file{.newsrc} file, but doesn't exist on the news server. Checking for
1608 bogus groups can take quite a while, so to save time and resources it's
1609 best to leave this option off, and do the checking for bogus groups once
1610 in a while from the group buffer instead (@pxref{Group Maintenance}).
1612 @item gnus-inhibit-startup-message
1613 @vindex gnus-inhibit-startup-message
1614 If non-@code{nil}, the startup message won't be displayed. That way,
1615 your boss might not notice as easily that you are reading news instead
1616 of doing your job. Note that this variable is used before
1617 @file{~/.gnus.el} is loaded, so it should be set in @file{.emacs} instead.
1619 @item gnus-no-groups-message
1620 @vindex gnus-no-groups-message
1621 Message displayed by Gnus when no groups are available.
1623 @item gnus-use-backend-marks
1624 @vindex gnus-use-backend-marks
1625 If non-@code{nil}, Gnus will store article marks both in the
1626 @file{.newsrc.eld} file and in the backends. This will slow down
1627 group operation some.
1633 @chapter Group Buffer
1634 @cindex group buffer
1636 @c Alex Schroeder suggests to rearrange this as follows:
1638 @c <kensanata> ok, just save it for reference. I'll go to bed in a minute.
1639 @c 1. Selecting a Group, 2. (new) Finding a Group, 3. Group Levels,
1640 @c 4. Subscription Commands, 5. Group Maneuvering, 6. Group Data,
1641 @c 7. Group Score, 8. Group Buffer Format
1642 @c <kensanata> Group Levels should have more information on levels 5 to 9. I
1643 @c suggest to split the 4th paragraph ("Gnus considers groups...") as follows:
1644 @c <kensanata> First, "Gnus considers groups... (default 9)."
1645 @c <kensanata> New, a table summarizing what levels 1 to 9 mean.
1646 @c <kensanata> Third, "Gnus treats subscribed ... reasons of efficiency"
1647 @c <kensanata> Then expand the next paragraph or add some more to it.
1648 @c This short one sentence explains levels 1 and 2, therefore I understand
1649 @c that I should keep important news at 3 and boring news at 4.
1650 @c Say so! Then go on to explain why I should bother with levels 6 to 9.
1651 @c Maybe keep those that you don't want to read temporarily at 6,
1652 @c those that you never want to read at 8, those that offend your
1653 @c human rights at 9...
1656 The @dfn{group buffer} lists all (or parts) of the available groups. It
1657 is the first buffer shown when Gnus starts, and will never be killed as
1658 long as Gnus is active.
1662 \gnusfigure{The Group Buffer}{320}{
1663 \put(75,50){\epsfig{figure=ps/group,height=9cm}}
1664 \put(120,37){\makebox(0,0)[t]{Buffer name}}
1665 \put(120,38){\vector(1,2){10}}
1666 \put(40,60){\makebox(0,0)[r]{Mode line}}
1667 \put(40,58){\vector(1,0){30}}
1668 \put(200,28){\makebox(0,0)[t]{Native select method}}
1669 \put(200,26){\vector(-1,2){15}}
1675 * Group Buffer Format:: Information listed and how you can change it.
1676 * Group Maneuvering:: Commands for moving in the group buffer.
1677 * Selecting a Group:: Actually reading news.
1678 * Subscription Commands:: Unsubscribing, killing, subscribing.
1679 * Group Data:: Changing the info for a group.
1680 * Group Levels:: Levels? What are those, then?
1681 * Group Score:: A mechanism for finding out what groups you like.
1682 * Marking Groups:: You can mark groups for later processing.
1683 * Foreign Groups:: Creating and editing groups.
1684 * Group Parameters:: Each group may have different parameters set.
1685 * Listing Groups:: Gnus can list various subsets of the groups.
1686 * Sorting Groups:: Re-arrange the group order.
1687 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
1688 * Browse Foreign Server:: You can browse a server. See what it has to offer.
1689 * Exiting Gnus:: Stop reading news and get some work done.
1690 * Group Topics:: A folding group mode divided into topics.
1691 * Non-ASCII Group Names:: Accessing groups of non-English names.
1692 * Misc Group Stuff:: Other stuff that you can to do.
1696 @node Group Buffer Format
1697 @section Group Buffer Format
1700 * Group Line Specification:: Deciding how the group buffer is to look.
1701 * Group Mode Line Specification:: The group buffer mode line.
1702 * Group Highlighting:: Having nice colors in the group buffer.
1705 You can customize the Group Mode tool bar, see @kbd{M-x
1706 customize-apropos RET gnus-group-tool-bar}. This feature is only
1709 The tool bar icons are now (de)activated correctly depending on the
1710 cursor position. Therefore, moving around in the Group Buffer is
1711 slower. You can disable this via the variable
1712 @code{gnus-group-update-tool-bar}. Its default value depends on your
1715 @node Group Line Specification
1716 @subsection Group Line Specification
1717 @cindex group buffer format
1719 The default format of the group buffer is nice and dull, but you can
1720 make it as exciting and ugly as you feel like.
1722 Here's a couple of example group lines:
1725 25: news.announce.newusers
1726 * 0: alt.fan.andrea-dworkin
1731 You can see that there are 25 unread articles in
1732 @samp{news.announce.newusers}. There are no unread articles, but some
1733 ticked articles, in @samp{alt.fan.andrea-dworkin} (see that little
1734 asterisk at the beginning of the line?).
1736 @vindex gnus-group-line-format
1737 You can change that format to whatever you want by fiddling with the
1738 @code{gnus-group-line-format} variable. This variable works along the
1739 lines of a @code{format} specification, which is pretty much the same as
1740 a @code{printf} specifications, for those of you who use (feh!) C.
1741 @xref{Formatting Variables}.
1743 @samp{%M%S%5y:%B%(%g%)\n} is the value that produced those lines above.
1745 There should always be a colon on the line; the cursor always moves to
1746 the colon after performing an operation. @xref{Positioning
1747 Point}. Nothing else is required---not even the group name. All
1748 displayed text is just window dressing, and is never examined by Gnus.
1749 Gnus stores all real information it needs using text properties.
1751 (Note that if you make a really strange, wonderful, spreadsheet-like
1752 layout, everybody will believe you are hard at work with the accounting
1753 instead of wasting time reading news.)
1755 Here's a list of all available format characters:
1760 An asterisk if the group only has marked articles.
1763 Whether the group is subscribed.
1766 Level of subscribedness.
1769 Number of unread articles.
1772 Number of dormant articles.
1775 Number of ticked articles.
1778 Number of read articles.
1781 Number of unseen articles.
1784 Estimated total number of articles. (This is really @var{max-number}
1785 minus @var{min-number} plus 1.)
1787 Gnus uses this estimation because the @acronym{NNTP} protocol provides
1788 efficient access to @var{max-number} and @var{min-number} but getting
1789 the true unread message count is not possible efficiently. For
1790 hysterical raisins, even the mail back ends, where the true number of
1791 unread messages might be available efficiently, use the same limited
1792 interface. To remove this restriction from Gnus means that the back
1793 end interface has to be changed, which is not an easy job.
1795 The nnml backend (@pxref{Mail Spool}) has a feature called ``group
1796 compaction'' which circumvents this deficiency: the idea is to
1797 renumber all articles from 1, removing all gaps between numbers, hence
1798 getting a correct total count. Other backends may support this in the
1799 future. In order to keep your total article count relatively up to
1800 date, you might want to compact your groups (or even directly your
1801 server) from time to time. @xref{Misc Group Stuff}, @xref{Server Commands}.
1804 Number of unread, unticked, non-dormant articles.
1807 Number of ticked and dormant articles.
1816 Group comment (@pxref{Group Parameters}) or group name if there is no
1817 comment element in the group parameters.
1820 Newsgroup description. You need to read the group descriptions
1821 before these will appear, and to do that, you either have to set
1822 @code{gnus-read-active-file} or use the group buffer @kbd{M-d}
1826 @samp{m} if moderated.
1829 @samp{(m)} if moderated.
1835 If the summary buffer for the group is open or not.
1841 A string that looks like @samp{<%s:%n>} if a foreign select method is
1845 Indentation based on the level of the topic (@pxref{Group Topics}).
1848 @vindex gnus-group-uncollapsed-levels
1849 Short (collapsed) group name. The @code{gnus-group-uncollapsed-levels}
1850 variable says how many levels to leave at the end of the group name.
1851 The default is 1---this will mean that group names like
1852 @samp{gnu.emacs.gnus} will be shortened to @samp{g.e.gnus}.
1855 @vindex gnus-new-mail-mark
1857 @samp{%} (@code{gnus-new-mail-mark}) if there has arrived new mail to
1861 @samp{#} (@code{gnus-process-mark}) if the group is process marked.
1864 A string that says when you last read the group (@pxref{Group
1868 The disk space used by the articles fetched by both the cache and
1869 agent. The value is automatically scaled to bytes(B), kilobytes(K),
1870 megabytes(M), or gigabytes(G) to minimize the column width. A format
1871 of %7F is sufficient for a fixed-width column.
1874 User defined specifier. The next character in the format string should
1875 be a letter. Gnus will call the function
1876 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
1877 following @samp{%u}. The function will be passed a single dummy
1878 parameter as argument. The function should return a string, which will
1879 be inserted into the buffer just like information from any other
1884 All the ``number-of'' specs will be filled with an asterisk (@samp{*})
1885 if no info is available---for instance, if it is a non-activated foreign
1886 group, or a bogus native group.
1889 @node Group Mode Line Specification
1890 @subsection Group Mode Line Specification
1891 @cindex group mode line
1893 @vindex gnus-group-mode-line-format
1894 The mode line can be changed by setting
1895 @code{gnus-group-mode-line-format} (@pxref{Mode Line Formatting}). It
1896 doesn't understand that many format specifiers:
1900 The native news server.
1902 The native select method.
1906 @node Group Highlighting
1907 @subsection Group Highlighting
1908 @cindex highlighting
1909 @cindex group highlighting
1911 @vindex gnus-group-highlight
1912 Highlighting in the group buffer is controlled by the
1913 @code{gnus-group-highlight} variable. This is an alist with elements
1914 that look like @code{(@var{form} . @var{face})}. If @var{form} evaluates to
1915 something non-@code{nil}, the @var{face} will be used on the line.
1917 Here's an example value for this variable that might look nice if the
1921 (cond (window-system
1922 (setq custom-background-mode 'light)
1923 (defface my-group-face-1
1924 '((t (:foreground "Red" :bold t))) "First group face")
1925 (defface my-group-face-2
1926 '((t (:foreground "DarkSeaGreen4" :bold t)))
1927 "Second group face")
1928 (defface my-group-face-3
1929 '((t (:foreground "Green4" :bold t))) "Third group face")
1930 (defface my-group-face-4
1931 '((t (:foreground "SteelBlue" :bold t))) "Fourth group face")
1932 (defface my-group-face-5
1933 '((t (:foreground "Blue" :bold t))) "Fifth group face")))
1935 (setq gnus-group-highlight
1936 '(((> unread 200) . my-group-face-1)
1937 ((and (< level 3) (zerop unread)) . my-group-face-2)
1938 ((< level 3) . my-group-face-3)
1939 ((zerop unread) . my-group-face-4)
1940 (t . my-group-face-5)))
1943 Also @pxref{Faces and Fonts}.
1945 Variables that are dynamically bound when the forms are evaluated
1952 The number of unread articles in the group.
1956 Whether the group is a mail group.
1958 The level of the group.
1960 The score of the group.
1962 The number of ticked articles in the group.
1964 The total number of articles in the group. Or rather,
1965 @var{max-number} minus @var{min-number} plus one.
1967 When using the topic minor mode, this variable is bound to the current
1968 topic being inserted.
1971 When the forms are @code{eval}ed, point is at the beginning of the line
1972 of the group in question, so you can use many of the normal Gnus
1973 functions for snarfing info on the group.
1975 @vindex gnus-group-update-hook
1976 @findex gnus-group-highlight-line
1977 @code{gnus-group-update-hook} is called when a group line is changed.
1978 It will not be called when @code{gnus-visual} is @code{nil}.
1981 @node Group Maneuvering
1982 @section Group Maneuvering
1983 @cindex group movement
1985 All movement commands understand the numeric prefix and will behave as
1986 expected, hopefully.
1992 @findex gnus-group-next-unread-group
1993 Go to the next group that has unread articles
1994 (@code{gnus-group-next-unread-group}).
2000 @findex gnus-group-prev-unread-group
2001 Go to the previous group that has unread articles
2002 (@code{gnus-group-prev-unread-group}).
2006 @findex gnus-group-next-group
2007 Go to the next group (@code{gnus-group-next-group}).
2011 @findex gnus-group-prev-group
2012 Go to the previous group (@code{gnus-group-prev-group}).
2016 @findex gnus-group-next-unread-group-same-level
2017 Go to the next unread group on the same (or lower) level
2018 (@code{gnus-group-next-unread-group-same-level}).
2022 @findex gnus-group-prev-unread-group-same-level
2023 Go to the previous unread group on the same (or lower) level
2024 (@code{gnus-group-prev-unread-group-same-level}).
2027 Three commands for jumping to groups:
2033 @findex gnus-group-jump-to-group
2034 Jump to a group (and make it visible if it isn't already)
2035 (@code{gnus-group-jump-to-group}). Killed groups can be jumped to, just
2040 @findex gnus-group-best-unread-group
2041 Jump to the unread group with the lowest level
2042 (@code{gnus-group-best-unread-group}).
2046 @findex gnus-group-first-unread-group
2047 Jump to the first group with unread articles
2048 (@code{gnus-group-first-unread-group}).
2051 @vindex gnus-group-goto-unread
2052 If @code{gnus-group-goto-unread} is @code{nil}, all the movement
2053 commands will move to the next group, not the next unread group. Even
2054 the commands that say they move to the next unread group. The default
2057 @vindex gnus-summary-next-group-on-exit
2058 If @code{gnus-summary-next-group-on-exit} is @code{t}, when a summary is
2059 exited, the point in the group buffer is moved to the next unread group.
2060 Otherwise, the point is set to the group just exited. The default is
2063 @node Selecting a Group
2064 @section Selecting a Group
2065 @cindex group selection
2070 @kindex SPACE (Group)
2071 @findex gnus-group-read-group
2072 Select the current group, switch to the summary buffer and display the
2073 first unread article (@code{gnus-group-read-group}). If there are no
2074 unread articles in the group, or if you give a non-numerical prefix to
2075 this command, Gnus will offer to fetch all the old articles in this
2076 group from the server. If you give a numerical prefix @var{n}, @var{n}
2077 determines the number of articles Gnus will fetch. If @var{n} is
2078 positive, Gnus fetches the @var{n} newest articles, if @var{n} is
2079 negative, Gnus fetches the @code{abs(@var{n})} oldest articles.
2081 Thus, @kbd{SPC} enters the group normally, @kbd{C-u SPC} offers old
2082 articles, @kbd{C-u 4 2 SPC} fetches the 42 newest articles, and @kbd{C-u
2083 - 4 2 SPC} fetches the 42 oldest ones.
2085 When you are in the group (in the Summary buffer), you can type
2086 @kbd{M-g} to fetch new articles, or @kbd{C-u M-g} to also show the old
2091 @findex gnus-group-select-group
2092 Select the current group and switch to the summary buffer
2093 (@code{gnus-group-select-group}). Takes the same arguments as
2094 @code{gnus-group-read-group}---the only difference is that this command
2095 does not display the first unread article automatically upon group
2099 @kindex M-RET (Group)
2100 @findex gnus-group-quick-select-group
2101 This does the same as the command above, but tries to do it with the
2102 minimum amount of fuzz (@code{gnus-group-quick-select-group}). No
2103 scoring/killing will be performed, there will be no highlights and no
2104 expunging. This might be useful if you're in a real hurry and have to
2105 enter some humongous group. If you give a 0 prefix to this command
2106 (i.e., @kbd{0 M-RET}), Gnus won't even generate the summary buffer,
2107 which is useful if you want to toggle threading before generating the
2108 summary buffer (@pxref{Summary Generation Commands}).
2111 @kindex M-SPACE (Group)
2112 @findex gnus-group-visible-select-group
2113 This is yet one more command that does the same as the @kbd{RET}
2114 command, but this one does it without expunging and hiding dormants
2115 (@code{gnus-group-visible-select-group}).
2118 @kindex C-M-RET (Group)
2119 @findex gnus-group-select-group-ephemerally
2120 Finally, this command selects the current group ephemerally without
2121 doing any processing of its contents
2122 (@code{gnus-group-select-group-ephemerally}). Even threading has been
2123 turned off. Everything you do in the group after selecting it in this
2124 manner will have no permanent effects.
2128 @vindex gnus-large-newsgroup
2129 The @code{gnus-large-newsgroup} variable says what Gnus should
2130 consider to be a big group. If it is @code{nil}, no groups are
2131 considered big. The default value is 200. If the group has more
2132 (unread and/or ticked) articles than this, Gnus will query the user
2133 before entering the group. The user can then specify how many
2134 articles should be fetched from the server. If the user specifies a
2135 negative number (@var{-n}), the @var{n} oldest articles will be
2136 fetched. If it is positive, the @var{n} articles that have arrived
2137 most recently will be fetched.
2139 @vindex gnus-large-ephemeral-newsgroup
2140 @code{gnus-large-ephemeral-newsgroup} is the same as
2141 @code{gnus-large-newsgroup}, but is only used for ephemeral
2144 @vindex gnus-newsgroup-maximum-articles
2145 In groups in some news servers, there might be a big gap between a few
2146 very old articles that will never be expired and the recent ones. In
2147 such a case, the server will return the data like @code{(1 . 30000000)}
2148 for the @code{LIST ACTIVE group} command, for example. Even if there
2149 are actually only the articles 1-10 and 29999900-30000000, Gnus doesn't
2150 know it at first and prepares for getting 30000000 articles. However,
2151 it will consume hundreds megabytes of memories and might make Emacs get
2152 stuck as the case may be. If you use such news servers, set the
2153 variable @code{gnus-newsgroup-maximum-articles} to a positive number.
2154 The value means that Gnus ignores articles other than this number of the
2155 latest ones in every group. For instance, the value 10000 makes Gnus
2156 get only the articles 29990001-30000000 (if the latest article number is
2157 30000000 in a group). Note that setting this variable to a number might
2158 prevent you from reading very old articles. The default value of the
2159 variable @code{gnus-newsgroup-maximum-articles} is @code{nil}, which
2160 means Gnus never ignores old articles.
2162 @vindex gnus-select-group-hook
2163 @vindex gnus-auto-select-first
2164 @vindex gnus-auto-select-subject
2165 If @code{gnus-auto-select-first} is non-@code{nil}, select an article
2166 automatically when entering a group with the @kbd{SPACE} command.
2167 Which article this is controlled by the
2168 @code{gnus-auto-select-subject} variable. Valid values for this
2174 Place point on the subject line of the first unread article.
2177 Place point on the subject line of the first article.
2180 Place point on the subject line of the first unseen article.
2182 @item unseen-or-unread
2183 Place point on the subject line of the first unseen article, and if
2184 there is no such article, place point on the subject line of the first
2188 Place point on the subject line of the highest-scored unread article.
2192 This variable can also be a function. In that case, that function
2193 will be called to place point on a subject line.
2195 If you want to prevent automatic selection in some group (say, in a
2196 binary group with Huge articles) you can set the
2197 @code{gnus-auto-select-first} variable to @code{nil} in
2198 @code{gnus-select-group-hook}, which is called when a group is
2202 @node Subscription Commands
2203 @section Subscription Commands
2204 @cindex subscription
2206 The following commands allow for managing your subscriptions in the
2207 Group buffer. If you want to subscribe to many groups, it's probably
2208 more convenient to go to the @ref{Server Buffer}, and choose the
2209 server there using @kbd{RET} or @kbd{SPC}. Then you'll have the
2210 commands listed in @ref{Browse Foreign Server} at hand.
2218 @findex gnus-group-unsubscribe-current-group
2219 @c @icon{gnus-group-unsubscribe}
2220 Toggle subscription to the current group
2221 (@code{gnus-group-unsubscribe-current-group}).
2227 @findex gnus-group-unsubscribe-group
2228 Prompt for a group to subscribe, and then subscribe it. If it was
2229 subscribed already, unsubscribe it instead
2230 (@code{gnus-group-unsubscribe-group}).
2236 @findex gnus-group-kill-group
2237 @c @icon{gnus-group-kill-group}
2238 Kill the current group (@code{gnus-group-kill-group}).
2244 @findex gnus-group-yank-group
2245 Yank the last killed group (@code{gnus-group-yank-group}).
2248 @kindex C-x C-t (Group)
2249 @findex gnus-group-transpose-groups
2250 Transpose two groups (@code{gnus-group-transpose-groups}). This isn't
2251 really a subscription command, but you can use it instead of a
2252 kill-and-yank sequence sometimes.
2258 @findex gnus-group-kill-region
2259 Kill all groups in the region (@code{gnus-group-kill-region}).
2263 @findex gnus-group-kill-all-zombies
2264 Kill all zombie groups (@code{gnus-group-kill-all-zombies}).
2267 @kindex S C-k (Group)
2268 @findex gnus-group-kill-level
2269 Kill all groups on a certain level (@code{gnus-group-kill-level}).
2270 These groups can't be yanked back after killing, so this command should
2271 be used with some caution. The only time where this command comes in
2272 really handy is when you have a @file{.newsrc} with lots of unsubscribed
2273 groups that you want to get rid off. @kbd{S C-k} on level 7 will
2274 kill off all unsubscribed groups that do not have message numbers in the
2275 @file{.newsrc} file.
2279 Also @pxref{Group Levels}.
2289 @findex gnus-group-catchup-current
2290 @vindex gnus-group-catchup-group-hook
2291 @c @icon{gnus-group-catchup-current}
2292 Mark all unticked articles in this group as read
2293 (@code{gnus-group-catchup-current}).
2294 @code{gnus-group-catchup-group-hook} is called when catching up a group from
2299 @findex gnus-group-catchup-current-all
2300 Mark all articles in this group, even the ticked ones, as read
2301 (@code{gnus-group-catchup-current-all}).
2305 @findex gnus-group-clear-data
2306 Clear the data from the current group---nix out marks and the list of
2307 read articles (@code{gnus-group-clear-data}).
2309 @item M-x gnus-group-clear-data-on-native-groups
2310 @kindex M-x gnus-group-clear-data-on-native-groups
2311 @findex gnus-group-clear-data-on-native-groups
2312 If you have switched from one @acronym{NNTP} server to another, all your marks
2313 and read ranges have become worthless. You can use this command to
2314 clear out all data that you have on your native groups. Use with
2321 @section Group Levels
2325 All groups have a level of @dfn{subscribedness}. For instance, if a
2326 group is on level 2, it is more subscribed than a group on level 5. You
2327 can ask Gnus to just list groups on a given level or lower
2328 (@pxref{Listing Groups}), or to just check for new articles in groups on
2329 a given level or lower (@pxref{Scanning New Messages}).
2331 Remember: The higher the level of the group, the less important it is.
2337 @findex gnus-group-set-current-level
2338 Set the level of the current group. If a numeric prefix is given, the
2339 next @var{n} groups will have their levels set. The user will be
2340 prompted for a level.
2343 @vindex gnus-level-killed
2344 @vindex gnus-level-zombie
2345 @vindex gnus-level-unsubscribed
2346 @vindex gnus-level-subscribed
2347 Gnus considers groups from levels 1 to
2348 @code{gnus-level-subscribed} (inclusive) (default 5) to be subscribed,
2349 @code{gnus-level-subscribed} (exclusive) and
2350 @code{gnus-level-unsubscribed} (inclusive) (default 7) to be
2351 unsubscribed, @code{gnus-level-zombie} to be zombies (walking dead)
2352 (default 8) and @code{gnus-level-killed} to be killed (completely dead)
2353 (default 9). Gnus treats subscribed and unsubscribed groups exactly the
2354 same, but zombie and killed groups have no information on what articles
2355 you have read, etc, stored. This distinction between dead and living
2356 groups isn't done because it is nice or clever, it is done purely for
2357 reasons of efficiency.
2359 It is recommended that you keep all your mail groups (if any) on quite
2360 low levels (e.g. 1 or 2).
2362 Maybe the following description of the default behavior of Gnus helps to
2363 understand what these levels are all about. By default, Gnus shows you
2364 subscribed nonempty groups, but by hitting @kbd{L} you can have it show
2365 empty subscribed groups and unsubscribed groups, too. Type @kbd{l} to
2366 go back to showing nonempty subscribed groups again. Thus, unsubscribed
2367 groups are hidden, in a way.
2369 @cindex zombie groups
2370 Zombie and killed groups are similar to unsubscribed groups in that they
2371 are hidden by default. But they are different from subscribed and
2372 unsubscribed groups in that Gnus doesn't ask the news server for
2373 information (number of messages, number of unread messages) on zombie
2374 and killed groups. Normally, you use @kbd{C-k} to kill the groups you
2375 aren't interested in. If most groups are killed, Gnus is faster.
2377 Why does Gnus distinguish between zombie and killed groups? Well, when
2378 a new group arrives on the server, Gnus by default makes it a zombie
2379 group. This means that you are normally not bothered with new groups,
2380 but you can type @kbd{A z} to get a list of all new groups. Subscribe
2381 the ones you like and kill the ones you don't want. (@kbd{A k} shows a
2382 list of killed groups.)
2384 If you want to play with the level variables, you should show some care.
2385 Set them once, and don't touch them ever again. Better yet, don't touch
2386 them at all unless you know exactly what you're doing.
2388 @vindex gnus-level-default-unsubscribed
2389 @vindex gnus-level-default-subscribed
2390 Two closely related variables are @code{gnus-level-default-subscribed}
2391 (default 3) and @code{gnus-level-default-unsubscribed} (default 6),
2392 which are the levels that new groups will be put on if they are
2393 (un)subscribed. These two variables should, of course, be inside the
2394 relevant valid ranges.
2396 @vindex gnus-keep-same-level
2397 If @code{gnus-keep-same-level} is non-@code{nil}, some movement commands
2398 will only move to groups of the same level (or lower). In
2399 particular, going from the last article in one group to the next group
2400 will go to the next group of the same level (or lower). This might be
2401 handy if you want to read the most important groups before you read the
2404 If this variable is @code{best}, Gnus will make the next newsgroup the
2405 one with the best level.
2407 @vindex gnus-group-default-list-level
2408 All groups with a level less than or equal to
2409 @code{gnus-group-default-list-level} will be listed in the group buffer
2411 This variable can also be a function. In that case, that function will
2412 be called and the result will be used as value.
2415 @vindex gnus-group-list-inactive-groups
2416 If @code{gnus-group-list-inactive-groups} is non-@code{nil}, non-active
2417 groups will be listed along with the unread groups. This variable is
2418 @code{t} by default. If it is @code{nil}, inactive groups won't be
2421 @vindex gnus-group-use-permanent-levels
2422 If @code{gnus-group-use-permanent-levels} is non-@code{nil}, once you
2423 give a level prefix to @kbd{g} or @kbd{l}, all subsequent commands will
2424 use this level as the ``work'' level.
2426 @vindex gnus-activate-level
2427 Gnus will normally just activate (i. e., query the server about) groups
2428 on level @code{gnus-activate-level} or less. If you don't want to
2429 activate unsubscribed groups, for instance, you might set this variable
2430 to 5. The default is 6.
2434 @section Group Score
2439 You would normally keep important groups on high levels, but that scheme
2440 is somewhat restrictive. Don't you wish you could have Gnus sort the
2441 group buffer according to how often you read groups, perhaps? Within
2444 This is what @dfn{group score} is for. You can have Gnus assign a score
2445 to each group through the mechanism described below. You can then sort
2446 the group buffer based on this score. Alternatively, you can sort on
2447 score and then level. (Taken together, the level and the score is
2448 called the @dfn{rank} of the group. A group that is on level 4 and has
2449 a score of 1 has a higher rank than a group on level 5 that has a score
2450 of 300. (The level is the most significant part and the score is the
2451 least significant part.))
2453 @findex gnus-summary-bubble-group
2454 If you want groups you read often to get higher scores than groups you
2455 read seldom you can add the @code{gnus-summary-bubble-group} function to
2456 the @code{gnus-summary-exit-hook} hook. This will result (after
2457 sorting) in a bubbling sort of action. If you want to see that in
2458 action after each summary exit, you can add
2459 @code{gnus-group-sort-groups-by-rank} or
2460 @code{gnus-group-sort-groups-by-score} to the same hook, but that will
2461 slow things down somewhat.
2464 @node Marking Groups
2465 @section Marking Groups
2466 @cindex marking groups
2468 If you want to perform some command on several groups, and they appear
2469 subsequently in the group buffer, you would normally just give a
2470 numerical prefix to the command. Most group commands will then do your
2471 bidding on those groups.
2473 However, if the groups are not in sequential order, you can still
2474 perform a command on several groups. You simply mark the groups first
2475 with the process mark and then execute the command.
2483 @findex gnus-group-mark-group
2484 Set the mark on the current group (@code{gnus-group-mark-group}).
2490 @findex gnus-group-unmark-group
2491 Remove the mark from the current group
2492 (@code{gnus-group-unmark-group}).
2496 @findex gnus-group-unmark-all-groups
2497 Remove the mark from all groups (@code{gnus-group-unmark-all-groups}).
2501 @findex gnus-group-mark-region
2502 Mark all groups between point and mark (@code{gnus-group-mark-region}).
2506 @findex gnus-group-mark-buffer
2507 Mark all groups in the buffer (@code{gnus-group-mark-buffer}).
2511 @findex gnus-group-mark-regexp
2512 Mark all groups that match some regular expression
2513 (@code{gnus-group-mark-regexp}).
2516 Also @pxref{Process/Prefix}.
2518 @findex gnus-group-universal-argument
2519 If you want to execute some command on all groups that have been marked
2520 with the process mark, you can use the @kbd{M-&}
2521 (@code{gnus-group-universal-argument}) command. It will prompt you for
2522 the command to be executed.
2525 @node Foreign Groups
2526 @section Foreign Groups
2527 @cindex foreign groups
2529 If you recall how to subscribe to servers (@pxref{Finding the News})
2530 you will remember that @code{gnus-secondary-select-methods} and
2531 @code{gnus-select-method} let you write a definition in Emacs Lisp of
2532 what servers you want to see when you start up. The alternate
2533 approach is to use foreign servers and groups. ``Foreign'' here means
2534 they are not coming from the select methods. All foreign server
2535 configuration and subscriptions are stored only in the
2536 @file{~/.newsrc.eld} file.
2538 Below are some group mode commands for making and editing general foreign
2539 groups, as well as commands to ease the creation of a few
2540 special-purpose groups. All these commands insert the newly created
2541 groups under point---@code{gnus-subscribe-newsgroup-method} is not
2544 Changes from the group editing commands are stored in
2545 @file{~/.newsrc.eld} (@code{gnus-startup-file}). An alternative is the
2546 variable @code{gnus-parameters}, @xref{Group Parameters}.
2552 @findex gnus-group-make-group
2553 @cindex making groups
2554 Make a new group (@code{gnus-group-make-group}). Gnus will prompt you
2555 for a name, a method and possibly an @dfn{address}. For an easier way
2556 to subscribe to @acronym{NNTP} groups (@pxref{Browse Foreign Server}).
2560 @findex gnus-group-read-ephemeral-group
2561 Make an ephemeral group (@code{gnus-group-read-ephemeral-group}). Gnus
2562 will prompt you for a name, a method and an @dfn{address}.
2566 @findex gnus-group-rename-group
2567 @cindex renaming groups
2568 Rename the current group to something else
2569 (@code{gnus-group-rename-group}). This is valid only on some
2570 groups---mail groups mostly. This command might very well be quite slow
2576 @findex gnus-group-customize
2577 Customize the group parameters (@code{gnus-group-customize}).
2581 @findex gnus-group-edit-group-method
2582 @cindex renaming groups
2583 Enter a buffer where you can edit the select method of the current
2584 group (@code{gnus-group-edit-group-method}).
2588 @findex gnus-group-edit-group-parameters
2589 Enter a buffer where you can edit the group parameters
2590 (@code{gnus-group-edit-group-parameters}).
2594 @findex gnus-group-edit-group
2595 Enter a buffer where you can edit the group info
2596 (@code{gnus-group-edit-group}).
2600 @findex gnus-group-make-directory-group
2602 Make a directory group (@pxref{Directory Groups}). You will be prompted
2603 for a directory name (@code{gnus-group-make-directory-group}).
2608 @findex gnus-group-make-help-group
2609 Make the Gnus help group (@code{gnus-group-make-help-group}).
2613 @findex gnus-group-enter-directory
2615 Read an arbitrary directory as if it were a newsgroup with the
2616 @code{nneething} back end (@code{gnus-group-enter-directory}).
2617 @xref{Anything Groups}.
2621 @findex gnus-group-make-doc-group
2622 @cindex ClariNet Briefs
2624 Make a group based on some file or other
2625 (@code{gnus-group-make-doc-group}). If you give a prefix to this
2626 command, you will be prompted for a file name and a file type.
2627 Currently supported types are @code{mbox}, @code{babyl},
2628 @code{digest}, @code{news}, @code{rnews}, @code{mmdf}, @code{forward},
2629 @code{rfc934}, @code{rfc822-forward}, @code{mime-parts},
2630 @code{standard-digest}, @code{slack-digest}, @code{clari-briefs},
2631 @code{nsmail}, @code{outlook}, @code{oe-dbx}, and @code{mailman}. If
2632 you run this command without a prefix, Gnus will guess at the file
2633 type. @xref{Document Groups}.
2637 @vindex gnus-useful-groups
2638 @findex gnus-group-make-useful-group
2639 Create one of the groups mentioned in @code{gnus-useful-groups}
2640 (@code{gnus-group-make-useful-group}).
2644 @findex gnus-group-make-web-group
2648 Make an ephemeral group based on a web search
2649 (@code{gnus-group-make-web-group}). If you give a prefix to this
2650 command, make a solid group instead. You will be prompted for the
2651 search engine type and the search string. Valid search engine types
2652 include @code{google}, @code{dejanews}, and @code{gmane}.
2653 @xref{Web Searches}.
2655 If you use the @code{google} search engine, you can limit the search
2656 to a particular group by using a match string like
2657 @samp{shaving group:alt.sysadmin.recovery}.
2661 @findex gnus-group-make-rss-group
2662 Make a group based on an @acronym{RSS} feed
2663 (@code{gnus-group-make-rss-group}). You will be prompted for an URL.
2667 @kindex G DEL (Group)
2668 @findex gnus-group-delete-group
2669 This function will delete the current group
2670 (@code{gnus-group-delete-group}). If given a prefix, this function will
2671 actually delete all the articles in the group, and forcibly remove the
2672 group itself from the face of the Earth. Use a prefix only if you are
2673 absolutely sure of what you are doing. This command can't be used on
2674 read-only groups (like @code{nntp} groups), though.
2678 @findex gnus-group-make-empty-virtual
2679 Make a new, fresh, empty @code{nnvirtual} group
2680 (@code{gnus-group-make-empty-virtual}). @xref{Virtual Groups}.
2684 @findex gnus-group-add-to-virtual
2685 Add the current group to an @code{nnvirtual} group
2686 (@code{gnus-group-add-to-virtual}). Uses the process/prefix convention.
2689 @xref{Select Methods}, for more information on the various select
2692 @vindex gnus-activate-foreign-newsgroups
2693 If @code{gnus-activate-foreign-newsgroups} is a positive number,
2694 Gnus will check all foreign groups with this level or lower at startup.
2695 This might take quite a while, especially if you subscribe to lots of
2696 groups from different @acronym{NNTP} servers. Also @pxref{Group Levels};
2697 @code{gnus-activate-level} also affects activation of foreign
2701 The following commands create ephemeral groups. They can be called not
2702 only from the Group buffer, but in any Gnus buffer.
2705 @item gnus-read-ephemeral-gmane-group
2706 @findex gnus-read-ephemeral-gmane-group
2707 @vindex gnus-gmane-group-download-format
2708 Read an ephemeral group on Gmane.org. The articles are downloaded via
2709 HTTP using the URL specified by @code{gnus-gmane-group-download-format}.
2710 Gnus will prompt you for a group name, the start article number and an
2713 @item gnus-read-ephemeral-gmane-group-url
2714 @findex gnus-read-ephemeral-gmane-group-url
2715 This command is similar to @code{gnus-read-ephemeral-gmane-group}, but
2716 the group name and the article number and range are constructed from a
2717 given @acronym{URL}. Supported @acronym{URL} formats include e.g.
2718 @url{http://thread.gmane.org/gmane.foo.bar/12300/focus=12399},
2719 @url{http://thread.gmane.org/gmane.foo.bar/12345/},
2720 @url{http://article.gmane.org/gmane.foo.bar/12345/},
2721 @url{http://permalink.gmane.org/gmane.foo.bar/12345/}, and
2722 @url{http://news.gmane.org/group/gmane.foo.bar/thread=12345}.
2724 @item gnus-read-ephemeral-emacs-bug-group
2725 @findex gnus-read-ephemeral-emacs-bug-group
2726 Read an Emacs bug report in an ephemeral group. Gnus will prompt for a
2727 bug number. The default is the number at point. The @acronym{URL} is
2728 specified in @code{gnus-bug-group-download-format-alist}.
2730 @item gnus-read-ephemeral-debian-bug-group
2731 @findex gnus-read-ephemeral-debian-bug-group
2732 Read a Debian bug report in an ephemeral group. Analog to
2733 @code{gnus-read-ephemeral-emacs-bug-group}.
2736 Some of these command are also useful for article buttons, @xref{Article
2744 '("#\\([0-9]+\\)\\>" 1
2745 (string-match "\\<emacs\\>" (or gnus-newsgroup-name ""))
2746 gnus-read-ephemeral-emacs-bug-group 1))
2750 @node Group Parameters
2751 @section Group Parameters
2752 @cindex group parameters
2754 The group parameters store information local to a particular group.
2756 Use the @kbd{G p} or the @kbd{G c} command to edit group parameters of a
2757 group. (@kbd{G p} presents you with a Lisp-based interface, @kbd{G c}
2758 presents you with a Customize-like interface. The latter helps avoid
2759 silly Lisp errors.) You might also be interested in reading about topic
2760 parameters (@pxref{Topic Parameters}).
2761 Additionally, you can set group parameters via the
2762 @code{gnus-parameters} variable, see below.
2764 Here's an example group parameter list:
2767 ((to-address . "ding@@gnus.org")
2771 We see that each element consists of a ``dotted pair''---the thing before
2772 the dot is the key, while the thing after the dot is the value. All the
2773 parameters have this form @emph{except} local variable specs, which are
2774 not dotted pairs, but proper lists.
2776 Some parameters have correspondent customizable variables, each of which
2777 is an alist of regexps and values.
2779 The following group parameters can be used:
2784 Address used by when doing followups and new posts.
2787 (to-address . "some@@where.com")
2790 This is primarily useful in mail groups that represent closed mailing
2791 lists---mailing lists where it's expected that everybody that writes to
2792 the mailing list is subscribed to it. Since using this parameter
2793 ensures that the mail only goes to the mailing list itself, it means
2794 that members won't receive two copies of your followups.
2796 Using @code{to-address} will actually work whether the group is foreign
2797 or not. Let's say there's a group on the server that is called
2798 @samp{fa.4ad-l}. This is a real newsgroup, but the server has gotten
2799 the articles from a mail-to-news gateway. Posting directly to this
2800 group is therefore impossible---you have to send mail to the mailing
2801 list address instead.
2803 See also @code{gnus-parameter-to-address-alist}.
2807 Address used when doing @kbd{a} in that group.
2810 (to-list . "some@@where.com")
2813 It is totally ignored
2814 when doing a followup---except that if it is present in a news group,
2815 you'll get mail group semantics when doing @kbd{f}.
2817 If you do an @kbd{a} command in a mail group and you have neither a
2818 @code{to-list} group parameter nor a @code{to-address} group parameter,
2819 then a @code{to-list} group parameter will be added automatically upon
2820 sending the message if @code{gnus-add-to-list} is set to @code{t}.
2821 @vindex gnus-add-to-list
2823 @findex gnus-mailing-list-mode
2824 @cindex mail list groups
2825 If this variable is set, @code{gnus-mailing-list-mode} is turned on when
2826 entering summary buffer.
2828 See also @code{gnus-parameter-to-list-alist}.
2833 @cindex Mail-Followup-To
2834 @findex gnus-find-subscribed-addresses
2835 If this parameter is set to @code{t}, Gnus will consider the
2836 to-address and to-list parameters for this group as addresses of
2837 mailing lists you are subscribed to. Giving Gnus this information is
2838 (only) a first step in getting it to generate correct Mail-Followup-To
2839 headers for your posts to these lists. The second step is to put the
2840 following in your @file{.gnus.el}
2843 (setq message-subscribed-address-functions
2844 '(gnus-find-subscribed-addresses))
2847 @xref{Mailing Lists, ,Mailing Lists, message, The Message Manual}, for
2848 a complete treatment of available MFT support.
2852 If the group parameter list has the element @code{(visible . t)},
2853 that group will always be visible in the Group buffer, regardless
2854 of whether it has any unread articles.
2856 This parameter cannot be set via @code{gnus-parameters}. See
2857 @code{gnus-permanently-visible-groups} as an alternative.
2859 @item broken-reply-to
2860 @cindex broken-reply-to
2861 Elements like @code{(broken-reply-to . t)} signals that @code{Reply-To}
2862 headers in this group are to be ignored, and for the header to be hidden
2863 if @code{reply-to} is part of @code{gnus-boring-article-headers}. This
2864 can be useful if you're reading a mailing list group where the listserv
2865 has inserted @code{Reply-To} headers that point back to the listserv
2866 itself. That is broken behavior. So there!
2870 Elements like @code{(to-group . "some.group.name")} means that all
2871 posts in that group will be sent to @code{some.group.name}.
2875 If you have @code{(newsgroup . t)} in the group parameter list, Gnus
2876 will treat all responses as if they were responses to news articles.
2877 This can be useful if you have a mail group that's really a mirror of a
2882 If @code{(gcc-self . t)} is present in the group parameter list, newly
2883 composed messages will be @code{Gcc}'d to the current group. If
2884 @code{(gcc-self . none)} is present, no @code{Gcc:} header will be
2885 generated, if @code{(gcc-self . "string")} is present, this string will
2886 be inserted literally as a @code{gcc} header. This parameter takes
2887 precedence over any default @code{Gcc} rules as described later
2888 (@pxref{Archived Messages}).
2890 @strong{Caveat}: Adding @code{(gcc-self . t)} to the parameter list of
2891 @code{nntp} groups (or the like) isn't valid. An @code{nntp} server
2892 doesn't accept articles.
2896 @cindex expiring mail
2897 If the group parameter has an element that looks like @code{(auto-expire
2898 . t)}, all articles read will be marked as expirable. For an
2899 alternative approach, @pxref{Expiring Mail}.
2901 See also @code{gnus-auto-expirable-newsgroups}.
2904 @cindex total-expire
2905 @cindex expiring mail
2906 If the group parameter has an element that looks like
2907 @code{(total-expire . t)}, all read articles will be put through the
2908 expiry process, even if they are not marked as expirable. Use with
2909 caution. Unread, ticked and dormant articles are not eligible for
2912 See also @code{gnus-total-expirable-newsgroups}.
2916 @vindex nnmail-expiry-wait-function
2917 If the group parameter has an element that looks like
2918 @code{(expiry-wait . 10)}, this value will override any
2919 @code{nnmail-expiry-wait} and @code{nnmail-expiry-wait-function}
2920 (@pxref{Expiring Mail}) when expiring expirable messages. The value
2921 can either be a number of days (not necessarily an integer) or the
2922 symbols @code{never} or @code{immediate}.
2925 @cindex expiry-target
2926 Where expired messages end up. This parameter overrides
2927 @code{nnmail-expiry-target}.
2930 @cindex score file group parameter
2931 Elements that look like @code{(score-file . "file")} will make
2932 @file{file} into the current score file for the group in question. All
2933 interactive score entries will be put into this file.
2936 @cindex adapt file group parameter
2937 Elements that look like @code{(adapt-file . "file")} will make
2938 @file{file} into the current adaptive file for the group in question.
2939 All adaptive score entries will be put into this file.
2942 @cindex admin-address
2943 When unsubscribing from a mailing list you should never send the
2944 unsubscription notice to the mailing list itself. Instead, you'd send
2945 messages to the administrative address. This parameter allows you to
2946 put the admin address somewhere convenient.
2950 Elements that look like @code{(display . MODE)} say which articles to
2951 display on entering the group. Valid values are:
2955 Display all articles, both read and unread.
2958 Display the last @var{integer} articles in the group. This is the same as
2959 entering the group with @kbd{C-u @var{integer}}.
2962 Display the default visible articles, which normally includes unread and
2966 Display articles that satisfy a predicate.
2968 Here are some examples:
2972 Display only unread articles.
2975 Display everything except expirable articles.
2977 @item [and (not reply) (not expire)]
2978 Display everything except expirable and articles you've already
2982 The available operators are @code{not}, @code{and} and @code{or}.
2983 Predicates include @code{tick}, @code{unsend}, @code{undownload},
2984 @code{unread}, @code{dormant}, @code{expire}, @code{reply},
2985 @code{killed}, @code{bookmark}, @code{score}, @code{save},
2986 @code{cache}, @code{forward}, and @code{unseen}.
2990 The @code{display} parameter works by limiting the summary buffer to
2991 the subset specified. You can pop the limit by using the @kbd{/ w}
2992 command (@pxref{Limiting}).
2996 Elements that look like @code{(comment . "This is a comment")} are
2997 arbitrary comments on the group. You can display comments in the
2998 group line (@pxref{Group Line Specification}).
3002 Elements that look like @code{(charset . iso-8859-1)} will make
3003 @code{iso-8859-1} the default charset; that is, the charset that will be
3004 used for all articles that do not specify a charset.
3006 See also @code{gnus-group-charset-alist}.
3008 @item ignored-charsets
3009 @cindex ignored-charset
3010 Elements that look like @code{(ignored-charsets x-unknown iso-8859-1)}
3011 will make @code{iso-8859-1} and @code{x-unknown} ignored; that is, the
3012 default charset will be used for decoding articles.
3014 See also @code{gnus-group-ignored-charsets-alist}.
3017 @cindex posting-style
3018 You can store additional posting style information for this group
3019 here (@pxref{Posting Styles}). The format is that of an entry in the
3020 @code{gnus-posting-styles} alist, except that there's no regexp matching
3021 the group name (of course). Style elements in this group parameter will
3022 take precedence over the ones found in @code{gnus-posting-styles}.
3024 For instance, if you want a funky name and signature in this group only,
3025 instead of hacking @code{gnus-posting-styles}, you could put something
3026 like this in the group parameters:
3031 ("X-My-Header" "Funky Value")
3032 (signature "Funky Signature"))
3035 If you're using topics to organize your group buffer
3036 (@pxref{Group Topics}), note that posting styles can also be set in
3037 the topics parameters. Posting styles in topic parameters apply to all
3038 groups in this topic. More precisely, the posting-style settings for a
3039 group result from the hierarchical merging of all posting-style
3040 entries in the parameters of this group and all the topics it belongs
3046 If it is set, the value is used as the method for posting message
3047 instead of @code{gnus-post-method}.
3051 If it is set, and the setting of @code{mail-sources} includes a
3052 @code{group} mail source (@pxref{Mail Sources}), the value is a
3053 mail source for this group.
3057 An item like @code{(banner . @var{regexp})} causes any part of an article
3058 that matches the regular expression @var{regexp} to be stripped. Instead of
3059 @var{regexp}, you can also use the symbol @code{signature} which strips the
3060 last signature or any of the elements of the alist
3061 @code{gnus-article-banner-alist}.
3065 This parameter contains a Sieve test that should match incoming mail
3066 that should be placed in this group. From this group parameter, a
3067 Sieve @samp{IF} control structure is generated, having the test as the
3068 condition and @samp{fileinto "group.name";} as the body.
3070 For example, if the @samp{INBOX.list.sieve} group has the @code{(sieve
3071 address "sender" "sieve-admin@@extundo.com")} group parameter, when
3072 translating the group parameter into a Sieve script (@pxref{Sieve
3073 Commands}) the following Sieve code is generated:
3076 if address "sender" "sieve-admin@@extundo.com" @{
3077 fileinto "INBOX.list.sieve";
3081 To generate tests for multiple email-addresses use a group parameter
3082 like @code{(sieve address "sender" ("name@@one.org" else@@two.org"))}.
3083 When generating a sieve script (@pxref{Sieve Commands}) Sieve code
3084 like the following is generated:
3087 if address "sender" ["name@@one.org", "else@@two.org"] @{
3088 fileinto "INBOX.list.sieve";
3092 See @pxref{Sieve Commands} for commands and variables that might be of
3093 interest in relation to the sieve parameter.
3095 The Sieve language is described in RFC 3028. @xref{Top, Emacs Sieve,
3096 Top, sieve, Emacs Sieve}.
3098 @item (agent parameters)
3099 If the agent has been enabled, you can set any of its parameters to
3100 control the behavior of the agent in individual groups. See Agent
3101 Parameters in @ref{Category Syntax}. Most users will choose to set
3102 agent parameters in either an agent category or group topic to
3103 minimize the configuration effort.
3105 @item (@var{variable} @var{form})
3106 You can use the group parameters to set variables local to the group you
3107 are entering. If you want to turn threading off in @samp{news.answers},
3108 you could put @code{(gnus-show-threads nil)} in the group parameters of
3109 that group. @code{gnus-show-threads} will be made into a local variable
3110 in the summary buffer you enter, and the form @code{nil} will be
3111 @code{eval}ed there.
3113 Note that this feature sets the variable locally to the summary buffer
3114 if and only if @var{variable} has been bound as a variable. Otherwise,
3115 only evaluating the form will take place. So, you may want to bind the
3116 variable in advance using @code{defvar} or other if the result of the
3117 form needs to be set to it.
3119 But some variables are evaluated in the article buffer, or in the
3120 message buffer (of a reply or followup or otherwise newly created
3121 message). As a workaround, it might help to add the variable in
3122 question to @code{gnus-newsgroup-variables}. @xref{Various Summary
3123 Stuff}. So if you want to set @code{message-from-style} via the group
3124 parameters, then you may need the following statement elsewhere in your
3125 @file{~/.gnus.el} file:
3128 (add-to-list 'gnus-newsgroup-variables 'message-from-style)
3131 @vindex gnus-list-identifiers
3132 A use for this feature is to remove a mailing list identifier tag in
3133 the subject fields of articles. E.g. if the news group
3136 nntp+news.gnus.org:gmane.text.docbook.apps
3139 has the tag @samp{DOC-BOOK-APPS:} in the subject of all articles, this
3140 tag can be removed from the article subjects in the summary buffer for
3141 the group by putting @code{(gnus-list-identifiers "DOCBOOK-APPS:")}
3142 into the group parameters for the group.
3144 This can also be used as a group-specific hook function. If you want to
3145 hear a beep when you enter a group, you could put something like
3146 @code{(dummy-variable (ding))} in the parameters of that group. If
3147 @code{dummy-variable} has been bound (see above), it will be set to the
3148 (meaningless) result of the @code{(ding)} form.
3150 Alternatively, since the VARIABLE becomes local to the group, this
3151 pattern can be used to temporarily change a hook. For example, if the
3152 following is added to a group parameter
3155 (gnus-summary-prepared-hook
3156 '(lambda nil (local-set-key "d" (local-key-binding "n"))))
3159 when the group is entered, the 'd' key will not mark the article as
3164 @vindex gnus-parameters
3165 Group parameters can be set via the @code{gnus-parameters} variable too.
3166 But some variables, such as @code{visible}, have no effect (For this
3167 case see @code{gnus-permanently-visible-groups} as an alternative.).
3171 (setq gnus-parameters
3173 (gnus-show-threads nil)
3174 (gnus-use-scoring nil)
3175 (gnus-summary-line-format
3176 "%U%R%z%I%(%[%d:%ub%-23,23f%]%) %s\n")
3180 ("^nnimap:\\(foo.bar\\)$"
3184 (gnus-use-scoring t))
3188 (broken-reply-to . t))))
3191 All clauses that matches the group name will be used, but the last
3192 setting ``wins''. So if you have two clauses that both match the
3193 group name, and both set, say @code{display}, the last setting will
3196 Parameters that are strings will be subjected to regexp substitution,
3197 as the @code{to-group} example shows.
3199 @vindex gnus-parameters-case-fold-search
3200 By default, whether comparing the group name and one of those regexps
3201 specified in @code{gnus-parameters} is done in a case-sensitive manner
3202 or a case-insensitive manner depends on the value of
3203 @code{case-fold-search} at the time when the comparison is done. The
3204 value of @code{case-fold-search} is typically @code{t}; it means, for
3205 example, the element @code{("INBOX\\.FOO" (total-expire . t))} might be
3206 applied to both the @samp{INBOX.FOO} group and the @samp{INBOX.foo}
3207 group. If you want to make those regexps always case-sensitive, set the
3208 value of the @code{gnus-parameters-case-fold-search} variable to
3209 @code{nil}. Otherwise, set it to @code{t} if you want to compare them
3210 always in a case-insensitive manner.
3212 You can define different sorting to different groups via
3213 @code{gnus-parameters}. Here is an example to sort an @acronym{NNTP}
3214 group by reverse date to see the latest news at the top and an
3215 @acronym{RSS} group by subject. In this example, the first group is the
3216 Debian daily news group @code{gmane.linux.debian.user.news} from
3217 news.gmane.org. The @acronym{RSS} group corresponds to the Debian
3218 weekly news RSS feed
3219 @url{http://packages.debian.org/unstable/newpkg_main.en.rdf},
3225 '(("nntp.*gmane\\.debian\\.user\\.news"
3226 (gnus-show-threads nil)
3227 (gnus-article-sort-functions '((not gnus-article-sort-by-date)))
3228 (gnus-use-adaptive-scoring nil)
3229 (gnus-use-scoring nil))
3231 (gnus-show-threads nil)
3232 (gnus-article-sort-functions 'gnus-article-sort-by-subject)
3233 (gnus-use-adaptive-scoring nil)
3234 (gnus-use-scoring t)
3235 (gnus-score-find-score-files-function 'gnus-score-find-single)
3236 (gnus-summary-line-format "%U%R%z%d %I%(%[ %s %]%)\n"))))
3240 @node Listing Groups
3241 @section Listing Groups
3242 @cindex group listing
3244 These commands all list various slices of the groups available.
3252 @findex gnus-group-list-groups
3253 List all groups that have unread articles
3254 (@code{gnus-group-list-groups}). If the numeric prefix is used, this
3255 command will list only groups of level ARG and lower. By default, it
3256 only lists groups of level five (i.e.,
3257 @code{gnus-group-default-list-level}) or lower (i.e., just subscribed
3264 @findex gnus-group-list-all-groups
3265 List all groups, whether they have unread articles or not
3266 (@code{gnus-group-list-all-groups}). If the numeric prefix is used,
3267 this command will list only groups of level ARG and lower. By default,
3268 it lists groups of level seven or lower (i.e., just subscribed and
3269 unsubscribed groups).
3273 @findex gnus-group-list-level
3274 List all unread groups on a specific level
3275 (@code{gnus-group-list-level}). If given a prefix, also list the groups
3276 with no unread articles.
3280 @findex gnus-group-list-killed
3281 List all killed groups (@code{gnus-group-list-killed}). If given a
3282 prefix argument, really list all groups that are available, but aren't
3283 currently (un)subscribed. This could entail reading the active file
3288 @findex gnus-group-list-zombies
3289 List all zombie groups (@code{gnus-group-list-zombies}).
3293 @findex gnus-group-list-matching
3294 List all unread, subscribed groups with names that match a regexp
3295 (@code{gnus-group-list-matching}).
3299 @findex gnus-group-list-all-matching
3300 List groups that match a regexp (@code{gnus-group-list-all-matching}).
3304 @findex gnus-group-list-active
3305 List absolutely all groups in the active file(s) of the
3306 server(s) you are connected to (@code{gnus-group-list-active}). This
3307 might very well take quite a while. It might actually be a better idea
3308 to do a @kbd{A M} to list all matching, and just give @samp{.} as the
3309 thing to match on. Also note that this command may list groups that
3310 don't exist (yet)---these will be listed as if they were killed groups.
3311 Take the output with some grains of salt.
3315 @findex gnus-group-apropos
3316 List all groups that have names that match a regexp
3317 (@code{gnus-group-apropos}).
3321 @findex gnus-group-description-apropos
3322 List all groups that have names or descriptions that match a regexp
3323 (@code{gnus-group-description-apropos}).
3327 @findex gnus-group-list-cached
3328 List all groups with cached articles (@code{gnus-group-list-cached}).
3332 @findex gnus-group-list-dormant
3333 List all groups with dormant articles (@code{gnus-group-list-dormant}).
3337 @findex gnus-group-list-ticked
3338 List all groups with ticked articles (@code{gnus-group-list-ticked}).
3342 @findex gnus-group-list-limit
3343 Further limit groups within the current selection
3344 (@code{gnus-group-list-limit}). If you've first limited to groups
3345 with dormant articles with @kbd{A ?}, you can then further limit with
3346 @kbd{A / c}, which will then limit to groups with cached articles,
3347 giving you the groups that have both dormant articles and cached
3352 @findex gnus-group-list-flush
3353 Flush groups from the current selection (@code{gnus-group-list-flush}).
3357 @findex gnus-group-list-plus
3358 List groups plus the current selection (@code{gnus-group-list-plus}).
3362 @vindex gnus-permanently-visible-groups
3363 @cindex visible group parameter
3364 Groups that match the @code{gnus-permanently-visible-groups} regexp will
3365 always be shown, whether they have unread articles or not. You can also
3366 add the @code{visible} element to the group parameters in question to
3367 get the same effect.
3369 @vindex gnus-list-groups-with-ticked-articles
3370 Groups that have just ticked articles in it are normally listed in the
3371 group buffer. If @code{gnus-list-groups-with-ticked-articles} is
3372 @code{nil}, these groups will be treated just like totally empty
3373 groups. It is @code{t} by default.
3376 @node Sorting Groups
3377 @section Sorting Groups
3378 @cindex sorting groups
3380 @kindex C-c C-s (Group)
3381 @findex gnus-group-sort-groups
3382 @vindex gnus-group-sort-function
3383 The @kbd{C-c C-s} (@code{gnus-group-sort-groups}) command sorts the
3384 group buffer according to the function(s) given by the
3385 @code{gnus-group-sort-function} variable. Available sorting functions
3390 @item gnus-group-sort-by-alphabet
3391 @findex gnus-group-sort-by-alphabet
3392 Sort the group names alphabetically. This is the default.
3394 @item gnus-group-sort-by-real-name
3395 @findex gnus-group-sort-by-real-name
3396 Sort the group alphabetically on the real (unprefixed) group names.
3398 @item gnus-group-sort-by-level
3399 @findex gnus-group-sort-by-level
3400 Sort by group level.
3402 @item gnus-group-sort-by-score
3403 @findex gnus-group-sort-by-score
3404 Sort by group score. @xref{Group Score}.
3406 @item gnus-group-sort-by-rank
3407 @findex gnus-group-sort-by-rank
3408 Sort by group score and then the group level. The level and the score
3409 are, when taken together, the group's @dfn{rank}. @xref{Group Score}.
3411 @item gnus-group-sort-by-unread
3412 @findex gnus-group-sort-by-unread
3413 Sort by number of unread articles.
3415 @item gnus-group-sort-by-method
3416 @findex gnus-group-sort-by-method
3417 Sort alphabetically on the select method.
3419 @item gnus-group-sort-by-server
3420 @findex gnus-group-sort-by-server
3421 Sort alphabetically on the Gnus server name.
3426 @code{gnus-group-sort-function} can also be a list of sorting
3427 functions. In that case, the most significant sort key function must be
3431 There are also a number of commands for sorting directly according to
3432 some sorting criteria:
3436 @kindex G S a (Group)
3437 @findex gnus-group-sort-groups-by-alphabet
3438 Sort the group buffer alphabetically by group name
3439 (@code{gnus-group-sort-groups-by-alphabet}).
3442 @kindex G S u (Group)
3443 @findex gnus-group-sort-groups-by-unread
3444 Sort the group buffer by the number of unread articles
3445 (@code{gnus-group-sort-groups-by-unread}).
3448 @kindex G S l (Group)
3449 @findex gnus-group-sort-groups-by-level
3450 Sort the group buffer by group level
3451 (@code{gnus-group-sort-groups-by-level}).
3454 @kindex G S v (Group)
3455 @findex gnus-group-sort-groups-by-score
3456 Sort the group buffer by group score
3457 (@code{gnus-group-sort-groups-by-score}). @xref{Group Score}.
3460 @kindex G S r (Group)
3461 @findex gnus-group-sort-groups-by-rank
3462 Sort the group buffer by group rank
3463 (@code{gnus-group-sort-groups-by-rank}). @xref{Group Score}.
3466 @kindex G S m (Group)
3467 @findex gnus-group-sort-groups-by-method
3468 Sort the group buffer alphabetically by back end name@*
3469 (@code{gnus-group-sort-groups-by-method}).
3472 @kindex G S n (Group)
3473 @findex gnus-group-sort-groups-by-real-name
3474 Sort the group buffer alphabetically by real (unprefixed) group name
3475 (@code{gnus-group-sort-groups-by-real-name}).
3479 All the commands below obey the process/prefix convention
3480 (@pxref{Process/Prefix}).
3482 When given a symbolic prefix (@pxref{Symbolic Prefixes}), all these
3483 commands will sort in reverse order.
3485 You can also sort a subset of the groups:
3489 @kindex G P a (Group)
3490 @findex gnus-group-sort-selected-groups-by-alphabet
3491 Sort the groups alphabetically by group name
3492 (@code{gnus-group-sort-selected-groups-by-alphabet}).
3495 @kindex G P u (Group)
3496 @findex gnus-group-sort-selected-groups-by-unread
3497 Sort the groups by the number of unread articles
3498 (@code{gnus-group-sort-selected-groups-by-unread}).
3501 @kindex G P l (Group)
3502 @findex gnus-group-sort-selected-groups-by-level
3503 Sort the groups by group level
3504 (@code{gnus-group-sort-selected-groups-by-level}).
3507 @kindex G P v (Group)
3508 @findex gnus-group-sort-selected-groups-by-score
3509 Sort the groups by group score
3510 (@code{gnus-group-sort-selected-groups-by-score}). @xref{Group Score}.
3513 @kindex G P r (Group)
3514 @findex gnus-group-sort-selected-groups-by-rank
3515 Sort the groups by group rank
3516 (@code{gnus-group-sort-selected-groups-by-rank}). @xref{Group Score}.
3519 @kindex G P m (Group)
3520 @findex gnus-group-sort-selected-groups-by-method
3521 Sort the groups alphabetically by back end name@*
3522 (@code{gnus-group-sort-selected-groups-by-method}).
3525 @kindex G P n (Group)
3526 @findex gnus-group-sort-selected-groups-by-real-name
3527 Sort the groups alphabetically by real (unprefixed) group name
3528 (@code{gnus-group-sort-selected-groups-by-real-name}).
3531 @kindex G P s (Group)
3532 @findex gnus-group-sort-selected-groups
3533 Sort the groups according to @code{gnus-group-sort-function}.
3537 And finally, note that you can use @kbd{C-k} and @kbd{C-y} to manually
3541 @node Group Maintenance
3542 @section Group Maintenance
3543 @cindex bogus groups
3548 @findex gnus-group-check-bogus-groups
3549 Find bogus groups and delete them
3550 (@code{gnus-group-check-bogus-groups}).
3554 @findex gnus-group-find-new-groups
3555 Find new groups and process them (@code{gnus-group-find-new-groups}).
3556 With 1 @kbd{C-u}, use the @code{ask-server} method to query the server
3557 for new groups. With 2 @kbd{C-u}'s, use most complete method possible
3558 to query the server for new groups, and subscribe the new groups as
3562 @kindex C-c C-x (Group)
3563 @findex gnus-group-expire-articles
3564 @cindex expiring mail
3565 Run all expirable articles in the current group through the expiry
3566 process (if any) (@code{gnus-group-expire-articles}). That is, delete
3567 all expirable articles in the group that have been around for a while.
3568 (@pxref{Expiring Mail}).
3571 @kindex C-c C-M-x (Group)
3572 @findex gnus-group-expire-all-groups
3573 @cindex expiring mail
3574 Run all expirable articles in all groups through the expiry process
3575 (@code{gnus-group-expire-all-groups}).
3580 @node Browse Foreign Server
3581 @section Browse Foreign Server
3582 @cindex foreign servers
3583 @cindex browsing servers
3588 @findex gnus-group-browse-foreign-server
3589 You will be queried for a select method and a server name. Gnus will
3590 then attempt to contact this server and let you browse the groups there
3591 (@code{gnus-group-browse-foreign-server}).
3594 @findex gnus-browse-mode
3595 A new buffer with a list of available groups will appear. This buffer
3596 will use the @code{gnus-browse-mode}. This buffer looks a bit (well,
3597 a lot) like a normal group buffer.
3599 Here's a list of keystrokes available in the browse mode:
3604 @findex gnus-group-next-group
3605 Go to the next group (@code{gnus-group-next-group}).
3609 @findex gnus-group-prev-group
3610 Go to the previous group (@code{gnus-group-prev-group}).
3613 @kindex SPACE (Browse)
3614 @findex gnus-browse-read-group
3615 Enter the current group and display the first article
3616 (@code{gnus-browse-read-group}).
3619 @kindex RET (Browse)
3620 @findex gnus-browse-select-group
3621 Enter the current group (@code{gnus-browse-select-group}).
3625 @findex gnus-browse-unsubscribe-current-group
3626 @vindex gnus-browse-subscribe-newsgroup-method
3627 Unsubscribe to the current group, or, as will be the case here,
3628 subscribe to it (@code{gnus-browse-unsubscribe-current-group}). You
3629 can affect the way the new group is entered into the Group buffer
3630 using the variable @code{gnus-browse-subscribe-newsgroup-method}. See
3631 @pxref{Subscription Methods} for available options.
3637 @findex gnus-browse-exit
3638 Exit browse mode (@code{gnus-browse-exit}).
3642 @findex gnus-browse-describe-group
3643 Describe the current group (@code{gnus-browse-describe-group}).
3647 @findex gnus-browse-describe-briefly
3648 Describe browse mode briefly (well, there's not much to describe, is
3649 there) (@code{gnus-browse-describe-briefly}).
3654 @section Exiting Gnus
3655 @cindex exiting Gnus
3657 Yes, Gnus is ex(c)iting.
3662 @findex gnus-group-suspend
3663 Suspend Gnus (@code{gnus-group-suspend}). This doesn't really exit Gnus,
3664 but it kills all buffers except the Group buffer. I'm not sure why this
3665 is a gain, but then who am I to judge?
3669 @findex gnus-group-exit
3670 @c @icon{gnus-group-exit}
3671 Quit Gnus (@code{gnus-group-exit}).
3675 @findex gnus-group-quit
3676 Quit Gnus without saving the @file{.newsrc} files (@code{gnus-group-quit}).
3677 The dribble file will be saved, though (@pxref{Auto Save}).
3680 @vindex gnus-exit-gnus-hook
3681 @vindex gnus-suspend-gnus-hook
3682 @vindex gnus-after-exiting-gnus-hook
3683 @code{gnus-suspend-gnus-hook} is called when you suspend Gnus and
3684 @code{gnus-exit-gnus-hook} is called when you quit Gnus, while
3685 @code{gnus-after-exiting-gnus-hook} is called as the final item when
3691 Miss Lisa Cannifax, while sitting in English class, felt her feet go
3692 numbly heavy and herself fall into a hazy trance as the boy sitting
3693 behind her drew repeated lines with his pencil across the back of her
3699 @section Group Topics
3702 If you read lots and lots of groups, it might be convenient to group
3703 them hierarchically according to topics. You put your Emacs groups over
3704 here, your sex groups over there, and the rest (what, two groups or so?)
3705 you put in some misc section that you never bother with anyway. You can
3706 even group the Emacs sex groups as a sub-topic to either the Emacs
3707 groups or the sex groups---or both! Go wild!
3711 \gnusfigure{Group Topics}{400}{
3712 \put(75,50){\epsfig{figure=ps/group-topic,height=9cm}}
3723 2: alt.religion.emacs
3726 0: comp.talk.emacs.recovery
3728 8: comp.binaries.fractals
3729 13: comp.sources.unix
3732 @findex gnus-topic-mode
3734 To get this @emph{fab} functionality you simply turn on (ooh!) the
3735 @code{gnus-topic} minor mode---type @kbd{t} in the group buffer. (This
3736 is a toggling command.)
3738 Go ahead, just try it. I'll still be here when you get back. La de
3739 dum@dots{} Nice tune, that@dots{} la la la@dots{} What, you're back?
3740 Yes, and now press @kbd{l}. There. All your groups are now listed
3741 under @samp{misc}. Doesn't that make you feel all warm and fuzzy?
3744 If you want this permanently enabled, you should add that minor mode to
3745 the hook for the group mode. Put the following line in your
3746 @file{~/.gnus.el} file:
3749 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
3753 * Topic Commands:: Interactive E-Z commands.
3754 * Topic Variables:: How to customize the topics the Lisp Way.
3755 * Topic Sorting:: Sorting each topic individually.
3756 * Topic Topology:: A map of the world.
3757 * Topic Parameters:: Parameters that apply to all groups in a topic.
3761 @node Topic Commands
3762 @subsection Topic Commands
3763 @cindex topic commands
3765 When the topic minor mode is turned on, a new @kbd{T} submap will be
3766 available. In addition, a few of the standard keys change their
3767 definitions slightly.
3769 In general, the following kinds of operations are possible on topics.
3770 First of all, you want to create topics. Secondly, you want to put
3771 groups in topics and to move them around until you have an order you
3772 like. The third kind of operation is to show/hide parts of the whole
3773 shebang. You might want to hide a topic including its subtopics and
3774 groups, to get a better overview of the other groups.
3776 Here is a list of the basic keys that you might need to set up topics
3783 @findex gnus-topic-create-topic
3784 Prompt for a new topic name and create it
3785 (@code{gnus-topic-create-topic}).
3789 @kindex T TAB (Topic)
3791 @findex gnus-topic-indent
3792 ``Indent'' the current topic so that it becomes a sub-topic of the
3793 previous topic (@code{gnus-topic-indent}). If given a prefix,
3794 ``un-indent'' the topic instead.
3797 @kindex M-TAB (Topic)
3798 @findex gnus-topic-unindent
3799 ``Un-indent'' the current topic so that it becomes a sub-topic of the
3800 parent of its current parent (@code{gnus-topic-unindent}).
3804 The following two keys can be used to move groups and topics around.
3805 They work like the well-known cut and paste. @kbd{C-k} is like cut and
3806 @kbd{C-y} is like paste. Of course, this being Emacs, we use the terms
3807 kill and yank rather than cut and paste.
3813 @findex gnus-topic-kill-group
3814 Kill a group or topic (@code{gnus-topic-kill-group}). All groups in the
3815 topic will be removed along with the topic.
3819 @findex gnus-topic-yank-group
3820 Yank the previously killed group or topic
3821 (@code{gnus-topic-yank-group}). Note that all topics will be yanked
3824 So, to move a topic to the beginning of the list of topics, just hit
3825 @kbd{C-k} on it. This is like the ``cut'' part of cut and paste. Then,
3826 move the cursor to the beginning of the buffer (just below the ``Gnus''
3827 topic) and hit @kbd{C-y}. This is like the ``paste'' part of cut and
3828 paste. Like I said -- E-Z.
3830 You can use @kbd{C-k} and @kbd{C-y} on groups as well as on topics. So
3831 you can move topics around as well as groups.
3835 After setting up the topics the way you like them, you might wish to
3836 hide a topic, or to show it again. That's why we have the following
3843 @findex gnus-topic-select-group
3845 Either select a group or fold a topic (@code{gnus-topic-select-group}).
3846 When you perform this command on a group, you'll enter the group, as
3847 usual. When done on a topic line, the topic will be folded (if it was
3848 visible) or unfolded (if it was folded already). So it's basically a
3849 toggling command on topics. In addition, if you give a numerical
3850 prefix, group on that level (and lower) will be displayed.
3854 Now for a list of other commands, in no particular order.
3860 @findex gnus-topic-move-group
3861 Move the current group to some other topic
3862 (@code{gnus-topic-move-group}). This command uses the process/prefix
3863 convention (@pxref{Process/Prefix}).
3867 @findex gnus-topic-jump-to-topic
3868 Go to a topic (@code{gnus-topic-jump-to-topic}).
3872 @findex gnus-topic-copy-group
3873 Copy the current group to some other topic
3874 (@code{gnus-topic-copy-group}). This command uses the process/prefix
3875 convention (@pxref{Process/Prefix}).
3879 @findex gnus-topic-hide-topic
3880 Hide the current topic (@code{gnus-topic-hide-topic}). If given
3881 a prefix, hide the topic permanently.
3885 @findex gnus-topic-show-topic
3886 Show the current topic (@code{gnus-topic-show-topic}). If given
3887 a prefix, show the topic permanently.
3891 @findex gnus-topic-remove-group
3892 Remove a group from the current topic (@code{gnus-topic-remove-group}).
3893 This command is mainly useful if you have the same group in several
3894 topics and wish to remove it from one of the topics. You may also
3895 remove a group from all topics, but in that case, Gnus will add it to
3896 the root topic the next time you start Gnus. In fact, all new groups
3897 (which, naturally, don't belong to any topic) will show up in the root
3900 This command uses the process/prefix convention
3901 (@pxref{Process/Prefix}).
3905 @findex gnus-topic-move-matching
3906 Move all groups that match some regular expression to a topic
3907 (@code{gnus-topic-move-matching}).
3911 @findex gnus-topic-copy-matching
3912 Copy all groups that match some regular expression to a topic
3913 (@code{gnus-topic-copy-matching}).
3917 @findex gnus-topic-toggle-display-empty-topics
3918 Toggle hiding empty topics
3919 (@code{gnus-topic-toggle-display-empty-topics}).
3923 @findex gnus-topic-mark-topic
3924 Mark all groups in the current topic with the process mark
3925 (@code{gnus-topic-mark-topic}). This command works recursively on
3926 sub-topics unless given a prefix.
3929 @kindex T M-# (Topic)
3930 @findex gnus-topic-unmark-topic
3931 Remove the process mark from all groups in the current topic
3932 (@code{gnus-topic-unmark-topic}). This command works recursively on
3933 sub-topics unless given a prefix.
3936 @kindex C-c C-x (Topic)
3937 @findex gnus-topic-expire-articles
3938 @cindex expiring mail
3939 Run all expirable articles in the current group or topic through the
3940 expiry process (if any)
3941 (@code{gnus-topic-expire-articles}). (@pxref{Expiring Mail}).
3945 @findex gnus-topic-rename
3946 Rename a topic (@code{gnus-topic-rename}).
3949 @kindex T DEL (Topic)
3950 @findex gnus-topic-delete
3951 Delete an empty topic (@code{gnus-topic-delete}).
3955 @findex gnus-topic-list-active
3956 List all groups that Gnus knows about in a topics-ified way
3957 (@code{gnus-topic-list-active}).
3960 @kindex T M-n (Topic)
3961 @findex gnus-topic-goto-next-topic
3962 Go to the next topic (@code{gnus-topic-goto-next-topic}).
3965 @kindex T M-p (Topic)
3966 @findex gnus-topic-goto-previous-topic
3967 Go to the previous topic (@code{gnus-topic-goto-previous-topic}).
3971 @findex gnus-topic-edit-parameters
3972 @cindex group parameters
3973 @cindex topic parameters
3975 Edit the topic parameters (@code{gnus-topic-edit-parameters}).
3976 @xref{Topic Parameters}.
3981 @node Topic Variables
3982 @subsection Topic Variables
3983 @cindex topic variables
3985 The previous section told you how to tell Gnus which topics to display.
3986 This section explains how to tell Gnus what to display about each topic.
3988 @vindex gnus-topic-line-format
3989 The topic lines themselves are created according to the
3990 @code{gnus-topic-line-format} variable (@pxref{Formatting Variables}).
4003 Number of groups in the topic.
4005 Number of unread articles in the topic.
4007 Number of unread articles in the topic and all its subtopics.
4010 @vindex gnus-topic-indent-level
4011 Each sub-topic (and the groups in the sub-topics) will be indented with
4012 @code{gnus-topic-indent-level} times the topic level number of spaces.
4015 @vindex gnus-topic-mode-hook
4016 @code{gnus-topic-mode-hook} is called in topic minor mode buffers.
4018 @vindex gnus-topic-display-empty-topics
4019 The @code{gnus-topic-display-empty-topics} says whether to display even
4020 topics that have no unread articles in them. The default is @code{t}.
4024 @subsection Topic Sorting
4025 @cindex topic sorting
4027 You can sort the groups in each topic individually with the following
4033 @kindex T S a (Topic)
4034 @findex gnus-topic-sort-groups-by-alphabet
4035 Sort the current topic alphabetically by group name
4036 (@code{gnus-topic-sort-groups-by-alphabet}).
4039 @kindex T S u (Topic)
4040 @findex gnus-topic-sort-groups-by-unread
4041 Sort the current topic by the number of unread articles
4042 (@code{gnus-topic-sort-groups-by-unread}).
4045 @kindex T S l (Topic)
4046 @findex gnus-topic-sort-groups-by-level
4047 Sort the current topic by group level
4048 (@code{gnus-topic-sort-groups-by-level}).
4051 @kindex T S v (Topic)
4052 @findex gnus-topic-sort-groups-by-score
4053 Sort the current topic by group score
4054 (@code{gnus-topic-sort-groups-by-score}). @xref{Group Score}.
4057 @kindex T S r (Topic)
4058 @findex gnus-topic-sort-groups-by-rank
4059 Sort the current topic by group rank
4060 (@code{gnus-topic-sort-groups-by-rank}). @xref{Group Score}.
4063 @kindex T S m (Topic)
4064 @findex gnus-topic-sort-groups-by-method
4065 Sort the current topic alphabetically by back end name
4066 (@code{gnus-topic-sort-groups-by-method}).
4069 @kindex T S e (Topic)
4070 @findex gnus-topic-sort-groups-by-server
4071 Sort the current topic alphabetically by server name
4072 (@code{gnus-topic-sort-groups-by-server}).
4075 @kindex T S s (Topic)
4076 @findex gnus-topic-sort-groups
4077 Sort the current topic according to the function(s) given by the
4078 @code{gnus-group-sort-function} variable
4079 (@code{gnus-topic-sort-groups}).
4083 When given a prefix argument, all these commands will sort in reverse
4084 order. @xref{Sorting Groups}, for more information about group
4088 @node Topic Topology
4089 @subsection Topic Topology
4090 @cindex topic topology
4093 So, let's have a look at an example group buffer:
4100 2: alt.religion.emacs
4103 0: comp.talk.emacs.recovery
4105 8: comp.binaries.fractals
4106 13: comp.sources.unix
4110 So, here we have one top-level topic (@samp{Gnus}), two topics under
4111 that, and one sub-topic under one of the sub-topics. (There is always
4112 just one (1) top-level topic). This topology can be expressed as
4117 (("Emacs -- I wuw it!" visible)
4118 (("Naughty Emacs" visible)))
4122 @vindex gnus-topic-topology
4123 This is in fact how the variable @code{gnus-topic-topology} would look
4124 for the display above. That variable is saved in the @file{.newsrc.eld}
4125 file, and shouldn't be messed with manually---unless you really want
4126 to. Since this variable is read from the @file{.newsrc.eld} file,
4127 setting it in any other startup files will have no effect.
4129 This topology shows what topics are sub-topics of what topics (right),
4130 and which topics are visible. Two settings are currently
4131 allowed---@code{visible} and @code{invisible}.
4134 @node Topic Parameters
4135 @subsection Topic Parameters
4136 @cindex topic parameters
4138 All groups in a topic will inherit group parameters from the parent
4139 (and ancestor) topic parameters. All valid group parameters are valid
4140 topic parameters (@pxref{Group Parameters}). When the agent is
4141 enabled, all agent parameters (See Agent Parameters in @ref{Category
4142 Syntax}) are also valid topic parameters.
4144 In addition, the following parameters are only valid as topic
4149 When subscribing new groups by topic (@pxref{Subscription Methods}), the
4150 @code{subscribe} topic parameter says what groups go in what topic. Its
4151 value should be a regexp to match the groups that should go in that
4154 @item subscribe-level
4155 When subscribing new groups by topic (see the @code{subscribe} parameter),
4156 the group will be subscribed with the level specified in the
4157 @code{subscribe-level} instead of @code{gnus-level-default-subscribed}.
4161 Group parameters (of course) override topic parameters, and topic
4162 parameters in sub-topics override topic parameters in super-topics. You
4163 know. Normal inheritance rules. (@dfn{Rules} is here a noun, not a
4164 verb, although you may feel free to disagree with me here.)
4171 2: alt.religion.emacs
4175 0: comp.talk.emacs.recovery
4177 8: comp.binaries.fractals
4178 13: comp.sources.unix
4183 The @samp{Emacs} topic has the topic parameter @code{(score-file
4184 . "emacs.SCORE")}; the @samp{Relief} topic has the topic parameter
4185 @code{(score-file . "relief.SCORE")}; and the @samp{Misc} topic has the
4186 topic parameter @code{(score-file . "emacs.SCORE")}. In addition,
4187 @* @samp{alt.religion.emacs} has the group parameter @code{(score-file
4188 . "religion.SCORE")}.
4190 Now, when you enter @samp{alt.sex.emacs} in the @samp{Relief} topic, you
4191 will get the @file{relief.SCORE} home score file. If you enter the same
4192 group in the @samp{Emacs} topic, you'll get the @file{emacs.SCORE} home
4193 score file. If you enter the group @samp{alt.religion.emacs}, you'll
4194 get the @file{religion.SCORE} home score file.
4196 This seems rather simple and self-evident, doesn't it? Well, yes. But
4197 there are some problems, especially with the @code{total-expiry}
4198 parameter. Say you have a mail group in two topics; one with
4199 @code{total-expiry} and one without. What happens when you do @kbd{M-x
4200 gnus-expire-all-expirable-groups}? Gnus has no way of telling which one
4201 of these topics you mean to expire articles from, so anything may
4202 happen. In fact, I hereby declare that it is @dfn{undefined} what
4203 happens. You just have to be careful if you do stuff like that.
4206 @node Non-ASCII Group Names
4207 @section Accessing groups of non-English names
4208 @cindex non-ascii group names
4210 There are some news servers that provide groups of which the names are
4211 expressed with their native languages in the world. For instance, in a
4212 certain news server there are some newsgroups of which the names are
4213 spelled in Chinese, where people are talking in Chinese. You can, of
4214 course, subscribe to such news groups using Gnus. Currently Gnus
4215 supports non-@acronym{ASCII} group names not only with the @code{nntp}
4216 back end but also with the @code{nnml} back end and the @code{nnrss}
4219 Every such group name is encoded by a certain charset in the server
4220 side (in an @acronym{NNTP} server its administrator determines the
4221 charset, but for groups in the other back ends it is determined by you).
4222 Gnus has to display the decoded ones for you in the group buffer and the
4223 article buffer, and needs to use the encoded ones when communicating
4224 with servers. However, Gnus doesn't know what charset is used for each
4225 non-@acronym{ASCII} group name. The following two variables are just
4226 the ones for telling Gnus what charset should be used for each group:
4229 @item gnus-group-name-charset-method-alist
4230 @vindex gnus-group-name-charset-method-alist
4231 An alist of select methods and charsets. The default value is
4232 @code{nil}. The names of groups in the server specified by that select
4233 method are all supposed to use the corresponding charset. For example:
4236 (setq gnus-group-name-charset-method-alist
4237 '(((nntp "news.com.cn") . cn-gb-2312)))
4240 Charsets specified for groups with this variable are preferred to the
4241 ones specified for the same groups with the
4242 @code{gnus-group-name-charset-group-alist} variable (see below).
4244 A select method can be very long, like:
4248 (nntp-address "news.gmane.org")
4249 (nntp-end-of-line "\n")
4250 (nntp-open-connection-function
4251 nntp-open-via-rlogin-and-telnet)
4252 (nntp-via-rlogin-command "ssh")
4253 (nntp-via-rlogin-command-switches
4254 ("-C" "-t" "-e" "none"))
4255 (nntp-via-address @dots{}))
4258 In that case, you can truncate it into @code{(nntp "gmane")} in this
4259 variable. That is, it is enough to contain only the back end name and
4262 @item gnus-group-name-charset-group-alist
4263 @cindex UTF-8 group names
4264 @vindex gnus-group-name-charset-group-alist
4265 An alist of regexp of group name and the charset for group names.
4266 @code{((".*" . utf-8))} is the default value if UTF-8 is supported,
4267 otherwise the default is @code{nil}. For example:
4270 (setq gnus-group-name-charset-group-alist
4271 '(("\\.com\\.cn:" . cn-gb-2312)
4275 Note that this variable is ignored if the match is made with
4276 @code{gnus-group-name-charset-method-alist}.
4279 Those two variables are used also to determine the charset for encoding
4280 and decoding non-@acronym{ASCII} group names that are in the back ends
4281 other than @code{nntp}. It means that it is you who determine it. If
4282 you do nothing, the charset used for group names in those back ends will
4283 all be @code{utf-8} because of the last element of
4284 @code{gnus-group-name-charset-group-alist}.
4286 There is one more important variable for non-@acronym{ASCII} group
4290 @item nnmail-pathname-coding-system
4291 @vindex nnmail-pathname-coding-system
4292 The value of this variable should be a coding system or @code{nil}. The
4293 default is @code{nil} in Emacs, or is the aliasee of the coding system
4294 named @code{file-name} (a certain coding system of which an alias is
4295 @code{file-name}) in XEmacs.
4297 The @code{nnml} back end, the @code{nnrss} back end, the @acronym{NNTP}
4298 marks feature (@pxref{NNTP marks}), the agent, and the cache use
4299 non-@acronym{ASCII} group names in those files and directories. This
4300 variable overrides the value of @code{file-name-coding-system} which
4301 specifies the coding system used when encoding and decoding those file
4302 names and directory names.
4304 In XEmacs (with the @code{mule} feature), @code{file-name-coding-system}
4305 is the only means to specify the coding system used to encode and decode
4306 file names. On the other hand, Emacs uses the value of
4307 @code{default-file-name-coding-system} if @code{file-name-coding-system}
4308 is @code{nil} or it is bound to the value of
4309 @code{nnmail-pathname-coding-system} which is @code{nil}.
4311 Normally the value of @code{default-file-name-coding-system} in Emacs or
4312 @code{nnmail-pathname-coding-system} in XEmacs is initialized according
4313 to the locale, so you will need to do nothing if the value is suitable
4314 to encode and decode non-@acronym{ASCII} group names.
4316 The value of this variable (or @code{default-file-name-coding-system})
4317 does not necessarily need to be the same value that is determined by
4318 @code{gnus-group-name-charset-method-alist} and
4319 @code{gnus-group-name-charset-group-alist}.
4321 If @code{default-file-name-coding-system} or this variable is
4322 initialized by default to @code{iso-latin-1} for example, although you
4323 want to subscribe to the groups spelled in Chinese, that is the most
4324 typical case where you have to customize
4325 @code{nnmail-pathname-coding-system}. The @code{utf-8} coding system is
4326 a good candidate for it. Otherwise, you may change the locale in your
4327 system so that @code{default-file-name-coding-system} or this variable
4328 may be initialized to an appropriate value.
4331 Note that when you copy or move articles from a non-@acronym{ASCII}
4332 group to another group, the charset used to encode and decode group
4333 names should be the same in both groups. Otherwise the Newsgroups
4334 header will be displayed incorrectly in the article buffer.
4337 @node Misc Group Stuff
4338 @section Misc Group Stuff
4341 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
4342 * Group Information:: Information and help on groups and Gnus.
4343 * Group Timestamp:: Making Gnus keep track of when you last read a group.
4344 * File Commands:: Reading and writing the Gnus files.
4345 * Sieve Commands:: Managing Sieve scripts.
4352 @cindex keys, reserved for users (Group)
4353 The key @kbd{v} is reserved for users. You can bind it to some
4354 command or better use it as a prefix key. For example:
4357 (define-key gnus-group-mode-map (kbd "v j d")
4360 (gnus-group-jump-to-group "nndraft:drafts")))
4363 On keys reserved for users in Emacs and on keybindings in general
4364 @xref{Keymaps, Keymaps, , emacs, The Emacs Editor}.
4368 @findex gnus-group-enter-server-mode
4369 Enter the server buffer (@code{gnus-group-enter-server-mode}).
4370 @xref{Server Buffer}.
4374 @findex gnus-group-post-news
4375 Start composing a message (a news by default)
4376 (@code{gnus-group-post-news}). If given a prefix, post to the group
4377 under the point. If the prefix is 1, prompt for a group to post to.
4378 Contrary to what the name of this function suggests, the prepared
4379 article might be a mail instead of a news, if a mail group is specified
4380 with the prefix argument. @xref{Composing Messages}.
4384 @findex gnus-group-mail
4385 Mail a message somewhere (@code{gnus-group-mail}). If given a prefix,
4386 use the posting style of the group under the point. If the prefix is 1,
4387 prompt for a group name to find the posting style.
4388 @xref{Composing Messages}.
4392 @findex gnus-group-news
4393 Start composing a news (@code{gnus-group-news}). If given a prefix,
4394 post to the group under the point. If the prefix is 1, prompt
4395 for group to post to. @xref{Composing Messages}.
4397 This function actually prepares a news even when using mail groups.
4398 This is useful for ``posting'' messages to mail groups without actually
4399 sending them over the network: they're just saved directly to the group
4400 in question. The corresponding back end must have a request-post method
4401 for this to work though.
4405 @findex gnus-group-compact-group
4407 Compact the group under point (@code{gnus-group-compact-group}).
4408 Currently implemented only in nnml (@pxref{Mail Spool}). This removes
4409 gaps between article numbers, hence getting a correct total article
4414 Variables for the group buffer:
4418 @item gnus-group-mode-hook
4419 @vindex gnus-group-mode-hook
4420 is called after the group buffer has been
4423 @item gnus-group-prepare-hook
4424 @vindex gnus-group-prepare-hook
4425 is called after the group buffer is
4426 generated. It may be used to modify the buffer in some strange,
4429 @item gnus-group-prepared-hook
4430 @vindex gnus-group-prepare-hook
4431 is called as the very last thing after the group buffer has been
4432 generated. It may be used to move point around, for instance.
4434 @item gnus-permanently-visible-groups
4435 @vindex gnus-permanently-visible-groups
4436 Groups matching this regexp will always be listed in the group buffer,
4437 whether they are empty or not.
4441 @node Scanning New Messages
4442 @subsection Scanning New Messages
4443 @cindex new messages
4444 @cindex scanning new news
4450 @findex gnus-group-get-new-news
4451 @c @icon{gnus-group-get-new-news}
4452 Check the server(s) for new articles. If the numerical prefix is used,
4453 this command will check only groups of level @var{arg} and lower
4454 (@code{gnus-group-get-new-news}). If given a non-numerical prefix, this
4455 command will force a total re-reading of the active file(s) from the
4460 @findex gnus-group-get-new-news-this-group
4461 @vindex gnus-goto-next-group-when-activating
4462 @c @icon{gnus-group-get-new-news-this-group}
4463 Check whether new articles have arrived in the current group
4464 (@code{gnus-group-get-new-news-this-group}).
4465 @code{gnus-goto-next-group-when-activating} says whether this command is
4466 to move point to the next group or not. It is @code{t} by default.
4468 @findex gnus-activate-all-groups
4469 @cindex activating groups
4471 @kindex C-c M-g (Group)
4472 Activate absolutely all groups (@code{gnus-activate-all-groups}).
4477 @findex gnus-group-restart
4478 Restart Gnus (@code{gnus-group-restart}). This saves the @file{.newsrc}
4479 file(s), closes the connection to all servers, clears up all run-time
4480 Gnus variables, and then starts Gnus all over again.
4484 @vindex gnus-get-new-news-hook
4485 @code{gnus-get-new-news-hook} is run just before checking for new news.
4487 @vindex gnus-after-getting-new-news-hook
4488 @code{gnus-after-getting-new-news-hook} is run after checking for new
4492 @node Group Information
4493 @subsection Group Information
4494 @cindex group information
4495 @cindex information on groups
4502 @c @icon{gnus-group-describe-group}
4504 @kindex C-c C-d (Group)
4505 @cindex describing groups
4506 @cindex group description
4507 @findex gnus-group-describe-group
4508 Describe the current group (@code{gnus-group-describe-group}). If given
4509 a prefix, force Gnus to re-read the description from the server.
4513 @findex gnus-group-describe-all-groups
4514 Describe all groups (@code{gnus-group-describe-all-groups}). If given a
4515 prefix, force Gnus to re-read the description file from the server.
4522 @findex gnus-version
4523 Display current Gnus version numbers (@code{gnus-version}).
4527 @findex gnus-group-describe-briefly
4528 Give a very short help message (@code{gnus-group-describe-briefly}).
4531 @kindex C-c C-i (Group)
4534 @findex gnus-info-find-node
4535 Go to the Gnus info node (@code{gnus-info-find-node}).
4539 @node Group Timestamp
4540 @subsection Group Timestamp
4542 @cindex group timestamps
4544 It can be convenient to let Gnus keep track of when you last read a
4545 group. To set the ball rolling, you should add
4546 @code{gnus-group-set-timestamp} to @code{gnus-select-group-hook}:
4549 (add-hook 'gnus-select-group-hook 'gnus-group-set-timestamp)
4552 After doing this, each time you enter a group, it'll be recorded.
4554 This information can be displayed in various ways---the easiest is to
4555 use the @samp{%d} spec in the group line format:
4558 (setq gnus-group-line-format
4559 "%M\%S\%p\%P\%5y: %(%-40,40g%) %d\n")
4562 This will result in lines looking like:
4565 * 0: mail.ding 19961002T012943
4566 0: custom 19961002T012713
4569 As you can see, the date is displayed in compact ISO 8601 format. This
4570 may be a bit too much, so to just display the date, you could say
4574 (setq gnus-group-line-format
4575 "%M\%S\%p\%P\%5y: %(%-40,40g%) %6,6~(cut 2)d\n")
4578 If you would like greater control of the time format, you can use a
4579 user-defined format spec. Something like the following should do the
4583 (setq gnus-group-line-format
4584 "%M\%S\%p\%P\%5y: %(%-40,40g%) %ud\n")
4585 (defun gnus-user-format-function-d (headers)
4586 (let ((time (gnus-group-timestamp gnus-tmp-group)))
4588 (format-time-string "%b %d %H:%M" time)
4594 @subsection File Commands
4595 @cindex file commands
4601 @findex gnus-group-read-init-file
4602 @vindex gnus-init-file
4603 @cindex reading init file
4604 Re-read the init file (@code{gnus-init-file}, which defaults to
4605 @file{~/.gnus.el}) (@code{gnus-group-read-init-file}).
4609 @findex gnus-group-save-newsrc
4610 @cindex saving .newsrc
4611 Save the @file{.newsrc.eld} file (and @file{.newsrc} if wanted)
4612 (@code{gnus-group-save-newsrc}). If given a prefix, force saving the
4613 file(s) whether Gnus thinks it is necessary or not.
4616 @c @kindex Z (Group)
4617 @c @findex gnus-group-clear-dribble
4618 @c Clear the dribble buffer (@code{gnus-group-clear-dribble}).
4623 @node Sieve Commands
4624 @subsection Sieve Commands
4625 @cindex group sieve commands
4627 Sieve is a server-side mail filtering language. In Gnus you can use
4628 the @code{sieve} group parameter (@pxref{Group Parameters}) to specify
4629 sieve rules that should apply to each group. Gnus provides two
4630 commands to translate all these group parameters into a proper Sieve
4631 script that can be transferred to the server somehow.
4633 @vindex gnus-sieve-file
4634 @vindex gnus-sieve-region-start
4635 @vindex gnus-sieve-region-end
4636 The generated Sieve script is placed in @code{gnus-sieve-file} (by
4637 default @file{~/.sieve}). The Sieve code that Gnus generate is placed
4638 between two delimiters, @code{gnus-sieve-region-start} and
4639 @code{gnus-sieve-region-end}, so you may write additional Sieve code
4640 outside these delimiters that will not be removed the next time you
4641 regenerate the Sieve script.
4643 @vindex gnus-sieve-crosspost
4644 The variable @code{gnus-sieve-crosspost} controls how the Sieve script
4645 is generated. If it is non-@code{nil} (the default) articles is
4646 placed in all groups that have matching rules, otherwise the article
4647 is only placed in the group with the first matching rule. For
4648 example, the group parameter @samp{(sieve address "sender"
4649 "owner-ding@@hpc.uh.edu")} will generate the following piece of Sieve
4650 code if @code{gnus-sieve-crosspost} is @code{nil}. (When
4651 @code{gnus-sieve-crosspost} is non-@code{nil}, it looks the same
4652 except that the line containing the call to @code{stop} is removed.)
4655 if address "sender" "owner-ding@@hpc.uh.edu" @{
4656 fileinto "INBOX.ding";
4661 @xref{Top, Emacs Sieve, Top, sieve, Emacs Sieve}.
4667 @findex gnus-sieve-generate
4668 @vindex gnus-sieve-file
4669 @cindex generating sieve script
4670 Regenerate a Sieve script from the @code{sieve} group parameters and
4671 put you into the @code{gnus-sieve-file} without saving it.
4675 @findex gnus-sieve-update
4676 @vindex gnus-sieve-file
4677 @cindex updating sieve script
4678 Regenerates the Gnus managed part of @code{gnus-sieve-file} using the
4679 @code{sieve} group parameters, save the file and upload it to the
4680 server using the @code{sieveshell} program.
4685 @node Summary Buffer
4686 @chapter Summary Buffer
4687 @cindex summary buffer
4689 A line for each article is displayed in the summary buffer. You can
4690 move around, read articles, post articles and reply to articles.
4692 The most common way to a summary buffer is to select a group from the
4693 group buffer (@pxref{Selecting a Group}).
4695 You can have as many summary buffers open as you wish.
4697 You can customize the Summary Mode tool bar, see @kbd{M-x
4698 customize-apropos RET gnus-summary-tool-bar}. This feature is only
4702 @cindex keys, reserved for users (Summary)
4703 The key @kbd{v} is reserved for users. You can bind it to some
4704 command or better use it as a prefix key. For example:
4706 (define-key gnus-summary-mode-map (kbd "v -") "LrS") ;; lower subthread
4710 * Summary Buffer Format:: Deciding how the summary buffer is to look.
4711 * Summary Maneuvering:: Moving around the summary buffer.
4712 * Choosing Articles:: Reading articles.
4713 * Paging the Article:: Scrolling the current article.
4714 * Reply Followup and Post:: Posting articles.
4715 * Delayed Articles:: Send articles at a later time.
4716 * Marking Articles:: Marking articles as read, expirable, etc.
4717 * Limiting:: You can limit the summary buffer.
4718 * Threading:: How threads are made.
4719 * Sorting the Summary Buffer:: How articles and threads are sorted.
4720 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
4721 * Article Caching:: You may store articles in a cache.
4722 * Persistent Articles:: Making articles expiry-resistant.
4723 * Sticky Articles:: Article buffers that are not reused.
4724 * Article Backlog:: Having already read articles hang around.
4725 * Saving Articles:: Ways of customizing article saving.
4726 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
4727 * Article Treatment:: The article buffer can be mangled at will.
4728 * MIME Commands:: Doing MIMEy things with the articles.
4729 * Charsets:: Character set issues.
4730 * Article Commands:: Doing various things with the article buffer.
4731 * Summary Sorting:: Sorting the summary buffer in various ways.
4732 * Finding the Parent:: No child support? Get the parent.
4733 * Alternative Approaches:: Reading using non-default summaries.
4734 * Tree Display:: A more visual display of threads.
4735 * Mail Group Commands:: Some commands can only be used in mail groups.
4736 * Various Summary Stuff:: What didn't fit anywhere else.
4737 * Exiting the Summary Buffer:: Returning to the Group buffer,
4738 or reselecting the current group.
4739 * Crosspost Handling:: How crossposted articles are dealt with.
4740 * Duplicate Suppression:: An alternative when crosspost handling fails.
4741 * Security:: Decrypt and Verify.
4742 * Mailing List:: Mailing list minor mode.
4746 @node Summary Buffer Format
4747 @section Summary Buffer Format
4748 @cindex summary buffer format
4752 \gnusfigure{The Summary Buffer}{180}{
4753 \put(0,0){\epsfig{figure=ps/summary,width=7.5cm}}
4754 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-article,width=7.5cm}}}
4760 * Summary Buffer Lines:: You can specify how summary lines should look.
4761 * To From Newsgroups:: How to not display your own name.
4762 * Summary Buffer Mode Line:: You can say how the mode line should look.
4763 * Summary Highlighting:: Making the summary buffer all pretty and nice.
4766 @findex mail-extract-address-components
4767 @findex gnus-extract-address-components
4768 @vindex gnus-extract-address-components
4769 Gnus will use the value of the @code{gnus-extract-address-components}
4770 variable as a function for getting the name and address parts of a
4771 @code{From} header. Two pre-defined functions exist:
4772 @code{gnus-extract-address-components}, which is the default, quite
4773 fast, and too simplistic solution; and
4774 @code{mail-extract-address-components}, which works very nicely, but is
4775 slower. The default function will return the wrong answer in 5% of the
4776 cases. If this is unacceptable to you, use the other function instead:
4779 (setq gnus-extract-address-components
4780 'mail-extract-address-components)
4783 @vindex gnus-summary-same-subject
4784 @code{gnus-summary-same-subject} is a string indicating that the current
4785 article has the same subject as the previous. This string will be used
4786 with those specs that require it. The default is @code{""}.
4789 @node Summary Buffer Lines
4790 @subsection Summary Buffer Lines
4792 @vindex gnus-summary-line-format
4793 You can change the format of the lines in the summary buffer by changing
4794 the @code{gnus-summary-line-format} variable. It works along the same
4795 lines as a normal @code{format} string, with some extensions
4796 (@pxref{Formatting Variables}).
4798 There should always be a colon or a point position marker on the line;
4799 the cursor always moves to the point position marker or the colon after
4800 performing an operation. (Of course, Gnus wouldn't be Gnus if it wasn't
4801 possible to change this. Just write a new function
4802 @code{gnus-goto-colon} which does whatever you like with the cursor.)
4803 @xref{Positioning Point}.
4805 The default string is @samp{%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n}.
4807 The following format specification characters and extended format
4808 specification(s) are understood:
4814 Subject string. List identifiers stripped,
4815 @code{gnus-list-identifiers}. @xref{Article Hiding}.
4817 Subject if the article is the root of the thread or the previous article
4818 had a different subject, @code{gnus-summary-same-subject} otherwise.
4819 (@code{gnus-summary-same-subject} defaults to @code{""}.)
4821 Full @code{From} header.
4823 The name (from the @code{From} header).
4825 The name, @code{To} header or the @code{Newsgroups} header (@pxref{To
4828 The name (from the @code{From} header). This differs from the @code{n}
4829 spec in that it uses the function designated by the
4830 @code{gnus-extract-address-components} variable, which is slower, but
4831 may be more thorough.
4833 The address (from the @code{From} header). This works the same way as
4836 Number of lines in the article.
4838 Number of characters in the article. This specifier is not supported
4839 in some methods (like nnfolder).
4841 Pretty-printed version of the number of characters in the article;
4842 for example, @samp{1.2k} or @samp{0.4M}.
4844 Indentation based on thread level (@pxref{Customizing Threading}).
4846 A complex trn-style thread tree, showing response-connecting trace
4847 lines. A thread could be drawn like this:
4860 You can customize the appearance with the following options. Note
4861 that it is possible to make the thread display look really neat by
4862 replacing the default @acronym{ASCII} characters with graphic
4863 line-drawing glyphs.
4865 @item gnus-sum-thread-tree-root
4866 @vindex gnus-sum-thread-tree-root
4867 Used for the root of a thread. If @code{nil}, use subject
4868 instead. The default is @samp{> }.
4870 @item gnus-sum-thread-tree-false-root
4871 @vindex gnus-sum-thread-tree-false-root
4872 Used for the false root of a thread (@pxref{Loose Threads}). If
4873 @code{nil}, use subject instead. The default is @samp{> }.
4875 @item gnus-sum-thread-tree-single-indent
4876 @vindex gnus-sum-thread-tree-single-indent
4877 Used for a thread with just one message. If @code{nil}, use subject
4878 instead. The default is @samp{}.
4880 @item gnus-sum-thread-tree-vertical
4881 @vindex gnus-sum-thread-tree-vertical
4882 Used for drawing a vertical line. The default is @samp{| }.
4884 @item gnus-sum-thread-tree-indent
4885 @vindex gnus-sum-thread-tree-indent
4886 Used for indenting. The default is @samp{ }.
4888 @item gnus-sum-thread-tree-leaf-with-other
4889 @vindex gnus-sum-thread-tree-leaf-with-other
4890 Used for a leaf with brothers. The default is @samp{+-> }.
4892 @item gnus-sum-thread-tree-single-leaf
4893 @vindex gnus-sum-thread-tree-single-leaf
4894 Used for a leaf without brothers. The default is @samp{\-> }
4899 Nothing if the article is a root and lots of spaces if it isn't (it
4900 pushes everything after it off the screen).
4902 Opening bracket, which is normally @samp{[}, but can also be @samp{<}
4903 for adopted articles (@pxref{Customizing Threading}).
4905 Closing bracket, which is normally @samp{]}, but can also be @samp{>}
4906 for adopted articles.
4908 One space for each thread level.
4910 Twenty minus thread level spaces.
4912 Unread. @xref{Read Articles}.
4915 This misleadingly named specifier is the @dfn{secondary mark}. This
4916 mark will say whether the article has been replied to, has been cached,
4917 or has been saved. @xref{Other Marks}.
4920 Score as a number (@pxref{Scoring}).
4922 @vindex gnus-summary-zcore-fuzz
4923 Zcore, @samp{+} if above the default level and @samp{-} if below the
4924 default level. If the difference between
4925 @code{gnus-summary-default-score} and the score is less than
4926 @code{gnus-summary-zcore-fuzz}, this spec will not be used.
4934 The @code{Date} in @code{DD-MMM} format.
4936 The @code{Date} in @var{YYYYMMDD}@code{T}@var{HHMMSS} format.
4942 Number of articles in the current sub-thread. Using this spec will slow
4943 down summary buffer generation somewhat.
4945 An @samp{=} (@code{gnus-not-empty-thread-mark}) will be displayed if the
4946 article has any children.
4952 Desired cursor position (instead of after first colon).
4954 Age sensitive date format. Various date format is defined in
4955 @code{gnus-user-date-format-alist}.
4957 User defined specifier. The next character in the format string should
4958 be a letter. Gnus will call the function
4959 @code{gnus-user-format-function-@var{x}}, where @var{x} is the letter
4960 following @samp{%u}. The function will be passed the current header as
4961 argument. The function should return a string, which will be inserted
4962 into the summary just like information from any other summary specifier.
4965 Text between @samp{%(} and @samp{%)} will be highlighted with
4966 @code{gnus-mouse-face} when the mouse point is placed inside the area.
4967 There can only be one such area.
4969 The @samp{%U} (status), @samp{%R} (replied) and @samp{%z} (zcore) specs
4970 have to be handled with care. For reasons of efficiency, Gnus will
4971 compute what column these characters will end up in, and ``hard-code''
4972 that. This means that it is invalid to have these specs after a
4973 variable-length spec. Well, you might not be arrested, but your summary
4974 buffer will look strange, which is bad enough.
4976 The smart choice is to have these specs as far to the left as possible.
4977 (Isn't that the case with everything, though? But I digress.)
4979 This restriction may disappear in later versions of Gnus.
4982 @node To From Newsgroups
4983 @subsection To From Newsgroups
4987 In some groups (particularly in archive groups), the @code{From} header
4988 isn't very interesting, since all the articles there are written by
4989 you. To display the information in the @code{To} or @code{Newsgroups}
4990 headers instead, you need to decide three things: What information to
4991 gather; where to display it; and when to display it.
4995 @vindex gnus-extra-headers
4996 The reading of extra header information is controlled by the
4997 @code{gnus-extra-headers}. This is a list of header symbols. For
5001 (setq gnus-extra-headers
5002 '(To Newsgroups X-Newsreader))
5005 This will result in Gnus trying to obtain these three headers, and
5006 storing it in header structures for later easy retrieval.
5009 @findex gnus-extra-header
5010 The value of these extra headers can be accessed via the
5011 @code{gnus-extra-header} function. Here's a format line spec that will
5012 access the @code{X-Newsreader} header:
5015 "%~(form (gnus-extra-header 'X-Newsreader))@@"
5019 @vindex gnus-ignored-from-addresses
5020 The @code{gnus-ignored-from-addresses} variable says when the @samp{%f}
5021 summary line spec returns the @code{To}, @code{Newsreader} or
5022 @code{From} header. If this regexp matches the contents of the
5023 @code{From} header, the value of the @code{To} or @code{Newsreader}
5024 headers are used instead.
5026 To distinguish regular articles from those where the @code{From} field
5027 has been swapped, a string is prefixed to the @code{To} or
5028 @code{Newsgroups} header in the summary line. By default the string is
5029 @samp{-> } for @code{To} and @samp{=> } for @code{Newsgroups}, you can
5030 customize these strings with @code{gnus-summary-to-prefix} and
5031 @code{gnus-summary-newsgroup-prefix}.
5035 @vindex nnmail-extra-headers
5036 A related variable is @code{nnmail-extra-headers}, which controls when
5037 to include extra headers when generating overview (@acronym{NOV}) files.
5038 If you have old overview files, you should regenerate them after
5039 changing this variable, by entering the server buffer using @kbd{^},
5040 and then @kbd{g} on the appropriate mail server (e.g. nnml) to cause
5043 @vindex gnus-summary-line-format
5044 You also have to instruct Gnus to display the data by changing the
5045 @code{%n} spec to the @code{%f} spec in the
5046 @code{gnus-summary-line-format} variable.
5048 In summary, you'd typically put something like the following in
5052 (setq gnus-extra-headers
5054 (setq nnmail-extra-headers gnus-extra-headers)
5055 (setq gnus-summary-line-format
5056 "%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n")
5057 (setq gnus-ignored-from-addresses
5061 (The values listed above are the default values in Gnus. Alter them
5064 A note for news server administrators, or for users who wish to try to
5065 convince their news server administrator to provide some additional
5068 The above is mostly useful for mail groups, where you have control over
5069 the @acronym{NOV} files that are created. However, if you can persuade your
5070 nntp admin to add (in the usual implementation, notably INN):
5076 to the end of her @file{overview.fmt} file, then you can use that just
5077 as you would the extra headers from the mail groups.
5080 @node Summary Buffer Mode Line
5081 @subsection Summary Buffer Mode Line
5083 @vindex gnus-summary-mode-line-format
5084 You can also change the format of the summary mode bar (@pxref{Mode Line
5085 Formatting}). Set @code{gnus-summary-mode-line-format} to whatever you
5086 like. The default is @samp{Gnus: %%b [%A] %Z}.
5088 Here are the elements you can play with:
5094 Unprefixed group name.
5096 Current article number.
5098 Current article score.
5102 Number of unread articles in this group.
5104 Number of unread articles in this group that aren't displayed in the
5107 A string with the number of unread and unselected articles represented
5108 either as @samp{<%U(+%e) more>} if there are both unread and unselected
5109 articles, and just as @samp{<%U more>} if there are just unread articles
5110 and no unselected ones.
5112 Shortish group name. For instance, @samp{rec.arts.anime} will be
5113 shortened to @samp{r.a.anime}.
5115 Subject of the current article.
5117 User-defined spec (@pxref{User-Defined Specs}).
5119 Name of the current score file (@pxref{Scoring}).
5121 Number of dormant articles (@pxref{Unread Articles}).
5123 Number of ticked articles (@pxref{Unread Articles}).
5125 Number of articles that have been marked as read in this session.
5127 Number of articles expunged by the score files.
5131 @node Summary Highlighting
5132 @subsection Summary Highlighting
5136 @item gnus-visual-mark-article-hook
5137 @vindex gnus-visual-mark-article-hook
5138 This hook is run after selecting an article. It is meant to be used for
5139 highlighting the article in some way. It is not run if
5140 @code{gnus-visual} is @code{nil}.
5142 @item gnus-summary-update-hook
5143 @vindex gnus-summary-update-hook
5144 This hook is called when a summary line is changed. It is not run if
5145 @code{gnus-visual} is @code{nil}.
5147 @item gnus-summary-selected-face
5148 @vindex gnus-summary-selected-face
5149 This is the face (or @dfn{font} as some people call it) used to
5150 highlight the current article in the summary buffer.
5152 @item gnus-summary-highlight
5153 @vindex gnus-summary-highlight
5154 Summary lines are highlighted according to this variable, which is a
5155 list where the elements are of the format @code{(@var{form}
5156 . @var{face})}. If you would, for instance, like ticked articles to be
5157 italic and high-scored articles to be bold, you could set this variable
5160 (((eq mark gnus-ticked-mark) . italic)
5161 ((> score default) . bold))
5163 As you may have guessed, if @var{form} returns a non-@code{nil} value,
5164 @var{face} will be applied to the line.
5168 @node Summary Maneuvering
5169 @section Summary Maneuvering
5170 @cindex summary movement
5172 All the straight movement commands understand the numeric prefix and
5173 behave pretty much as you'd expect.
5175 None of these commands select articles.
5180 @kindex M-n (Summary)
5181 @kindex G M-n (Summary)
5182 @findex gnus-summary-next-unread-subject
5183 Go to the next summary line of an unread article
5184 (@code{gnus-summary-next-unread-subject}).
5188 @kindex M-p (Summary)
5189 @kindex G M-p (Summary)
5190 @findex gnus-summary-prev-unread-subject
5191 Go to the previous summary line of an unread article
5192 (@code{gnus-summary-prev-unread-subject}).
5195 @kindex G g (Summary)
5196 @findex gnus-summary-goto-subject
5197 Ask for an article number and then go to the summary line of that article
5198 without displaying the article (@code{gnus-summary-goto-subject}).
5201 If Gnus asks you to press a key to confirm going to the next group, you
5202 can use the @kbd{C-n} and @kbd{C-p} keys to move around the group
5203 buffer, searching for the next group to read without actually returning
5204 to the group buffer.
5206 Variables related to summary movement:
5210 @vindex gnus-auto-select-next
5211 @item gnus-auto-select-next
5212 If you issue one of the movement commands (like @kbd{n}) and there are
5213 no more unread articles after the current one, Gnus will offer to go to
5214 the next group. If this variable is @code{t} and the next group is
5215 empty, Gnus will exit summary mode and return to the group buffer. If
5216 this variable is neither @code{t} nor @code{nil}, Gnus will select the
5217 next group with unread articles. As a special case, if this variable
5218 is @code{quietly}, Gnus will select the next group without asking for
5219 confirmation. If this variable is @code{almost-quietly}, the same
5220 will happen only if you are located on the last article in the group.
5221 Finally, if this variable is @code{slightly-quietly}, the @kbd{Z n}
5222 command will go to the next group without confirmation. Also
5223 @pxref{Group Levels}.
5225 @item gnus-auto-select-same
5226 @vindex gnus-auto-select-same
5227 If non-@code{nil}, all the movement commands will try to go to the next
5228 article with the same subject as the current. (@dfn{Same} here might
5229 mean @dfn{roughly equal}. See @code{gnus-summary-gather-subject-limit}
5230 for details (@pxref{Customizing Threading}).) If there are no more
5231 articles with the same subject, go to the first unread article.
5233 This variable is not particularly useful if you use a threaded display.
5235 @item gnus-summary-check-current
5236 @vindex gnus-summary-check-current
5237 If non-@code{nil}, all the ``unread'' movement commands will not proceed
5238 to the next (or previous) article if the current article is unread.
5239 Instead, they will choose the current article.
5241 @item gnus-auto-center-summary
5242 @vindex gnus-auto-center-summary
5243 If non-@code{nil}, Gnus will keep the point in the summary buffer
5244 centered at all times. This makes things quite tidy, but if you have a
5245 slow network connection, or simply do not like this un-Emacsism, you can
5246 set this variable to @code{nil} to get the normal Emacs scrolling
5247 action. This will also inhibit horizontal re-centering of the summary
5248 buffer, which might make it more inconvenient to read extremely long
5251 This variable can also be a number. In that case, center the window at
5252 the given number of lines from the top.
5254 @item gnus-summary-stop-at-end-of-message
5255 @vindex gnus-summary-stop-at-end-of-message
5256 If non-@code{nil}, don't go to the next article when hitting
5257 @kbd{SPC}, and you're at the end of the article.
5262 @node Choosing Articles
5263 @section Choosing Articles
5264 @cindex selecting articles
5267 * Choosing Commands:: Commands for choosing articles.
5268 * Choosing Variables:: Variables that influence these commands.
5272 @node Choosing Commands
5273 @subsection Choosing Commands
5275 None of the following movement commands understand the numeric prefix,
5276 and they all select and display an article.
5278 If you want to fetch new articles or redisplay the group, see
5279 @ref{Exiting the Summary Buffer}.
5283 @kindex SPACE (Summary)
5284 @findex gnus-summary-next-page
5285 Select the current article, or, if that one's read already, the next
5286 unread article (@code{gnus-summary-next-page}).
5288 If you have an article window open already and you press @kbd{SPACE}
5289 again, the article will be scrolled. This lets you conveniently
5290 @kbd{SPACE} through an entire newsgroup. @xref{Paging the Article}.
5295 @kindex G n (Summary)
5296 @findex gnus-summary-next-unread-article
5297 @c @icon{gnus-summary-next-unread}
5298 Go to next unread article (@code{gnus-summary-next-unread-article}).
5303 @findex gnus-summary-prev-unread-article
5304 @c @icon{gnus-summary-prev-unread}
5305 Go to previous unread article (@code{gnus-summary-prev-unread-article}).
5310 @kindex G N (Summary)
5311 @findex gnus-summary-next-article
5312 Go to the next article (@code{gnus-summary-next-article}).
5317 @kindex G P (Summary)
5318 @findex gnus-summary-prev-article
5319 Go to the previous article (@code{gnus-summary-prev-article}).
5322 @kindex G C-n (Summary)
5323 @findex gnus-summary-next-same-subject
5324 Go to the next article with the same subject
5325 (@code{gnus-summary-next-same-subject}).
5328 @kindex G C-p (Summary)
5329 @findex gnus-summary-prev-same-subject
5330 Go to the previous article with the same subject
5331 (@code{gnus-summary-prev-same-subject}).
5335 @kindex G f (Summary)
5337 @findex gnus-summary-first-unread-article
5338 Go to the first unread article
5339 (@code{gnus-summary-first-unread-article}).
5343 @kindex G b (Summary)
5345 @findex gnus-summary-best-unread-article
5346 Go to the unread article with the highest score
5347 (@code{gnus-summary-best-unread-article}). If given a prefix argument,
5348 go to the first unread article that has a score over the default score.
5353 @kindex G l (Summary)
5354 @findex gnus-summary-goto-last-article
5355 Go to the previous article read (@code{gnus-summary-goto-last-article}).
5358 @kindex G o (Summary)
5359 @findex gnus-summary-pop-article
5361 @cindex article history
5362 Pop an article off the summary history and go to this article
5363 (@code{gnus-summary-pop-article}). This command differs from the
5364 command above in that you can pop as many previous articles off the
5365 history as you like, while @kbd{l} toggles the two last read articles.
5366 For a somewhat related issue (if you use these commands a lot),
5367 @pxref{Article Backlog}.
5372 @kindex G j (Summary)
5373 @findex gnus-summary-goto-article
5374 Ask for an article number or @code{Message-ID}, and then go to that
5375 article (@code{gnus-summary-goto-article}).
5380 @node Choosing Variables
5381 @subsection Choosing Variables
5383 Some variables relevant for moving and selecting articles:
5386 @item gnus-auto-extend-newsgroup
5387 @vindex gnus-auto-extend-newsgroup
5388 All the movement commands will try to go to the previous (or next)
5389 article, even if that article isn't displayed in the Summary buffer if
5390 this variable is non-@code{nil}. Gnus will then fetch the article from
5391 the server and display it in the article buffer.
5393 @item gnus-select-article-hook
5394 @vindex gnus-select-article-hook
5395 This hook is called whenever an article is selected. The default is
5396 @code{nil}. If you would like each article to be saved in the Agent as
5397 you read it, putting @code{gnus-agent-fetch-selected-article} on this
5400 @item gnus-mark-article-hook
5401 @vindex gnus-mark-article-hook
5402 @findex gnus-summary-mark-unread-as-read
5403 @findex gnus-summary-mark-read-and-unread-as-read
5404 @findex gnus-unread-mark
5405 This hook is called whenever an article is selected. It is intended to
5406 be used for marking articles as read. The default value is
5407 @code{gnus-summary-mark-read-and-unread-as-read}, and will change the
5408 mark of almost any article you read to @code{gnus-read-mark}. The only
5409 articles not affected by this function are ticked, dormant, and
5410 expirable articles. If you'd instead like to just have unread articles
5411 marked as read, you can use @code{gnus-summary-mark-unread-as-read}
5412 instead. It will leave marks like @code{gnus-low-score-mark},
5413 @code{gnus-del-mark} (and so on) alone.
5418 @node Paging the Article
5419 @section Scrolling the Article
5420 @cindex article scrolling
5425 @kindex SPACE (Summary)
5426 @findex gnus-summary-next-page
5427 Pressing @kbd{SPACE} will scroll the current article forward one page,
5428 or, if you have come to the end of the current article, will choose the
5429 next article (@code{gnus-summary-next-page}).
5431 @vindex gnus-article-boring-faces
5432 @vindex gnus-article-skip-boring
5433 If @code{gnus-article-skip-boring} is non-@code{nil} and the rest of
5434 the article consists only of citations and signature, then it will be
5435 skipped; the next article will be shown instead. You can customize
5436 what is considered uninteresting with
5437 @code{gnus-article-boring-faces}. You can manually view the article's
5438 pages, no matter how boring, using @kbd{C-M-v}.
5441 @kindex DEL (Summary)
5442 @findex gnus-summary-prev-page
5443 Scroll the current article back one page (@code{gnus-summary-prev-page}).
5446 @kindex RET (Summary)
5447 @findex gnus-summary-scroll-up
5448 Scroll the current article one line forward
5449 (@code{gnus-summary-scroll-up}).
5452 @kindex M-RET (Summary)
5453 @findex gnus-summary-scroll-down
5454 Scroll the current article one line backward
5455 (@code{gnus-summary-scroll-down}).
5459 @kindex A g (Summary)
5461 @findex gnus-summary-show-article
5462 @vindex gnus-summary-show-article-charset-alist
5463 (Re)fetch the current article (@code{gnus-summary-show-article}). If
5464 given a prefix, show a completely ``raw'' article, just the way it
5465 came from the server. If given a prefix twice (i.e., @kbd{C-u C-u
5466 g'}), fetch the current article, but don't run any of the article
5467 treatment functions.
5469 @cindex charset, view article with different charset
5470 If given a numerical prefix, you can do semi-manual charset stuff.
5471 @kbd{C-u 0 g cn-gb-2312 RET} will decode the message as if it were
5472 encoded in the @code{cn-gb-2312} charset. If you have
5475 (setq gnus-summary-show-article-charset-alist
5480 then you can say @kbd{C-u 1 g} to get the same effect.
5485 @kindex A < (Summary)
5486 @findex gnus-summary-beginning-of-article
5487 Scroll to the beginning of the article
5488 (@code{gnus-summary-beginning-of-article}).
5493 @kindex A > (Summary)
5494 @findex gnus-summary-end-of-article
5495 Scroll to the end of the article (@code{gnus-summary-end-of-article}).
5499 @kindex A s (Summary)
5501 @findex gnus-summary-isearch-article
5502 Perform an isearch in the article buffer
5503 (@code{gnus-summary-isearch-article}).
5507 @findex gnus-summary-select-article-buffer
5508 Select the article buffer (@code{gnus-summary-select-article-buffer}).
5513 @node Reply Followup and Post
5514 @section Reply, Followup and Post
5517 * Summary Mail Commands:: Sending mail.
5518 * Summary Post Commands:: Sending news.
5519 * Summary Message Commands:: Other Message-related commands.
5520 * Canceling and Superseding::
5524 @node Summary Mail Commands
5525 @subsection Summary Mail Commands
5527 @cindex composing mail
5529 Commands for composing a mail message:
5535 @kindex S r (Summary)
5537 @findex gnus-summary-reply
5538 @c @icon{gnus-summary-mail-reply}
5539 @c @icon{gnus-summary-reply}
5540 Mail a reply to the author of the current article
5541 (@code{gnus-summary-reply}).
5546 @kindex S R (Summary)
5547 @findex gnus-summary-reply-with-original
5548 @c @icon{gnus-summary-reply-with-original}
5549 Mail a reply to the author of the current article and include the
5550 original message (@code{gnus-summary-reply-with-original}). This
5551 command uses the process/prefix convention.
5554 @kindex S w (Summary)
5555 @findex gnus-summary-wide-reply
5556 Mail a wide reply to the author of the current article
5557 (@code{gnus-summary-wide-reply}). A @dfn{wide reply} is a reply that
5558 goes out to all people listed in the @code{To}, @code{From} (or
5559 @code{Reply-to}) and @code{Cc} headers. If @code{Mail-Followup-To} is
5560 present, that's used instead.
5563 @kindex S W (Summary)
5564 @findex gnus-summary-wide-reply-with-original
5565 Mail a wide reply to the current article and include the original
5566 message (@code{gnus-summary-wide-reply-with-original}). This command uses
5567 the process/prefix convention, but only uses the headers from the
5568 first article to determine the recipients.
5571 @kindex S L (Summary)
5572 @findex gnus-summary-reply-to-list-with-original
5573 When replying to a message from a mailing list, send a reply to that
5574 message to the mailing list, and include the original message
5575 (@code{gnus-summary-reply-to-list-with-original}).
5578 @kindex S v (Summary)
5579 @findex gnus-summary-very-wide-reply
5580 Mail a very wide reply to the author of the current article
5581 (@code{gnus-summary-wide-reply}). A @dfn{very wide reply} is a reply
5582 that goes out to all people listed in the @code{To}, @code{From} (or
5583 @code{Reply-to}) and @code{Cc} headers in all the process/prefixed
5584 articles. This command uses the process/prefix convention.
5587 @kindex S V (Summary)
5588 @findex gnus-summary-very-wide-reply-with-original
5589 Mail a very wide reply to the author of the current article and include the
5590 original message (@code{gnus-summary-very-wide-reply-with-original}). This
5591 command uses the process/prefix convention.
5594 @kindex S B r (Summary)
5595 @findex gnus-summary-reply-broken-reply-to
5596 Mail a reply to the author of the current article but ignore the
5597 @code{Reply-To} field (@code{gnus-summary-reply-broken-reply-to}).
5598 If you need this because a mailing list incorrectly sets a
5599 @code{Reply-To} header pointing to the list, you probably want to set
5600 the @code{broken-reply-to} group parameter instead, so things will work
5601 correctly. @xref{Group Parameters}.
5604 @kindex S B R (Summary)
5605 @findex gnus-summary-reply-broken-reply-to-with-original
5606 Mail a reply to the author of the current article and include the
5607 original message but ignore the @code{Reply-To} field
5608 (@code{gnus-summary-reply-broken-reply-to-with-original}).
5612 @kindex S o m (Summary)
5613 @kindex C-c C-f (Summary)
5614 @findex gnus-summary-mail-forward
5615 @c @icon{gnus-summary-mail-forward}
5616 Forward the current article to some other person
5617 (@code{gnus-summary-mail-forward}). If no prefix is given, the message
5618 is forwarded according to the value of (@code{message-forward-as-mime})
5619 and (@code{message-forward-show-mml}); if the prefix is 1, decode the
5620 message and forward directly inline; if the prefix is 2, forward message
5621 as an rfc822 @acronym{MIME} section; if the prefix is 3, decode message and
5622 forward as an rfc822 @acronym{MIME} section; if the prefix is 4, forward message
5623 directly inline; otherwise, the message is forwarded as no prefix given
5624 but use the flipped value of (@code{message-forward-as-mime}). By
5625 default, the message is decoded and forwarded as an rfc822 @acronym{MIME}
5631 @kindex S m (Summary)
5632 @findex gnus-summary-mail-other-window
5633 @c @icon{gnus-summary-mail-originate}
5634 Prepare a mail (@code{gnus-summary-mail-other-window}). By default, use
5635 the posting style of the current group. If given a prefix, disable that.
5636 If the prefix is 1, prompt for a group name to find the posting style.
5639 @kindex S i (Summary)
5640 @findex gnus-summary-news-other-window
5641 Prepare a news (@code{gnus-summary-news-other-window}). By default,
5642 post to the current group. If given a prefix, disable that. If the
5643 prefix is 1, prompt for a group to post to.
5645 This function actually prepares a news even when using mail groups.
5646 This is useful for ``posting'' messages to mail groups without actually
5647 sending them over the network: they're just saved directly to the group
5648 in question. The corresponding back end must have a request-post method
5649 for this to work though.
5652 @kindex S D b (Summary)
5653 @findex gnus-summary-resend-bounced-mail
5654 @cindex bouncing mail
5655 If you have sent a mail, but the mail was bounced back to you for some
5656 reason (wrong address, transient failure), you can use this command to
5657 resend that bounced mail (@code{gnus-summary-resend-bounced-mail}). You
5658 will be popped into a mail buffer where you can edit the headers before
5659 sending the mail off again. If you give a prefix to this command, and
5660 the bounced mail is a reply to some other mail, Gnus will try to fetch
5661 that mail and display it for easy perusal of its headers. This might
5662 very well fail, though.
5665 @kindex S D r (Summary)
5666 @findex gnus-summary-resend-message
5667 Not to be confused with the previous command,
5668 @code{gnus-summary-resend-message} will prompt you for an address to
5669 send the current message off to, and then send it to that place. The
5670 headers of the message won't be altered---but lots of headers that say
5671 @code{Resent-To}, @code{Resent-From} and so on will be added. This
5672 means that you actually send a mail to someone that has a @code{To}
5673 header that (probably) points to yourself. This will confuse people.
5674 So, natcherly you'll only do that if you're really eVIl.
5676 This command is mainly used if you have several accounts and want to
5677 ship a mail to a different account of yours. (If you're both
5678 @code{root} and @code{postmaster} and get a mail for @code{postmaster}
5679 to the @code{root} account, you may want to resend it to
5680 @code{postmaster}. Ordnung muss sein!
5682 This command understands the process/prefix convention
5683 (@pxref{Process/Prefix}).
5686 @kindex S D e (Summary)
5687 @findex gnus-summary-resend-message-edit
5689 Like the previous command, but will allow you to edit the message as
5690 if it were a new message before resending.
5693 @kindex S O m (Summary)
5694 @findex gnus-uu-digest-mail-forward
5695 Digest the current series (@pxref{Decoding Articles}) and forward the
5696 result using mail (@code{gnus-uu-digest-mail-forward}). This command
5697 uses the process/prefix convention (@pxref{Process/Prefix}).
5700 @kindex S M-c (Summary)
5701 @findex gnus-summary-mail-crosspost-complaint
5702 @cindex crossposting
5703 @cindex excessive crossposting
5704 Send a complaint about excessive crossposting to the author of the
5705 current article (@code{gnus-summary-mail-crosspost-complaint}).
5707 @findex gnus-crosspost-complaint
5708 This command is provided as a way to fight back against the current
5709 crossposting pandemic that's sweeping Usenet. It will compose a reply
5710 using the @code{gnus-crosspost-complaint} variable as a preamble. This
5711 command understands the process/prefix convention
5712 (@pxref{Process/Prefix}) and will prompt you before sending each mail.
5716 Also @xref{Header Commands, ,Header Commands, message, The Message
5717 Manual}, for more information.
5720 @node Summary Post Commands
5721 @subsection Summary Post Commands
5723 @cindex composing news
5725 Commands for posting a news article:
5731 @kindex S p (Summary)
5732 @findex gnus-summary-post-news
5733 @c @icon{gnus-summary-post-news}
5734 Prepare for posting an article (@code{gnus-summary-post-news}). By
5735 default, post to the current group. If given a prefix, disable that.
5736 If the prefix is 1, prompt for another group instead.
5741 @kindex S f (Summary)
5742 @findex gnus-summary-followup
5743 @c @icon{gnus-summary-followup}
5744 Post a followup to the current article (@code{gnus-summary-followup}).
5748 @kindex S F (Summary)
5750 @c @icon{gnus-summary-followup-with-original}
5751 @findex gnus-summary-followup-with-original
5752 Post a followup to the current article and include the original message
5753 (@code{gnus-summary-followup-with-original}). This command uses the
5754 process/prefix convention.
5757 @kindex S n (Summary)
5758 @findex gnus-summary-followup-to-mail
5759 Post a followup to the current article via news, even if you got the
5760 message through mail (@code{gnus-summary-followup-to-mail}).
5763 @kindex S N (Summary)
5764 @findex gnus-summary-followup-to-mail-with-original
5765 Post a followup to the current article via news, even if you got the
5766 message through mail and include the original message
5767 (@code{gnus-summary-followup-to-mail-with-original}). This command uses
5768 the process/prefix convention.
5771 @kindex S o p (Summary)
5772 @findex gnus-summary-post-forward
5773 Forward the current article to a newsgroup
5774 (@code{gnus-summary-post-forward}).
5775 If no prefix is given, the message is forwarded according to the value
5776 of (@code{message-forward-as-mime}) and
5777 (@code{message-forward-show-mml}); if the prefix is 1, decode the
5778 message and forward directly inline; if the prefix is 2, forward message
5779 as an rfc822 @acronym{MIME} section; if the prefix is 3, decode message and
5780 forward as an rfc822 @acronym{MIME} section; if the prefix is 4, forward message
5781 directly inline; otherwise, the message is forwarded as no prefix given
5782 but use the flipped value of (@code{message-forward-as-mime}). By
5783 default, the message is decoded and forwarded as an rfc822 @acronym{MIME} section.
5786 @kindex S O p (Summary)
5787 @findex gnus-uu-digest-post-forward
5789 @cindex making digests
5790 Digest the current series and forward the result to a newsgroup
5791 (@code{gnus-uu-digest-post-forward}). This command uses the
5792 process/prefix convention.
5795 @kindex S u (Summary)
5796 @findex gnus-uu-post-news
5797 @c @icon{gnus-uu-post-news}
5798 Uuencode a file, split it into parts, and post it as a series
5799 (@code{gnus-uu-post-news}). (@pxref{Uuencoding and Posting}).
5802 Also @xref{Header Commands, ,Header Commands, message, The Message
5803 Manual}, for more information.
5806 @node Summary Message Commands
5807 @subsection Summary Message Commands
5811 @kindex S y (Summary)
5812 @findex gnus-summary-yank-message
5813 Yank the current article into an already existing Message composition
5814 buffer (@code{gnus-summary-yank-message}). This command prompts for
5815 what message buffer you want to yank into, and understands the
5816 process/prefix convention (@pxref{Process/Prefix}).
5821 @node Canceling and Superseding
5822 @subsection Canceling Articles
5823 @cindex canceling articles
5824 @cindex superseding articles
5826 Have you ever written something, and then decided that you really,
5827 really, really wish you hadn't posted that?
5829 Well, you can't cancel mail, but you can cancel posts.
5831 @findex gnus-summary-cancel-article
5833 @c @icon{gnus-summary-cancel-article}
5834 Find the article you wish to cancel (you can only cancel your own
5835 articles, so don't try any funny stuff). Then press @kbd{C} or @kbd{S
5836 c} (@code{gnus-summary-cancel-article}). Your article will be
5837 canceled---machines all over the world will be deleting your article.
5838 This command uses the process/prefix convention (@pxref{Process/Prefix}).
5840 Be aware, however, that not all sites honor cancels, so your article may
5841 live on here and there, while most sites will delete the article in
5844 Gnus will use the ``current'' select method when canceling. If you
5845 want to use the standard posting method, use the @samp{a} symbolic
5846 prefix (@pxref{Symbolic Prefixes}).
5848 Gnus ensures that only you can cancel your own messages using a
5849 @code{Cancel-Lock} header (@pxref{Canceling News, Canceling News, ,
5850 message, Message Manual}).
5852 If you discover that you have made some mistakes and want to do some
5853 corrections, you can post a @dfn{superseding} article that will replace
5854 your original article.
5856 @findex gnus-summary-supersede-article
5858 Go to the original article and press @kbd{S s}
5859 (@code{gnus-summary-supersede-article}). You will be put in a buffer
5860 where you can edit the article all you want before sending it off the
5863 The same goes for superseding as for canceling, only more so: Some
5864 sites do not honor superseding. On those sites, it will appear that you
5865 have posted almost the same article twice.
5867 If you have just posted the article, and change your mind right away,
5868 there is a trick you can use to cancel/supersede the article without
5869 waiting for the article to appear on your site first. You simply return
5870 to the post buffer (which is called @code{*sent ...*}). There you will
5871 find the article you just posted, with all the headers intact. Change
5872 the @code{Message-ID} header to a @code{Cancel} or @code{Supersedes}
5873 header by substituting one of those words for the word
5874 @code{Message-ID}. Then just press @kbd{C-c C-c} to send the article as
5875 you would do normally. The previous article will be
5876 canceled/superseded.
5878 Just remember, kids: There is no 'c' in 'supersede'.
5880 @node Delayed Articles
5881 @section Delayed Articles
5882 @cindex delayed sending
5883 @cindex send delayed
5885 Sometimes, you might wish to delay the sending of a message. For
5886 example, you might wish to arrange for a message to turn up just in time
5887 to remind your about the birthday of your Significant Other. For this,
5888 there is the @code{gnus-delay} package. Setup is simple:
5891 (gnus-delay-initialize)
5894 @findex gnus-delay-article
5895 Normally, to send a message you use the @kbd{C-c C-c} command from
5896 Message mode. To delay a message, use @kbd{C-c C-j}
5897 (@code{gnus-delay-article}) instead. This will ask you for how long the
5898 message should be delayed. Possible answers are:
5902 A time span. Consists of an integer and a letter. For example,
5903 @code{42d} means to delay for 42 days. Available letters are @code{m}
5904 (minutes), @code{h} (hours), @code{d} (days), @code{w} (weeks), @code{M}
5905 (months) and @code{Y} (years).
5908 A specific date. Looks like @code{YYYY-MM-DD}. The message will be
5909 delayed until that day, at a specific time (eight o'clock by default).
5910 See also @code{gnus-delay-default-hour}.
5913 A specific time of day. Given in @code{hh:mm} format, 24h, no am/pm
5914 stuff. The deadline will be at that time today, except if that time has
5915 already passed, then it's at the given time tomorrow. So if it's ten
5916 o'clock in the morning and you specify @code{11:15}, then the deadline
5917 is one hour and fifteen minutes hence. But if you specify @code{9:20},
5918 that means a time tomorrow.
5921 The action of the @code{gnus-delay-article} command is influenced by a
5922 couple of variables:
5925 @item gnus-delay-default-hour
5926 @vindex gnus-delay-default-hour
5927 When you specify a specific date, the message will be due on that hour
5928 on the given date. Possible values are integers 0 through 23.
5930 @item gnus-delay-default-delay
5931 @vindex gnus-delay-default-delay
5932 This is a string and gives the default delay. It can be of any of the
5933 formats described above.
5935 @item gnus-delay-group
5936 @vindex gnus-delay-group
5937 Delayed articles will be kept in this group on the drafts server until
5938 they are due. You probably don't need to change this. The default
5939 value is @code{"delayed"}.
5941 @item gnus-delay-header
5942 @vindex gnus-delay-header
5943 The deadline for each article will be stored in a header. This variable
5944 is a string and gives the header name. You probably don't need to
5945 change this. The default value is @code{"X-Gnus-Delayed"}.
5948 The way delaying works is like this: when you use the
5949 @code{gnus-delay-article} command, you give a certain delay. Gnus
5950 calculates the deadline of the message and stores it in the
5951 @code{X-Gnus-Delayed} header and puts the message in the
5952 @code{nndraft:delayed} group.
5954 @findex gnus-delay-send-queue
5955 And whenever you get new news, Gnus looks through the group for articles
5956 which are due and sends them. It uses the @code{gnus-delay-send-queue}
5957 function for this. By default, this function is added to the hook
5958 @code{gnus-get-new-news-hook}. But of course, you can change this.
5959 Maybe you want to use the demon to send drafts? Just tell the demon to
5960 execute the @code{gnus-delay-send-queue} function.
5963 @item gnus-delay-initialize
5964 @findex gnus-delay-initialize
5965 By default, this function installs @code{gnus-delay-send-queue} in
5966 @code{gnus-get-new-news-hook}. But it accepts the optional second
5967 argument @code{no-check}. If it is non-@code{nil},
5968 @code{gnus-get-new-news-hook} is not changed. The optional first
5969 argument is ignored.
5971 For example, @code{(gnus-delay-initialize nil t)} means to do nothing.
5972 Presumably, you want to use the demon for sending due delayed articles.
5973 Just don't forget to set that up :-)
5976 When delaying an article with @kbd{C-c C-j}, Message mode will
5977 automatically add a @code{"Date"} header with the current time. In
5978 many cases you probably want the @code{"Date"} header to reflect the
5979 time the message is sent instead. To do this, you have to delete
5980 @code{Date} from @code{message-draft-headers}.
5983 @node Marking Articles
5984 @section Marking Articles
5985 @cindex article marking
5986 @cindex article ticking
5989 There are several marks you can set on an article.
5991 You have marks that decide the @dfn{readedness} (whoo, neato-keano
5992 neologism ohoy!) of the article. Alphabetic marks generally mean
5993 @dfn{read}, while non-alphabetic characters generally mean @dfn{unread}.
5995 In addition, you also have marks that do not affect readedness.
5998 There's a plethora of commands for manipulating these marks.
6002 * Unread Articles:: Marks for unread articles.
6003 * Read Articles:: Marks for read articles.
6004 * Other Marks:: Marks that do not affect readedness.
6005 * Setting Marks:: How to set and remove marks.
6006 * Generic Marking Commands:: How to customize the marking.
6007 * Setting Process Marks:: How to mark articles for later processing.
6011 @node Unread Articles
6012 @subsection Unread Articles
6014 The following marks mark articles as (kinda) unread, in one form or
6019 @vindex gnus-ticked-mark
6020 Marked as ticked (@code{gnus-ticked-mark}).
6022 @dfn{Ticked articles} are articles that will remain visible always. If
6023 you see an article that you find interesting, or you want to put off
6024 reading it, or replying to it, until sometime later, you'd typically
6025 tick it. However, articles can be expired (from news servers by the
6026 news server software, Gnus itself never expires ticked messages), so if
6027 you want to keep an article forever, you'll have to make it persistent
6028 (@pxref{Persistent Articles}).
6031 @vindex gnus-dormant-mark
6032 Marked as dormant (@code{gnus-dormant-mark}).
6034 @dfn{Dormant articles} will only appear in the summary buffer if there
6035 are followups to it. If you want to see them even if they don't have
6036 followups, you can use the @kbd{/ D} command (@pxref{Limiting}).
6037 Otherwise (except for the visibility issue), they are just like ticked
6041 @vindex gnus-unread-mark
6042 Marked as unread (@code{gnus-unread-mark}).
6044 @dfn{Unread articles} are articles that haven't been read at all yet.
6049 @subsection Read Articles
6050 @cindex expirable mark
6052 All the following marks mark articles as read.
6057 @vindex gnus-del-mark
6058 These are articles that the user has marked as read with the @kbd{d}
6059 command manually, more or less (@code{gnus-del-mark}).
6062 @vindex gnus-read-mark
6063 Articles that have actually been read (@code{gnus-read-mark}).
6066 @vindex gnus-ancient-mark
6067 Articles that were marked as read in previous sessions and are now
6068 @dfn{old} (@code{gnus-ancient-mark}).
6071 @vindex gnus-killed-mark
6072 Marked as killed (@code{gnus-killed-mark}).
6075 @vindex gnus-kill-file-mark
6076 Marked as killed by kill files (@code{gnus-kill-file-mark}).
6079 @vindex gnus-low-score-mark
6080 Marked as read by having too low a score (@code{gnus-low-score-mark}).
6083 @vindex gnus-catchup-mark
6084 Marked as read by a catchup (@code{gnus-catchup-mark}).
6087 @vindex gnus-canceled-mark
6088 Canceled article (@code{gnus-canceled-mark})
6091 @vindex gnus-sparse-mark
6092 Sparsely reffed article (@code{gnus-sparse-mark}). @xref{Customizing
6096 @vindex gnus-duplicate-mark
6097 Article marked as read by duplicate suppression
6098 (@code{gnus-duplicate-mark}). @xref{Duplicate Suppression}.
6102 All these marks just mean that the article is marked as read, really.
6103 They are interpreted differently when doing adaptive scoring, though.
6105 One more special mark, though:
6109 @vindex gnus-expirable-mark
6110 Marked as expirable (@code{gnus-expirable-mark}).
6112 Marking articles as @dfn{expirable} (or have them marked as such
6113 automatically) doesn't make much sense in normal groups---a user doesn't
6114 control expiring of news articles, but in mail groups, for instance,
6115 articles marked as @dfn{expirable} can be deleted by Gnus at
6121 @subsection Other Marks
6122 @cindex process mark
6125 There are some marks that have nothing to do with whether the article is
6131 You can set a bookmark in the current article. Say you are reading a
6132 long thesis on cats' urinary tracts, and have to go home for dinner
6133 before you've finished reading the thesis. You can then set a bookmark
6134 in the article, and Gnus will jump to this bookmark the next time it
6135 encounters the article. @xref{Setting Marks}.
6138 @vindex gnus-replied-mark
6139 All articles that you have replied to or made a followup to (i.e., have
6140 answered) will be marked with an @samp{A} in the second column
6141 (@code{gnus-replied-mark}).
6144 @vindex gnus-forwarded-mark
6145 All articles that you have forwarded will be marked with an @samp{F} in
6146 the second column (@code{gnus-forwarded-mark}).
6149 @vindex gnus-cached-mark
6150 Articles stored in the article cache will be marked with an @samp{*} in
6151 the second column (@code{gnus-cached-mark}). @xref{Article Caching}.
6154 @vindex gnus-saved-mark
6155 Articles ``saved'' (in some manner or other; not necessarily
6156 religiously) are marked with an @samp{S} in the second column
6157 (@code{gnus-saved-mark}).
6160 @vindex gnus-unseen-mark
6161 Articles that haven't been seen before in Gnus by the user are marked
6162 with a @samp{.} in the second column (@code{gnus-unseen-mark}).
6165 @vindex gnus-downloaded-mark
6166 When using the Gnus agent (@pxref{Agent Basics}), articles may be
6167 downloaded for unplugged (offline) viewing. If you are using the
6168 @samp{%O} spec, these articles get the @samp{+} mark in that spec.
6169 (The variable @code{gnus-downloaded-mark} controls which character to
6173 @vindex gnus-undownloaded-mark
6174 When using the Gnus agent (@pxref{Agent Basics}), some articles might
6175 not have been downloaded. Such articles cannot be viewed while you
6176 are unplugged (offline). If you are using the @samp{%O} spec, these
6177 articles get the @samp{-} mark in that spec. (The variable
6178 @code{gnus-undownloaded-mark} controls which character to use.)
6181 @vindex gnus-downloadable-mark
6182 The Gnus agent (@pxref{Agent Basics}) downloads some articles
6183 automatically, but it is also possible to explicitly mark articles for
6184 download, even if they would not be downloaded automatically. Such
6185 explicitly-marked articles get the @samp{%} mark in the first column.
6186 (The variable @code{gnus-downloadable-mark} controls which character to
6190 @vindex gnus-not-empty-thread-mark
6191 @vindex gnus-empty-thread-mark
6192 If the @samp{%e} spec is used, the presence of threads or not will be
6193 marked with @code{gnus-not-empty-thread-mark} and
6194 @code{gnus-empty-thread-mark} in the third column, respectively.
6197 @vindex gnus-process-mark
6198 Finally we have the @dfn{process mark} (@code{gnus-process-mark}). A
6199 variety of commands react to the presence of the process mark. For
6200 instance, @kbd{X u} (@code{gnus-uu-decode-uu}) will uudecode and view
6201 all articles that have been marked with the process mark. Articles
6202 marked with the process mark have a @samp{#} in the second column.
6206 You might have noticed that most of these ``non-readedness'' marks
6207 appear in the second column by default. So if you have a cached, saved,
6208 replied article that you have process-marked, what will that look like?
6210 Nothing much. The precedence rules go as follows: process -> cache ->
6211 replied -> saved. So if the article is in the cache and is replied,
6212 you'll only see the cache mark and not the replied mark.
6216 @subsection Setting Marks
6217 @cindex setting marks
6219 All the marking commands understand the numeric prefix.
6224 @kindex M c (Summary)
6225 @kindex M-u (Summary)
6226 @findex gnus-summary-clear-mark-forward
6227 @cindex mark as unread
6228 Clear all readedness-marks from the current article
6229 (@code{gnus-summary-clear-mark-forward}). In other words, mark the
6235 @kindex M t (Summary)
6236 @findex gnus-summary-tick-article-forward
6237 Tick the current article (@code{gnus-summary-tick-article-forward}).
6238 @xref{Article Caching}.
6243 @kindex M ? (Summary)
6244 @findex gnus-summary-mark-as-dormant
6245 Mark the current article as dormant
6246 (@code{gnus-summary-mark-as-dormant}). @xref{Article Caching}.
6250 @kindex M d (Summary)
6252 @findex gnus-summary-mark-as-read-forward
6253 Mark the current article as read
6254 (@code{gnus-summary-mark-as-read-forward}).
6258 @findex gnus-summary-mark-as-read-backward
6259 Mark the current article as read and move point to the previous line
6260 (@code{gnus-summary-mark-as-read-backward}).
6265 @kindex M k (Summary)
6266 @findex gnus-summary-kill-same-subject-and-select
6267 Mark all articles that have the same subject as the current one as read,
6268 and then select the next unread article
6269 (@code{gnus-summary-kill-same-subject-and-select}).
6273 @kindex M K (Summary)
6274 @kindex C-k (Summary)
6275 @findex gnus-summary-kill-same-subject
6276 Mark all articles that have the same subject as the current one as read
6277 (@code{gnus-summary-kill-same-subject}).
6280 @kindex M C (Summary)
6281 @findex gnus-summary-catchup
6282 @c @icon{gnus-summary-catchup}
6283 Mark all unread articles as read (@code{gnus-summary-catchup}).
6286 @kindex M C-c (Summary)
6287 @findex gnus-summary-catchup-all
6288 Mark all articles in the group as read---even the ticked and dormant
6289 articles (@code{gnus-summary-catchup-all}).
6292 @kindex M H (Summary)
6293 @findex gnus-summary-catchup-to-here
6294 Catchup the current group to point (before the point)
6295 (@code{gnus-summary-catchup-to-here}).
6298 @kindex M h (Summary)
6299 @findex gnus-summary-catchup-from-here
6300 Catchup the current group from point (after the point)
6301 (@code{gnus-summary-catchup-from-here}).
6304 @kindex C-w (Summary)
6305 @findex gnus-summary-mark-region-as-read
6306 Mark all articles between point and mark as read
6307 (@code{gnus-summary-mark-region-as-read}).
6310 @kindex M V k (Summary)
6311 @findex gnus-summary-kill-below
6312 Kill all articles with scores below the default score (or below the
6313 numeric prefix) (@code{gnus-summary-kill-below}).
6317 @kindex M e (Summary)
6319 @findex gnus-summary-mark-as-expirable
6320 Mark the current article as expirable
6321 (@code{gnus-summary-mark-as-expirable}).
6324 @kindex M b (Summary)
6325 @findex gnus-summary-set-bookmark
6326 Set a bookmark in the current article
6327 (@code{gnus-summary-set-bookmark}).
6330 @kindex M B (Summary)
6331 @findex gnus-summary-remove-bookmark
6332 Remove the bookmark from the current article
6333 (@code{gnus-summary-remove-bookmark}).
6336 @kindex M V c (Summary)
6337 @findex gnus-summary-clear-above
6338 Clear all marks from articles with scores over the default score (or
6339 over the numeric prefix) (@code{gnus-summary-clear-above}).
6342 @kindex M V u (Summary)
6343 @findex gnus-summary-tick-above
6344 Tick all articles with scores over the default score (or over the
6345 numeric prefix) (@code{gnus-summary-tick-above}).
6348 @kindex M V m (Summary)
6349 @findex gnus-summary-mark-above
6350 Prompt for a mark, and mark all articles with scores over the default
6351 score (or over the numeric prefix) with this mark
6352 (@code{gnus-summary-clear-above}).
6355 @vindex gnus-summary-goto-unread
6356 The @code{gnus-summary-goto-unread} variable controls what action should
6357 be taken after setting a mark. If non-@code{nil}, point will move to
6358 the next/previous unread article. If @code{nil}, point will just move
6359 one line up or down. As a special case, if this variable is
6360 @code{never}, all the marking commands as well as other commands (like
6361 @kbd{SPACE}) will move to the next article, whether it is unread or not.
6362 The default is @code{t}.
6365 @node Generic Marking Commands
6366 @subsection Generic Marking Commands
6368 Some people would like the command that ticks an article (@kbd{!}) go to
6369 the next article. Others would like it to go to the next unread
6370 article. Yet others would like it to stay on the current article. And
6371 even though I haven't heard of anybody wanting it to go to the
6372 previous (unread) article, I'm sure there are people that want that as
6375 Multiply these five behaviors with five different marking commands, and
6376 you get a potentially complex set of variable to control what each
6379 To sidestep that mess, Gnus provides commands that do all these
6380 different things. They can be found on the @kbd{M M} map in the summary
6381 buffer. Type @kbd{M M C-h} to see them all---there are too many of them
6382 to list in this manual.
6384 While you can use these commands directly, most users would prefer
6385 altering the summary mode keymap. For instance, if you would like the
6386 @kbd{!} command to go to the next article instead of the next unread
6387 article, you could say something like:
6391 (add-hook 'gnus-summary-mode-hook 'my-alter-summary-map)
6392 (defun my-alter-summary-map ()
6393 (local-set-key "!" 'gnus-summary-put-mark-as-ticked-next))
6401 (defun my-alter-summary-map ()
6402 (local-set-key "!" "MM!n"))
6406 @node Setting Process Marks
6407 @subsection Setting Process Marks
6408 @cindex setting process marks
6410 Process marks are displayed as @code{#} in the summary buffer, and are
6411 used for marking articles in such a way that other commands will
6412 process these articles. For instance, if you process mark four
6413 articles and then use the @kbd{*} command, Gnus will enter these four
6414 articles into the cache. For more information,
6415 @pxref{Process/Prefix}.
6422 @kindex M P p (Summary)
6423 @findex gnus-summary-mark-as-processable
6424 Mark the current article with the process mark
6425 (@code{gnus-summary-mark-as-processable}).
6426 @findex gnus-summary-unmark-as-processable
6430 @kindex M P u (Summary)
6431 @kindex M-# (Summary)
6432 Remove the process mark, if any, from the current article
6433 (@code{gnus-summary-unmark-as-processable}).
6436 @kindex M P U (Summary)
6437 @findex gnus-summary-unmark-all-processable
6438 Remove the process mark from all articles
6439 (@code{gnus-summary-unmark-all-processable}).
6442 @kindex M P i (Summary)
6443 @findex gnus-uu-invert-processable
6444 Invert the list of process marked articles
6445 (@code{gnus-uu-invert-processable}).
6448 @kindex M P R (Summary)
6449 @findex gnus-uu-mark-by-regexp
6450 Mark articles that have a @code{Subject} header that matches a regular
6451 expression (@code{gnus-uu-mark-by-regexp}).
6454 @kindex M P G (Summary)
6455 @findex gnus-uu-unmark-by-regexp
6456 Unmark articles that have a @code{Subject} header that matches a regular
6457 expression (@code{gnus-uu-unmark-by-regexp}).
6460 @kindex M P r (Summary)
6461 @findex gnus-uu-mark-region
6462 Mark articles in region (@code{gnus-uu-mark-region}).
6465 @kindex M P g (Summary)
6466 @findex gnus-uu-unmark-region
6467 Unmark articles in region (@code{gnus-uu-unmark-region}).
6470 @kindex M P t (Summary)
6471 @findex gnus-uu-mark-thread
6472 Mark all articles in the current (sub)thread
6473 (@code{gnus-uu-mark-thread}).
6476 @kindex M P T (Summary)
6477 @findex gnus-uu-unmark-thread
6478 Unmark all articles in the current (sub)thread
6479 (@code{gnus-uu-unmark-thread}).
6482 @kindex M P v (Summary)
6483 @findex gnus-uu-mark-over
6484 Mark all articles that have a score above the prefix argument
6485 (@code{gnus-uu-mark-over}).
6488 @kindex M P s (Summary)
6489 @findex gnus-uu-mark-series
6490 Mark all articles in the current series (@code{gnus-uu-mark-series}).
6493 @kindex M P S (Summary)
6494 @findex gnus-uu-mark-sparse
6495 Mark all series that have already had some articles marked
6496 (@code{gnus-uu-mark-sparse}).
6499 @kindex M P a (Summary)
6500 @findex gnus-uu-mark-all
6501 Mark all articles in series order (@code{gnus-uu-mark-all}).
6504 @kindex M P b (Summary)
6505 @findex gnus-uu-mark-buffer
6506 Mark all articles in the buffer in the order they appear
6507 (@code{gnus-uu-mark-buffer}).
6510 @kindex M P k (Summary)
6511 @findex gnus-summary-kill-process-mark
6512 Push the current process mark set onto the stack and unmark all articles
6513 (@code{gnus-summary-kill-process-mark}).
6516 @kindex M P y (Summary)
6517 @findex gnus-summary-yank-process-mark
6518 Pop the previous process mark set from the stack and restore it
6519 (@code{gnus-summary-yank-process-mark}).
6522 @kindex M P w (Summary)
6523 @findex gnus-summary-save-process-mark
6524 Push the current process mark set onto the stack
6525 (@code{gnus-summary-save-process-mark}).
6529 Also see the @kbd{&} command in @ref{Searching for Articles}, for how to
6530 set process marks based on article body contents.
6537 It can be convenient to limit the summary buffer to just show some
6538 subset of the articles currently in the group. The effect most limit
6539 commands have is to remove a few (or many) articles from the summary
6542 Limiting commands work on subsets of the articles already fetched from
6543 the servers. These commands don't query the server for additional
6550 @kindex / / (Summary)
6551 @findex gnus-summary-limit-to-subject
6552 Limit the summary buffer to articles that match some subject
6553 (@code{gnus-summary-limit-to-subject}). If given a prefix, exclude
6557 @kindex / a (Summary)
6558 @findex gnus-summary-limit-to-author
6559 Limit the summary buffer to articles that match some author
6560 (@code{gnus-summary-limit-to-author}). If given a prefix, exclude
6564 @kindex / R (Summary)
6565 @findex gnus-summary-limit-to-recipient
6566 Limit the summary buffer to articles that match some recipient
6567 (@code{gnus-summary-limit-to-recipient}). If given a prefix, exclude
6571 @kindex / A (Summary)
6572 @findex gnus-summary-limit-to-address
6573 Limit the summary buffer to articles in which contents of From, To or Cc
6574 header match a given address (@code{gnus-summary-limit-to-address}). If
6575 given a prefix, exclude matching articles.
6578 @kindex / S (Summary)
6579 @findex gnus-summary-limit-to-singletons
6580 Limit the summary buffer to articles that aren't part of any displayed
6581 threads (@code{gnus-summary-limit-to-singletons}). If given a prefix,
6582 limit to articles that are part of displayed threads.
6585 @kindex / x (Summary)
6586 @findex gnus-summary-limit-to-extra
6587 Limit the summary buffer to articles that match one of the ``extra''
6588 headers (@pxref{To From Newsgroups})
6589 (@code{gnus-summary-limit-to-extra}). If given a prefix, exclude
6594 @kindex / u (Summary)
6596 @findex gnus-summary-limit-to-unread
6597 Limit the summary buffer to articles not marked as read
6598 (@code{gnus-summary-limit-to-unread}). If given a prefix, limit the
6599 buffer to articles strictly unread. This means that ticked and
6600 dormant articles will also be excluded.
6603 @kindex / m (Summary)
6604 @findex gnus-summary-limit-to-marks
6605 Ask for a mark and then limit to all articles that have been marked
6606 with that mark (@code{gnus-summary-limit-to-marks}).
6609 @kindex / t (Summary)
6610 @findex gnus-summary-limit-to-age
6611 Ask for a number and then limit the summary buffer to articles older than (or equal to) that number of days
6612 (@code{gnus-summary-limit-to-age}). If given a prefix, limit to
6613 articles younger than that number of days.
6616 @kindex / n (Summary)
6617 @findex gnus-summary-limit-to-articles
6618 With prefix @samp{n}, limit the summary buffer to the next @samp{n}
6619 articles. If not given a prefix, use the process marked articles
6620 instead. (@code{gnus-summary-limit-to-articles}).
6623 @kindex / w (Summary)
6624 @findex gnus-summary-pop-limit
6625 Pop the previous limit off the stack and restore it
6626 (@code{gnus-summary-pop-limit}). If given a prefix, pop all limits off
6630 @kindex / . (Summary)
6631 @findex gnus-summary-limit-to-unseen
6632 Limit the summary buffer to the unseen articles
6633 (@code{gnus-summary-limit-to-unseen}).
6636 @kindex / v (Summary)
6637 @findex gnus-summary-limit-to-score
6638 Limit the summary buffer to articles that have a score at or above some
6639 score (@code{gnus-summary-limit-to-score}).
6642 @kindex / p (Summary)
6643 @findex gnus-summary-limit-to-display-predicate
6644 Limit the summary buffer to articles that satisfy the @code{display}
6645 group parameter predicate
6646 (@code{gnus-summary-limit-to-display-predicate}). @xref{Group
6647 Parameters}, for more on this predicate.
6650 @kindex / r (Summary)
6651 @findex gnus-summary-limit-to-replied
6652 Limit the summary buffer to replied articles
6653 (@code{gnus-summary-limit-to-replied}). If given a prefix, exclude
6658 @kindex M S (Summary)
6659 @kindex / E (Summary)
6660 @findex gnus-summary-limit-include-expunged
6661 Include all expunged articles in the limit
6662 (@code{gnus-summary-limit-include-expunged}).
6665 @kindex / D (Summary)
6666 @findex gnus-summary-limit-include-dormant
6667 Include all dormant articles in the limit
6668 (@code{gnus-summary-limit-include-dormant}).
6671 @kindex / * (Summary)
6672 @findex gnus-summary-limit-include-cached
6673 Include all cached articles in the limit
6674 (@code{gnus-summary-limit-include-cached}).
6677 @kindex / d (Summary)
6678 @findex gnus-summary-limit-exclude-dormant
6679 Exclude all dormant articles from the limit
6680 (@code{gnus-summary-limit-exclude-dormant}).
6683 @kindex / M (Summary)
6684 @findex gnus-summary-limit-exclude-marks
6685 Exclude all marked articles (@code{gnus-summary-limit-exclude-marks}).
6688 @kindex / T (Summary)
6689 @findex gnus-summary-limit-include-thread
6690 Include all the articles in the current thread in the limit.
6693 @kindex / c (Summary)
6694 @findex gnus-summary-limit-exclude-childless-dormant
6695 Exclude all dormant articles that have no children from the limit@*
6696 (@code{gnus-summary-limit-exclude-childless-dormant}).
6699 @kindex / C (Summary)
6700 @findex gnus-summary-limit-mark-excluded-as-read
6701 Mark all excluded unread articles as read
6702 (@code{gnus-summary-limit-mark-excluded-as-read}). If given a prefix,
6703 also mark excluded ticked and dormant articles as read.
6706 @kindex / b (Summary)
6707 @findex gnus-summary-limit-to-bodies
6708 Limit the summary buffer to articles that have bodies that match a
6709 certain regexp (@code{gnus-summary-limit-to-bodies}). If given a
6710 prefix, reverse the limit. This command is quite slow since it
6711 requires selecting each article to find the matches.
6714 @kindex / h (Summary)
6715 @findex gnus-summary-limit-to-headers
6716 Like the previous command, only limit to headers instead
6717 (@code{gnus-summary-limit-to-headers}).
6722 The following commands aren't limiting commands, but use the @kbd{/}
6727 @kindex / N (Summary)
6728 @findex gnus-summary-insert-new-articles
6729 Insert all new articles in the summary buffer. It scans for new emails
6730 if @var{back-end}@code{-get-new-mail} is non-@code{nil}.
6733 @kindex / o (Summary)
6734 @findex gnus-summary-insert-old-articles
6735 Insert all old articles in the summary buffer. If given a numbered
6736 prefix, fetch this number of articles.
6744 @cindex article threading
6746 Gnus threads articles by default. @dfn{To thread} is to put responses
6747 to articles directly after the articles they respond to---in a
6748 hierarchical fashion.
6750 Threading is done by looking at the @code{References} headers of the
6751 articles. In a perfect world, this would be enough to build pretty
6752 trees, but unfortunately, the @code{References} header is often broken
6753 or simply missing. Weird news propagation exacerbates the problem,
6754 so one has to employ other heuristics to get pleasing results. A
6755 plethora of approaches exists, as detailed in horrible detail in
6756 @ref{Customizing Threading}.
6758 First, a quick overview of the concepts:
6762 The top-most article in a thread; the first article in the thread.
6765 A tree-like article structure.
6768 A small(er) section of this tree-like structure.
6771 Threads often lose their roots due to article expiry, or due to the root
6772 already having been read in a previous session, and not displayed in the
6773 summary buffer. We then typically have many sub-threads that really
6774 belong to one thread, but are without connecting roots. These are
6775 called loose threads.
6777 @item thread gathering
6778 An attempt to gather loose threads into bigger threads.
6780 @item sparse threads
6781 A thread where the missing articles have been ``guessed'' at, and are
6782 displayed as empty lines in the summary buffer.
6788 * Customizing Threading:: Variables you can change to affect the threading.
6789 * Thread Commands:: Thread based commands in the summary buffer.
6793 @node Customizing Threading
6794 @subsection Customizing Threading
6795 @cindex customizing threading
6798 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
6799 * Filling In Threads:: Making the threads displayed look fuller.
6800 * More Threading:: Even more variables for fiddling with threads.
6801 * Low-Level Threading:: You thought it was over@dots{} but you were wrong!
6806 @subsubsection Loose Threads
6809 @cindex loose threads
6812 @item gnus-summary-make-false-root
6813 @vindex gnus-summary-make-false-root
6814 If non-@code{nil}, Gnus will gather all loose subtrees into one big tree
6815 and create a dummy root at the top. (Wait a minute. Root at the top?
6816 Yup.) Loose subtrees occur when the real root has expired, or you've
6817 read or killed the root in a previous session.
6819 When there is no real root of a thread, Gnus will have to fudge
6820 something. This variable says what fudging method Gnus should use.
6821 There are four possible values:
6825 \gnusfigure{The Summary Buffer}{390}{
6826 \put(0,0){\epsfig{figure=ps/summary-adopt,width=7.5cm}}
6827 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-empty,width=7.5cm}}}
6828 \put(0,400){\makebox(0,0)[tl]{\epsfig{figure=ps/summary-none,width=7.5cm}}}
6829 \put(445,400){\makebox(0,0)[tr]{\epsfig{figure=ps/summary-dummy,width=7.5cm}}}
6834 @cindex adopting articles
6839 Gnus will make the first of the orphaned articles the parent. This
6840 parent will adopt all the other articles. The adopted articles will be
6841 marked as such by pointy brackets (@samp{<>}) instead of the standard
6842 square brackets (@samp{[]}). This is the default method.
6845 @vindex gnus-summary-dummy-line-format
6846 @vindex gnus-summary-make-false-root-always
6847 Gnus will create a dummy summary line that will pretend to be the
6848 parent. This dummy line does not correspond to any real article, so
6849 selecting it will just select the first real article after the dummy
6850 article. @code{gnus-summary-dummy-line-format} is used to specify the
6851 format of the dummy roots. It accepts only one format spec: @samp{S},
6852 which is the subject of the article. @xref{Formatting Variables}.
6853 If you want all threads to have a dummy root, even the non-gathered
6854 ones, set @code{gnus-summary-make-false-root-always} to @code{t}.
6857 Gnus won't actually make any article the parent, but simply leave the
6858 subject field of all orphans except the first empty. (Actually, it will
6859 use @code{gnus-summary-same-subject} as the subject (@pxref{Summary
6863 Don't make any article parent at all. Just gather the threads and
6864 display them after one another.
6867 Don't gather loose threads.
6870 @item gnus-summary-gather-subject-limit
6871 @vindex gnus-summary-gather-subject-limit
6872 Loose threads are gathered by comparing subjects of articles. If this
6873 variable is @code{nil}, Gnus requires an exact match between the
6874 subjects of the loose threads before gathering them into one big
6875 super-thread. This might be too strict a requirement, what with the
6876 presence of stupid newsreaders that chop off long subject lines. If
6877 you think so, set this variable to, say, 20 to require that only the
6878 first 20 characters of the subjects have to match. If you set this
6879 variable to a really low number, you'll find that Gnus will gather
6880 everything in sight into one thread, which isn't very helpful.
6882 @cindex fuzzy article gathering
6883 If you set this variable to the special value @code{fuzzy}, Gnus will
6884 use a fuzzy string comparison algorithm on the subjects (@pxref{Fuzzy
6887 @item gnus-simplify-subject-fuzzy-regexp
6888 @vindex gnus-simplify-subject-fuzzy-regexp
6889 This can either be a regular expression or list of regular expressions
6890 that match strings that will be removed from subjects if fuzzy subject
6891 simplification is used.
6893 @item gnus-simplify-ignored-prefixes
6894 @vindex gnus-simplify-ignored-prefixes
6895 If you set @code{gnus-summary-gather-subject-limit} to something as low
6896 as 10, you might consider setting this variable to something sensible:
6898 @c Written by Michael Ernst <mernst@cs.rice.edu>
6900 (setq gnus-simplify-ignored-prefixes
6906 "wanted" "followup" "summary\\( of\\)?"
6907 "help" "query" "problem" "question"
6908 "answer" "reference" "announce"
6909 "How can I" "How to" "Comparison of"
6914 (mapconcat 'identity
6915 '("for" "for reference" "with" "about")
6917 "\\)?\\]?:?[ \t]*"))
6920 All words that match this regexp will be removed before comparing two
6923 @item gnus-simplify-subject-functions
6924 @vindex gnus-simplify-subject-functions
6925 If non-@code{nil}, this variable overrides
6926 @code{gnus-summary-gather-subject-limit}. This variable should be a
6927 list of functions to apply to the @code{Subject} string iteratively to
6928 arrive at the simplified version of the string.
6930 Useful functions to put in this list include:
6933 @item gnus-simplify-subject-re
6934 @findex gnus-simplify-subject-re
6935 Strip the leading @samp{Re:}.
6937 @item gnus-simplify-subject-fuzzy
6938 @findex gnus-simplify-subject-fuzzy
6941 @item gnus-simplify-whitespace
6942 @findex gnus-simplify-whitespace
6943 Remove excessive whitespace.
6945 @item gnus-simplify-all-whitespace
6946 @findex gnus-simplify-all-whitespace
6947 Remove all whitespace.
6950 You may also write your own functions, of course.
6953 @item gnus-summary-gather-exclude-subject
6954 @vindex gnus-summary-gather-exclude-subject
6955 Since loose thread gathering is done on subjects only, that might lead
6956 to many false hits, especially with certain common subjects like
6957 @samp{} and @samp{(none)}. To make the situation slightly better,
6958 you can use the regexp @code{gnus-summary-gather-exclude-subject} to say
6959 what subjects should be excluded from the gathering process.@*
6960 The default is @samp{^ *$\\|^(none)$}.
6962 @item gnus-summary-thread-gathering-function
6963 @vindex gnus-summary-thread-gathering-function
6964 Gnus gathers threads by looking at @code{Subject} headers. This means
6965 that totally unrelated articles may end up in the same ``thread'', which
6966 is confusing. An alternate approach is to look at all the
6967 @code{Message-ID}s in all the @code{References} headers to find matches.
6968 This will ensure that no gathered threads ever include unrelated
6969 articles, but it also means that people who have posted with broken
6970 newsreaders won't be gathered properly. The choice is yours---plague or
6974 @item gnus-gather-threads-by-subject
6975 @findex gnus-gather-threads-by-subject
6976 This function is the default gathering function and looks at
6977 @code{Subject}s exclusively.
6979 @item gnus-gather-threads-by-references
6980 @findex gnus-gather-threads-by-references
6981 This function looks at @code{References} headers exclusively.
6984 If you want to test gathering by @code{References}, you could say
6988 (setq gnus-summary-thread-gathering-function
6989 'gnus-gather-threads-by-references)
6995 @node Filling In Threads
6996 @subsubsection Filling In Threads
6999 @item gnus-fetch-old-headers
7000 @vindex gnus-fetch-old-headers
7001 If non-@code{nil}, Gnus will attempt to build old threads by fetching
7002 more old headers---headers to articles marked as read. If you would
7003 like to display as few summary lines as possible, but still connect as
7004 many loose threads as possible, you should set this variable to
7005 @code{some} or a number. If you set it to a number, no more than that
7006 number of extra old headers will be fetched. In either case, fetching
7007 old headers only works if the back end you are using carries overview
7008 files---this would normally be @code{nntp}, @code{nnspool},
7009 @code{nnml}, and @code{nnmaildir}. Also remember that if the root of
7010 the thread has been expired by the server, there's not much Gnus can
7013 This variable can also be set to @code{invisible}. This won't have any
7014 visible effects, but is useful if you use the @kbd{A T} command a lot
7015 (@pxref{Finding the Parent}).
7017 The server has to support @acronym{NOV} for any of this to work.
7019 @cindex Gmane, gnus-fetch-old-headers
7020 This feature can seriously impact performance it ignores all locally
7021 cached header entries. Setting it to @code{t} for groups for a server
7022 that doesn't expire articles (such as news.gmane.org), leads to very
7023 slow summary generation.
7025 @item gnus-fetch-old-ephemeral-headers
7026 @vindex gnus-fetch-old-ephemeral-headers
7027 Same as @code{gnus-fetch-old-headers}, but only used for ephemeral
7030 @item gnus-build-sparse-threads
7031 @vindex gnus-build-sparse-threads
7032 Fetching old headers can be slow. A low-rent similar effect can be
7033 gotten by setting this variable to @code{some}. Gnus will then look at
7034 the complete @code{References} headers of all articles and try to string
7035 together articles that belong in the same thread. This will leave
7036 @dfn{gaps} in the threading display where Gnus guesses that an article
7037 is missing from the thread. (These gaps appear like normal summary
7038 lines. If you select a gap, Gnus will try to fetch the article in
7039 question.) If this variable is @code{t}, Gnus will display all these
7040 ``gaps'' without regard for whether they are useful for completing the
7041 thread or not. Finally, if this variable is @code{more}, Gnus won't cut
7042 off sparse leaf nodes that don't lead anywhere. This variable is
7043 @code{nil} by default.
7045 @item gnus-read-all-available-headers
7046 @vindex gnus-read-all-available-headers
7047 This is a rather obscure variable that few will find useful. It's
7048 intended for those non-news newsgroups where the back end has to fetch
7049 quite a lot to present the summary buffer, and where it's impossible to
7050 go back to parents of articles. This is mostly the case in the
7053 If you don't use those, then it's safe to leave this as the default
7054 @code{nil}. If you want to use this variable, it should be a regexp
7055 that matches the group name, or @code{t} for all groups.
7060 @node More Threading
7061 @subsubsection More Threading
7064 @item gnus-show-threads
7065 @vindex gnus-show-threads
7066 If this variable is @code{nil}, no threading will be done, and all of
7067 the rest of the variables here will have no effect. Turning threading
7068 off will speed group selection up a bit, but it is sure to make reading
7069 slower and more awkward.
7071 @item gnus-thread-hide-subtree
7072 @vindex gnus-thread-hide-subtree
7073 If non-@code{nil}, all threads will be hidden when the summary buffer is
7076 This can also be a predicate specifier (@pxref{Predicate Specifiers}).
7077 Available predicates are @code{gnus-article-unread-p} and
7078 @code{gnus-article-unseen-p}.
7083 (setq gnus-thread-hide-subtree
7084 '(or gnus-article-unread-p
7085 gnus-article-unseen-p))
7088 (It's a pretty nonsensical example, since all unseen articles are also
7089 unread, but you get my drift.)
7092 @item gnus-thread-expunge-below
7093 @vindex gnus-thread-expunge-below
7094 All threads that have a total score (as defined by
7095 @code{gnus-thread-score-function}) less than this number will be
7096 expunged. This variable is @code{nil} by default, which means that no
7097 threads are expunged.
7099 @item gnus-thread-hide-killed
7100 @vindex gnus-thread-hide-killed
7101 if you kill a thread and this variable is non-@code{nil}, the subtree
7104 @item gnus-thread-ignore-subject
7105 @vindex gnus-thread-ignore-subject
7106 Sometimes somebody changes the subject in the middle of a thread. If
7107 this variable is non-@code{nil}, which is the default, the subject
7108 change is ignored. If it is @code{nil}, a change in the subject will
7109 result in a new thread.
7111 @item gnus-thread-indent-level
7112 @vindex gnus-thread-indent-level
7113 This is a number that says how much each sub-thread should be indented.
7116 @item gnus-sort-gathered-threads-function
7117 @vindex gnus-sort-gathered-threads-function
7118 Sometimes, particularly with mailing lists, the order in which mails
7119 arrive locally is not necessarily the same as the order in which they
7120 arrived on the mailing list. Consequently, when sorting sub-threads
7121 using the default @code{gnus-thread-sort-by-number}, responses can end
7122 up appearing before the article to which they are responding to.
7123 Setting this variable to an alternate value
7124 (e.g. @code{gnus-thread-sort-by-date}), in a group's parameters or in an
7125 appropriate hook (e.g. @code{gnus-summary-generate-hook}) can produce a
7126 more logical sub-thread ordering in such instances.
7131 @node Low-Level Threading
7132 @subsubsection Low-Level Threading
7136 @item gnus-parse-headers-hook
7137 @vindex gnus-parse-headers-hook
7138 Hook run before parsing any headers.
7140 @item gnus-alter-header-function
7141 @vindex gnus-alter-header-function
7142 If non-@code{nil}, this function will be called to allow alteration of
7143 article header structures. The function is called with one parameter,
7144 the article header vector, which it may alter in any way. For instance,
7145 if you have a mail-to-news gateway which alters the @code{Message-ID}s
7146 in systematic ways (by adding prefixes and such), you can use this
7147 variable to un-scramble the @code{Message-ID}s so that they are more
7148 meaningful. Here's one example:
7151 (setq gnus-alter-header-function 'my-alter-message-id)
7153 (defun my-alter-message-id (header)
7154 (let ((id (mail-header-id header)))
7156 "\\(<[^<>@@]*\\)\\.?cygnus\\..*@@\\([^<>@@]*>\\)" id)
7158 (concat (match-string 1 id) "@@" (match-string 2 id))
7165 @node Thread Commands
7166 @subsection Thread Commands
7167 @cindex thread commands
7173 @kindex T k (Summary)
7174 @kindex C-M-k (Summary)
7175 @findex gnus-summary-kill-thread
7176 Mark all articles in the current (sub-)thread as read
7177 (@code{gnus-summary-kill-thread}). If the prefix argument is positive,
7178 remove all marks instead. If the prefix argument is negative, tick
7183 @kindex T l (Summary)
7184 @kindex C-M-l (Summary)
7185 @findex gnus-summary-lower-thread
7186 Lower the score of the current (sub-)thread
7187 (@code{gnus-summary-lower-thread}).
7190 @kindex T i (Summary)
7191 @findex gnus-summary-raise-thread
7192 Increase the score of the current (sub-)thread
7193 (@code{gnus-summary-raise-thread}).
7196 @kindex T # (Summary)
7197 @findex gnus-uu-mark-thread
7198 Set the process mark on the current (sub-)thread
7199 (@code{gnus-uu-mark-thread}).
7202 @kindex T M-# (Summary)
7203 @findex gnus-uu-unmark-thread
7204 Remove the process mark from the current (sub-)thread
7205 (@code{gnus-uu-unmark-thread}).
7208 @kindex T T (Summary)
7209 @findex gnus-summary-toggle-threads
7210 Toggle threading (@code{gnus-summary-toggle-threads}).
7213 @kindex T s (Summary)
7214 @findex gnus-summary-show-thread
7215 Expose the (sub-)thread hidden under the current article, if any@*
7216 (@code{gnus-summary-show-thread}).
7219 @kindex T h (Summary)
7220 @findex gnus-summary-hide-thread
7221 Hide the current (sub-)thread (@code{gnus-summary-hide-thread}).
7224 @kindex T S (Summary)
7225 @findex gnus-summary-show-all-threads
7226 Expose all hidden threads (@code{gnus-summary-show-all-threads}).
7229 @kindex T H (Summary)
7230 @findex gnus-summary-hide-all-threads
7231 Hide all threads (@code{gnus-summary-hide-all-threads}).
7234 @kindex T t (Summary)
7235 @findex gnus-summary-rethread-current
7236 Re-thread the current article's thread
7237 (@code{gnus-summary-rethread-current}). This works even when the
7238 summary buffer is otherwise unthreaded.
7241 @kindex T ^ (Summary)
7242 @findex gnus-summary-reparent-thread
7243 Make the current article the child of the marked (or previous) article
7244 (@code{gnus-summary-reparent-thread}).
7247 @kindex T M-^ (Summary)
7248 @findex gnus-summary-reparent-children
7249 Make the current article the parent of the marked articles
7250 (@code{gnus-summary-reparent-children}).
7254 The following commands are thread movement commands. They all
7255 understand the numeric prefix.
7260 @kindex T n (Summary)
7262 @kindex C-M-n (Summary)
7264 @kindex M-down (Summary)
7265 @findex gnus-summary-next-thread
7266 Go to the next thread (@code{gnus-summary-next-thread}).
7269 @kindex T p (Summary)
7271 @kindex C-M-p (Summary)
7273 @kindex M-up (Summary)
7274 @findex gnus-summary-prev-thread
7275 Go to the previous thread (@code{gnus-summary-prev-thread}).
7278 @kindex T d (Summary)
7279 @findex gnus-summary-down-thread
7280 Descend the thread (@code{gnus-summary-down-thread}).
7283 @kindex T u (Summary)
7284 @findex gnus-summary-up-thread
7285 Ascend the thread (@code{gnus-summary-up-thread}).
7288 @kindex T o (Summary)
7289 @findex gnus-summary-top-thread
7290 Go to the top of the thread (@code{gnus-summary-top-thread}).
7293 @vindex gnus-thread-operation-ignore-subject
7294 If you ignore subject while threading, you'll naturally end up with
7295 threads that have several different subjects in them. If you then issue
7296 a command like @kbd{T k} (@code{gnus-summary-kill-thread}) you might not
7297 wish to kill the entire thread, but just those parts of the thread that
7298 have the same subject as the current article. If you like this idea,
7299 you can fiddle with @code{gnus-thread-operation-ignore-subject}. If it
7300 is non-@code{nil} (which it is by default), subjects will be ignored
7301 when doing thread commands. If this variable is @code{nil}, articles in
7302 the same thread with different subjects will not be included in the
7303 operation in question. If this variable is @code{fuzzy}, only articles
7304 that have subjects fuzzily equal will be included (@pxref{Fuzzy
7308 @node Sorting the Summary Buffer
7309 @section Sorting the Summary Buffer
7311 @findex gnus-thread-sort-by-total-score
7312 @findex gnus-thread-sort-by-date
7313 @findex gnus-thread-sort-by-score
7314 @findex gnus-thread-sort-by-subject
7315 @findex gnus-thread-sort-by-author
7316 @findex gnus-thread-sort-by-recipient
7317 @findex gnus-thread-sort-by-number
7318 @findex gnus-thread-sort-by-random
7319 @vindex gnus-thread-sort-functions
7320 @findex gnus-thread-sort-by-most-recent-number
7321 @findex gnus-thread-sort-by-most-recent-date
7322 If you are using a threaded summary display, you can sort the threads by
7323 setting @code{gnus-thread-sort-functions}, which can be either a single
7324 function, a list of functions, or a list containing functions and
7325 @code{(not some-function)} elements.
7327 By default, sorting is done on article numbers. Ready-made sorting
7328 predicate functions include @code{gnus-thread-sort-by-number},
7329 @code{gnus-thread-sort-by-author}, @code{gnus-thread-sort-by-recipient},
7330 @code{gnus-thread-sort-by-subject},
7331 @code{gnus-thread-sort-by-date},
7332 @code{gnus-thread-sort-by-score},
7333 @code{gnus-thread-sort-by-most-recent-number},
7334 @code{gnus-thread-sort-by-most-recent-date},
7335 @code{gnus-thread-sort-by-random} and
7336 @code{gnus-thread-sort-by-total-score}.
7338 Each function takes two threads and returns non-@code{nil} if the first
7339 thread should be sorted before the other. Note that sorting really is
7340 normally done by looking only at the roots of each thread. Exceptions
7341 to this rule are @code{gnus-thread-sort-by-most-recent-number} and
7342 @code{gnus-thread-sort-by-most-recent-date}.
7344 If you use more than one function, the primary sort key should be the
7345 last function in the list. You should probably always include
7346 @code{gnus-thread-sort-by-number} in the list of sorting
7347 functions---preferably first. This will ensure that threads that are
7348 equal with respect to the other sort criteria will be displayed in
7349 ascending article order.
7351 If you would like to sort by reverse score, then by subject, and finally
7352 by number, you could do something like:
7355 (setq gnus-thread-sort-functions
7356 '(gnus-thread-sort-by-number
7357 gnus-thread-sort-by-subject
7358 (not gnus-thread-sort-by-total-score)))
7361 The threads that have highest score will be displayed first in the
7362 summary buffer. When threads have the same score, they will be sorted
7363 alphabetically. The threads that have the same score and the same
7364 subject will be sorted by number, which is (normally) the sequence in
7365 which the articles arrived.
7367 If you want to sort by score and then reverse arrival order, you could
7371 (setq gnus-thread-sort-functions
7372 '((not gnus-thread-sort-by-number)
7373 gnus-thread-sort-by-score))
7376 @vindex gnus-thread-score-function
7377 The function in the @code{gnus-thread-score-function} variable (default