1 \input texinfo @c -*-texinfo-*- -*- coding: iso-latin-1 -*-
10 * Gnus: (gnus). The newsreader Gnus.
15 @setchapternewpage odd
19 \documentclass[twoside,a4paper,openright,11pt]{book}
20 \usepackage[latin1]{inputenc}
21 \usepackage{pagestyle}
29 \newcommand{\gnuschaptername}{}
30 \newcommand{\gnussectionname}{}
32 \newcommand{\gnusbackslash}{/}
34 \newcommand{\gnusref}[1]{``#1'' on page \pageref{#1}}
35 \newcommand{\gnusuref}[1]{\gnustt{#1}}
36 \newcommand{\gnusxref}[1]{See ``#1'' on page \pageref{#1}}
37 \newcommand{\gnuspxref}[1]{see ``#1'' on page \pageref{#1}}
39 \newcommand{\gnuskindex}[1]{\index{#1}}
40 \newcommand{\gnusindex}[1]{\index{#1}}
42 \newcommand{\gnustt}[1]{{\fontfamily{pfu}\fontsize{10pt}{10}\selectfont #1}}
43 \newcommand{\gnuscode}[1]{\gnustt{#1}}
44 \newcommand{\gnussamp}[1]{``{\fontencoding{OT1}\fontfamily{pfu}\fontsize{10pt}{10}\selectfont #1}''}
45 \newcommand{\gnuslisp}[1]{\gnustt{#1}}
46 \newcommand{\gnuskbd}[1]{`\gnustt{#1}'}
47 \newcommand{\gnusfile}[1]{`\gnustt{#1}'}
48 \newcommand{\gnusdfn}[1]{\textit{#1}}
49 \newcommand{\gnusi}[1]{\textit{#1}}
50 \newcommand{\gnusstrong}[1]{\textbf{#1}}
51 \newcommand{\gnusemph}[1]{\textit{#1}}
52 \newcommand{\gnusvar}[1]{{\fontsize{10pt}{10}\selectfont\textsl{\textsf{#1}}}}
53 \newcommand{\gnussc}[1]{\textsc{#1}}
54 \newcommand{\gnustitle}[1]{{\huge\textbf{#1}}}
55 \newcommand{\gnusauthor}[1]{{\large\textbf{#1}}}
56 \newcommand{\gnusresult}[1]{\gnustt{=> #1}}
58 \newcommand{\gnusbullet}{{${\bullet}$}}
59 \newcommand{\gnusdollar}{\$}
60 \newcommand{\gnusampersand}{\&}
61 \newcommand{\gnuspercent}{\%}
62 \newcommand{\gnushash}{\#}
63 \newcommand{\gnushat}{\symbol{"5E}}
64 \newcommand{\gnusunderline}{\symbol{"5F}}
65 \newcommand{\gnusnot}{$\neg$}
66 \newcommand{\gnustilde}{\symbol{"7E}}
67 \newcommand{\gnusless}{{$<$}}
68 \newcommand{\gnusgreater}{{$>$}}
69 \newcommand{\gnusbraceleft}{{$>$}}
70 \newcommand{\gnusbraceright}{{$>$}}
72 \newcommand{\gnushead}{\raisebox{-1cm}{\epsfig{figure=ps/gnus-head.ps,height=1cm}}}
73 \newcommand{\gnusinteresting}{
74 \marginpar[\mbox{}\hfill\gnushead]{\gnushead}
77 \newcommand{\gnuscleardoublepage}{\ifodd\count0\mbox{}\clearpage\thispagestyle{empty}\mbox{}\clearpage\else\clearpage\fi}
79 \newcommand{\gnuspagechapter}[1]{
86 \newcommand{\gnuschapter}[2]{
88 \ifdim \gnusdimen = 0pt\setcounter{page}{1}\pagestyle{gnus}\pagenumbering{arabic} \gnusdimen 1pt\fi
90 \renewcommand{\gnussectionname}{}
91 \renewcommand{\gnuschaptername}{#2}
94 \begin{picture}(500,500)(0,0)
95 \put(480,350){\makebox(0,0)[tr]{#1}}
96 \put(40,300){\makebox(500,50)[bl]{{\Huge\bf{#2}}}}
101 \newcommand{\gnusfigure}[3]{
103 \mbox{}\ifodd\count0\hspace*{-0.8cm}\else\hspace*{-3cm}\fi\begin{picture}(440,#2)
110 \newcommand{\gnusicon}[1]{
111 \marginpar[\mbox{}\hfill\raisebox{-1.5cm}{\epsfig{figure=ps/#1-up.ps,height=1.5cm}}]{\raisebox{-1cm}{\epsfig{figure=ps/#1-up.ps,height=1cm}}}
114 \newcommand{\gnuspicon}[1]{
115 \margindex{\epsfig{figure=#1,width=2cm}}
118 \newcommand{\gnusxface}[2]{
119 \margindex{\epsfig{figure=#1,width=1cm}\epsfig{figure=#2,width=1cm}}
122 \newcommand{\gnussmiley}[2]{
123 \margindex{\makebox[2cm]{\hfill\epsfig{figure=#1,width=0.5cm}\hfill\epsfig{figure=#2,width=0.5cm}\hfill}}
126 \newcommand{\gnusitemx}[1]{\mbox{}\vspace*{-\itemsep}\vspace*{-\parsep}\item#1}
128 \newcommand{\gnussection}[1]{
129 \renewcommand{\gnussectionname}{#1}
133 \newenvironment{codelist}%
138 \newenvironment{kbdlist}%
144 \newenvironment{dfnlist}%
149 \newenvironment{stronglist}%
154 \newenvironment{samplist}%
159 \newenvironment{varlist}%
164 \newenvironment{emphlist}%
169 \newlength\gnusheadtextwidth
170 \setlength{\gnusheadtextwidth}{\headtextwidth}
171 \addtolength{\gnusheadtextwidth}{1cm}
173 \newpagestyle{gnuspreamble}%
178 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\mbox{}}\textbf{\hfill\roman{page}}}
182 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\roman{page}\hfill\mbox{}}}
191 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo.ps,height=1cm}}
193 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo.ps,height=1cm}}
198 \newpagestyle{gnusindex}%
203 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\gnuschaptername\hfill\arabic{page}}}}
207 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}
215 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo.ps,height=1cm}}
217 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo.ps,height=1cm}}
227 \makebox[12cm]{\hspace*{3.1cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{chapter}.\arabic{section}} \textbf{\gnussectionname\hfill\arabic{page}}}}}
231 \makebox[12cm]{\hspace*{-2.95cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}}
239 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo.ps,height=1cm}}
241 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo.ps,height=1cm}}
246 \pagenumbering{roman}
247 \pagestyle{gnuspreamble}
257 %\addtolength{\oddsidemargin}{-5cm}
258 %\addtolength{\evensidemargin}{-5cm}
260 \addtolength{\textheight}{2cm}
262 \gnustitle{\gnustitlename}\\
265 \hspace*{0cm}\epsfig{figure=ps/gnus-big-logo.ps,height=15cm}
268 \gnusauthor{by Lars Magne Ingebrigtsen}
275 \thispagestyle{empty}
277 Copyright \copyright{} 1995, 1996, 1997, 1998, 1999, 2000
278 Free Software Foundation, Inc.
281 Permission is granted to copy, distribute and/or modify this document
282 under the terms of the GNU Free Documentation License, Version 1.1 or
283 any later version published by the Free Software Foundation; with no
284 Invariant Sections, with the Front-Cover texts being ``A GNU
285 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
286 license is included in the section entitled ``GNU Free Documentation
287 License'' in the Emacs manual.
289 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
290 this GNU Manual, like GNU software. Copies published by the Free
291 Software Foundation raise funds for GNU development.''
293 This document is part of a collection distributed under the GNU Free
294 Documentation License. If you want to distribute this document
295 separately from the collection, you can do so by adding a copy of the
296 license to the document, as described in section 6 of the license.
304 This file documents Gnus, the GNU Emacs newsreader.
306 Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000 Free Software Foundation, Inc.
308 Permission is granted to copy, distribute and/or modify this document
309 under the terms of the GNU Free Documentation License, Version 1.1 or
310 any later version published by the Free Software Foundation; with the
311 Invariant Sections being none, with the Front-Cover texts being ``A GNU
312 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
313 license is included in the section entitled ``GNU Free Documentation
314 License'' in the Emacs manual.
316 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
317 this GNU Manual, like GNU software. Copies published by the Free
318 Software Foundation raise funds for GNU development.''
320 This document is part of a collection distributed under the GNU Free
321 Documentation License. If you want to distribute this document
322 separately from the collection, you can do so by adding a copy of the
323 license to the document, as described in section 6 of the license.
331 @author by Lars Magne Ingebrigtsen
334 @vskip 0pt plus 1filll
335 Copyright @copyright{} 1995, 1996, 1997, 1998, 1999, 2000 Free Software Foundation, Inc.
337 Permission is granted to copy, distribute and/or modify this document
338 under the terms of the GNU Free Documentation License, Version 1.1 or
339 any later version published by the Free Software Foundation; with no
340 Invariant Sections, with the Front-Cover texts being ``A GNU
341 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
342 license is included in the section entitled ``GNU Free Documentation
343 License'' in the Emacs manual.
345 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
346 this GNU Manual, like GNU software. Copies published by the Free
347 Software Foundation raise funds for GNU development.''
349 This document is part of a collection distributed under the GNU Free
350 Documentation License. If you want to distribute this document
351 separately from the collection, you can do so by adding a copy of the
352 license to the document, as described in section 6 of the license.
361 @top The Gnus Newsreader
365 You can read news (and mail) from within Emacs by using Gnus. The news
366 can be gotten by any nefarious means you can think of---@sc{nntp}, local
367 spool or your mbox file. All at the same time, if you want to push your
370 This manual corresponds to Oort Gnus v.
381 Gnus is the advanced, self-documenting, customizable, extensible
382 unreal-time newsreader for GNU Emacs.
384 Oops. That sounds oddly familiar, so let's start over again to avoid
385 being accused of plagiarism:
387 Gnus is a message-reading laboratory. It will let you look at just
388 about anything as if it were a newsgroup. You can read mail with it,
389 you can browse directories with it, you can @code{ftp} with it---you
390 can even read news with it!
392 Gnus tries to empower people who read news the same way Emacs empowers
393 people who edit text. Gnus sets no limits to what the user should be
394 allowed to do. Users are encouraged to extend Gnus to make it behave
395 like they want it to behave. A program should not control people;
396 people should be empowered to do what they want by using (or abusing)
402 * Starting Up:: Finding news can be a pain.
403 * Group Buffer:: Selecting, subscribing and killing groups.
404 * Summary Buffer:: Reading, saving and posting articles.
405 * Article Buffer:: Displaying and handling articles.
406 * Composing Messages:: Information on sending mail and news.
407 * Select Methods:: Gnus reads all messages from various select methods.
408 * Scoring:: Assigning values to articles.
409 * Various:: General purpose settings.
410 * The End:: Farewell and goodbye.
411 * Appendices:: Terminology, Emacs intro, FAQ, History, Internals.
412 * Index:: Variable, function and concept index.
413 * Key Index:: Key Index.
416 --- The Detailed Node Listing ---
420 * Finding the News:: Choosing a method for getting news.
421 * The First Time:: What does Gnus do the first time you start it?
422 * The Server is Down:: How can I read my mail then?
423 * Slave Gnusae:: You can have more than one Gnus active at a time.
424 * Fetching a Group:: Starting Gnus just to read a group.
425 * New Groups:: What is Gnus supposed to do with new groups?
426 * Changing Servers:: You may want to move from one server to another.
427 * Startup Files:: Those pesky startup files---@file{.newsrc}.
428 * Auto Save:: Recovering from a crash.
429 * The Active File:: Reading the active file over a slow line Takes Time.
430 * Startup Variables:: Other variables you might change.
434 * Checking New Groups:: Determining what groups are new.
435 * Subscription Methods:: What Gnus should do with new groups.
436 * Filtering New Groups:: Making Gnus ignore certain new groups.
440 * Group Buffer Format:: Information listed and how you can change it.
441 * Group Maneuvering:: Commands for moving in the group buffer.
442 * Selecting a Group:: Actually reading news.
443 * Subscription Commands:: Unsubscribing, killing, subscribing.
444 * Group Data:: Changing the info for a group.
445 * Group Levels:: Levels? What are those, then?
446 * Group Score:: A mechanism for finding out what groups you like.
447 * Marking Groups:: You can mark groups for later processing.
448 * Foreign Groups:: Creating and editing groups.
449 * Group Parameters:: Each group may have different parameters set.
450 * Listing Groups:: Gnus can list various subsets of the groups.
451 * Sorting Groups:: Re-arrange the group order.
452 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
453 * Browse Foreign Server:: You can browse a server. See what it has to offer.
454 * Exiting Gnus:: Stop reading news and get some work done.
455 * Group Topics:: A folding group mode divided into topics.
456 * Misc Group Stuff:: Other stuff that you can to do.
460 * Group Line Specification:: Deciding how the group buffer is to look.
461 * Group Modeline Specification:: The group buffer modeline.
462 * Group Highlighting:: Having nice colors in the group buffer.
466 * Topic Variables:: How to customize the topics the Lisp Way.
467 * Topic Commands:: Interactive E-Z commands.
468 * Topic Sorting:: Sorting each topic individually.
469 * Topic Topology:: A map of the world.
470 * Topic Parameters:: Parameters that apply to all groups in a topic.
474 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
475 * Group Information:: Information and help on groups and Gnus.
476 * Group Timestamp:: Making Gnus keep track of when you last read a group.
477 * File Commands:: Reading and writing the Gnus files.
481 * Summary Buffer Format:: Deciding how the summary buffer is to look.
482 * Summary Maneuvering:: Moving around the summary buffer.
483 * Choosing Articles:: Reading articles.
484 * Paging the Article:: Scrolling the current article.
485 * Reply Followup and Post:: Posting articles.
487 * Marking Articles:: Marking articles as read, expirable, etc.
488 * Limiting:: You can limit the summary buffer.
489 * Threading:: How threads are made.
490 * Sorting the Summary Buffer:: How articles and threads are sorted.
491 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
492 * Article Caching:: You may store articles in a cache.
493 * Persistent Articles:: Making articles expiry-resistant.
494 * Article Backlog:: Having already read articles hang around.
495 * Saving Articles:: Ways of customizing article saving.
496 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
497 * Article Treatment:: The article buffer can be mangled at will.
498 * MIME Commands:: Doing MIMEy things with the articles.
499 * Charsets:: Character set issues.
500 * Article Commands:: Doing various things with the article buffer.
501 * Summary Sorting:: Sorting the summary buffer in various ways.
502 * Finding the Parent:: No child support? Get the parent.
503 * Alternative Approaches:: Reading using non-default summaries.
504 * Tree Display:: A more visual display of threads.
505 * Mail Group Commands:: Some commands can only be used in mail groups.
506 * Various Summary Stuff:: What didn't fit anywhere else.
507 * Exiting the Summary Buffer:: Returning to the Group buffer,
508 or reselecting the current group.
509 * Crosspost Handling:: How crossposted articles are dealt with.
510 * Duplicate Suppression:: An alternative when crosspost handling fails.
511 * Security:: Decrypt and Verify.
512 * Mailing List:: Mailing list minor mode.
514 Summary Buffer Format
516 * Summary Buffer Lines:: You can specify how summary lines should look.
517 * To From Newsgroups:: How to not display your own name.
518 * Summary Buffer Mode Line:: You can say how the mode line should look.
519 * Summary Highlighting:: Making the summary buffer all pretty and nice.
523 * Choosing Commands:: Commands for choosing articles.
524 * Choosing Variables:: Variables that influence these commands.
526 Reply, Followup and Post
528 * Summary Mail Commands:: Sending mail.
529 * Summary Post Commands:: Sending news.
530 * Summary Message Commands:: Other Message-related commands.
531 * Canceling and Superseding::
535 * Unread Articles:: Marks for unread articles.
536 * Read Articles:: Marks for read articles.
537 * Other Marks:: Marks that do not affect readedness.
539 * Generic Marking Commands::
540 * Setting Process Marks::
544 * Setting Marks:: How to set and remove marks.
545 * Generic Marking Commands:: How to customize the marking.
546 * Setting Process Marks:: How to mark articles for later processing.
550 * Customizing Threading:: Variables you can change to affect the threading.
551 * Thread Commands:: Thread based commands in the summary buffer.
553 Customizing Threading
555 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
556 * Filling In Threads:: Making the threads displayed look fuller.
557 * More Threading:: Even more variables for fiddling with threads.
558 * Low-Level Threading:: You thought it was over... but you were wrong!
562 * Uuencoded Articles:: Uudecode articles.
563 * Shell Archives:: Unshar articles.
564 * PostScript Files:: Split PostScript.
565 * Other Files:: Plain save and binhex.
566 * Decoding Variables:: Variables for a happy decoding.
567 * Viewing Files:: You want to look at the result of the decoding?
571 * Rule Variables:: Variables that say how a file is to be viewed.
572 * Other Decode Variables:: Other decode variables.
573 * Uuencoding and Posting:: Variables for customizing uuencoding.
577 * Article Highlighting:: You want to make the article look like fruit salad.
578 * Article Fontisizing:: Making emphasized text look nice.
579 * Article Hiding:: You also want to make certain info go away.
580 * Article Washing:: Lots of way-neat functions to make life better.
581 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
582 * Article Date:: Grumble, UT!
583 * Article Signature:: What is a signature?
584 * Article Miscellania:: Various other stuff.
586 Alternative Approaches
588 * Pick and Read:: First mark articles and then read them.
589 * Binary Groups:: Auto-decode all articles.
591 Various Summary Stuff
593 * Summary Group Information:: Information oriented commands.
594 * Searching for Articles:: Multiple article commands.
595 * Summary Generation Commands::
596 * Really Various Summary Commands:: Those pesky non-conformant commands.
600 * Hiding Headers:: Deciding what headers should be displayed.
601 * Using MIME:: Pushing articles through @sc{mime} before reading them.
602 * Customizing Articles:: Tailoring the look of the articles.
603 * Article Keymap:: Keystrokes available in the article buffer.
604 * Misc Article:: Other stuff.
608 * Mail:: Mailing and replying.
609 * Posting Server:: What server should you post via?
610 * Mail and Post:: Mailing and posting at the same time.
611 * Archived Messages:: Where Gnus stores the messages you've sent.
612 * Posting Styles:: An easier way to specify who you are.
613 * Drafts:: Postponing messages and rejected messages.
614 * Rejected Articles:: What happens if the server doesn't like your article?
615 * Using GPG:: How to use GPG and MML to sign and encrypt messages
619 * Server Buffer:: Making and editing virtual servers.
620 * Getting News:: Reading USENET news with Gnus.
621 * Getting Mail:: Reading your personal mail with Gnus.
622 * Browsing the Web:: Getting messages from a plethora of Web sources.
623 * IMAP:: Using Gnus as a @sc{imap} client.
624 * Other Sources:: Reading directories, files, SOUP packets.
625 * Combined Groups:: Combining groups into one group.
626 * Gnus Unplugged:: Reading news and mail offline.
630 * Server Buffer Format:: You can customize the look of this buffer.
631 * Server Commands:: Commands to manipulate servers.
632 * Example Methods:: Examples server specifications.
633 * Creating a Virtual Server:: An example session.
634 * Server Variables:: Which variables to set.
635 * Servers and Methods:: You can use server names as select methods.
636 * Unavailable Servers:: Some servers you try to contact may be down.
640 * NNTP:: Reading news from an @sc{nntp} server.
641 * News Spool:: Reading news from the local spool.
645 * Direct Functions:: Connecting directly to the server.
646 * Indirect Functions:: Connecting indirectly to the server.
647 * Common Variables:: Understood by several connection functions.
651 * Mail in a Newsreader:: Important introductory notes.
652 * Getting Started Reading Mail:: A simple cookbook example.
653 * Splitting Mail:: How to create mail groups.
654 * Mail Sources:: How to tell Gnus where to get mail from.
655 * Mail Back End Variables:: Variables for customizing mail handling.
656 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
657 * Group Mail Splitting:: Use group customize to drive mail splitting.
658 * Incorporating Old Mail:: What about the old mail you have?
659 * Expiring Mail:: Getting rid of unwanted mail.
660 * Washing Mail:: Removing gruft from the mail you get.
661 * Duplicates:: Dealing with duplicated mail.
662 * Not Reading Mail:: Using mail back ends for reading other files.
663 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
664 * Archiving Mail:: How to backup your mail.
668 * Mail Source Specifiers:: How to specify what a mail source is.
669 * Mail Source Customization:: Some variables that influence things.
670 * Fetching Mail:: Using the mail source specifiers.
672 Choosing a Mail Back End
674 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
675 * Rmail Babyl:: Emacs programs use the rmail babyl format.
676 * Mail Spool:: Store your mail in a private spool?
677 * MH Spool:: An mhspool-like back end.
678 * Mail Folders:: Having one file for each group.
679 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
683 * Web Searches:: Creating groups from articles that match a string.
684 * Slashdot:: Reading the Slashdot comments.
685 * Ultimate:: The Ultimate Bulletin Board systems.
686 * Web Archive:: Reading mailing list archived on web.
687 * RSS:: Reading RDF site summary.
688 * Customizing w3:: Doing stuff to Emacs/w3 from Gnus.
692 * Splitting in IMAP:: Splitting mail with nnimap.
693 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
694 * Expunging mailboxes:: Equivalent of a "compress mailbox" button.
698 * Directory Groups:: You can read a directory as if it was a newsgroup.
699 * Anything Groups:: Dired? Who needs dired?
700 * Document Groups:: Single files can be the basis of a group.
701 * SOUP:: Reading @sc{soup} packets ``offline''.
702 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
706 * Document Server Internals:: How to add your own document types.
710 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
711 * SOUP Groups:: A back end for reading @sc{soup} packets.
712 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
716 * Virtual Groups:: Combining articles from many groups.
717 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
721 * Agent Basics:: How it all is supposed to work.
722 * Agent Categories:: How to tell the Gnus Agent what to download.
723 * Agent Commands:: New commands for all the buffers.
724 * Agent Expiry:: How to make old articles go away.
725 * Agent and IMAP:: How to use the Agent with IMAP.
726 * Outgoing Messages:: What happens when you post/mail something?
727 * Agent Variables:: Customizing is fun.
728 * Example Setup:: An example @file{.gnus.el} file for offline people.
729 * Batching Agents:: How to fetch news from a @code{cron} job.
730 * Agent Caveats:: What you think it'll do and what it does.
734 * Category Syntax:: What a category looks like.
735 * Category Buffer:: A buffer for maintaining categories.
736 * Category Variables:: Customize'r'Us.
740 * Group Agent Commands::
741 * Summary Agent Commands::
742 * Server Agent Commands::
746 * Summary Score Commands:: Adding score entries for the current group.
747 * Group Score Commands:: General score commands.
748 * Score Variables:: Customize your scoring. (My, what terminology).
749 * Score File Format:: What a score file may contain.
750 * Score File Editing:: You can edit score files by hand as well.
751 * Adaptive Scoring:: Big Sister Gnus knows what you read.
752 * Home Score File:: How to say where new score entries are to go.
753 * Followups To Yourself:: Having Gnus notice when people answer you.
754 * Scoring On Other Headers:: Scoring on non-standard headers.
755 * Scoring Tips:: How to score effectively.
756 * Reverse Scoring:: That problem child of old is not problem.
757 * Global Score Files:: Earth-spanning, ear-splitting score files.
758 * Kill Files:: They are still here, but they can be ignored.
759 * Converting Kill Files:: Translating kill files to score files.
760 * GroupLens:: Getting predictions on what you like to read.
761 * Advanced Scoring:: Using logical expressions to build score rules.
762 * Score Decays:: It can be useful to let scores wither away.
766 * Using GroupLens:: How to make Gnus use GroupLens.
767 * Rating Articles:: Letting GroupLens know how you rate articles.
768 * Displaying Predictions:: Displaying predictions given by GroupLens.
769 * GroupLens Variables:: Customizing GroupLens.
773 * Advanced Scoring Syntax:: A definition.
774 * Advanced Scoring Examples:: What they look like.
775 * Advanced Scoring Tips:: Getting the most out of it.
779 * Process/Prefix:: A convention used by many treatment commands.
780 * Interactive:: Making Gnus ask you many questions.
781 * Symbolic Prefixes:: How to supply some Gnus functions with options.
782 * Formatting Variables:: You can specify what buffers should look like.
783 * Window Layout:: Configuring the Gnus buffer windows.
784 * Faces and Fonts:: How to change how faces look.
785 * Compilation:: How to speed Gnus up.
786 * Mode Lines:: Displaying information in the mode lines.
787 * Highlighting and Menus:: Making buffers look all nice and cozy.
788 * Buttons:: Get tendinitis in ten easy steps!
789 * Daemons:: Gnus can do things behind your back.
790 * NoCeM:: How to avoid spam and other fatty foods.
791 * Undo:: Some actions can be undone.
792 * Moderation:: What to do if you're a moderator.
793 * XEmacs Enhancements:: There are more pictures and stuff under XEmacs.
794 * Fuzzy Matching:: What's the big fuzz?
795 * Thwarting Email Spam:: A how-to on avoiding unsolicited commercial email.
796 * Various Various:: Things that are really various.
800 * Formatting Basics:: A formatting variable is basically a format string.
801 * Mode Line Formatting:: Some rules about mode line formatting variables.
802 * Advanced Formatting:: Modifying output in various ways.
803 * User-Defined Specs:: Having Gnus call your own functions.
804 * Formatting Fonts:: Making the formatting look colorful and nice.
805 * Positioning Point:: Moving point to a position after an operation.
806 * Tabulation:: Tabulating your output.
807 * Wide Characters:: Dealing with wide characters.
811 * Picons:: How to display pictures of what your reading.
812 * Smileys:: Show all those happy faces the way they were meant to be shown.
813 * Toolbar:: Click'n'drool.
814 * XVarious:: Other XEmacsy Gnusey variables.
818 * Picon Basics:: What are picons and How do I get them.
819 * Picon Requirements:: Don't go further if you aren't using XEmacs.
820 * Easy Picons:: Displaying Picons---the easy way.
821 * Hard Picons:: The way you should do it. You'll learn something.
822 * Picon Useless Configuration:: Other variables you can trash/tweak/munge/play with.
826 * History:: How Gnus got where it is today.
827 * On Writing Manuals:: Why this is not a beginner's guide.
828 * Terminology:: We use really difficult, like, words here.
829 * Customization:: Tailoring Gnus to your needs.
830 * Troubleshooting:: What you might try if things do not work.
831 * Gnus Reference Guide:: Rilly, rilly technical stuff.
832 * Emacs for Heathens:: A short introduction to Emacsian terms.
836 * Gnus Versions:: What Gnus versions have been released.
837 * Other Gnus Versions:: Other Gnus versions that also have been released.
838 * Why?:: What's the point of Gnus?
839 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
840 * Conformity:: Gnus tries to conform to all standards.
841 * Emacsen:: Gnus can be run on a few modern Emacsen.
842 * Gnus Development:: How Gnus is developed.
843 * Contributors:: Oodles of people.
844 * New Features:: Pointers to some of the new stuff in Gnus.
848 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
849 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
850 * Red Gnus:: Third time best---Gnus 5.4/5.5.
851 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
852 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
856 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
857 * Slow Terminal Connection:: You run a remote Emacs.
858 * Little Disk Space:: You feel that having large setup files is icky.
859 * Slow Machine:: You feel like buying a faster machine.
863 * Gnus Utility Functions:: Common functions and variable to use.
864 * Back End Interface:: How Gnus communicates with the servers.
865 * Score File Syntax:: A BNF definition of the score file standard.
866 * Headers:: How Gnus stores headers internally.
867 * Ranges:: A handy format for storing mucho numbers.
868 * Group Info:: The group info format.
869 * Extended Interactive:: Symbolic prefixes and stuff.
870 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
871 * Various File Formats:: Formats of files that Gnus use.
875 * Required Back End Functions:: Functions that must be implemented.
876 * Optional Back End Functions:: Functions that need not be implemented.
877 * Error Messaging:: How to get messages and report errors.
878 * Writing New Back Ends:: Extending old back ends.
879 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
880 * Mail-like Back Ends:: Some tips on mail back ends.
884 * Active File Format:: Information on articles and groups available.
885 * Newsgroups File Format:: Group descriptions.
889 * Keystrokes:: Entering text and executing commands.
890 * Emacs Lisp:: The built-in Emacs programming language.
896 @chapter Starting Gnus
901 If your system administrator has set things up properly, starting Gnus
902 and reading news is extremely easy---you just type @kbd{M-x gnus} in
905 @findex gnus-other-frame
906 @kindex M-x gnus-other-frame
907 If you want to start Gnus in a different frame, you can use the command
908 @kbd{M-x gnus-other-frame} instead.
910 If things do not go smoothly at startup, you have to twiddle some
911 variables in your @file{~/.gnus} file. This file is similar to
912 @file{~/.emacs}, but is read when gnus starts.
914 If you puzzle at any terms used in this manual, please refer to the
915 terminology section (@pxref{Terminology}).
918 * Finding the News:: Choosing a method for getting news.
919 * The First Time:: What does Gnus do the first time you start it?
920 * The Server is Down:: How can I read my mail then?
921 * Slave Gnusae:: You can have more than one Gnus active at a time.
922 * Fetching a Group:: Starting Gnus just to read a group.
923 * New Groups:: What is Gnus supposed to do with new groups?
924 * Changing Servers:: You may want to move from one server to another.
925 * Startup Files:: Those pesky startup files---@file{.newsrc}.
926 * Auto Save:: Recovering from a crash.
927 * The Active File:: Reading the active file over a slow line Takes Time.
928 * Startup Variables:: Other variables you might change.
932 @node Finding the News
933 @section Finding the News
936 @vindex gnus-select-method
938 The @code{gnus-select-method} variable says where Gnus should look for
939 news. This variable should be a list where the first element says
940 @dfn{how} and the second element says @dfn{where}. This method is your
941 native method. All groups not fetched with this method are
944 For instance, if the @samp{news.somewhere.edu} @sc{nntp} server is where
945 you want to get your daily dosage of news from, you'd say:
948 (setq gnus-select-method '(nntp "news.somewhere.edu"))
951 If you want to read directly from the local spool, say:
954 (setq gnus-select-method '(nnspool ""))
957 If you can use a local spool, you probably should, as it will almost
958 certainly be much faster.
960 @vindex gnus-nntpserver-file
962 @cindex @sc{nntp} server
963 If this variable is not set, Gnus will take a look at the
964 @code{NNTPSERVER} environment variable. If that variable isn't set,
965 Gnus will see whether @code{gnus-nntpserver-file}
966 (@file{/etc/nntpserver} by default) has any opinions on the matter. If
967 that fails as well, Gnus will try to use the machine running Emacs as an @sc{nntp} server. That's a long shot, though.
969 @vindex gnus-nntp-server
970 If @code{gnus-nntp-server} is set, this variable will override
971 @code{gnus-select-method}. You should therefore set
972 @code{gnus-nntp-server} to @code{nil}, which is what it is by default.
974 @vindex gnus-secondary-servers
975 @vindex gnus-nntp-server
976 You can also make Gnus prompt you interactively for the name of an
977 @sc{nntp} server. If you give a non-numerical prefix to @code{gnus}
978 (i.e., @kbd{C-u M-x gnus}), Gnus will let you choose between the servers
979 in the @code{gnus-secondary-servers} list (if any). You can also just
980 type in the name of any server you feel like visiting. (Note that this
981 will set @code{gnus-nntp-server}, which means that if you then @kbd{M-x
982 gnus} later in the same Emacs session, Gnus will contact the same
985 @findex gnus-group-browse-foreign-server
987 However, if you use one @sc{nntp} server regularly and are just
988 interested in a couple of groups from a different server, you would be
989 better served by using the @kbd{B} command in the group buffer. It will
990 let you have a look at what groups are available, and you can subscribe
991 to any of the groups you want to. This also makes @file{.newsrc}
992 maintenance much tidier. @xref{Foreign Groups}.
994 @vindex gnus-secondary-select-methods
996 A slightly different approach to foreign groups is to set the
997 @code{gnus-secondary-select-methods} variable. The select methods
998 listed in this variable are in many ways just as native as the
999 @code{gnus-select-method} server. They will also be queried for active
1000 files during startup (if that's required), and new newsgroups that
1001 appear on these servers will be subscribed (or not) just as native
1004 For instance, if you use the @code{nnmbox} back end to read your mail,
1005 you would typically set this variable to
1008 (setq gnus-secondary-select-methods '((nnmbox "")))
1012 @node The First Time
1013 @section The First Time
1014 @cindex first time usage
1016 If no startup files exist, Gnus will try to determine what groups should
1017 be subscribed by default.
1019 @vindex gnus-default-subscribed-newsgroups
1020 If the variable @code{gnus-default-subscribed-newsgroups} is set, Gnus
1021 will subscribe you to just those groups in that list, leaving the rest
1022 killed. Your system administrator should have set this variable to
1025 Since she hasn't, Gnus will just subscribe you to a few arbitrarily
1026 picked groups (i.e., @samp{*.newusers}). (@dfn{Arbitrary} is defined
1027 here as @dfn{whatever Lars thinks you should read}.)
1029 You'll also be subscribed to the Gnus documentation group, which should
1030 help you with most common problems.
1032 If @code{gnus-default-subscribed-newsgroups} is @code{t}, Gnus will just
1033 use the normal functions for handling new groups, and not do anything
1037 @node The Server is Down
1038 @section The Server is Down
1039 @cindex server errors
1041 If the default server is down, Gnus will understandably have some
1042 problems starting. However, if you have some mail groups in addition to
1043 the news groups, you may want to start Gnus anyway.
1045 Gnus, being the trusting sort of program, will ask whether to proceed
1046 without a native select method if that server can't be contacted. This
1047 will happen whether the server doesn't actually exist (i.e., you have
1048 given the wrong address) or the server has just momentarily taken ill
1049 for some reason or other. If you decide to continue and have no foreign
1050 groups, you'll find it difficult to actually do anything in the group
1051 buffer. But, hey, that's your problem. Blllrph!
1053 @findex gnus-no-server
1054 @kindex M-x gnus-no-server
1056 If you know that the server is definitely down, or you just want to read
1057 your mail without bothering with the server at all, you can use the
1058 @code{gnus-no-server} command to start Gnus. That might come in handy
1059 if you're in a hurry as well. This command will not attempt to contact
1060 your primary server---instead, it will just activate all groups on level
1061 1 and 2. (You should preferably keep no native groups on those two
1062 levels.) Also @pxref{Group Levels}.
1066 @section Slave Gnusae
1069 You might want to run more than one Emacs with more than one Gnus at the
1070 same time. If you are using different @file{.newsrc} files (e.g., if you
1071 are using the two different Gnusae to read from two different servers),
1072 that is no problem whatsoever. You just do it.
1074 The problem appears when you want to run two Gnusae that use the same
1075 @code{.newsrc} file.
1077 To work around that problem some, we here at the Think-Tank at the Gnus
1078 Towers have come up with a new concept: @dfn{Masters} and
1079 @dfn{slaves}. (We have applied for a patent on this concept, and have
1080 taken out a copyright on those words. If you wish to use those words in
1081 conjunction with each other, you have to send $1 per usage instance to
1082 me. Usage of the patent (@dfn{Master/Slave Relationships In Computer
1083 Applications}) will be much more expensive, of course.)
1085 Anyway, you start one Gnus up the normal way with @kbd{M-x gnus} (or
1086 however you do it). Each subsequent slave Gnusae should be started with
1087 @kbd{M-x gnus-slave}. These slaves won't save normal @file{.newsrc}
1088 files, but instead save @dfn{slave files} that contain information only
1089 on what groups have been read in the slave session. When a master Gnus
1090 starts, it will read (and delete) these slave files, incorporating all
1091 information from them. (The slave files will be read in the sequence
1092 they were created, so the latest changes will have precedence.)
1094 Information from the slave files has, of course, precedence over the
1095 information in the normal (i.e., master) @code{.newsrc} file.
1098 @node Fetching a Group
1099 @section Fetching a Group
1100 @cindex fetching a group
1102 @findex gnus-fetch-group
1103 It is sometimes convenient to be able to just say ``I want to read this
1104 group and I don't care whether Gnus has been started or not''. This is
1105 perhaps more useful for people who write code than for users, but the
1106 command @code{gnus-fetch-group} provides this functionality in any case.
1107 It takes the group name as a parameter.
1113 @cindex subscription
1115 @vindex gnus-check-new-newsgroups
1116 If you are satisfied that you really never want to see any new groups,
1117 you can set @code{gnus-check-new-newsgroups} to @code{nil}. This will
1118 also save you some time at startup. Even if this variable is
1119 @code{nil}, you can always subscribe to the new groups just by pressing
1120 @kbd{U} in the group buffer (@pxref{Group Maintenance}). This variable
1121 is @code{ask-server} by default. If you set this variable to
1122 @code{always}, then Gnus will query the back ends for new groups even
1123 when you do the @kbd{g} command (@pxref{Scanning New Messages}).
1126 * Checking New Groups:: Determining what groups are new.
1127 * Subscription Methods:: What Gnus should do with new groups.
1128 * Filtering New Groups:: Making Gnus ignore certain new groups.
1132 @node Checking New Groups
1133 @subsection Checking New Groups
1135 Gnus normally determines whether a group is new or not by comparing the
1136 list of groups from the active file(s) with the lists of subscribed and
1137 dead groups. This isn't a particularly fast method. If
1138 @code{gnus-check-new-newsgroups} is @code{ask-server}, Gnus will ask the
1139 server for new groups since the last time. This is both faster and
1140 cheaper. This also means that you can get rid of the list of killed
1141 groups altogether, so you may set @code{gnus-save-killed-list} to
1142 @code{nil}, which will save time both at startup, at exit, and all over.
1143 Saves disk space, too. Why isn't this the default, then?
1144 Unfortunately, not all servers support this command.
1146 I bet I know what you're thinking now: How do I find out whether my
1147 server supports @code{ask-server}? No? Good, because I don't have a
1148 fail-safe answer. I would suggest just setting this variable to
1149 @code{ask-server} and see whether any new groups appear within the next
1150 few days. If any do, then it works. If none do, then it doesn't
1151 work. I could write a function to make Gnus guess whether the server
1152 supports @code{ask-server}, but it would just be a guess. So I won't.
1153 You could @code{telnet} to the server and say @code{HELP} and see
1154 whether it lists @samp{NEWGROUPS} among the commands it understands. If
1155 it does, then it might work. (But there are servers that lists
1156 @samp{NEWGROUPS} without supporting the function properly.)
1158 This variable can also be a list of select methods. If so, Gnus will
1159 issue an @code{ask-server} command to each of the select methods, and
1160 subscribe them (or not) using the normal methods. This might be handy
1161 if you are monitoring a few servers for new groups. A side effect is
1162 that startup will take much longer, so you can meditate while waiting.
1163 Use the mantra ``dingnusdingnusdingnus'' to achieve permanent bliss.
1166 @node Subscription Methods
1167 @subsection Subscription Methods
1169 @vindex gnus-subscribe-newsgroup-method
1170 What Gnus does when it encounters a new group is determined by the
1171 @code{gnus-subscribe-newsgroup-method} variable.
1173 This variable should contain a function. This function will be called
1174 with the name of the new group as the only parameter.
1176 Some handy pre-fab functions are:
1180 @item gnus-subscribe-zombies
1181 @vindex gnus-subscribe-zombies
1182 Make all new groups zombies. This is the default. You can browse the
1183 zombies later (with @kbd{A z}) and either kill them all off properly
1184 (with @kbd{S z}), or subscribe to them (with @kbd{u}).
1186 @item gnus-subscribe-randomly
1187 @vindex gnus-subscribe-randomly
1188 Subscribe all new groups in arbitrary order. This really means that all
1189 new groups will be added at ``the top'' of the group buffer.
1191 @item gnus-subscribe-alphabetically
1192 @vindex gnus-subscribe-alphabetically
1193 Subscribe all new groups in alphabetical order.
1195 @item gnus-subscribe-hierarchically
1196 @vindex gnus-subscribe-hierarchically
1197 Subscribe all new groups hierarchically. The difference between this
1198 function and @code{gnus-subscribe-alphabetically} is slight.
1199 @code{gnus-subscribe-alphabetically} will subscribe new groups in a strictly
1200 alphabetical fashion, while this function will enter groups into its
1201 hierarchy. So if you want to have the @samp{rec} hierarchy before the
1202 @samp{comp} hierarchy, this function will not mess that configuration
1203 up. Or something like that.
1205 @item gnus-subscribe-interactively
1206 @vindex gnus-subscribe-interactively
1207 Subscribe new groups interactively. This means that Gnus will ask
1208 you about @strong{all} new groups. The groups you choose to subscribe
1209 to will be subscribed hierarchically.
1211 @item gnus-subscribe-killed
1212 @vindex gnus-subscribe-killed
1213 Kill all new groups.
1215 @item gnus-subscribe-topics
1216 @vindex gnus-subscribe-topics
1217 Put the groups into the topic that has a matching @code{subscribe} topic
1218 parameter (@pxref{Topic Parameters}). For instance, a @code{subscribe}
1219 topic parameter that looks like
1225 will mean that all groups that match that regex will be subscribed under
1228 If no topics match the groups, the groups will be subscribed in the
1233 @vindex gnus-subscribe-hierarchical-interactive
1234 A closely related variable is
1235 @code{gnus-subscribe-hierarchical-interactive}. (That's quite a
1236 mouthful.) If this variable is non-@code{nil}, Gnus will ask you in a
1237 hierarchical fashion whether to subscribe to new groups or not. Gnus
1238 will ask you for each sub-hierarchy whether you want to descend the
1241 One common mistake is to set the variable a few paragraphs above
1242 (@code{gnus-subscribe-newsgroup-method}) to
1243 @code{gnus-subscribe-hierarchical-interactive}. This is an error. This
1244 will not work. This is ga-ga. So don't do it.
1247 @node Filtering New Groups
1248 @subsection Filtering New Groups
1250 A nice and portable way to control which new newsgroups should be
1251 subscribed (or ignored) is to put an @dfn{options} line at the start of
1252 the @file{.newsrc} file. Here's an example:
1255 options -n !alt.all !rec.all sci.all
1258 @vindex gnus-subscribe-options-newsgroup-method
1259 This line obviously belongs to a serious-minded intellectual scientific
1260 person (or she may just be plain old boring), because it says that all
1261 groups that have names beginning with @samp{alt} and @samp{rec} should
1262 be ignored, and all groups with names beginning with @samp{sci} should
1263 be subscribed. Gnus will not use the normal subscription method for
1264 subscribing these groups.
1265 @code{gnus-subscribe-options-newsgroup-method} is used instead. This
1266 variable defaults to @code{gnus-subscribe-alphabetically}.
1268 @vindex gnus-options-not-subscribe
1269 @vindex gnus-options-subscribe
1270 If you don't want to mess with your @file{.newsrc} file, you can just
1271 set the two variables @code{gnus-options-subscribe} and
1272 @code{gnus-options-not-subscribe}. These two variables do exactly the
1273 same as the @file{.newsrc} @samp{options -n} trick. Both are regexps,
1274 and if the new group matches the former, it will be unconditionally
1275 subscribed, and if it matches the latter, it will be ignored.
1277 @vindex gnus-auto-subscribed-groups
1278 Yet another variable that meddles here is
1279 @code{gnus-auto-subscribed-groups}. It works exactly like
1280 @code{gnus-options-subscribe}, and is therefore really superfluous, but I
1281 thought it would be nice to have two of these. This variable is more
1282 meant for setting some ground rules, while the other variable is used
1283 more for user fiddling. By default this variable makes all new groups
1284 that come from mail back ends (@code{nnml}, @code{nnbabyl},
1285 @code{nnfolder}, @code{nnmbox}, and @code{nnmh}) subscribed. If you
1286 don't like that, just set this variable to @code{nil}.
1288 New groups that match this regexp are subscribed using
1289 @code{gnus-subscribe-options-newsgroup-method}.
1292 @node Changing Servers
1293 @section Changing Servers
1294 @cindex changing servers
1296 Sometimes it is necessary to move from one @sc{nntp} server to another.
1297 This happens very rarely, but perhaps you change jobs, or one server is
1298 very flaky and you want to use another.
1300 Changing the server is pretty easy, right? You just change
1301 @code{gnus-select-method} to point to the new server?
1305 Article numbers are not (in any way) kept synchronized between different
1306 @sc{nntp} servers, and the only way Gnus keeps track of what articles
1307 you have read is by keeping track of article numbers. So when you
1308 change @code{gnus-select-method}, your @file{.newsrc} file becomes
1311 Gnus provides a few functions to attempt to translate a @file{.newsrc}
1312 file from one server to another. They all have one thing in
1313 common---they take a looong time to run. You don't want to use these
1314 functions more than absolutely necessary.
1316 @kindex M-x gnus-change-server
1317 @findex gnus-change-server
1318 If you have access to both servers, Gnus can request the headers for all
1319 the articles you have read and compare @code{Message-ID}s and map the
1320 article numbers of the read articles and article marks. The @kbd{M-x
1321 gnus-change-server} command will do this for all your native groups. It
1322 will prompt for the method you want to move to.
1324 @kindex M-x gnus-group-move-group-to-server
1325 @findex gnus-group-move-group-to-server
1326 You can also move individual groups with the @kbd{M-x
1327 gnus-group-move-group-to-server} command. This is useful if you want to
1328 move a (foreign) group from one server to another.
1330 @kindex M-x gnus-group-clear-data-on-native-groups
1331 @findex gnus-group-clear-data-on-native-groups
1332 If you don't have access to both the old and new server, all your marks
1333 and read ranges have become worthless. You can use the @kbd{M-x
1334 gnus-group-clear-data-on-native-groups} command to clear out all data
1335 that you have on your native groups. Use with caution.
1337 After changing servers, you @strong{must} move the cache hierarchy away,
1338 since the cached articles will have wrong article numbers, which will
1339 affect which articles Gnus thinks are read.
1343 @section Startup Files
1344 @cindex startup files
1349 Now, you all know about the @file{.newsrc} file. All subscription
1350 information is traditionally stored in this file.
1352 Things got a bit more complicated with @sc{gnus}. In addition to
1353 keeping the @file{.newsrc} file updated, it also used a file called
1354 @file{.newsrc.el} for storing all the information that didn't fit into
1355 the @file{.newsrc} file. (Actually, it also duplicated everything in
1356 the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
1357 files was the most recently saved, which enabled people to swap between
1358 @sc{gnus} and other newsreaders.
1360 That was kinda silly, so Gnus went one better: In addition to the
1361 @file{.newsrc} and @file{.newsrc.el} files, Gnus also has a file called
1362 @file{.newsrc.eld}. It will read whichever of these files that are most
1363 recent, but it will never write a @file{.newsrc.el} file. You should
1364 never delete the @file{.newsrc.eld} file---it contains much information
1365 not stored in the @file{.newsrc} file.
1367 @vindex gnus-save-newsrc-file
1368 @vindex gnus-read-newsrc-file
1369 You can turn off writing the @file{.newsrc} file by setting
1370 @code{gnus-save-newsrc-file} to @code{nil}, which means you can delete
1371 the file and save some space, as well as exiting from Gnus faster.
1372 However, this will make it impossible to use other newsreaders than
1373 Gnus. But hey, who would want to, right? Similarly, setting
1374 @code{gnus-read-newsrc-file} to @code{nil} makes Gnus ignore the
1375 @file{.newsrc} file and any @file{.newsrc-SERVER} files, which is
1376 convenient if you have a tendency to use Netscape once in a while.
1378 @vindex gnus-save-killed-list
1379 If @code{gnus-save-killed-list} (default @code{t}) is @code{nil}, Gnus
1380 will not save the list of killed groups to the startup file. This will
1381 save both time (when starting and quitting) and space (on disk). It
1382 will also mean that Gnus has no record of what groups are new or old,
1383 so the automatic new groups subscription methods become meaningless.
1384 You should always set @code{gnus-check-new-newsgroups} to @code{nil} or
1385 @code{ask-server} if you set this variable to @code{nil} (@pxref{New
1386 Groups}). This variable can also be a regular expression. If that's
1387 the case, remove all groups that do not match this regexp before
1388 saving. This can be useful in certain obscure situations that involve
1389 several servers where not all servers support @code{ask-server}.
1391 @vindex gnus-startup-file
1392 The @code{gnus-startup-file} variable says where the startup files are.
1393 The default value is @file{~/.newsrc}, with the Gnus (El Dingo) startup
1394 file being whatever that one is, with a @samp{.eld} appended.
1396 @vindex gnus-save-newsrc-hook
1397 @vindex gnus-save-quick-newsrc-hook
1398 @vindex gnus-save-standard-newsrc-hook
1399 @code{gnus-save-newsrc-hook} is called before saving any of the newsrc
1400 files, while @code{gnus-save-quick-newsrc-hook} is called just before
1401 saving the @file{.newsrc.eld} file, and
1402 @code{gnus-save-standard-newsrc-hook} is called just before saving the
1403 @file{.newsrc} file. The latter two are commonly used to turn version
1404 control on or off. Version control is on by default when saving the
1405 startup files. If you want to turn backup creation off, say something like:
1408 (defun turn-off-backup ()
1409 (set (make-local-variable 'backup-inhibited) t))
1411 (add-hook 'gnus-save-quick-newsrc-hook 'turn-off-backup)
1412 (add-hook 'gnus-save-standard-newsrc-hook 'turn-off-backup)
1415 @vindex gnus-init-file
1416 When Gnus starts, it will read the @code{gnus-site-init-file}
1417 (@file{.../site-lisp/gnus} by default) and @code{gnus-init-file}
1418 (@file{~/.gnus} by default) files. These are normal Emacs Lisp files
1419 and can be used to avoid cluttering your @file{~/.emacs} and
1420 @file{site-init} files with Gnus stuff. Gnus will also check for files
1421 with the same names as these, but with @file{.elc} and @file{.el}
1422 suffixes. In other words, if you have set @code{gnus-init-file} to
1423 @file{~/.gnus}, it will look for @file{~/.gnus.elc}, @file{~/.gnus.el},
1424 and finally @file{~/.gnus} (in this order).
1430 @cindex dribble file
1433 Whenever you do something that changes the Gnus data (reading articles,
1434 catching up, killing/subscribing groups), the change is added to a
1435 special @dfn{dribble buffer}. This buffer is auto-saved the normal
1436 Emacs way. If your Emacs should crash before you have saved the
1437 @file{.newsrc} files, all changes you have made can be recovered from
1440 If Gnus detects this file at startup, it will ask the user whether to
1441 read it. The auto save file is deleted whenever the real startup file is
1444 @vindex gnus-use-dribble-file
1445 If @code{gnus-use-dribble-file} is @code{nil}, Gnus won't create and
1446 maintain a dribble buffer. The default is @code{t}.
1448 @vindex gnus-dribble-directory
1449 Gnus will put the dribble file(s) in @code{gnus-dribble-directory}. If
1450 this variable is @code{nil}, which it is by default, Gnus will dribble
1451 into the directory where the @file{.newsrc} file is located. (This is
1452 normally the user's home directory.) The dribble file will get the same
1453 file permissions as the @code{.newsrc} file.
1455 @vindex gnus-always-read-dribble-file
1456 If @code{gnus-always-read-dribble-file} is non-@code{nil}, Gnus will
1457 read the dribble file on startup without querying the user.
1460 @node The Active File
1461 @section The Active File
1463 @cindex ignored groups
1465 When Gnus starts, or indeed whenever it tries to determine whether new
1466 articles have arrived, it reads the active file. This is a very large
1467 file that lists all the active groups and articles on the server.
1469 @vindex gnus-ignored-newsgroups
1470 Before examining the active file, Gnus deletes all lines that match the
1471 regexp @code{gnus-ignored-newsgroups}. This is done primarily to reject
1472 any groups with bogus names, but you can use this variable to make Gnus
1473 ignore hierarchies you aren't ever interested in. However, this is not
1474 recommended. In fact, it's highly discouraged. Instead, @pxref{New
1475 Groups} for an overview of other variables that can be used instead.
1478 @c @code{nil} by default, and will slow down active file handling somewhat
1479 @c if you set it to anything else.
1481 @vindex gnus-read-active-file
1483 The active file can be rather Huge, so if you have a slow network, you
1484 can set @code{gnus-read-active-file} to @code{nil} to prevent Gnus from
1485 reading the active file. This variable is @code{some} by default.
1487 Gnus will try to make do by getting information just on the groups that
1488 you actually subscribe to.
1490 Note that if you subscribe to lots and lots of groups, setting this
1491 variable to @code{nil} will probably make Gnus slower, not faster. At
1492 present, having this variable @code{nil} will slow Gnus down
1493 considerably, unless you read news over a 2400 baud modem.
1495 This variable can also have the value @code{some}. Gnus will then
1496 attempt to read active info only on the subscribed groups. On some
1497 servers this is quite fast (on sparkling, brand new INN servers that
1498 support the @code{LIST ACTIVE group} command), on others this isn't fast
1499 at all. In any case, @code{some} should be faster than @code{nil}, and
1500 is certainly faster than @code{t} over slow lines.
1502 Some news servers (old versions of Leafnode and old versions of INN, for
1503 instance) do not support the @code{LIST ACTIVE group}. For these
1504 servers, @code{nil} is probably the most efficient value for this
1507 If this variable is @code{nil}, Gnus will ask for group info in total
1508 lock-step, which isn't very fast. If it is @code{some} and you use an
1509 @sc{nntp} server, Gnus will pump out commands as fast as it can, and
1510 read all the replies in one swoop. This will normally result in better
1511 performance, but if the server does not support the aforementioned
1512 @code{LIST ACTIVE group} command, this isn't very nice to the server.
1514 If you think that starting up Gnus takes too long, try all the three
1515 different values for this variable and see what works best for you.
1517 In any case, if you use @code{some} or @code{nil}, you should definitely
1518 kill all groups that you aren't interested in to speed things up.
1520 Note that this variable also affects active file retrieval from
1521 secondary select methods.
1524 @node Startup Variables
1525 @section Startup Variables
1529 @item gnus-load-hook
1530 @vindex gnus-load-hook
1531 A hook run while Gnus is being loaded. Note that this hook will
1532 normally be run just once in each Emacs session, no matter how many
1533 times you start Gnus.
1535 @item gnus-before-startup-hook
1536 @vindex gnus-before-startup-hook
1537 A hook run after starting up Gnus successfully.
1539 @item gnus-startup-hook
1540 @vindex gnus-startup-hook
1541 A hook run as the very last thing after starting up Gnus
1543 @item gnus-started-hook
1544 @vindex gnus-started-hook
1545 A hook that is run as the very last thing after starting up Gnus
1548 @item gnus-setup-news-hook
1549 @vindex gnus-setup-news-hook
1550 A hook that is run after reading the @file{.newsrc} file(s), but before
1551 generating the group buffer.
1553 @item gnus-check-bogus-newsgroups
1554 @vindex gnus-check-bogus-newsgroups
1555 If non-@code{nil}, Gnus will check for and delete all bogus groups at
1556 startup. A @dfn{bogus group} is a group that you have in your
1557 @file{.newsrc} file, but doesn't exist on the news server. Checking for
1558 bogus groups can take quite a while, so to save time and resources it's
1559 best to leave this option off, and do the checking for bogus groups once
1560 in a while from the group buffer instead (@pxref{Group Maintenance}).
1562 @item gnus-inhibit-startup-message
1563 @vindex gnus-inhibit-startup-message
1564 If non-@code{nil}, the startup message won't be displayed. That way,
1565 your boss might not notice as easily that you are reading news instead
1566 of doing your job. Note that this variable is used before
1567 @file{.gnus.el} is loaded, so it should be set in @code{.emacs} instead.
1569 @item gnus-no-groups-message
1570 @vindex gnus-no-groups-message
1571 Message displayed by Gnus when no groups are available.
1573 @item gnus-play-startup-jingle
1574 @vindex gnus-play-startup-jingle
1575 If non-@code{nil}, play the Gnus jingle at startup.
1577 @item gnus-startup-jingle
1578 @vindex gnus-startup-jingle
1579 Jingle to be played if the above variable is non-@code{nil}. The
1580 default is @samp{Tuxedomoon.Jingle4.au}.
1586 @chapter Group Buffer
1587 @cindex group buffer
1589 @c Alex Schroeder suggests to rearrange this as follows:
1591 @c <kensanata> ok, just save it for reference. I'll go to bed in a minute.
1592 @c 1. Selecting a Group, 2. (new) Finding a Group, 3. Group Levels,
1593 @c 4. Subscription Commands, 5. Group Maneuvering, 6. Group Data,
1594 @c 7. Group Score, 8. Group Buffer Format
1595 @c <kensanata> Group Levels should have more information on levels 5 to 9. I
1596 @c suggest to split the 4th paragraph ("Gnus considers groups...") as follows:
1597 @c <kensanata> First, "Gnus considers groups... (default 9)."
1598 @c <kensanata> New, a table summarizing what levels 1 to 9 mean.
1599 @c <kensanata> Third, "Gnus treats subscribed ... reasons of efficiency"
1600 @c <kensanata> Then expand the next paragraph or add some more to it.
1601 @c This short one sentence explains levels 1 and 2, therefore I understand
1602 @c that I should keep important news at 3 and boring news at 4.
1603 @c Say so! Then go on to explain why I should bother with levels 6 to 9.
1604 @c Maybe keep those that you don't want to read temporarily at 6,
1605 @c those that you never want to read at 8, those that offend your
1606 @c human rights at 9...
1609 The @dfn{group buffer} lists all (or parts) of the available groups. It
1610 is the first buffer shown when Gnus starts, and will never be killed as
1611 long as Gnus is active.
1615 \gnusfigure{The Group Buffer}{320}{
1616 \put(75,50){\epsfig{figure=ps/group.ps,height=9cm}}
1617 \put(120,37){\makebox(0,0)[t]{Buffer name}}
1618 \put(120,38){\vector(1,2){10}}
1619 \put(40,60){\makebox(0,0)[r]{Mode line}}
1620 \put(40,58){\vector(1,0){30}}
1621 \put(200,28){\makebox(0,0)[t]{Native select method}}
1622 \put(200,26){\vector(-1,2){15}}
1628 * Group Buffer Format:: Information listed and how you can change it.
1629 * Group Maneuvering:: Commands for moving in the group buffer.
1630 * Selecting a Group:: Actually reading news.
1631 * Subscription Commands:: Unsubscribing, killing, subscribing.
1632 * Group Data:: Changing the info for a group.
1633 * Group Levels:: Levels? What are those, then?
1634 * Group Score:: A mechanism for finding out what groups you like.
1635 * Marking Groups:: You can mark groups for later processing.
1636 * Foreign Groups:: Creating and editing groups.
1637 * Group Parameters:: Each group may have different parameters set.
1638 * Listing Groups:: Gnus can list various subsets of the groups.
1639 * Sorting Groups:: Re-arrange the group order.
1640 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
1641 * Browse Foreign Server:: You can browse a server. See what it has to offer.
1642 * Exiting Gnus:: Stop reading news and get some work done.
1643 * Group Topics:: A folding group mode divided into topics.
1644 * Misc Group Stuff:: Other stuff that you can to do.
1648 @node Group Buffer Format
1649 @section Group Buffer Format
1652 * Group Line Specification:: Deciding how the group buffer is to look.
1653 * Group Modeline Specification:: The group buffer modeline.
1654 * Group Highlighting:: Having nice colors in the group buffer.
1658 @node Group Line Specification
1659 @subsection Group Line Specification
1660 @cindex group buffer format
1662 The default format of the group buffer is nice and dull, but you can
1663 make it as exciting and ugly as you feel like.
1665 Here's a couple of example group lines:
1668 25: news.announce.newusers
1669 * 0: alt.fan.andrea-dworkin
1674 You can see that there are 25 unread articles in
1675 @samp{news.announce.newusers}. There are no unread articles, but some
1676 ticked articles, in @samp{alt.fan.andrea-dworkin} (see that little
1677 asterisk at the beginning of the line?).
1679 @vindex gnus-group-line-format
1680 You can change that format to whatever you want by fiddling with the
1681 @code{gnus-group-line-format} variable. This variable works along the
1682 lines of a @code{format} specification, which is pretty much the same as
1683 a @code{printf} specifications, for those of you who use (feh!) C.
1684 @xref{Formatting Variables}.
1686 @samp{%M%S%5y: %(%g%)\n} is the value that produced those lines above.
1688 There should always be a colon on the line; the cursor always moves to
1689 the colon after performing an operation. Nothing else is required---not
1690 even the group name. All displayed text is just window dressing, and is
1691 never examined by Gnus. Gnus stores all real information it needs using
1694 (Note that if you make a really strange, wonderful, spreadsheet-like
1695 layout, everybody will believe you are hard at work with the accounting
1696 instead of wasting time reading news.)
1698 Here's a list of all available format characters:
1703 An asterisk if the group only has marked articles.
1706 Whether the group is subscribed.
1709 Level of subscribedness.
1712 Number of unread articles.
1715 Number of dormant articles.
1718 Number of ticked articles.
1721 Number of read articles.
1724 Estimated total number of articles. (This is really @var{max-number}
1725 minus @var{min-number} plus 1.)
1727 Gnus uses this estimation because the NNTP protocol provides efficient
1728 access to @var{max-number} and @var{min-number} but getting the true
1729 unread message count is not possible efficiently. For hysterical
1730 raisins, even the mail back ends, where the true number of unread
1731 messages might be available efficiently, use the same limited
1732 interface. To remove this restriction from Gnus means that the
1733 back end interface has to be changed, which is not an easy job. If you
1734 want to work on this, please contact the Gnus mailing list.
1737 Number of unread, unticked, non-dormant articles.
1740 Number of ticked and dormant articles.
1749 Newsgroup description.
1752 @samp{m} if moderated.
1755 @samp{(m)} if moderated.
1764 A string that looks like @samp{<%s:%n>} if a foreign select method is
1768 Indentation based on the level of the topic (@pxref{Group Topics}).
1771 @vindex gnus-group-uncollapsed-levels
1772 Short (collapsed) group name. The @code{gnus-group-uncollapsed-levels}
1773 variable says how many levels to leave at the end of the group name.
1774 The default is 1---this will mean that group names like
1775 @samp{gnu.emacs.gnus} will be shortened to @samp{g.e.gnus}.
1778 @vindex gnus-new-mail-mark
1780 @samp{%} (@code{gnus-new-mail-mark}) if there has arrived new mail to
1784 @samp{#} (@code{gnus-process-mark}) if the group is process marked.
1787 A string that says when you last read the group (@pxref{Group
1791 User defined specifier. The next character in the format string should
1792 be a letter. Gnus will call the function
1793 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
1794 following @samp{%u}. The function will be passed a single dummy
1795 parameter as argument. The function should return a string, which will
1796 be inserted into the buffer just like information from any other
1801 All the ``number-of'' specs will be filled with an asterisk (@samp{*})
1802 if no info is available---for instance, if it is a non-activated foreign
1803 group, or a bogus native group.
1806 @node Group Modeline Specification
1807 @subsection Group Modeline Specification
1808 @cindex group modeline
1810 @vindex gnus-group-mode-line-format
1811 The mode line can be changed by setting
1812 @code{gnus-group-mode-line-format} (@pxref{Mode Line Formatting}). It
1813 doesn't understand that many format specifiers:
1817 The native news server.
1819 The native select method.
1823 @node Group Highlighting
1824 @subsection Group Highlighting
1825 @cindex highlighting
1826 @cindex group highlighting
1828 @vindex gnus-group-highlight
1829 Highlighting in the group buffer is controlled by the
1830 @code{gnus-group-highlight} variable. This is an alist with elements
1831 that look like @code{(@var{form} . @var{face})}. If @var{form} evaluates to
1832 something non-@code{nil}, the @var{face} will be used on the line.
1834 Here's an example value for this variable that might look nice if the
1838 (cond (window-system
1839 (setq custom-background-mode 'light)
1840 (defface my-group-face-1
1841 '((t (:foreground "Red" :bold t))) "First group face")
1842 (defface my-group-face-2
1843 '((t (:foreground "DarkSeaGreen4" :bold t))) "Second group face")
1844 (defface my-group-face-3
1845 '((t (:foreground "Green4" :bold t))) "Third group face")
1846 (defface my-group-face-4
1847 '((t (:foreground "SteelBlue" :bold t))) "Fourth group face")
1848 (defface my-group-face-5
1849 '((t (:foreground "Blue" :bold t))) "Fifth group face")))
1851 (setq gnus-group-highlight
1852 '(((> unread 200) . my-group-face-1)
1853 ((and (< level 3) (zerop unread)) . my-group-face-2)
1854 ((< level 3) . my-group-face-3)
1855 ((zerop unread) . my-group-face-4)
1856 (t . my-group-face-5)))
1859 Also @pxref{Faces and Fonts}.
1861 Variables that are dynamically bound when the forms are evaluated
1868 The number of unread articles in the group.
1872 Whether the group is a mail group.
1874 The level of the group.
1876 The score of the group.
1878 The number of ticked articles in the group.
1880 The total number of articles in the group. Or rather, MAX-NUMBER minus
1881 MIN-NUMBER plus one.
1883 When using the topic minor mode, this variable is bound to the current
1884 topic being inserted.
1887 When the forms are @code{eval}ed, point is at the beginning of the line
1888 of the group in question, so you can use many of the normal Gnus
1889 functions for snarfing info on the group.
1891 @vindex gnus-group-update-hook
1892 @findex gnus-group-highlight-line
1893 @code{gnus-group-update-hook} is called when a group line is changed.
1894 It will not be called when @code{gnus-visual} is @code{nil}. This hook
1895 calls @code{gnus-group-highlight-line} by default.
1898 @node Group Maneuvering
1899 @section Group Maneuvering
1900 @cindex group movement
1902 All movement commands understand the numeric prefix and will behave as
1903 expected, hopefully.
1909 @findex gnus-group-next-unread-group
1910 Go to the next group that has unread articles
1911 (@code{gnus-group-next-unread-group}).
1917 @findex gnus-group-prev-unread-group
1918 Go to the previous group that has unread articles
1919 (@code{gnus-group-prev-unread-group}).
1923 @findex gnus-group-next-group
1924 Go to the next group (@code{gnus-group-next-group}).
1928 @findex gnus-group-prev-group
1929 Go to the previous group (@code{gnus-group-prev-group}).
1933 @findex gnus-group-next-unread-group-same-level
1934 Go to the next unread group on the same (or lower) level
1935 (@code{gnus-group-next-unread-group-same-level}).
1939 @findex gnus-group-prev-unread-group-same-level
1940 Go to the previous unread group on the same (or lower) level
1941 (@code{gnus-group-prev-unread-group-same-level}).
1944 Three commands for jumping to groups:
1950 @findex gnus-group-jump-to-group
1951 Jump to a group (and make it visible if it isn't already)
1952 (@code{gnus-group-jump-to-group}). Killed groups can be jumped to, just
1957 @findex gnus-group-best-unread-group
1958 Jump to the unread group with the lowest level
1959 (@code{gnus-group-best-unread-group}).
1963 @findex gnus-group-first-unread-group
1964 Jump to the first group with unread articles
1965 (@code{gnus-group-first-unread-group}).
1968 @vindex gnus-group-goto-unread
1969 If @code{gnus-group-goto-unread} is @code{nil}, all the movement
1970 commands will move to the next group, not the next unread group. Even
1971 the commands that say they move to the next unread group. The default
1975 @node Selecting a Group
1976 @section Selecting a Group
1977 @cindex group selection
1982 @kindex SPACE (Group)
1983 @findex gnus-group-read-group
1984 Select the current group, switch to the summary buffer and display the
1985 first unread article (@code{gnus-group-read-group}). If there are no
1986 unread articles in the group, or if you give a non-numerical prefix to
1987 this command, Gnus will offer to fetch all the old articles in this
1988 group from the server. If you give a numerical prefix @var{N}, @var{N}
1989 determines the number of articles Gnus will fetch. If @var{N} is
1990 positive, Gnus fetches the @var{N} newest articles, if @var{N} is
1991 negative, Gnus fetches the @code{abs(@var{N})} oldest articles.
1993 Thus, @kbd{SPC} enters the group normally, @kbd{C-u SPC} offers old
1994 articles, @kbd{C-u 4 2 SPC} fetches the 42 newest articles, and @kbd{C-u
1995 - 4 2 SPC} fetches the 42 oldest ones.
1997 When you are in the group (in the Summary buffer), you can type
1998 @kbd{M-g} to fetch new articles, or @kbd{C-u M-g} to also show the old
2003 @findex gnus-group-select-group
2004 Select the current group and switch to the summary buffer
2005 (@code{gnus-group-select-group}). Takes the same arguments as
2006 @code{gnus-group-read-group}---the only difference is that this command
2007 does not display the first unread article automatically upon group
2011 @kindex M-RET (Group)
2012 @findex gnus-group-quick-select-group
2013 This does the same as the command above, but tries to do it with the
2014 minimum amount of fuzz (@code{gnus-group-quick-select-group}). No
2015 scoring/killing will be performed, there will be no highlights and no
2016 expunging. This might be useful if you're in a real hurry and have to
2017 enter some humongous group. If you give a 0 prefix to this command
2018 (i.e., @kbd{0 M-RET}), Gnus won't even generate the summary buffer,
2019 which is useful if you want to toggle threading before generating the
2020 summary buffer (@pxref{Summary Generation Commands}).
2023 @kindex M-SPACE (Group)
2024 @findex gnus-group-visible-select-group
2025 This is yet one more command that does the same as the @kbd{RET}
2026 command, but this one does it without expunging and hiding dormants
2027 (@code{gnus-group-visible-select-group}).
2030 @kindex M-C-RET (Group)
2031 @findex gnus-group-select-group-ephemerally
2032 Finally, this command selects the current group ephemerally without
2033 doing any processing of its contents
2034 (@code{gnus-group-select-group-ephemerally}). Even threading has been
2035 turned off. Everything you do in the group after selecting it in this
2036 manner will have no permanent effects.
2040 @vindex gnus-large-newsgroup
2041 The @code{gnus-large-newsgroup} variable says what Gnus should consider
2042 to be a big group. This is 200 by default. If the group has more
2043 (unread and/or ticked) articles than this, Gnus will query the user
2044 before entering the group. The user can then specify how many articles
2045 should be fetched from the server. If the user specifies a negative
2046 number (@code{-n}), the @code{n} oldest articles will be fetched. If it
2047 is positive, the @code{n} articles that have arrived most recently will
2050 @vindex gnus-select-group-hook
2051 @vindex gnus-auto-select-first
2052 @code{gnus-auto-select-first} control whether any articles are selected
2053 automatically when entering a group with the @kbd{SPACE} command.
2058 Don't select any articles when entering the group. Just display the
2059 full summary buffer.
2062 Select the first unread article when entering the group.
2065 Select the highest scored article in the group when entering the
2070 This variable can also be a function. In that case, that function will
2071 be called to place point on a subject line, and/or select some article.
2072 Useful functions include:
2075 @item gnus-summary-first-unread-subject
2076 Place point on the subject line of the first unread article, but
2077 don't select the article.
2079 @item gnus-summary-first-unread-article
2080 Select the first unread article.
2082 @item gnus-summary-best-unread-article
2083 Select the highest-scored unread article.
2087 If you want to prevent automatic selection in some group (say, in a
2088 binary group with Huge articles) you can set this variable to @code{nil}
2089 in @code{gnus-select-group-hook}, which is called when a group is
2093 @node Subscription Commands
2094 @section Subscription Commands
2095 @cindex subscription
2103 @findex gnus-group-unsubscribe-current-group
2104 @c @icon{gnus-group-unsubscribe}
2105 Toggle subscription to the current group
2106 (@code{gnus-group-unsubscribe-current-group}).
2112 @findex gnus-group-unsubscribe-group
2113 Prompt for a group to subscribe, and then subscribe it. If it was
2114 subscribed already, unsubscribe it instead
2115 (@code{gnus-group-unsubscribe-group}).
2121 @findex gnus-group-kill-group
2122 @c @icon{gnus-group-kill-group}
2123 Kill the current group (@code{gnus-group-kill-group}).
2129 @findex gnus-group-yank-group
2130 Yank the last killed group (@code{gnus-group-yank-group}).
2133 @kindex C-x C-t (Group)
2134 @findex gnus-group-transpose-groups
2135 Transpose two groups (@code{gnus-group-transpose-groups}). This isn't
2136 really a subscription command, but you can use it instead of a
2137 kill-and-yank sequence sometimes.
2143 @findex gnus-group-kill-region
2144 Kill all groups in the region (@code{gnus-group-kill-region}).
2148 @findex gnus-group-kill-all-zombies
2149 Kill all zombie groups (@code{gnus-group-kill-all-zombies}).
2152 @kindex S C-k (Group)
2153 @findex gnus-group-kill-level
2154 Kill all groups on a certain level (@code{gnus-group-kill-level}).
2155 These groups can't be yanked back after killing, so this command should
2156 be used with some caution. The only time where this command comes in
2157 really handy is when you have a @file{.newsrc} with lots of unsubscribed
2158 groups that you want to get rid off. @kbd{S C-k} on level 7 will
2159 kill off all unsubscribed groups that do not have message numbers in the
2160 @file{.newsrc} file.
2164 Also @pxref{Group Levels}.
2174 @findex gnus-group-catchup-current
2175 @vindex gnus-group-catchup-group-hook
2176 @c @icon{gnus-group-catchup-current}
2177 Mark all unticked articles in this group as read
2178 (@code{gnus-group-catchup-current}).
2179 @code{gnus-group-catchup-group-hook} is called when catching up a group from
2184 @findex gnus-group-catchup-current-all
2185 Mark all articles in this group, even the ticked ones, as read
2186 (@code{gnus-group-catchup-current-all}).
2190 @findex gnus-group-clear-data
2191 Clear the data from the current group---nix out marks and the list of
2192 read articles (@code{gnus-group-clear-data}).
2194 @item M-x gnus-group-clear-data-on-native-groups
2195 @kindex M-x gnus-group-clear-data-on-native-groups
2196 @findex gnus-group-clear-data-on-native-groups
2197 If you have switched from one @sc{nntp} server to another, all your marks
2198 and read ranges have become worthless. You can use this command to
2199 clear out all data that you have on your native groups. Use with
2206 @section Group Levels
2210 All groups have a level of @dfn{subscribedness}. For instance, if a
2211 group is on level 2, it is more subscribed than a group on level 5. You
2212 can ask Gnus to just list groups on a given level or lower
2213 (@pxref{Listing Groups}), or to just check for new articles in groups on
2214 a given level or lower (@pxref{Scanning New Messages}).
2216 Remember: The higher the level of the group, the less important it is.
2222 @findex gnus-group-set-current-level
2223 Set the level of the current group. If a numeric prefix is given, the
2224 next @var{n} groups will have their levels set. The user will be
2225 prompted for a level.
2228 @vindex gnus-level-killed
2229 @vindex gnus-level-zombie
2230 @vindex gnus-level-unsubscribed
2231 @vindex gnus-level-subscribed
2232 Gnus considers groups from levels 1 to
2233 @code{gnus-level-subscribed} (inclusive) (default 5) to be subscribed,
2234 @code{gnus-level-subscribed} (exclusive) and
2235 @code{gnus-level-unsubscribed} (inclusive) (default 7) to be
2236 unsubscribed, @code{gnus-level-zombie} to be zombies (walking dead)
2237 (default 8) and @code{gnus-level-killed} to be killed (completely dead)
2238 (default 9). Gnus treats subscribed and unsubscribed groups exactly the
2239 same, but zombie and killed groups have no information on what articles
2240 you have read, etc, stored. This distinction between dead and living
2241 groups isn't done because it is nice or clever, it is done purely for
2242 reasons of efficiency.
2244 It is recommended that you keep all your mail groups (if any) on quite
2245 low levels (e.g. 1 or 2).
2247 Maybe the following description of the default behavior of Gnus helps to
2248 understand what these levels are all about. By default, Gnus shows you
2249 subscribed nonempty groups, but by hitting @kbd{L} you can have it show
2250 empty subscribed groups and unsubscribed groups, too. Type @kbd{l} to
2251 go back to showing nonempty subscribed groups again. Thus, unsubscribed
2252 groups are hidden, in a way.
2254 Zombie and killed groups are similar to unsubscribed groups in that they
2255 are hidden by default. But they are different from subscribed and
2256 unsubscribed groups in that Gnus doesn't ask the news server for
2257 information (number of messages, number of unread messages) on zombie
2258 and killed groups. Normally, you use @kbd{C-k} to kill the groups you
2259 aren't interested in. If most groups are killed, Gnus is faster.
2261 Why does Gnus distinguish between zombie and killed groups? Well, when
2262 a new group arrives on the server, Gnus by default makes it a zombie
2263 group. This means that you are normally not bothered with new groups,
2264 but you can type @kbd{A z} to get a list of all new groups. Subscribe
2265 the ones you like and kill the ones you don't want. (@kbd{A k} shows a
2266 list of killed groups.)
2268 If you want to play with the level variables, you should show some care.
2269 Set them once, and don't touch them ever again. Better yet, don't touch
2270 them at all unless you know exactly what you're doing.
2272 @vindex gnus-level-default-unsubscribed
2273 @vindex gnus-level-default-subscribed
2274 Two closely related variables are @code{gnus-level-default-subscribed}
2275 (default 3) and @code{gnus-level-default-unsubscribed} (default 6),
2276 which are the levels that new groups will be put on if they are
2277 (un)subscribed. These two variables should, of course, be inside the
2278 relevant valid ranges.
2280 @vindex gnus-keep-same-level
2281 If @code{gnus-keep-same-level} is non-@code{nil}, some movement commands
2282 will only move to groups of the same level (or lower). In
2283 particular, going from the last article in one group to the next group
2284 will go to the next group of the same level (or lower). This might be
2285 handy if you want to read the most important groups before you read the
2288 If this variable is @code{best}, Gnus will make the next newsgroup the
2289 one with the best level.
2291 @vindex gnus-group-default-list-level
2292 All groups with a level less than or equal to
2293 @code{gnus-group-default-list-level} will be listed in the group buffer
2296 @vindex gnus-group-list-inactive-groups
2297 If @code{gnus-group-list-inactive-groups} is non-@code{nil}, non-active
2298 groups will be listed along with the unread groups. This variable is
2299 @code{t} by default. If it is @code{nil}, inactive groups won't be
2302 @vindex gnus-group-use-permanent-levels
2303 If @code{gnus-group-use-permanent-levels} is non-@code{nil}, once you
2304 give a level prefix to @kbd{g} or @kbd{l}, all subsequent commands will
2305 use this level as the ``work'' level.
2307 @vindex gnus-activate-level
2308 Gnus will normally just activate (i. e., query the server about) groups
2309 on level @code{gnus-activate-level} or less. If you don't want to
2310 activate unsubscribed groups, for instance, you might set this variable
2311 to 5. The default is 6.
2315 @section Group Score
2320 You would normally keep important groups on high levels, but that scheme
2321 is somewhat restrictive. Don't you wish you could have Gnus sort the
2322 group buffer according to how often you read groups, perhaps? Within
2325 This is what @dfn{group score} is for. You can have Gnus assign a score
2326 to each group through the mechanism described below. You can then sort
2327 the group buffer based on this score. Alternatively, you can sort on
2328 score and then level. (Taken together, the level and the score is
2329 called the @dfn{rank} of the group. A group that is on level 4 and has
2330 a score of 1 has a higher rank than a group on level 5 that has a score
2331 of 300. (The level is the most significant part and the score is the
2332 least significant part.))
2334 @findex gnus-summary-bubble-group
2335 If you want groups you read often to get higher scores than groups you
2336 read seldom you can add the @code{gnus-summary-bubble-group} function to
2337 the @code{gnus-summary-exit-hook} hook. This will result (after
2338 sorting) in a bubbling sort of action. If you want to see that in
2339 action after each summary exit, you can add
2340 @code{gnus-group-sort-groups-by-rank} or
2341 @code{gnus-group-sort-groups-by-score} to the same hook, but that will
2342 slow things down somewhat.
2345 @node Marking Groups
2346 @section Marking Groups
2347 @cindex marking groups
2349 If you want to perform some command on several groups, and they appear
2350 subsequently in the group buffer, you would normally just give a
2351 numerical prefix to the command. Most group commands will then do your
2352 bidding on those groups.
2354 However, if the groups are not in sequential order, you can still
2355 perform a command on several groups. You simply mark the groups first
2356 with the process mark and then execute the command.
2364 @findex gnus-group-mark-group
2365 Set the mark on the current group (@code{gnus-group-mark-group}).
2371 @findex gnus-group-unmark-group
2372 Remove the mark from the current group
2373 (@code{gnus-group-unmark-group}).
2377 @findex gnus-group-unmark-all-groups
2378 Remove the mark from all groups (@code{gnus-group-unmark-all-groups}).
2382 @findex gnus-group-mark-region
2383 Mark all groups between point and mark (@code{gnus-group-mark-region}).
2387 @findex gnus-group-mark-buffer
2388 Mark all groups in the buffer (@code{gnus-group-mark-buffer}).
2392 @findex gnus-group-mark-regexp
2393 Mark all groups that match some regular expression
2394 (@code{gnus-group-mark-regexp}).
2397 Also @pxref{Process/Prefix}.
2399 @findex gnus-group-universal-argument
2400 If you want to execute some command on all groups that have been marked
2401 with the process mark, you can use the @kbd{M-&}
2402 (@code{gnus-group-universal-argument}) command. It will prompt you for
2403 the command to be executed.
2406 @node Foreign Groups
2407 @section Foreign Groups
2408 @cindex foreign groups
2410 Below are some group mode commands for making and editing general foreign
2411 groups, as well as commands to ease the creation of a few
2412 special-purpose groups. All these commands insert the newly created
2413 groups under point---@code{gnus-subscribe-newsgroup-method} is not
2420 @findex gnus-group-make-group
2421 @cindex making groups
2422 Make a new group (@code{gnus-group-make-group}). Gnus will prompt you
2423 for a name, a method and possibly an @dfn{address}. For an easier way
2424 to subscribe to @sc{nntp} groups, @pxref{Browse Foreign Server}.
2428 @findex gnus-group-rename-group
2429 @cindex renaming groups
2430 Rename the current group to something else
2431 (@code{gnus-group-rename-group}). This is valid only on some
2432 groups---mail groups mostly. This command might very well be quite slow
2438 @findex gnus-group-customize
2439 Customize the group parameters (@code{gnus-group-customize}).
2443 @findex gnus-group-edit-group-method
2444 @cindex renaming groups
2445 Enter a buffer where you can edit the select method of the current
2446 group (@code{gnus-group-edit-group-method}).
2450 @findex gnus-group-edit-group-parameters
2451 Enter a buffer where you can edit the group parameters
2452 (@code{gnus-group-edit-group-parameters}).
2456 @findex gnus-group-edit-group
2457 Enter a buffer where you can edit the group info
2458 (@code{gnus-group-edit-group}).
2462 @findex gnus-group-make-directory-group
2464 Make a directory group (@pxref{Directory Groups}). You will be prompted
2465 for a directory name (@code{gnus-group-make-directory-group}).
2470 @findex gnus-group-make-help-group
2471 Make the Gnus help group (@code{gnus-group-make-help-group}).
2475 @cindex (ding) archive
2476 @cindex archive group
2477 @findex gnus-group-make-archive-group
2478 @vindex gnus-group-archive-directory
2479 @vindex gnus-group-recent-archive-directory
2480 Make a Gnus archive group (@code{gnus-group-make-archive-group}). By
2481 default a group pointing to the most recent articles will be created
2482 (@code{gnus-group-recent-archive-directory}), but given a prefix, a full
2483 group will be created from @code{gnus-group-archive-directory}.
2487 @findex gnus-group-make-kiboze-group
2489 Make a kiboze group. You will be prompted for a name, for a regexp to
2490 match groups to be ``included'' in the kiboze group, and a series of
2491 strings to match on headers (@code{gnus-group-make-kiboze-group}).
2492 @xref{Kibozed Groups}.
2496 @findex gnus-group-enter-directory
2498 Read an arbitrary directory as if it were a newsgroup with the
2499 @code{nneething} back end (@code{gnus-group-enter-directory}).
2500 @xref{Anything Groups}.
2504 @findex gnus-group-make-doc-group
2505 @cindex ClariNet Briefs
2507 Make a group based on some file or other
2508 (@code{gnus-group-make-doc-group}). If you give a prefix to this
2509 command, you will be prompted for a file name and a file type.
2510 Currently supported types are @code{babyl}, @code{mbox}, @code{digest},
2511 @code{mmdf}, @code{news}, @code{rnews}, @code{clari-briefs},
2512 @code{rfc934}, @code{rfc822-forward}, @code{nsmail} and @code{forward}.
2513 If you run this command without a prefix, Gnus will guess at the file
2514 type. @xref{Document Groups}.
2518 @vindex gnus-useful-groups
2519 @findex gnus-group-make-useful-group
2520 Create one of the groups mentioned in @code{gnus-useful-groups}
2521 (@code{gnus-group-make-useful-group}).
2525 @findex gnus-group-make-web-group
2530 Make an ephemeral group based on a web search
2531 (@code{gnus-group-make-web-group}). If you give a prefix to this
2532 command, make a solid group instead. You will be prompted for the
2533 search engine type and the search string. Valid search engine types
2534 include @code{dejanews}, @code{altavista} and @code{reference}.
2535 @xref{Web Searches}.
2537 If you use the @code{dejanews} search engine, you can limit the search
2538 to a particular group by using a match string like
2539 @samp{~g alt.sysadmin.recovery shaving}.
2542 @kindex G DEL (Group)
2543 @findex gnus-group-delete-group
2544 This function will delete the current group
2545 (@code{gnus-group-delete-group}). If given a prefix, this function will
2546 actually delete all the articles in the group, and forcibly remove the
2547 group itself from the face of the Earth. Use a prefix only if you are
2548 absolutely sure of what you are doing. This command can't be used on
2549 read-only groups (like @code{nntp} group), though.
2553 @findex gnus-group-make-empty-virtual
2554 Make a new, fresh, empty @code{nnvirtual} group
2555 (@code{gnus-group-make-empty-virtual}). @xref{Virtual Groups}.
2559 @findex gnus-group-add-to-virtual
2560 Add the current group to an @code{nnvirtual} group
2561 (@code{gnus-group-add-to-virtual}). Uses the process/prefix convention.
2564 @xref{Select Methods}, for more information on the various select
2567 @vindex gnus-activate-foreign-newsgroups
2568 If @code{gnus-activate-foreign-newsgroups} is a positive number,
2569 Gnus will check all foreign groups with this level or lower at startup.
2570 This might take quite a while, especially if you subscribe to lots of
2571 groups from different @sc{nntp} servers. Also @pxref{Group Levels};
2572 @code{gnus-activate-level} also affects activation of foreign
2576 @node Group Parameters
2577 @section Group Parameters
2578 @cindex group parameters
2580 The group parameters store information local to a particular group.
2581 Here's an example group parameter list:
2584 ((to-address . "ding@@gnus.org")
2588 We see that each element consists of a "dotted pair"---the thing before
2589 the dot is the key, while the thing after the dot is the value. All the
2590 parameters have this form @emph{except} local variable specs, which are
2591 not dotted pairs, but proper lists.
2593 Some parameters have correspondant customizable variables, each of which
2594 is an alist of regexps and values.
2596 The following group parameters can be used:
2601 Address used by when doing followups and new posts.
2604 (to-address . "some@@where.com")
2607 This is primarily useful in mail groups that represent closed mailing
2608 lists---mailing lists where it's expected that everybody that writes to
2609 the mailing list is subscribed to it. Since using this parameter
2610 ensures that the mail only goes to the mailing list itself, it means
2611 that members won't receive two copies of your followups.
2613 Using @code{to-address} will actually work whether the group is foreign
2614 or not. Let's say there's a group on the server that is called
2615 @samp{fa.4ad-l}. This is a real newsgroup, but the server has gotten
2616 the articles from a mail-to-news gateway. Posting directly to this
2617 group is therefore impossible---you have to send mail to the mailing
2618 list address instead.
2620 See also @code{gnus-parameter-to-address-alist}.
2624 Address used when doing @kbd{a} in that group.
2627 (to-list . "some@@where.com")
2630 It is totally ignored
2631 when doing a followup---except that if it is present in a news group,
2632 you'll get mail group semantics when doing @kbd{f}.
2634 If you do an @kbd{a} command in a mail group and you have neither a
2635 @code{to-list} group parameter nor a @code{to-address} group parameter,
2636 then a @code{to-list} group parameter will be added automatically upon
2637 sending the message if @code{gnus-add-to-list} is set to @code{t}.
2638 @vindex gnus-add-to-list
2640 If you do an @kbd{a} command in a mail group and you don't have a
2641 @code{to-list} group parameter, one will be added automatically upon
2642 sending the message.
2644 @findex gnus-mailing-list-mode
2645 @cindex Mail List Groups
2646 If this variable is set, @code{gnus-mailing-list-mode} is turned on when
2647 entering summary buffer.
2649 See also @code{gnus-parameter-to-list-alist}.
2653 If the group parameter list has the element @code{(visible . t)},
2654 that group will always be visible in the Group buffer, regardless
2655 of whether it has any unread articles.
2657 @item broken-reply-to
2658 @cindex broken-reply-to
2659 Elements like @code{(broken-reply-to . t)} signals that @code{Reply-To}
2660 headers in this group are to be ignored. This can be useful if you're
2661 reading a mailing list group where the listserv has inserted
2662 @code{Reply-To} headers that point back to the listserv itself. This is
2663 broken behavior. So there!
2667 Elements like @code{(to-group . "some.group.name")} means that all
2668 posts in that group will be sent to @code{some.group.name}.
2672 If you have @code{(newsgroup . t)} in the group parameter list, Gnus
2673 will treat all responses as if they were responses to news articles.
2674 This can be useful if you have a mail group that's really a mirror of a
2679 If @code{(gcc-self . t)} is present in the group parameter list, newly
2680 composed messages will be @code{Gcc}'d to the current group. If
2681 @code{(gcc-self . none)} is present, no @code{Gcc:} header will be
2682 generated, if @code{(gcc-self . "string")} is present, this string will
2683 be inserted literally as a @code{gcc} header. This parameter takes
2684 precedence over any default @code{Gcc} rules as described later
2685 (@pxref{Archived Messages}).
2689 If the group parameter has an element that looks like @code{(auto-expire
2690 . t)}, all articles read will be marked as expirable. For an
2691 alternative approach, @pxref{Expiring Mail}.
2693 See also @code{gnus-auto-expirable-newsgroups}.
2696 @cindex total-expire
2697 If the group parameter has an element that looks like
2698 @code{(total-expire . t)}, all read articles will be put through the
2699 expiry process, even if they are not marked as expirable. Use with
2700 caution. Unread, ticked and dormant articles are not eligible for
2703 See also @code{gnus-total-expirable-newsgroups}.
2707 @vindex nnmail-expiry-wait-function
2708 If the group parameter has an element that looks like @code{(expiry-wait
2709 . 10)}, this value will override any @code{nnmail-expiry-wait} and
2710 @code{nnmail-expiry-wait-function} when expiring expirable messages.
2711 The value can either be a number of days (not necessarily an integer) or
2712 the symbols @code{never} or @code{immediate}.
2715 @cindex score file group parameter
2716 Elements that look like @code{(score-file . "file")} will make
2717 @file{file} into the current score file for the group in question. All
2718 interactive score entries will be put into this file.
2721 @cindex adapt file group parameter
2722 Elements that look like @code{(adapt-file . "file")} will make
2723 @file{file} into the current adaptive file for the group in question.
2724 All adaptive score entries will be put into this file.
2727 @cindex admin-address
2728 When unsubscribing from a mailing list you should never send the
2729 unsubscription notice to the mailing list itself. Instead, you'd send
2730 messages to the administrative address. This parameter allows you to
2731 put the admin address somewhere convenient.
2735 Elements that look like @code{(display . MODE)} say which articles to
2736 display on entering the group. Valid values are:
2740 Display all articles, both read and unread.
2743 Display the default visible articles, which normally includes unread and
2747 Display articles that satisfy a predicate.
2749 Here are some examples:
2753 Display only read articles.
2756 Display everything except expirable articles.
2758 @item [and (not reply) (not expire)]
2759 Display everything except expirable and articles you've already
2763 The available operators are @code{not}, @code{and} and @code{or}.
2764 Predicates include @code{tick}, @code{unsend}, @code{undownload},
2765 @code{read}, @code{dormant}, @code{expire}, @code{reply},
2766 @code{killed}, @code{bookmark}, @code{score}, @code{save},
2767 @code{cache}, @code{forward}, @code{seen} and @code{recent}.
2771 The @code{display} parameter works by limiting the summary buffer to
2772 the subset specified. You can pop the limit by using the @kbd{/ w}
2773 command (@pxref{Limiting}).
2777 Elements that look like @code{(comment . "This is a comment")}
2778 are arbitrary comments on the group. They are currently ignored by
2779 Gnus, but provide a place for you to store information on particular
2784 Elements that look like @code{(charset . iso-8859-1)} will make
2785 @code{iso-8859-1} the default charset; that is, the charset that will be
2786 used for all articles that do not specify a charset.
2788 See also @code{gnus-group-charset-alist}.
2790 @item ignored-charsets
2791 @cindex ignored-charset
2792 Elements that look like @code{(ignored-charsets x-unknown iso-8859-1)}
2793 will make @code{iso-8859-1} and @code{x-unknown} ignored; that is, the
2794 default charset will be used for decoding articles.
2796 See also @code{gnus-group-ignored-charsets-alist}.
2799 @cindex posting-style
2800 You can store additional posting style information for this group only
2801 here (@pxref{Posting Styles}). The format is that of an entry in the
2802 @code{gnus-posting-styles} alist, except that there's no regexp matching
2803 the group name (of course). Style elements in this group parameter will
2804 take precedence over the ones found in @code{gnus-posting-styles}.
2806 For instance, if you want a funky name and signature in this group only,
2807 instead of hacking @code{gnus-posting-styles}, you could put something
2808 like this in the group parameters:
2813 (signature "Funky Signature"))
2818 If it is set, the value is used as the method for posting message
2819 instead of @code{gnus-post-method}.
2823 An item like @code{(banner . "regex")} causes any part of an article
2824 that matches the regular expression "regex" to be stripped. Instead of
2825 "regex", you can also use the symbol @code{signature} which strips the
2826 last signature or any of the elements of the alist
2827 @code{gnus-article-banner-alist}.
2829 @item (@var{variable} @var{form})
2830 You can use the group parameters to set variables local to the group you
2831 are entering. If you want to turn threading off in @samp{news.answers},
2832 you could put @code{(gnus-show-threads nil)} in the group parameters of
2833 that group. @code{gnus-show-threads} will be made into a local variable
2834 in the summary buffer you enter, and the form @code{nil} will be
2835 @code{eval}ed there.
2837 This can also be used as a group-specific hook function, if you'd like.
2838 If you want to hear a beep when you enter a group, you could put
2839 something like @code{(dummy-variable (ding))} in the parameters of that
2840 group. @code{dummy-variable} will be set to the result of the
2841 @code{(ding)} form, but who cares?
2845 Use the @kbd{G p} or the @kbd{G c} command to edit group parameters of a
2846 group. (@kbd{G p} presents you with a Lisp-based interface, @kbd{G c}
2847 presents you with a Customize-like interface. The latter helps avoid
2848 silly Lisp errors.) You might also be interested in reading about topic
2849 parameters (@pxref{Topic Parameters}).
2851 Group parameters can be set via the @code{gnus-parameters} variable too.
2852 But some variables, such as @code{visible}, have no effect. For
2856 (setq gnus-parameters
2858 (gnus-show-threads nil)
2859 (gnus-use-scoring nil)
2860 (gnus-summary-line-format
2861 "%U%R%z%I%(%[%d:%ub%-23,23f%]%) %s\n")
2865 ("^nnimap:\\(foo.bar\\)$"
2869 (gnus-use-scoring t))
2873 (broken-reply-to . t))))
2876 String value of parameters will be subjected to regexp substitution, as
2877 the @code{to-group} example shows.
2880 @node Listing Groups
2881 @section Listing Groups
2882 @cindex group listing
2884 These commands all list various slices of the groups available.
2892 @findex gnus-group-list-groups
2893 List all groups that have unread articles
2894 (@code{gnus-group-list-groups}). If the numeric prefix is used, this
2895 command will list only groups of level ARG and lower. By default, it
2896 only lists groups of level five (i. e.,
2897 @code{gnus-group-default-list-level}) or lower (i.e., just subscribed
2904 @findex gnus-group-list-all-groups
2905 List all groups, whether they have unread articles or not
2906 (@code{gnus-group-list-all-groups}). If the numeric prefix is used,
2907 this command will list only groups of level ARG and lower. By default,
2908 it lists groups of level seven or lower (i.e., just subscribed and
2909 unsubscribed groups).
2913 @findex gnus-group-list-level
2914 List all unread groups on a specific level
2915 (@code{gnus-group-list-level}). If given a prefix, also list the groups
2916 with no unread articles.
2920 @findex gnus-group-list-killed
2921 List all killed groups (@code{gnus-group-list-killed}). If given a
2922 prefix argument, really list all groups that are available, but aren't
2923 currently (un)subscribed. This could entail reading the active file
2928 @findex gnus-group-list-zombies
2929 List all zombie groups (@code{gnus-group-list-zombies}).
2933 @findex gnus-group-list-matching
2934 List all unread, subscribed groups with names that match a regexp
2935 (@code{gnus-group-list-matching}).
2939 @findex gnus-group-list-all-matching
2940 List groups that match a regexp (@code{gnus-group-list-all-matching}).
2944 @findex gnus-group-list-active
2945 List absolutely all groups in the active file(s) of the
2946 server(s) you are connected to (@code{gnus-group-list-active}). This
2947 might very well take quite a while. It might actually be a better idea
2948 to do a @kbd{A M} to list all matching, and just give @samp{.} as the
2949 thing to match on. Also note that this command may list groups that
2950 don't exist (yet)---these will be listed as if they were killed groups.
2951 Take the output with some grains of salt.
2955 @findex gnus-group-apropos
2956 List all groups that have names that match a regexp
2957 (@code{gnus-group-apropos}).
2961 @findex gnus-group-description-apropos
2962 List all groups that have names or descriptions that match a regexp
2963 (@code{gnus-group-description-apropos}).
2967 @findex gnus-group-list-cached
2968 List all groups with cached articles (@code{gnus-group-list-cached}).
2972 @findex gnus-group-list-dormant
2973 List all groups with dormant articles (@code{gnus-group-list-dormant}).
2977 @findex gnus-group-list-limit
2978 List groups limited within the current selection
2979 (@code{gnus-group-list-limit}).
2983 @findex gnus-group-list-flush
2984 Flush groups from the current selection (@code{gnus-group-list-flush}).
2988 @findex gnus-group-list-plus
2989 List groups plus the current selection (@code{gnus-group-list-plus}).
2993 @vindex gnus-permanently-visible-groups
2994 @cindex visible group parameter
2995 Groups that match the @code{gnus-permanently-visible-groups} regexp will
2996 always be shown, whether they have unread articles or not. You can also
2997 add the @code{visible} element to the group parameters in question to
2998 get the same effect.
3000 @vindex gnus-list-groups-with-ticked-articles
3001 Groups that have just ticked articles in it are normally listed in the
3002 group buffer. If @code{gnus-list-groups-with-ticked-articles} is
3003 @code{nil}, these groups will be treated just like totally empty
3004 groups. It is @code{t} by default.
3007 @node Sorting Groups
3008 @section Sorting Groups
3009 @cindex sorting groups
3011 @kindex C-c C-s (Group)
3012 @findex gnus-group-sort-groups
3013 @vindex gnus-group-sort-function
3014 The @kbd{C-c C-s} (@code{gnus-group-sort-groups}) command sorts the
3015 group buffer according to the function(s) given by the
3016 @code{gnus-group-sort-function} variable. Available sorting functions
3021 @item gnus-group-sort-by-alphabet
3022 @findex gnus-group-sort-by-alphabet
3023 Sort the group names alphabetically. This is the default.
3025 @item gnus-group-sort-by-real-name
3026 @findex gnus-group-sort-by-real-name
3027 Sort the group alphabetically on the real (unprefixed) group names.
3029 @item gnus-group-sort-by-level
3030 @findex gnus-group-sort-by-level
3031 Sort by group level.
3033 @item gnus-group-sort-by-score
3034 @findex gnus-group-sort-by-score
3035 Sort by group score. @xref{Group Score}.
3037 @item gnus-group-sort-by-rank
3038 @findex gnus-group-sort-by-rank
3039 Sort by group score and then the group level. The level and the score
3040 are, when taken together, the group's @dfn{rank}. @xref{Group Score}.
3042 @item gnus-group-sort-by-unread
3043 @findex gnus-group-sort-by-unread
3044 Sort by number of unread articles.
3046 @item gnus-group-sort-by-method
3047 @findex gnus-group-sort-by-method
3048 Sort alphabetically on the select method.
3050 @item gnus-group-sort-by-server
3051 @findex gnus-group-sort-by-server
3052 Sort alphabetically on the Gnus server name.
3057 @code{gnus-group-sort-function} can also be a list of sorting
3058 functions. In that case, the most significant sort key function must be
3062 There are also a number of commands for sorting directly according to
3063 some sorting criteria:
3067 @kindex G S a (Group)
3068 @findex gnus-group-sort-groups-by-alphabet
3069 Sort the group buffer alphabetically by group name
3070 (@code{gnus-group-sort-groups-by-alphabet}).
3073 @kindex G S u (Group)
3074 @findex gnus-group-sort-groups-by-unread
3075 Sort the group buffer by the number of unread articles
3076 (@code{gnus-group-sort-groups-by-unread}).
3079 @kindex G S l (Group)
3080 @findex gnus-group-sort-groups-by-level
3081 Sort the group buffer by group level
3082 (@code{gnus-group-sort-groups-by-level}).
3085 @kindex G S v (Group)
3086 @findex gnus-group-sort-groups-by-score
3087 Sort the group buffer by group score
3088 (@code{gnus-group-sort-groups-by-score}). @xref{Group Score}.
3091 @kindex G S r (Group)
3092 @findex gnus-group-sort-groups-by-rank
3093 Sort the group buffer by group rank
3094 (@code{gnus-group-sort-groups-by-rank}). @xref{Group Score}.
3097 @kindex G S m (Group)
3098 @findex gnus-group-sort-groups-by-method
3099 Sort the group buffer alphabetically by back end name
3100 (@code{gnus-group-sort-groups-by-method}).
3104 All the commands below obey the process/prefix convention
3105 (@pxref{Process/Prefix}).
3107 When given a symbolic prefix (@pxref{Symbolic Prefixes}), all these
3108 commands will sort in reverse order.
3110 You can also sort a subset of the groups:
3114 @kindex G P a (Group)
3115 @findex gnus-group-sort-selected-groups-by-alphabet
3116 Sort the groups alphabetically by group name
3117 (@code{gnus-group-sort-selected-groups-by-alphabet}).
3120 @kindex G P u (Group)
3121 @findex gnus-group-sort-selected-groups-by-unread
3122 Sort the groups by the number of unread articles
3123 (@code{gnus-group-sort-selected-groups-by-unread}).
3126 @kindex G P l (Group)
3127 @findex gnus-group-sort-selected-groups-by-level
3128 Sort the groups by group level
3129 (@code{gnus-group-sort-selected-groups-by-level}).
3132 @kindex G P v (Group)
3133 @findex gnus-group-sort-selected-groups-by-score
3134 Sort the groups by group score
3135 (@code{gnus-group-sort-selected-groups-by-score}). @xref{Group Score}.
3138 @kindex G P r (Group)
3139 @findex gnus-group-sort-selected-groups-by-rank
3140 Sort the groups by group rank
3141 (@code{gnus-group-sort-selected-groups-by-rank}). @xref{Group Score}.
3144 @kindex G P m (Group)
3145 @findex gnus-group-sort-selected-groups-by-method
3146 Sort the groups alphabetically by back end name
3147 (@code{gnus-group-sort-selected-groups-by-method}).
3151 And finally, note that you can use @kbd{C-k} and @kbd{C-y} to manually
3155 @node Group Maintenance
3156 @section Group Maintenance
3157 @cindex bogus groups
3162 @findex gnus-group-check-bogus-groups
3163 Find bogus groups and delete them
3164 (@code{gnus-group-check-bogus-groups}).
3168 @findex gnus-group-find-new-groups
3169 Find new groups and process them (@code{gnus-group-find-new-groups}).
3170 With 1 @kbd{C-u}, use the @code{ask-server} method to query the server
3171 for new groups. With 2 @kbd{C-u}'s, use most complete method possible
3172 to query the server for new groups, and subscribe the new groups as
3176 @kindex C-c C-x (Group)
3177 @findex gnus-group-expire-articles
3178 Run all expirable articles in the current group through the expiry
3179 process (if any) (@code{gnus-group-expire-articles}). That is, delete
3180 all expirable articles in the group that have been around for a while.
3181 (@pxref{Expiring Mail}).
3184 @kindex C-c M-C-x (Group)
3185 @findex gnus-group-expire-all-groups
3186 Run all expirable articles in all groups through the expiry process
3187 (@code{gnus-group-expire-all-groups}).
3192 @node Browse Foreign Server
3193 @section Browse Foreign Server
3194 @cindex foreign servers
3195 @cindex browsing servers
3200 @findex gnus-group-browse-foreign-server
3201 You will be queried for a select method and a server name. Gnus will
3202 then attempt to contact this server and let you browse the groups there
3203 (@code{gnus-group-browse-foreign-server}).
3206 @findex gnus-browse-mode
3207 A new buffer with a list of available groups will appear. This buffer
3208 will use the @code{gnus-browse-mode}. This buffer looks a bit (well,
3209 a lot) like a normal group buffer.
3211 Here's a list of keystrokes available in the browse mode:
3216 @findex gnus-group-next-group
3217 Go to the next group (@code{gnus-group-next-group}).
3221 @findex gnus-group-prev-group
3222 Go to the previous group (@code{gnus-group-prev-group}).
3225 @kindex SPACE (Browse)
3226 @findex gnus-browse-read-group
3227 Enter the current group and display the first article
3228 (@code{gnus-browse-read-group}).
3231 @kindex RET (Browse)
3232 @findex gnus-browse-select-group
3233 Enter the current group (@code{gnus-browse-select-group}).
3237 @findex gnus-browse-unsubscribe-current-group
3238 Unsubscribe to the current group, or, as will be the case here,
3239 subscribe to it (@code{gnus-browse-unsubscribe-current-group}).
3245 @findex gnus-browse-exit
3246 Exit browse mode (@code{gnus-browse-exit}).
3250 @findex gnus-browse-describe-briefly
3251 Describe browse mode briefly (well, there's not much to describe, is
3252 there) (@code{gnus-browse-describe-briefly}).
3257 @section Exiting Gnus
3258 @cindex exiting Gnus
3260 Yes, Gnus is ex(c)iting.
3265 @findex gnus-group-suspend
3266 Suspend Gnus (@code{gnus-group-suspend}). This doesn't really exit Gnus,
3267 but it kills all buffers except the Group buffer. I'm not sure why this
3268 is a gain, but then who am I to judge?
3272 @findex gnus-group-exit
3273 @c @icon{gnus-group-exit}
3274 Quit Gnus (@code{gnus-group-exit}).
3278 @findex gnus-group-quit
3279 Quit Gnus without saving the @file{.newsrc} files (@code{gnus-group-quit}).
3280 The dribble file will be saved, though (@pxref{Auto Save}).
3283 @vindex gnus-exit-gnus-hook
3284 @vindex gnus-suspend-gnus-hook
3285 @code{gnus-suspend-gnus-hook} is called when you suspend Gnus and
3286 @code{gnus-exit-gnus-hook} is called when you quit Gnus, while
3287 @code{gnus-after-exiting-gnus-hook} is called as the final item when
3292 If you wish to completely unload Gnus and all its adherents, you can use
3293 the @code{gnus-unload} command. This command is also very handy when
3294 trying to customize meta-variables.
3299 Miss Lisa Cannifax, while sitting in English class, felt her feet go
3300 numbly heavy and herself fall into a hazy trance as the boy sitting
3301 behind her drew repeated lines with his pencil across the back of her
3307 @section Group Topics
3310 If you read lots and lots of groups, it might be convenient to group
3311 them hierarchically according to topics. You put your Emacs groups over
3312 here, your sex groups over there, and the rest (what, two groups or so?)
3313 you put in some misc section that you never bother with anyway. You can
3314 even group the Emacs sex groups as a sub-topic to either the Emacs
3315 groups or the sex groups---or both! Go wild!
3319 \gnusfigure{Group Topics}{400}{
3320 \put(75,50){\epsfig{figure=ps/group-topic.ps,height=9cm}}
3331 2: alt.religion.emacs
3334 0: comp.talk.emacs.recovery
3336 8: comp.binaries.fractals
3337 13: comp.sources.unix
3340 @findex gnus-topic-mode
3342 To get this @emph{fab} functionality you simply turn on (ooh!) the
3343 @code{gnus-topic} minor mode---type @kbd{t} in the group buffer. (This
3344 is a toggling command.)
3346 Go ahead, just try it. I'll still be here when you get back. La de
3347 dum... Nice tune, that... la la la... What, you're back? Yes, and
3348 now press @kbd{l}. There. All your groups are now listed under
3349 @samp{misc}. Doesn't that make you feel all warm and fuzzy? Hot and
3352 If you want this permanently enabled, you should add that minor mode to
3353 the hook for the group mode. Put the following line in your
3354 @file{~/.gnus} file:
3357 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
3361 * Topic Commands:: Interactive E-Z commands.
3362 * Topic Variables:: How to customize the topics the Lisp Way.
3363 * Topic Sorting:: Sorting each topic individually.
3364 * Topic Topology:: A map of the world.
3365 * Topic Parameters:: Parameters that apply to all groups in a topic.
3369 @node Topic Commands
3370 @subsection Topic Commands
3371 @cindex topic commands
3373 When the topic minor mode is turned on, a new @kbd{T} submap will be
3374 available. In addition, a few of the standard keys change their
3375 definitions slightly.
3377 In general, the following kinds of operations are possible on topics.
3378 First of all, you want to create topics. Secondly, you want to put
3379 groups in topics and to move them around until you have an order you
3380 like. The third kind of operation is to show/hide parts of the whole
3381 shebang. You might want to hide a topic including its subtopics and
3382 groups, to get a better overview of the other groups.
3384 Here is a list of the basic keys that you might need to set up topics
3391 @findex gnus-topic-create-topic
3392 Prompt for a new topic name and create it
3393 (@code{gnus-topic-create-topic}).
3397 @kindex T TAB (Topic)
3399 @findex gnus-topic-indent
3400 ``Indent'' the current topic so that it becomes a sub-topic of the
3401 previous topic (@code{gnus-topic-indent}). If given a prefix,
3402 ``un-indent'' the topic instead.
3405 @kindex M-TAB (Topic)
3406 @findex gnus-topic-unindent
3407 ``Un-indent'' the current topic so that it becomes a sub-topic of the
3408 parent of its current parent (@code{gnus-topic-unindent}).
3412 The following two keys can be used to move groups and topics around.
3413 They work like the well-known cut and paste. @kbd{C-k} is like cut and
3414 @kbd{C-y} is like paste. Of course, this being Emacs, we use the terms
3415 kill and yank rather than cut and paste.
3421 @findex gnus-topic-kill-group
3422 Kill a group or topic (@code{gnus-topic-kill-group}). All groups in the
3423 topic will be removed along with the topic.
3427 @findex gnus-topic-yank-group
3428 Yank the previously killed group or topic
3429 (@code{gnus-topic-yank-group}). Note that all topics will be yanked
3432 So, to move a topic to the beginning of the list of topics, just hit
3433 @kbd{C-k} on it. This is like the `cut' part of cut and paste. Then,
3434 move the cursor to the beginning of the buffer (just below the `Gnus'
3435 topic) and hit @kbd{C-y}. This is like the `paste' part of cut and
3436 paste. Like I said -- E-Z.
3438 You can use @kbd{C-k} and @kbd{C-y} on groups as well as on topics. So
3439 you can move topics around as well as groups.
3443 After setting up the topics the way you like them, you might wish to
3444 hide a topic, or to show it again. That's why we have the following
3451 @findex gnus-topic-select-group
3453 Either select a group or fold a topic (@code{gnus-topic-select-group}).
3454 When you perform this command on a group, you'll enter the group, as
3455 usual. When done on a topic line, the topic will be folded (if it was
3456 visible) or unfolded (if it was folded already). So it's basically a
3457 toggling command on topics. In addition, if you give a numerical
3458 prefix, group on that level (and lower) will be displayed.
3462 Now for a list of other commands, in no particular order.
3468 @findex gnus-topic-move-group
3469 Move the current group to some other topic
3470 (@code{gnus-topic-move-group}). This command uses the process/prefix
3471 convention (@pxref{Process/Prefix}).
3475 @findex gnus-topic-jump-to-topic
3476 Go to a topic (@code{gnus-topic-jump-to-topic}).
3480 @findex gnus-topic-copy-group
3481 Copy the current group to some other topic
3482 (@code{gnus-topic-copy-group}). This command uses the process/prefix
3483 convention (@pxref{Process/Prefix}).
3487 @findex gnus-topic-hide-topic
3488 Hide the current topic (@code{gnus-topic-hide-topic}). If given
3489 a prefix, hide the topic permanently.
3493 @findex gnus-topic-show-topic
3494 Show the current topic (@code{gnus-topic-show-topic}). If given
3495 a prefix, show the topic permanently.
3499 @findex gnus-topic-remove-group
3500 Remove a group from the current topic (@code{gnus-topic-remove-group}).
3501 This command is mainly useful if you have the same group in several
3502 topics and wish to remove it from one of the topics. You may also
3503 remove a group from all topics, but in that case, Gnus will add it to
3504 the root topic the next time you start Gnus. In fact, all new groups
3505 (which, naturally, don't belong to any topic) will show up in the root
3508 This command uses the process/prefix convention
3509 (@pxref{Process/Prefix}).
3513 @findex gnus-topic-move-matching
3514 Move all groups that match some regular expression to a topic
3515 (@code{gnus-topic-move-matching}).
3519 @findex gnus-topic-copy-matching
3520 Copy all groups that match some regular expression to a topic
3521 (@code{gnus-topic-copy-matching}).
3525 @findex gnus-topic-toggle-display-empty-topics
3526 Toggle hiding empty topics
3527 (@code{gnus-topic-toggle-display-empty-topics}).
3531 @findex gnus-topic-mark-topic
3532 Mark all groups in the current topic with the process mark
3533 (@code{gnus-topic-mark-topic}).
3536 @kindex T M-# (Topic)
3537 @findex gnus-topic-unmark-topic
3538 Remove the process mark from all groups in the current topic
3539 (@code{gnus-topic-unmark-topic}).
3542 @kindex C-c C-x (Topic)
3543 @findex gnus-topic-expire-articles
3544 Run all expirable articles in the current group or topic through the
3545 expiry process (if any)
3546 (@code{gnus-topic-expire-articles}). (@pxref{Expiring Mail}).
3550 @findex gnus-topic-rename
3551 Rename a topic (@code{gnus-topic-rename}).
3554 @kindex T DEL (Topic)
3555 @findex gnus-topic-delete
3556 Delete an empty topic (@code{gnus-topic-delete}).
3560 @findex gnus-topic-list-active
3561 List all groups that Gnus knows about in a topics-ified way
3562 (@code{gnus-topic-list-active}).
3566 @findex gnus-topic-edit-parameters
3567 @cindex group parameters
3568 @cindex topic parameters
3570 Edit the topic parameters (@code{gnus-topic-edit-parameters}).
3571 @xref{Topic Parameters}.
3576 @node Topic Variables
3577 @subsection Topic Variables
3578 @cindex topic variables
3580 The previous section told you how to tell Gnus which topics to display.
3581 This section explains how to tell Gnus what to display about each topic.
3583 @vindex gnus-topic-line-format
3584 The topic lines themselves are created according to the
3585 @code{gnus-topic-line-format} variable (@pxref{Formatting Variables}).
3598 Number of groups in the topic.
3600 Number of unread articles in the topic.
3602 Number of unread articles in the topic and all its subtopics.
3605 @vindex gnus-topic-indent-level
3606 Each sub-topic (and the groups in the sub-topics) will be indented with
3607 @code{gnus-topic-indent-level} times the topic level number of spaces.
3610 @vindex gnus-topic-mode-hook
3611 @code{gnus-topic-mode-hook} is called in topic minor mode buffers.
3613 @vindex gnus-topic-display-empty-topics
3614 The @code{gnus-topic-display-empty-topics} says whether to display even
3615 topics that have no unread articles in them. The default is @code{t}.
3619 @subsection Topic Sorting
3620 @cindex topic sorting
3622 You can sort the groups in each topic individually with the following
3628 @kindex T S a (Topic)
3629 @findex gnus-topic-sort-groups-by-alphabet
3630 Sort the current topic alphabetically by group name
3631 (@code{gnus-topic-sort-groups-by-alphabet}).
3634 @kindex T S u (Topic)
3635 @findex gnus-topic-sort-groups-by-unread
3636 Sort the current topic by the number of unread articles
3637 (@code{gnus-topic-sort-groups-by-unread}).
3640 @kindex T S l (Topic)
3641 @findex gnus-topic-sort-groups-by-level
3642 Sort the current topic by group level
3643 (@code{gnus-topic-sort-groups-by-level}).
3646 @kindex T S v (Topic)
3647 @findex gnus-topic-sort-groups-by-score
3648 Sort the current topic by group score
3649 (@code{gnus-topic-sort-groups-by-score}). @xref{Group Score}.
3652 @kindex T S r (Topic)
3653 @findex gnus-topic-sort-groups-by-rank
3654 Sort the current topic by group rank
3655 (@code{gnus-topic-sort-groups-by-rank}). @xref{Group Score}.
3658 @kindex T S m (Topic)
3659 @findex gnus-topic-sort-groups-by-method
3660 Sort the current topic alphabetically by back end name
3661 (@code{gnus-topic-sort-groups-by-method}).
3665 @xref{Sorting Groups}, for more information about group sorting.
3668 @node Topic Topology
3669 @subsection Topic Topology
3670 @cindex topic topology
3673 So, let's have a look at an example group buffer:
3679 2: alt.religion.emacs
3682 0: comp.talk.emacs.recovery
3684 8: comp.binaries.fractals
3685 13: comp.sources.unix
3688 So, here we have one top-level topic (@samp{Gnus}), two topics under
3689 that, and one sub-topic under one of the sub-topics. (There is always
3690 just one (1) top-level topic). This topology can be expressed as
3695 (("Emacs -- I wuw it!" visible)
3696 (("Naughty Emacs" visible)))
3700 @vindex gnus-topic-topology
3701 This is in fact how the variable @code{gnus-topic-topology} would look
3702 for the display above. That variable is saved in the @file{.newsrc.eld}
3703 file, and shouldn't be messed with manually---unless you really want
3704 to. Since this variable is read from the @file{.newsrc.eld} file,
3705 setting it in any other startup files will have no effect.
3707 This topology shows what topics are sub-topics of what topics (right),
3708 and which topics are visible. Two settings are currently
3709 allowed---@code{visible} and @code{invisible}.
3712 @node Topic Parameters
3713 @subsection Topic Parameters
3714 @cindex topic parameters
3716 All groups in a topic will inherit group parameters from the parent (and
3717 ancestor) topic parameters. All valid group parameters are valid topic
3718 parameters (@pxref{Group Parameters}).
3720 In addition, the following parameters are only valid as topic
3725 When subscribing new groups by topic (@pxref{Subscription Methods}), the
3726 @code{subscribe} topic parameter says what groups go in what topic. Its
3727 value should be a regexp to match the groups that should go in that
3732 Group parameters (of course) override topic parameters, and topic
3733 parameters in sub-topics override topic parameters in super-topics. You
3734 know. Normal inheritance rules. (@dfn{Rules} is here a noun, not a
3735 verb, although you may feel free to disagree with me here.)
3741 2: alt.religion.emacs
3745 0: comp.talk.emacs.recovery
3747 8: comp.binaries.fractals
3748 13: comp.sources.unix
3752 The @samp{Emacs} topic has the topic parameter @code{(score-file
3753 . "emacs.SCORE")}; the @samp{Relief} topic has the topic parameter
3754 @code{(score-file . "relief.SCORE")}; and the @samp{Misc} topic has the
3755 topic parameter @code{(score-file . "emacs.SCORE")}. In addition,
3756 @* @samp{alt.religion.emacs} has the group parameter @code{(score-file
3757 . "religion.SCORE")}.
3759 Now, when you enter @samp{alt.sex.emacs} in the @samp{Relief} topic, you
3760 will get the @file{relief.SCORE} home score file. If you enter the same
3761 group in the @samp{Emacs} topic, you'll get the @file{emacs.SCORE} home
3762 score file. If you enter the group @samp{alt.religion.emacs}, you'll
3763 get the @file{religion.SCORE} home score file.
3765 This seems rather simple and self-evident, doesn't it? Well, yes. But
3766 there are some problems, especially with the @code{total-expiry}
3767 parameter. Say you have a mail group in two topics; one with
3768 @code{total-expiry} and one without. What happens when you do @kbd{M-x
3769 gnus-expire-all-expirable-groups}? Gnus has no way of telling which one
3770 of these topics you mean to expire articles from, so anything may
3771 happen. In fact, I hereby declare that it is @dfn{undefined} what
3772 happens. You just have to be careful if you do stuff like that.
3775 @node Misc Group Stuff
3776 @section Misc Group Stuff
3779 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
3780 * Group Information:: Information and help on groups and Gnus.
3781 * Group Timestamp:: Making Gnus keep track of when you last read a group.
3782 * File Commands:: Reading and writing the Gnus files.
3789 @findex gnus-group-enter-server-mode
3790 Enter the server buffer (@code{gnus-group-enter-server-mode}).
3791 @xref{Server Buffer}.
3795 @findex gnus-group-post-news
3796 Post an article to a group (@code{gnus-group-post-news}). If given a
3797 prefix, the current group name will be used as the default.
3801 @findex gnus-group-mail
3802 Mail a message somewhere (@code{gnus-group-mail}).
3806 Variables for the group buffer:
3810 @item gnus-group-mode-hook
3811 @vindex gnus-group-mode-hook
3812 is called after the group buffer has been
3815 @item gnus-group-prepare-hook
3816 @vindex gnus-group-prepare-hook
3817 is called after the group buffer is
3818 generated. It may be used to modify the buffer in some strange,
3821 @item gnus-group-prepared-hook
3822 @vindex gnus-group-prepare-hook
3823 is called as the very last thing after the group buffer has been
3824 generated. It may be used to move point around, for instance.
3826 @item gnus-permanently-visible-groups
3827 @vindex gnus-permanently-visible-groups
3828 Groups matching this regexp will always be listed in the group buffer,
3829 whether they are empty or not.
3831 @item gnus-group-name-charset-method-alist
3832 @vindex gnus-group-name-charset-method-alist
3833 An alist of method and the charset for group names. It is used to show
3834 non-ASCII group names.
3838 (setq gnus-group-name-charset-method-alist
3839 '(((nntp "news.com.cn") . cn-gb-2312)))
3842 @item gnus-group-name-charset-group-alist
3843 @vindex gnus-group-name-charset-group-alist
3844 An alist of regexp of group name and the charset for group names.
3845 It is used to show non-ASCII group names.
3849 (setq gnus-group-name-charset-group-alist
3850 '(("\\.com\\.cn:" . cn-gb-2312)))
3855 @node Scanning New Messages
3856 @subsection Scanning New Messages
3857 @cindex new messages
3858 @cindex scanning new news
3864 @findex gnus-group-get-new-news
3865 @c @icon{gnus-group-get-new-news}
3866 Check the server(s) for new articles. If the numerical prefix is used,
3867 this command will check only groups of level @var{arg} and lower
3868 (@code{gnus-group-get-new-news}). If given a non-numerical prefix, this
3869 command will force a total re-reading of the active file(s) from the
3874 @findex gnus-group-get-new-news-this-group
3875 @vindex gnus-goto-next-group-when-activating
3876 @c @icon{gnus-group-get-new-news-this-group}
3877 Check whether new articles have arrived in the current group
3878 (@code{gnus-group-get-new-news-this-group}).
3879 @code{gnus-goto-next-group-when-activating} says whether this command is
3880 to move point to the next group or not. It is @code{t} by default.
3882 @findex gnus-activate-all-groups
3883 @cindex activating groups
3885 @kindex C-c M-g (Group)
3886 Activate absolutely all groups (@code{gnus-activate-all-groups}).
3891 @findex gnus-group-restart
3892 Restart Gnus (@code{gnus-group-restart}). This saves the @file{.newsrc}
3893 file(s), closes the connection to all servers, clears up all run-time
3894 Gnus variables, and then starts Gnus all over again.
3898 @vindex gnus-get-new-news-hook
3899 @code{gnus-get-new-news-hook} is run just before checking for new news.
3901 @vindex gnus-after-getting-new-news-hook
3902 @code{gnus-after-getting-new-news-hook} is run after checking for new
3906 @node Group Information
3907 @subsection Group Information
3908 @cindex group information
3909 @cindex information on groups
3916 @findex gnus-group-fetch-faq
3917 @vindex gnus-group-faq-directory
3920 Try to fetch the FAQ for the current group
3921 (@code{gnus-group-fetch-faq}). Gnus will try to get the FAQ from
3922 @code{gnus-group-faq-directory}, which is usually a directory on a
3923 remote machine. This variable can also be a list of directories. In
3924 that case, giving a prefix to this command will allow you to choose
3925 between the various sites. @code{ange-ftp} (or @code{efs}) will be used
3926 for fetching the file.
3928 If fetching from the first site is unsuccessful, Gnus will attempt to go
3929 through @code{gnus-group-faq-directory} and try to open them one by one.
3933 @c @icon{gnus-group-describe-group}
3935 @kindex C-c C-d (Group)
3936 @cindex describing groups
3937 @cindex group description
3938 @findex gnus-group-describe-group
3939 Describe the current group (@code{gnus-group-describe-group}). If given
3940 a prefix, force Gnus to re-read the description from the server.
3944 @findex gnus-group-describe-all-groups
3945 Describe all groups (@code{gnus-group-describe-all-groups}). If given a
3946 prefix, force Gnus to re-read the description file from the server.
3953 @findex gnus-version
3954 Display current Gnus version numbers (@code{gnus-version}).
3958 @findex gnus-group-describe-briefly
3959 Give a very short help message (@code{gnus-group-describe-briefly}).
3962 @kindex C-c C-i (Group)
3965 @findex gnus-info-find-node
3966 Go to the Gnus info node (@code{gnus-info-find-node}).
3970 @node Group Timestamp
3971 @subsection Group Timestamp
3973 @cindex group timestamps
3975 It can be convenient to let Gnus keep track of when you last read a
3976 group. To set the ball rolling, you should add
3977 @code{gnus-group-set-timestamp} to @code{gnus-select-group-hook}:
3980 (add-hook 'gnus-select-group-hook 'gnus-group-set-timestamp)
3983 After doing this, each time you enter a group, it'll be recorded.
3985 This information can be displayed in various ways---the easiest is to
3986 use the @samp{%d} spec in the group line format:
3989 (setq gnus-group-line-format
3990 "%M\%S\%p\%P\%5y: %(%-40,40g%) %d\n")
3993 This will result in lines looking like:
3996 * 0: mail.ding 19961002T012943
3997 0: custom 19961002T012713
4000 As you can see, the date is displayed in compact ISO 8601 format. This
4001 may be a bit too much, so to just display the date, you could say
4005 (setq gnus-group-line-format
4006 "%M\%S\%p\%P\%5y: %(%-40,40g%) %6,6~(cut 2)d\n")
4011 @subsection File Commands
4012 @cindex file commands
4018 @findex gnus-group-read-init-file
4019 @vindex gnus-init-file
4020 @cindex reading init file
4021 Re-read the init file (@code{gnus-init-file}, which defaults to
4022 @file{~/.gnus}) (@code{gnus-group-read-init-file}).
4026 @findex gnus-group-save-newsrc
4027 @cindex saving .newsrc
4028 Save the @file{.newsrc.eld} file (and @file{.newsrc} if wanted)
4029 (@code{gnus-group-save-newsrc}). If given a prefix, force saving the
4030 file(s) whether Gnus thinks it is necessary or not.
4033 @c @kindex Z (Group)
4034 @c @findex gnus-group-clear-dribble
4035 @c Clear the dribble buffer (@code{gnus-group-clear-dribble}).
4040 @node Summary Buffer
4041 @chapter Summary Buffer
4042 @cindex summary buffer
4044 A line for each article is displayed in the summary buffer. You can
4045 move around, read articles, post articles and reply to articles.
4047 The most common way to a summary buffer is to select a group from the
4048 group buffer (@pxref{Selecting a Group}).
4050 You can have as many summary buffers open as you wish.
4053 * Summary Buffer Format:: Deciding how the summary buffer is to look.
4054 * Summary Maneuvering:: Moving around the summary buffer.
4055 * Choosing Articles:: Reading articles.
4056 * Paging the Article:: Scrolling the current article.
4057 * Reply Followup and Post:: Posting articles.
4058 * Delayed Articles::
4059 * Marking Articles:: Marking articles as read, expirable, etc.
4060 * Limiting:: You can limit the summary buffer.
4061 * Threading:: How threads are made.
4062 * Sorting the Summary Buffer:: How articles and threads are sorted.
4063 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
4064 * Article Caching:: You may store articles in a cache.
4065 * Persistent Articles:: Making articles expiry-resistant.
4066 * Article Backlog:: Having already read articles hang around.
4067 * Saving Articles:: Ways of customizing article saving.
4068 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
4069 * Article Treatment:: The article buffer can be mangled at will.
4070 * MIME Commands:: Doing MIMEy things with the articles.
4071 * Charsets:: Character set issues.
4072 * Article Commands:: Doing various things with the article buffer.
4073 * Summary Sorting:: Sorting the summary buffer in various ways.
4074 * Finding the Parent:: No child support? Get the parent.
4075 * Alternative Approaches:: Reading using non-default summaries.
4076 * Tree Display:: A more visual display of threads.
4077 * Mail Group Commands:: Some commands can only be used in mail groups.
4078 * Various Summary Stuff:: What didn't fit anywhere else.
4079 * Exiting the Summary Buffer:: Returning to the Group buffer,
4080 or reselecting the current group.
4081 * Crosspost Handling:: How crossposted articles are dealt with.
4082 * Duplicate Suppression:: An alternative when crosspost handling fails.
4083 * Security:: Decrypt and Verify.
4084 * Mailing List:: Mailing list minor mode.
4088 @node Summary Buffer Format
4089 @section Summary Buffer Format
4090 @cindex summary buffer format
4094 \gnusfigure{The Summary Buffer}{180}{
4095 \put(0,0){\epsfig{figure=ps/summary.ps,width=7.5cm}}
4096 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-article.ps,width=7.5cm}}}
4102 * Summary Buffer Lines:: You can specify how summary lines should look.
4103 * To From Newsgroups:: How to not display your own name.
4104 * Summary Buffer Mode Line:: You can say how the mode line should look.
4105 * Summary Highlighting:: Making the summary buffer all pretty and nice.
4108 @findex mail-extract-address-components
4109 @findex gnus-extract-address-components
4110 @vindex gnus-extract-address-components
4111 Gnus will use the value of the @code{gnus-extract-address-components}
4112 variable as a function for getting the name and address parts of a
4113 @code{From} header. Two pre-defined functions exist:
4114 @code{gnus-extract-address-components}, which is the default, quite
4115 fast, and too simplistic solution; and
4116 @code{mail-extract-address-components}, which works very nicely, but is
4117 slower. The default function will return the wrong answer in 5% of the
4118 cases. If this is unacceptable to you, use the other function instead:
4121 (setq gnus-extract-address-components
4122 'mail-extract-address-components)
4125 @vindex gnus-summary-same-subject
4126 @code{gnus-summary-same-subject} is a string indicating that the current
4127 article has the same subject as the previous. This string will be used
4128 with those specs that require it. The default is @code{""}.
4131 @node Summary Buffer Lines
4132 @subsection Summary Buffer Lines
4134 @vindex gnus-summary-line-format
4135 You can change the format of the lines in the summary buffer by changing
4136 the @code{gnus-summary-line-format} variable. It works along the same
4137 lines as a normal @code{format} string, with some extensions
4138 (@pxref{Formatting Variables}).
4140 There should always be a colon or a point position marker on the line;
4141 the cursor always moves to the point position marker or the colon after
4142 performing an operation. (Of course, Gnus wouldn't be Gnus if it wasn't
4143 possible to change this. Just write a new function
4144 @code{gnus-goto-colon} which does whatever you like with the cursor.)
4146 The default string is @samp{%U%R%z%I%(%[%4L: %-23,23n%]%) %s\n}.
4148 The following format specification characters are understood:
4154 Subject string. List identifiers stripped,
4155 @code{gnus-list-identifies}. @xref{Article Hiding}.
4157 Subject if the article is the root of the thread or the previous article
4158 had a different subject, @code{gnus-summary-same-subject} otherwise.
4159 (@code{gnus-summary-same-subject} defaults to @code{""}.)
4161 Full @code{From} header.
4163 The name (from the @code{From} header).
4165 The name, code @code{To} header or the @code{Newsgroups} header
4166 (@pxref{To From Newsgroups}).
4168 The name (from the @code{From} header). This differs from the @code{n}
4169 spec in that it uses the function designated by the
4170 @code{gnus-extract-address-components} variable, which is slower, but
4171 may be more thorough.
4173 The address (from the @code{From} header). This works the same way as
4176 Number of lines in the article.
4178 Number of characters in the article. This specifier is not supported
4179 in some methods (like nnfolder).
4181 Indentation based on thread level (@pxref{Customizing Threading}).
4183 A complex trn-style thread tree, showing response-connecting trace
4186 Nothing if the article is a root and lots of spaces if it isn't (it
4187 pushes everything after it off the screen).
4189 Opening bracket, which is normally @samp{[}, but can also be @samp{<}
4190 for adopted articles (@pxref{Customizing Threading}).
4192 Closing bracket, which is normally @samp{]}, but can also be @samp{>}
4193 for adopted articles.
4195 One space for each thread level.
4197 Twenty minus thread level spaces.
4202 This misleadingly named specifier is the @dfn{secondary mark}. This
4203 mark will say whether the article has been replied to, has been cached,
4207 Score as a number (@pxref{Scoring}).
4209 @vindex gnus-summary-zcore-fuzz
4210 Zcore, @samp{+} if above the default level and @samp{-} if below the
4211 default level. If the difference between
4212 @code{gnus-summary-default-score} and the score is less than
4213 @code{gnus-summary-zcore-fuzz}, this spec will not be used.
4221 The @code{Date} in @code{DD-MMM} format.
4223 The @code{Date} in @var{YYYYMMDD}@code{T}@var{HHMMSS} format.
4229 Number of articles in the current sub-thread. Using this spec will slow
4230 down summary buffer generation somewhat.
4232 An @samp{=} (@code{gnus-not-empty-thread-mark}) will be displayed if the
4233 article has any children.
4239 User defined specifier. The next character in the format string should
4240 be a letter. Gnus will call the function
4241 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
4242 following @samp{%u}. The function will be passed the current header as
4243 argument. The function should return a string, which will be inserted
4244 into the summary just like information from any other summary specifier.
4247 The @samp{%U} (status), @samp{%R} (replied) and @samp{%z} (zcore) specs
4248 have to be handled with care. For reasons of efficiency, Gnus will
4249 compute what column these characters will end up in, and ``hard-code''
4250 that. This means that it is invalid to have these specs after a
4251 variable-length spec. Well, you might not be arrested, but your summary
4252 buffer will look strange, which is bad enough.
4254 The smart choice is to have these specs as far to the left as possible.
4255 (Isn't that the case with everything, though? But I digress.)
4257 This restriction may disappear in later versions of Gnus.
4260 @node To From Newsgroups
4261 @subsection To From Newsgroups
4265 In some groups (particularly in archive groups), the @code{From} header
4266 isn't very interesting, since all the articles there are written by
4267 you. To display the information in the @code{To} or @code{Newsgroups}
4268 headers instead, you need to decide three things: What information to
4269 gather; where to display it; and when to display it.
4273 @vindex gnus-extra-headers
4274 The reading of extra header information is controlled by the
4275 @code{gnus-extra-headers}. This is a list of header symbols. For
4279 (setq gnus-extra-headers
4280 '(To Newsgroups X-Newsreader))
4283 This will result in Gnus trying to obtain these three headers, and
4284 storing it in header structures for later easy retrieval.
4287 @findex gnus-extra-header
4288 The value of these extra headers can be accessed via the
4289 @code{gnus-extra-header} function. Here's a format line spec that will
4290 access the @code{X-Newsreader} header:
4293 "%~(form (gnus-extra-header 'X-Newsreader))@@"
4297 @vindex gnus-ignored-from-addresses
4298 The @code{gnus-ignored-from-addresses} variable says when the @samp{%f}
4299 summary line spec returns the @code{To}, @code{Newsreader} or
4300 @code{From} header. If this regexp matches the contents of the
4301 @code{From} header, the value of the @code{To} or @code{Newsreader}
4302 headers are used instead.
4306 @vindex nnmail-extra-headers
4307 A related variable is @code{nnmail-extra-headers}, which controls when
4308 to include extra headers when generating overview (@sc{nov}) files. If
4309 you have old overview files, you should regenerate them after changing
4312 @vindex gnus-summary-line-format
4313 You also have to instruct Gnus to display the data by changing the
4314 @code{%n} spec to the @code{%f} spec in the
4315 @code{gnus-summary-line-format} variable.
4317 In summary, you'd typically put something like the following in
4321 (setq gnus-extra-headers
4323 (setq nnmail-extra-headers gnus-extra-headers)
4324 (setq gnus-summary-line-format
4325 "%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n")
4326 (setq gnus-ignored-from-addresses
4330 Now, this is mostly useful for mail groups, where you have control over
4331 the @sc{nov} files that are created. However, if you can persuade your