10 * Gnus: (gnus). The newsreader Gnus.
15 @setchapternewpage odd
19 \documentclass[twoside,a4paper,openright,11pt]{book}
20 \usepackage[latin1]{inputenc}
21 \usepackage{pagestyle}
24 \input{gnusconfig.tex}
26 \ifx\pdfoutput\undefined
28 \usepackage[pdftex,bookmarks,colorlinks=true]{hyperref}
36 \newcommand{\gnusversionname}{Oort Gnus v0.05}
37 \newcommand{\gnuschaptername}{}
38 \newcommand{\gnussectionname}{}
40 \newcommand{\gnusbackslash}{/}
42 \newcommand{\gnusref}[1]{``#1'' on page \pageref{#1}}
43 \ifx\pdfoutput\undefined
44 \newcommand{\gnusuref}[1]{\gnustt{#1}}
46 \newcommand{\gnusuref}[1]{\href{#1}{\gnustt{#1}}}
48 \newcommand{\gnusxref}[1]{See ``#1'' on page \pageref{#1}}
49 \newcommand{\gnuspxref}[1]{see ``#1'' on page \pageref{#1}}
51 \newcommand{\gnuskindex}[1]{\index{#1}}
52 \newcommand{\gnusindex}[1]{\index{#1}}
54 \newcommand{\gnustt}[1]{{\gnusselectttfont{}#1}}
55 \newcommand{\gnuscode}[1]{\gnustt{#1}}
56 \newcommand{\gnussamp}[1]{``{\fontencoding{OT1}\gnusselectttfont{}#1}''}
57 \newcommand{\gnuslisp}[1]{\gnustt{#1}}
58 \newcommand{\gnuskbd}[1]{`\gnustt{#1}'}
59 \newcommand{\gnusfile}[1]{`\gnustt{#1}'}
60 \newcommand{\gnusdfn}[1]{\textit{#1}}
61 \newcommand{\gnusi}[1]{\textit{#1}}
62 \newcommand{\gnusstrong}[1]{\textbf{#1}}
63 \newcommand{\gnusemph}[1]{\textit{#1}}
64 \newcommand{\gnusvar}[1]{{\fontsize{10pt}{10}\selectfont\textsl{\textsf{#1}}}}
65 \newcommand{\gnussc}[1]{\textsc{#1}}
66 \newcommand{\gnustitle}[1]{{\huge\textbf{#1}}}
67 \newcommand{\gnusversion}[1]{{\small\textit{#1}}}
68 \newcommand{\gnusauthor}[1]{{\large\textbf{#1}}}
69 \newcommand{\gnusresult}[1]{\gnustt{=> #1}}
71 \newcommand{\gnusbullet}{{${\bullet}$}}
72 \newcommand{\gnusdollar}{\$}
73 \newcommand{\gnusampersand}{\&}
74 \newcommand{\gnuspercent}{\%}
75 \newcommand{\gnushash}{\#}
76 \newcommand{\gnushat}{\symbol{"5E}}
77 \newcommand{\gnusunderline}{\symbol{"5F}}
78 \newcommand{\gnusnot}{$\neg$}
79 \newcommand{\gnustilde}{\symbol{"7E}}
80 \newcommand{\gnusless}{{$<$}}
81 \newcommand{\gnusgreater}{{$>$}}
82 \newcommand{\gnusbraceleft}{{$>$}}
83 \newcommand{\gnusbraceright}{{$>$}}
85 \newcommand{\gnushead}{\raisebox{-1cm}{\epsfig{figure=ps/gnus-head,height=1cm}}}
86 \newcommand{\gnusinteresting}{
87 \marginpar[\mbox{}\hfill\gnushead]{\gnushead}
90 \newcommand{\gnuscleardoublepage}{\ifodd\count0\mbox{}\clearpage\thispagestyle{empty}\mbox{}\clearpage\else\clearpage\fi}
92 \newcommand{\gnuspagechapter}[1]{
99 \newcommand{\gnuschapter}[2]{
101 \ifdim \gnusdimen = 0pt\setcounter{page}{1}\pagestyle{gnus}\pagenumbering{arabic} \gnusdimen 1pt\fi
103 \renewcommand{\gnussectionname}{}
104 \renewcommand{\gnuschaptername}{#2}
105 \thispagestyle{empty}
107 \begin{picture}(500,500)(0,0)
108 \put(480,350){\makebox(0,0)[tr]{#1}}
109 \put(40,300){\makebox(500,50)[bl]{{\Huge\bf{#2}}}}
114 \newcommand{\gnusfigure}[3]{
116 \mbox{}\ifodd\count0\hspace*{-0.8cm}\else\hspace*{-3cm}\fi\begin{picture}(440,#2)
123 \newcommand{\gnusicon}[1]{
124 \marginpar[\mbox{}\hfill\raisebox{-1.5cm}{\epsfig{figure=ps/#1-up,height=1.5cm}}]{\raisebox{-1cm}{\epsfig{figure=ps/#1-up,height=1cm}}}
127 \newcommand{\gnuspicon}[1]{
128 \margindex{\epsfig{figure=#1,width=2cm}}
131 \newcommand{\gnusxface}[2]{
132 \margindex{\epsfig{figure=#1,width=1cm}\epsfig{figure=#2,width=1cm}}
135 \newcommand{\gnussmiley}[2]{
136 \margindex{\makebox[2cm]{\hfill\epsfig{figure=#1,width=0.5cm}\hfill\epsfig{figure=#2,width=0.5cm}\hfill}}
139 \newcommand{\gnusitemx}[1]{\mbox{}\vspace*{-\itemsep}\vspace*{-\parsep}\item#1}
141 \newcommand{\gnussection}[1]{
142 \renewcommand{\gnussectionname}{#1}
146 \newenvironment{codelist}%
151 \newenvironment{kbdlist}%
157 \newenvironment{dfnlist}%
162 \newenvironment{stronglist}%
167 \newenvironment{samplist}%
172 \newenvironment{varlist}%
177 \newenvironment{emphlist}%
182 \newlength\gnusheadtextwidth
183 \setlength{\gnusheadtextwidth}{\headtextwidth}
184 \addtolength{\gnusheadtextwidth}{1cm}
186 \newpagestyle{gnuspreamble}%
191 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\mbox{}}\textbf{\hfill\roman{page}}}
195 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\roman{page}\hfill\mbox{}}}
204 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
206 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
211 \newpagestyle{gnusindex}%
216 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\gnuschaptername\hfill\arabic{page}}}}
220 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}
228 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
230 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
240 \makebox[12cm]{\hspace*{3.1cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{chapter}.\arabic{section}} \textbf{\gnussectionname\hfill\arabic{page}}}}}
244 \makebox[12cm]{\hspace*{-2.95cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}}
252 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
254 \raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo,height=1cm}}
259 \pagenumbering{roman}
260 \pagestyle{gnuspreamble}
270 %\addtolength{\oddsidemargin}{-5cm}
271 %\addtolength{\evensidemargin}{-5cm}
273 \addtolength{\textheight}{2cm}
275 \gnustitle{\gnustitlename}\hfill\gnusversion{\gnusversionname}\\
278 \hspace*{0cm}\epsfig{figure=ps/gnus-big-logo,height=15cm}
281 \gnusauthor{by Lars Magne Ingebrigtsen}
288 \thispagestyle{empty}
290 Copyright \copyright{} 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002
291 Free Software Foundation, Inc.
294 Permission is granted to copy, distribute and/or modify this document
295 under the terms of the GNU Free Documentation License, Version 1.1 or
296 any later version published by the Free Software Foundation; with no
297 Invariant Sections, with the Front-Cover texts being ``A GNU
298 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
299 license is included in the section entitled ``GNU Free Documentation
300 License'' in the Emacs manual.
302 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
303 this GNU Manual, like GNU software. Copies published by the Free
304 Software Foundation raise funds for GNU development.''
306 This document is part of a collection distributed under the GNU Free
307 Documentation License. If you want to distribute this document
308 separately from the collection, you can do so by adding a copy of the
309 license to the document, as described in section 6 of the license.
317 This file documents Gnus, the GNU Emacs newsreader.
319 Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002
320 Free Software Foundation, Inc.
322 Permission is granted to copy, distribute and/or modify this document
323 under the terms of the GNU Free Documentation License, Version 1.1 or
324 any later version published by the Free Software Foundation; with the
325 Invariant Sections being none, with the Front-Cover texts being ``A GNU
326 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
327 license is included in the section entitled ``GNU Free Documentation
328 License'' in the Emacs manual.
330 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
331 this GNU Manual, like GNU software. Copies published by the Free
332 Software Foundation raise funds for GNU development.''
334 This document is part of a collection distributed under the GNU Free
335 Documentation License. If you want to distribute this document
336 separately from the collection, you can do so by adding a copy of the
337 license to the document, as described in section 6 of the license.
345 @author by Lars Magne Ingebrigtsen
348 @vskip 0pt plus 1filll
349 Copyright @copyright{} 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002
350 Free Software Foundation, Inc.
352 Permission is granted to copy, distribute and/or modify this document
353 under the terms of the GNU Free Documentation License, Version 1.1 or
354 any later version published by the Free Software Foundation; with no
355 Invariant Sections, with the Front-Cover texts being ``A GNU
356 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
357 license is included in the section entitled ``GNU Free Documentation
358 License'' in the Emacs manual.
360 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
361 this GNU Manual, like GNU software. Copies published by the Free
362 Software Foundation raise funds for GNU development.''
364 This document is part of a collection distributed under the GNU Free
365 Documentation License. If you want to distribute this document
366 separately from the collection, you can do so by adding a copy of the
367 license to the document, as described in section 6 of the license.
376 @top The Gnus Newsreader
380 You can read news (and mail) from within Emacs by using Gnus. The news
381 can be gotten by any nefarious means you can think of---@sc{nntp}, local
382 spool or your mbox file. All at the same time, if you want to push your
385 This manual corresponds to Oort Gnus v0.05
396 Gnus is the advanced, self-documenting, customizable, extensible
397 unreal-time newsreader for GNU Emacs.
399 Oops. That sounds oddly familiar, so let's start over again to avoid
400 being accused of plagiarism:
402 Gnus is a message-reading laboratory. It will let you look at just
403 about anything as if it were a newsgroup. You can read mail with it,
404 you can browse directories with it, you can @code{ftp} with it---you
405 can even read news with it!
407 Gnus tries to empower people who read news the same way Emacs empowers
408 people who edit text. Gnus sets no limits to what the user should be
409 allowed to do. Users are encouraged to extend Gnus to make it behave
410 like they want it to behave. A program should not control people;
411 people should be empowered to do what they want by using (or abusing)
417 * Starting Up:: Finding news can be a pain.
418 * Group Buffer:: Selecting, subscribing and killing groups.
419 * Summary Buffer:: Reading, saving and posting articles.
420 * Article Buffer:: Displaying and handling articles.
421 * Composing Messages:: Information on sending mail and news.
422 * Select Methods:: Gnus reads all messages from various select methods.
423 * Scoring:: Assigning values to articles.
424 * Various:: General purpose settings.
425 * The End:: Farewell and goodbye.
426 * Appendices:: Terminology, Emacs intro, FAQ, History, Internals.
427 * Index:: Variable, function and concept index.
428 * Key Index:: Key Index.
431 --- The Detailed Node Listing ---
435 * Finding the News:: Choosing a method for getting news.
436 * The First Time:: What does Gnus do the first time you start it?
437 * The Server is Down:: How can I read my mail then?
438 * Slave Gnusae:: You can have more than one Gnus active at a time.
439 * Fetching a Group:: Starting Gnus just to read a group.
440 * New Groups:: What is Gnus supposed to do with new groups?
441 * Changing Servers:: You may want to move from one server to another.
442 * Startup Files:: Those pesky startup files---@file{.newsrc}.
443 * Auto Save:: Recovering from a crash.
444 * The Active File:: Reading the active file over a slow line Takes Time.
445 * Startup Variables:: Other variables you might change.
449 * Checking New Groups:: Determining what groups are new.
450 * Subscription Methods:: What Gnus should do with new groups.
451 * Filtering New Groups:: Making Gnus ignore certain new groups.
455 * Group Buffer Format:: Information listed and how you can change it.
456 * Group Maneuvering:: Commands for moving in the group buffer.
457 * Selecting a Group:: Actually reading news.
458 * Subscription Commands:: Unsubscribing, killing, subscribing.
459 * Group Data:: Changing the info for a group.
460 * Group Levels:: Levels? What are those, then?
461 * Group Score:: A mechanism for finding out what groups you like.
462 * Marking Groups:: You can mark groups for later processing.
463 * Foreign Groups:: Creating and editing groups.
464 * Group Parameters:: Each group may have different parameters set.
465 * Listing Groups:: Gnus can list various subsets of the groups.
466 * Sorting Groups:: Re-arrange the group order.
467 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
468 * Browse Foreign Server:: You can browse a server. See what it has to offer.
469 * Exiting Gnus:: Stop reading news and get some work done.
470 * Group Topics:: A folding group mode divided into topics.
471 * Misc Group Stuff:: Other stuff that you can to do.
475 * Group Line Specification:: Deciding how the group buffer is to look.
476 * Group Modeline Specification:: The group buffer modeline.
477 * Group Highlighting:: Having nice colors in the group buffer.
481 * Topic Commands:: Interactive E-Z commands.
482 * Topic Variables:: How to customize the topics the Lisp Way.
483 * Topic Sorting:: Sorting each topic individually.
484 * Topic Topology:: A map of the world.
485 * Topic Parameters:: Parameters that apply to all groups in a topic.
489 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
490 * Group Information:: Information and help on groups and Gnus.
491 * Group Timestamp:: Making Gnus keep track of when you last read a group.
492 * File Commands:: Reading and writing the Gnus files.
493 * Sieve Commands:: Managing Sieve scripts.
497 * Summary Buffer Format:: Deciding how the summary buffer is to look.
498 * Summary Maneuvering:: Moving around the summary buffer.
499 * Choosing Articles:: Reading articles.
500 * Paging the Article:: Scrolling the current article.
501 * Reply Followup and Post:: Posting articles.
503 * Marking Articles:: Marking articles as read, expirable, etc.
504 * Limiting:: You can limit the summary buffer.
505 * Threading:: How threads are made.
506 * Sorting the Summary Buffer:: How articles and threads are sorted.
507 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
508 * Article Caching:: You may store articles in a cache.
509 * Persistent Articles:: Making articles expiry-resistant.
510 * Article Backlog:: Having already read articles hang around.
511 * Saving Articles:: Ways of customizing article saving.
512 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
513 * Article Treatment:: The article buffer can be mangled at will.
514 * MIME Commands:: Doing MIMEy things with the articles.
515 * Charsets:: Character set issues.
516 * Article Commands:: Doing various things with the article buffer.
517 * Summary Sorting:: Sorting the summary buffer in various ways.
518 * Finding the Parent:: No child support? Get the parent.
519 * Alternative Approaches:: Reading using non-default summaries.
520 * Tree Display:: A more visual display of threads.
521 * Mail Group Commands:: Some commands can only be used in mail groups.
522 * Various Summary Stuff:: What didn't fit anywhere else.
523 * Exiting the Summary Buffer:: Returning to the Group buffer,
524 or reselecting the current group.
525 * Crosspost Handling:: How crossposted articles are dealt with.
526 * Duplicate Suppression:: An alternative when crosspost handling fails.
527 * Security:: Decrypt and Verify.
528 * Mailing List:: Mailing list minor mode.
530 Summary Buffer Format
532 * Summary Buffer Lines:: You can specify how summary lines should look.
533 * To From Newsgroups:: How to not display your own name.
534 * Summary Buffer Mode Line:: You can say how the mode line should look.
535 * Summary Highlighting:: Making the summary buffer all pretty and nice.
539 * Choosing Commands:: Commands for choosing articles.
540 * Choosing Variables:: Variables that influence these commands.
542 Reply, Followup and Post
544 * Summary Mail Commands:: Sending mail.
545 * Summary Post Commands:: Sending news.
546 * Summary Message Commands:: Other Message-related commands.
547 * Canceling and Superseding::
551 * Unread Articles:: Marks for unread articles.
552 * Read Articles:: Marks for read articles.
553 * Other Marks:: Marks that do not affect readedness.
555 * Generic Marking Commands::
556 * Setting Process Marks::
560 * Setting Marks:: How to set and remove marks.
561 * Generic Marking Commands:: How to customize the marking.
562 * Setting Process Marks:: How to mark articles for later processing.
566 * Customizing Threading:: Variables you can change to affect the threading.
567 * Thread Commands:: Thread based commands in the summary buffer.
569 Customizing Threading
571 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
572 * Filling In Threads:: Making the threads displayed look fuller.
573 * More Threading:: Even more variables for fiddling with threads.
574 * Low-Level Threading:: You thought it was over... but you were wrong!
578 * Uuencoded Articles:: Uudecode articles.
579 * Shell Archives:: Unshar articles.
580 * PostScript Files:: Split PostScript.
581 * Other Files:: Plain save and binhex.
582 * Decoding Variables:: Variables for a happy decoding.
583 * Viewing Files:: You want to look at the result of the decoding?
587 * Rule Variables:: Variables that say how a file is to be viewed.
588 * Other Decode Variables:: Other decode variables.
589 * Uuencoding and Posting:: Variables for customizing uuencoding.
593 * Article Highlighting:: You want to make the article look like fruit salad.
594 * Article Fontisizing:: Making emphasized text look nice.
595 * Article Hiding:: You also want to make certain info go away.
596 * Article Washing:: Lots of way-neat functions to make life better.
597 * Article Header:: Doing various header transformations.
598 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
599 * Article Date:: Grumble, UT!
600 * Article Display:: Display various stuff---X-Face, Picons, Smileys
601 * Article Signature:: What is a signature?
602 * Article Miscellania:: Various other stuff.
604 Alternative Approaches
606 * Pick and Read:: First mark articles and then read them.
607 * Binary Groups:: Auto-decode all articles.
609 Various Summary Stuff
611 * Summary Group Information:: Information oriented commands.
612 * Searching for Articles:: Multiple article commands.
613 * Summary Generation Commands::
614 * Really Various Summary Commands:: Those pesky non-conformant commands.
618 * Hiding Headers:: Deciding what headers should be displayed.
619 * Using MIME:: Pushing articles through @sc{mime} before reading them.
620 * Customizing Articles:: Tailoring the look of the articles.
621 * Article Keymap:: Keystrokes available in the article buffer.
622 * Misc Article:: Other stuff.
626 * Mail:: Mailing and replying.
627 * Posting Server:: What server should you post via?
628 * Mail and Post:: Mailing and posting at the same time.
629 * Archived Messages:: Where Gnus stores the messages you've sent.
630 * Posting Styles:: An easier way to specify who you are.
631 * Drafts:: Postponing messages and rejected messages.
632 * Rejected Articles:: What happens if the server doesn't like your article?
633 * Signing and encrypting:: How to compose secure messages.
637 * Server Buffer:: Making and editing virtual servers.
638 * Getting News:: Reading USENET news with Gnus.
639 * Getting Mail:: Reading your personal mail with Gnus.
640 * Browsing the Web:: Getting messages from a plethora of Web sources.
641 * IMAP:: Using Gnus as a @sc{imap} client.
642 * Other Sources:: Reading directories, files, SOUP packets.
643 * Combined Groups:: Combining groups into one group.
644 * Gnus Unplugged:: Reading news and mail offline.
648 * Server Buffer Format:: You can customize the look of this buffer.
649 * Server Commands:: Commands to manipulate servers.
650 * Example Methods:: Examples server specifications.
651 * Creating a Virtual Server:: An example session.
652 * Server Variables:: Which variables to set.
653 * Servers and Methods:: You can use server names as select methods.
654 * Unavailable Servers:: Some servers you try to contact may be down.
658 * NNTP:: Reading news from an @sc{nntp} server.
659 * News Spool:: Reading news from the local spool.
663 * Direct Functions:: Connecting directly to the server.
664 * Indirect Functions:: Connecting indirectly to the server.
665 * Common Variables:: Understood by several connection functions.
669 * Mail in a Newsreader:: Important introductory notes.
670 * Getting Started Reading Mail:: A simple cookbook example.
671 * Splitting Mail:: How to create mail groups.
672 * Mail Sources:: How to tell Gnus where to get mail from.
673 * Mail Back End Variables:: Variables for customizing mail handling.
674 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
675 * Group Mail Splitting:: Use group customize to drive mail splitting.
676 * Incorporating Old Mail:: What about the old mail you have?
677 * Expiring Mail:: Getting rid of unwanted mail.
678 * Washing Mail:: Removing gruft from the mail you get.
679 * Duplicates:: Dealing with duplicated mail.
680 * Not Reading Mail:: Using mail back ends for reading other files.
681 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
685 * Mail Source Specifiers:: How to specify what a mail source is.
686 * Mail Source Customization:: Some variables that influence things.
687 * Fetching Mail:: Using the mail source specifiers.
689 Choosing a Mail Back End
691 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
692 * Rmail Babyl:: Emacs programs use the rmail babyl format.
693 * Mail Spool:: Store your mail in a private spool?
694 * MH Spool:: An mhspool-like back end.
695 * Mail Folders:: Having one file for each group.
696 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
701 * Web Searches:: Creating groups from articles that match a string.
702 * Slashdot:: Reading the Slashdot comments.
703 * Ultimate:: The Ultimate Bulletin Board systems.
704 * Web Archive:: Reading mailing list archived on web.
705 * RSS:: Reading RDF site summary.
706 * Customizing w3:: Doing stuff to Emacs/w3 from Gnus.
710 * Splitting in IMAP:: Splitting mail with nnimap.
711 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
712 * Expunging mailboxes:: Equivalent of a "compress mailbox" button.
716 * Directory Groups:: You can read a directory as if it was a newsgroup.
717 * Anything Groups:: Dired? Who needs dired?
718 * Document Groups:: Single files can be the basis of a group.
719 * SOUP:: Reading @sc{soup} packets ``offline''.
720 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
724 * Document Server Internals:: How to add your own document types.
728 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
729 * SOUP Groups:: A back end for reading @sc{soup} packets.
730 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
734 * Virtual Groups:: Combining articles from many groups.
735 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
739 * Agent Basics:: How it all is supposed to work.
740 * Agent Categories:: How to tell the Gnus Agent what to download.
741 * Agent Commands:: New commands for all the buffers.
742 * Agent Expiry:: How to make old articles go away.
743 * Agent and IMAP:: How to use the Agent with IMAP.
744 * Outgoing Messages:: What happens when you post/mail something?
745 * Agent Variables:: Customizing is fun.
746 * Example Setup:: An example @file{.gnus.el} file for offline people.
747 * Batching Agents:: How to fetch news from a @code{cron} job.
748 * Agent Caveats:: What you think it'll do and what it does.
752 * Category Syntax:: What a category looks like.
753 * Category Buffer:: A buffer for maintaining categories.
754 * Category Variables:: Customize'r'Us.
758 * Group Agent Commands::
759 * Summary Agent Commands::
760 * Server Agent Commands::
764 * Summary Score Commands:: Adding score entries for the current group.
765 * Group Score Commands:: General score commands.
766 * Score Variables:: Customize your scoring. (My, what terminology).
767 * Score File Format:: What a score file may contain.
768 * Score File Editing:: You can edit score files by hand as well.
769 * Adaptive Scoring:: Big Sister Gnus knows what you read.
770 * Home Score File:: How to say where new score entries are to go.
771 * Followups To Yourself:: Having Gnus notice when people answer you.
772 * Scoring On Other Headers:: Scoring on non-standard headers.
773 * Scoring Tips:: How to score effectively.
774 * Reverse Scoring:: That problem child of old is not problem.
775 * Global Score Files:: Earth-spanning, ear-splitting score files.
776 * Kill Files:: They are still here, but they can be ignored.
777 * Converting Kill Files:: Translating kill files to score files.
778 * GroupLens:: Getting predictions on what you like to read.
779 * Advanced Scoring:: Using logical expressions to build score rules.
780 * Score Decays:: It can be useful to let scores wither away.
784 * Using GroupLens:: How to make Gnus use GroupLens.
785 * Rating Articles:: Letting GroupLens know how you rate articles.
786 * Displaying Predictions:: Displaying predictions given by GroupLens.
787 * GroupLens Variables:: Customizing GroupLens.
791 * Advanced Scoring Syntax:: A definition.
792 * Advanced Scoring Examples:: What they look like.
793 * Advanced Scoring Tips:: Getting the most out of it.
797 * Process/Prefix:: A convention used by many treatment commands.
798 * Interactive:: Making Gnus ask you many questions.
799 * Symbolic Prefixes:: How to supply some Gnus functions with options.
800 * Formatting Variables:: You can specify what buffers should look like.
801 * Window Layout:: Configuring the Gnus buffer windows.
802 * Faces and Fonts:: How to change how faces look.
803 * Compilation:: How to speed Gnus up.
804 * Mode Lines:: Displaying information in the mode lines.
805 * Highlighting and Menus:: Making buffers look all nice and cozy.
806 * Buttons:: Get tendinitis in ten easy steps!
807 * Daemons:: Gnus can do things behind your back.
808 * NoCeM:: How to avoid spam and other fatty foods.
809 * Undo:: Some actions can be undone.
810 * Predicate Specifiers:: Specifying predicates.
811 * Moderation:: What to do if you're a moderator.
812 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
813 * Fuzzy Matching:: What's the big fuzz?
814 * Thwarting Email Spam:: A how-to on avoiding unsolicited commercial email.
815 * Various Various:: Things that are really various.
819 * Formatting Basics:: A formatting variable is basically a format string.
820 * Mode Line Formatting:: Some rules about mode line formatting variables.
821 * Advanced Formatting:: Modifying output in various ways.
822 * User-Defined Specs:: Having Gnus call your own functions.
823 * Formatting Fonts:: Making the formatting look colorful and nice.
824 * Positioning Point:: Moving point to a position after an operation.
825 * Tabulation:: Tabulating your output.
826 * Wide Characters:: Dealing with wide characters.
830 * Picons:: How to display pictures of what you're reading.
831 * Smileys:: Show all those happy faces the way they were meant to be shown.
832 * X-Face:: Display a funky, teensy black-and-white image.
833 * Toolbar:: Click'n'drool.
834 * XVarious:: Other XEmacsy Gnusey variables.
838 * Picon Basics:: What are picons and How do I get them.
839 * Picon Requirements:: Don't go further if you aren't using XEmacs.
840 * Easy Picons:: Displaying Picons---the easy way.
841 * Hard Picons:: The way you should do it. You'll learn something.
842 * Picon Useless Configuration:: Other variables you can trash/tweak/munge/play with.
846 * XEmacs:: Requirements for installing under XEmacs.
847 * History:: How Gnus got where it is today.
848 * On Writing Manuals:: Why this is not a beginner's guide.
849 * Terminology:: We use really difficult, like, words here.
850 * Customization:: Tailoring Gnus to your needs.
851 * Troubleshooting:: What you might try if things do not work.
852 * Gnus Reference Guide:: Rilly, rilly technical stuff.
853 * Emacs for Heathens:: A short introduction to Emacsian terms.
854 * Frequently Asked Questions::
858 * Gnus Versions:: What Gnus versions have been released.
859 * Other Gnus Versions:: Other Gnus versions that also have been released.
860 * Why?:: What's the point of Gnus?
861 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
862 * Conformity:: Gnus tries to conform to all standards.
863 * Emacsen:: Gnus can be run on a few modern Emacsen.
864 * Gnus Development:: How Gnus is developed.
865 * Contributors:: Oodles of people.
866 * New Features:: Pointers to some of the new stuff in Gnus.
870 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
871 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
872 * Red Gnus:: Third time best---Gnus 5.4/5.5.
873 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
874 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
878 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
879 * Slow Terminal Connection:: You run a remote Emacs.
880 * Little Disk Space:: You feel that having large setup files is icky.
881 * Slow Machine:: You feel like buying a faster machine.
885 * Gnus Utility Functions:: Common functions and variable to use.
886 * Back End Interface:: How Gnus communicates with the servers.
887 * Score File Syntax:: A BNF definition of the score file standard.
888 * Headers:: How Gnus stores headers internally.
889 * Ranges:: A handy format for storing mucho numbers.
890 * Group Info:: The group info format.
891 * Extended Interactive:: Symbolic prefixes and stuff.
892 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
893 * Various File Formats:: Formats of files that Gnus use.
897 * Required Back End Functions:: Functions that must be implemented.
898 * Optional Back End Functions:: Functions that need not be implemented.
899 * Error Messaging:: How to get messages and report errors.
900 * Writing New Back Ends:: Extending old back ends.
901 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
902 * Mail-like Back Ends:: Some tips on mail back ends.
906 * Active File Format:: Information on articles and groups available.
907 * Newsgroups File Format:: Group descriptions.
911 * Keystrokes:: Entering text and executing commands.
912 * Emacs Lisp:: The built-in Emacs programming language.
918 @chapter Starting Gnus
923 If your system administrator has set things up properly, starting Gnus
924 and reading news is extremely easy---you just type @kbd{M-x gnus} in
927 @findex gnus-other-frame
928 @kindex M-x gnus-other-frame
929 If you want to start Gnus in a different frame, you can use the command
930 @kbd{M-x gnus-other-frame} instead.
932 If things do not go smoothly at startup, you have to twiddle some
933 variables in your @file{~/.gnus} file. This file is similar to
934 @file{~/.emacs}, but is read when gnus starts.
936 If you puzzle at any terms used in this manual, please refer to the
937 terminology section (@pxref{Terminology}).
940 * Finding the News:: Choosing a method for getting news.
941 * The First Time:: What does Gnus do the first time you start it?
942 * The Server is Down:: How can I read my mail then?
943 * Slave Gnusae:: You can have more than one Gnus active at a time.
944 * Fetching a Group:: Starting Gnus just to read a group.
945 * New Groups:: What is Gnus supposed to do with new groups?
946 * Changing Servers:: You may want to move from one server to another.
947 * Startup Files:: Those pesky startup files---@file{.newsrc}.
948 * Auto Save:: Recovering from a crash.
949 * The Active File:: Reading the active file over a slow line Takes Time.
950 * Startup Variables:: Other variables you might change.
954 @node Finding the News
955 @section Finding the News
958 @vindex gnus-select-method
960 The @code{gnus-select-method} variable says where Gnus should look for
961 news. This variable should be a list where the first element says
962 @dfn{how} and the second element says @dfn{where}. This method is your
963 native method. All groups not fetched with this method are
966 For instance, if the @samp{news.somewhere.edu} @sc{nntp} server is where
967 you want to get your daily dosage of news from, you'd say:
970 (setq gnus-select-method '(nntp "news.somewhere.edu"))
973 If you want to read directly from the local spool, say:
976 (setq gnus-select-method '(nnspool ""))
979 If you can use a local spool, you probably should, as it will almost
980 certainly be much faster. But do not use the local spool if your
981 server is running Leafnode; in this case, use @code{(nntp "localhost")}.
983 @vindex gnus-nntpserver-file
985 @cindex @sc{nntp} server
986 If this variable is not set, Gnus will take a look at the
987 @code{NNTPSERVER} environment variable. If that variable isn't set,
988 Gnus will see whether @code{gnus-nntpserver-file}
989 (@file{/etc/nntpserver} by default) has any opinions on the matter. If
990 that fails as well, Gnus will try to use the machine running Emacs as an @sc{nntp} server. That's a long shot, though.
992 @vindex gnus-nntp-server
993 If @code{gnus-nntp-server} is set, this variable will override
994 @code{gnus-select-method}. You should therefore set
995 @code{gnus-nntp-server} to @code{nil}, which is what it is by default.
997 @vindex gnus-secondary-servers
998 @vindex gnus-nntp-server
999 You can also make Gnus prompt you interactively for the name of an
1000 @sc{nntp} server. If you give a non-numerical prefix to @code{gnus}
1001 (i.e., @kbd{C-u M-x gnus}), Gnus will let you choose between the servers
1002 in the @code{gnus-secondary-servers} list (if any). You can also just
1003 type in the name of any server you feel like visiting. (Note that this
1004 will set @code{gnus-nntp-server}, which means that if you then @kbd{M-x
1005 gnus} later in the same Emacs session, Gnus will contact the same
1008 @findex gnus-group-browse-foreign-server
1010 However, if you use one @sc{nntp} server regularly and are just
1011 interested in a couple of groups from a different server, you would be
1012 better served by using the @kbd{B} command in the group buffer. It will
1013 let you have a look at what groups are available, and you can subscribe
1014 to any of the groups you want to. This also makes @file{.newsrc}
1015 maintenance much tidier. @xref{Foreign Groups}.
1017 @vindex gnus-secondary-select-methods
1019 A slightly different approach to foreign groups is to set the
1020 @code{gnus-secondary-select-methods} variable. The select methods
1021 listed in this variable are in many ways just as native as the
1022 @code{gnus-select-method} server. They will also be queried for active
1023 files during startup (if that's required), and new newsgroups that
1024 appear on these servers will be subscribed (or not) just as native
1027 For instance, if you use the @code{nnmbox} back end to read your mail,
1028 you would typically set this variable to
1031 (setq gnus-secondary-select-methods '((nnmbox "")))
1035 @node The First Time
1036 @section The First Time
1037 @cindex first time usage
1039 If no startup files exist, Gnus will try to determine what groups should
1040 be subscribed by default.
1042 @vindex gnus-default-subscribed-newsgroups
1043 If the variable @code{gnus-default-subscribed-newsgroups} is set, Gnus
1044 will subscribe you to just those groups in that list, leaving the rest
1045 killed. Your system administrator should have set this variable to
1048 Since she hasn't, Gnus will just subscribe you to a few arbitrarily
1049 picked groups (i.e., @samp{*.newusers}). (@dfn{Arbitrary} is defined
1050 here as @dfn{whatever Lars thinks you should read}.)
1052 You'll also be subscribed to the Gnus documentation group, which should
1053 help you with most common problems.
1055 If @code{gnus-default-subscribed-newsgroups} is @code{t}, Gnus will just
1056 use the normal functions for handling new groups, and not do anything
1060 @node The Server is Down
1061 @section The Server is Down
1062 @cindex server errors
1064 If the default server is down, Gnus will understandably have some
1065 problems starting. However, if you have some mail groups in addition to
1066 the news groups, you may want to start Gnus anyway.
1068 Gnus, being the trusting sort of program, will ask whether to proceed
1069 without a native select method if that server can't be contacted. This
1070 will happen whether the server doesn't actually exist (i.e., you have
1071 given the wrong address) or the server has just momentarily taken ill
1072 for some reason or other. If you decide to continue and have no foreign
1073 groups, you'll find it difficult to actually do anything in the group
1074 buffer. But, hey, that's your problem. Blllrph!
1076 @findex gnus-no-server
1077 @kindex M-x gnus-no-server
1079 If you know that the server is definitely down, or you just want to read
1080 your mail without bothering with the server at all, you can use the
1081 @code{gnus-no-server} command to start Gnus. That might come in handy
1082 if you're in a hurry as well. This command will not attempt to contact
1083 your primary server---instead, it will just activate all groups on level
1084 1 and 2. (You should preferably keep no native groups on those two
1085 levels.) Also @pxref{Group Levels}.
1089 @section Slave Gnusae
1092 You might want to run more than one Emacs with more than one Gnus at the
1093 same time. If you are using different @file{.newsrc} files (e.g., if you
1094 are using the two different Gnusae to read from two different servers),
1095 that is no problem whatsoever. You just do it.
1097 The problem appears when you want to run two Gnusae that use the same
1098 @code{.newsrc} file.
1100 To work around that problem some, we here at the Think-Tank at the Gnus
1101 Towers have come up with a new concept: @dfn{Masters} and
1102 @dfn{slaves}. (We have applied for a patent on this concept, and have
1103 taken out a copyright on those words. If you wish to use those words in
1104 conjunction with each other, you have to send $1 per usage instance to
1105 me. Usage of the patent (@dfn{Master/Slave Relationships In Computer
1106 Applications}) will be much more expensive, of course.)
1108 Anyway, you start one Gnus up the normal way with @kbd{M-x gnus} (or
1109 however you do it). Each subsequent slave Gnusae should be started with
1110 @kbd{M-x gnus-slave}. These slaves won't save normal @file{.newsrc}
1111 files, but instead save @dfn{slave files} that contain information only
1112 on what groups have been read in the slave session. When a master Gnus
1113 starts, it will read (and delete) these slave files, incorporating all
1114 information from them. (The slave files will be read in the sequence
1115 they were created, so the latest changes will have precedence.)
1117 Information from the slave files has, of course, precedence over the
1118 information in the normal (i.e., master) @code{.newsrc} file.
1121 @node Fetching a Group
1122 @section Fetching a Group
1123 @cindex fetching a group
1125 @findex gnus-fetch-group
1126 It is sometimes convenient to be able to just say ``I want to read this
1127 group and I don't care whether Gnus has been started or not''. This is
1128 perhaps more useful for people who write code than for users, but the
1129 command @code{gnus-fetch-group} provides this functionality in any case.
1130 It takes the group name as a parameter.
1136 @cindex subscription
1138 @vindex gnus-check-new-newsgroups
1139 If you are satisfied that you really never want to see any new groups,
1140 you can set @code{gnus-check-new-newsgroups} to @code{nil}. This will
1141 also save you some time at startup. Even if this variable is
1142 @code{nil}, you can always subscribe to the new groups just by pressing
1143 @kbd{U} in the group buffer (@pxref{Group Maintenance}). This variable
1144 is @code{ask-server} by default. If you set this variable to
1145 @code{always}, then Gnus will query the back ends for new groups even
1146 when you do the @kbd{g} command (@pxref{Scanning New Messages}).
1149 * Checking New Groups:: Determining what groups are new.
1150 * Subscription Methods:: What Gnus should do with new groups.
1151 * Filtering New Groups:: Making Gnus ignore certain new groups.
1155 @node Checking New Groups
1156 @subsection Checking New Groups
1158 Gnus normally determines whether a group is new or not by comparing the
1159 list of groups from the active file(s) with the lists of subscribed and
1160 dead groups. This isn't a particularly fast method. If
1161 @code{gnus-check-new-newsgroups} is @code{ask-server}, Gnus will ask the
1162 server for new groups since the last time. This is both faster and
1163 cheaper. This also means that you can get rid of the list of killed
1164 groups altogether, so you may set @code{gnus-save-killed-list} to
1165 @code{nil}, which will save time both at startup, at exit, and all over.
1166 Saves disk space, too. Why isn't this the default, then?
1167 Unfortunately, not all servers support this command.
1169 I bet I know what you're thinking now: How do I find out whether my
1170 server supports @code{ask-server}? No? Good, because I don't have a
1171 fail-safe answer. I would suggest just setting this variable to
1172 @code{ask-server} and see whether any new groups appear within the next
1173 few days. If any do, then it works. If none do, then it doesn't
1174 work. I could write a function to make Gnus guess whether the server
1175 supports @code{ask-server}, but it would just be a guess. So I won't.
1176 You could @code{telnet} to the server and say @code{HELP} and see
1177 whether it lists @samp{NEWGROUPS} among the commands it understands. If
1178 it does, then it might work. (But there are servers that lists
1179 @samp{NEWGROUPS} without supporting the function properly.)
1181 This variable can also be a list of select methods. If so, Gnus will
1182 issue an @code{ask-server} command to each of the select methods, and
1183 subscribe them (or not) using the normal methods. This might be handy
1184 if you are monitoring a few servers for new groups. A side effect is
1185 that startup will take much longer, so you can meditate while waiting.
1186 Use the mantra ``dingnusdingnusdingnus'' to achieve permanent bliss.
1189 @node Subscription Methods
1190 @subsection Subscription Methods
1192 @vindex gnus-subscribe-newsgroup-method
1193 What Gnus does when it encounters a new group is determined by the
1194 @code{gnus-subscribe-newsgroup-method} variable.
1196 This variable should contain a function. This function will be called
1197 with the name of the new group as the only parameter.
1199 Some handy pre-fab functions are:
1203 @item gnus-subscribe-zombies
1204 @vindex gnus-subscribe-zombies
1205 Make all new groups zombies. This is the default. You can browse the
1206 zombies later (with @kbd{A z}) and either kill them all off properly
1207 (with @kbd{S z}), or subscribe to them (with @kbd{u}).
1209 @item gnus-subscribe-randomly
1210 @vindex gnus-subscribe-randomly
1211 Subscribe all new groups in arbitrary order. This really means that all
1212 new groups will be added at ``the top'' of the group buffer.
1214 @item gnus-subscribe-alphabetically
1215 @vindex gnus-subscribe-alphabetically
1216 Subscribe all new groups in alphabetical order.
1218 @item gnus-subscribe-hierarchically
1219 @vindex gnus-subscribe-hierarchically
1220 Subscribe all new groups hierarchically. The difference between this
1221 function and @code{gnus-subscribe-alphabetically} is slight.
1222 @code{gnus-subscribe-alphabetically} will subscribe new groups in a strictly
1223 alphabetical fashion, while this function will enter groups into its
1224 hierarchy. So if you want to have the @samp{rec} hierarchy before the
1225 @samp{comp} hierarchy, this function will not mess that configuration
1226 up. Or something like that.
1228 @item gnus-subscribe-interactively
1229 @vindex gnus-subscribe-interactively
1230 Subscribe new groups interactively. This means that Gnus will ask
1231 you about @strong{all} new groups. The groups you choose to subscribe
1232 to will be subscribed hierarchically.
1234 @item gnus-subscribe-killed
1235 @vindex gnus-subscribe-killed
1236 Kill all new groups.
1238 @item gnus-subscribe-topics
1239 @vindex gnus-subscribe-topics
1240 Put the groups into the topic that has a matching @code{subscribe} topic
1241 parameter (@pxref{Topic Parameters}). For instance, a @code{subscribe}
1242 topic parameter that looks like
1248 will mean that all groups that match that regex will be subscribed under
1251 If no topics match the groups, the groups will be subscribed in the
1256 @vindex gnus-subscribe-hierarchical-interactive
1257 A closely related variable is
1258 @code{gnus-subscribe-hierarchical-interactive}. (That's quite a
1259 mouthful.) If this variable is non-@code{nil}, Gnus will ask you in a
1260 hierarchical fashion whether to subscribe to new groups or not. Gnus
1261 will ask you for each sub-hierarchy whether you want to descend the
1264 One common mistake is to set the variable a few paragraphs above
1265 (@code{gnus-subscribe-newsgroup-method}) to
1266 @code{gnus-subscribe-hierarchical-interactive}. This is an error. This
1267 will not work. This is ga-ga. So don't do it.
1270 @node Filtering New Groups
1271 @subsection Filtering New Groups
1273 A nice and portable way to control which new newsgroups should be
1274 subscribed (or ignored) is to put an @dfn{options} line at the start of
1275 the @file{.newsrc} file. Here's an example:
1278 options -n !alt.all !rec.all sci.all
1281 @vindex gnus-subscribe-options-newsgroup-method
1282 This line obviously belongs to a serious-minded intellectual scientific
1283 person (or she may just be plain old boring), because it says that all
1284 groups that have names beginning with @samp{alt} and @samp{rec} should
1285 be ignored, and all groups with names beginning with @samp{sci} should
1286 be subscribed. Gnus will not use the normal subscription method for
1287 subscribing these groups.
1288 @code{gnus-subscribe-options-newsgroup-method} is used instead. This
1289 variable defaults to @code{gnus-subscribe-alphabetically}.
1291 @vindex gnus-options-not-subscribe
1292 @vindex gnus-options-subscribe
1293 If you don't want to mess with your @file{.newsrc} file, you can just
1294 set the two variables @code{gnus-options-subscribe} and
1295 @code{gnus-options-not-subscribe}. These two variables do exactly the
1296 same as the @file{.newsrc} @samp{options -n} trick. Both are regexps,
1297 and if the new group matches the former, it will be unconditionally
1298 subscribed, and if it matches the latter, it will be ignored.
1300 @vindex gnus-auto-subscribed-groups
1301 Yet another variable that meddles here is
1302 @code{gnus-auto-subscribed-groups}. It works exactly like
1303 @code{gnus-options-subscribe}, and is therefore really superfluous, but I
1304 thought it would be nice to have two of these. This variable is more
1305 meant for setting some ground rules, while the other variable is used
1306 more for user fiddling. By default this variable makes all new groups
1307 that come from mail back ends (@code{nnml}, @code{nnbabyl},
1308 @code{nnfolder}, @code{nnmbox}, and @code{nnmh}) subscribed. If you
1309 don't like that, just set this variable to @code{nil}.
1311 New groups that match this regexp are subscribed using
1312 @code{gnus-subscribe-options-newsgroup-method}.
1315 @node Changing Servers
1316 @section Changing Servers
1317 @cindex changing servers
1319 Sometimes it is necessary to move from one @sc{nntp} server to another.
1320 This happens very rarely, but perhaps you change jobs, or one server is
1321 very flaky and you want to use another.
1323 Changing the server is pretty easy, right? You just change
1324 @code{gnus-select-method} to point to the new server?
1328 Article numbers are not (in any way) kept synchronized between different
1329 @sc{nntp} servers, and the only way Gnus keeps track of what articles
1330 you have read is by keeping track of article numbers. So when you
1331 change @code{gnus-select-method}, your @file{.newsrc} file becomes
1334 Gnus provides a few functions to attempt to translate a @file{.newsrc}
1335 file from one server to another. They all have one thing in
1336 common---they take a looong time to run. You don't want to use these
1337 functions more than absolutely necessary.
1339 @kindex M-x gnus-change-server
1340 @findex gnus-change-server
1341 If you have access to both servers, Gnus can request the headers for all
1342 the articles you have read and compare @code{Message-ID}s and map the
1343 article numbers of the read articles and article marks. The @kbd{M-x
1344 gnus-change-server} command will do this for all your native groups. It
1345 will prompt for the method you want to move to.
1347 @kindex M-x gnus-group-move-group-to-server
1348 @findex gnus-group-move-group-to-server
1349 You can also move individual groups with the @kbd{M-x
1350 gnus-group-move-group-to-server} command. This is useful if you want to
1351 move a (foreign) group from one server to another.
1353 @kindex M-x gnus-group-clear-data-on-native-groups
1354 @findex gnus-group-clear-data-on-native-groups
1355 If you don't have access to both the old and new server, all your marks
1356 and read ranges have become worthless. You can use the @kbd{M-x
1357 gnus-group-clear-data-on-native-groups} command to clear out all data
1358 that you have on your native groups. Use with caution.
1360 @kindex M-x gnus-group-clear-data
1361 @findex gnus-group-clear-data
1362 Clear the data from the current group only---nix out marks and the
1363 list of read articles (@code{gnus-group-clear-data}).
1365 After changing servers, you @strong{must} move the cache hierarchy away,
1366 since the cached articles will have wrong article numbers, which will
1367 affect which articles Gnus thinks are read.
1368 @code{gnus-group-clear-data-on-native-groups} will ask you if you want
1369 to have it done automatically; for @code{gnus-group-clear-data}, you
1370 can use @kbd{M-x gnus-cache-move-cache} (but beware, it will move the
1371 cache for all groups).
1375 @section Startup Files
1376 @cindex startup files
1381 Now, you all know about the @file{.newsrc} file. All subscription
1382 information is traditionally stored in this file.
1384 Things got a bit more complicated with @sc{gnus}. In addition to
1385 keeping the @file{.newsrc} file updated, it also used a file called
1386 @file{.newsrc.el} for storing all the information that didn't fit into
1387 the @file{.newsrc} file. (Actually, it also duplicated everything in
1388 the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
1389 files was the most recently saved, which enabled people to swap between
1390 @sc{gnus} and other newsreaders.
1392 That was kinda silly, so Gnus went one better: In addition to the
1393 @file{.newsrc} and @file{.newsrc.el} files, Gnus also has a file called
1394 @file{.newsrc.eld}. It will read whichever of these files that are most
1395 recent, but it will never write a @file{.newsrc.el} file. You should
1396 never delete the @file{.newsrc.eld} file---it contains much information
1397 not stored in the @file{.newsrc} file.
1399 @vindex gnus-save-newsrc-file
1400 @vindex gnus-read-newsrc-file
1401 You can turn off writing the @file{.newsrc} file by setting
1402 @code{gnus-save-newsrc-file} to @code{nil}, which means you can delete
1403 the file and save some space, as well as exiting from Gnus faster.
1404 However, this will make it impossible to use other newsreaders than
1405 Gnus. But hey, who would want to, right? Similarly, setting
1406 @code{gnus-read-newsrc-file} to @code{nil} makes Gnus ignore the
1407 @file{.newsrc} file and any @file{.newsrc-SERVER} files, which is
1408 convenient if you have a tendency to use Netscape once in a while.
1410 @vindex gnus-save-killed-list
1411 If @code{gnus-save-killed-list} (default @code{t}) is @code{nil}, Gnus
1412 will not save the list of killed groups to the startup file. This will
1413 save both time (when starting and quitting) and space (on disk). It
1414 will also mean that Gnus has no record of what groups are new or old,
1415 so the automatic new groups subscription methods become meaningless.
1416 You should always set @code{gnus-check-new-newsgroups} to @code{nil} or
1417 @code{ask-server} if you set this variable to @code{nil} (@pxref{New
1418 Groups}). This variable can also be a regular expression. If that's
1419 the case, remove all groups that do not match this regexp before
1420 saving. This can be useful in certain obscure situations that involve
1421 several servers where not all servers support @code{ask-server}.
1423 @vindex gnus-startup-file
1424 The @code{gnus-startup-file} variable says where the startup files are.
1425 The default value is @file{~/.newsrc}, with the Gnus (El Dingo) startup
1426 file being whatever that one is, with a @samp{.eld} appended.
1428 @vindex gnus-save-newsrc-hook
1429 @vindex gnus-save-quick-newsrc-hook
1430 @vindex gnus-save-standard-newsrc-hook
1431 @code{gnus-save-newsrc-hook} is called before saving any of the newsrc
1432 files, while @code{gnus-save-quick-newsrc-hook} is called just before
1433 saving the @file{.newsrc.eld} file, and
1434 @code{gnus-save-standard-newsrc-hook} is called just before saving the
1435 @file{.newsrc} file. The latter two are commonly used to turn version
1436 control on or off. Version control is on by default when saving the
1437 startup files. If you want to turn backup creation off, say something like:
1440 (defun turn-off-backup ()
1441 (set (make-local-variable 'backup-inhibited) t))
1443 (add-hook 'gnus-save-quick-newsrc-hook 'turn-off-backup)
1444 (add-hook 'gnus-save-standard-newsrc-hook 'turn-off-backup)
1447 @vindex gnus-init-file
1448 When Gnus starts, it will read the @code{gnus-site-init-file}
1449 (@file{.../site-lisp/gnus} by default) and @code{gnus-init-file}
1450 (@file{~/.gnus} by default) files. These are normal Emacs Lisp files
1451 and can be used to avoid cluttering your @file{~/.emacs} and
1452 @file{site-init} files with Gnus stuff. Gnus will also check for files
1453 with the same names as these, but with @file{.elc} and @file{.el}
1454 suffixes. In other words, if you have set @code{gnus-init-file} to
1455 @file{~/.gnus}, it will look for @file{~/.gnus.elc}, @file{~/.gnus.el},
1456 and finally @file{~/.gnus} (in this order).
1462 @cindex dribble file
1465 Whenever you do something that changes the Gnus data (reading articles,
1466 catching up, killing/subscribing groups), the change is added to a
1467 special @dfn{dribble buffer}. This buffer is auto-saved the normal
1468 Emacs way. If your Emacs should crash before you have saved the
1469 @file{.newsrc} files, all changes you have made can be recovered from
1472 If Gnus detects this file at startup, it will ask the user whether to
1473 read it. The auto save file is deleted whenever the real startup file is
1476 @vindex gnus-use-dribble-file
1477 If @code{gnus-use-dribble-file} is @code{nil}, Gnus won't create and
1478 maintain a dribble buffer. The default is @code{t}.
1480 @vindex gnus-dribble-directory
1481 Gnus will put the dribble file(s) in @code{gnus-dribble-directory}. If
1482 this variable is @code{nil}, which it is by default, Gnus will dribble
1483 into the directory where the @file{.newsrc} file is located. (This is
1484 normally the user's home directory.) The dribble file will get the same
1485 file permissions as the @code{.newsrc} file.
1487 @vindex gnus-always-read-dribble-file
1488 If @code{gnus-always-read-dribble-file} is non-@code{nil}, Gnus will
1489 read the dribble file on startup without querying the user.
1492 @node The Active File
1493 @section The Active File
1495 @cindex ignored groups
1497 When Gnus starts, or indeed whenever it tries to determine whether new
1498 articles have arrived, it reads the active file. This is a very large
1499 file that lists all the active groups and articles on the server.
1501 @vindex gnus-ignored-newsgroups
1502 Before examining the active file, Gnus deletes all lines that match the
1503 regexp @code{gnus-ignored-newsgroups}. This is done primarily to reject
1504 any groups with bogus names, but you can use this variable to make Gnus
1505 ignore hierarchies you aren't ever interested in. However, this is not
1506 recommended. In fact, it's highly discouraged. Instead, @pxref{New
1507 Groups} for an overview of other variables that can be used instead.
1510 @c @code{nil} by default, and will slow down active file handling somewhat
1511 @c if you set it to anything else.
1513 @vindex gnus-read-active-file
1515 The active file can be rather Huge, so if you have a slow network, you
1516 can set @code{gnus-read-active-file} to @code{nil} to prevent Gnus from
1517 reading the active file. This variable is @code{some} by default.
1519 Gnus will try to make do by getting information just on the groups that
1520 you actually subscribe to.
1522 Note that if you subscribe to lots and lots of groups, setting this
1523 variable to @code{nil} will probably make Gnus slower, not faster. At
1524 present, having this variable @code{nil} will slow Gnus down
1525 considerably, unless you read news over a 2400 baud modem.
1527 This variable can also have the value @code{some}. Gnus will then
1528 attempt to read active info only on the subscribed groups. On some
1529 servers this is quite fast (on sparkling, brand new INN servers that
1530 support the @code{LIST ACTIVE group} command), on others this isn't fast
1531 at all. In any case, @code{some} should be faster than @code{nil}, and
1532 is certainly faster than @code{t} over slow lines.
1534 Some news servers (old versions of Leafnode and old versions of INN, for
1535 instance) do not support the @code{LIST ACTIVE group}. For these
1536 servers, @code{nil} is probably the most efficient value for this
1539 If this variable is @code{nil}, Gnus will ask for group info in total
1540 lock-step, which isn't very fast. If it is @code{some} and you use an
1541 @sc{nntp} server, Gnus will pump out commands as fast as it can, and
1542 read all the replies in one swoop. This will normally result in better
1543 performance, but if the server does not support the aforementioned
1544 @code{LIST ACTIVE group} command, this isn't very nice to the server.
1546 If you think that starting up Gnus takes too long, try all the three
1547 different values for this variable and see what works best for you.
1549 In any case, if you use @code{some} or @code{nil}, you should definitely
1550 kill all groups that you aren't interested in to speed things up.
1552 Note that this variable also affects active file retrieval from
1553 secondary select methods.
1556 @node Startup Variables
1557 @section Startup Variables
1561 @item gnus-load-hook
1562 @vindex gnus-load-hook
1563 A hook run while Gnus is being loaded. Note that this hook will
1564 normally be run just once in each Emacs session, no matter how many
1565 times you start Gnus.
1567 @item gnus-before-startup-hook
1568 @vindex gnus-before-startup-hook
1569 A hook run after starting up Gnus successfully.
1571 @item gnus-startup-hook
1572 @vindex gnus-startup-hook
1573 A hook run as the very last thing after starting up Gnus
1575 @item gnus-started-hook
1576 @vindex gnus-started-hook
1577 A hook that is run as the very last thing after starting up Gnus
1580 @item gnus-setup-news-hook
1581 @vindex gnus-setup-news-hook
1582 A hook that is run after reading the @file{.newsrc} file(s), but before
1583 generating the group buffer.
1585 @item gnus-check-bogus-newsgroups
1586 @vindex gnus-check-bogus-newsgroups
1587 If non-@code{nil}, Gnus will check for and delete all bogus groups at
1588 startup. A @dfn{bogus group} is a group that you have in your
1589 @file{.newsrc} file, but doesn't exist on the news server. Checking for
1590 bogus groups can take quite a while, so to save time and resources it's
1591 best to leave this option off, and do the checking for bogus groups once
1592 in a while from the group buffer instead (@pxref{Group Maintenance}).
1594 @item gnus-inhibit-startup-message
1595 @vindex gnus-inhibit-startup-message
1596 If non-@code{nil}, the startup message won't be displayed. That way,
1597 your boss might not notice as easily that you are reading news instead
1598 of doing your job. Note that this variable is used before
1599 @file{.gnus.el} is loaded, so it should be set in @code{.emacs} instead.
1601 @item gnus-no-groups-message
1602 @vindex gnus-no-groups-message
1603 Message displayed by Gnus when no groups are available.
1605 @item gnus-play-startup-jingle
1606 @vindex gnus-play-startup-jingle
1607 If non-@code{nil}, play the Gnus jingle at startup.
1609 @item gnus-startup-jingle
1610 @vindex gnus-startup-jingle
1611 Jingle to be played if the above variable is non-@code{nil}. The
1612 default is @samp{Tuxedomoon.Jingle4.au}.
1618 @chapter Group Buffer
1619 @cindex group buffer
1621 @c Alex Schroeder suggests to rearrange this as follows:
1623 @c <kensanata> ok, just save it for reference. I'll go to bed in a minute.
1624 @c 1. Selecting a Group, 2. (new) Finding a Group, 3. Group Levels,
1625 @c 4. Subscription Commands, 5. Group Maneuvering, 6. Group Data,
1626 @c 7. Group Score, 8. Group Buffer Format
1627 @c <kensanata> Group Levels should have more information on levels 5 to 9. I
1628 @c suggest to split the 4th paragraph ("Gnus considers groups...") as follows:
1629 @c <kensanata> First, "Gnus considers groups... (default 9)."
1630 @c <kensanata> New, a table summarizing what levels 1 to 9 mean.
1631 @c <kensanata> Third, "Gnus treats subscribed ... reasons of efficiency"
1632 @c <kensanata> Then expand the next paragraph or add some more to it.
1633 @c This short one sentence explains levels 1 and 2, therefore I understand
1634 @c that I should keep important news at 3 and boring news at 4.
1635 @c Say so! Then go on to explain why I should bother with levels 6 to 9.
1636 @c Maybe keep those that you don't want to read temporarily at 6,
1637 @c those that you never want to read at 8, those that offend your
1638 @c human rights at 9...
1641 The @dfn{group buffer} lists all (or parts) of the available groups. It
1642 is the first buffer shown when Gnus starts, and will never be killed as
1643 long as Gnus is active.
1647 \gnusfigure{The Group Buffer}{320}{
1648 \put(75,50){\epsfig{figure=ps/group,height=9cm}}
1649 \put(120,37){\makebox(0,0)[t]{Buffer name}}
1650 \put(120,38){\vector(1,2){10}}
1651 \put(40,60){\makebox(0,0)[r]{Mode line}}
1652 \put(40,58){\vector(1,0){30}}
1653 \put(200,28){\makebox(0,0)[t]{Native select method}}
1654 \put(200,26){\vector(-1,2){15}}
1660 * Group Buffer Format:: Information listed and how you can change it.
1661 * Group Maneuvering:: Commands for moving in the group buffer.
1662 * Selecting a Group:: Actually reading news.
1663 * Subscription Commands:: Unsubscribing, killing, subscribing.
1664 * Group Data:: Changing the info for a group.
1665 * Group Levels:: Levels? What are those, then?
1666 * Group Score:: A mechanism for finding out what groups you like.
1667 * Marking Groups:: You can mark groups for later processing.
1668 * Foreign Groups:: Creating and editing groups.
1669 * Group Parameters:: Each group may have different parameters set.
1670 * Listing Groups:: Gnus can list various subsets of the groups.
1671 * Sorting Groups:: Re-arrange the group order.
1672 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
1673 * Browse Foreign Server:: You can browse a server. See what it has to offer.
1674 * Exiting Gnus:: Stop reading news and get some work done.
1675 * Group Topics:: A folding group mode divided into topics.
1676 * Misc Group Stuff:: Other stuff that you can to do.
1680 @node Group Buffer Format
1681 @section Group Buffer Format
1684 * Group Line Specification:: Deciding how the group buffer is to look.
1685 * Group Modeline Specification:: The group buffer modeline.
1686 * Group Highlighting:: Having nice colors in the group buffer.
1690 @node Group Line Specification
1691 @subsection Group Line Specification
1692 @cindex group buffer format
1694 The default format of the group buffer is nice and dull, but you can
1695 make it as exciting and ugly as you feel like.
1697 Here's a couple of example group lines:
1700 25: news.announce.newusers
1701 * 0: alt.fan.andrea-dworkin
1706 You can see that there are 25 unread articles in
1707 @samp{news.announce.newusers}. There are no unread articles, but some
1708 ticked articles, in @samp{alt.fan.andrea-dworkin} (see that little
1709 asterisk at the beginning of the line?).
1711 @vindex gnus-group-line-format
1712 You can change that format to whatever you want by fiddling with the
1713 @code{gnus-group-line-format} variable. This variable works along the
1714 lines of a @code{format} specification, which is pretty much the same as
1715 a @code{printf} specifications, for those of you who use (feh!) C.
1716 @xref{Formatting Variables}.
1718 @samp{%M%S%5y: %(%g%)\n} is the value that produced those lines above.
1720 There should always be a colon on the line; the cursor always moves to
1721 the colon after performing an operation. @xref{Positioning
1722 Point}. Nothing else is required---not even the group name. All
1723 displayed text is just window dressing, and is never examined by Gnus.
1724 Gnus stores all real information it needs using text properties.
1726 (Note that if you make a really strange, wonderful, spreadsheet-like
1727 layout, everybody will believe you are hard at work with the accounting
1728 instead of wasting time reading news.)
1730 Here's a list of all available format characters:
1735 An asterisk if the group only has marked articles.
1738 Whether the group is subscribed.
1741 Level of subscribedness.
1744 Number of unread articles.
1747 Number of dormant articles.
1750 Number of ticked articles.
1753 Number of read articles.
1756 Estimated total number of articles. (This is really @var{max-number}
1757 minus @var{min-number} plus 1.)
1759 Gnus uses this estimation because the NNTP protocol provides efficient
1760 access to @var{max-number} and @var{min-number} but getting the true
1761 unread message count is not possible efficiently. For hysterical
1762 raisins, even the mail back ends, where the true number of unread
1763 messages might be available efficiently, use the same limited
1764 interface. To remove this restriction from Gnus means that the
1765 back end interface has to be changed, which is not an easy job. If you
1766 want to work on this, please contact the Gnus mailing list.
1769 Number of unread, unticked, non-dormant articles.
1772 Number of ticked and dormant articles.
1781 Newsgroup description.
1784 @samp{m} if moderated.
1787 @samp{(m)} if moderated.
1796 A string that looks like @samp{<%s:%n>} if a foreign select method is
1800 Indentation based on the level of the topic (@pxref{Group Topics}).
1803 @vindex gnus-group-uncollapsed-levels
1804 Short (collapsed) group name. The @code{gnus-group-uncollapsed-levels}
1805 variable says how many levels to leave at the end of the group name.
1806 The default is 1---this will mean that group names like
1807 @samp{gnu.emacs.gnus} will be shortened to @samp{g.e.gnus}.
1810 @vindex gnus-new-mail-mark
1812 @samp{%} (@code{gnus-new-mail-mark}) if there has arrived new mail to
1816 @samp{#} (@code{gnus-process-mark}) if the group is process marked.
1819 A string that says when you last read the group (@pxref{Group
1823 User defined specifier. The next character in the format string should
1824 be a letter. Gnus will call the function
1825 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
1826 following @samp{%u}. The function will be passed a single dummy
1827 parameter as argument. The function should return a string, which will
1828 be inserted into the buffer just like information from any other
1833 All the ``number-of'' specs will be filled with an asterisk (@samp{*})
1834 if no info is available---for instance, if it is a non-activated foreign
1835 group, or a bogus native group.
1838 @node Group Modeline Specification
1839 @subsection Group Modeline Specification
1840 @cindex group modeline
1842 @vindex gnus-group-mode-line-format
1843 The mode line can be changed by setting
1844 @code{gnus-group-mode-line-format} (@pxref{Mode Line Formatting}). It
1845 doesn't understand that many format specifiers:
1849 The native news server.
1851 The native select method.
1855 @node Group Highlighting
1856 @subsection Group Highlighting
1857 @cindex highlighting
1858 @cindex group highlighting
1860 @vindex gnus-group-highlight
1861 Highlighting in the group buffer is controlled by the
1862 @code{gnus-group-highlight} variable. This is an alist with elements
1863 that look like @code{(@var{form} . @var{face})}. If @var{form} evaluates to
1864 something non-@code{nil}, the @var{face} will be used on the line.
1866 Here's an example value for this variable that might look nice if the
1870 (cond (window-system
1871 (setq custom-background-mode 'light)
1872 (defface my-group-face-1
1873 '((t (:foreground "Red" :bold t))) "First group face")
1874 (defface my-group-face-2
1875 '((t (:foreground "DarkSeaGreen4" :bold t))) "Second group face")
1876 (defface my-group-face-3
1877 '((t (:foreground "Green4" :bold t))) "Third group face")
1878 (defface my-group-face-4
1879 '((t (:foreground "SteelBlue" :bold t))) "Fourth group face")
1880 (defface my-group-face-5
1881 '((t (:foreground "Blue" :bold t))) "Fifth group face")))
1883 (setq gnus-group-highlight
1884 '(((> unread 200) . my-group-face-1)
1885 ((and (< level 3) (zerop unread)) . my-group-face-2)
1886 ((< level 3) . my-group-face-3)
1887 ((zerop unread) . my-group-face-4)
1888 (t . my-group-face-5)))
1891 Also @pxref{Faces and Fonts}.
1893 Variables that are dynamically bound when the forms are evaluated
1900 The number of unread articles in the group.
1904 Whether the group is a mail group.
1906 The level of the group.
1908 The score of the group.
1910 The number of ticked articles in the group.
1912 The total number of articles in the group. Or rather, MAX-NUMBER minus
1913 MIN-NUMBER plus one.
1915 When using the topic minor mode, this variable is bound to the current
1916 topic being inserted.
1919 When the forms are @code{eval}ed, point is at the beginning of the line
1920 of the group in question, so you can use many of the normal Gnus
1921 functions for snarfing info on the group.
1923 @vindex gnus-group-update-hook
1924 @findex gnus-group-highlight-line
1925 @code{gnus-group-update-hook} is called when a group line is changed.
1926 It will not be called when @code{gnus-visual} is @code{nil}. This hook
1927 calls @code{gnus-group-highlight-line} by default.
1930 @node Group Maneuvering
1931 @section Group Maneuvering
1932 @cindex group movement
1934 All movement commands understand the numeric prefix and will behave as
1935 expected, hopefully.
1941 @findex gnus-group-next-unread-group
1942 Go to the next group that has unread articles
1943 (@code{gnus-group-next-unread-group}).
1949 @findex gnus-group-prev-unread-group
1950 Go to the previous group that has unread articles
1951 (@code{gnus-group-prev-unread-group}).
1955 @findex gnus-group-next-group
1956 Go to the next group (@code{gnus-group-next-group}).
1960 @findex gnus-group-prev-group
1961 Go to the previous group (@code{gnus-group-prev-group}).
1965 @findex gnus-group-next-unread-group-same-level
1966 Go to the next unread group on the same (or lower) level
1967 (@code{gnus-group-next-unread-group-same-level}).
1971 @findex gnus-group-prev-unread-group-same-level
1972 Go to the previous unread group on the same (or lower) level
1973 (@code{gnus-group-prev-unread-group-same-level}).
1976 Three commands for jumping to groups:
1982 @findex gnus-group-jump-to-group
1983 Jump to a group (and make it visible if it isn't already)
1984 (@code{gnus-group-jump-to-group}). Killed groups can be jumped to, just
1989 @findex gnus-group-best-unread-group
1990 Jump to the unread group with the lowest level
1991 (@code{gnus-group-best-unread-group}).
1995 @findex gnus-group-first-unread-group
1996 Jump to the first group with unread articles
1997 (@code{gnus-group-first-unread-group}).
2000 @vindex gnus-group-goto-unread
2001 If @code{gnus-group-goto-unread} is @code{nil}, all the movement
2002 commands will move to the next group, not the next unread group. Even
2003 the commands that say they move to the next unread group. The default
2007 @node Selecting a Group
2008 @section Selecting a Group
2009 @cindex group selection
2014 @kindex SPACE (Group)
2015 @findex gnus-group-read-group
2016 Select the current group, switch to the summary buffer and display the
2017 first unread article (@code{gnus-group-read-group}). If there are no
2018 unread articles in the group, or if you give a non-numerical prefix to
2019 this command, Gnus will offer to fetch all the old articles in this
2020 group from the server. If you give a numerical prefix @var{N}, @var{N}
2021 determines the number of articles Gnus will fetch. If @var{N} is
2022 positive, Gnus fetches the @var{N} newest articles, if @var{N} is
2023 negative, Gnus fetches the @code{abs(@var{N})} oldest articles.
2025 Thus, @kbd{SPC} enters the group normally, @kbd{C-u SPC} offers old
2026 articles, @kbd{C-u 4 2 SPC} fetches the 42 newest articles, and @kbd{C-u
2027 - 4 2 SPC} fetches the 42 oldest ones.
2029 When you are in the group (in the Summary buffer), you can type
2030 @kbd{M-g} to fetch new articles, or @kbd{C-u M-g} to also show the old
2035 @findex gnus-group-select-group
2036 Select the current group and switch to the summary buffer
2037 (@code{gnus-group-select-group}). Takes the same arguments as
2038 @code{gnus-group-read-group}---the only difference is that this command
2039 does not display the first unread article automatically upon group
2043 @kindex M-RET (Group)
2044 @findex gnus-group-quick-select-group
2045 This does the same as the command above, but tries to do it with the
2046 minimum amount of fuzz (@code{gnus-group-quick-select-group}). No
2047 scoring/killing will be performed, there will be no highlights and no
2048 expunging. This might be useful if you're in a real hurry and have to
2049 enter some humongous group. If you give a 0 prefix to this command
2050 (i.e., @kbd{0 M-RET}), Gnus won't even generate the summary buffer,
2051 which is useful if you want to toggle threading before generating the
2052 summary buffer (@pxref{Summary Generation Commands}).
2055 @kindex M-SPACE (Group)
2056 @findex gnus-group-visible-select-group
2057 This is yet one more command that does the same as the @kbd{RET}
2058 command, but this one does it without expunging and hiding dormants
2059 (@code{gnus-group-visible-select-group}).
2062 @kindex C-M-RET (Group)
2063 @findex gnus-group-select-group-ephemerally
2064 Finally, this command selects the current group ephemerally without
2065 doing any processing of its contents
2066 (@code{gnus-group-select-group-ephemerally}). Even threading has been
2067 turned off. Everything you do in the group after selecting it in this
2068 manner will have no permanent effects.
2072 @vindex gnus-large-newsgroup
2073 The @code{gnus-large-newsgroup} variable says what Gnus should consider
2074 to be a big group. This is 200 by default. If the group has more
2075 (unread and/or ticked) articles than this, Gnus will query the user
2076 before entering the group. The user can then specify how many articles
2077 should be fetched from the server. If the user specifies a negative
2078 number (@code{-n}), the @code{n} oldest articles will be fetched. If it
2079 is positive, the @code{n} articles that have arrived most recently will
2082 @vindex gnus-select-group-hook
2083 @vindex gnus-auto-select-first
2084 If @code{gnus-auto-select-first} is non-@code{nil}, select an article
2085 automatically when entering a group with the @kbd{SPACE} command.
2086 Which article this is is controlled by the
2087 @code{gnus-auto-select-subject} variable. Valid values for this
2093 Place point on the subject line of the first unread article.
2096 Place point on the subject line of the first article.
2099 Place point on the subject line of the first unseen article.
2101 @item unseen-or-unread
2102 Place point on the subject line of the first unseen article, and if
2103 there is no such article, place point on the subject line of the first
2107 Place point on the subject line of the highest-scored unread article.
2111 This variable can also be a function. In that case, that function
2112 will be called to place point on a subject line.
2114 If you want to prevent automatic selection in some group (say, in a
2115 binary group with Huge articles) you can set the
2116 @code{gnus-auto-select-first} variable to @code{nil} in
2117 @code{gnus-select-group-hook}, which is called when a group is
2121 @node Subscription Commands
2122 @section Subscription Commands
2123 @cindex subscription
2131 @findex gnus-group-unsubscribe-current-group
2132 @c @icon{gnus-group-unsubscribe}
2133 Toggle subscription to the current group
2134 (@code{gnus-group-unsubscribe-current-group}).
2140 @findex gnus-group-unsubscribe-group
2141 Prompt for a group to subscribe, and then subscribe it. If it was
2142 subscribed already, unsubscribe it instead
2143 (@code{gnus-group-unsubscribe-group}).
2149 @findex gnus-group-kill-group
2150 @c @icon{gnus-group-kill-group}
2151 Kill the current group (@code{gnus-group-kill-group}).
2157 @findex gnus-group-yank-group
2158 Yank the last killed group (@code{gnus-group-yank-group}).
2161 @kindex C-x C-t (Group)
2162 @findex gnus-group-transpose-groups
2163 Transpose two groups (@code{gnus-group-transpose-groups}). This isn't
2164 really a subscription command, but you can use it instead of a
2165 kill-and-yank sequence sometimes.
2171 @findex gnus-group-kill-region
2172 Kill all groups in the region (@code{gnus-group-kill-region}).
2176 @findex gnus-group-kill-all-zombies
2177 Kill all zombie groups (@code{gnus-group-kill-all-zombies}).
2180 @kindex S C-k (Group)
2181 @findex gnus-group-kill-level
2182 Kill all groups on a certain level (@code{gnus-group-kill-level}).
2183 These groups can't be yanked back after killing, so this command should
2184 be used with some caution. The only time where this command comes in
2185 really handy is when you have a @file{.newsrc} with lots of unsubscribed
2186 groups that you want to get rid off. @kbd{S C-k} on level 7 will
2187 kill off all unsubscribed groups that do not have message numbers in the
2188 @file{.newsrc} file.
2192 Also @pxref{Group Levels}.
2202 @findex gnus-group-catchup-current
2203 @vindex gnus-group-catchup-group-hook
2204 @c @icon{gnus-group-catchup-current}
2205 Mark all unticked articles in this group as read
2206 (@code{gnus-group-catchup-current}).
2207 @code{gnus-group-catchup-group-hook} is called when catching up a group from
2212 @findex gnus-group-catchup-current-all
2213 Mark all articles in this group, even the ticked ones, as read
2214 (@code{gnus-group-catchup-current-all}).
2218 @findex gnus-group-clear-data
2219 Clear the data from the current group---nix out marks and the list of
2220 read articles (@code{gnus-group-clear-data}).
2222 @item M-x gnus-group-clear-data-on-native-groups
2223 @kindex M-x gnus-group-clear-data-on-native-groups
2224 @findex gnus-group-clear-data-on-native-groups
2225 If you have switched from one @sc{nntp} server to another, all your marks
2226 and read ranges have become worthless. You can use this command to
2227 clear out all data that you have on your native groups. Use with
2234 @section Group Levels
2238 All groups have a level of @dfn{subscribedness}. For instance, if a
2239 group is on level 2, it is more subscribed than a group on level 5. You
2240 can ask Gnus to just list groups on a given level or lower
2241 (@pxref{Listing Groups}), or to just check for new articles in groups on
2242 a given level or lower (@pxref{Scanning New Messages}).
2244 Remember: The higher the level of the group, the less important it is.
2250 @findex gnus-group-set-current-level
2251 Set the level of the current group. If a numeric prefix is given, the
2252 next @var{n} groups will have their levels set. The user will be
2253 prompted for a level.
2256 @vindex gnus-level-killed
2257 @vindex gnus-level-zombie
2258 @vindex gnus-level-unsubscribed
2259 @vindex gnus-level-subscribed
2260 Gnus considers groups from levels 1 to
2261 @code{gnus-level-subscribed} (inclusive) (default 5) to be subscribed,
2262 @code{gnus-level-subscribed} (exclusive) and
2263 @code{gnus-level-unsubscribed} (inclusive) (default 7) to be
2264 unsubscribed, @code{gnus-level-zombie} to be zombies (walking dead)
2265 (default 8) and @code{gnus-level-killed} to be killed (completely dead)
2266 (default 9). Gnus treats subscribed and unsubscribed groups exactly the
2267 same, but zombie and killed groups have no information on what articles
2268 you have read, etc, stored. This distinction between dead and living
2269 groups isn't done because it is nice or clever, it is done purely for
2270 reasons of efficiency.
2272 It is recommended that you keep all your mail groups (if any) on quite
2273 low levels (e.g. 1 or 2).
2275 Maybe the following description of the default behavior of Gnus helps to
2276 understand what these levels are all about. By default, Gnus shows you
2277 subscribed nonempty groups, but by hitting @kbd{L} you can have it show
2278 empty subscribed groups and unsubscribed groups, too. Type @kbd{l} to
2279 go back to showing nonempty subscribed groups again. Thus, unsubscribed
2280 groups are hidden, in a way.
2282 Zombie and killed groups are similar to unsubscribed groups in that they
2283 are hidden by default. But they are different from subscribed and
2284 unsubscribed groups in that Gnus doesn't ask the news server for
2285 information (number of messages, number of unread messages) on zombie
2286 and killed groups. Normally, you use @kbd{C-k} to kill the groups you
2287 aren't interested in. If most groups are killed, Gnus is faster.
2289 Why does Gnus distinguish between zombie and killed groups? Well, when
2290 a new group arrives on the server, Gnus by default makes it a zombie
2291 group. This means that you are normally not bothered with new groups,
2292 but you can type @kbd{A z} to get a list of all new groups. Subscribe
2293 the ones you like and kill the ones you don't want. (@kbd{A k} shows a
2294 list of killed groups.)
2296 If you want to play with the level variables, you should show some care.
2297 Set them once, and don't touch them ever again. Better yet, don't touch
2298 them at all unless you know exactly what you're doing.
2300 @vindex gnus-level-default-unsubscribed
2301 @vindex gnus-level-default-subscribed
2302 Two closely related variables are @code{gnus-level-default-subscribed}
2303 (default 3) and @code{gnus-level-default-unsubscribed} (default 6),
2304 which are the levels that new groups will be put on if they are
2305 (un)subscribed. These two variables should, of course, be inside the
2306 relevant valid ranges.
2308 @vindex gnus-keep-same-level
2309 If @code{gnus-keep-same-level} is non-@code{nil}, some movement commands
2310 will only move to groups of the same level (or lower). In
2311 particular, going from the last article in one group to the next group
2312 will go to the next group of the same level (or lower). This might be
2313 handy if you want to read the most important groups before you read the
2316 If this variable is @code{best}, Gnus will make the next newsgroup the
2317 one with the best level.
2319 @vindex gnus-group-default-list-level
2320 All groups with a level less than or equal to
2321 @code{gnus-group-default-list-level} will be listed in the group buffer
2324 @vindex gnus-group-list-inactive-groups
2325 If @code{gnus-group-list-inactive-groups} is non-@code{nil}, non-active
2326 groups will be listed along with the unread groups. This variable is
2327 @code{t} by default. If it is @code{nil}, inactive groups won't be
2330 @vindex gnus-group-use-permanent-levels
2331 If @code{gnus-group-use-permanent-levels} is non-@code{nil}, once you
2332 give a level prefix to @kbd{g} or @kbd{l}, all subsequent commands will
2333 use this level as the ``work'' level.
2335 @vindex gnus-activate-level
2336 Gnus will normally just activate (i. e., query the server about) groups
2337 on level @code{gnus-activate-level} or less. If you don't want to
2338 activate unsubscribed groups, for instance, you might set this variable
2339 to 5. The default is 6.
2343 @section Group Score
2348 You would normally keep important groups on high levels, but that scheme
2349 is somewhat restrictive. Don't you wish you could have Gnus sort the
2350 group buffer according to how often you read groups, perhaps? Within
2353 This is what @dfn{group score} is for. You can have Gnus assign a score
2354 to each group through the mechanism described below. You can then sort
2355 the group buffer based on this score. Alternatively, you can sort on
2356 score and then level. (Taken together, the level and the score is
2357 called the @dfn{rank} of the group. A group that is on level 4 and has
2358 a score of 1 has a higher rank than a group on level 5 that has a score
2359 of 300. (The level is the most significant part and the score is the
2360 least significant part.))
2362 @findex gnus-summary-bubble-group
2363 If you want groups you read often to get higher scores than groups you
2364 read seldom you can add the @code{gnus-summary-bubble-group} function to
2365 the @code{gnus-summary-exit-hook} hook. This will result (after
2366 sorting) in a bubbling sort of action. If you want to see that in
2367 action after each summary exit, you can add
2368 @code{gnus-group-sort-groups-by-rank} or
2369 @code{gnus-group-sort-groups-by-score} to the same hook, but that will
2370 slow things down somewhat.
2373 @node Marking Groups
2374 @section Marking Groups
2375 @cindex marking groups
2377 If you want to perform some command on several groups, and they appear
2378 subsequently in the group buffer, you would normally just give a
2379 numerical prefix to the command. Most group commands will then do your
2380 bidding on those groups.
2382 However, if the groups are not in sequential order, you can still
2383 perform a command on several groups. You simply mark the groups first
2384 with the process mark and then execute the command.
2392 @findex gnus-group-mark-group
2393 Set the mark on the current group (@code{gnus-group-mark-group}).
2399 @findex gnus-group-unmark-group
2400 Remove the mark from the current group
2401 (@code{gnus-group-unmark-group}).
2405 @findex gnus-group-unmark-all-groups
2406 Remove the mark from all groups (@code{gnus-group-unmark-all-groups}).
2410 @findex gnus-group-mark-region
2411 Mark all groups between point and mark (@code{gnus-group-mark-region}).
2415 @findex gnus-group-mark-buffer
2416 Mark all groups in the buffer (@code{gnus-group-mark-buffer}).
2420 @findex gnus-group-mark-regexp
2421 Mark all groups that match some regular expression
2422 (@code{gnus-group-mark-regexp}).
2425 Also @pxref{Process/Prefix}.
2427 @findex gnus-group-universal-argument
2428 If you want to execute some command on all groups that have been marked
2429 with the process mark, you can use the @kbd{M-&}
2430 (@code{gnus-group-universal-argument}) command. It will prompt you for
2431 the command to be executed.
2434 @node Foreign Groups
2435 @section Foreign Groups
2436 @cindex foreign groups
2438 Below are some group mode commands for making and editing general foreign
2439 groups, as well as commands to ease the creation of a few
2440 special-purpose groups. All these commands insert the newly created
2441 groups under point---@code{gnus-subscribe-newsgroup-method} is not
2448 @findex gnus-group-make-group
2449 @cindex making groups
2450 Make a new group (@code{gnus-group-make-group}). Gnus will prompt you
2451 for a name, a method and possibly an @dfn{address}. For an easier way
2452 to subscribe to @sc{nntp} groups, @pxref{Browse Foreign Server}.
2456 @findex gnus-group-rename-group
2457 @cindex renaming groups
2458 Rename the current group to something else
2459 (@code{gnus-group-rename-group}). This is valid only on some
2460 groups---mail groups mostly. This command might very well be quite slow
2466 @findex gnus-group-customize
2467 Customize the group parameters (@code{gnus-group-customize}).
2471 @findex gnus-group-edit-group-method
2472 @cindex renaming groups
2473 Enter a buffer where you can edit the select method of the current
2474 group (@code{gnus-group-edit-group-method}).
2478 @findex gnus-group-edit-group-parameters
2479 Enter a buffer where you can edit the group parameters
2480 (@code{gnus-group-edit-group-parameters}).
2484 @findex gnus-group-edit-group
2485 Enter a buffer where you can edit the group info
2486 (@code{gnus-group-edit-group}).
2490 @findex gnus-group-make-directory-group
2492 Make a directory group (@pxref{Directory Groups}). You will be prompted
2493 for a directory name (@code{gnus-group-make-directory-group}).
2498 @findex gnus-group-make-help-group
2499 Make the Gnus help group (@code{gnus-group-make-help-group}).
2503 @cindex (ding) archive
2504 @cindex archive group
2505 @findex gnus-group-make-archive-group
2506 @vindex gnus-group-archive-directory
2507 @vindex gnus-group-recent-archive-directory
2508 Make a Gnus archive group (@code{gnus-group-make-archive-group}). By
2509 default a group pointing to the most recent articles will be created
2510 (@code{gnus-group-recent-archive-directory}), but given a prefix, a full
2511 group will be created from @code{gnus-group-archive-directory}.
2515 @findex gnus-group-make-kiboze-group
2517 Make a kiboze group. You will be prompted for a name, for a regexp to
2518 match groups to be ``included'' in the kiboze group, and a series of
2519 strings to match on headers (@code{gnus-group-make-kiboze-group}).
2520 @xref{Kibozed Groups}.
2524 @findex gnus-group-enter-directory
2526 Read an arbitrary directory as if it were a newsgroup with the
2527 @code{nneething} back end (@code{gnus-group-enter-directory}).
2528 @xref{Anything Groups}.
2532 @findex gnus-group-make-doc-group
2533 @cindex ClariNet Briefs
2535 Make a group based on some file or other
2536 (@code{gnus-group-make-doc-group}). If you give a prefix to this
2537 command, you will be prompted for a file name and a file type.
2538 Currently supported types are @code{mbox}, @code{babyl},
2539 @code{digest}, @code{news}, @code{rnews}, @code{mmdf}, @code{forward},
2540 @code{rfc934}, @code{rfc822-forward}, @code{mime-parts},
2541 @code{standard-digest}, @code{slack-digest}, @code{clari-briefs},
2542 @code{nsmail}, @code{outlook}, @code{oe-dbx}, and @code{mailman}. If
2543 you run this command without a prefix, Gnus will guess at the file
2544 type. @xref{Document Groups}.
2548 @vindex gnus-useful-groups
2549 @findex gnus-group-make-useful-group
2550 Create one of the groups mentioned in @code{gnus-useful-groups}
2551 (@code{gnus-group-make-useful-group}).
2555 @findex gnus-group-make-web-group
2560 Make an ephemeral group based on a web search
2561 (@code{gnus-group-make-web-group}). If you give a prefix to this
2562 command, make a solid group instead. You will be prompted for the
2563 search engine type and the search string. Valid search engine types
2564 include @code{dejanews}, @code{altavista} and @code{reference}.
2565 @xref{Web Searches}.
2567 If you use the @code{dejanews} search engine, you can limit the search
2568 to a particular group by using a match string like
2569 @samp{~g alt.sysadmin.recovery shaving}.
2572 @kindex G DEL (Group)
2573 @findex gnus-group-delete-group
2574 This function will delete the current group
2575 (@code{gnus-group-delete-group}). If given a prefix, this function will
2576 actually delete all the articles in the group, and forcibly remove the
2577 group itself from the face of the Earth. Use a prefix only if you are
2578 absolutely sure of what you are doing. This command can't be used on
2579 read-only groups (like @code{nntp} group), though.
2583 @findex gnus-group-make-empty-virtual
2584 Make a new, fresh, empty @code{nnvirtual} group
2585 (@code{gnus-group-make-empty-virtual}). @xref{Virtual Groups}.
2589 @findex gnus-group-add-to-virtual
2590 Add the current group to an @code{nnvirtual} group
2591 (@code{gnus-group-add-to-virtual}). Uses the process/prefix convention.
2594 @xref{Select Methods}, for more information on the various select
2597 @vindex gnus-activate-foreign-newsgroups
2598 If @code{gnus-activate-foreign-newsgroups} is a positive number,
2599 Gnus will check all foreign groups with this level or lower at startup.
2600 This might take quite a while, especially if you subscribe to lots of
2601 groups from different @sc{nntp} servers. Also @pxref{Group Levels};
2602 @code{gnus-activate-level} also affects activation of foreign
2606 @node Group Parameters
2607 @section Group Parameters
2608 @cindex group parameters
2610 The group parameters store information local to a particular group.
2611 Here's an example group parameter list:
2614 ((to-address . "ding@@gnus.org")
2618 We see that each element consists of a "dotted pair"---the thing before
2619 the dot is the key, while the thing after the dot is the value. All the
2620 parameters have this form @emph{except} local variable specs, which are
2621 not dotted pairs, but proper lists.
2623 Some parameters have correspondant customizable variables, each of which
2624 is an alist of regexps and values.
2626 The following group parameters can be used:
2631 Address used by when doing followups and new posts.
2634 (to-address . "some@@where.com")
2637 This is primarily useful in mail groups that represent closed mailing
2638 lists---mailing lists where it's expected that everybody that writes to
2639 the mailing list is subscribed to it. Since using this parameter
2640 ensures that the mail only goes to the mailing list itself, it means
2641 that members won't receive two copies of your followups.
2643 Using @code{to-address} will actually work whether the group is foreign
2644 or not. Let's say there's a group on the server that is called
2645 @samp{fa.4ad-l}. This is a real newsgroup, but the server has gotten
2646 the articles from a mail-to-news gateway. Posting directly to this
2647 group is therefore impossible---you have to send mail to the mailing
2648 list address instead.
2650 See also @code{gnus-parameter-to-address-alist}.
2654 Address used when doing @kbd{a} in that group.
2657 (to-list . "some@@where.com")
2660 It is totally ignored
2661 when doing a followup---except that if it is present in a news group,
2662 you'll get mail group semantics when doing @kbd{f}.
2664 If you do an @kbd{a} command in a mail group and you have neither a
2665 @code{to-list} group parameter nor a @code{to-address} group parameter,
2666 then a @code{to-list} group parameter will be added automatically upon
2667 sending the message if @code{gnus-add-to-list} is set to @code{t}.
2668 @vindex gnus-add-to-list
2670 If you do an @kbd{a} command in a mail group and you don't have a
2671 @code{to-list} group parameter, one will be added automatically upon
2672 sending the message.
2674 @findex gnus-mailing-list-mode
2675 @cindex Mail List Groups
2676 If this variable is set, @code{gnus-mailing-list-mode} is turned on when
2677 entering summary buffer.
2679 See also @code{gnus-parameter-to-list-alist}.
2683 If this parameter is set to @code{t}, Gnus will consider the
2684 to-address and to-list parameters for this group as addresses of
2685 mailing lists you are subscribed to. Giving Gnus this information
2686 will help it to generate correct Mail-Followup-To headers for your
2687 posts to these lists.
2689 See also @code{gnus-find-subscribed-addresses}, the function that
2690 directly uses this group parameter.
2694 If the group parameter list has the element @code{(visible . t)},
2695 that group will always be visible in the Group buffer, regardless
2696 of whether it has any unread articles.
2698 @item broken-reply-to
2699 @cindex broken-reply-to
2700 Elements like @code{(broken-reply-to . t)} signals that @code{Reply-To}
2701 headers in this group are to be ignored. This can be useful if you're
2702 reading a mailing list group where the listserv has inserted
2703 @code{Reply-To} headers that point back to the listserv itself. This is
2704 broken behavior. So there!
2708 Elements like @code{(to-group . "some.group.name")} means that all
2709 posts in that group will be sent to @code{some.group.name}.
2713 If you have @code{(newsgroup . t)} in the group parameter list, Gnus
2714 will treat all responses as if they were responses to news articles.
2715 This can be useful if you have a mail group that's really a mirror of a
2720 If @code{(gcc-self . t)} is present in the group parameter list, newly
2721 composed messages will be @code{Gcc}'d to the current group. If
2722 @code{(gcc-self . none)} is present, no @code{Gcc:} header will be
2723 generated, if @code{(gcc-self . "string")} is present, this string will
2724 be inserted literally as a @code{gcc} header. This parameter takes
2725 precedence over any default @code{Gcc} rules as described later
2726 (@pxref{Archived Messages}).
2730 If the group parameter has an element that looks like @code{(auto-expire
2731 . t)}, all articles read will be marked as expirable. For an
2732 alternative approach, @pxref{Expiring Mail}.
2734 See also @code{gnus-auto-expirable-newsgroups}.
2737 @cindex total-expire
2738 If the group parameter has an element that looks like
2739 @code{(total-expire . t)}, all read articles will be put through the
2740 expiry process, even if they are not marked as expirable. Use with
2741 caution. Unread, ticked and dormant articles are not eligible for
2744 See also @code{gnus-total-expirable-newsgroups}.
2748 @vindex nnmail-expiry-wait-function
2749 If the group parameter has an element that looks like @code{(expiry-wait
2750 . 10)}, this value will override any @code{nnmail-expiry-wait} and
2751 @code{nnmail-expiry-wait-function} when expiring expirable messages.
2752 The value can either be a number of days (not necessarily an integer) or
2753 the symbols @code{never} or @code{immediate}.
2756 @cindex score file group parameter
2757 Elements that look like @code{(score-file . "file")} will make
2758 @file{file} into the current score file for the group in question. All
2759 interactive score entries will be put into this file.
2762 @cindex adapt file group parameter
2763 Elements that look like @code{(adapt-file . "file")} will make
2764 @file{file} into the current adaptive file for the group in question.
2765 All adaptive score entries will be put into this file.
2768 @cindex admin-address
2769 When unsubscribing from a mailing list you should never send the
2770 unsubscription notice to the mailing list itself. Instead, you'd send
2771 messages to the administrative address. This parameter allows you to
2772 put the admin address somewhere convenient.
2776 Elements that look like @code{(display . MODE)} say which articles to
2777 display on entering the group. Valid values are:
2781 Display all articles, both read and unread.
2784 Display the last INTEGER articles in the group. This is the same as
2785 entering the group with C-u INTEGER.
2788 Display the default visible articles, which normally includes unread and
2792 Display articles that satisfy a predicate.
2794 Here are some examples:
2798 Display only read articles.
2801 Display everything except expirable articles.
2803 @item [and (not reply) (not expire)]
2804 Display everything except expirable and articles you've already
2808 The available operators are @code{not}, @code{and} and @code{or}.
2809 Predicates include @code{tick}, @code{unsend}, @code{undownload},
2810 @code{read}, @code{dormant}, @code{expire}, @code{reply},
2811 @code{killed}, @code{bookmark}, @code{score}, @code{save},
2812 @code{cache}, @code{forward}, @code{seen} and @code{recent}.
2816 The @code{display} parameter works by limiting the summary buffer to
2817 the subset specified. You can pop the limit by using the @kbd{/ w}
2818 command (@pxref{Limiting}).
2822 Elements that look like @code{(comment . "This is a comment")}
2823 are arbitrary comments on the group. They are currently ignored by
2824 Gnus, but provide a place for you to store information on particular
2829 Elements that look like @code{(charset . iso-8859-1)} will make
2830 @code{iso-8859-1} the default charset; that is, the charset that will be
2831 used for all articles that do not specify a charset.
2833 See also @code{gnus-group-charset-alist}.
2835 @item ignored-charsets
2836 @cindex ignored-charset
2837 Elements that look like @code{(ignored-charsets x-unknown iso-8859-1)}
2838 will make @code{iso-8859-1} and @code{x-unknown} ignored; that is, the
2839 default charset will be used for decoding articles.
2841 See also @code{gnus-group-ignored-charsets-alist}.
2844 @cindex posting-style
2845 You can store additional posting style information for this group only
2846 here (@pxref{Posting Styles}). The format is that of an entry in the
2847 @code{gnus-posting-styles} alist, except that there's no regexp matching
2848 the group name (of course). Style elements in this group parameter will
2849 take precedence over the ones found in @code{gnus-posting-styles}.
2851 For instance, if you want a funky name and signature in this group only,
2852 instead of hacking @code{gnus-posting-styles}, you could put something
2853 like this in the group parameters:
2858 (signature "Funky Signature"))
2863 If it is set, the value is used as the method for posting message
2864 instead of @code{gnus-post-method}.
2868 An item like @code{(banner . "regex")} causes any part of an article
2869 that matches the regular expression "regex" to be stripped. Instead of
2870 "regex", you can also use the symbol @code{signature} which strips the
2871 last signature or any of the elements of the alist
2872 @code{gnus-article-banner-alist}.
2876 This parameter contains a Sieve test that should match incoming mail
2877 that should be placed in this group. From this group parameter, a
2878 Sieve @samp{IF} control structure is generated, having the test as the
2879 condition and @samp{fileinto "group.name";} as the body.
2881 For example, if the INBOX.list.sieve group has the @code{(sieve
2882 address "sender" "sieve-admin@@extundo.com")} group parameter, when
2883 translating the group parameter into a Sieve script (@pxref{Sieve
2884 Commands}) the following Sieve code is generated:
2887 if address \"sender\" \"sieve-admin@@extundo.com\" @{
2888 fileinto \"INBOX.list.sieve\";
2892 The Sieve language is described in RFC 3028. @xref{Top, , Top, sieve,
2895 @item (@var{variable} @var{form})
2896 You can use the group parameters to set variables local to the group you
2897 are entering. If you want to turn threading off in @samp{news.answers},
2898 you could put @code{(gnus-show-threads nil)} in the group parameters of
2899 that group. @code{gnus-show-threads} will be made into a local variable
2900 in the summary buffer you enter, and the form @code{nil} will be
2901 @code{eval}ed there.
2903 This can also be used as a group-specific hook function, if you'd like.
2904 If you want to hear a beep when you enter a group, you could put
2905 something like @code{(dummy-variable (ding))} in the parameters of that
2906 group. @code{dummy-variable} will be set to the result of the
2907 @code{(ding)} form, but who cares?
2911 Use the @kbd{G p} or the @kbd{G c} command to edit group parameters of a
2912 group. (@kbd{G p} presents you with a Lisp-based interface, @kbd{G c}
2913 presents you with a Customize-like interface. The latter helps avoid
2914 silly Lisp errors.) You might also be interested in reading about topic
2915 parameters (@pxref{Topic Parameters}).
2917 Group parameters can be set via the @code{gnus-parameters} variable too.
2918 But some variables, such as @code{visible}, have no effect. For
2922 (setq gnus-parameters
2924 (gnus-show-threads nil)
2925 (gnus-use-scoring nil)
2926 (gnus-summary-line-format
2927 "%U%R%z%I%(%[%d:%ub%-23,23f%]%) %s\n")
2931 ("^nnimap:\\(foo.bar\\)$"
2935 (gnus-use-scoring t))
2939 (broken-reply-to . t))))
2942 String value of parameters will be subjected to regexp substitution, as
2943 the @code{to-group} example shows.
2946 @node Listing Groups
2947 @section Listing Groups
2948 @cindex group listing
2950 These commands all list various slices of the groups available.
2958 @findex gnus-group-list-groups
2959 List all groups that have unread articles
2960 (@code{gnus-group-list-groups}). If the numeric prefix is used, this
2961 command will list only groups of level ARG and lower. By default, it
2962 only lists groups of level five (i. e.,
2963 @code{gnus-group-default-list-level}) or lower (i.e., just subscribed
2970 @findex gnus-group-list-all-groups
2971 List all groups, whether they have unread articles or not
2972 (@code{gnus-group-list-all-groups}). If the numeric prefix is used,
2973 this command will list only groups of level ARG and lower. By default,
2974 it lists groups of level seven or lower (i.e., just subscribed and
2975 unsubscribed groups).
2979 @findex gnus-group-list-level
2980 List all unread groups on a specific level
2981 (@code{gnus-group-list-level}). If given a prefix, also list the groups
2982 with no unread articles.
2986 @findex gnus-group-list-killed
2987 List all killed groups (@code{gnus-group-list-killed}). If given a
2988 prefix argument, really list all groups that are available, but aren't
2989 currently (un)subscribed. This could entail reading the active file
2994 @findex gnus-group-list-zombies
2995 List all zombie groups (@code{gnus-group-list-zombies}).
2999 @findex gnus-group-list-matching
3000 List all unread, subscribed groups with names that match a regexp
3001 (@code{gnus-group-list-matching}).
3005 @findex gnus-group-list-all-matching
3006 List groups that match a regexp (@code{gnus-group-list-all-matching}).
3010 @findex gnus-group-list-active
3011 List absolutely all groups in the active file(s) of the
3012 server(s) you are connected to (@code{gnus-group-list-active}). This
3013 might very well take quite a while. It might actually be a better idea
3014 to do a @kbd{A M} to list all matching, and just give @samp{.} as the
3015 thing to match on. Also note that this command may list groups that
3016 don't exist (yet)---these will be listed as if they were killed groups.
3017 Take the output with some grains of salt.
3021 @findex gnus-group-apropos
3022 List all groups that have names that match a regexp
3023 (@code{gnus-group-apropos}).
3027 @findex gnus-group-description-apropos
3028 List all groups that have names or descriptions that match a regexp
3029 (@code{gnus-group-description-apropos}).
3033 @findex gnus-group-list-cached
3034 List all groups with cached articles (@code{gnus-group-list-cached}).
3038 @findex gnus-group-list-dormant
3039 List all groups with dormant articles (@code{gnus-group-list-dormant}).
3043 @findex gnus-group-list-limit
3044 List groups limited within the current selection
3045 (@code{gnus-group-list-limit}).
3049 @findex gnus-group-list-flush
3050 Flush groups from the current selection (@code{gnus-group-list-flush}).
3054 @findex gnus-group-list-plus
3055 List groups plus the current selection (@code{gnus-group-list-plus}).
3059 @vindex gnus-permanently-visible-groups
3060 @cindex visible group parameter
3061 Groups that match the @code{gnus-permanently-visible-groups} regexp will
3062 always be shown, whether they have unread articles or not. You can also
3063 add the @code{visible} element to the group parameters in question to
3064 get the same effect.
3066 @vindex gnus-list-groups-with-ticked-articles
3067 Groups that have just ticked articles in it are normally listed in the
3068 group buffer. If @code{gnus-list-groups-with-ticked-articles} is
3069 @code{nil}, these groups will be treated just like totally empty
3070 groups. It is @code{t} by default.
3073 @node Sorting Groups
3074 @section Sorting Groups
3075 @cindex sorting groups
3077 @kindex C-c C-s (Group)
3078 @findex gnus-group-sort-groups
3079 @vindex gnus-group-sort-function
3080 The @kbd{C-c C-s} (@code{gnus-group-sort-groups}) command sorts the
3081 group buffer according to the function(s) given by the
3082 @code{gnus-group-sort-function} variable. Available sorting functions
3087 @item gnus-group-sort-by-alphabet
3088 @findex gnus-group-sort-by-alphabet
3089 Sort the group names alphabetically. This is the default.
3091 @item gnus-group-sort-by-real-name
3092 @findex gnus-group-sort-by-real-name
3093 Sort the group alphabetically on the real (unprefixed) group names.
3095 @item gnus-group-sort-by-level
3096 @findex gnus-group-sort-by-level
3097 Sort by group level.
3099 @item gnus-group-sort-by-score
3100 @findex gnus-group-sort-by-score
3101 Sort by group score. @xref{Group Score}.
3103 @item gnus-group-sort-by-rank
3104 @findex gnus-group-sort-by-rank
3105 Sort by group score and then the group level. The level and the score
3106 are, when taken together, the group's @dfn{rank}. @xref{Group Score}.
3108 @item gnus-group-sort-by-unread
3109 @findex gnus-group-sort-by-unread
3110 Sort by number of unread articles.
3112 @item gnus-group-sort-by-method
3113 @findex gnus-group-sort-by-method
3114 Sort alphabetically on the select method.
3116 @item gnus-group-sort-by-server
3117 @findex gnus-group-sort-by-server
3118 Sort alphabetically on the Gnus server name.
3123 @code{gnus-group-sort-function} can also be a list of sorting
3124 functions. In that case, the most significant sort key function must be
3128 There are also a number of commands for sorting directly according to
3129 some sorting criteria:
3133 @kindex G S a (Group)
3134 @findex gnus-group-sort-groups-by-alphabet
3135 Sort the group buffer alphabetically by group name
3136 (@code{gnus-group-sort-groups-by-alphabet}).
3139 @kindex G S u (Group)
3140 @findex gnus-group-sort-groups-by-unread
3141 Sort the group buffer by the number of unread articles
3142 (@code{gnus-group-sort-groups-by-unread}).
3145 @kindex G S l (Group)
3146 @findex gnus-group-sort-groups-by-level
3147 Sort the group buffer by group level
3148 (@code{gnus-group-sort-groups-by-level}).
3151 @kindex G S v (Group)
3152 @findex gnus-group-sort-groups-by-score
3153 Sort the group buffer by group score
3154 (@code{gnus-group-sort-groups-by-score}). @xref{Group Score}.
3157 @kindex G S r (Group)
3158 @findex gnus-group-sort-groups-by-rank
3159 Sort the group buffer by group rank
3160 (@code{gnus-group-sort-groups-by-rank}). @xref{Group Score}.
3163 @kindex G S m (Group)
3164 @findex gnus-group-sort-groups-by-method
3165 Sort the group buffer alphabetically by back end name
3166 (@code{gnus-group-sort-groups-by-method}).
3170 All the commands below obey the process/prefix convention
3171 (@pxref{Process/Prefix}).
3173 When given a symbolic prefix (@pxref{Symbolic Prefixes}), all these
3174 commands will sort in reverse order.
3176 You can also sort a subset of the groups:
3180 @kindex G P a (Group)
3181 @findex gnus-group-sort-selected-groups-by-alphabet
3182 Sort the groups alphabetically by group name
3183 (@code{gnus-group-sort-selected-groups-by-alphabet}).
3186 @kindex G P u (Group)
3187 @findex gnus-group-sort-selected-groups-by-unread
3188 Sort the groups by the number of unread articles
3189 (@code{gnus-group-sort-selected-groups-by-unread}).
3192 @kindex G P l (Group)
3193 @findex gnus-group-sort-selected-groups-by-level
3194 Sort the groups by group level
3195 (@code{gnus-group-sort-selected-groups-by-level}).
3198 @kindex G P v (Group)
3199 @findex gnus-group-sort-selected-groups-by-score
3200 Sort the groups by group score
3201 (@code{gnus-group-sort-selected-groups-by-score}). @xref{Group Score}.
3204 @kindex G P r (Group)
3205 @findex gnus-group-sort-selected-groups-by-rank
3206 Sort the groups by group rank
3207 (@code{gnus-group-sort-selected-groups-by-rank}). @xref{Group Score}.
3210 @kindex G P m (Group)
3211 @findex gnus-group-sort-selected-groups-by-method
3212 Sort the groups alphabetically by back end name
3213 (@code{gnus-group-sort-selected-groups-by-method}).
3217 And finally, note that you can use @kbd{C-k} and @kbd{C-y} to manually
3221 @node Group Maintenance
3222 @section Group Maintenance
3223 @cindex bogus groups
3228 @findex gnus-group-check-bogus-groups
3229 Find bogus groups and delete them
3230 (@code{gnus-group-check-bogus-groups}).
3234 @findex gnus-group-find-new-groups
3235 Find new groups and process them (@code{gnus-group-find-new-groups}).
3236 With 1 @kbd{C-u}, use the @code{ask-server} method to query the server
3237 for new groups. With 2 @kbd{C-u}'s, use most complete method possible
3238 to query the server for new groups, and subscribe the new groups as
3242 @kindex C-c C-x (Group)
3243 @findex gnus-group-expire-articles
3244 Run all expirable articles in the current group through the expiry
3245 process (if any) (@code{gnus-group-expire-articles}). That is, delete
3246 all expirable articles in the group that have been around for a while.
3247 (@pxref{Expiring Mail}).
3250 @kindex C-c C-M-x (Group)
3251 @findex gnus-group-expire-all-groups
3252 Run all expirable articles in all groups through the expiry process
3253 (@code{gnus-group-expire-all-groups}).
3258 @node Browse Foreign Server
3259 @section Browse Foreign Server
3260 @cindex foreign servers
3261 @cindex browsing servers
3266 @findex gnus-group-browse-foreign-server
3267 You will be queried for a select method and a server name. Gnus will
3268 then attempt to contact this server and let you browse the groups there
3269 (@code{gnus-group-browse-foreign-server}).
3272 @findex gnus-browse-mode
3273 A new buffer with a list of available groups will appear. This buffer
3274 will use the @code{gnus-browse-mode}. This buffer looks a bit (well,
3275 a lot) like a normal group buffer.
3277 Here's a list of keystrokes available in the browse mode:
3282 @findex gnus-group-next-group
3283 Go to the next group (@code{gnus-group-next-group}).
3287 @findex gnus-group-prev-group
3288 Go to the previous group (@code{gnus-group-prev-group}).
3291 @kindex SPACE (Browse)
3292 @findex gnus-browse-read-group
3293 Enter the current group and display the first article
3294 (@code{gnus-browse-read-group}).
3297 @kindex RET (Browse)
3298 @findex gnus-browse-select-group
3299 Enter the current group (@code{gnus-browse-select-group}).
3303 @findex gnus-browse-unsubscribe-current-group
3304 Unsubscribe to the current group, or, as will be the case here,
3305 subscribe to it (@code{gnus-browse-unsubscribe-current-group}).
3311 @findex gnus-browse-exit
3312 Exit browse mode (@code{gnus-browse-exit}).
3316 @findex gnus-browse-describe-briefly
3317 Describe browse mode briefly (well, there's not much to describe, is
3318 there) (@code{gnus-browse-describe-briefly}).
3323 @section Exiting Gnus
3324 @cindex exiting Gnus
3326 Yes, Gnus is ex(c)iting.
3331 @findex gnus-group-suspend
3332 Suspend Gnus (@code{gnus-group-suspend}). This doesn't really exit Gnus,
3333 but it kills all buffers except the Group buffer. I'm not sure why this
3334 is a gain, but then who am I to judge?
3338 @findex gnus-group-exit
3339 @c @icon{gnus-group-exit}
3340 Quit Gnus (@code{gnus-group-exit}).
3344 @findex gnus-group-quit
3345 Quit Gnus without saving the @file{.newsrc} files (@code{gnus-group-quit}).
3346 The dribble file will be saved, though (@pxref{Auto Save}).
3349 @vindex gnus-exit-gnus-hook
3350 @vindex gnus-suspend-gnus-hook
3351 @code{gnus-suspend-gnus-hook} is called when you suspend Gnus and
3352 @code{gnus-exit-gnus-hook} is called when you quit Gnus, while
3353 @code{gnus-after-exiting-gnus-hook} is called as the final item when
3358 If you wish to completely unload Gnus and all its adherents, you can use
3359 the @code{gnus-unload} command. This command is also very handy when
3360 trying to customize meta-variables.
3365 Miss Lisa Cannifax, while sitting in English class, felt her feet go
3366 numbly heavy and herself fall into a hazy trance as the boy sitting
3367 behind her drew repeated lines with his pencil across the back of her
3373 @section Group Topics
3376 If you read lots and lots of groups, it might be convenient to group
3377 them hierarchically according to topics. You put your Emacs groups over
3378 here, your sex groups over there, and the rest (what, two groups or so?)
3379 you put in some misc section that you never bother with anyway. You can
3380 even group the Emacs sex groups as a sub-topic to either the Emacs
3381 groups or the sex groups---or both! Go wild!
3385 \gnusfigure{Group Topics}{400}{
3386 \put(75,50){\epsfig{figure=ps/group-topic,height=9cm}}
3397 2: alt.religion.emacs
3400 0: comp.talk.emacs.recovery
3402 8: comp.binaries.fractals
3403 13: comp.sources.unix
3406 @findex gnus-topic-mode
3408 To get this @emph{fab} functionality you simply turn on (ooh!) the
3409 @code{gnus-topic} minor mode---type @kbd{t} in the group buffer. (This
3410 is a toggling command.)
3412 Go ahead, just try it. I'll still be here when you get back. La de
3413 dum... Nice tune, that... la la la... What, you're back? Yes, and
3414 now press @kbd{l}. There. All your groups are now listed under
3415 @samp{misc}. Doesn't that make you feel all warm and fuzzy? Hot and
3418 If you want this permanently enabled, you should add that minor mode to
3419 the hook for the group mode. Put the following line in your
3420 @file{~/.gnus} file:
3423 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
3427 * Topic Commands:: Interactive E-Z commands.
3428 * Topic Variables:: How to customize the topics the Lisp Way.
3429 * Topic Sorting:: Sorting each topic individually.
3430 * Topic Topology:: A map of the world.
3431 * Topic Parameters:: Parameters that apply to all groups in a topic.
3435 @node Topic Commands
3436 @subsection Topic Commands
3437 @cindex topic commands
3439 When the topic minor mode is turned on, a new @kbd{T} submap will be
3440 available. In addition, a few of the standard keys change their
3441 definitions slightly.
3443 In general, the following kinds of operations are possible on topics.
3444 First of all, you want to create topics. Secondly, you want to put
3445 groups in topics and to move them around until you have an order you
3446 like. The third kind of operation is to show/hide parts of the whole
3447 shebang. You might want to hide a topic including its subtopics and
3448 groups, to get a better overview of the other groups.
3450 Here is a list of the basic keys that you might need to set up topics
3457 @findex gnus-topic-create-topic
3458 Prompt for a new topic name and create it
3459 (@code{gnus-topic-create-topic}).
3463 @kindex T TAB (Topic)
3465 @findex gnus-topic-indent
3466 ``Indent'' the current topic so that it becomes a sub-topic of the
3467 previous topic (@code{gnus-topic-indent}). If given a prefix,
3468 ``un-indent'' the topic instead.
3471 @kindex M-TAB (Topic)
3472 @findex gnus-topic-unindent
3473 ``Un-indent'' the current topic so that it becomes a sub-topic of the
3474 parent of its current parent (@code{gnus-topic-unindent}).
3478 The following two keys can be used to move groups and topics around.
3479 They work like the well-known cut and paste. @kbd{C-k} is like cut and
3480 @kbd{C-y} is like paste. Of course, this being Emacs, we use the terms
3481 kill and yank rather than cut and paste.
3487 @findex gnus-topic-kill-group
3488 Kill a group or topic (@code{gnus-topic-kill-group}). All groups in the
3489 topic will be removed along with the topic.
3493 @findex gnus-topic-yank-group
3494 Yank the previously killed group or topic
3495 (@code{gnus-topic-yank-group}). Note that all topics will be yanked
3498 So, to move a topic to the beginning of the list of topics, just hit
3499 @kbd{C-k} on it. This is like the `cut' part of cut and paste. Then,
3500 move the cursor to the beginning of the buffer (just below the `Gnus'
3501 topic) and hit @kbd{C-y}. This is like the `paste' part of cut and
3502 paste. Like I said -- E-Z.
3504 You can use @kbd{C-k} and @kbd{C-y} on groups as well as on topics. So
3505 you can move topics around as well as groups.
3509 After setting up the topics the way you like them, you might wish to
3510 hide a topic, or to show it again. That's why we have the following
3517 @findex gnus-topic-select-group
3519 Either select a group or fold a topic (@code{gnus-topic-select-group}).
3520 When you perform this command on a group, you'll enter the group, as
3521 usual. When done on a topic line, the topic will be folded (if it was
3522 visible) or unfolded (if it was folded already). So it's basically a
3523 toggling command on topics. In addition, if you give a numerical
3524 prefix, group on that level (and lower) will be displayed.
3528 Now for a list of other commands, in no particular order.
3534 @findex gnus-topic-move-group
3535 Move the current group to some other topic
3536 (@code{gnus-topic-move-group}). This command uses the process/prefix
3537 convention (@pxref{Process/Prefix}).
3541 @findex gnus-topic-jump-to-topic
3542 Go to a topic (@code{gnus-topic-jump-to-topic}).
3546 @findex gnus-topic-copy-group
3547 Copy the current group to some other topic
3548 (@code{gnus-topic-copy-group}). This command uses the process/prefix
3549 convention (@pxref{Process/Prefix}).
3553 @findex gnus-topic-hide-topic
3554 Hide the current topic (@code{gnus-topic-hide-topic}). If given
3555 a prefix, hide the topic permanently.
3559 @findex gnus-topic-show-topic
3560 Show the current topic (@code{gnus-topic-show-topic}). If given
3561 a prefix, show the topic permanently.
3565 @findex gnus-topic-remove-group
3566 Remove a group from the current topic (@code{gnus-topic-remove-group}).
3567 This command is mainly useful if you have the same group in several
3568 topics and wish to remove it from one of the topics. You may also
3569 remove a group from all topics, but in that case, Gnus will add it to
3570 the root topic the next time you start Gnus. In fact, all new groups
3571 (which, naturally, don't belong to any topic) will show up in the root
3574 This command uses the process/prefix convention
3575 (@pxref{Process/Prefix}).
3579 @findex gnus-topic-move-matching
3580 Move all groups that match some regular expression to a topic
3581 (@code{gnus-topic-move-matching}).
3585 @findex gnus-topic-copy-matching
3586 Copy all groups that match some regular expression to a topic
3587 (@code{gnus-topic-copy-matching}).
3591 @findex gnus-topic-toggle-display-empty-topics
3592 Toggle hiding empty topics
3593 (@code{gnus-topic-toggle-display-empty-topics}).
3597 @findex gnus-topic-mark-topic
3598 Mark all groups in the current topic with the process mark
3599 (@code{gnus-topic-mark-topic}).
3602 @kindex T M-# (Topic)
3603 @findex gnus-topic-unmark-topic
3604 Remove the process mark from all groups in the current topic
3605 (@code{gnus-topic-unmark-topic}).
3608 @kindex C-c C-x (Topic)
3609 @findex gnus-topic-expire-articles
3610 Run all expirable articles in the current group or topic through the
3611 expiry process (if any)
3612 (@code{gnus-topic-expire-articles}). (@pxref{Expiring Mail}).
3616 @findex gnus-topic-rename
3617 Rename a topic (@code{gnus-topic-rename}).
3620 @kindex T DEL (Topic)
3621 @findex gnus-topic-delete
3622 Delete an empty topic (@code{gnus-topic-delete}).
3626 @findex gnus-topic-list-active
3627 List all groups that Gnus knows about in a topics-ified way
3628 (@code{gnus-topic-list-active}).
3631 @kindex T M-n (Topic)
3632 @findex gnus-topic-goto-next-topic
3633 Go to the next topic (@code{gnus-topic-goto-next-topic}).
3636 @kindex T M-p (Topic)
3637 @findex gnus-topic-goto-previous-topic
3638 Go to the next topic (@code{gnus-topic-goto-previous-topic}).
3642 @findex gnus-topic-edit-parameters
3643 @cindex group parameters
3644 @cindex topic parameters
3646 Edit the topic parameters (@code{gnus-topic-edit-parameters}).
3647 @xref{Topic Parameters}.
3652 @node Topic Variables
3653 @subsection Topic Variables
3654 @cindex topic variables
3656 The previous section told you how to tell Gnus which topics to display.
3657 This section explains how to tell Gnus what to display about each topic.
3659 @vindex gnus-topic-line-format
3660 The topic lines themselves are created according to the
3661 @code{gnus-topic-line-format} variable (@pxref{Formatting Variables}).
3674 Number of groups in the topic.
3676 Number of unread articles in the topic.
3678 Number of unread articles in the topic and all its subtopics.
3681 @vindex gnus-topic-indent-level
3682 Each sub-topic (and the groups in the sub-topics) will be indented with
3683 @code{gnus-topic-indent-level} times the topic level number of spaces.
3686 @vindex gnus-topic-mode-hook
3687 @code{gnus-topic-mode-hook} is called in topic minor mode buffers.
3689 @vindex gnus-topic-display-empty-topics
3690 The @code{gnus-topic-display-empty-topics} says whether to display even
3691 topics that have no unread articles in them. The default is @code{t}.
3695 @subsection Topic Sorting
3696 @cindex topic sorting
3698 You can sort the groups in each topic individually with the following
3704 @kindex T S a (Topic)
3705 @findex gnus-topic-sort-groups-by-alphabet
3706 Sort the current topic alphabetically by group name
3707 (@code{gnus-topic-sort-groups-by-alphabet}).
3710 @kindex T S u (Topic)
3711 @findex gnus-topic-sort-groups-by-unread
3712 Sort the current topic by the number of unread articles
3713 (@code{gnus-topic-sort-groups-by-unread}).
3716 @kindex T S l (Topic)
3717 @findex gnus-topic-sort-groups-by-level
3718 Sort the current topic by group level
3719 (@code{gnus-topic-sort-groups-by-level}).
3722 @kindex T S v (Topic)
3723 @findex gnus-topic-sort-groups-by-score
3724 Sort the current topic by group score
3725 (@code{gnus-topic-sort-groups-by-score}). @xref{Group Score}.
3728 @kindex T S r (Topic)
3729 @findex gnus-topic-sort-groups-by-rank
3730 Sort the current topic by group rank
3731 (@code{gnus-topic-sort-groups-by-rank}). @xref{Group Score}.
3734 @kindex T S m (Topic)
3735 @findex gnus-topic-sort-groups-by-method
3736 Sort the current topic alphabetically by back end name
3737 (@code{gnus-topic-sort-groups-by-method}).
3740 @kindex T S e (Topic)
3741 @findex gnus-topic-sort-groups-by-server
3742 Sort the current topic alphabetically by server name
3743 (@code{gnus-topic-sort-groups-by-server}).
3747 @xref{Sorting Groups}, for more information about group sorting.
3750 @node Topic Topology
3751 @subsection Topic Topology
3752 @cindex topic topology
3755 So, let's have a look at an example group buffer:
3761 2: alt.religion.emacs
3764 0: comp.talk.emacs.recovery
3766 8: comp.binaries.fractals
3767 13: comp.sources.unix
3770 So, here we have one top-level topic (@samp{Gnus}), two topics under
3771 that, and one sub-topic under one of the sub-topics. (There is always
3772 just one (1) top-level topic). This topology can be expressed as
3777 (("Emacs -- I wuw it!" visible)
3778 (("Naughty Emacs" visible)))
3782 @vindex gnus-topic-topology
3783 This is in fact how the variable @code{gnus-topic-topology} would look
3784 for the display above. That variable is saved in the @file{.newsrc.eld}
3785 file, and shouldn't be messed with manually---unless you really want
3786 to. Since this variable is read from the @file{.newsrc.eld} file,
3787 setting it in any other startup files will have no effect.
3789 This topology shows what topics are sub-topics of what topics (right),
3790 and which topics are visible. Two settings are currently
3791 allowed---@code{visible} and @code{invisible}.
3794 @node Topic Parameters
3795 @subsection Topic Parameters
3796 @cindex topic parameters
3798 All groups in a topic will inherit group parameters from the parent (and
3799 ancestor) topic parameters. All valid group parameters are valid topic
3800 parameters (@pxref{Group Parameters}).
3802 In addition, the following parameters are only valid as topic
3807 When subscribing new groups by topic (@pxref{Subscription Methods}), the
3808 @code{subscribe} topic parameter says what groups go in what topic. Its
3809 value should be a regexp to match the groups that should go in that
3812 @item subscribe-level
3813 When subscribing new groups by topic (see the @code{subscribe} parameter),
3814 the group will be subscribed with the level specified in the
3815 @code{subscribe-level} instead of @code{gnus-level-default-subscribed}.
3819 Group parameters (of course) override topic parameters, and topic
3820 parameters in sub-topics override topic parameters in super-topics. You
3821 know. Normal inheritance rules. (@dfn{Rules} is here a noun, not a
3822 verb, although you may feel free to disagree with me here.)
3828 2: alt.religion.emacs
3832 0: comp.talk.emacs.recovery
3834 8: comp.binaries.fractals
3835 13: comp.sources.unix
3839 The @samp{Emacs} topic has the topic parameter @code{(score-file
3840 . "emacs.SCORE")}; the @samp{Relief} topic has the topic parameter
3841 @code{(score-file . "relief.SCORE")}; and the @samp{Misc} topic has the
3842 topic parameter @code{(score-file . "emacs.SCORE")}. In addition,
3843 @* @samp{alt.religion.emacs} has the group parameter @code{(score-file
3844 . "religion.SCORE")}.
3846 Now, when you enter @samp{alt.sex.emacs} in the @samp{Relief} topic, you
3847 will get the @file{relief.SCORE} home score file. If you enter the same
3848 group in the @samp{Emacs} topic, you'll get the @file{emacs.SCORE} home
3849 score file. If you enter the group @samp{alt.religion.emacs}, you'll
3850 get the @file{religion.SCORE} home score file.
3852 This seems rather simple and self-evident, doesn't it? Well, yes. But
3853 there are some problems, especially with the @code{total-expiry}
3854 parameter. Say you have a mail group in two topics; one with
3855 @code{total-expiry} and one without. What happens when you do @kbd{M-x
3856 gnus-expire-all-expirable-groups}? Gnus has no way of telling which one
3857 of these topics you mean to expire articles from, so anything may
3858 happen. In fact, I hereby declare that it is @dfn{undefined} what
3859 happens. You just have to be careful if you do stuff like that.
3862 @node Misc Group Stuff
3863 @section Misc Group Stuff
3866 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
3867 * Group Information:: Information and help on groups and Gnus.
3868 * Group Timestamp:: Making Gnus keep track of when you last read a group.
3869 * File Commands:: Reading and writing the Gnus files.
3870 * Sieve Commands:: Managing Sieve scripts.
3877 @findex gnus-group-enter-server-mode
3878 Enter the server buffer (@code{gnus-group-enter-server-mode}).
3879 @xref{Server Buffer}.
3883 @findex gnus-group-post-news
3884 Start composing a message (a news by default)
3885 (@code{gnus-group-post-news}). If given a prefix, post to the group
3886 under the point. If the prefix is 1, prompt for a group to post to.
3887 Contrary to what the name of this function suggests, the prepared
3888 article might be a mail instead of a news, if a mail group is specified
3889 with the prefix argument. @xref{Composing Messages}.
3893 @findex gnus-group-mail
3894 Mail a message somewhere (@code{gnus-group-mail}). If given a prefix,
3895 use the posting style of the group under the point. If the prefix is 1,
3896 prompt for a group name to find the posting style.
3897 @xref{Composing Messages}.
3901 @findex gnus-group-news
3902 Start composing a news (@code{gnus-group-news}). If given a prefix,
3903 post to the group under the point. If the prefix is 1, prompt
3904 for group to post to. @xref{Composing Messages}.
3906 This function actually prepares a news even when using mail groups.
3907 This is useful for "posting" messages to mail groups without actually
3908 sending them over the network: they're just saved directly to the group
3909 in question. The corresponding back end must have a request-post method
3910 for this to work though.
3914 Variables for the group buffer:
3918 @item gnus-group-mode-hook
3919 @vindex gnus-group-mode-hook
3920 is called after the group buffer has been
3923 @item gnus-group-prepare-hook
3924 @vindex gnus-group-prepare-hook
3925 is called after the group buffer is
3926 generated. It may be used to modify the buffer in some strange,
3929 @item gnus-group-prepared-hook
3930 @vindex gnus-group-prepare-hook
3931 is called as the very last thing after the group buffer has been
3932 generated. It may be used to move point around, for instance.
3934 @item gnus-permanently-visible-groups
3935 @vindex gnus-permanently-visible-groups
3936 Groups matching this regexp will always be listed in the group buffer,
3937 whether they are empty or not.
3939 @item gnus-group-name-charset-method-alist
3940 @vindex gnus-group-name-charset-method-alist
3941 An alist of method and the charset for group names. It is used to show
3942 non-ASCII group names.
3946 (setq gnus-group-name-charset-method-alist
3947 '(((nntp "news.com.cn") . cn-gb-2312)))
3950 @item gnus-group-name-charset-group-alist
3951 @cindex UTF-8 group names
3952 @vindex gnus-group-name-charset-group-alist
3953 An alist of regexp of group name and the charset for group names. It
3954 is used to show non-ASCII group names. @code{((".*" utf-8))} is the
3955 default value if UTF-8 is supported, otherwise the default is nil.
3959 (setq gnus-group-name-charset-group-alist
3960 '(("\\.com\\.cn:" . cn-gb-2312)))
3965 @node Scanning New Messages
3966 @subsection Scanning New Messages
3967 @cindex new messages
3968 @cindex scanning new news
3974 @findex gnus-group-get-new-news
3975 @c @icon{gnus-group-get-new-news}
3976 Check the server(s) for new articles. If the numerical prefix is used,
3977 this command will check only groups of level @var{arg} and lower
3978 (@code{gnus-group-get-new-news}). If given a non-numerical prefix, this
3979 command will force a total re-reading of the active file(s) from the
3984 @findex gnus-group-get-new-news-this-group
3985 @vindex gnus-goto-next-group-when-activating
3986 @c @icon{gnus-group-get-new-news-this-group}
3987 Check whether new articles have arrived in the current group
3988 (@code{gnus-group-get-new-news-this-group}).
3989 @code{gnus-goto-next-group-when-activating} says whether this command is
3990 to move point to the next group or not. It is @code{t} by default.
3992 @findex gnus-activate-all-groups
3993 @cindex activating groups
3995 @kindex C-c M-g (Group)
3996 Activate absolutely all groups (@code{gnus-activate-all-groups}).
4001 @findex gnus-group-restart
4002 Restart Gnus (@code{gnus-group-restart}). This saves the @file{.newsrc}
4003 file(s), closes the connection to all servers, clears up all run-time
4004 Gnus variables, and then starts Gnus all over again.
4008 @vindex gnus-get-new-news-hook
4009 @code{gnus-get-new-news-hook} is run just before checking for new news.
4011 @vindex gnus-after-getting-new-news-hook
4012 @code{gnus-after-getting-new-news-hook} is run after checking for new
4016 @node Group Information
4017 @subsection Group Information
4018 @cindex group information
4019 @cindex information on groups
4026 @findex gnus-group-fetch-faq
4027 @vindex gnus-group-faq-directory
4030 Try to fetch the FAQ for the current group
4031 (@code{gnus-group-fetch-faq}). Gnus will try to get the FAQ from
4032 @code{gnus-group-faq-directory}, which is usually a directory on a
4033 remote machine. This variable can also be a list of directories. In
4034 that case, giving a prefix to this command will allow you to choose
4035 between the various sites. @code{ange-ftp} (or @code{efs}) will be used
4036 for fetching the file.
4038 If fetching from the first site is unsuccessful, Gnus will attempt to go
4039 through @code{gnus-group-faq-directory} and try to open them one by one.
4043 @c @icon{gnus-group-describe-group}
4045 @kindex C-c C-d (Group)
4046 @cindex describing groups
4047 @cindex group description
4048 @findex gnus-group-describe-group
4049 Describe the current group (@code{gnus-group-describe-group}). If given
4050 a prefix, force Gnus to re-read the description from the server.
4054 @findex gnus-group-describe-all-groups
4055 Describe all groups (@code{gnus-group-describe-all-groups}). If given a
4056 prefix, force Gnus to re-read the description file from the server.
4063 @findex gnus-version
4064 Display current Gnus version numbers (@code{gnus-version}).
4068 @findex gnus-group-describe-briefly
4069 Give a very short help message (@code{gnus-group-describe-briefly}).
4072 @kindex C-c C-i (Group)
4075 @findex gnus-info-find-node
4076 Go to the Gnus info node (@code{gnus-info-find-node}).
4080 @node Group Timestamp
4081 @subsection Group Timestamp
4083 @cindex group timestamps
4085 It can be convenient to let Gnus keep track of when you last read a
4086 group. To set the ball rolling, you should add
4087 @code{gnus-group-set-timestamp} to @code{gnus-select-group-hook}:
4090 (add-hook 'gnus-select-group-hook 'gnus-group-set-timestamp)
4093 After doing this, each time you enter a group, it'll be recorded.
4095 This information can be displayed in various ways---the easiest is to
4096 use the @samp{%d} spec in the group line format:
4099 (setq gnus-group-line-format
4100 "%M\%S\%p\%P\%5y: %(%-40,40g%) %d\n")
4103 This will result in lines looking like:
4106 * 0: mail.ding 19961002T012943
4107 0: custom 19961002T012713
4110 As you can see, the date is displayed in compact ISO 8601 format. This
4111 may be a bit too much, so to just display the date, you could say
4115 (setq gnus-group-line-format
4116 "%M\%S\%p\%P\%5y: %(%-40,40g%) %6,6~(cut 2)d\n")
4119 If you would like greater control of the time format, you can use a
4120 user-defined format spec. Something like the following should do the
4124 (setq gnus-group-line-format
4125 "%M\%S\%p\%P\%5y: %(%-40,40g%) %ud\n")
4126 (defun gnus-user-format-function-d (headers)
4127 (let ((time (gnus-group-timestamp gnus-tmp-group)))
4129 (format-time-string "%b %d %H:%M" time)
4135 @subsection File Commands
4136 @cindex file commands
4142 @findex gnus-group-read-init-file
4143 @vindex gnus-init-file
4144 @cindex reading init file
4145 Re-read the init file (@code{gnus-init-file}, which defaults to
4146 @file{~/.gnus}) (@code{gnus-group-read-init-file}).
4150 @findex gnus-group-save-newsrc
4151 @cindex saving .newsrc
4152 Save the @file{.newsrc.eld} file (and @file{.newsrc} if wanted)
4153 (@code{gnus-group-save-newsrc}). If given a prefix, force saving the
4154 file(s) whether Gnus thinks it is necessary or not.
4157 @c @kindex Z (Group)
4158 @c @findex gnus-group-clear-dribble
4159 @c Clear the dribble buffer (@code{gnus-group-clear-dribble}).
4164 @node Sieve Commands
4165 @subsection Sieve Commands
4166 @cindex group sieve commands
4168 Sieve is a server-side mail filtering language. In Gnus you can use
4169 the @code{sieve} group parameter (@pxref{Group Parameters}) to specify
4170 sieve rules that should apply to each group. Gnus provides two
4171 commands to translate all these group parameters into a proper Sieve
4172 script that can be transfered to the server somehow.
4174 @vindex gnus-sieve-file
4175 @vindex gnus-sieve-region-start
4176 @vindex gnus-sieve-region-end
4177 The generated Sieve script is placed in @code{gnus-sieve-file} (by
4178 default @file{~/.sieve}). The Sieve code that Gnus generate is placed
4179 between two delimiters, @code{gnus-sieve-region-start} and
4180 @code{gnus-sieve-region-end}, so you may write additional Sieve code
4181 outside these delimiters that will not be removed the next time you
4182 regenerate the Sieve script.
4184 @vindex gnus-sieve-crosspost
4185 The variable @code{gnus-sieve-crosspost} controls how the Sieve script
4186 is generated. If it is non-nil (the default) articles is placed in
4187 all groups that have matching rules, otherwise the article is only
4188 placed in the group with the first matching rule. For example, the
4189 group parameter @samp{(sieve address "sender"
4190 "owner-ding@@hpc.uh.edu")} will generate the following piece of Sieve
4191 code if @code{gnus-sieve-crosspost} is nil. (When
4192 @code{gnus-sieve-crosspost} is non-nil, it looks the same except that
4193 the line containing the call to @code{stop} is removed.)
4196 if address "sender" "owner-ding@@hpc.uh.edu" @{
4197 fileinto "INBOX.ding";
4202 @xref{Top, ,Top, sieve, Emacs Sieve}.
4208 @findex gnus-sieve-generate
4209 @vindex gnus-sieve-file
4210 @cindex generating sieve script
4211 Regenerate a Sieve script from the @code{sieve} group parameters and
4212 put you into the @code{gnus-sieve-file} without saving it.
4216 @findex gnus-sieve-update
4217 @vindex gnus-sieve-file
4218 @cindex updating sieve script
4219 Regenerates the Gnus managed part of @code{gnus-sieve-file} using the
4220 @code{sieve} group parameters, save the file and upload it to the
4221 server using the @code{sieveshell} program.
4226 @node Summary Buffer
4227 @chapter Summary Buffer
4228 @cindex summary buffer
4230 A line for each article is displayed in the summary buffer. You can
4231 move around, read articles, post articles and reply to articles.
4233 The most common way to a summary buffer is to select a group from the
4234 group buffer (@pxref{Selecting a Group}).
4236 You can have as many summary buffers open as you wish.
4239 * Summary Buffer Format:: Deciding how the summary buffer is to look.
4240 * Summary Maneuvering:: Moving around the summary buffer.
4241 * Choosing Articles:: Reading articles.
4242 * Paging the Article:: Scrolling the current article.
4243 * Reply Followup and Post:: Posting articles.
4244 * Delayed Articles::
4245 * Marking Articles:: Marking articles as read, expirable, etc.
4246 * Limiting:: You can limit the summary buffer.
4247 * Threading:: How threads are made.
4248 * Sorting the Summary Buffer:: How articles and threads are sorted.
4249 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
4250 * Article Caching:: You may store articles in a cache.
4251 * Persistent Articles:: Making articles expiry-resistant.
4252 * Article Backlog:: Having already read articles hang around.
4253 * Saving Articles:: Ways of customizing article saving.
4254 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
4255 * Article Treatment:: The article buffer can be mangled at will.
4256 * MIME Commands:: Doing MIMEy things with the articles.
4257 * Charsets:: Character set issues.
4258 * Article Commands:: Doing various things with the article buffer.
4259 * Summary Sorting:: Sorting the summary buffer in various ways.
4260 * Finding the Parent:: No child support? Get the parent.
4261 * Alternative Approaches:: Reading using non-default summaries.
4262 * Tree Display:: A more visual display of threads.
4263 * Mail Group Commands:: Some commands can only be used in mail groups.
4264 * Various Summary Stuff:: What didn't fit anywhere else.
4265 * Exiting the Summary Buffer:: Returning to the Group buffer,
4266 or reselecting the current group.
4267 * Crosspost Handling:: How crossposted articles are dealt with.
4268 * Duplicate Suppression:: An alternative when crosspost handling fails.
4269 * Security:: Decrypt and Verify.
4270 * Mailing List:: Mailing list minor mode.
4274 @node Summary Buffer Format
4275 @section Summary Buffer Format
4276 @cindex summary buffer format
4280 \gnusfigure{The Summary Buffer}{180}{
4281 \put(0,0){\epsfig{figure=ps/summary,width=7.5cm}}
4282 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-article,width=7.5cm}}}
4288 * Summary Buffer Lines:: You can specify how summary lines should look.
4289 * To From Newsgroups:: How to not display your own name.
4290 * Summary Buffer Mode Line:: You can say how the mode line should look.
4291 * Summary Highlighting:: Making the summary buffer all pretty and nice.
4294 @findex mail-extract-address-components
4295 @findex gnus-extract-address-components
4296 @vindex gnus-extract-address-components
4297 Gnus will use the value of the @code{gnus-extract-address-components}
4298 variable as a function for getting the name and address parts of a
4299 @code{From} header. Two pre-defined functions exist:
4300 @code{gnus-extract-address-components}, which is the default, quite
4301 fast, and too simplistic solution; and
4302 @code{mail-extract-address-components}, which works very nicely, but is
4303 slower. The default function will return the wrong answer in 5% of the
4304 cases. If this is unacceptable to you, use the other function instead:
4307 (setq gnus-extract-address-components
4308 'mail-extract-address-components)
4311 @vindex gnus-summary-same-subject
4312 @code{gnus-summary-same-subject} is a string indicating that the current
4313 article has the same subject as the previous. This string will be used
4314 with those specs that require it. The default is @code{""}.
4317 @node Summary Buffer Lines
4318 @subsection Summary Buffer Lines
4320 @vindex gnus-summary-line-format
4321 You can change the format of the lines in the summary buffer by changing
4322 the @code{gnus-summary-line-format} variable. It works along the same
4323 lines as a normal @code{format} string, with some extensions
4324 (@pxref{Formatting Variables}).
4326 There should always be a colon or a point position marker on the line;
4327 the cursor always moves to the point position marker or the colon after
4328 performing an operation. (Of course, Gnus wouldn't be Gnus if it wasn't
4329 possible to change this. Just write a new function
4330 @code{gnus-goto-colon} which does whatever you like with the cursor.)
4331 @xref{Positioning Point}.
4333 The default string is @samp{%U%R%z%I%(%[%4L: %-23,23n%]%) %s\n}.
4335 The following format specification characters and extended format
4336 specification(s) are understood:
4342 Subject string. List identifiers stripped,
4343 @code{gnus-list-identifies}. @xref{Article Hiding}.
4345 Subject if the article is the root of the thread or the previous article
4346 had a different subject, @code{gnus-summary-same-subject} otherwise.
4347 (@code{gnus-summary-same-subject} defaults to @code{""}.)
4349 Full @code{From} header.
4351 The name (from the @code{From} header).
4353 The name, code @code{To} header or the @code{Newsgroups} header
4354 (@pxref{To From Newsgroups}).
4356 The name (from the @code{From} header). This differs from the @code{n}
4357 spec in that it uses the function designated by the
4358 @code{gnus-extract-address-components} variable, which is slower, but
4359 may be more thorough.
4361 The address (from the @code{From} header). This works the same way as
4364 Number of lines in the article.
4366 Number of characters in the article. This specifier is not supported
4367 in some methods (like nnfolder).
4369 Indentation based on thread level (@pxref{Customizing Threading}).
4371 A complex trn-style thread tree, showing response-connecting trace
4374 Nothing if the article is a root and lots of spaces if it isn't (it
4375 pushes everything after it off the screen).
4377 Opening bracket, which is normally @samp{[}, but can also be @samp{<}
4378 for adopted articles (@pxref{Customizing Threading}).
4380 Closing bracket, which is normally @samp{]}, but can also be @samp{>}
4381 for adopted articles.
4383 One space for each thread level.
4385 Twenty minus thread level spaces.
4387 Unread. @xref{Read Articles}.
4390 This misleadingly named specifier is the @dfn{secondary mark}. This
4391 mark will say whether the article has been replied to, has been cached,
4392 or has been saved. @xref{Other Marks}.
4395 Score as a number (@pxref{Scoring}).
4397 @vindex gnus-summary-zcore-fuzz
4398 Zcore, @samp{+} if above the default level and @samp{-} if below the
4399 default level. If the difference between
4400 @code{gnus-summary-default-score} and the score is less than
4401 @code{gnus-summary-zcore-fuzz}, this spec will not be used.
4409 The @code{Date} in @code{DD-MMM} format.
4411 The @code{Date} in @var{YYYYMMDD}@code{T}@var{HHMMSS} format.
4417 Number of articles in the current sub-thread. Using this spec will slow
4418 down summary buffer generation somewhat.
4420 An @samp{=} (@code{gnus-not-empty-thread-mark}) will be displayed if the
4421 article has any children.
4427 Age sensitive date format. Various date format is defined in
4428 @code{gnus-user-date-format-alist}.
4430 User defined specifier. The next character in the format string should
4431 be a letter. Gnus will call the function
4432 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
4433 following @samp{%u}. The function will be passed the current header as
4434 argument. The function should return a string, which will be inserted
4435 into the summary just like information from any other summary specifier.
4438 Text between @samp{%(} and @samp{%)} will be highlighted with
4439 @code{gnus-mouse-face} when the mouse point is placed inside the area.
4440 There can only be one such area.
4442 The @samp{%U} (status), @samp{%R} (replied) and @samp{%z} (zcore) specs
4443 have to be handled with care. For reasons of efficiency, Gnus will
4444 compute what column these characters will end up in, and ``hard-code''
4445 that. This means that it is invalid to have these specs after a
4446 variable-length spec. Well, you might not be arrested, but your summary
4447 buffer will look strange, which is bad enough.
4449 The smart choice is to have these specs as far to the left as possible.
4450 (Isn't that the case with everything, though? But I digress.)
4452 This restriction may disappear in later versions of Gnus.
4455 @node To From Newsgroups
4456 @subsection To From Newsgroups
4460 In some groups (particularly in archive groups), the @code{From} header
4461 isn't very interesting, since all the articles there are written by
4462 you. To display the information in the @code{To} or @code{Newsgroups}
4463 headers instead, you need to decide three things: What information to
4464 gather; where to display it; and when to display it.
4468 @vindex gnus-extra-headers
4469 The reading of extra header information is controlled by the
4470 @code{gnus-extra-headers}. This is a list of header symbols. For
4474 (setq gnus-extra-headers
4475 '(To Newsgroups X-Newsreader))
4478 This will result in Gnus trying to obtain these three headers, and
4479 storing it in header structures for later easy retrieval.
4482 @findex gnus-extra-header
4483 The value of these extra headers can be accessed via the
4484 @code{gnus-extra-header} function. Here's a format line spec that will
4485 access the @code{X-Newsreader} header:
4488 "%~(form (gnus-extra-header 'X-Newsreader))@@"
4492 @vindex gnus-ignored-from-addresses
4493 The @code{gnus-ignored-from-addresses} variable says when the @samp{%f}
4494 summary line spec returns the @code{To}, @code{Newsreader} or
4495 @code{From} header. If this regexp matches the contents of the
4496 @code{From} header, the value of the @code{To} or @code{Newsreader}
4497 headers are used instead.
4501 @vindex nnmail-extra-headers
4502 A related variable is @code{nnmail-extra-headers}, which controls when
4503 to include extra headers when generating overview (@sc{nov}) files. If
4504 you have old overview files, you should regenerate them after changing
4507 @vindex gnus-summary-line-format
4508 You also have to instruct Gnus to display the data by changing the
4509 @code{%n} spec to the @code{%f} spec in the
4510 @code{gnus-summary-line-format} variable.
4512 In summary, you'd typically put something like the following in
4516 (setq gnus-extra-headers
4518 (setq nnmail-extra-headers gnus-extra-headers)
4519 (setq gnus-summary-line-format
4520 "%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n")
4521 (setq gnus-ignored-from-addresses
4525 (The values listed above are the default values in Gnus. Alter them
4528 Now, this is mostly useful for mail groups, where you have control over
4529 the @sc{nov} files that are created. However, if you can persuade your
4536 to the end of her @file{overview.fmt} file, then you can use that just
4537 as you would the extra headers from the mail groups.
4540 @node Summary Buffer Mode Line
4541 @subsection Summary Buffer Mode Line
4543 @vindex gnus-summary-mode-line-format
4544 You can also change the format of the summary mode bar (@pxref{Mode Line
4545 Formatting}). Set @code{gnus-summary-mode-line-format} to whatever you
4546 like. The default is @samp{Gnus: %%b [%A] %Z}.
4548 Here are the elements you can play with:
4554 Unprefixed group name.
4556 Current article number.
4558 Current article score.
4562 Number of unread articles in this group.
4564 Number of unread articles in this group that aren't displayed in the
4567 A string with the number of unread and unselected articles represented
4568 either as @samp{<%U(+%e) more>} if there are both unread and unselected
4569 articles, and just as @samp{<%U more>} if there are just unread articles
4570 and no unselected ones.
4572 Shortish group name. For instance, @samp{rec.arts.anime} will be
4573 shortened to @samp{r.a.anime}.
4575 Subject of the current article.
4577 User-defined spec (@pxref{User-Defined Specs}).
4579 Name of the current score file (@pxref{Scoring}).
4581 Number of dormant articles (@pxref{Unread Articles}).
4583 Number of ticked articles (@pxref{Unread Articles}).
4585 Number of articles that have been marked as read in this session.
4587 Number of articles expunged by the score files.
4591 @node Summary Highlighting
4592 @subsection Summary Highlighting
4596 @item gnus-visual-mark-article-hook
4597 @vindex gnus-visual-mark-article-hook
4598 This hook is run after selecting an article. It is meant to be used for
4599 highlighting the article in some way. It is not run if
4600 @code{gnus-visual} is @code{nil}.
4602 @item gnus-summary-update-hook
4603 @vindex gnus-summary-update-hook
4604 This hook is called when a summary line is changed. It is not run if
4605 @code{gnus-visual} is @code{nil}.
4607 @item gnus-summary-selected-face
4608 @vindex gnus-summary-selected-face
4609 This is the face (or @dfn{font} as some people call it) used to
4610 highlight the current article in the summary buffer.
4612 @item gnus-summary-highlight
4613 @vindex gnus-summary-highlight
4614 Summary lines are highlighted according to this variable, which is a
4615 list where the elements are of the format @code{(@var{form}
4616 . @var{face})}. If you would, for instance, like ticked articles to be
4617 italic and high-scored articles to be bold, you could set this variable
4620 (((eq mark gnus-ticked-mark) . italic)
4621 ((> score default) . bold))
4623 As you may have guessed, if @var{form} returns a non-@code{nil} value,
4624 @var{face} will be applied to the line.
4628 @node Summary Maneuvering
4629 @section Summary Maneuvering
4630 @cindex summary movement
4632 All the straight movement commands understand the numeric prefix and
4633 behave pretty much as you'd expect.
4635 None of these commands select articles.
4640 @kindex M-n (Summary)
4641 @kindex G M-n (Summary)
4642 @findex gnus-summary-next-unread-subject
4643 Go to the next summary line of an unread article
4644 (@code{gnus-summary-next-unread-subject}).
4648 @kindex M-p (Summary)
4649 @kindex G M-p (Summary)
4650 @findex gnus-summary-prev-unread-subject
4651 Go to the previous summary line of an unread article
4652 (@code{gnus-summary-prev-unread-subject}).
4655 @kindex G g (Summary)
4656 @findex gnus-summary-goto-subject
4657 Ask for an article number and then go to the summary line of that article
4658 without displaying the article (@code{gnus-summary-goto-subject}).
4661 If Gnus asks you to press a key to confirm going to the next group, you
4662 can use the @kbd{C-n} and @kbd{C-p} keys to move around the group
4663 buffer, searching for the next group to read without actually returning
4664 to the group buffer.
4666 Variables related to summary movement:
4670 @vindex gnus-auto-select-next
4671 @item gnus-auto-select-next
4672 If you issue one of the movement commands (like @kbd{n}) and there are
4673 no more unread articles after the current one, Gnus will offer to go to
4674 the next group. If this variable is @code{t} and the next group is
4675 empty, Gnus will exit summary mode and return to the group buffer. If
4676 this variable is neither @code{t} nor @code{nil}, Gnus will select the
4677 next group, no matter whether it has any unread articles or not. As a
4678 special case, if this variable is @code{quietly}, Gnus will select the
4679 next group without asking for confirmation. If this variable is
4680 @code{almost-quietly}, the same will happen only if you are located on
4681 the last article in the group. Finally, if this variable is
4682 @code{slightly-quietly}, the @kbd{Z n} command will go to the next group
4683 without confirmation. Also @pxref{Group Levels}.
4685 @item gnus-auto-select-same
4686 @vindex gnus-auto-select-same
4687 If non-@code{nil}, all the movement commands will try to go to the next
4688 article with the same subject as the current. (@dfn{Same} here might
4689 mean @dfn{roughly equal}. See @code{gnus-summary-gather-subject-limit}
4690 for details (@pxref{Customizing Threading}).) If there are no more
4691 articles with the same subject, go to the first unread article.
4693 This variable is not particularly useful if you use a threaded display.
4695 @item gnus-summary-check-current
4696 @vindex gnus-summary-check-current
4697 If non-@code{nil}, all the ``unread'' movement commands will not proceed
4698 to the next (or previous) article if the current article is unread.
4699 Instead, they will choose the current article.
4701 @item gnus-auto-center-summary
4702 @vindex gnus-auto-center-summary
4703 If non-@code{nil}, Gnus will keep the point in the summary buffer
4704 centered at all times. This makes things quite tidy, but if you have a
4705 slow network connection, or simply do not like this un-Emacsism, you can
4706 set this variable to @code{nil} to get the normal Emacs scrolling
4707 action. This will also inhibit horizontal re-centering of the summary
4708 buffer, which might make it more inconvenient to read extremely long
4711 This variable can also be a number. In that case, center the window at
4712 the given number of lines from the top.
4717 @node Choosing Articles
4718 @section Choosing Articles
4719 @cindex selecting articles
4722 * Choosing Commands:: Commands for choosing articles.
4723 * Choosing Variables:: Variables that influence these commands.
4727 @node Choosing Commands
4728 @subsection Choosing Commands
4730 None of the following movement commands understand the numeric prefix,
4731 and they all select and display an article.
4733 If you want to fetch new articles or redisplay the group, see
4734 @ref{Exiting the Summary Buffer}.
4738 @kindex SPACE (Summary)
4739 @findex gnus-summary-next-page
4740 Select the current article, or, if that one's read already, the next
4741 unread article (@code{gnus-summary-next-page}).
4746 @kindex G n (Summary)
4747 @findex gnus-summary-next-unread-article
4748 @c @icon{gnus-summary-next-unread}
4749 Go to next unread article (@code{gnus-summary-next-unread-article}).
4754 @findex gnus-summary-prev-unread-article
4755 @c @icon{gnus-summary-prev-unread}
4756 Go to previous unread article (@code{gnus-summary-prev-unread-article}).
4761 @kindex G N (Summary)
4762 @findex gnus-summary-next-article
4763 Go to the next article (@code{gnus-summary-next-article}).
4768 @kindex G P (Summary)
4769 @findex gnus-summary-prev-article
4770 Go to the previous article (@code{gnus-summary-prev-article}).
4773 @kindex G C-n (Summary)
4774 @findex gnus-summary-next-same-subject
4775 Go to the next article with the same subject
4776 (@code{gnus-summary-next-same-subject}).
4779 @kindex G C-p (Summary)
4780 @findex gnus-summary-prev-same-subject
4781 Go to the previous article with the same subject
4782 (@code{gnus-summary-prev-same-subject}).
4786 @kindex G f (Summary)
4788 @findex gnus-summary-first-unread-article
4789 Go to the first unread article
4790 (@code{gnus-summary-first-unread-article}).
4794 @kindex G b (Summary)
4796 @findex gnus-summary-best-unread-article
4797 Go to the unread article with the highest score
4798 (@code{gnus-summary-best-unread-article}). If given a prefix argument,
4799 go to the first unread article that has a score over the default score.
4804 @kindex G l (Summary)
4805 @findex gnus-summary-goto-last-article
4806 Go to the previous article read (@code{gnus-summary-goto-last-article}).
4809 @kindex G o (Summary)
4810 @findex gnus-summary-pop-article
4812 @cindex article history
4813 Pop an article off the summary history and go to this article
4814 (@code{gnus-summary-pop-article}). This command differs from the
4815 command above in that you can pop as many previous articles off the
4816 history as you like, while @kbd{l} toggles the two last read articles.
4817 For a somewhat related issue (if you use these commands a lot),
4818 @pxref{Article Backlog}.
4823 @kindex G j (Summary)
4824 @findex gnus-summary-goto-article
4825 Ask for an article number or @code{Message-ID}, and then go to that
4826 article (@code{gnus-summary-goto-article}).
4831 @node Choosing Variables
4832 @subsection Choosing Variables
4834 Some variables relevant for moving and selecting articles:
4837 @item gnus-auto-extend-newsgroup
4838 @vindex gnus-auto-extend-newsgroup
4839 All the movement commands will try to go to the previous (or next)
4840 article, even if that article isn't displayed in the Summary buffer if
4841 this variable is non-@code{nil}. Gnus will then fetch the article from
4842 the server and display it in the article buffer.
4844 @item gnus-select-article-hook
4845 @vindex gnus-select-article-hook
4846 This hook is called whenever an article is selected. By default it
4847 exposes any threads hidden under the selected article.
4849 @item gnus-mark-article-hook
4850 @vindex gnus-mark-article-hook
4851 @findex gnus-summary-mark-unread-as-read
4852 @findex gnus-summary-mark-read-and-unread-as-read
4853 @findex gnus-unread-mark
4854 This hook is called whenever an article is selected. It is intended to
4855 be used for marking articles as read. The default value is
4856 @code{gnus-summary-mark-read-and-unread-as-read}, and will change the
4857 mark of almost any article you read to @code{gnus-unread-mark}. The
4858 only articles not affected by this function are ticked, dormant, and
4859 expirable articles. If you'd instead like to just have unread articles
4860 marked as read, you can use @code{gnus-summary-mark-unread-as-read}
4861 instead. It will leave marks like @code{gnus-low-score-mark},
4862 @code{gnus-del-mark} (and so on) alone.
4867 @node Paging the Article
4868 @section Scrolling the Article
4869 @cindex article scrolling
4874 @kindex SPACE (Summary)
4875 @findex gnus-summary-next-page
4876 Pressing @kbd{SPACE} will scroll the current article forward one page,
4877 or, if you have come to the end of the current article, will choose the
4878 next article (@code{gnus-summary-next-page}).
4881 @kindex DEL (Summary)
4882 @findex gnus-summary-prev-page
4883 Scroll the current article back one page (@code{gnus-summary-prev-page}).
4886 @kindex RET (Summary)
4887 @findex gnus-summary-scroll-up
4888 Scroll the current article one line forward
4889 (@code{gnus-summary-scroll-up}).
4892 @kindex M-RET (Summary)
4893 @findex gnus-summary-scroll-down
4894 Scroll the current article one line backward
4895 (@code{gnus-summary-scroll-down}).
4899 @kindex A g (Summary)
4901 @findex gnus-summary-show-article
4902 @vindex gnus-summary-show-article-charset-alist
4903 (Re)fetch the current article (@code{gnus-summary-show-article}). If
4904 given a prefix, fetch the current article, but don't run any of the
4905 article treatment functions. This will give you a ``raw'' article, just
4906 the way it came from the server.
4908 If given a numerical prefix, you can do semi-manual charset stuff.
4909 @kbd{C-u 0 g cn-gb-2312 RET} will decode the message as if it were
4910 encoded in the @code{cn-gb-2312} charset. If you have
4913 (setq gnus-summary-show-article-charset-alist
4918 then you can say @kbd{C-u 1 g} to get the same effect.
4923 @kindex A < (Summary)
4924 @findex gnus-summary-beginning-of-article
4925 Scroll to the beginning of the article
4926 (@code{gnus-summary-beginning-of-article}).
4931 @kindex A > (Summary)
4932 @findex gnus-summary-end-of-article
4933 Scroll to the end of the article (@code{gnus-summary-end-of-article}).
4937 @kindex A s (Summary)
4939 @findex gnus-summary-isearch-article
4940 Perform an isearch in the article buffer
4941 (@code{gnus-summary-isearch-article}).
4945 @findex gnus-summary-select-article-buffer
4946 Select the article buffer (@code{gnus-summary-select-article-buffer}).
4951 @node Reply Followup and Post
4952 @section Reply, Followup and Post
4955 * Summary Mail Commands:: Sending mail.
4956 * Summary Post Commands:: Sending news.
4957 * Summary Message Commands:: Other Message-related commands.
4958 * Canceling and Superseding::
4962 @node Summary Mail Commands
4963 @subsection Summary Mail Commands
4965 @cindex composing mail
4967 Commands for composing a mail message:
4973 @kindex S r (Summary)
4975 @findex gnus-summary-reply
4976 @c @icon{gnus-summary-mail-reply}
4977 @c @icon{gnus-summary-reply}
4978 Mail a reply to the author of the current article
4979 (@code{gnus-summary-reply}).
4984 @kindex S R (Summary)
4985 @findex gnus-summary-reply-with-original
4986 @c @icon{gnus-summary-reply-with-original}
4987 Mail a reply to the author of the current article and include the
4988 original message (@code{gnus-summary-reply-with-original}). This
4989 command uses the process/prefix convention.
4992 @kindex S w (Summary)
4993 @findex gnus-summary-wide-reply
4994 Mail a wide reply to the author of the current article
4995 (@code{gnus-summary-wide-reply}). A @dfn{wide reply} is a reply that
4996 goes out to all people listed in the @code{To}, @code{From} (or
4997 @code{Reply-to}) and @code{Cc} headers.
5000 @kindex S V (Summary)
5001 @findex gnus-summary-wide-reply-with-original
5002 Mail a wide reply to the current article and include the original
5003 message (@code{gnus-summary-wide-reply-with-original}). This command uses
5004 the process/prefix convention.
5007 @kindex S v (Summary)
5008 @findex gnus-summary-very-wide-reply
5009 Mail a very wide reply to the author of the current article
5010 (@code{gnus-summary-wide-reply}). A @dfn{very wide reply} is a reply
5011 that goes out to all people listed in the @code{To}, @code{From} (or
5012 @code{Reply-to}) and @code{Cc} headers in all the process/prefixed
5013 articles. This command uses the process/prefix convention.
5017 @kindex S o m (Summary)
5018 @kindex C-c C-f (Summary)
5019 @findex gnus-summary-mail-forward
5020 @c @icon{gnus-summary-mail-forward}
5021 Forward the current article to some other person
5022 (@code{gnus-summary-mail-forward}). If no prefix is given, the message
5023 is forwarded according to the value of (@code{message-forward-as-mime})
5024 and (@code{message-forward-show-mml}); if the prefix is 1, decode the
5025 message and forward directly inline; if the prefix is 2, forward message
5026 as an rfc822 MIME section; if the prefix is 3, decode message and
5027 forward as an rfc822 MIME section; if the prefix is 4, forward message
5028 directly inline; otherwise, the message is forwarded as no prefix given
5029 but use the flipped value of (@code{message-forward-as-mime}). By
5030 default, the message is decoded and forwarded as an rfc822 MIME section.
5035 @kindex S m (Summary)
5036 @findex gnus-summary-mail-other-window
5037 @c @icon{gnus-summary-mail-originate}
5038 Prepare a mail (@code{gnus-summary-mail-other-window}). By default, use
5039 the posting style of the current group. If given a prefix, disable that.
5040 If the prefix is 1, prompt for a group name to find the posting style.
5045 @kindex S i (Summary)
5046 @findex gnus-summary-news-other-window
5047 Prepare a news (@code{gnus-summary-news-other-window}). By default,
5048 post to the current group. If given a prefix, disable that. If the
5049 prefix is 1, prompt for a group to post to.
5051 This function actually prepares a news even when using mail groups.
5052 This is useful for "posting" messages to mail groups without actually
5053 sending them over the network: they're just saved directly to the group
5054 in question. The corresponding back end must have a request-post method
5055 for this to work though.
5058 @kindex S D b (Summary)
5059 @findex gnus-summary-resend-bounced-mail
5060 @cindex bouncing mail
5061 If you have sent a mail, but the mail was bounced back to you for some
5062 reason (wrong address, transient failure), you can use this command to
5063 resend that bounced mail (@code{gnus-summary-resend-bounced-mail}). You
5064 will be popped into a mail buffer where you can edit the headers before
5065 sending the mail off again. If you give a prefix to this command, and
5066 the bounced mail is a reply to some other mail, Gnus will try to fetch
5067 that mail and display it for easy perusal of its headers. This might
5068 very well fail, though.
5071 @kindex S D r (Summary)
5072 @findex gnus-summary-resend-message
5073 Not to be confused with the previous command,
5074 @code{gnus-summary-resend-message} will prompt you for an address to
5075 send the current message off to, and then send it to that place. The
5076 headers of the message won't be altered---but lots of headers that say
5077 @code{Resent-To}, @code{Resent-From} and so on will be added. This
5078 means that you actually send a mail to someone that has a @code{To}
5079 header that (probably) points to yourself. This will confuse people.
5080 So, natcherly you'll only do that if you're really eVIl.
5082 This command is mainly used if you have several accounts and want to
5083 ship a mail to a different account of yours. (If you're both
5084 @code{root} and @code{postmaster} and get a mail for @code{postmaster}
5085 to the @code{root} account, you may want to resend it to
5086 @code{postmaster}. Ordnung muß sein!
5088 This command understands the process/prefix convention
5089 (@pxref{Process/Prefix}).
5092 @kindex S O m (Summary)
5093 @findex gnus-uu-digest-mail-forward
5094 Digest the current series (@pxref{Decoding Articles}) and forward the
5095 result using mail (@code{gnus-uu-digest-mail-forward}). This command
5096 uses the process/prefix convention (@pxref{Process/Prefix}).
5099 @kindex S M-c (Summary)
5100 @findex gnus-summary-mail-crosspost-complaint
5101 @cindex crossposting
5102 @cindex excessive crossposting
5103 Send a complaint about excessive crossposting to the author of the
5104 current article (@code{gnus-summary-mail-crosspost-complaint}).
5106 @findex gnus-crosspost-complaint
5107 This command is provided as a way to fight back against the current
5108 crossposting pandemic that's sweeping Usenet. It will compose a reply
5109 using the @code{gnus-crosspost-complaint} variable as a preamble. This
5110 command understands the process/prefix convention
5111 (@pxref{Process/Prefix}) and will prompt you before sending each mail.
5115 Also @xref{Header Commands, ,Header Commands, message, The Message
5116 Manual}, for more information.
5119 @node Summary Post Commands
5120 @subsection Summary Post Commands
5122 @cindex composing news
5124 Commands for posting a news article:
5130 @kindex S p (Summary)
5131 @findex gnus-summary-post-news
5132 @c @icon{gnus-summary-post-news}
5133 Prepare for posting an article (@code{gnus-summary-post-news}). By
5134 default, post to the current group. If given a prefix, disable that.
5135 If the prefix is 1, prompt for another group instead.
5140 @kindex S f (Summary)
5141 @findex gnus-summary-followup
5142 @c @icon{gnus-summary-followup}
5143 Post a followup to the current article (@code{gnus-summary-followup}).
5147 @kindex S F (Summary)
5149 @c @icon{gnus-summary-followup-with-original}
5150 @findex gnus-summary-followup-with-original
5151 Post a followup to the current article and include the original message
5152 (@code{gnus-summary-followup-with-original}). This command uses the
5153 process/prefix convention.
5156 @kindex S n (Summary)
5157 @findex gnus-summary-followup-to-mail
5158 Post a followup to the current article via news, even if you got the
5159 message through mail (@code{gnus-summary-followup-to-mail}).
5162 @kindex S N (Summary)
5163 @findex gnus-summary-followup-to-mail-with-original
5164 Post a followup to the current article via news, even if you got the
5165 message through mail and include the original message
5166 (@code{gnus-summary-followup-to-mail-with-original}). This command uses
5167 the process/prefix convention.
5170 @kindex S o p (Summary)
5171 @findex gnus-summary-post-forward
5172 Forward the current article to a newsgroup
5173 (@code{gnus-summary-post-forward}).
5174 If no prefix is given, the message is forwarded according to the value
5175 of (@code{message-forward-as-mime}) and
5176 (@code{message-forward-show-mml}); if the prefix is 1, decode the
5177 message and forward directly inline; if the prefix is 2, forward message
5178 as an rfc822 MIME section; if the prefix is 3, decode message and
5179 forward as an rfc822 MIME section; if the prefix is 4, forward message
5180 directly inline; otherwise, the message is forwarded as no prefix given
5181 but use the flipped value of (@code{message-forward-as-mime}). By
5182 default, the message is decoded and forwarded as an rfc822 MIME section.
5185 @kindex S O p (Summary)
5186 @findex gnus-uu-digest-post-forward
5188 @cindex making digests
5189 Digest the current series and forward the result to a newsgroup
5190 (@code{gnus-uu-digest-mail-forward}). This command uses the
5191 process/prefix convention.
5194 @kindex S u (Summary)
5195 @findex gnus-uu-post-news
5196 @c @icon{gnus-uu-post-news}
5197 Uuencode a file, split it into parts, and post it as a series
5198 (@code{gnus-uu-post-news}). (@pxref{Uuencoding and Posting}).
5201 Also @xref{Header Commands, ,Header Commands, message, The Message
5202 Manual}, for more information.
5205 @node Summary Message Commands
5206 @subsection Summary Message Commands
5210 @kindex S y (Summary)
5211 @findex gnus-summary-yank-message
5212 Yank the current article into an already existing Message composition
5213 buffer (@code{gnus-summary-yank-message}). This command prompts for
5214 what message buffer you want to yank into, and understands the
5215 process/prefix convention (@pxref{Process/Prefix}).
5220 @node Canceling and Superseding
5221 @subsection Canceling Articles
5222 @cindex canceling articles
5223 @cindex superseding articles
5225 Have you ever written something, and then decided that you really,
5226 really, really wish you hadn't posted that?
5228 Well, you can't cancel mail, but you can cancel posts.
5230 @findex gnus-summary-cancel-article
5232 @c @icon{gnus-summary-cancel-article}
5233 Find the article you wish to cancel (you can only cancel your own
5234 articles, so don't try any funny stuff). Then press @kbd{C} or @kbd{S
5235 c} (@code{gnus-summary-cancel-article}). Your article will be
5236 canceled---machines all over the world will be deleting your article.
5237 This command uses the process/prefix convention (@pxref{Process/Prefix}).
5239 Be aware, however, that not all sites honor cancels, so your article may
5240 live on here and there, while most sites will delete the article in
5243 Gnus will use the ``current'' select method when canceling. If you
5244 want to use the standard posting method, use the @samp{a} symbolic
5245 prefix (@pxref{Symbolic Prefixes}).
5247 If you discover that you have made some mistakes and want to do some
5248 corrections, you can post a @dfn{superseding} article that will replace
5249 your original article.
5251 @findex gnus-summary-supersede-article
5253 Go to the original article and press @kbd{S s}
5254 (@code{gnus-summary-supersede-article}). You will be put in a buffer
5255 where you can edit the article all you want before sending it off the
5258 The same goes for superseding as for canceling, only more so: Some
5259 sites do not honor superseding. On those sites, it will appear that you
5260 have posted almost the same article twice.
5262 If you have just posted the article, and change your mind right away,
5263 there is a trick you can use to cancel/supersede the article without
5264 waiting for the article to appear on your site first. You simply return
5265 to the post buffer (which is called @code{*sent ...*}). There you will
5266 find the article you just posted, with all the headers intact. Change
5267 the @code{Message-ID} header to a @code{Cancel} or @code{Supersedes}
5268 header by substituting one of those words for the word
5269 @code{Message-ID}. Then just press @kbd{C-c C-c} to send the article as
5270 you would do normally. The previous article will be
5271 canceled/superseded.
5273 Just remember, kids: There is no 'c' in 'supersede'.
5275 @node Delayed Articles
5276 @section Delayed Articles
5277 @cindex delayed sending
5278 @cindex send delayed
5280 Sometimes, you might wish to delay the sending of a message. For
5281 example, you might wish to arrange for a message to turn up just in time
5282 to remind your about the birthday of your Significant Other. For this,
5283 there is the @code{gnus-delay} package. Setup is simple:
5286 (gnus-delay-initialize)
5289 @findex gnus-delay-article
5290 Normally, to send a message you use the @kbd{C-c C-c} command from
5291 Message mode. To delay a message, use @kbd{C-c C-j}
5292 (@code{gnus-delay-article}) instead. This will ask you for how long the
5293 message should be delayed. Possible answers are:
5297 A time span. Consists of an integer and a letter. For example,
5298 @code{42d} means to delay for 42 days. Available letters are @code{m}
5299 (minutes), @code{h} (hours), @code{d} (days), @code{w} (weeks), @code{M}
5300 (months) and @code{Y} (years).
5303 A specific date. Looks like @code{YYYYY-MM-DD}. The message will be
5304 delayed until that day, at a specific time (eight o'clock by default).
5305 See also @code{gnus-delay-default-hour}.
5308 A specific time of day. Given in @code{hh:mm} format, 24h, no am/pm
5309 stuff. The deadline will be at that time today, except if that time has
5310 already passed, then it's at the given time tomorrow. So if it's ten
5311 o'clock in the morning and you specify @code{11:15}, then the deadline
5312 is one hour and fifteen minutes hence. But if you specify @code{9:20},
5313 that means a time tomorrow.
5316 The action of the @code{gnus-delay-article} command is influenced by a
5317 couple of variables:
5320 @item gnus-delay-default-hour
5321 @vindex gnus-delay-default-hour
5322 When you specify a specific date, the message will be due on that hour
5323 on the given date. Possible values are integers 0 through 23.
5325 @item gnus-delay-default-delay
5326 @vindex gnus-delay-default-delay
5327 This is a string and gives the default delay. It can be of any of the
5328 formats described above.
5330 @item gnus-delay-group
5331 @vindex gnus-delay-group
5332 Delayed articles will be kept in this group on the drafts server until
5333 they are due. You probably don't need to change this. The default
5334 value is @code{"delayed"}.
5336 @item gnus-delay-header
5337 @vindex gnus-delay-header
5338 The deadline for each article will be stored in a header. This variable
5339 is a string and gives the header name. You probably don't need to
5340 change this. The default value is @code{"X-Gnus-Delayed"}.
5343 The way delaying works is like this: when you use the
5344 @code{gnus-delay-article} command, you give a certain delay. Gnus
5345 calculates the deadline of the message and stores it in the
5346 @code{X-Gnus-Delayed} header and puts the message in the
5347 @code{nndraft:delayed} group.
5349 And whenever you get new news, Gnus looks through the group for articles
5350 which are due and sends them. It uses the @code{gnus-delay-send-queue}
5351 function for this. By default, this function is added to the hook
5352 @code{gnus-get-new-news-hook}. But of course, you can change this.
5353 Maybe you want to use the demon to send drafts? Just tell the demon to
5354 execute the @code{gnus-delay-send-queue} function.
5357 @item gnus-delay-initialize
5358 @findex gnus-delay-initialize
5359 By default, this function installs the @kbd{C-c C-j} key binding in
5360 Message mode and @code{gnus-delay-send-queue} in
5361 @code{gnus-get-new-news-hook}. But it accepts two optional arguments,
5362 @code{no-keymap} and @code{no-check}. If @code{no-keymap} is non-nil,
5363 the @kbd{C-c C-j} binding is not intalled. If @code{no-check} is
5364 non-nil, @code{gnus-get-new-news-hook} is not changed.
5366 For example, @code{(gnus-delay-initialize nil t)} means to change the
5367 keymap but not to change @code{gnus-get-new-news-hook}. Presumably, you
5368 want to use the demon for sending due delayed articles. Just don't
5369 forget to set that up :-)
5373 @node Marking Articles
5374 @section Marking Articles
5375 @cindex article marking
5376 @cindex article ticking
5379 There are several marks you can set on an article.
5381 You have marks that decide the @dfn{readedness} (whoo, neato-keano
5382 neologism ohoy!) of the article. Alphabetic marks generally mean
5383 @dfn{read}, while non-alphabetic characters generally mean @dfn{unread}.
5385 In addition, you also have marks that do not affect readedness.
5388 * Unread Articles:: Marks for unread articles.
5389 * Read Articles:: Marks for read articles.
5390 * Other Marks:: Marks that do not affect readedness.
5394 There's a plethora of commands for manipulating these marks:
5398 * Setting Marks:: How to set and remove marks.
5399 * Generic Marking Commands:: How to customize the marking.
5400 * Setting Process Marks:: How to mark articles for later processing.
5404 @node Unread Articles
5405 @subsection Unread Articles
5407 The following marks mark articles as (kinda) unread, in one form or
5412 @vindex gnus-ticked-mark
5413 Marked as ticked (@code{gnus-ticked-mark}).
5415 @dfn{Ticked articles} are articles that will remain visible always. If
5416 you see an article that you find interesting, or you want to put off
5417 reading it, or replying to it, until sometime later, you'd typically
5418 tick it. However, articles can be expired (from news servers by the
5419 news server software, Gnus itself never expires ticked messages), so if
5420 you want to keep an article forever, you'll have to make it persistent
5421 (@pxref{Persistent Articles}).
5424 @vindex gnus-dormant-mark
5425 Marked as dormant (@code{gnus-dormant-mark}).
5427 @dfn{Dormant articles} will only appear in the summary buffer if there
5428 are followups to it. If you want to see them even if they don't have
5429 followups, you can use the @kbd{/ D} command (@pxref{Limiting}).
5430 Otherwise (except for the visibility issue), they are just like ticked
5434 @vindex gnus-unread-mark
5435 Marked as unread (@code{gnus-unread-mark}).
5437 @dfn{Unread articles} are articles that haven't been read at all yet.
5442 @subsection Read Articles
5443 @cindex expirable mark
5445 All the following marks mark articles as read.
5450 @vindex gnus-del-mark
5451 These are articles that the user has marked as read with the @kbd{d}
5452 command manually, more or less (@code{gnus-del-mark}).
5455 @vindex gnus-read-mark
5456 Articles that have actually been read (@code{gnus-read-mark}).
5459 @vindex gnus-ancient-mark
5460 Articles that were marked as read in previous sessions and are now
5461 @dfn{old} (@code{gnus-ancient-mark}).
5464 @vindex gnus-killed-mark
5465 Marked as killed (@code{gnus-killed-mark}).
5468 @vindex gnus-kill-file-mark
5469 Marked as killed by kill files (@code{gnus-kill-file-mark}).
5472 @vindex gnus-low-score-mark
5473 Marked as read by having too low a score (@code{gnus-low-score-mark}).
5476 @vindex gnus-catchup-mark
5477 Marked as read by a catchup (@code{gnus-catchup-mark}).
5480 @vindex gnus-canceled-mark
5481 Canceled article (@code{gnus-canceled-mark})
5484 @vindex gnus-souped-mark
5485 @sc{soup}ed article (@code{gnus-souped-mark}). @xref{SOUP}.
5488 @vindex gnus-sparse-mark
5489 Sparsely reffed article (@code{gnus-sparse-mark}). @xref{Customizing
5493 @vindex gnus-duplicate-mark
5494 Article marked as read by duplicate suppression
5495 (@code{gnus-duplicate-mark}). @xref{Duplicate Suppression}.
5499 All these marks just mean that the article is marked as read, really.
5500 They are interpreted differently when doing adaptive scoring, though.
5502 One more special mark, though:
5506 @vindex gnus-expirable-mark
5507 Marked as expirable (@code{gnus-expirable-mark}).
5509 Marking articles as @dfn{expirable} (or have them marked as such
5510 automatically) doesn't make much sense in normal groups---a user doesn't
5511 control expiring of news articles, but in mail groups, for instance,
5512 articles marked as @dfn{expirable} can be deleted by Gnus at
5518 @subsection Other Marks
5519 @cindex process mark
5522 There are some marks that have nothing to do with whether the article is
5528 You can set a bookmark in the current article. Say you are reading a
5529 long thesis on cats' urinary tracts, and have to go home for dinner
5530 before you've finished reading the thesis. You can then set a bookmark
5531 in the article, and Gnus will jump to this bookmark the next time it
5532 encounters the article. @xref{Setting Marks}.
5535 @vindex gnus-replied-mark
5536 All articles that you have replied to or made a followup to (i.e., have
5537 answered) will be marked with an @samp{A} in the second column
5538 (@code{gnus-replied-mark}).
5540 @vindex gnus-forwarded-mark
5541 All articles that you have forwarded will be marked with an @samp{F} in
5542 the second column (@code{gnus-forwarded-mark}).
5544 @vindex gnus-recent-mark
5545 Articles that are ``recently'' arrived in the group will be marked
5546 with an @samp{N} in the second column (@code{gnus-recent-mark}). Most
5547 back end doesn't support the mark, in which case it's not shown.
5550 @vindex gnus-cached-mark
5551 Articles stored in the article cache will be marked with an @samp{*} in
5552 the second column (@code{gnus-cached-mark}). @xref{Article Caching}.
5555 @vindex gnus-saved-mark
5556 Articles ``saved'' (in some manner or other; not necessarily
5557 religiously) are marked with an @samp{S} in the second column
5558 (@code{gnus-saved-mark}).
5561 @vindex gnus-recent-mark
5562 Articles that according to the back end haven't been seen by the user
5563 before are marked with a @samp{N} in the second column
5564 (@code{gnus-recent-mark}). Note that not all back ends support this
5565 mark, in which case it simply never appear.
5568 @vindex gnus-unseen-mark
5569 Articles that haven't been seen by the user before are marked with a
5570 @samp{.} in the second column (@code{gnus-unseen-mark}).
5573 @vindex gnus-not-empty-thread-mark
5574 @vindex gnus-empty-thread-mark
5575 If the @samp{%e} spec is used, the presence of threads or not will be
5576 marked with @code{gnus-not-empty-thread-mark} and
5577 @code{gnus-empty-thread-mark} in the third column, respectively.
5580 @vindex gnus-process-mark
5581 Finally we have the @dfn{process mark} (@code{gnus-process-mark}). A
5582 variety of commands react to the presence of the process mark. For
5583 instance, @kbd{X u} (@code{gnus-uu-decode-uu}) will uudecode and view
5584 all articles that have been marked with the process mark. Articles
5585 marked with the process mark have a @samp{#} in the second column.
5589 You might have noticed that most of these ``non-readedness'' marks
5590 appear in the second column by default. So if you have a cached, saved,
5591 replied article that you have process-marked, what will that look like?
5593 Nothing much. The precedence rules go as follows: process -> cache ->
5594 replied -> saved. So if the article is in the cache and is replied,
5595 you'll only see the cache mark and not the replied mark.
5599 @subsection Setting Marks
5600 @cindex setting marks
5602 All the marking commands understand the numeric prefix.
5607 @kindex M c (Summary)
5608 @kindex M-u (Summary)
5609 @findex gnus-summary-clear-mark-forward
5610 @cindex mark as unread
5611 Clear all readedness-marks from the current article
5612 (@code{gnus-summary-clear-mark-forward}). In other words, mark the
5618 @kindex M t (Summary)
5619 @findex gnus-summary-tick-article-forward
5620 Tick the current article (@code{gnus-summary-tick-article-forward}).
5621 @xref{Article Caching}.
5626 @kindex M ? (Summary)
5627 @findex gnus-summary-mark-as-dormant
5628 Mark the current article as dormant
5629 (@code{gnus-summary-mark-as-dormant}). @xref{Article Caching}.
5633 @kindex M d (Summary)
5635 @findex gnus-summary-mark-as-read-forward
5636 Mark the current article as read
5637 (@code{gnus-summary-mark-as-read-forward}).
5641 @findex gnus-summary-mark-as-read-backward
5642 Mark the current article as read and move point to the previous line
5643 (@code{gnus-summary-mark-as-read-backward}).
5648 @kindex M k (Summary)
5649 @findex gnus-summary-kill-same-subject-and-select
5650 Mark all articles that have the same subject as the current one as read,
5651 and then select the next unread article
5652 (@code{gnus-summary-kill-same-subject-and-select}).
5656 @kindex M K (Summary)
5657 @kindex C-k (Summary)
5658 @findex gnus-summary-kill-same-subject
5659 Mark all articles that have the same subject as the current one as read
5660 (@code{gnus-summary-kill-same-subject}).
5663 @kindex M C (Summary)
5664 @findex gnus-summary-catchup
5665 @c @icon{gnus-summary-catchup}
5666 Mark all unread articles as read (@code{gnus-summary-catchup}).
5669 @kindex M C-c (Summary)
5670 @findex gnus-summary-catchup-all
5671 Mark all articles in the group as read---even the ticked and dormant
5672 articles (@code{gnus-summary-catchup-all}).
5675 @kindex M H (Summary)
5676 @findex gnus-summary-catchup-to-here
5677 Catchup the current group to point (before the point)
5678 (@code{gnus-summary-catchup-to-here}).
5681 @kindex M h (Summary)
5682 @findex gnus-summary-catchup-from-here
5683 Catchup the current group from point (after the point)
5684 (@code{gnus-summary-catchup-from-here}).
5687 @kindex C-w (Summary)
5688 @findex gnus-summary-mark-region-as-read
5689 Mark all articles between point and mark as read
5690 (@code{gnus-summary-mark-region-as-read}).
5693 @kindex M V k (Summary)
5694 @findex gnus-summary-kill-below
5695 Kill all articles with scores below the default score (or below the
5696 numeric prefix) (@code{gnus-summary-kill-below}).
5700 @kindex M e (Summary)
5702 @findex gnus-summary-mark-as-expirable
5703 Mark the current article as expirable
5704 (@code{gnus-summary-mark-as-expirable}).
5707 @kindex M b (Summary)
5708 @findex gnus-summary-set-bookmark
5709 Set a bookmark in the current article
5710 (@code{gnus-summary-set-bookmark}).
5713 @kindex M B (Summary)
5714 @findex gnus-summary-remove-bookmark
5715 Remove the bookmark from the current article
5716 (@code{gnus-summary-remove-bookmark}).
5719 @kindex M V c (Summary)
5720 @findex gnus-summary-clear-above
5721 Clear all marks from articles with scores over the default score (or
5722 over the numeric prefix) (@code{gnus-summary-clear-above}).
5725 @kindex M V u (Summary)
5726 @findex gnus-summary-tick-above
5727 Tick all articles with scores over the default score (or over the
5728 numeric prefix) (@code{gnus-summary-tick-above}).
5731 @kindex M V m (Summary)
5732 @findex gnus-summary-mark-above
5733 Prompt for a mark, and mark all articles with scores over the default
5734 score (or over the numeric prefix) with this mark
5735 (@code{gnus-summary-clear-above}).
5738 @vindex gnus-summary-goto-unread
5739 The @code{gnus-summary-goto-unread} variable controls what action should
5740 be taken after setting a mark. If non-@code{nil}, point will move to
5741 the next/previous unread article. If @code{nil}, point will just move
5742 one line up or down. As a special case, if this variable is
5743 @code{never}, all the marking commands as well as other commands (like
5744 @kbd{SPACE}) will move to the next article, whether it is unread or not.
5745 The default is @code{t}.
5748 @node Generic Marking Commands
5749 @subsection Generic Marking Commands
5751 Some people would like the command that ticks an article (@kbd{!}) go to
5752 the next article. Others would like it to go to the next unread
5753 article. Yet others would like it to stay on the current article. And
5754 even though I haven't heard of anybody wanting it to go to the
5755 previous (unread) article, I'm sure there are people that want that as
5758 Multiply these five behaviors with five different marking commands, and
5759 you get a potentially complex set of variable to control what each
5762 To sidestep that mess, Gnus provides commands that do all these
5763 different things. They can be found on the @kbd{M M} map in the summary
5764 buffer. Type @kbd{M M C-h} to see them all---there are too many of them
5765 to list in this manual.
5767 While you can use these commands directly, most users would prefer
5768 altering the summary mode keymap. For instance, if you would like the
5769 @kbd{!} command to go to the next article instead of the next unread
5770 article, you could say something like:
5773 (add-hook 'gnus-summary-mode-hook 'my-alter-summary-map)
5774 (defun my-alter-summary-map ()
5775 (local-set-key "!" 'gnus-summary-put-mark-as-ticked-next))
5781 (defun my-alter-summary-map ()
5782 (local-set-key "!" "MM!n"))
5786 @node Setting Process Marks
5787 @subsection Setting Process Marks
5788 @cindex setting process marks
5795 @kindex M P p (Summary)
5796 @findex gnus-summary-mark-as-processable
5797 Mark the current article with the process mark
5798 (@code{gnus-summary-mark-as-processable}).
5799 @findex gnus-summary-unmark-as-processable
5803 @kindex M P u (Summary)
5804 @kindex M-# (Summary)
5805 Remove the process mark, if any, from the current article
5806 (@code{gnus-summary-unmark-as-processable}).
5809 @kindex M P U (Summary)
5810 @findex gnus-summary-unmark-all-processable
5811 Remove the process mark from all articles
5812 (@code{gnus-summary-unmark-all-processable}).
5815 @kindex M P i (Summary)
5816 @findex gnus-uu-invert-processable
5817 Invert the list of process marked articles
5818 (@code{gnus-uu-invert-processable}).
5821 @kindex M P R (Summary)
5822 @findex gnus-uu-mark-by-regexp
5823 Mark articles that have a @code{Subject} header that matches a regular
5824 expression (@code{gnus-uu-mark-by-regexp}).
5827 @kindex M P G (Summary)
5828 @findex gnus-uu-unmark-by-regexp
5829 Unmark articles that have a @code{Subject} header that matches a regular
5830 expression (@code{gnus-uu-unmark-by-regexp}).
5833 @kindex M P r (Summary)
5834 @findex gnus-uu-mark-region
5835 Mark articles in region (@code{gnus-uu-mark-region}).
5838 @kindex M P t (Summary)
5839 @findex gnus-uu-mark-thread
5840 Mark all articles in the current (sub)thread
5841 (@code{gnus-uu-mark-thread}).
5844 @kindex M P T (Summary)
5845 @findex gnus-uu-unmark-thread
5846 Unmark all articles in the current (sub)thread
5847 (@code{gnus-uu-unmark-thread}).
5850 @kindex M P v (Summary)
5851 @findex gnus-uu-mark-over
5852 Mark all articles that have a score above the prefix argument
5853 (@code{gnus-uu-mark-over}).
5856 @kindex M P s (Summary)
5857 @findex gnus-uu-mark-series
5858 Mark all articles in the current series (@code{gnus-uu-mark-series}).
5861 @kindex M P S (Summary)
5862 @findex gnus-uu-mark-sparse
5863 Mark all series that have already had some articles marked
5864 (@code{gnus-uu-mark-sparse}).
5867 @kindex M P a (Summary)
5868 @findex gnus-uu-mark-all
5869 Mark all articles in series order (@code{gnus-uu-mark-series}).
5872 @kindex M P b (Summary)
5873 @findex gnus-uu-mark-buffer
5874 Mark all articles in the buffer in the order they appear
5875 (@code{gnus-uu-mark-buffer}).
5878 @kindex M P k (Summary)
5879 @findex gnus-summary-kill-process-mark
5880 Push the current process mark set onto the stack and unmark all articles
5881 (@code{gnus-summary-kill-process-mark}).
5884 @kindex M P y (Summary)
5885 @findex gnus-summary-yank-process-mark
5886 Pop the previous process mark set from the stack and restore it
5887 (@code{gnus-summary-yank-process-mark}).
5890 @kindex M P w (Summary)
5891 @findex gnus-summary-save-process-mark
5892 Push the current process mark set onto the stack
5893 (@code{gnus-summary-save-process-mark}).
5897 Also see the @kbd{&} command in @pxref{Searching for Articles} for how to
5898 set process marks based on article body contents.
5905 It can be convenient to limit the summary buffer to just show some
5906 subset of the articles currently in the group. The effect most limit
5907 commands have is to remove a few (or many) articles from the summary
5910 All limiting commands work on subsets of the articles already fetched
5911 from the servers. None of these commands query the server for
5912 additional articles.
5918 @kindex / / (Summary)
5919 @findex gnus-summary-limit-to-subject
5920 Limit the summary buffer to articles that match some subject
5921 (@code{gnus-summary-limit-to-subject}). If given a prefix, exclude
5925 @kindex / a (Summary)
5926 @findex gnus-summary-limit-to-author
5927 Limit the summary buffer to articles that match some author
5928 (@code{gnus-summary-limit-to-author}). If given a prefix, exclude
5932 @kindex / x (Summary)
5933 @findex gnus-summary-limit-to-extra
5934 Limit the summary buffer to articles that match one of the ``extra''
5935 headers (@pxref{To From Newsgroups})
5936 (@code{gnus-summary-limit-to-extra}). If given a prefix, exclude
5941 @kindex / u (Summary)
5943 @findex gnus-summary-limit-to-unread
5944 Limit the summary buffer to articles not marked as read
5945 (@code{gnus-summary-limit-to-unread}). If given a prefix, limit the
5946 buffer to articles strictly unread. This means that ticked and
5947 dormant articles will also be excluded.
5950 @kindex / m (Summary)
5951 @findex gnus-summary-limit-to-marks
5952 Ask for a mark and then limit to all articles that have been marked
5953 with that mark (@code{gnus-summary-limit-to-marks}).
5956 @kindex / t (Summary)
5957 @findex gnus-summary-limit-to-age
5958 Ask for a number and then limit the summary buffer to articles older than (or equal to) that number of days
5959 (@code{gnus-summary-limit-to-age}). If given a prefix, limit to
5960 articles younger than that number of days.
5963 @kindex / n (Summary)
5964 @findex gnus-summary-limit-to-articles
5965 Limit the summary buffer to the current article
5966 (@code{gnus-summary-limit-to-articles}). Uses the process/prefix
5967 convention (@pxref{Process/Prefix}).
5970 @kindex / w (Summary)
5971 @findex gnus-summary-pop-limit
5972 Pop the previous limit off the stack and restore it
5973 (@code{gnus-summary-pop-limit}). If given a prefix, pop all limits off
5977 @kindex / v (Summary)
5978 @findex gnus-summary-limit-to-score
5979 Limit the summary buffer to articles that have a score at or above some
5980 score (@code{gnus-summary-limit-to-score}).
5983 @kindex / p (Summary)
5984 @findex gnus-summary-limit-to-display-parameter
5985 Limit the summary buffer to articles that satisfy the @code{display}
5986 group parameter predicate
5987 (@code{gnus-summary-limit-to-display-parameter}). See @pxref{Group
5988 Parameters} for more on this predicate.
5992 @kindex M S (Summary)
5993 @kindex / E (Summary)
5994 @findex gnus-summary-limit-include-expunged
5995 Include all expunged articles in the limit
5996 (@code{gnus-summary-limit-include-expunged}).
5999 @kindex / D (Summary)
6000 @findex gnus-summary-limit-include-dormant
6001 Include all dormant articles in the limit
6002 (@code{gnus-summary-limit-include-dormant}).
6005 @kindex / * (Summary)
6006 @findex gnus-summary-limit-include-cached
6007 Include all cached articles in the limit
6008 (@code{gnus-summary-limit-include-cached}).
6011 @kindex / d (Summary)
6012 @findex gnus-summary-limit-exclude-dormant
6013 Exclude all dormant articles from the limit
6014 (@code{gnus-summary-limit-exclude-dormant}).
6017 @kindex / M (Summary)
6018 @findex gnus-summary-limit-exclude-marks
6019 Exclude all marked articles (@code{gnus-summary-limit-exclude-marks}).
6022 @kindex / T (Summary)
6023 @findex gnus-summary-limit-include-thread
6024 Include all the articles in the current thread in the limit.
6027 @kindex / c (Summary)
6028 @findex gnus-summary-limit-exclude-childless-dormant
6029 Exclude all dormant articles that have no children from the limit
6030 (@code{gnus-summary-limit-exclude-childless-dormant}).
6033 @kindex / C (Summary)
6034 @findex gnus-summary-limit-mark-excluded-as-read
6035 Mark all excluded unread articles as read
6036 (@code{gnus-summary-limit-mark-excluded-as-read}). If given a prefix,
6037 also mark excluded ticked and dormant articles as read.
6040 @kindex / N (Summary)
6041 @findex gnus-summary-insert-new-articles
6042 Insert all new articles in the summary buffer. It scans for new emails
6043 if @var{back-end}@code{-get-new-mail} is non-@code{nil}.
6046 @kindex / o (Summary)
6047 @findex gnus-summary-insert-old-articles
6048 Insert all old articles in the summary buffer. If given a numbered
6049 prefix, fetch this number of articles.
6057 @cindex article threading
6059 Gnus threads articles by default. @dfn{To thread} is to put responses
6060 to articles directly after the articles they respond to---in a
6061 hierarchical fashion.
6063 Threading is done by looking at the @code{References} headers of the
6064 articles. In a perfect world, this would be enough to build pretty
6065 trees, but unfortunately, the @code{References} header is often broken
6066 or simply missing. Weird news propagation exacerbates the problem,
6067 so one has to employ other heuristics to get pleasing results. A
6068 plethora of approaches exists, as detailed in horrible detail in
6069 @pxref{Customizing Threading}.
6071 First, a quick overview of the concepts:
6075 The top-most article in a thread; the first article in the thread.
6078 A tree-like article structure.
6081 A small(er) section of this tree-like structure.
6084 Threads often lose their roots due to article expiry, or due to the root
6085 already having been read in a previous session, and not displayed in the
6086 summary buffer. We then typically have many sub-threads that really
6087 belong to one thread, but are without connecting roots. These are
6088 called loose threads.
6090 @item thread gathering
6091 An attempt to gather loose threads into bigger threads.
6093 @item sparse threads
6094 A thread where the missing articles have been ``guessed'' at, and are
6095 displayed as empty lines in the summary buffer.
6101 * Customizing Threading:: Variables you can change to affect the threading.
6102 * Thread Commands:: Thread based commands in the summary buffer.
6106 @node Customizing Threading
6107 @subsection Customizing Threading
6108 @cindex customizing threading
6111 * Loose Threads:: How Gnus gathers loose threads into bigger threads.
6112 * Filling In Threads:: Making the threads displayed look fuller.
6113 * More Threading:: Even more variables for fiddling with threads.
6114 * Low-Level Threading:: You thought it was over... but you were wrong!
6119 @subsubsection Loose Threads
6122 @cindex loose threads
6125 @item gnus-summary-make-false-root
6126 @vindex gnus-summary-make-false-root
6127 If non-@code{nil}, Gnus will gather all loose subtrees into one big tree
6128 and create a dummy root at the top. (Wait a minute. Root at the top?
6129 Yup.) Loose subtrees occur when the real root has expired, or you've
6130 read or killed the root in a previous session.
6132 When there is no real root of a thread, Gnus will have to fudge
6133 something. This variable says what fudging method Gnus should use.
6134 There are four possible values:
6138 \gnusfigure{The Summary Buffer}{390}{
6139 \put(0,0){\epsfig{figure=ps/summary-adopt,width=7.5cm}}
6140 \put(445,0){\makebox(0,0)[br]{\epsfig{figure=ps/summary-empty,width=7.5cm}}}
6141 \put(0,400){\makebox(0,0)[tl]{\epsfig{figure=ps/summary-none,width=7.5cm}}}
6142 \put(445,400){\makebox(0,0)[tr]{\epsfig{figure=ps/summary-dummy,width=7.5cm}}}
6147 @cindex adopting articles
6152 Gnus will make the first of the orphaned articles the parent. This
6153 parent will adopt all the other articles. The adopted articles will be
6154 marked as such by pointy brackets (@samp{<>}) instead of the standard
6155 square brackets (@samp{[]}). This is the default method.
6158 @vindex gnus-summary-dummy-line-format
6159 Gnus will create a dummy summary line that will pretend to be the
6160 parent. This dummy line does not correspond to any real article, so
6161 selecting it will just select the first real article after the dummy
6162 article. @code{gnus-summary-dummy-line-format} is used to specify the
6163 format of the dummy roots. It accepts only one format spec: @samp{S},
6164 which is the subject of the article. @xref{Formatting Variables}.
6167 Gnus won't actually make any article the parent, but simply leave the
6168 subject field of all orphans except the first empty. (Actually, it will
6169 use @code{gnus-summary-same-subject} as the subject (@pxref{Summary
6173 Don't make any article parent at all. Just gather the threads and
6174 display them after one another.
6177 Don't gather loose threads.
6180 @item gnus-summary-gather-subject-limit
6181 @vindex gnus-summary-gather-subject-limit
6182 Loose threads are gathered by comparing subjects of articles. If this
6183 variable is @code{nil}, Gnus requires an exact match between the
6184 subjects of the loose threads before gathering them into one big
6185 super-thread. This might be too strict a requirement, what with the
6186 presence of stupid newsreaders that chop off long subject lines. If
6187 you think so, set this variable to, say, 20 to require that only the
6188 first 20 characters of the subjects have to match. If you set this
6189 variable to a really low number, you'll find that Gnus will gather
6190 everything in sight into one thread, which isn't very helpful.
6192 @cindex fuzzy article gathering
6193 If you set this variable to the special value @code{fuzzy}, Gnus will
6194 use a fuzzy string comparison algorithm on the subjects (@pxref{Fuzzy
6197 @item gnus-simplify-subject-fuzzy-regexp
6198 @vindex gnus-simplify-subject-fuzzy-regexp
6199 This can either be a regular expression or list of regular expressions
6200 that match strings that will be removed from subjects if fuzzy subject
6201 simplification is used.
6203 @item gnus-simplify-ignored-prefixes
6204 @vindex gnus-simplify-ignored-prefixes
6205 If you set @code{gnus-summary-gather-subject-limit} to something as low
6206 as 10, you might consider setting this variable to something sensible:
6208 @c Written by Michael Ernst <mernst@cs.rice.edu>
6210 (setq gnus-simplify-ignored-prefixes
6216 "wanted" "followup" "summary\\( of\\)?"
6217 "help" "query" "problem" "question"
6218 "answer" "reference" "announce"
6219 "How can I" "How to" "Comparison of"
6224 (mapconcat 'identity
6225 '("for" "for reference" "with" "about")
6227 "\\)?\\]?:?[ \t]*"))
6230 All words that match this regexp will be removed before comparing two
6233 @item gnus-simplify-subject-functions
6234 @vindex gnus-simplify-subject-functions
6235 If non-@code{nil}, this variable overrides
6236 @code{gnus-summary-gather-subject-limit}. This variable should be a
6237 list of functions to apply to the @code{Subject} string iteratively to
6238 arrive at the simplified version of the string.
6240 Useful functions to put in this list include:
6243 @item gnus-simplify-subject-re
6244 @findex gnus-simplify-subject-re
6245 Strip the leading @samp{Re:}.
6247 @item gnus-simplify-subject-fuzzy
6248 @findex gnus-simplify-subject-fuzzy
6251 @item gnus-simplify-whitespace
6252 @findex gnus-simplify-whitespace
6253 Remove excessive whitespace.
6256 You may also write your own functions, of course.
6259 @item gnus-summary-gather-exclude-subject
6260 @vindex gnus-summary-gather-exclude-subject
6261 Since loose thread gathering is done on subjects only, that might lead
6262 to many false hits, especially with certain common subjects like
6263 @samp{} and @samp{(none)}. To make the situation slightly better,
6264 you can use the regexp @code{gnus-summary-gather-exclude-subject} to say
6265 what subjects should be excluded from the gathering process.@*
6266 The default is @samp{^ *$\\|^(none)$}.
6268 @item gnus-summary-thread-gathering-function
6269 @vindex gnus-summary-thread-gathering-function
6270 Gnus gathers threads by looking at @code{Subject} headers. This means
6271 that totally unrelated articles may end up in the same ``thread'', which
6272 is confusing. An alternate approach is to look at all the
6273 @code{Message-ID}s in all the @code{References} headers to find matches.
6274 This will ensure that no gathered threads ever include unrelated
6275 articles, but it also means that people who have posted with broken
6276 newsreaders won't be gathered properly. The choice is yours---plague or
6280 @item gnus-gather-threads-by-subject
6281 @findex gnus-gather-threads-by-subject
6282 This function is the default gathering function and looks at
6283 @code{Subject}s exclusively.
6285 @item gnus-gather-threads-by-references
6286 @findex gnus-gather-threads-by-references
6287 This function looks at @code{References} headers exclusively.
6290 If you want to test gathering by @code{References}, you could say
6294 (setq gnus-summary-thread-gathering-function
6295 'gnus-gather-threads-by-references)
6301 @node Filling In Threads
6302 @subsubsection Filling In Threads
6305 @item gnus-fetch-old-headers
6306 @vindex gnus-fetch-old-headers
6307 If non-@code{nil}, Gnus will attempt to build old threads by fetching
6308 more old headers---headers to articles marked as read. If you
6309 would like to display as few summary lines as possible, but still
6310 connect as many loose threads as possible, you should set this variable
6311 to @code{some} or a number. If you set it to a number, no more than
6312 that number of extra old headers will be fetched. In either case,
6313 fetching old headers only works if the back end you are using carries
6314 overview files---this would normally be @code{nntp}, @code{nnspool} and
6315 @code{nnml}. Also remember that if the root of the thread has been
6316 expired by the server, there's not much Gnus can do about that.
6318 This variable can also be set to @code{invisible}. This won't have any
6319 visible effects, but is useful if you use the @kbd{A T} command a lot
6320 (@pxref{Finding the Parent}).
6322 @item gnus-build-sparse-threads
6323 @vindex gnus-build-sparse-threads
6324 Fetching old headers can be slow. A low-rent similar effect can be
6325 gotten by setting this variable to @code{some}. Gnus will then look at
6326 the complete @code{References} headers of all articles and try to string
6327 together articles that belong in the same thread. This will leave
6328 @dfn{gaps} in the threading display where Gnus guesses that an article
6329 is missing from the thread. (These gaps appear like normal summary
6330 lines. If you select a gap, Gnus will try to fetch the article in
6331 question.) If this variable is @code{t}, Gnus will display all these
6332 ``gaps'' without regard for whether they are useful for completing the
6333 thread or not. Finally, if this variable is @code{more}, Gnus won't cut
6334 off sparse leaf nodes that don't lead anywhere. This variable is
6335 @code{nil} by default.
6337 @item gnus-read-all-available-headers
6338 @vindex gnus-read-all-available-headers
6339 This is a rather obscure variable that few will find useful. It's
6340 intended for those non-news newsgroups where the back end has to fetch
6341 quite a lot to present the summary buffer, and where it's impossible to
6342 go back to parents of articles. This is mostly the case in the
6343 web-based groups, like the @code{nnultimate} groups.
6345 If you don't use those, then it's safe to leave this as the default
6346 @code{nil}. If you want to use this variable, it should be a regexp
6347 that matches the group name, or @code{t} for all groups.
6352 @node More Threading
6353 @subsubsection More Threading
6356 @item gnus-show-threads
6357 @vindex gnus-show-threads
6358 If this variable is @code{nil}, no threading will be done, and all of
6359 the rest of the variables here will have no effect. Turning threading
6360 off will speed group selection up a bit, but it is sure to make reading
6361 slower and more awkward.
6363 @item gnus-thread-hide-subtree
6364 @vindex gnus-thread-hide-subtree
6365 If non-@code{nil}, all threads will be hidden when the summary buffer is
6368 This can also be a predicate specifier (@pxref{Predicate Specifiers}).
6369 Avaliable predicates are @code{gnus-article-unread-p} and
6370 @code{gnus-article-unseen-p}).
6375 (setq gnus-thread-hide-subtree
6376 '(or gnus-article-unread-p
6377 gnus-article-unseen-p))
6380 (It's a pretty nonsensical example, since all unseen articles are also
6381 unread, but you get my drift.)
6384 @item gnus-thread-expunge-below
6385 @vindex gnus-thread-expunge-below
6386 All threads that have a total score (as defined by
6387 @code{gnus-thread-score-function}) less than this number will be
6388 expunged. This variable is @code{nil} by default, which means that no
6389 threads are expunged.
6391 @item gnus-thread-hide-killed
6392 @vindex gnus-thread-hide-killed
6393 if you kill a thread and this variable is non-@code{nil}, the subtree
6396 @item gnus-thread-ignore-subject
6397 @vindex gnus-thread-ignore-subject
6398 Sometimes somebody changes the subject in the middle of a thread. If
6399 this variable is non-@code{nil}, which is the default, the subject
6400 change is ignored. If it is @code{nil}, a change in the subject will
6401 result in a new thread.
6403 @item gnus-thread-indent-level
6404 @vindex gnus-thread-indent-level
6405 This is a number that says how much each sub-thread should be indented.
6408 @item gnus-sort-gathered-threads-function
6409 @vindex gnus-sort-gathered-threads-function
6410 Sometimes, particularly with mailing lists, the order in which mails
6411 arrive locally is not necessarily the same as the order in which they
6412 arrived on the mailing list. Consequently, when sorting sub-threads
6413 using the default @code{gnus-thread-sort-by-number}, responses can end
6414 up appearing before the article to which they are responding to.
6415 Setting this variable to an alternate value
6416 (e.g. @code{gnus-thread-sort-by-date}), in a group's parameters or in an
6417 appropriate hook (e.g. @code{gnus-summary-generate-hook}) can produce a
6418 more logical sub-thread ordering in such instances.
6423 @node Low-Level Threading
6424 @subsubsection Low-Level Threading
6428 @item gnus-parse-headers-hook
6429 @vindex gnus-parse-headers-hook
6430 Hook run before parsing any headers.
6432 @item gnus-alter-header-function
6433 @vindex gnus-alter-header-function
6434 If non-@code{nil}, this function will be called to allow alteration of
6435 article header structures. The function is called with one parameter,
6436 the article header vector, which it may alter in any way. For instance,
6437 if you have a mail-to-news gateway which alters the @code{Message-ID}s
6438 in systematic ways (by adding prefixes and such), you can use this
6439 variable to un-scramble the @code{Message-ID}s so that they are more
6440 meaningful. Here's one example:
6443 (setq gnus-alter-header-function 'my-alter-message-id)
6445 (defun my-alter-message-id (header)
6446 (let ((id (mail-header-id header)))
6448 "\\(<[^<>@@]*\\)\\.?cygnus\\..*@@\\([^<>@@]*>\\)" id)
6450 (concat (match-string 1 id) "@@" (match-string 2 id))
6457 @node Thread Commands
6458 @subsection Thread Commands
6459 @cindex thread commands
6465 @kindex T k (Summary)
6466 @kindex C-M-k (Summary)
6467 @findex gnus-summary-kill-thread
6468 Mark all articles in the current (sub-)thread as read
6469 (@code{gnus-summary-kill-thread}). If the prefix argument is positive,
6470 remove all marks instead. If the prefix argument is negative, tick
6475 @kindex T l (Summary)
6476 @kindex C-M-l (Summary)
6477 @findex gnus-summary-lower-thread
6478 Lower the score of the current (sub-)thread
6479 (@code{gnus-summary-lower-thread}).
6482 @kindex T i (Summary)
6483 @findex gnus-summary-raise-thread
6484 Increase the score of the current (sub-)thread
6485 (@code{gnus-summary-raise-thread}).
6488 @kindex T # (Summary)
6489 @findex gnus-uu-mark-thread
6490 Set the process mark on the current (sub-)thread
6491 (@code{gnus-uu-mark-thread}).
6494 @kindex T M-# (Summary)
6495 @findex gnus-uu-unmark-thread
6496 Remove the process mark from the current (sub-)thread
6497 (@code{gnus-uu-unmark-thread}).
6500 @kindex T T (Summary)
6501 @findex gnus-summary-toggle-threads
6502 Toggle threading (@code{gnus-summary-toggle-threads}).
6505 @kindex T s (Summary)
6506 @findex gnus-summary-show-thread
6507 Expose the (sub-)thread hidden under the current article, if any
6508 (@code{gnus-summary-show-thread}).
6511 @kindex T h (Summary)
6512 @findex gnus-summary-hide-thread
6513 Hide the current (sub-)thread (@code{gnus-summary-hide-thread}).
6516 @kindex T S (Summary)
6517 @findex gnus-summary-show-all-threads
6518 Expose all hidden threads (@code{gnus-summary-show-all-threads}).
6521 @kindex T H (Summary)
6522 @findex gnus-summary-hide-all-threads
6523 Hide all threads (@code{gnus-summary-hide-all-threads}).
6526 @kindex T t (Summary)
6527 @findex gnus-summary-rethread-current
6528 Re-thread the current article's thread
6529 (@code{gnus-summary-rethread-current}). This works even when the
6530 summary buffer is otherwise unthreaded.
6533 @kindex T ^ (Summary)
6534 @findex gnus-summary-reparent-thread
6535 Make the current article the child of the marked (or previous) article
6536 (@code{gnus-summary-reparent-thread}).
6540 The following commands are thread movement commands. They all
6541 understand the numeric prefix.
6546 @kindex T n (Summary)
6548 @kindex C-M-n (Summary)
6550 @kindex M-down (Summary)
6551 @findex gnus-summary-next-thread
6552 Go to the next thread (@code{gnus-summary-next-thread}).
6555 @kindex T p (Summary)
6557 @kindex C-M-p (Summary)
6559 @kindex M-up (Summary)
6560 @findex gnus-summary-prev-thread
6561 Go to the previous thread (@code{gnus-summary-prev-thread}).
6564 @kindex T d (Summary)
6565 @findex gnus-summary-down-thread
6566 Descend the thread (@code{gnus-summary-down-thread}).
6569 @kindex T u (Summary)
6570 @findex gnus-summary-up-thread
6571 Ascend the thread (@code{gnus-summary-up-thread}).
6574 @kindex T o (Summary)
6575 @findex gnus-summary-top-thread
6576 Go to the top of the thread (@code{gnus-summary-top-thread}).
6579 @vindex gnus-thread-operation-ignore-subject
6580 If you ignore subject while threading, you'll naturally end up with
6581 threads that have several different subjects in them. If you then issue
6582 a command like `T k' (@code{gnus-summary-kill-thread}) you might not
6583 wish to kill the entire thread, but just those parts of the thread that
6584 have the same subject as the current article. If you like this idea,
6585 you can fiddle with @code{gnus-thread-operation-ignore-subject}. If it
6586 is non-@code{nil} (which it is by default), subjects will be ignored
6587 when doing thread commands. If this variable is @code{nil}, articles in
6588 the same thread with different subjects will not be included in the
6589 operation in question. If this variable is @code{fuzzy}, only articles
6590 that have subjects fuzzily equal will be included (@pxref{Fuzzy
6594 @node Sorting the Summary Buffer
6595 @section Sorting the Summary Buffer
6597 @findex gnus-thread-sort-by-total-score
6598 @findex gnus-thread-sort-by-date
6599 @findex gnus-thread-sort-by-score
6600 @findex gnus-thread-sort-by-subject
6601 @findex gnus-thread-sort-by-author
6602 @findex gnus-thread-sort-by-number
6603 @vindex gnus-thread-sort-functions
6604 @findex gnus-thread-sort-by-most-recent-thread
6605 If you are using a threaded summary display, you can sort the threads by
6606 setting @code{gnus-thread-sort-functions}, which can be either a single
6607 function, a list of functions, or a list containing functions and
6608 @code{(not some-function)} elements.
6610 By default, sorting is done on article numbers. Ready-made sorting
6611 predicate functions include @code{gnus-thread-sort-by-number},
6612 @code{gnus-thread-sort-by-author}, @code{gnus-thread-sort-by-subject},
6613 @code{gnus-thread-sort-by-date}, @code{gnus-thread-sort-by-score},
6614 @code{gnus-thread-sort-by-most-recent-number},
6615 @code{gnus-thread-sort-by-most-recent-date} and
6616 @code{gnus-thread-sort-by-total-score}.
6618 Each function takes two threads and returns non-@code{nil} if the first
6619 thread should be sorted before the other. Note that sorting really is
6620 normally done by looking only at the roots of each thread.
6622 If you use more than one function, the primary sort key should be the
6623 last function in the list. You should probably always include
6624 @code{gnus-thread-sort-by-number} in the list of sorting
6625 functions---preferably first. This will ensure that threads that are
6626 equal with respect to the other sort criteria will be displayed in
6627 ascending article order.
6629 If you would like to sort by reverse score, then by subject, and finally
6630 by number, you could do something like:
6633 (setq gnus-thread-sort-functions
6634 '(gnus-thread-sort-by-number
6635 gnus-thread-sort-by-subject
6636 (not gnus-thread-sort-by-total-score)))
6639 The threads that have highest score will be displayed first in the
6640 summary buffer. When threads have the same score, they will be sorted
6641 alphabetically. The threads that have the same score and the same
6642 subject will be sorted by number, which is (normally) the sequence in
6643 which the articles arrived.
6645 If you want to sort by score and then reverse arrival order, you could
6649 (setq gnus-thread-sort-functions
6651 (not (gnus-thread-sort-by-number t1 t2)))
6652 gnus-thread-sort-by-score))
6655 @vindex gnus-thread-score-function
6656 The function in the @code{gnus-thread-score-function} variable (default
6657 @code{+}) is used for calculating the total score of a thread. Useful
6658 functions might be @code{max}, @code{min}, or squared means, or whatever
6661 @findex gnus-article-sort-functions
6662 @findex gnus-article-sort-by-date
6663 @findex gnus-article-sort-by-score
6664 @findex gnus-article-sort-by-subject
6665 @findex gnus-article-sort-by-author
6666 @findex gnus-article-sort-by-number
6667 If you are using an unthreaded display for some strange reason or other,
6668 you have to fiddle with the @code{gnus-article-sort-functions} variable.
6669 It is very similar to the @code{gnus-thread-sort-functions}, except that
6670 it uses slightly different functions for article comparison. Available
6671 sorting predicate functions are @code{gnus-article-sort-by-number},
6672 @code{gnus-article-sort-by-author}, @code{gnus-article-sort-by-subject},
6673 @code{gnus-article-sort-by-date}, and @code{gnus-article-sort-by-score}.
6675 If you want to sort an unthreaded summary display by subject, you could
6679 (setq gnus-article-sort-functions
6680 '(gnus-article-sort-by-number
6681 gnus-article-sort-by-subject))
6686 @node Asynchronous Fetching
6687 @section Asynchronous Article Fetching
6688 @cindex asynchronous article fetching
6689 @cindex article pre-fetch
6692 If you read your news from an @sc{nntp} server that's far away, the
6693 network latencies may make reading articles a chore. You have to wait
6694 for a while after pressing @kbd{n} to go to the next article before the
6695 article appears. Why can't Gnus just go ahead and fetch the article
6696 while you are reading the previous one? Why not, indeed.
6698 First, some caveats. There are some pitfalls to using asynchronous
6699 article fetching, especially the way Gnus does it.
6701 Let's say you are reading article 1, which is short, and article 2 is
6702 quite long, and you are not interested in reading that. Gnus does not
6703 know this, so it goes ahead and fetches article 2. You decide to read
6704 article 3, but since Gnus is in the process of fetching article 2, the
6705 connection is blocked.
6707 To avoid these situations, Gnus will open two (count 'em two)
6708 connections to the server. Some people may think this isn't a very nice
6709 thing to do, but I don't see any real alternatives. Setting up that
6710 extra connection takes some time, so Gnus startup will be slower.
6712 Gnus will fetch more articles than you will read. This will mean that
6713 the link between your machine and the @sc{nntp} server will become more
6714 loaded than if you didn't use article pre-fetch. The server itself will
6715 also become more loaded---both with the extra article requests, and the
6718 Ok, so now you know that you shouldn't really use this thing... unless
6721 @vindex gnus-asynchronous
6722 Here's how: Set @code{gnus-asynchronous} to @code{t}. The rest should
6723 happen automatically.
6725 @vindex gnus-use-article-prefetch
6726 You can control how many articles are to be pre-fetched by setting
6727 @code{gnus-use-article-prefetch}. This is 30 by default, which means
6728 that when you read an article in the group, the back end will pre-fetch
6729 the next 30 articles. If this variable is @code{t}, the back end will
6730 pre-fetch all the articles it can without bound. If it is
6731 @code{nil}, no pre-fetching will be done.
6733 @vindex gnus-async-prefetch-article-p
6734 @findex gnus-async-read-p
6735 There are probably some articles that you don't want to pre-fetch---read
6736 articles, for instance. The @code{gnus-async-prefetch-article-p} variable controls whether an article is to be pre-fetched. This function should
6737 return non-@code{nil} when the article in question is to be
6738 pre-fetched. The default is @code{gnus-async-read-p}, which returns
6739 @code{nil} on read articles. The function is called with an article
6740 data structure as the only parameter.
6742 If, for instance, you wish to pre-fetch only unread articles shorter than 100 lines, you could say something like:
6745 (defun my-async-short-unread-p (data)
6746 "Return non-nil for short, unread articles."
6747 (and (gnus-data-unread-p data)
6748 (< (mail-header-lines (gnus-data-header data))
6751 (setq gnus-async-prefetch-article-p 'my-async-short-unread-p)
6754 These functions will be called many, many times, so they should
6755 preferably be short and sweet to avoid slowing down Gnus too much.
6756 It's probably a good idea to byte-compile things like this.
6758 @vindex gnus-prefetched-article-deletion-strategy
6759 Articles have to be removed from the asynch buffer sooner or later. The
6760 @code{gnus-prefetched-article-deletion-strategy} says when to remove
6761 articles. This is a list that may contain the following elements:
6765 Remove articles when they are read.
6768 Remove articles when exiting the group.
6771 The default value is @code{(read exit)}.
6773 @c @vindex gnus-use-header-prefetch
6774 @c If @code{gnus-use-header-prefetch} is non-@code{nil}, prefetch articles
6775 @c from the next group.
6778 @node Article Caching
6779 @section Article Caching
6780 @cindex article caching
6783 If you have an @emph{extremely} slow @sc{nntp} connection, you may
6784 consider turning article caching on. Each article will then be stored
6785 locally under your home directory. As you may surmise, this could
6786 potentially use @emph{huge} amounts of disk space, as well as eat up all
6787 your inodes so fast it will make your head swim. In vodka.
6789 Used carefully, though, it could be just an easier way to save articles.
6791 @vindex gnus-use-long-file-name
6792 @vindex gnus-cache-directory
6793 @vindex gnus-use-cache
6794 To turn caching on, set @code{gnus-use-cache} to @code{t}. By default,
6795 all articles ticked or marked as dormant will then be copied
6796 over to your local cache (@code{gnus-cache-directory}). Whether this
6797 cache is flat or hierarchical is controlled by the
6798 @code{gnus-use-long-file-name} variable, as usual.
6800 When re-selecting a ticked or dormant article, it will be fetched from the
6801 cache instead of from the server. As articles in your cache will never
6802 expire, this might serve as a method of saving articles while still
6803 keeping them where they belong. Just mark all articles you want to save
6804 as dormant, and don't worry.
6806 When an article is marked as read, is it removed from the cache.
6808 @vindex gnus-cache-remove-articles
6809 @vindex gnus-cache-enter-articles
6810 The entering/removal of articles from the cache is controlled by the
6811 @code{gnus-cache-enter-articles} and @code{gnus-cache-remove-articles}
6812 variables. Both are lists of symbols. The first is @code{(ticked
6813 dormant)} by default, meaning that ticked and dormant articles will be
6814 put in the cache. The latter is @code{(read)} by default, meaning that
6815 articles marked as read are removed from the cache. Possibly
6816 symbols in these two lists are @code{ticked}, @code{dormant},
6817 @code{unread} and @code{read}.
6819 @findex gnus-jog-cache
6820 So where does the massive article-fetching and storing come into the
6821 picture? The @code{gnus-jog-cache} command will go through all
6822 subscribed newsgroups, request all unread articles, score them, and
6823 store them in the cache. You should only ever, ever ever ever, use this
6824 command if 1) your connection to the @sc{nntp} server is really, really,
6825 really slow and 2) you have a really, really, really huge disk.
6826 Seriously. One way to cut down on the number of articles downloaded is
6827 to score unwanted articles down and have them marked as read. They will
6828 not then be downloaded by this command.
6830 @vindex gnus-uncacheable-groups
6831 @vindex gnus-cacheable-groups
6832 It is likely that you do not want caching on all groups. For instance,
6833 if your @code{nnml} mail is located under your home directory, it makes no
6834 sense to cache it somewhere else under your home directory. Unless you
6835 feel that it's neat to use twice as much space.
6837 To limit the caching, you could set @code{gnus-cacheable-groups} to a
6838 regexp of groups to cache, @samp{^nntp} for instance, or set the
6839 @code{gnus-uncacheable-groups} regexp to @samp{^nnml}, for instance.
6840 Both variables are @code{nil} by default. If a group matches both
6841 variables, the group is not cached.
6843 @findex gnus-cache-generate-nov-databases
6844 @findex gnus-cache-generate-active
6845 @vindex gnus-cache-active-file
6846 The cache stores information on what articles it contains in its active
6847 file (@code{gnus-cache-active-file}). If this file (or any other parts
6848 of the cache) becomes all messed up for some reason or other, Gnus
6849 offers two functions that will try to set things right. @kbd{M-x
6850 gnus-cache-generate-nov-databases} will (re)build all the @sc{nov}
6851 files, and @kbd{gnus-cache-generate-active} will (re)generate the active
6854 @findex gnus-cache-move-cache
6855 @code{gnus-cache-move-cache} will move your whole
6856 @code{gnus-cache-directory} to some other location. You get asked to
6857 where, isn't that cool?
6859 @node Persistent Articles
6860 @section Persistent Articles
6861 @cindex persistent articles
6863 Closely related to article caching, we have @dfn{persistent articles}.
6864 In fact, it's just a different way of looking at caching, and much more
6865 useful in my opinion.
6867 Say you're reading a newsgroup, and you happen on to some valuable gem
6868 that you want to keep and treasure forever. You'd normally just save it
6869 (using one of the many saving commands) in some file. The problem with
6870 that is that it's just, well, yucky. Ideally you'd prefer just having
6871 the article remain in the group where you found it forever; untouched by
6872 the expiry going on at the news server.
6874 This is what a @dfn{persistent article} is---an article that just won't
6875 be deleted. It's implemented using the normal cache functions, but
6876 you use two explicit commands for managing persistent articles:
6882 @findex gnus-cache-enter-article
6883 Make the current article persistent (@code{gnus-cache-enter-article}).
6886 @kindex M-* (Summary)
6887 @findex gnus-cache-remove-article
6888 Remove the current article from the persistent articles
6889 (@code{gnus-cache-remove-article}). This will normally delete the
6893 Both these commands understand the process/prefix convention.
6895 To avoid having all ticked articles (and stuff) entered into the cache,
6896 you should set @code{gnus-use-cache} to @code{passive} if you're just
6897 interested in persistent articles:
6900 (setq gnus-use-cache 'passive)
6904 @node Article Backlog
6905 @section Article Backlog
6907 @cindex article backlog
6909 If you have a slow connection, but the idea of using caching seems
6910 unappealing to you (and it is, really), you can help the situation some
6911 by switching on the @dfn{backlog}. This is where Gnus will buffer
6912 already read articles so that it doesn't have to re-fetch articles
6913 you've already read. This only helps if you are in the habit of
6914 re-selecting articles you've recently read, of course. If you never do
6915 that, turning the backlog on will slow Gnus down a little bit, and
6916 increase memory usage some.
6918 @vindex gnus-keep-backlog
6919 If you set @code{gnus-keep-backlog} to a number @var{n}, Gnus will store
6920 at most @var{n} old articles in a buffer for later re-fetching. If this
6921 variable is non-@code{nil} and is not a number, Gnus will store
6922 @emph{all} read articles, which means that your Emacs will grow without
6923 bound before exploding and taking your machine down with you. I put
6924 that in there just to keep y'all on your toes.
6926 This variable is @code{nil} by default.
6929 @node Saving Articles
6930 @section Saving Articles
6931 @cindex saving articles
6933 Gnus can save articles in a number of ways. Below is the documentation
6934 for saving articles in a fairly straight-forward fashion (i.e., little
6935 processing of the article is done before it is saved). For a different
6936 approach (uudecoding, unsharing) you should use @code{gnus-uu}
6937 (@pxref{Decoding Articles}).
6939 @vindex gnus-save-all-headers
6940 If @code{gnus-save-all-headers} is non-@code{nil}, Gnus will not delete
6941 unwanted headers before saving the article.
6943 @vindex gnus-saved-headers
6944 If the preceding variable is @code{nil}, all headers that match the
6945 @code{gnus-saved-headers} regexp will be kept, while the rest will be
6946 deleted before saving.
6952 @kindex O o (Summary)
6954 @findex gnus-summary-save-article
6955 @c @icon{gnus-summary-save-article}
6956 Save the current article using the default article saver
6957 (@code{gnus-summary-save-article}).
6960 @kindex O m (Summary)
6961 @findex gnus-summary-save-article-mail
6962 Save the current article in mail format
6963 (@code{gnus-summary-save-article-mail}).
6966 @kindex O r (Summary)
6967 @findex gnus-summary-save-article-rmail
6968 Save the current article in rmail format
6969 (@code{gnus-summary-save-article-rmail}).
6972 @kindex O f (Summary)
6973 @findex gnus-summary-save-article-file
6974 @c @icon{gnus-summary-save-article-file}
6975 Save the current article in plain file format
6976 (@code{gnus-summary-save-article-file}).
6979 @kindex O F (Summary)
6980 @findex gnus-summary-write-article-file
6981 Write the current article in plain file format, overwriting any previous
6982 file contents (@code{gnus-summary-write-article-file}).
6985 @kindex O b (Summary)
6986 @findex gnus-summary-save-article-body-file
6987 Save the current article body in plain file format
6988 (@code{gnus-summary-save-article-body-file}).
6991 @kindex O h (Summary)
6992 @findex gnus-summary-save-article-folder
6993 Save the current article in mh folder format
6994 (@code{gnus-summary-save-article-folder}).
6997 @kindex O v (Summary)
6998 @findex gnus-summary-save-article-vm
6999 Save the current article in a VM folder
7000 (@code{gnus-summary-save-article-vm}).
7004 @kindex O p (Summary)
7006 @findex gnus-summary-pipe-output
7007 Save the current article in a pipe. Uhm, like, what I mean is---Pipe
7008 the current article to a process (@code{gnus-summary-pipe-output}).
7011 @kindex O P (Summary)
7012 @findex gnus-summary-muttprint
7013 @vindex gnus-summary-muttprint-program
7014 Save the current article into muttprint. That is, print it using the
7015 external program Muttprint (see
7016 @uref{http://muttprint.sourceforge.net/}). The program name and
7017 options to use is controlled by the variable
7018 @code{gnus-summary-muttprint-program}. (@code{gnus-summary-muttprint}).
7022 @vindex gnus-prompt-before-saving
7023 All these commands use the process/prefix convention
7024 (@pxref{Process/Prefix}). If you save bunches of articles using these
7025 functions, you might get tired of being prompted for files to save each
7026 and every article in. The prompting action is controlled by
7027 the @code{gnus-prompt-before-saving} variable, which is @code{always} by
7028 default, giving you that excessive prompting action you know and
7029 loathe. If you set this variable to @code{t} instead, you'll be prompted
7030 just once for each series of articles you save. If you like to really
7031 have Gnus do all your thinking for you, you can even set this variable
7032 to @code{nil}, which means that you will never be prompted for files to
7033 save articles in. Gnus will simply save all the articles in the default
7037 @vindex gnus-default-article-saver
7038 You can customize the @code{gnus-default-article-saver} variable to make
7039 Gnus do what you want it to. You can use any of the six ready-made
7040 functions below, or you can create your own.
7044 @item gnus-summary-save-in-rmail
7045 @findex gnus-summary-save-in-rmail
7046 @vindex gnus-rmail-save-name
7047 @findex gnus-plain-save-name
7048 This is the default format, @dfn{babyl}. Uses the function in the
7049 @code{gnus-rmail-save-name} variable to get a file name to save the
7050 article in. The default is @code{gnus-plain-save-name}.
7052 @item gnus-summary-save-in-mail
7053 @findex gnus-summary-save-in-mail
7054 @vindex gnus-mail-save-name
7055 Save in a Unix mail (mbox) file. Uses the function in the
7056 @code{gnus-mail-save-name} variable to get a file name to save the
7057 article in. The default is @code{gnus-plain-save-name}.
7059 @item gnus-summary-save-in-file
7060 @findex gnus-summary-save-in-file
7061 @vindex gnus-file-save-name
7062 @findex gnus-numeric-save-name
7063 Append the article straight to an ordinary file. Uses the function in
7064 the @code{gnus-file-save-name} variable to get a file name to save the
7065 article in. The default is @code{gnus-numeric-save-name}.
7067 @item gnus-summary-write-to-file
7068 @findex gnus-summary-write-to-file
7069 Write the article straight to an ordinary file. The file is
7070 overwritten if it exists. Uses the function in the
7071 @code{gnus-file-save-name} variable to get a file name to save the
7072 article in. The default is @code{gnus-numeric-save-name}.
7074 @item gnus-summary-save-body-in-file
7075 @findex gnus-summary-save-body-in-file
7076 Append the article body to an ordinary file. Uses the function in the
7077 @code{gnus-file-save-name} variable to get a file name to save the
7078 article in. The default is @code{gnus-numeric-save-name}.
7080 @item gnus-summary-save-in-folder
7081 @findex gnus-summary-save-in-folder
7082 @findex gnus-folder-save-name
7083 @findex gnus-Folder-save-name
7084 @vindex gnus-folder-save-name
7087 Save the article to an MH folder using @code{rcvstore} from the MH
7088 library. Uses the function in the @code{gnus-folder-save-name} variable
7089 to get a file name to save the article in. The default is
7090 @code{gnus-folder-save-name}, but you can also use
7091 @code{gnus-Folder-save-name}, which creates capitalized names.
7093 @item gnus-summary-save-in-vm
7094 @findex gnus-summary-save-in-vm
7095 Save the article in a VM folder. You have to have the VM mail
7096 reader to use this setting.
7099 @vindex gnus-article-save-directory
7100 All of these functions, except for the last one, will save the article
7101 in the @code{gnus-article-save-directory}, which is initialized from the
7102 @code{SAVEDIR} environment variable. This is @file{~/News/} by
7105 As you can see above, the functions use different functions to find a
7106 suitable name of a file to save the article in. Below is a list of
7107 available functions that generate names:
7111 @item gnus-Numeric-save-name
7112 @findex gnus-Numeric-save-name
7113 File names like @file{~/News/Alt.andrea-dworkin/45}.
7115 @item gnus-numeric-save-name
7116 @findex gnus-numeric-save-name
7117 File names like @file{~/News/alt.andrea-dworkin/45}.
7119 @item gnus-Plain-save-name
7120 @findex gnus-Plain-save-name
7121 File names like @file{~/News/Alt.andrea-dworkin}.
7123 @item gnus-plain-save-name
7124 @findex gnus-plain-save-name
7125 File names like @file{~/News/alt.andrea-dworkin}.
7127 @item gnus-sender-save-name
7128 @findex gnus-sender-save-name
7129 File names like @file{~/News/larsi}.
7132 @vindex gnus-split-methods
7133 You can have Gnus suggest where to save articles by plonking a regexp into
7134 the @code{gnus-split-methods} alist. For instance, if you would like to
7135 save articles related to Gnus in the file @file{gnus-stuff}, and articles
7136 related to VM in @code{vm-stuff}, you could set this variable to something
7140 (("^Subject:.*gnus\\|^Newsgroups:.*gnus" "gnus-stuff")
7141 ("^Subject:.*vm\\|^Xref:.*vm" "vm-stuff")
7142 (my-choosing-function "../other-dir/my-stuff")
7143 ((equal gnus-newsgroup-name "mail.misc") "mail-stuff"))
7146 We see that this is a list where each element is a list that has two
7147 elements---the @dfn{match} and the @dfn{file}. The match can either be
7148 a string (in which case it is used as a regexp to match on the article
7149 head); it can be a symbol (which will be called as a function with the
7150 group name as a parameter); or it can be a list (which will be
7151 @code{eval}ed). If any of these actions have a non-@code{nil} result,
7152 the @dfn{file} will be used as a default prompt. In addition, the
7153 result of the operation itself will be used if the function or form
7154 called returns a string or a list of strings.
7156 You basically end up with a list of file names that might be used when
7157 saving the current article. (All ``matches'' will be used.) You will
7158 then be prompted for what you really want to use as a name, with file
7159 name completion over the results from applying this variable.
7161 This variable is @code{((gnus-article-archive-name))} by default, which
7162 means that Gnus will look at the articles it saves for an
7163 @code{Archive-name} line and use that as a suggestion for the file
7166 Here's an example function to clean up file names somewhat. If you have
7167 lots of mail groups called things like
7168 @samp{nnml:mail.whatever}, you may want to chop off the beginning of
7169 these group names before creating the file name to save to. The
7170 following will do just that:
7173 (defun my-save-name (group)
7174 (when (string-match "^nnml:mail." group)
7175 (substring group (match-end 0))))
7177 (setq gnus-split-methods
7178 '((gnus-article-archive-name)
7183 @vindex gnus-use-long-file-name
7184 Finally, you have the @code{gnus-use-long-file-name} variable. If it is
7185 @code{nil}, all the preceding functions will replace all periods
7186 (@samp{.}) in the group names with slashes (@samp{/})---which means that
7187 the functions will generate hierarchies of directories instead of having
7188 all the files in the top level directory
7189 (@file{~/News/alt/andrea-dworkin} instead of
7190 @file{~/News/alt.andrea-dworkin}.) This variable is @code{t} by default
7191 on most systems. However, for historical reasons, this is @code{nil} on
7192 Xenix and usg-unix-v machines by default.
7194 This function also affects kill and score file names. If this variable
7195 is a list, and the list contains the element @code{not-score}, long file
7196 names will not be used for score files, if it contains the element
7197 @code{not-save}, long file names will not be used for saving, and if it
7198 contains the element @code{not-kill}, long file names will not be used
7201 If you'd like to save articles in a hierarchy that looks something like
7205 (setq gnus-use-long-file-name '(not-save)) ; to get a hierarchy
7206 (setq gnus-default-article-saver
7207 'gnus-summary-save-in-file) ; no encoding
7210 Then just save with @kbd{o}. You'd then read this hierarchy with
7211 ephemeral @code{nneething} groups---@kbd{G D} in the group buffer, and
7212 the top level directory as the argument (@file{~/News/}). Then just walk
7213 around to the groups/directories with @code{nneething}.
7216 @node Decoding Articles
7217 @section Decoding Articles
7218 @cindex decoding articles
7220 Sometime users post articles (or series of articles) that have been
7221 encoded in some way or other. Gnus can decode them for you.
7224 * Uuencoded Articles:: Uudecode articles.
7225 * Shell Archives:: Unshar articles.
7226 * PostScript Files:: Split PostScript.
7227 * Other Files:: Plain save and binhex.
7228 * Decoding Variables:: Variables for a happy decoding.
7229 * Viewing Files:: You want to look at the result of the decoding?
7233 @cindex article series
7234 All these functions use the process/prefix convention
7235 (@pxref{Process/Prefix}) for finding out what articles to work on, with
7236 the extension that a ``single article'' means ``a single series''. Gnus
7237 can find out by itself what articles belong to a series, decode all the
7238 articles and unpack/view/save the resulting file(s).
7240 Gnus guesses what articles are in the series according to the following
7241 simplish rule: The subjects must be (nearly) identical, except for the
7242 last two numbers of the line. (Spaces are largely ignored, however.)
7244 For example: If you choose a subject called @samp{cat.gif (2/3)}, Gnus
7245 will find all the articles that match the regexp @samp{^cat.gif
7246 ([0-9]+/[0-9]+).*$}.
7248 Subjects that are non-standard, like @samp{cat.gif (2/3) Part 6 of a
7249 series}, will not be properly recognized by any of the automatic viewing
7250 commands, and you have to mark the articles manually with @kbd{#}.
7253 @node Uuencoded Articles
7254 @subsection Uuencoded Articles
7256 @cindex uuencoded articles
7261 @kindex X u (Summary)
7262 @findex gnus-uu-decode-uu
7263 @c @icon{gnus-uu-decode-uu}
7264 Uudecodes the current series (@code{gnus-uu-decode-uu}).
7267 @kindex X U (Summary)
7268 @findex gnus-uu-decode-uu-and-save
7269 Uudecodes and saves the current series
7270 (@code{gnus-uu-decode-uu-and-save}).
7273 @kindex X v u (Summary)
7274 @findex gnus-uu-decode-uu-view
7275 Uudecodes and views the current series (@code{gnus-uu-decode-uu-view}).
7278 @kindex X v U (Summary)
7279 @findex gnus-uu-decode-uu-and-save-view
7280 Uudecodes, views and saves the current series
7281 (@code{gnus-uu-decode-uu-and-save-view}).
7285 Remember that these all react to the presence of articles marked with
7286 the process mark. If, for instance, you'd like to decode and save an
7287 entire newsgroup, you'd typically do @kbd{M P a}
7288 (@code{gnus-uu-mark-all}) and then @kbd{X U}
7289 (@code{gnus-uu-decode-uu-and-save}).
7291 All this is very much different from how @code{gnus-uu} worked with
7292 @sc{gnus 4.1}, where you had explicit keystrokes for everything under
7293 the sun. This version of @code{gnus-uu} generally assumes that you mark
7294 articles in some way (@pxref{Setting Process Marks}) and then press
7297 @vindex gnus-uu-notify-files
7298 Note: When trying to decode articles that have names matching
7299 @code{gnus-uu-notify-files}, which is hard-coded to
7300 @samp{[Cc][Ii][Nn][Dd][Yy][0-9]+.\\(gif\\|jpg\\)}, @code{gnus-uu} will
7301 automatically post an article on @samp{comp.unix.wizards} saying that
7302 you have just viewed the file in question. This feature can't be turned
7306 @node Shell Archives
7307 @subsection Shell Archives
7309 @cindex shell archives
7310 @cindex shared articles
7312 Shell archives (``shar files'') used to be a popular way to distribute
7313 sources, but it isn't used all that much today. In any case, we have
7314 some commands to deal with these:
7319 @kindex X s (Summary)
7320 @findex gnus-uu-decode-unshar
7321 Unshars the current series (@code{gnus-uu-decode-unshar}).
7324 @kindex X S (Summary)
7325 @findex gnus-uu-decode-unshar-and-save
7326 Unshars and saves the current series (@code{gnus-uu-decode-unshar-and-save}).
7329 @kindex X v s (Summary)
7330 @findex gnus-uu-decode-unshar-view
7331 Unshars and views the current series (@code{gnus-uu-decode-unshar-view}).
7334 @kindex X v S (Summary)
7335 @findex gnus-uu-decode-unshar-and-save-view
7336 Unshars, views and saves the current series
7337 (@code{gnus-uu-decode-unshar-and-save-view}).
7341 @node PostScript Files
7342 @subsection PostScript Files
7348 @kindex X p (Summary)
7349 @findex gnus-uu-decode-postscript
7350 Unpack the current PostScript series (@code{gnus-uu-decode-postscript}).
7353 @kindex X P (Summary)
7354 @findex gnus-uu-decode-postscript-and-save
7355 Unpack and save the current PostScript series
7356 (@code{gnus-uu-decode-postscript-and-save}).
7359 @kindex X v p (Summary)
7360 @findex gnus-uu-decode-postscript-view
7361 View the current PostScript series
7362 (@code{gnus-uu-decode-postscript-view}).
7365 @kindex X v P (Summary)
7366 @findex gnus-uu-decode-postscript-and-save-view
7367 View and save the current PostScript series
7368 (@code{gnus-uu-decode-postscript-and-save-view}).
7373 @subsection Other Files
7377 @kindex X o (Summary)
7378 @findex gnus-uu-decode-save
7379 Save the current series
7380 (@code{gnus-uu-decode-save}).
7383 @kindex X b (Summary)
7384 @findex gnus-uu-decode-binhex
7385 Unbinhex the current series (@code{gnus-uu-decode-binhex}). This
7386 doesn't really work yet.
7390 @node Decoding Variables
7391 @subsection Decoding Variables
7393 Adjective, not verb.
7396 * Rule Variables:: Variables that say how a file is to be viewed.
7397 * Other Decode Variables:: Other decode variables.
7398 * Uuencoding and Posting:: Variables for customizing uuencoding.
7402 @node Rule Variables
7403 @subsubsection Rule Variables
7404 @cindex rule variables
7406 Gnus uses @dfn{rule variables} to decide how to view a file. All these
7407 variables are of the form
7410 (list '(regexp1 command2)
7417 @item gnus-uu-user-view-rules
7418 @vindex gnus-uu-user-view-rules
7420 This variable is consulted first when viewing files. If you wish to use,
7421 for instance, @code{sox} to convert an @samp{.au} sound file, you could
7424 (setq gnus-uu-user-view-rules
7425 (list '("\\\\.au$" "sox %s -t .aiff > /dev/audio")))
7428 @item gnus-uu-user-view-rules-end
7429 @vindex gnus-uu-user-view-rules-end
7430 This variable is consulted if Gnus couldn't make any matches from the
7431 user and default view rules.
7433 @item gnus-uu-user-archive-rules
7434 @vindex gnus-uu-user-archive-rules
7435 This variable can be used to say what commands should be used to unpack
7440 @node Other Decode Variables
7441 @subsubsection Other Decode Variables
7444 @vindex gnus-uu-grabbed-file-functions
7446 @item gnus-uu-grabbed-file-functions
7447 All functions in this list will be called right after each file has been
7448 successfully decoded---so that you can move or view files right away,
7449 and don't have to wait for all files to be decoded before you can do
7450 anything. Ready-made functions you can put in this list are:
7454 @item gnus-uu-grab-view
7455 @findex gnus-uu-grab-view
7458 @item gnus-uu-grab-move
7459 @findex gnus-uu-grab-move
7460 Move the file (if you're using a saving function.)
7463 @item gnus-uu-be-dangerous
7464 @vindex gnus-uu-be-dangerous
7465 Specifies what to do if unusual situations arise during decoding. If
7466 @code{nil}, be as conservative as possible. If @code{t}, ignore things
7467 that didn't work, and overwrite existing files. Otherwise, ask each
7470 @item gnus-uu-ignore-files-by-name
7471 @vindex gnus-uu-ignore-files-by-name
7472 Files with name matching this regular expression won't be viewed.
7474 @item gnus-uu-ignore-files-by-type
7475 @vindex gnus-uu-ignore-files-by-type
7476 Files with a @sc{mime} type matching this variable won't be viewed.
7477 Note that Gnus tries to guess what type the file is based on the name.
7478 @code{gnus-uu} is not a @sc{mime} package (yet), so this is slightly
7481 @item gnus-uu-tmp-dir
7482 @vindex gnus-uu-tmp-dir
7483 Where @code{gnus-uu} does its work.
7485 @item gnus-uu-do-not-unpack-archives
7486 @vindex gnus-uu-do-not-unpack-archives
7487 Non-@code{nil} means that @code{gnus-uu} won't peek inside archives
7488 looking for files to display.
7490 @item gnus-uu-view-and-save
7491 @vindex gnus-uu-view-and-save
7492 Non-@code{nil} means that the user will always be asked to save a file
7495 @item gnus-uu-ignore-default-view-rules
7496 @vindex gnus-uu-ignore-default-view-rules
7497 Non-@code{nil} means that @code{gnus-uu} will ignore the default viewing
7500 @item gnus-uu-ignore-default-archive-rules
7501 @vindex gnus-uu-ignore-default-archive-rules
7502 Non-@code{nil} means that @code{gnus-uu} will ignore the default archive
7505 @item gnus-uu-kill-carriage-return
7506 @vindex gnus-uu-kill-carriage-return
7507 Non-@code{nil} means that @code{gnus-uu} will strip all carriage returns
7510 @item gnus-uu-unmark-articles-not-decoded
7511 @vindex gnus-uu-unmark-articles-not-decoded
7512 Non-@code{nil} means that @code{gnus-uu} will mark unsuccessfully
7513 decoded articles as unread.
7515 @item gnus-uu-correct-stripped-uucode
7516 @vindex gnus-uu-correct-stripped-uucode
7517 Non-@code{nil} means that @code{gnus-uu} will @emph{try} to fix
7518 uuencoded files that have had trailing spaces deleted.
7520 @item gnus-uu-pre-uudecode-hook
7521 @vindex gnus-uu-pre-uudecode-hook
7522 Hook run before sending a message to @code{uudecode}.
7524 @item gnus-uu-view-with-metamail
7525 @vindex gnus-uu-view-with-metamail
7527 Non-@code{nil} means that @code{gnus-uu} will ignore the viewing
7528 commands defined by the rule variables and just fudge a @sc{mime}
7529 content type based on the file name. The result will be fed to
7530 @code{metamail} for viewing.
7532 @item gnus-uu-save-in-digest
7533 @vindex gnus-uu-save-in-digest
7534 Non-@code{nil} means that @code{gnus-uu}, when asked to save without
7535 decoding, will save in digests. If this variable is @code{nil},
7536 @code{gnus-uu} will just save everything in a file without any
7537 embellishments. The digesting almost conforms to RFC 1153---no easy way
7538 to specify any meaningful volume and issue numbers were found, so I
7539 simply dropped them.
7544 @node Uuencoding and Posting
7545 @subsubsection Uuencoding and Posting
7549 @item gnus-uu-post-include-before-composing
7550 @vindex gnus-uu-post-include-before-composing
7551 Non-@code{nil} means that @code{gnus-uu} will ask for a file to encode
7552 before you compose the article. If this variable is @code{t}, you can
7553 either include an encoded file with @kbd{C-c C-i} or have one included
7554 for you when you post the article.
7556 @item gnus-uu-post-length
7557 @vindex gnus-uu-post-length
7558 Maximum length of an article. The encoded file will be split into how
7559 many articles it takes to post the entire file.
7561 @item gnus-uu-post-threaded
7562 @vindex gnus-uu-post-threaded
7563 Non-@code{nil} means that @code{gnus-uu} will post the encoded file in a
7564 thread. This may not be smart, as no other decoder I have seen is able
7565 to follow threads when collecting uuencoded articles. (Well, I have
7566 seen one package that does that---@code{gnus-uu}, but somehow, I don't
7567 think that counts...) Default is @code{nil}.
7569 @item gnus-uu-post-separate-description
7570 @vindex gnus-uu-post-separate-description
7571 Non-@code{nil} means that the description will be posted in a separate
7572 article. The first article will typically be numbered (0/x). If this
7573 variable is @code{nil}, the description the user enters will be included
7574 at the beginning of the first article, which will be numbered (1/x).
7575 Default is @code{t}.
7581 @subsection Viewing Files
7582 @cindex viewing files
7583 @cindex pseudo-articles
7585 After decoding, if the file is some sort of archive, Gnus will attempt
7586 to unpack the archive and see if any of the files in the archive can be
7587 viewed. For instance, if you have a gzipped tar file @file{pics.tar.gz}
7588 containing the files @file{pic1.jpg} and @file{pic2.gif}, Gnus will
7589 uncompress and de-tar the main file, and then view the two pictures.
7590 This unpacking process is recursive, so if the archive contains archives
7591 of archives, it'll all be unpacked.
7593 Finally, Gnus will normally insert a @dfn{pseudo-article} for each
7594 extracted file into the summary buffer. If you go to these
7595 ``articles'', you will be prompted for a command to run (usually Gnus
7596 will make a suggestion), and then the command will be run.
7598 @vindex gnus-view-pseudo-asynchronously
7599 If @code{gnus-view-pseudo-asynchronously} is @code{nil}, Emacs will wait
7600 until the viewing is done before proceeding.
7602 @vindex gnus-view-pseudos
7603 If @code{gnus-view-pseudos} is @code{automatic}, Gnus will not insert
7604 the pseudo-articles into the summary buffer, but view them
7605 immediately. If this variable is @code{not-confirm}, the user won't even
7606 be asked for a confirmation before viewing is done.
7608 @vindex gnus-view-pseudos-separately
7609 If @code{gnus-view-pseudos-separately} is non-@code{nil}, one
7610 pseudo-article will be created for each file to be viewed. If
7611 @code{nil}, all files that use the same viewing command will be given as
7612 a list of parameters to that command.
7614 @vindex gnus-insert-pseudo-articles
7615 If @code{gnus-insert-pseudo-articles} is non-@code{nil}, insert
7616 pseudo-articles when decoding. It is @code{t} by default.
7618 So; there you are, reading your @emph{pseudo-articles} in your
7619 @emph{virtual newsgroup} from the @emph{virtual server}; and you think:
7620 Why isn't anything real anymore? How did we get here?
7623 @node Article Treatment
7624 @section Article Treatment
7626 Reading through this huge manual, you may have quite forgotten that the
7627 object of newsreaders is to actually, like, read what people have
7628 written. Reading articles. Unfortunately, people are quite bad at
7629 writing, so there are tons of functions and variables to make reading
7630 these articles easier.
7633 * Article Highlighting:: You want to make the article look like fruit salad.
7634 * Article Fontisizing:: Making emphasized text look nice.
7635 * Article Hiding:: You also want to make certain info go away.
7636 * Article Washing:: Lots of way-neat functions to make life better.
7637 * Article Header:: Doing various header transformations.
7638 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
7639 * Article Date:: Grumble, UT!
7640 * Article Display:: Display various stuff---X-Face, Picons, Smileys
7641 * Article Signature:: What is a signature?
7642 * Article Miscellania:: Various other stuff.
7646 @node Article Highlighting
7647 @subsection Article Highlighting
7648 @cindex highlighting
7650 Not only do you want your article buffer to look like fruit salad, but
7651 you want it to look like technicolor fruit salad.
7656 @kindex W H a (Summary)
7657 @findex gnus-article-highlight
7658 @findex gnus-article-maybe-highlight
7659 Do much highlighting of the current article
7660 (@code{gnus-article-highlight}). This function highlights header, cited
7661 text, the signature, and adds buttons to the body and the head.
7664 @kindex W H h (Summary)
7665 @findex gnus-article-highlight-headers
7666 @vindex gnus-header-face-alist
7667 Highlight the headers (@code{gnus-article-highlight-headers}). The
7668 highlighting will be done according to the @code{gnus-header-face-alist}
7669 variable, which is a list where each element has the form
7670 @code{(@var{regexp} @var{name} @var{content})}.
7671 @var{regexp} is a regular expression for matching the
7672 header, @var{name} is the face used for highlighting the header name
7673 (@pxref{Faces and Fonts}) and @var{content} is the face for highlighting
7674 the header value. The first match made will be used. Note that
7675 @var{regexp} shouldn't have @samp{^} prepended---Gnus will add one.
7678 @kindex W H c (Summary)
7679 @findex gnus-article-highlight-citation
7680 Highlight cited text (@code{gnus-article-highlight-citation}).
7682 Some variables to customize the citation highlights:
7685 @vindex gnus-cite-parse-max-size
7687 @item gnus-cite-parse-max-size
7688 If the article size if bigger than this variable (which is 25000 by
7689 default), no citation highlighting will be performed.
7691 @item gnus-cite-max-prefix
7692 @vindex gnus-cite-max-prefix
7693 Maximum possible length for a citation prefix (default 20).
7695 @item gnus-cite-face-list
7696 @vindex gnus-cite-face-list
7697 List of faces used for highlighting citations (@pxref{Faces and Fonts}).
7698 When there are citations from multiple articles in the same message,
7699 Gnus will try to give each citation from each article its own face.
7700 This should make it easier to see who wrote what.
7702 @item gnus-supercite-regexp
7703 @vindex gnus-supercite-regexp
7704 Regexp matching normal Supercite attribution lines.
7706 @item gnus-supercite-secondary-regexp
7707 @vindex gnus-supercite-secondary-regexp
7708 Regexp matching mangled Supercite attribution lines.
7710 @item gnus-cite-minimum-match-count
7711 @vindex gnus-cite-minimum-match-count
7712 Minimum number of identical prefixes we have to see before we believe
7713 that it's a citation.
7715 @item gnus-cite-attribution-prefix
7716 @vindex gnus-cite-attribution-prefix
7717 Regexp matching the beginning of an attribution line.
7719 @item gnus-cite-attribution-suffix
7720 @vindex gnus-cite-attribution-suffix
7721 Regexp matching the end of an attribution line.
7723 @item gnus-cite-attribution-face
7724 @vindex gnus-cite-attribution-face
7725 Face used for attribution lines. It is merged with the face for the
7726 cited text belonging to the attribution.
7732 @kindex W H s (Summary)
7733 @vindex gnus-signature-separator
7734 @vindex gnus-signature-face
7735 @findex gnus-article-highlight-signature
7736 Highlight the signature (@code{gnus-article-highlight-signature}).
7737 Everything after @code{gnus-signature-separator} (@pxref{Article
7738 Signature}) in an article will be considered a signature and will be
7739 highlighted with @code{gnus-signature-face}, which is @code{italic} by
7744 @xref{Customizing Articles}, for how to highlight articles automatically.
7747 @node Article Fontisizing
7748 @subsection Article Fontisizing
7750 @cindex article emphasis
7752 @findex gnus-article-emphasize
7753 @kindex W e (Summary)
7754 People commonly add emphasis to words in news articles by writing things
7755 like @samp{_this_} or @samp{*this*} or @samp{/this/}. Gnus can make
7756 this look nicer by running the article through the @kbd{W e}
7757 (@code{gnus-article-emphasize}) command.
7759 @vindex gnus-emphasis-alist
7760 How the emphasis is computed is controlled by the
7761 @code{gnus-emphasis-alist} variable. This is an alist where the first
7762 element is a regular expression to be matched. The second is a number
7763 that says what regular expression grouping is used to find the entire
7764 emphasized word. The third is a number that says what regexp grouping
7765 should be displayed and highlighted. (The text between these two
7766 groupings will be hidden.) The fourth is the face used for
7770 (setq gnus-emphasis-alist
7771 '(("_\\(\\w+\\)_" 0 1 gnus-emphasis-underline)
7772 ("\\*\\(\\w+\\)\\*" 0 1 gnus-emphasis-bold)))
7781 @vindex gnus-emphasis-underline
7782 @vindex gnus-emphasis-bold
7783 @vindex gnus-emphasis-italic
7784 @vindex gnus-emphasis-underline-bold
7785 @vindex gnus-emphasis-underline-italic
7786 @vindex gnus-emphasis-bold-italic
7787 @vindex gnus-emphasis-underline-bold-italic
7788 By default, there are seven rules, and they use the following faces:
7789 @code{gnus-emphasis-bold}, @code{gnus-emphasis-italic},
7790 @code{gnus-emphasis-underline}, @code{gnus-emphasis-bold-italic},
7791 @code{gnus-emphasis-underline-italic},
7792 @code{gnus-emphasis-underline-bold}, and
7793 @code{gnus-emphasis-underline-bold-italic}.
7795 If you want to change these faces, you can either use @kbd{M-x
7796 customize}, or you can use @code{copy-face}. For instance, if you want
7797 to make @code{gnus-emphasis-italic} use a red face instead, you could
7801 (copy-face 'red 'gnus-emphasis-italic)
7804 @vindex gnus-group-highlight-words-alist
7806 If you want to highlight arbitrary words, you can use the
7807 @code{gnus-group-highlight-words-alist} variable, which uses the same
7808 syntax as @code{gnus-emphasis-alist}. The @code{highlight-words} group
7809 parameter (@pxref{Group Parameters}) can also be used.
7811 @xref{Customizing Articles}, for how to fontize articles automatically.
7814 @node Article Hiding
7815 @subsection Article Hiding
7816 @cindex article hiding
7818 Or rather, hiding certain things in each article. There usually is much
7819 too much cruft in most articles.
7824 @kindex W W a (Summary)
7825 @findex gnus-article-hide
7826 Do quite a lot of hiding on the article buffer
7827 (@kbd{gnus-article-hide}). In particular, this function will hide
7828 headers, PGP, cited text and the signature.
7831 @kindex W W h (Summary)
7832 @findex gnus-article-hide-headers
7833 Hide headers (@code{gnus-article-hide-headers}). @xref{Hiding
7837 @kindex W W b (Summary)
7838 @findex gnus-article-hide-boring-headers
7839 Hide headers that aren't particularly interesting
7840 (@code{gnus-article-hide-boring-headers}). @xref{Hiding Headers}.
7843 @kindex W W s (Summary)
7844 @findex gnus-article-hide-signature
7845 Hide signature (@code{gnus-article-hide-signature}). @xref{Article
7849 @kindex W W l (Summary)
7850 @findex gnus-article-hide-list-identifiers
7851 @vindex gnus-list-identifiers
7852 Strip list identifiers specified in @code{gnus-list-identifiers}. These
7853 are strings some mailing list servers add to the beginning of all
7854 @code{Subject} headers---for example, @samp{[zebra 4711]}. Any leading
7855 @samp{Re: } is skipped before stripping. @code{gnus-list-identifiers}
7856 may not contain @code{\\(..\\)}.
7860 @item gnus-list-identifiers
7861 @vindex gnus-list-identifiers
7862 A regular expression that matches list identifiers to be removed from
7863 subject. This can also be a list of regular expressions.
7868 @kindex W W p (Summary)
7869 @findex gnus-article-hide-pgp
7870 @vindex gnus-article-hide-pgp-hook
7871 Hide @sc{pgp} signatures (@code{gnus-article-hide-pgp}). The
7872 @code{gnus-article-hide-pgp-hook} hook will be run after a @sc{pgp}
7873 signature has been hidden. For example, to automatically verify
7874 articles that have signatures in them do:
7876 ;;; Hide pgp cruft if any.
7878 (setq gnus-treat-strip-pgp t)
7880 ;;; After hiding pgp, verify the message;
7881 ;;; only happens if pgp signature is found.
7883 (add-hook 'gnus-article-hide-pgp-hook
7886 (set-buffer gnus-original-article-buffer)
7891 @kindex W W P (Summary)
7892 @findex gnus-article-hide-pem
7893 Hide @sc{pem} (privacy enhanced messages) cruft
7894 (@code{gnus-article-hide-pem}).
7897 @kindex W W B (Summary)
7898 @findex gnus-article-strip-banner
7901 @cindex stripping advertisements
7902 @cindex advertisements
7903 Strip the banner specified by the @code{banner} group parameter
7904 (@code{gnus-article-strip-banner}). This is mainly used to hide those
7905 annoying banners and/or signatures that some mailing lists and moderated
7906 groups adds to all the messages. The way to use this function is to add
7907 the @code{banner} group parameter (@pxref{Group Parameters}) to the
7908 group you want banners stripped from. The parameter either be a string,
7909 which will be interpreted as a regular expression matching text to be
7910 removed, or the symbol @code{signature}, meaning that the (last)
7911 signature should be removed, or other symbol, meaning that the
7912 corresponding regular expression in @code{gnus-article-banner-alist} is
7916 @kindex W W c (Summary)
7917 @findex gnus-article-hide-citation
7918 Hide citation (@code{gnus-article-hide-citation}). Some variables for
7919 customizing the hiding:
7923 @item gnus-cited-opened-text-button-line-format
7924 @itemx gnus-cited-closed-text-button-line-format
7925 @vindex gnus-cited-closed-text-button-line-format
7926 @vindex gnus-cited-opened-text-button-line-format
7927 Gnus adds buttons to show where the cited text has been hidden, and to
7928 allow toggle hiding the text. The format of the variable is specified
7929 by these format-like variable (@pxref{Formatting Variables}). These
7934 Starting point of the hidden text.
7936 Ending point of the hidden text.
7938 Number of characters in the hidden region.
7940 Number of lines of hidden text.
7943 @item gnus-cited-lines-visible
7944 @vindex gnus-cited-lines-visible
7945 The number of lines at the beginning of the cited text to leave
7946 shown. This can also be a cons cell with the number of lines at the top
7947 and bottom of the text, respectively, to remain visible.
7952 @kindex W W C-c (Summary)
7953 @findex gnus-article-hide-citation-maybe
7955 Hide citation (@code{gnus-article-hide-citation-maybe}) depending on the
7956 following two variables:
7959 @item gnus-cite-hide-percentage
7960 @vindex gnus-cite-hide-percentage
7961 If the cited text is of a bigger percentage than this variable (default
7962 50), hide the cited text.
7964 @item gnus-cite-hide-absolute
7965 @vindex gnus-cite-hide-absolute
7966 The cited text must have at least this length (default 10) before it
7971 @kindex W W C (Summary)
7972 @findex gnus-article-hide-citation-in-followups
7973 Hide cited text in articles that aren't roots
7974 (@code{gnus-article-hide-citation-in-followups}). This isn't very
7975 useful as an interactive command, but might be a handy function to stick
7976 have happen automatically (@pxref{Customizing Articles}).
7980 All these ``hiding'' commands are toggles, but if you give a negative
7981 prefix to these commands, they will show what they have previously
7982 hidden. If you give a positive prefix, they will always hide.
7984 Also @pxref{Article Highlighting} for further variables for
7985 citation customization.
7987 @xref{Customizing Articles}, for how to hide article elements
7991 @node Article Washing
7992 @subsection Article Washing
7994 @cindex article washing
7996 We call this ``article washing'' for a really good reason. Namely, the
7997 @kbd{A} key was taken, so we had to use the @kbd{W} key instead.
7999 @dfn{Washing} is defined by us as ``changing something from something to
8000 something else'', but normally results in something looking better.
8003 @xref{Customizing Articles}, if you want to change how Gnus displays
8004 articles by default.
8009 This is not really washing, it's sort of the opposite of washing. If
8010 you type this, you see the article exactly as it exists on disk or on
8014 @kindex W l (Summary)
8015 @findex gnus-summary-stop-page-breaking
8016 Remove page breaks from the current article
8017 (@code{gnus-summary-stop-page-breaking}). @xref{Misc Article}, for page
8021 @kindex W r (Summary)
8022 @findex gnus-summary-caesar-message
8023 @c @icon{gnus-summary-caesar-message}
8024 Do a Caesar rotate (rot13) on the article buffer
8025 (@code{gnus-summary-caesar-message}).
8026 Unreadable articles that tell you to read them with Caesar rotate or rot13.
8027 (Typically offensive jokes and such.)
8029 It's commonly called ``rot13'' because each letter is rotated 13
8030 positions in the alphabet, e. g. @samp{B} (letter #2) -> @samp{O} (letter
8031 #15). It is sometimes referred to as ``Caesar rotate'' because Caesar
8032 is rumored to have employed this form of, uh, somewhat weak encryption.
8036 @kindex W t (Summary)
8038 @findex gnus-summary-toggle-header
8039 Toggle whether to display all headers in the article buffer
8040 (@code{gnus-summary-toggle-header}).
8043 @kindex W v (Summary)
8044 @findex gnus-summary-verbose-header
8045 Toggle whether to display all headers in the article buffer permanently
8046 (@code{gnus-summary-verbose-header}).
8049 @kindex W o (Summary)
8050 @findex gnus-article-treat-overstrike
8051 Treat overstrike (@code{gnus-article-treat-overstrike}).
8054 @kindex W d (Summary)
8055 @findex gnus-article-treat-dumbquotes
8056 @vindex gnus-article-dumbquotes-map
8058 @cindex M****s*** sm*rtq**t*s
8060 Treat M****s*** sm*rtq**t*s according to
8061 @code{gnus-article-dumbquotes-map}
8062 (@code{gnus-article-treat-dumbquotes}). Note that this function guesses
8063 whether a character is a sm*rtq**t* or not, so it should only be used
8066 Sm*rtq**t*s are M****s***'s unilateral extension to the character map in
8067 an attempt to provide more quoting characters. If you see something
8068 like @code{\222} or @code{\264} where you're expecting some kind of
8069 apostrophe or quotation mark, then try this wash.
8072 @kindex W w (Summary)
8073 @findex gnus-article-fill-cited-article
8074 Do word wrap (@code{gnus-article-fill-cited-article}).
8076 You can give the command a numerical prefix to specify the width to use
8080 @kindex W Q (Summary)
8081 @findex gnus-article-fill-long-lines
8082 Fill long lines (@code{gnus-article-fill-long-lines}).
8085 @kindex W C (Summary)
8086 @findex gnus-article-capitalize-sentences
8087 Capitalize the first word in each sentence
8088 (@code{gnus-article-capitalize-sentences}).
8091 @kindex W c (Summary)
8092 @findex gnus-article-remove-cr
8093 Translate CRLF pairs (i. e., @samp{^M}s on the end of the lines) into LF
8094 (this takes care of DOS line endings), and then translate any remaining
8095 CRs into LF (this takes care of Mac line endings)
8096 (@code{gnus-article-remove-cr}).
8099 @kindex W q (Summary)
8100 @findex gnus-article-de-quoted-unreadable
8101 Treat quoted-printable (@code{gnus-article-de-quoted-unreadable}).
8102 Quoted-Printable is one common @sc{mime} encoding employed when sending
8103 non-ASCII (i. e., 8-bit) articles. It typically makes strings like
8104 @samp{déjà vu} look like @samp{d=E9j=E0 vu}, which doesn't look very
8105 readable to me. Note that the this is usually done automatically by
8106 Gnus if the message in question has a @code{Content-Transfer-Encoding}
8107 header that says that this encoding has been done.
8108 If a prefix is given, a charset will be asked for.
8111 @kindex W 6 (Summary)
8112 @findex gnus-article-de-base64-unreadable
8113 Treat base64 (@code{gnus-article-de-base64-unreadable}).
8114 Base64 is one common @sc{mime} encoding employed when sending non-ASCII
8115 (i. e., 8-bit) articles. Note that the this is usually done
8116 automatically by Gnus if the message in question has a
8117 @code{Content-Transfer-Encoding} header that says that this encoding has
8119 If a prefix is given, a charset will be asked for.
8122 @kindex W Z (Summary)
8123 @findex gnus-article-decode-HZ
8124 Treat HZ or HZP (@code{gnus-article-decode-HZ}). HZ (or HZP) is one
8125 common encoding employed when sending Chinese articles. It typically
8126 makes strings look like @samp{~@{<:Ky2;S@{#,NpJ)l6HK!#~@}}.
8129 @kindex W h (Summary)
8130 @findex gnus-article-wash-html
8131 Treat HTML (@code{gnus-article-wash-html}). Note that the this is
8132 usually done automatically by Gnus if the message in question has a
8133 @code{Content-Type} header that says that the message is HTML.
8135 If a prefix is given, a charset will be asked for.
8137 @vindex gnus-article-wash-function
8138 The default is to use w3 to convert the HTML, but this is controlled
8139 by the @code{gnus-article-wash-function} variable. Pre-defined
8140 functions you can use include:
8143 @item gnus-article-wash-html-with-w3
8144 @findex gnus-article-wash-html-with-w3
8145 Use w3 (this is the default).
8147 @item gnus-article-wash-html-with-w3m
8148 @item gnus-article-wash-html-with-w3m
8149 Use the external @samp{w3m} program.
8153 @kindex W b (Summary)
8154 @findex gnus-article-add-buttons
8155 Add clickable buttons to the article (@code{gnus-article-add-buttons}).
8156 @xref{Article Buttons}.
8159 @kindex W B (Summary)
8160 @findex gnus-article-add-buttons-to-head
8161 Add clickable buttons to the article headers
8162 (@code{gnus-article-add-buttons-to-head}).
8165 @kindex W p (Summary)
8166 @findex gnus-article-verify-x-pgp-sig
8167 Verify a signed control message (@code{gnus-article-verify-x-pgp-sig}).
8168 Control messages such as @code{newgroup} and @code{checkgroups} are
8169 usually signed by the hierarchy maintainer. You need to add the PGP
8170 public key of the maintainer to your keyring to verify the
8171 message.@footnote{PGP keys for many hierarchies are available at
8172 @uref{ftp://ftp.isc.org/pub/pgpcontrol/README.html}}
8175 @kindex W s (Summary)
8176 @findex gnus-summary-force-verify-and-decrypt
8177 Verify a signed (PGP, PGP/MIME or S/MIME) message
8178 (@code{gnus-summary-force-verify-and-decrypt}). @xref{Security}.
8181 @kindex W W H (Summary)
8182 @findex gnus-article-strip-headers-from-body
8183 Strip headers like the @code{X-No-Archive} header from the beginning of
8184 article bodies (@code{gnus-article-strip-headers-from-body}).
8187 @kindex W E l (Summary)
8188 @findex gnus-article-strip-leading-blank-lines
8189 Remove all blank lines from the beginning of the article
8190 (@code{gnus-article-strip-leading-blank-lines}).
8193 @kindex W E m (Summary)
8194 @findex gnus-article-strip-multiple-blank-lines
8195 Replace all blank lines with empty lines and then all multiple empty
8196 lines with a single empty line.
8197 (@code{gnus-article-strip-multiple-blank-lines}).
8200 @kindex W E t (Summary)
8201 @findex gnus-article-remove-trailing-blank-lines
8202 Remove all blank lines at the end of the article
8203 (@code{gnus-article-remove-trailing-blank-lines}).
8206 @kindex W E a (Summary)
8207 @findex gnus-article-strip-blank-lines
8208 Do all the three commands above
8209 (@code{gnus-article-strip-blank-lines}).
8212 @kindex W E A (Summary)
8213 @findex gnus-article-strip-all-blank-lines
8214 Remove all blank lines
8215 (@code{gnus-article-strip-all-blank-lines}).
8218 @kindex W E s (Summary)
8219 @findex gnus-article-strip-leading-space
8220 Remove all white space from the beginning of all lines of the article
8221 body (@code{gnus-article-strip-leading-space}).
8224 @kindex W E e (Summary)
8225 @findex gnus-article-strip-trailing-space
8226 Remove all white space from the end of all lines of the article
8227 body (@code{gnus-article-strip-trailing-space}).
8231 @xref{Customizing Articles}, for how to wash articles automatically.
8234 @node Article Header
8235 @subsection Article Header
8237 These commands perform various transformations of article header.
8242 @kindex W G u (Summary)
8243 @findex gnus-article-treat-unfold-headers
8244 Unfold folded header lines (@code{gnus-article-treat-unfold-headers}).
8247 @kindex W G n (Summary)
8248 @findex gnus-article-treat-fold-newsgroups
8249 Fold the @code{Newsgroups} and @code{Followup-To} headers
8250 (@code{gnus-article-treat-fold-newsgroups}).
8253 @kindex W G f (Summary)
8254 @findex gnus-article-treat-fold-header
8255 Fold all the message headers
8256 (@code{gnus-article-treat-fold-headers}).
8261 @node Article Buttons
8262 @subsection Article Buttons
8265 People often include references to other stuff in articles, and it would
8266 be nice if Gnus could just fetch whatever it is that people talk about
8267 with the minimum of fuzz when you hit @kbd{RET} or use the middle mouse
8268 button on these references.
8270 Gnus adds @dfn{buttons} to certain standard references by default:
8271 Well-formed URLs, mail addresses and Message-IDs. This is controlled by
8272 two variables, one that handles article bodies and one that handles
8277 @item gnus-button-alist
8278 @vindex gnus-button-alist
8279 This is an alist where each entry has this form:
8282 (REGEXP BUTTON-PAR USE-P FUNCTION DATA-PAR)
8288 All text that match this regular expression will be considered an
8289 external reference. Here's a typical regexp that matches embedded URLs:
8290 @samp{<URL:\\([^\n\r>]*\\)>}.
8293 Gnus has to know which parts of the matches is to be highlighted. This
8294 is a number that says what sub-expression of the regexp is to be
8295 highlighted. If you want it all highlighted, you use 0 here.
8298 This form will be @code{eval}ed, and if the result is non-@code{nil},
8299 this is considered a match. This is useful if you want extra sifting to
8300 avoid false matches.
8303 This function will be called when you click on this button.
8306 As with @var{button-par}, this is a sub-expression number, but this one
8307 says which part of the match is to be sent as data to @var{function}.
8311 So the full entry for buttonizing URLs is then
8314 ("<URL:\\([^\n\r>]*\\)>" 0 t gnus-button-url 1)
8317 @item gnus-header-button-alist
8318 @vindex gnus-header-button-alist
8319 This is just like the other alist, except that it is applied to the
8320 article head only, and that each entry has an additional element that is
8321 used to say what headers to apply the buttonize coding to:
8324 (HEADER REGEXP BUTTON-PAR USE-P FUNCTION DATA-PAR)
8327 @var{header} is a regular expression.
8329 @item gnus-button-url-regexp
8330 @vindex gnus-button-url-regexp
8331 A regular expression that matches embedded URLs. It is used in the
8332 default values of the variables above.
8334 @item gnus-article-button-face
8335 @vindex gnus-article-button-face
8336 Face used on buttons.
8338 @item gnus-article-mouse-face
8339 @vindex gnus-article-mouse-face
8340 Face used when the mouse cursor is over a button.
8344 @xref{Customizing Articles}, for how to buttonize articles automatically.
8348 @subsection Article Date
8350 The date is most likely generated in some obscure timezone you've never
8351 heard of, so it's quite nice to be able to find out what the time was
8352 when the article was sent.
8357 @kindex W T u (Summary)
8358 @findex gnus-article-date-ut
8359 Display the date in UT (aka. GMT, aka ZULU)
8360 (@code{gnus-article-date-ut}).
8363 @kindex W T i (Summary)
8364 @findex gnus-article-date-iso8601
8366 Display the date in international format, aka. ISO 8601
8367 (@code{gnus-article-date-iso8601}).
8370 @kindex W T l (Summary)
8371 @findex gnus-article-date-local
8372 Display the date in the local timezone (@code{gnus-article-date-local}).
8375 @kindex W T p (Summary)
8376 @findex gnus-article-date-english
8377 Display the date in a format that's easily pronounceable in English
8378 (@code{gnus-article-date-english}).
8381 @kindex W T s (Summary)
8382 @vindex gnus-article-time-format
8383 @findex gnus-article-date-user
8384 @findex format-time-string
8385 Display the date using a user-defined format
8386 (@code{gnus-article-date-user}). The format is specified by the
8387 @code{gnus-article-time-format} variable, and is a string that's passed
8388 to @code{format-time-string}. See the documentation of that variable
8389 for a list of possible format specs.
8392 @kindex W T e (Summary)
8393 @findex gnus-article-date-lapsed
8394 @findex gnus-start-date-timer
8395 @findex gnus-stop-date-timer
8396 Say how much time has elapsed between the article was posted and now
8397 (@code{gnus-article-date-lapsed}). It looks something like:
8400 X-Sent: 6 weeks, 4 days, 1 hour, 3 minutes, 8 seconds ago
8403 The value of @code{gnus-article-date-lapsed-new-header} determines
8404 whether this header will just be added below the old Date one, or will
8407 An advantage of using Gnus to read mail is that it converts simple bugs
8408 into wonderful absurdities.
8410 If you want to have this line updated continually, you can put
8413 (gnus-start-date-timer)
8416 in your @file{.gnus.el} file, or you can run it off of some hook. If
8417 you want to stop the timer, you can use the @code{gnus-stop-date-timer}
8421 @kindex W T o (Summary)
8422 @findex gnus-article-date-original
8423 Display the original date (@code{gnus-article-date-original}). This can
8424 be useful if you normally use some other conversion function and are
8425 worried that it might be doing something totally wrong. Say, claiming
8426 that the article was posted in 1854. Although something like that is
8427 @emph{totally} impossible. Don't you trust me? *titter*
8431 @xref{Customizing Articles}, for how to display the date in your
8432 preferred format automatically.
8435 @node Article Display
8436 @subsection Article Display
8441 These commands add various frivolous display gimmics to the article
8442 buffer in Emacs versions that support them.
8444 @code{X-Face} headers are small black-and-white images supplied by the
8445 message headers (@pxref{X-Face}).
8447 Picons, on the other hand, reside on your own system, and Gnus will
8448 try to match the headers to what you have (@pxref{Picons}).
8450 Smileys are those little @samp{:-)} symbols that people like to litter
8451 their messages with (@pxref{Smileys}).
8453 All these functions are toggles--if the elements already exist,
8458 @kindex W D x (Summary)
8459 @findex gnus-article-display-x-face
8460 Display an @code{X-Face} in the @code{From} header.
8461 (@code{gnus-article-display-x-face}).
8464 @kindex W D s (Summary)
8465 @findex gnus-smiley-smiley
8466 Display smileys (@code{gnus-treat-smiley}).
8469 @kindex W D f (Summary)
8470 @findex gnus-treat-from-picon
8471 Piconify the @code{From} header (@code{gnus-treat-from-picon}).
8474 @kindex W D m (Summary)
8475 @findex gnus-treat-mail-picon
8476 Piconify all mail headers (i. e., @code{Cc}, @code{To})
8477 (@code{gnus-treat-mail-picon}).
8480 @kindex W D n (Summary)
8481 @findex gnus-treat-newsgroups-picon
8482 Piconify all news headers (i. e., @code{Newsgroups} and
8483 @code{Followup-To}) (@code{gnus-treat-from-picon}).
8486 @kindex W D D (Summary)
8487 @findex gnus-article-remove-images
8488 Remove all images from the article buffer
8489 (@code{gnus-article-remove-images}).
8495 @node Article Signature
8496 @subsection Article Signature
8498 @cindex article signature
8500 @vindex gnus-signature-separator
8501 Each article is divided into two parts---the head and the body. The
8502 body can be divided into a signature part and a text part. The variable
8503 that says what is to be considered a signature is
8504 @code{gnus-signature-separator}. This is normally the standard
8505 @samp{^-- $} as mandated by son-of-RFC 1036. However, many people use
8506 non-standard signature separators, so this variable can also be a list
8507 of regular expressions to be tested, one by one. (Searches are done
8508 from the end of the body towards the beginning.) One likely value is:
8511 (setq gnus-signature-separator
8512 '("^-- $" ; The standard
8513 "^-- *$" ; A common mangling
8514 "^-------*$" ; Many people just use a looong
8515 ; line of dashes. Shame!
8516 "^ *--------*$" ; Double-shame!
8517 "^________*$" ; Underscores are also popular
8518 "^========*$")) ; Pervert!
8521 The more permissive you are, the more likely it is that you'll get false
8524 @vindex gnus-signature-limit
8525 @code{gnus-signature-limit} provides a limit to what is considered a
8526 signature when displaying articles.
8530 If it is an integer, no signature may be longer (in characters) than
8533 If it is a floating point number, no signature may be longer (in lines)
8536 If it is a function, the function will be called without any parameters,
8537 and if it returns @code{nil}, there is no signature in the buffer.
8539 If it is a string, it will be used as a regexp. If it matches, the text
8540 in question is not a signature.
8543 This variable can also be a list where the elements may be of the types
8544 listed above. Here's an example:
8547 (setq gnus-signature-limit
8548 '(200.0 "^---*Forwarded article"))
8551 This means that if there are more than 200 lines after the signature
8552 separator, or the text after the signature separator is matched by
8553 the regular expression @samp{^---*Forwarded article}, then it isn't a
8554 signature after all.
8557 @node Article Miscellania
8558 @subsection Article Miscellania
8562 @kindex A t (Summary)
8563 @findex gnus-article-babel
8564 Translate the article from one language to another
8565 (@code{gnus-article-babel}).
8571 @section @sc{mime} Commands
8572 @cindex MIME decoding
8574 @cindex viewing attachments
8576 The following commands all understand the numerical prefix. For
8577 instance, @kbd{3 b} means ``view the third @sc{mime} part''.
8583 @kindex K v (Summary)
8584 View the @sc{mime} part.
8587 @kindex K o (Summary)
8588 Save the @sc{mime} part.
8591 @kindex K c (Summary)
8592 Copy the @sc{mime} part.
8595 @kindex K e (Summary)
8596 View the @sc{mime} part externally.
8599 @kindex K i (Summary)
8600 View the @sc{mime} part internally.
8603 @kindex K | (Summary)
8604 Pipe the @sc{mime} part to an external command.
8607 The rest of these @sc{mime} commands do not use the numerical prefix in
8612 @kindex K b (Summary)
8613 Make all the @sc{mime} parts have buttons in front of them. This is
8614 mostly useful if you wish to save (or perform other actions) on inlined
8618 @kindex K m (Summary)
8619 @findex gnus-summary-repair-multipart
8620 Some multipart messages are transmitted with missing or faulty headers.
8621 This command will attempt to ``repair'' these messages so that they can
8622 be viewed in a more pleasant manner
8623 (@code{gnus-summary-repair-multipart}).
8626 @kindex X m (Summary)
8627 @findex gnus-summary-save-parts
8628 Save all parts matching a @sc{mime} type to a directory
8629 (@code{gnus-summary-save-parts}). Understands the process/prefix
8630 convention (@pxref{Process/Prefix}).
8633 @kindex M-t (Summary)
8634 @findex gnus-summary-display-buttonized
8635 Toggle the buttonized display of the article buffer
8636 (@code{gnus-summary-toggle-display-buttonized}).
8639 @kindex W M w (Summary)
8640 Decode RFC 2047-encoded words in the article headers
8641 (@code{gnus-article-decode-mime-words}).
8644 @kindex W M c (Summary)
8645 Decode encoded article bodies as well as charsets
8646 (@code{gnus-article-decode-charset}).
8648 This command looks in the @code{Content-Type} header to determine the
8649 charset. If there is no such header in the article, you can give it a
8650 prefix, which will prompt for the charset to decode as. In regional
8651 groups where people post using some common encoding (but do not include
8652 MIME headers), you can set the @code{charset} group/topic parameter to
8653 the required charset (@pxref{Group Parameters}).
8656 @kindex W M v (Summary)
8657 View all the @sc{mime} parts in the current article
8658 (@code{gnus-mime-view-all-parts}).
8665 @item gnus-ignored-mime-types
8666 @vindex gnus-ignored-mime-types
8667 This is a list of regexps. @sc{mime} types that match a regexp from
8668 this list will be completely ignored by Gnus. The default value is
8671 To have all Vcards be ignored, you'd say something like this:
8674 (setq gnus-ignored-mime-types
8678 @item gnus-unbuttonized-mime-types
8679 @vindex gnus-unbuttonized-mime-types
8680 This is a list of regexps. @sc{mime} types that match a regexp from
8681 this list won't have @sc{mime} buttons inserted unless they aren't
8682 displayed or this variable is overriden by
8683 @code{gnus-buttonized-mime-types}. The default value is
8686 @item gnus-buttonized-mime-types
8687 @vindex gnus-buttonized-mime-types
8688 This is a list of regexps. @sc{mime} types that match a regexp from
8689 this list will have @sc{mime} buttons inserted unless they aren't
8690 displayed. This variable overrides
8691 @code{gnus-unbuttonized-mime-types}. The default value is @code{nil}.
8693 To see e.g. security buttons but no other buttons, you could set this
8694 variable to @code{("multipart/signed")} and leave
8695 @code{gnus-unbuttonized-mime-types} to the default value.
8697 @item gnus-article-mime-part-function
8698 @vindex gnus-article-mime-part-function
8699 For each @sc{mime} part, this function will be called with the @sc{mime}
8700 handle as the parameter. The function is meant to be used to allow
8701 users to gather information from the article (e. g., add Vcard info to
8702 the bbdb database) or to do actions based on parts (e. g., automatically
8703 save all jpegs into some directory).
8705 Here's an example function the does the latter:
8708 (defun my-save-all-jpeg-parts (handle)
8709 (when (equal (car (mm-handle-type handle)) "image/jpeg")
8711 (insert (mm-get-part handle))
8712 (write-region (point-min) (point-max)
8713 (read-file-name "Save jpeg to: ")))))
8714 (setq gnus-article-mime-part-function
8715 'my-save-all-jpeg-parts)
8718 @vindex gnus-mime-multipart-functions
8719 @item gnus-mime-multipart-functions
8720 Alist of @sc{mime} multipart types and functions to handle them.
8722 @vindex mm-file-name-rewrite-functions
8723 @item mm-file-name-rewrite-functions
8724 List of functions used for rewriting file names of @sc{mime} parts.
8725 Each function takes a file name as input and returns a file name.
8727 Ready-made functions include@*
8728 @code{mm-file-name-delete-whitespace},
8729 @code{mm-file-name-trim-whitespace},
8730 @code{mm-file-name-collapse-whitespace}, and
8731 @code{mm-file-name-replace-whitespace}. The later uses the value of
8732 the variable @code{mm-file-name-replace-whitespace} to replace each
8733 whitespace character in a file name with that string; default value
8734 is @code{"_"} (a single underscore).
8735 @findex mm-file-name-delete-whitespace
8736 @findex mm-file-name-trim-whitespace
8737 @findex mm-file-name-collapse-whitespace
8738 @findex mm-file-name-replace-whitespace
8739 @vindex mm-file-name-replace-whitespace
8741 The standard functions @code{capitalize}, @code{downcase},
8742 @code{upcase}, and @code{upcase-initials} may be useful, too.
8744 Everybody knows that whitespace characters in file names are evil,
8745 except those who don't know. If you receive lots of attachments from
8746 such unenlightened users, you can make live easier by adding
8749 (setq mm-file-name-rewrite-functions
8750 '(mm-file-name-trim-whitespace
8751 mm-file-name-collapse-whitespace
8752 mm-file-name-replace-whitespace))
8756 to your @file{.gnus} file.
8765 People use different charsets, and we have @sc{mime} to let us know what
8766 charsets they use. Or rather, we wish we had. Many people use
8767 newsreaders and mailers that do not understand or use @sc{mime}, and
8768 just send out messages without saying what character sets they use. To
8769 help a bit with this, some local news hierarchies have policies that say
8770 what character set is the default. For instance, the @samp{fj}
8771 hierarchy uses @code{iso-2022-jp-2}.
8773 @vindex gnus-group-charset-alist
8774 This knowledge is encoded in the @code{gnus-group-charset-alist}
8775 variable, which is an alist of regexps (use the first item to match full
8776 group names) and default charsets to be used when reading these groups.
8778 In addition, some people do use soi-disant @sc{mime}-aware agents that
8779 aren't. These blithely mark messages as being in @code{iso-8859-1}
8780 even if they really are in @code{koi-8}. To help here, the
8781 @code{gnus-newsgroup-ignored-charsets} variable can be used. The
8782 charsets that are listed here will be ignored. The variable can be
8783 set on a group-by-group basis using the group parameters (@pxref{Group
8784 Parameters}). The default value is @code{(unknown-8bit x-unknown)},
8785 which includes values some agents insist on having in there.
8787 @vindex gnus-group-posting-charset-alist
8788 When posting, @code{gnus-group-posting-charset-alist} is used to
8789 determine which charsets should not be encoded using the @sc{mime}
8790 encodings. For instance, some hierarchies discourage using
8791 quoted-printable header encoding.
8793 This variable is an alist of regexps and permitted unencoded charsets
8794 for posting. Each element of the alist has the form @code{(}@var{test
8795 header body-list}@code{)}, where:
8799 is either a regular expression matching the newsgroup header or a
8802 is the charset which may be left unencoded in the header (@code{nil}
8803 means encode all charsets),
8805 is a list of charsets which may be encoded using 8bit content-transfer
8806 encoding in the body, or one of the special values @code{nil} (always
8807 encode using quoted-printable) or @code{t} (always use 8bit).
8814 @cindex coding system aliases
8815 @cindex preferred charset
8817 Other charset tricks that may be useful, although not Gnus-specific:
8819 If there are several @sc{mime} charsets that encode the same Emacs
8820 charset, you can choose what charset to use by saying the following:
8823 (put-charset-property 'cyrillic-iso8859-5
8824 'preferred-coding-system 'koi8-r)
8827 This means that Russian will be encoded using @code{koi8-r} instead of
8828 the default @code{iso-8859-5} @sc{mime} charset.
8830 If you want to read messages in @code{koi8-u}, you can cheat and say
8833 (define-coding-system-alias 'koi8-u 'koi8-r)
8836 This will almost do the right thing.
8838 And finally, to read charsets like @code{windows-1251}, you can say
8842 (codepage-setup 1251)
8843 (define-coding-system-alias 'windows-1251 'cp1251)
8847 @node Article Commands
8848 @section Article Commands
8855 @kindex A P (Summary)
8856 @vindex gnus-ps-print-hook
8857 @findex gnus-summary-print-article
8858 Generate and print a PostScript image of the article buffer
8859 (@code{gnus-summary-print-article}). @code{gnus-ps-print-hook} will
8860 be run just before printing the buffer. An alternative way to print
8861 article is to use Muttprint (@pxref{Saving Articles}).
8866 @node Summary Sorting
8867 @section Summary Sorting
8868 @cindex summary sorting
8870 You can have the summary buffer sorted in various ways, even though I
8871 can't really see why you'd want that.
8876 @kindex C-c C-s C-n (Summary)
8877 @findex gnus-summary-sort-by-number
8878 Sort by article number (@code{gnus-summary-sort-by-number}).
8881 @kindex C-c C-s C-a (Summary)
8882 @findex gnus-summary-sort-by-author
8883 Sort by author (@code{gnus-summary-sort-by-author}).
8886 @kindex C-c C-s C-s (Summary)
8887 @findex gnus-summary-sort-by-subject
8888 Sort by subject (@code{gnus-summary-sort-by-subject}).
8891 @kindex C-c C-s C-d (Summary)
8892 @findex gnus-summary-sort-by-date
8893 Sort by date (@code{gnus-summary-sort-by-date}).
8896 @kindex C-c C-s C-l (Summary)
8897 @findex gnus-summary-sort-by-lines
8898 Sort by lines (@code{gnus-summary-sort-by-lines}).
8901 @kindex C-c C-s C-c (Summary)
8902 @findex gnus-summary-sort-by-chars
8903 Sort by article length (@code{gnus-summary-sort-by-chars}).
8906 @kindex C-c C-s C-i (Summary)
8907 @findex gnus-summary-sort-by-score
8908 Sort by score (@code{gnus-summary-sort-by-score}).
8911 @kindex C-c C-s C-o (Summary)
8912 @findex gnus-summary-sort-by-original
8913 Sort using the default sorting method
8914 (@code{gnus-summary-sort-by-original}).
8917 These functions will work both when you use threading and when you don't
8918 use threading. In the latter case, all summary lines will be sorted,
8919 line by line. In the former case, sorting will be done on a
8920 root-by-root basis, which might not be what you were looking for. To
8921 toggle whether to use threading, type @kbd{T T} (@pxref{Thread
8925 @node Finding the Parent
8926 @section Finding the Parent
8927 @cindex parent articles
8928 @cindex referring articles
8933 @findex gnus-summary-refer-parent-article
8934 If you'd like to read the parent of the current article, and it is not
8935 displayed in the summary buffer, you might still be able to. That is,
8936 if the current group is fetched by @sc{nntp}, the parent hasn't expired
8937 and the @code{References} in the current article are not mangled, you
8938 can just press @kbd{^} or @kbd{A r}
8939 (@code{gnus-summary-refer-parent-article}). If everything goes well,
8940 you'll get the parent. If the parent is already displayed in the
8941 summary buffer, point will just move to this article.
8943 If given a positive numerical prefix, fetch that many articles back into
8944 the ancestry. If given a negative numerical prefix, fetch just that
8945 ancestor. So if you say @kbd{3 ^}, Gnus will fetch the parent, the
8946 grandparent and the grandgrandparent of the current article. If you say
8947 @kbd{-3 ^}, Gnus will only fetch the grandgrandparent of the current
8951 @findex gnus-summary-refer-references
8952 @kindex A R (Summary)
8953 Fetch all articles mentioned in the @code{References} header of the
8954 article (@code{gnus-summary-refer-references}).
8957 @findex gnus-summary-refer-thread
8958 @kindex A T (Summary)
8959 Display the full thread where the current article appears
8960 (@code{gnus-summary-refer-thread}). This command has to fetch all the
8961 headers in the current group to work, so it usually takes a while. If
8962 you do it often, you may consider setting @code{gnus-fetch-old-headers}
8963 to @code{invisible} (@pxref{Filling In Threads}). This won't have any
8964 visible effects normally, but it'll make this command work a whole lot
8965 faster. Of course, it'll make group entry somewhat slow.
8967 @vindex gnus-refer-thread-limit
8968 The @code{gnus-refer-thread-limit} variable says how many old (i. e.,
8969 articles before the first displayed in the current group) headers to
8970 fetch when doing this command. The default is 200. If @code{t}, all
8971 the available headers will be fetched. This variable can be overridden
8972 by giving the @kbd{A T} command a numerical prefix.
8975 @findex gnus-summary-refer-article
8976 @kindex M-^ (Summary)
8978 @cindex fetching by Message-ID
8979 You can also ask the @sc{nntp} server for an arbitrary article, no
8980 matter what group it belongs to. @kbd{M-^}
8981 (@code{gnus-summary-refer-article}) will ask you for a
8982 @code{Message-ID}, which is one of those long, hard-to-read thingies
8983 that look something like @samp{<38o6up$6f2@@hymir.ifi.uio.no>}. You
8984 have to get it all exactly right. No fuzzy searches, I'm afraid.
8987 The current select method will be used when fetching by
8988 @code{Message-ID} from non-news select method, but you can override this
8989 by giving this command a prefix.
8991 @vindex gnus-refer-article-method
8992 If the group you are reading is located on a back end that does not
8993 support fetching by @code{Message-ID} very well (like @code{nnspool}),
8994 you can set @code{gnus-refer-article-method} to an @sc{nntp} method. It
8995 would, perhaps, be best if the @sc{nntp} server you consult is the one
8996 updating the spool you are reading from, but that's not really
8999 It can also be a list of select methods, as well as the special symbol
9000 @code{current}, which means to use the current select method. If it
9001 is a list, Gnus will try all the methods in the list until it finds a
9004 Here's an example setting that will first try the current method, and
9005 then ask Deja if that fails:
9008 (setq gnus-refer-article-method
9010 (nnweb "refer" (nnweb-type dejanews))))
9013 Most of the mail back ends support fetching by @code{Message-ID}, but
9014 do not do a particularly excellent job at it. That is, @code{nnmbox}
9015 and @code{nnbabyl} are able to locate articles from any groups, while
9016 @code{nnml}, @code{nnfolder} and @code{nnimap}1 are only able to locate
9017 articles that have been posted to the current group. (Anything else
9018 would be too time consuming.) @code{nnmh} does not support this at
9022 @node Alternative Approaches
9023 @section Alternative Approaches
9025 Different people like to read news using different methods. This being
9026 Gnus, we offer a small selection of minor modes for the summary buffers.
9029 * Pick and Read:: First mark articles and then read them.
9030 * Binary Groups:: Auto-decode all articles.
9035 @subsection Pick and Read
9036 @cindex pick and read
9038 Some newsreaders (like @code{nn} and, uhm, @code{Netnews} on VM/CMS) use
9039 a two-phased reading interface. The user first marks in a summary
9040 buffer the articles she wants to read. Then she starts reading the
9041 articles with just an article buffer displayed.
9043 @findex gnus-pick-mode
9044 @kindex M-x gnus-pick-mode
9045 Gnus provides a summary buffer minor mode that allows
9046 this---@code{gnus-pick-mode}. This basically means that a few process
9047 mark commands become one-keystroke commands to allow easy marking, and
9048 it provides one additional command for switching to the summary buffer.
9050 Here are the available keystrokes when using pick mode:
9055 @findex gnus-pick-article-or-thread
9056 Pick the article or thread on the current line
9057 (@code{gnus-pick-article-or-thread}). If the variable
9058 @code{gnus-thread-hide-subtree} is true, then this key selects the
9059 entire thread when used at the first article of the thread. Otherwise,
9060 it selects just the article. If given a numerical prefix, go to that
9061 thread or article and pick it. (The line number is normally displayed
9062 at the beginning of the summary pick lines.)
9065 @kindex SPACE (Pick)
9066 @findex gnus-pick-next-page
9067 Scroll the summary buffer up one page (@code{gnus-pick-next-page}). If
9068 at the end of the buffer, start reading the picked articles.
9072 @findex gnus-pick-unmark-article-or-thread.
9073 Unpick the thread or article
9074 (@code{gnus-pick-unmark-article-or-thread}). If the variable
9075 @code{gnus-thread-hide-subtree} is true, then this key unpicks the
9076 thread if used at the first article of the thread. Otherwise it unpicks
9077 just the article. You can give this key a numerical prefix to unpick
9078 the thread or article at that line.
9082 @findex gnus-pick-start-reading
9083 @vindex gnus-pick-display-summary
9084 Start reading the picked articles (@code{gnus-pick-start-reading}). If
9085 given a prefix, mark all unpicked articles as read first. If
9086 @code{gnus-pick-display-summary} is non-@code{nil}, the summary buffer
9087 will still be visible when you are reading.
9091 All the normal summary mode commands are still available in the
9092 pick-mode, with the exception of @kbd{u}. However @kbd{!} is available
9093 which is mapped to the same function
9094 @code{gnus-summary-tick-article-forward}.
9096 If this sounds like a good idea to you, you could say:
9099 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
9102 @vindex gnus-pick-mode-hook
9103 @code{gnus-pick-mode-hook} is run in pick minor mode buffers.
9105 @vindex gnus-mark-unpicked-articles-as-read
9106 If @code{gnus-mark-unpicked-articles-as-read} is non-@code{nil}, mark
9107 all unpicked articles as read. The default is @code{nil}.
9109 @vindex gnus-summary-pick-line-format
9110 The summary line format in pick mode is slightly different from the
9111 standard format. At the beginning of each line the line number is
9112 displayed. The pick mode line format is controlled by the
9113 @code{gnus-summary-pick-line-format} variable (@pxref{Formatting
9114 Variables}). It accepts the same format specs that
9115 @code{gnus-summary-line-format} does (@pxref{Summary Buffer Lines}).
9119 @subsection Binary Groups
9120 @cindex binary groups
9122 @findex gnus-binary-mode
9123 @kindex M-x gnus-binary-mode
9124 If you spend much time in binary groups, you may grow tired of hitting
9125 @kbd{X u}, @kbd{n}, @kbd{RET} all the time. @kbd{M-x gnus-binary-mode}
9126 is a minor mode for summary buffers that makes all ordinary Gnus article
9127 selection functions uudecode series of articles and display the result
9128 instead of just displaying the articles the normal way.
9131 @findex gnus-binary-show-article
9132 The only way, in fact, to see the actual articles is the @kbd{g}
9133 command, when you have turned on this mode
9134 (@code{gnus-binary-show-article}).
9136 @vindex gnus-binary-mode-hook
9137 @code{gnus-binary-mode-hook} is called in binary minor mode buffers.
9141 @section Tree Display
9144 @vindex gnus-use-trees
9145 If you don't like the normal Gnus summary display, you might try setting
9146 @code{gnus-use-trees} to @code{t}. This will create (by default) an
9147 additional @dfn{tree buffer}. You can execute all summary mode commands
9150 There are a few variables to customize the tree display, of course:
9153 @item gnus-tree-mode-hook
9154 @vindex gnus-tree-mode-hook
9155 A hook called in all tree mode buffers.
9157 @item gnus-tree-mode-line-format
9158 @vindex gnus-tree-mode-line-format
9159 A format string for the mode bar in the tree mode buffers (@pxref{Mode
9160 Line Formatting}). The default is @samp{Gnus: %%b %S %Z}. For a list
9161 of valid specs, @pxref{Summary Buffer Mode Line}.
9163 @item gnus-selected-tree-face
9164 @vindex gnus-selected-tree-face
9165 Face used for highlighting the selected article in the tree buffer. The
9166 default is @code{modeline}.
9168 @item gnus-tree-line-format
9169 @vindex gnus-tree-line-format
9170 A format string for the tree nodes. The name is a bit of a misnomer,
9171 though---it doesn't define a line, but just the node. The default value
9172 is @samp{%(%[%3,3n%]%)}, which displays the first three characters of
9173 the name of the poster. It is vital that all nodes are of the same
9174 length, so you @emph{must} use @samp{%4,4n}-like specifiers.
9180 The name of the poster.
9182 The @code{From} header.
9184 The number of the article.
9186 The opening bracket.
9188 The closing bracket.
9193 @xref{Formatting Variables}.
9195 Variables related to the display are:
9198 @item gnus-tree-brackets
9199 @vindex gnus-tree-brackets
9200 This is used for differentiating between ``real'' articles and
9201 ``sparse'' articles. The format is @code{((@var{real-open} . @var{real-close})
9202 (@var{sparse-open} . @var{sparse-close}) (@var{dummy-open} . @var{dummy-close}))}, and the
9203 default is @code{((?[ . ?]) (?( . ?)) (?@{ . ?@}) (?< . ?>))}.
9205 @item gnus-tree-parent-child-edges
9206 @vindex gnus-tree-parent-child-edges
9207 This is a list that contains the characters used for connecting parent
9208 nodes to their children. The default is @code{(?- ?\\ ?|)}.
9212 @item gnus-tree-minimize-window
9213 @vindex gnus-tree-minimize-window
9214 If this variable is non-@code{nil}, Gnus will try to keep the tree
9215 buffer as small as possible to allow more room for the other Gnus
9216 windows. If this variable is a number, the tree buffer will never be
9217 higher than that number. The default is @code{t}. Note that if you
9218 have several windows displayed side-by-side in a frame and the tree
9219 buffer is one of these, minimizing the tree window will also resize all
9220 other windows displayed next to it.
9222 You may also wish to add the following hook to keep the window minimized
9226 (add-hook 'gnus-configure-windows-hook
9227 'gnus-tree-perhaps-minimize)
9230 @item gnus-generate-tree-function
9231 @vindex gnus-generate-tree-function
9232 @findex gnus-generate-horizontal-tree
9233 @findex gnus-generate-vertical-tree
9234 The function that actually generates the thread tree. Two predefined
9235 functions are available: @code{gnus-generate-horizontal-tree} and
9236 @code{gnus-generate-vertical-tree} (which is the default).
9240 Here's an example from a horizontal tree buffer:
9243 @{***@}-(***)-[odd]-[Gun]
9253 Here's the same thread displayed in a vertical tree buffer:
9257 |--------------------------\-----\-----\
9258 (***) [Bjo] [Gun] [Gun]
9260 [odd] [Jan] [odd] (***) [Jor]
9262 [Gun] [Eri] [Eri] [odd]
9267 If you're using horizontal trees, it might be nice to display the trees
9268 side-by-side with the summary buffer. You could add something like the
9269 following to your @file{.gnus.el} file:
9272 (setq gnus-use-trees t
9273 gnus-generate-tree-function 'gnus-generate-horizontal-tree
9274 gnus-tree-minimize-window nil)
9275 (gnus-add-configuration
9279 (summary 0.75 point)
9284 @xref{Window Layout}.
9287 @node Mail Group Commands
9288 @section Mail Group Commands
9289 @cindex mail group commands
9291 Some commands only make sense in mail groups. If these commands are
9292 invalid in the current group, they will raise a hell and let you know.
9294 All these commands (except the expiry and edit commands) use the
9295 process/prefix convention (@pxref{Process/Prefix}).
9300 @kindex B e (Summary)
9301 @findex gnus-summary-expire-articles
9302 Run all expirable articles in the current group through the expiry
9303 process (@code{gnus-summary-expire-articles}). That is, delete all
9304 expirable articles in the group that have been around for a while.
9305 (@pxref{Expiring Mail}).
9308 @kindex B C-M-e (Summary)
9309 @findex gnus-summary-expire-articles-now
9310 Delete all the expirable articles in the group
9311 (@code{gnus-summary-expire-articles-now}). This means that @strong{all}
9312 articles eligible for expiry in the current group will
9313 disappear forever into that big @file{/dev/null} in the sky.
9316 @kindex B DEL (Summary)
9317 @findex gnus-summary-delete-article
9318 @c @icon{gnus-summary-mail-delete}
9319 Delete the mail article. This is ``delete'' as in ``delete it from your
9320 disk forever and ever, never to return again.'' Use with caution.
9321 (@code{gnus-summary-delete-article}).
9324 @kindex B m (Summary)
9326 @findex gnus-summary-move-article
9327 @vindex gnus-preserve-marks
9328 Move the article from one mail group to another
9329 (@code{gnus-summary-move-article}). Marks will be preserved if
9330 @var{gnus-preserve-marks} is non-@code{nil} (which is the default).
9333 @kindex B c (Summary)
9335 @findex gnus-summary-copy-article
9336 @c @icon{gnus-summary-mail-copy}
9337 Copy the article from one group (mail group or not) to a mail group
9338 (@code{gnus-summary-copy-article}). Marks will be preserved if
9339 @var{gnus-preserve-marks} is non-@code{nil} (which is the default).
9342 @kindex B B (Summary)
9343 @cindex crosspost mail
9344 @findex gnus-summary-crosspost-article
9345 Crosspost the current article to some other group
9346 (@code{gnus-summary-crosspost-article}). This will create a new copy of
9347 the article in the other group, and the Xref headers of the article will
9348 be properly updated.
9351 @kindex B i (Summary)
9352 @findex gnus-summary-import-article
9353 Import an arbitrary file into the current mail newsgroup
9354 (@code{gnus-summary-import-article}). You will be prompted for a file
9355 name, a @code{From} header and a @code{Subject} header.
9358 @kindex B r (Summary)
9359 @findex gnus-summary-respool-article
9360 Respool the mail article (@code{gnus-summary-respool-article}).
9361 @code{gnus-summary-respool-default-method} will be used as the default
9362 select method when respooling. This variable is @code{nil} by default,
9363 which means that the current group select method will be used instead.
9364 Marks will be preserved if @var{gnus-preserve-marks} is non-@code{nil}
9365 (which is the default).
9369 @kindex B w (Summary)
9371 @findex gnus-summary-edit-article
9372 @kindex C-c C-c (Article)
9373 Edit the current article (@code{gnus-summary-edit-article}). To finish
9374 editing and make the changes permanent, type @kbd{C-c C-c}
9375 (@kbd{gnus-summary-edit-article-done}). If you give a prefix to the
9376 @kbd{C-c C-c} command, Gnus won't re-highlight the article.
9379 @kindex B q (Summary)
9380 @findex gnus-summary-respool-query
9381 If you want to re-spool an article, you might be curious as to what group
9382 the article will end up in before you do the re-spooling. This command
9383 will tell you (@code{gnus-summary-respool-query}).
9386 @kindex B t (Summary)
9387 @findex gnus-summary-respool-trace
9388 Similarly, this command will display all fancy splitting patterns used
9389 when repooling, if any (@code{gnus-summary-respool-trace}).
9392 @kindex B p (Summary)
9393 @findex gnus-summary-article-posted-p
9394 Some people have a tendency to send you "courtesy" copies when they
9395 follow up to articles you have posted. These usually have a
9396 @code{Newsgroups} header in them, but not always. This command
9397 (@code{gnus-summary-article-posted-p}) will try to fetch the current
9398 article from your news server (or rather, from
9399 @code{gnus-refer-article-method} or @code{gnus-select-method}) and will
9400 report back whether it found the article or not. Even if it says that
9401 it didn't find the article, it may have been posted anyway---mail
9402 propagation is much faster than news propagation, and the news copy may
9403 just not have arrived yet.
9407 @vindex gnus-move-split-methods
9408 @cindex moving articles
9409 If you move (or copy) articles regularly, you might wish to have Gnus
9410 suggest where to put the articles. @code{gnus-move-split-methods} is a
9411 variable that uses the same syntax as @code{gnus-split-methods}
9412 (@pxref{Saving Articles}). You may customize that variable to create
9413 suggestions you find reasonable. (Note that
9414 @code{gnus-move-split-methods} uses group names where
9415 @code{gnus-split-methods} uses file names.)
9418 (setq gnus-move-split-methods
9419 '(("^From:.*Lars Magne" "nnml:junk")
9420 ("^Subject:.*gnus" "nnfolder:important")
9421 (".*" "nnml:misc")))
9425 @node Various Summary Stuff
9426 @section Various Summary Stuff
9429 * Summary Group Information:: Information oriented commands.
9430 * Searching for Articles:: Multiple article commands.
9431 * Summary Generation Commands::
9432 * Really Various Summary Commands:: Those pesky non-conformant commands.
9436 @vindex gnus-summary-mode-hook
9437 @item gnus-summary-mode-hook
9438 This hook is called when creating a summary mode buffer.
9440 @vindex gnus-summary-generate-hook
9441 @item gnus-summary-generate-hook
9442 This is called as the last thing before doing the threading and the
9443 generation of the summary buffer. It's quite convenient for customizing
9444 the threading variables based on what data the newsgroup has. This hook
9445 is called from the summary buffer after most summary buffer variables
9448 @vindex gnus-summary-prepare-hook
9449 @item gnus-summary-prepare-hook
9450 It is called after the summary buffer has been generated. You might use
9451 it to, for instance, highlight lines or modify the look of the buffer in
9452 some other ungodly manner. I don't care.
9454 @vindex gnus-summary-prepared-hook
9455 @item gnus-summary-prepared-hook
9456 A hook called as the very last thing after the summary buffer has been
9459 @vindex gnus-summary-ignore-duplicates
9460 @item gnus-summary-ignore-duplicates
9461 When Gnus discovers two articles that have the same @code{Message-ID},
9462 it has to do something drastic. No articles are allowed to have the
9463 same @code{Message-ID}, but this may happen when reading mail from some
9464 sources. Gnus allows you to customize what happens with this variable.
9465 If it is @code{nil} (which is the default), Gnus will rename the
9466 @code{Message-ID} (for display purposes only) and display the article as
9467 any other article. If this variable is @code{t}, it won't display the
9468 article---it'll be as if it never existed.
9470 @vindex gnus-alter-articles-to-read-function
9471 @item gnus-alter-articles-to-read-function
9472 This function, which takes two parameters (the group name and the list
9473 of articles to be selected), is called to allow the user to alter the
9474 list of articles to be selected.
9476 For instance, the following function adds the list of cached articles to
9477 the list in one particular group:
9480 (defun my-add-cached-articles (group articles)
9481 (if (string= group "some.group")
9482 (append gnus-newsgroup-cached articles)
9486 @vindex gnus-newsgroup-variables
9487 @item gnus-newsgroup-variables
9488 A list of newsgroup (summary buffer) local variables, or cons of
9489 variables and their default values (when the default values are not
9490 nil), that should be made global while the summary buffer is active.
9491 These variables can be used to set variables in the group parameters
9492 while still allowing them to affect operations done in other
9493 buffers. For example:
9496 (setq gnus-newsgroup-variables
9497 '(message-use-followup-to
9498 (gnus-visible-headers .
9499 "^From:\\|^Newsgroups:\\|^Subject:\\|^Date:\\|^To:")))
9505 @node Summary Group Information
9506 @subsection Summary Group Information
9511 @kindex H f (Summary)
9512 @findex gnus-summary-fetch-faq
9513 @vindex gnus-group-faq-directory
9514 Try to fetch the FAQ (list of frequently asked questions) for the
9515 current group (@code{gnus-summary-fetch-faq}). Gnus will try to get the
9516 FAQ from @code{gnus-group-faq-directory}, which is usually a directory
9517 on a remote machine. This variable can also be a list of directories.
9518 In that case, giving a prefix to this command will allow you to choose
9519 between the various sites. @code{ange-ftp} or @code{efs} will probably
9520 be used for fetching the file.
9523 @kindex H d (Summary)
9524 @findex gnus-summary-describe-group
9525 Give a brief description of the current group
9526 (@code{gnus-summary-describe-group}). If given a prefix, force
9527 rereading the description from the server.
9530 @kindex H h (Summary)
9531 @findex gnus-summary-describe-briefly
9532 Give an extremely brief description of the most important summary
9533 keystrokes (@code{gnus-summary-describe-briefly}).
9536 @kindex H i (Summary)
9537 @findex gnus-info-find-node
9538 Go to the Gnus info node (@code{gnus-info-find-node}).
9542 @node Searching for Articles
9543 @subsection Searching for Articles
9548 @kindex M-s (Summary)
9549 @findex gnus-summary-search-article-forward
9550 Search through all subsequent (raw) articles for a regexp
9551 (@code{gnus-summary-search-article-forward}).
9554 @kindex M-r (Summary)
9555 @findex gnus-summary-search-article-backward
9556 Search through all previous (raw) articles for a regexp
9557 (@code{gnus-summary-search-article-backward}).
9561 @findex gnus-summary-execute-command
9562 This command will prompt you for a header, a regular expression to match
9563 on this field, and a command to be executed if the match is made
9564 (@code{gnus-summary-execute-command}). If the header is an empty
9565 string, the match is done on the entire article. If given a prefix,
9566 search backward instead.
9568 For instance, @kbd{& RET some.*string #} will put the process mark on
9569 all articles that have heads or bodies that match @samp{some.*string}.
9572 @kindex M-& (Summary)
9573 @findex gnus-summary-universal-argument
9574 Perform any operation on all articles that have been marked with
9575 the process mark (@code{gnus-summary-universal-argument}).
9578 @node Summary Generation Commands
9579 @subsection Summary Generation Commands
9584 @kindex Y g (Summary)
9585 @findex gnus-summary-prepare
9586 Regenerate the current summary buffer (@code{gnus-summary-prepare}).
9589 @kindex Y c (Summary)
9590 @findex gnus-summary-insert-cached-articles
9591 Pull all cached articles (for the current group) into the summary buffer
9592 (@code{gnus-summary-insert-cached-articles}).
9597 @node Really Various Summary Commands
9598 @subsection Really Various Summary Commands
9604 @kindex C-d (Summary)
9605 @kindex A D (Summary)
9606 @findex gnus-summary-enter-digest-group
9607 If the current article is a collection of other articles (for instance,
9608 a digest), you might use this command to enter a group based on the that
9609 article (@code{gnus-summary-enter-digest-group}). Gnus will try to
9610 guess what article type is currently displayed unless you give a prefix
9611 to this command, which forces a ``digest'' interpretation. Basically,
9612 whenever you see a message that is a collection of other messages of
9613 some format, you @kbd{C-d} and read these messages in a more convenient
9617 @kindex C-M-d (Summary)
9618 @findex gnus-summary-read-document
9619 This command is very similar to the one above, but lets you gather
9620 several documents into one biiig group
9621 (@code{gnus-summary-read-document}). It does this by opening several
9622 @code{nndoc} groups for each document, and then opening an
9623 @code{nnvirtual} group on top of these @code{nndoc} groups. This
9624 command understands the process/prefix convention
9625 (@pxref{Process/Prefix}).
9628 @kindex C-t (Summary)
9629 @findex gnus-summary-toggle-truncation
9630 Toggle truncation of summary lines
9631 (@code{gnus-summary-toggle-truncation}). This will probably confuse the
9632 line centering function in the summary buffer, so it's not a good idea
9633 to have truncation switched off while reading articles.
9637 @findex gnus-summary-expand-window
9638 Expand the summary buffer window (@code{gnus-summary-expand-window}).
9639 If given a prefix, force an @code{article} window configuration.
9642 @kindex C-M-e (Summary)
9643 @findex gnus-summary-edit-parameters
9644 Edit the group parameters (@pxref{Group Parameters}) of the current
9645 group (@code{gnus-summary-edit-parameters}).
9648 @kindex C-M-a (Summary)
9649 @findex gnus-summary-customize-parameters
9650 Customize the group parameters (@pxref{Group Parameters}) of the current
9651 group (@code{gnus-summary-customize-parameters}).
9656 @node Exiting the Summary Buffer
9657 @section Exiting the Summary Buffer
9658 @cindex summary exit
9659 @cindex exiting groups
9661 Exiting from the summary buffer will normally update all info on the
9662 group and return you to the group buffer.
9668 @kindex Z Z (Summary)
9670 @findex gnus-summary-exit
9671 @vindex gnus-summary-exit-hook
9672 @vindex gnus-summary-prepare-exit-hook
9673 @c @icon{gnus-summary-exit}
9674 Exit the current group and update all information on the group
9675 (@code{gnus-summary-exit}). @code{gnus-summary-prepare-exit-hook} is
9676 called before doing much of the exiting, which calls
9677 @code{gnus-summary-expire-articles} by default.
9678 @code{gnus-summary-exit-hook} is called after finishing the exit
9679 process. @code{gnus-group-no-more-groups-hook} is run when returning to
9680 group mode having no more (unread) groups.
9684 @kindex Z E (Summary)
9686 @findex gnus-summary-exit-no-update
9687 Exit the current group without updating any information on the group
9688 (@code{gnus-summary-exit-no-update}).
9692 @kindex Z c (Summary)
9694 @findex gnus-summary-catchup-and-exit
9695 @c @icon{gnus-summary-catchup-and-exit}
9696 Mark all unticked articles in the group as read and then exit
9697 (@code{gnus-summary-catchup-and-exit}).
9700 @kindex Z C (Summary)
9701 @findex gnus-summary-catchup-all-and-exit
9702 Mark all articles, even the ticked ones, as read and then exit
9703 (@code{gnus-summary-catchup-all-and-exit}).
9706 @kindex Z n (Summary)
9707 @findex gnus-summary-catchup-and-goto-next-group
9708 Mark all articles as read and go to the next group
9709 (@code{gnus-summary-catchup-and-goto-next-group}).
9712 @kindex Z R (Summary)
9713 @findex gnus-summary-reselect-current-group
9714 Exit this group, and then enter it again
9715 (@code{gnus-summary-reselect-current-group}). If given a prefix, select
9716 all articles, both read and unread.
9720 @kindex Z G (Summary)
9721 @kindex M-g (Summary)
9722 @findex gnus-summary-rescan-group
9723 @c @icon{gnus-summary-mail-get}
9724 Exit the group, check for new articles in the group, and select the
9725 group (@code{gnus-summary-rescan-group}). If given a prefix, select all
9726 articles, both read and unread.
9729 @kindex Z N (Summary)
9730 @findex gnus-summary-next-group
9731 Exit the group and go to the next group
9732 (@code{gnus-summary-next-group}).
9735 @kindex Z P (Summary)
9736 @findex gnus-summary-prev-group
9737 Exit the group and go to the previous group
9738 (@code{gnus-summary-prev-group}).
9741 @kindex Z s (Summary)
9742 @findex gnus-summary-save-newsrc
9743 Save the current number of read/marked articles in the dribble buffer
9744 and then save the dribble buffer (@code{gnus-summary-save-newsrc}). If
9745 given a prefix, also save the @file{.newsrc} file(s). Using this
9746 command will make exit without updating (the @kbd{Q} command) worthless.
9749 @vindex gnus-exit-group-hook
9750 @code{gnus-exit-group-hook} is called when you exit the current group
9751 with an ``updating'' exit. For instance @kbd{Q}
9752 (@code{gnus-summary-exit-no-update}) does not call this hook.
9754 @findex gnus-summary-wake-up-the-dead
9755 @findex gnus-dead-summary-mode
9756 @vindex gnus-kill-summary-on-exit
9757 If you're in the habit of exiting groups, and then changing your mind
9758 about it, you might set @code{gnus-kill-summary-on-exit} to @code{nil}.
9759 If you do that, Gnus won't kill the summary buffer when you exit it.
9760 (Quelle surprise!) Instead it will change the name of the buffer to
9761 something like @samp{*Dead Summary ... *} and install a minor mode
9762 called @code{gnus-dead-summary-mode}. Now, if you switch back to this
9763 buffer, you'll find that all keys are mapped to a function called
9764 @code{gnus-summary-wake-up-the-dead}. So tapping any keys in a dead
9765 summary buffer will result in a live, normal summary buffer.
9767 There will never be more than one dead summary buffer at any one time.
9769 @vindex gnus-use-cross-reference
9770 The data on the current group will be updated (which articles you have
9771 read, which articles you have replied to, etc.) when you exit the
9772 summary buffer. If the @code{gnus-use-cross-reference} variable is
9773 @code{t} (which is the default), articles that are cross-referenced to
9774 this group and are marked as read, will also be marked as read in the
9775 other subscribed groups they were cross-posted to. If this variable is
9776 neither @code{nil} nor @code{t}, the article will be marked as read in
9777 both subscribed and unsubscribed groups (@pxref{Crosspost Handling}).
9780 @node Crosspost Handling
9781 @section Crosspost Handling
9785 Marking cross-posted articles as read ensures that you'll never have to
9786 read the same article more than once. Unless, of course, somebody has
9787 posted it to several groups separately. Posting the same article to
9788 several groups (not cross-posting) is called @dfn{spamming}, and you are
9789 by law required to send nasty-grams to anyone who perpetrates such a
9790 heinous crime. You may want to try NoCeM handling to filter out spam
9793 Remember: Cross-posting is kinda ok, but posting the same article
9794 separately to several groups is not. Massive cross-posting (aka.
9795 @dfn{velveeta}) is to be avoided at all costs, and you can even use the
9796 @code{gnus-summary-mail-crosspost-complaint} command to complain about
9797 excessive crossposting (@pxref{Summary Mail Commands}).
9799 @cindex cross-posting
9802 One thing that may cause Gnus to not do the cross-posting thing
9803 correctly is if you use an @sc{nntp} server that supports @sc{xover}
9804 (which is very nice, because it speeds things up considerably) which
9805 does not include the @code{Xref} header in its @sc{nov} lines. This is
9806 Evil, but all too common, alas, alack. Gnus tries to Do The Right Thing
9807 even with @sc{xover} by registering the @code{Xref} lines of all
9808 articles you actually read, but if you kill the articles, or just mark
9809 them as read without reading them, Gnus will not get a chance to snoop
9810 the @code{Xref} lines out of these articles, and will be unable to use
9811 the cross reference mechanism.
9813 @cindex LIST overview.fmt
9814 @cindex overview.fmt
9815 To check whether your @sc{nntp} server includes the @code{Xref} header
9816 in its overview files, try @samp{telnet your.nntp.server nntp},
9817 @samp{MODE READER} on @code{inn} servers, and then say @samp{LIST
9818 overview.fmt}. This may not work, but if it does, and the last line you
9819 get does not read @samp{Xref:full}, then you should shout and whine at
9820 your news admin until she includes the @code{Xref} header in the
9823 @vindex gnus-nov-is-evil
9824 If you want Gnus to get the @code{Xref}s right all the time, you have to
9825 set @code{gnus-nov-is-evil} to @code{t}, which slows things down
9830 For an alternative approach, @pxref{Duplicate Suppression}.
9833 @node Duplicate Suppression
9834 @section Duplicate Suppression
9836 By default, Gnus tries to make sure that you don't have to read the same
9837 article more than once by utilizing the crossposting mechanism
9838 (@pxref{Crosspost Handling}). However, that simple and efficient
9839 approach may not work satisfactory for some users for various
9844 The @sc{nntp} server may fail to generate the @code{Xref} header. This
9845 is evil and not very common.
9848 The @sc{nntp} server may fail to include the @code{Xref} header in the
9849 @file{.overview} data bases. This is evil and all too common, alas.
9852 You may be reading the same group (or several related groups) from
9853 different @sc{nntp} servers.
9856 You may be getting mail that duplicates articles posted to groups.
9859 I'm sure there are other situations where @code{Xref} handling fails as
9860 well, but these four are the most common situations.
9862 If, and only if, @code{Xref} handling fails for you, then you may
9863 consider switching on @dfn{duplicate suppression}. If you do so, Gnus
9864 will remember the @code{Message-ID}s of all articles you have read or
9865 otherwise marked as read, and then, as if by magic, mark them as read
9866 all subsequent times you see them---in @emph{all} groups. Using this
9867 mechanism is quite likely to be somewhat inefficient, but not overly
9868 so. It's certainly preferable to reading the same articles more than
9871 Duplicate suppression is not a very subtle instrument. It's more like a
9872 sledge hammer than anything else. It works in a very simple
9873 fashion---if you have marked an article as read, it adds this Message-ID
9874 to a cache. The next time it sees this Message-ID, it will mark the
9875 article as read with the @samp{M} mark. It doesn't care what group it
9879 @item gnus-suppress-duplicates
9880 @vindex gnus-suppress-duplicates
9881 If non-@code{nil}, suppress duplicates.
9883 @item gnus-save-duplicate-list
9884 @vindex gnus-save-duplicate-list
9885 If non-@code{nil}, save the list of duplicates to a file. This will
9886 make startup and shutdown take longer, so the default is @code{nil}.
9887 However, this means that only duplicate articles read in a single Gnus
9888 session are suppressed.
9890 @item gnus-duplicate-list-length
9891 @vindex gnus-duplicate-list-length
9892 This variable says how many @code{Message-ID}s to keep in the duplicate
9893 suppression list. The default is 10000.
9895 @item gnus-duplicate-file
9896 @vindex gnus-duplicate-file
9897 The name of the file to store the duplicate suppression list in. The
9898 default is @file{~/News/suppression}.
9901 If you have a tendency to stop and start Gnus often, setting
9902 @code{gnus-save-duplicate-list} to @code{t} is probably a good idea. If
9903 you leave Gnus running for weeks on end, you may have it @code{nil}. On
9904 the other hand, saving the list makes startup and shutdown much slower,
9905 so that means that if you stop and start Gnus often, you should set
9906 @code{gnus-save-duplicate-list} to @code{nil}. Uhm. I'll leave this up
9907 to you to figure out, I think.
9912 Gnus is able to verify signed messages or decrypt encrypted messages.
9913 The formats that are supported are PGP, PGP/MIME and S/MIME, however
9914 you need some external programs to get things to work:
9918 To handle PGP messages, you have to install mailcrypt or gpg.el as
9919 well as a OpenPGP implementation (such as GnuPG).
9922 To handle S/MIME message, you need to install OpenSSL. OpenSSL 0.9.6
9923 or newer is recommended.
9927 More information on how to set things up can be found in the message
9928 manual (@pxref{Security, ,Security, message, Message Manual}).
9931 @item mm-verify-option
9932 @vindex mm-verify-option
9933 Option of verifying signed parts. @code{never}, not verify;
9934 @code{always}, always verify; @code{known}, only verify known
9935 protocols. Otherwise, ask user.
9937 @item mm-decrypt-option
9938 @vindex mm-decrypt-option
9939 Option of decrypting encrypted parts. @code{never}, no decryption;
9940 @code{always}, always decrypt; @code{known}, only decrypt known
9941 protocols. Otherwise, ask user.
9946 @section Mailing List
9948 Gnus understands some mailing list fields of RFC 2369. To enable it,
9949 either add a `to-list' group parameter (@pxref{Group Parameters}),
9950 possibly using @kbd{A M} in the summary buffer, or say:
9953 (add-hook 'gnus-summary-mode-hook 'turn-on-gnus-mailing-list-mode)
9956 That enables the following commands to the summary buffer:
9961 @kindex C-c C-n h (Summary)
9962 @findex gnus-mailing-list-help
9963 Send a message to fetch mailing list help, if List-Help field exists.
9966 @kindex C-c C-n s (Summary)
9967 @findex gnus-mailing-list-subscribe
9968 Send a message to subscribe the mailing list, if List-Subscribe field exists.
9971 @kindex C-c C-n u (Summary)
9972 @findex gnus-mailing-list-unsubscribe
9973 Send a message to unsubscribe the mailing list, if List-Unsubscribe
9977 @kindex C-c C-n p (Summary)
9978 @findex gnus-mailing-list-post
9979 Post to the mailing list, if List-Post field exists.
9982 @kindex C-c C-n o (Summary)
9983 @findex gnus-mailing-list-owner
9984 Send a message to the mailing list owner, if List-Owner field exists.
9987 @kindex C-c C-n a (Summary)
9988 @findex gnus-mailing-list-owner
9989 Browse the mailing list archive, if List-Archive field exists.
9993 @node Article Buffer
9994 @chapter Article Buffer
9995 @cindex article buffer
9997 The articles are displayed in the article buffer, of which there is only
9998 one. All the summary buffers share the same article buffer unless you
9999 tell Gnus otherwise.
10002 * Hiding Headers:: Deciding what headers should be displayed.
10003 * Using MIME:: Pushing articles through @sc{mime} before reading them.
10004 * Customizing Articles:: Tailoring the look of the articles.
10005 * Article Keymap:: Keystrokes available in the article buffer.
10006 * Misc Article:: Other stuff.
10010 @node Hiding Headers
10011 @section Hiding Headers
10012 @cindex hiding headers
10013 @cindex deleting headers
10015 The top section of each article is the @dfn{head}. (The rest is the
10016 @dfn{body}, but you may have guessed that already.)
10018 @vindex gnus-show-all-headers
10019 There is a lot of useful information in the head: the name of the person
10020 who wrote the article, the date it was written and the subject of the
10021 article. That's well and nice, but there's also lots of information
10022 most people do not want to see---what systems the article has passed
10023 through before reaching you, the @code{Message-ID}, the
10024 @code{References}, etc. ad nauseum---and you'll probably want to get rid
10025 of some of those lines. If you want to keep all those lines in the
10026 article buffer, you can set @code{gnus-show-all-headers} to @code{t}.
10028 Gnus provides you with two variables for sifting headers:
10032 @item gnus-visible-headers
10033 @vindex gnus-visible-headers
10034 If this variable is non-@code{nil}, it should be a regular expression
10035 that says what headers you wish to keep in the article buffer. All
10036 headers that do not match this variable will be hidden.
10038 For instance, if you only want to see the name of the person who wrote
10039 the article and the subject, you'd say:
10042 (setq gnus-visible-headers "^From:\\|^Subject:")
10045 This variable can also be a list of regexps to match headers to
10048 @item gnus-ignored-headers
10049 @vindex gnus-ignored-headers
10050 This variable is the reverse of @code{gnus-visible-headers}. If this
10051 variable is set (and @code{gnus-visible-headers} is @code{nil}), it
10052 should be a regular expression that matches all lines that you want to
10053 hide. All lines that do not match this variable will remain visible.
10055 For instance, if you just want to get rid of the @code{References} line
10056 and the @code{Xref} line, you might say:
10059 (setq gnus-ignored-headers "^References:\\|^Xref:")
10062 This variable can also be a list of regexps to match headers to
10065 Note that if @code{gnus-visible-headers} is non-@code{nil}, this
10066 variable will have no effect.
10070 @vindex gnus-sorted-header-list
10071 Gnus can also sort the headers for you. (It does this by default.) You
10072 can control the sorting by setting the @code{gnus-sorted-header-list}
10073 variable. It is a list of regular expressions that says in what order
10074 the headers are to be displayed.
10076 For instance, if you want the name of the author of the article first,
10077 and then the subject, you might say something like:
10080 (setq gnus-sorted-header-list '("^From:" "^Subject:"))
10083 Any headers that are to remain visible, but are not listed in this
10084 variable, will be displayed in random order after all the headers listed in this variable.
10086 @findex gnus-article-hide-boring-headers
10087 @vindex gnus-boring-article-headers
10088 You can hide further boring headers by setting
10089 @code{gnus-treat-hide-boring-headers} to @code{head}. What this function
10090 does depends on the @code{gnus-boring-article-headers} variable. It's a
10091 list, but this list doesn't actually contain header names. Instead is
10092 lists various @dfn{boring conditions} that Gnus can check and remove
10095 These conditions are:
10098 Remove all empty headers.
10100 Remove the @code{Followup-To} header if it is identical to the
10101 @code{Newsgroups} header.
10103 Remove the @code{Reply-To} header if it lists the same address as the
10104 @code{From} header.
10106 Remove the @code{Newsgroups} header if it only contains the current group
10109 Remove the @code{To} header if it only contains the address identical to
10110 the current groups's @code{to-address} parameter.
10112 Remove the @code{Date} header if the article is less than three days
10115 Remove the @code{To} header if it is very long.
10117 Remove all @code{To} headers if there are more than one.
10120 To include these three elements, you could say something like;
10123 (setq gnus-boring-article-headers
10124 '(empty followup-to reply-to))
10127 This is also the default value for this variable.
10131 @section Using MIME
10134 Mime is a standard for waving your hands through the air, aimlessly,
10135 while people stand around yawning.
10137 @sc{mime}, however, is a standard for encoding your articles, aimlessly,
10138 while all newsreaders die of fear.
10140 @sc{mime} may specify what character set the article uses, the encoding
10141 of the characters, and it also makes it possible to embed pictures and
10142 other naughty stuff in innocent-looking articles.
10144 @vindex gnus-display-mime-function
10145 @findex gnus-display-mime
10146 Gnus pushes @sc{mime} articles through @code{gnus-display-mime-function}
10147 to display the @sc{mime} parts. This is @code{gnus-display-mime} by
10148 default, which creates a bundle of clickable buttons that can be used to
10149 display, save and manipulate the @sc{mime} objects.
10151 The following commands are available when you have placed point over a
10155 @findex gnus-article-press-button
10156 @item RET (Article)
10157 @kindex RET (Article)
10158 @itemx BUTTON-2 (Article)
10159 Toggle displaying of the @sc{mime} object
10160 (@code{gnus-article-press-button}).
10162 @findex gnus-mime-view-part
10163 @item M-RET (Article)
10164 @kindex M-RET (Article)
10166 Prompt for a method, and then view the @sc{mime} object using this
10167 method (@code{gnus-mime-view-part}).
10169 @findex gnus-mime-view-part-as-type
10171 @kindex t (Article)
10172 View the @sc{mime} object as if it were a different @sc{mime} media type
10173 (@code{gnus-mime-view-part-as-type}).
10175 @findex gnus-mime-view-part-as-charset
10177 @kindex C (Article)
10178 Prompt for a charset, and then view the @sc{mime} object using this
10179 charset (@code{gnus-mime-view-part-as-charset}).
10181 @findex gnus-mime-save-part
10183 @kindex o (Article)
10184 Prompt for a file name, and then save the @sc{mime} object
10185 (@code{gnus-mime-save-part}).
10187 @findex gnus-mime-save-part-and-strip
10188 @item C-o (Article)
10189 @kindex C-o (Article)
10190 Prompt for a file name, then save the @sc{mime} object and strip it from
10191 the article. Then proceed to article editing, where a reasonable
10192 suggestion is being made on how the altered article should look
10193 like. The stripped @sc{mime} object will be referred via the
10194 message/external-body @sc{mime} type.
10195 (@code{gnus-mime-save-part-and-strip}).
10197 @findex gnus-mime-copy-part
10199 @kindex c (Article)
10200 Copy the @sc{mime} object to a fresh buffer and display this buffer
10201 (@code{gnus-mime-copy-part}).
10203 @findex gnus-mime-print-part
10205 @kindex p (Article)
10206 Print the @sc{mime} object (@code{gnus-mime-print-part}). This
10207 command respects the @samp{print=} specifications in the
10208 @file{.mailcap} file.
10210 @findex gnus-mime-inline-part
10212 @kindex i (Article)
10213 Insert the contents of the @sc{mime} object into the buffer
10214 (@code{gnus-mime-inline-part}) as text/plain. If given a prefix, insert
10215 the raw contents without decoding. If given a numerical prefix, you can
10216 do semi-manual charset stuff (see
10217 @code{gnus-summary-show-article-charset-alist} in @pxref{Paging the
10220 @findex gnus-mime-internalize-part
10222 @kindex E (Article)
10223 View the @sc{mime} object with an internal viewer. If no internal
10224 viewer is available, use an external viewer
10225 (@code{gnus-mime-internalize-part}).
10227 @findex gnus-mime-externalize-part
10229 @kindex e (Article)
10230 View the @sc{mime} object with an external viewer.
10231 (@code{gnus-mime-externalize-part}).
10233 @findex gnus-mime-pipe-part
10235 @kindex | (Article)
10236 Output the @sc{mime} object to a process (@code{gnus-mime-pipe-part}).
10238 @findex gnus-mime-action-on-part
10240 @kindex . (Article)
10241 Interactively run an action on the @sc{mime} object
10242 (@code{gnus-mime-action-on-part}).
10246 Gnus will display some @sc{mime} objects automatically. The way Gnus
10247 determines which parts to do this with is described in the Emacs MIME
10250 It might be best to just use the toggling functions from the article
10251 buffer to avoid getting nasty surprises. (For instance, you enter the
10252 group @samp{alt.sing-a-long} and, before you know it, @sc{mime} has
10253 decoded the sound file in the article and some horrible sing-a-long song
10254 comes screaming out your speakers, and you can't find the volume button,
10255 because there isn't one, and people are starting to look at you, and you
10256 try to stop the program, but you can't, and you can't find the program
10257 to control the volume, and everybody else in the room suddenly decides
10258 to look at you disdainfully, and you'll feel rather stupid.)
10260 Any similarity to real events and people is purely coincidental. Ahem.
10262 Also see @pxref{MIME Commands}.
10265 @node Customizing Articles
10266 @section Customizing Articles
10267 @cindex article customization
10269 A slew of functions for customizing how the articles are to look like
10270 exist. You can call these functions interactively, or you can have them
10271 called automatically when you select the articles.
10273 To have them called automatically, you should set the corresponding
10274 ``treatment'' variable. For instance, to have headers hidden, you'd set
10275 @code{gnus-treat-hide-headers}. Below is a list of variables that can
10276 be set, but first we discuss the values these variables can have.
10278 Note: Some values, while valid, make little sense. Check the list below
10279 for sensible values.
10283 @code{nil}: Don't do this treatment.
10286 @code{t}: Do this treatment on all body parts.
10289 @code{head}: Do the treatment on the headers.
10292 @code{last}: Do this treatment on the last part.
10295 An integer: Do this treatment on all body parts that have a length less
10299 A list of strings: Do this treatment on all body parts that are in
10300 articles that are read in groups that have names that match one of the
10301 regexps in the list.
10304 A list where the first element is not a string:
10306 The list is evaluated recursively. The first element of the list is a
10307 predicate. The following predicates are recognized: @code{or},
10308 @code{and}, @code{not} and @code{typep}. Here's an example:
10312 (typep "text/x-vcard"))
10317 You may have noticed that the word @dfn{part} is used here. This refers
10318 to the fact that some messages are @sc{mime} multipart articles that may
10319 be divided into several parts. Articles that are not multiparts are
10320 considered to contain just a single part.
10322 @vindex gnus-article-treat-types
10323 Are the treatments applied to all sorts of multipart parts? Yes, if you
10324 want to, but by default, only @samp{text/plain} parts are given the
10325 treatment. This is controlled by the @code{gnus-article-treat-types}
10326 variable, which is a list of regular expressions that are matched to the
10327 type of the part. This variable is ignored if the value of the
10328 controlling variable is a predicate list, as described above.
10330 The following treatment options are available. The easiest way to
10331 customize this is to examine the @code{gnus-article-treat} customization
10332 group. Values in parenthesis are suggested sensible values. Others are
10333 possible but those listed are probably sufficient for most people.
10336 @item gnus-treat-buttonize (t, integer)
10337 @item gnus-treat-buttonize-head (head)
10339 @xref{Article Buttons}.
10341 @item gnus-treat-capitalize-sentences (t, integer)
10342 @item gnus-treat-overstrike (t, integer)
10343 @item gnus-treat-strip-cr (t, integer)
10344 @item gnus-treat-strip-headers-in-body (t, integer)
10345 @item gnus-treat-strip-leading-blank-lines (t, integer)
10346 @item gnus-treat-strip-multiple-blank-lines (t, integer)
10347 @item gnus-treat-strip-pem (t, last, integer)
10348 @item gnus-treat-strip-pgp (t, last, integer)
10349 @item gnus-treat-strip-trailing-blank-lines (t, last, integer)
10351 @xref{Article Washing}.
10353 @item gnus-treat-date-english (head)
10354 @item gnus-treat-date-iso8601 (head)
10355 @item gnus-treat-date-lapsed (head)
10356 @item gnus-treat-date-local (head)
10357 @item gnus-treat-date-original (head)
10358 @item gnus-treat-date-user-defined (head)
10359 @item gnus-treat-date-ut (head)
10361 @xref{Article Date}.
10363 @item gnus-treat-from-picon (head)
10364 @item gnus-treat-mail-picon (head)
10365 @item gnus-treat-newsgroups-picon (head)
10369 @item gnus-treat-display-smileys (t, integer)
10371 @item gnus-treat-body-boundary (head)
10373 @vindex gnus-body-boundary-delimiter
10374 Adds a delimiter between header and body, the string used as delimiter
10375 is controlled by @code{gnus-body-boundary-delimiter}.
10379 @item gnus-treat-display-xface (head)
10383 @item gnus-treat-emphasize (t, head, integer)
10384 @item gnus-treat-fill-article (t, integer)
10385 @item gnus-treat-fill-long-lines (t, integer)
10386 @item gnus-treat-hide-boring-headers (head)
10387 @item gnus-treat-hide-citation (t, integer)
10388 @item gnus-treat-hide-citation-maybe (t, integer)
10389 @item gnus-treat-hide-headers (head)
10390 @item gnus-treat-hide-signature (t, last)
10392 @xref{Article Hiding}.
10394 @item gnus-treat-highlight-citation (t, integer)
10395 @item gnus-treat-highlight-headers (head)
10396 @item gnus-treat-highlight-signature (t, last, integer)
10398 @xref{Article Highlighting}.
10400 @item gnus-treat-play-sounds
10401 @item gnus-treat-translate
10402 @item gnus-treat-x-pgp-sig (head)
10404 @item gnus-treat-unfold-headers (head)
10405 @item gnus-treat-fold-headers (head)
10406 @item gnus-treat-fold-newsgroups (head)
10412 @vindex gnus-part-display-hook
10413 You can, of course, write your own functions to be called from
10414 @code{gnus-part-display-hook}. The functions are called narrowed to the
10415 part, and you can do anything you like, pretty much. There is no
10416 information that you have to keep in the buffer---you can change
10420 @node Article Keymap
10421 @section Article Keymap
10423 Most of the keystrokes in the summary buffer can also be used in the
10424 article buffer. They should behave as if you typed them in the summary
10425 buffer, which means that you don't actually have to have a summary
10426 buffer displayed while reading. You can do it all from the article
10429 A few additional keystrokes are available:
10434 @kindex SPACE (Article)
10435 @findex gnus-article-next-page
10436 Scroll forwards one page (@code{gnus-article-next-page}).
10439 @kindex DEL (Article)
10440 @findex gnus-article-prev-page
10441 Scroll backwards one page (@code{gnus-article-prev-page}).
10444 @kindex C-c ^ (Article)
10445 @findex gnus-article-refer-article
10446 If point is in the neighborhood of a @code{Message-ID} and you press
10447 @kbd{C-c ^}, Gnus will try to get that article from the server
10448 (@code{gnus-article-refer-article}).
10451 @kindex C-c C-m (Article)
10452 @findex gnus-article-mail
10453 Send a reply to the address near point (@code{gnus-article-mail}). If
10454 given a prefix, include the mail.
10457 @kindex s (Article)
10458 @findex gnus-article-show-summary
10459 Reconfigure the buffers so that the summary buffer becomes visible
10460 (@code{gnus-article-show-summary}).
10463 @kindex ? (Article)
10464 @findex gnus-article-describe-briefly
10465 Give a very brief description of the available keystrokes
10466 (@code{gnus-article-describe-briefly}).
10469 @kindex TAB (Article)
10470 @findex gnus-article-next-button
10471 Go to the next button, if any (@code{gnus-article-next-button}). This
10472 only makes sense if you have buttonizing turned on.
10475 @kindex M-TAB (Article)
10476 @findex gnus-article-prev-button
10477 Go to the previous button, if any (@code{gnus-article-prev-button}).
10480 @kindex R (Article)
10481 @findex gnus-article-reply-with-original
10482 Send a reply to the current article and yank the current article
10483 (@code{gnus-article-reply-with-original}). If given a prefix, make a
10484 wide reply. If the region is active, only yank the text in the
10488 @kindex F (Article)
10489 @findex gnus-article-followup-with-original
10490 Send a followup to the current article and yank the current article
10491 (@code{gnus-article-followup-with-original}). If given a prefix, make
10492 a wide reply. If the region is active, only yank the text in the
10500 @section Misc Article
10504 @item gnus-single-article-buffer
10505 @vindex gnus-single-article-buffer
10506 If non-@code{nil}, use the same article buffer for all the groups.
10507 (This is the default.) If @code{nil}, each group will have its own
10510 @vindex gnus-article-decode-hook
10511 @item gnus-article-decode-hook
10513 Hook used to decode @sc{mime} articles. The default value is
10514 @code{(article-decode-charset article-decode-encoded-words)}
10516 @vindex gnus-article-prepare-hook
10517 @item gnus-article-prepare-hook
10518 This hook is called right after the article has been inserted into the
10519 article buffer. It is mainly intended for functions that do something
10520 depending on the contents; it should probably not be used for changing
10521 the contents of the article buffer.
10523 @item gnus-article-mode-hook
10524 @vindex gnus-article-mode-hook
10525 Hook called in article mode buffers.
10527 @item gnus-article-mode-syntax-table
10528 @vindex gnus-article-mode-syntax-table
10529 Syntax table used in article buffers. It is initialized from
10530 @code{text-mode-syntax-table}.
10532 @vindex gnus-article-mode-line-format
10533 @item gnus-article-mode-line-format
10534 This variable is a format string along the same lines as
10535 @code{gnus-summary-mode-line-format} (@pxref{Mode Line Formatting}). It
10536 accepts the same format specifications as that variable, with two
10542 The @dfn{wash status} of the article. This is a short string with one
10543 character for each possible article wash operation that may have been
10544 performed. The characters and their meaning:
10549 Displayed when cited text may be hidden in the article buffer.
10552 Displayed when headers are hidden in the article buffer.
10555 Displayed when article is digitally signed or encrypted, and Gnus has
10556 hidden the security headers. (N.B. does not tell anything about
10557 security status, i.e. good or bad signature.)
10560 Displayed when the signature has been hidden in the Article buffer.
10563 Displayed when Gnus has treated overstrike characters in the article buffer.
10566 Displayed when Gnus has treated emphasised strings in the article buffer.
10571 The number of @sc{mime} parts in the article.
10575 @vindex gnus-break-pages
10577 @item gnus-break-pages
10578 Controls whether @dfn{page breaking} is to take place. If this variable
10579 is non-@code{nil}, the articles will be divided into pages whenever a
10580 page delimiter appears in the article. If this variable is @code{nil},
10581 paging will not be done.
10583 @item gnus-page-delimiter
10584 @vindex gnus-page-delimiter
10585 This is the delimiter mentioned above. By default, it is @samp{^L}
10590 @node Composing Messages
10591 @chapter Composing Messages
10592 @cindex composing messages
10595 @cindex sending mail
10600 @cindex using s/mime
10601 @cindex using smime
10603 @kindex C-c C-c (Post)
10604 All commands for posting and mailing will put you in a message buffer
10605 where you can edit the article all you like, before you send the
10606 article by pressing @kbd{C-c C-c}. @xref{Top, , Overview, message,
10607 Message Manual}. Where the message will be posted/mailed to depends
10608 on your setup (@pxref{Posting Server}).
10611 * Mail:: Mailing and replying.
10612 * Posting Server:: What server should you post via?
10613 * Mail and Post:: Mailing and posting at the same time.
10614 * Archived Messages:: Where Gnus stores the messages you've sent.
10615 * Posting Styles:: An easier way to specify who you are.
10616 * Drafts:: Postponing messages and rejected messages.
10617 * Rejected Articles:: What happens if the server doesn't like your article?
10618 * Signing and encrypting:: How to compose secure messages.
10621 Also see @pxref{Canceling and Superseding} for information on how to
10622 remove articles you shouldn't have posted.
10628 Variables for customizing outgoing mail:
10631 @item gnus-uu-digest-headers
10632 @vindex gnus-uu-digest-headers
10633 List of regexps to match headers included in digested messages. The
10634 headers will be included in the sequence they are matched.
10636 @item gnus-add-to-list
10637 @vindex gnus-add-to-list
10638 If non-@code{nil}, add a @code{to-list} group parameter to mail groups
10639 that have none when you do a @kbd{a}.
10644 @node Posting Server
10645 @section Posting Server
10647 When you press those magical @kbd{C-c C-c} keys to ship off your latest
10648 (extremely intelligent, of course) article, where does it go?
10650 Thank you for asking. I hate you.
10652 @vindex gnus-post-method
10654 It can be quite complicated. Normally, Gnus will post using the same
10655 select method as you're reading from (which might be convenient if
10656 you're reading lots of groups from different private servers).
10657 However. If the server you're reading from doesn't allow posting,
10658 just reading, you probably want to use some other server to post your
10659 (extremely intelligent and fabulously interesting) articles. You can
10660 then set the @code{gnus-post-method} to some other method:
10663 (setq gnus-post-method '(nnspool ""))
10666 Now, if you've done this, and then this server rejects your article, or
10667 this server is down, what do you do then? To override this variable you
10668 can use a non-zero prefix to the @kbd{C-c C-c} command to force using
10669 the ``current'' server, to get back the default behavior, for posting.
10671 If you give a zero prefix (i.e., @kbd{C-u 0 C-c C-c}) to that command,
10672 Gnus will prompt you for what method to use for posting.
10674 You can also set @code{gnus-post-method} to a list of select methods.
10675 If that's the case, Gnus will always prompt you for what method to use
10678 Finally, if you want to always post using the native select method,
10679 you can set this variable to @code{native}.
10682 @node Mail and Post
10683 @section Mail and Post
10685 Here's a list of variables relevant to both mailing and
10689 @item gnus-mailing-list-groups
10690 @findex gnus-mailing-list-groups
10691 @cindex mailing lists
10693 If your news server offers groups that are really mailing lists
10694 gatewayed to the @sc{nntp} server, you can read those groups without
10695 problems, but you can't post/followup to them without some difficulty.
10696 One solution is to add a @code{to-address} to the group parameters
10697 (@pxref{Group Parameters}). An easier thing to do is set the
10698 @code{gnus-mailing-list-groups} to a regexp that matches the groups that
10699 really are mailing lists. Then, at least, followups to the mailing
10700 lists will work most of the time. Posting to these groups (@kbd{a}) is
10701 still a pain, though.
10705 You may want to do spell-checking on messages that you send out. Or, if
10706 you don't want to spell-check by hand, you could add automatic
10707 spell-checking via the @code{ispell} package:
10710 @findex ispell-message
10712 (add-hook 'message-send-hook 'ispell-message)
10715 If you want to change the @code{ispell} dictionary based on what group
10716 you're in, you could say something like the following:
10719 (add-hook 'gnus-select-group-hook
10723 "^de\\." (gnus-group-real-name gnus-newsgroup-name))
10724 (ispell-change-dictionary "deutsch"))
10726 (ispell-change-dictionary "english")))))
10729 Modify to suit your needs.
10732 @node Archived Messages
10733 @section Archived Messages
10734 @cindex archived messages
10735 @cindex sent messages
10737 Gnus provides a few different methods for storing the mail and news you
10738 send. The default method is to use the @dfn{archive virtual server} to
10739 store the messages. If you want to disable this completely, the
10740 @code{gnus-message-archive-group} variable should be @code{nil}, which
10743 @vindex gnus-message-archive-method
10744 @code{gnus-message-archive-method} says what virtual server Gnus is to
10745 use to store sent messages. The default is:
10748 (nnfolder "archive"
10749 (nnfolder-directory "~/Mail/archive")
10750 (nnfolder-active-file "~/Mail/archive/active")
10751 (nnfolder-get-new-mail nil)
10752 (nnfolder-inhibit-expiry t))
10755 You can, however, use any mail select method (@code{nnml},
10756 @code{nnmbox}, etc.). @code{nnfolder} is a quite likable select method
10757 for doing this sort of thing, though. If you don't like the default
10758 directory chosen, you could say something like:
10761 (setq gnus-message-archive-method
10762 '(nnfolder "archive"
10763 (nnfolder-inhibit-expiry t)
10764 (nnfolder-active-file "~/News/sent-mail/active")
10765 (nnfolder-directory "~/News/sent-mail/")))
10768 @vindex gnus-message-archive-group
10770 Gnus will insert @code{Gcc} headers in all outgoing messages that point
10771 to one or more group(s) on that server. Which group to use is
10772 determined by the @code{gnus-message-archive-group} variable.
10774 This variable can be used to do the following:
10779 Messages will be saved in that group.
10781 Note that you can include a select method in the group name, then the
10782 message will not be stored in the select method given by
10783 @code{gnus-message-archive-method}, but in the select method specified
10784 by the group name, instead. Suppose @code{gnus-message-archive-method}
10785 has the default value shown above. Then setting
10786 @code{gnus-message-archive-group} to @code{"foo"} means that outgoing
10787 messages are stored in @samp{nnfolder+archive:foo}, but if you use the
10788 value @code{"nnml:foo"}, then outgoing messages will be stored in
10792 Messages will be saved in all those groups.
10794 an alist of regexps, functions and forms
10795 When a key ``matches'', the result is used.
10798 No message archiving will take place. This is the default.
10803 Just saving to a single group called @samp{MisK}:
10805 (setq gnus-message-archive-group "MisK")
10808 Saving to two groups, @samp{MisK} and @samp{safe}:
10810 (setq gnus-message-archive-group '("MisK" "safe"))
10813 Save to different groups based on what group you are in:
10815 (setq gnus-message-archive-group
10816 '(("^alt" "sent-to-alt")
10817 ("mail" "sent-to-mail")
10818 (".*" "sent-to-misc")))
10821 More complex stuff:
10823 (setq gnus-message-archive-group
10824 '((if (message-news-p)
10829 How about storing all news messages in one file, but storing all mail
10830 messages in one file per month:
10833 (setq gnus-message-archive-group
10834 '((if (message-news-p)
10836 (concat "mail." (format-time-string "%Y-%m")))))
10839 @c (XEmacs 19.13 doesn't have @code{format-time-string}, so you'll have to
10840 @c use a different value for @code{gnus-message-archive-group} there.)
10842 Now, when you send a message off, it will be stored in the appropriate
10843 group. (If you want to disable storing for just one particular message,
10844 you can just remove the @code{Gcc} header that has been inserted.) The
10845 archive group will appear in the group buffer the next time you start
10846 Gnus, or the next time you press @kbd{F} in the group buffer. You can
10847 enter it and read the articles in it just like you'd read any other
10848 group. If the group gets really big and annoying, you can simply rename
10849 if (using @kbd{G r} in the group buffer) to something
10850 nice---@samp{misc-mail-september-1995}, or whatever. New messages will
10851 continue to be stored in the old (now empty) group.
10853 That's the default method of archiving sent messages. Gnus offers a
10854 different way for the people who don't like the default method. In that
10855 case you should set @code{gnus-message-archive-group} to @code{nil};
10856 this will disable archiving.
10859 @item gnus-outgoing-message-group
10860 @vindex gnus-outgoing-message-group
10861 All outgoing messages will be put in this group. If you want to store
10862 all your outgoing mail and articles in the group @samp{nnml:archive},
10863 you set this variable to that value. This variable can also be a list of
10866 If you want to have greater control over what group to put each
10867 message in, you can set this variable to a function that checks the
10868 current newsgroup name and then returns a suitable group name (or list
10871 This variable can be used instead of @code{gnus-message-archive-group},
10872 but the latter is the preferred method.
10874 @item gnus-gcc-mark-as-read
10875 @vindex gnus-gcc-mark-as-read
10876 If non-@code{nil}, automatically mark @code{Gcc} articles as read.
10881 @node Posting Styles
10882 @section Posting Styles
10883 @cindex posting styles
10886 All them variables, they make my head swim.
10888 So what if you want a different @code{Organization} and signature based
10889 on what groups you post to? And you post both from your home machine
10890 and your work machine, and you want different @code{From} lines, and so
10893 @vindex gnus-posting-styles
10894 One way to do stuff like that is to write clever hooks that change the
10895 variables you need to have changed. That's a bit boring, so somebody
10896 came up with the bright idea of letting the user specify these things in
10897 a handy alist. Here's an example of a @code{gnus-posting-styles}
10902 (signature "Peace and happiness")
10903 (organization "What me?"))
10905 (signature "Death to everybody"))
10906 ("comp.emacs.i-love-it"
10907 (organization "Emacs is it")))
10910 As you might surmise from this example, this alist consists of several
10911 @dfn{styles}. Each style will be applicable if the first element
10912 ``matches'', in some form or other. The entire alist will be iterated
10913 over, from the beginning towards the end, and each match will be
10914 applied, which means that attributes in later styles that match override
10915 the same attributes in earlier matching styles. So
10916 @samp{comp.programming.literate} will have the @samp{Death to everybody}
10917 signature and the @samp{What me?} @code{Organization} header.
10919 The first element in each style is called the @code{match}. If it's a
10920 string, then Gnus will try to regexp match it against the group name.
10921 If it is the symbol @code{header}, then Gnus will look for header (the
10922 next element in the match) in the original article , and compare that to
10923 the last regexp in the match. If it's a function symbol, that function
10924 will be called with no arguments. If it's a variable symbol, then the
10925 variable will be referenced. If it's a list, then that list will be
10926 @code{eval}ed. In any case, if this returns a non-@code{nil} value,
10927 then the style is said to @dfn{match}.
10929 Each style may contain a arbitrary amount of @dfn{attributes}. Each
10930 attribute consists of a @code{(@var{name} @var{value})} pair. The
10931 attribute name can be one of @code{signature}, @code{signature-file},
10932 @code{organization}, @code{address}, @code{name} or @code{body}. The
10933 attribute name can also be a string. In that case, this will be used as
10934 a header name, and the value will be inserted in the headers of the
10935 article; if the value is @code{nil}, the header name will be removed.
10936 If the attribute name is @code{eval}, the form is evaluated, and the
10937 result is thrown away.
10939 The attribute value can be a string (used verbatim), a function with
10940 zero arguments (the return value will be used), a variable (its value
10941 will be used) or a list (it will be @code{eval}ed and the return value
10942 will be used). The functions and sexps are called/@code{eval}ed in the
10943 message buffer that is being set up. The headers of the current article
10944 are available through the @code{message-reply-headers} variable.
10946 If you wish to check whether the message you are about to compose is
10947 meant to be a news article or a mail message, you can check the values
10948 of the @code{message-news-p} and @code{message-mail-p} functions.
10950 @findex message-mail-p
10951 @findex message-news-p
10953 So here's a new example:
10956 (setq gnus-posting-styles
10958 (signature-file "~/.signature")
10960 ("X-Home-Page" (getenv "WWW_HOME"))
10961 (organization "People's Front Against MWM"))
10963 (signature my-funny-signature-randomizer))
10964 ((equal (system-name) "gnarly")
10965 (signature my-quote-randomizer))
10967 (signature my-news-signature))
10968 (header "to" "larsi.*org"
10969 (Organization "Somewhere, Inc."))
10970 ((posting-from-work-p)
10971 (signature-file "~/.work-signature")
10972 (address "user@@bar.foo")
10973 (body "You are fired.\n\nSincerely, your boss.")
10974 (organization "Important Work, Inc"))
10976 (From (save-excursion
10977 (set-buffer gnus-article-buffer)
10978 (message-fetch-field "to"))))
10980 (signature-file "~/.mail-signature"))))
10983 The @samp{nnml:.*} rule means that you use the @code{To} address as the
10984 @code{From} address in all your outgoing replies, which might be handy
10985 if you fill many roles.
10992 If you are writing a message (mail or news) and suddenly remember that
10993 you have a steak in the oven (or some pesto in the food processor, you
10994 craaazy vegetarians), you'll probably wish there was a method to save
10995 the message you are writing so that you can continue editing it some
10996 other day, and send it when you feel its finished.
10998 Well, don't worry about it. Whenever you start composing a message of
10999 some sort using the Gnus mail and post commands, the buffer you get will
11000 automatically associate to an article in a special @dfn{draft} group.
11001 If you save the buffer the normal way (@kbd{C-x C-s}, for instance), the
11002 article will be saved there. (Auto-save files also go to the draft
11006 @vindex nndraft-directory
11007 The draft group is a special group (which is implemented as an
11008 @code{nndraft} group, if you absolutely have to know) called
11009 @samp{nndraft:drafts}. The variable @code{nndraft-directory} says where
11010 @code{nndraft} is to store its files. What makes this group special is
11011 that you can't tick any articles in it or mark any articles as
11012 read---all articles in the group are permanently unread.
11014 If the group doesn't exist, it will be created and you'll be subscribed
11015 to it. The only way to make it disappear from the Group buffer is to
11018 @c @findex gnus-dissociate-buffer-from-draft
11019 @c @kindex C-c M-d (Mail)
11020 @c @kindex C-c M-d (Post)
11021 @c @findex gnus-associate-buffer-with-draft
11022 @c @kindex C-c C-d (Mail)
11023 @c @kindex C-c C-d (Post)
11024 @c If you're writing some super-secret message that you later want to
11025 @c encode with PGP before sending, you may wish to turn the auto-saving
11026 @c (and association with the draft group) off. You never know who might be
11027 @c interested in reading all your extremely valuable and terribly horrible
11028 @c and interesting secrets. The @kbd{C-c M-d}
11029 @c (@code{gnus-dissociate-buffer-from-draft}) command does that for you.
11030 @c If you change your mind and want to turn the auto-saving back on again,
11031 @c @kbd{C-c C-d} (@code{gnus-associate-buffer-with-draft} does that.
11033 @c @vindex gnus-use-draft
11034 @c To leave association with the draft group off by default, set
11035 @c @code{gnus-use-draft} to @code{nil}. It is @code{t} by default.
11037 @findex gnus-draft-edit-message
11038 @kindex D e (Draft)
11039 When you want to continue editing the article, you simply enter the
11040 draft group and push @kbd{D e} (@code{gnus-draft-edit-message}) to do
11041 that. You will be placed in a buffer where you left off.
11043 Rejected articles will also be put in this draft group (@pxref{Rejected
11046 @findex gnus-draft-send-all-messages
11047 @findex gnus-draft-send-message
11048 If you have lots of rejected messages you want to post (or mail) without
11049 doing further editing, you can use the @kbd{D s} command
11050 (@code{gnus-draft-send-message}). This command understands the
11051 process/prefix convention (@pxref{Process/Prefix}). The @kbd{D S}
11052 command (@code{gnus-draft-send-all-messages}) will ship off all messages
11055 If you have some messages that you wish not to send, you can use the
11056 @kbd{D t} (@code{gnus-draft-toggle-sending}) command to mark the message
11057 as unsendable. This is a toggling command.
11060 @node Rejected Articles
11061 @section Rejected Articles
11062 @cindex rejected articles
11064 Sometimes a news server will reject an article. Perhaps the server
11065 doesn't like your face. Perhaps it just feels miserable. Perhaps
11066 @emph{there be demons}. Perhaps you have included too much cited text.
11067 Perhaps the disk is full. Perhaps the server is down.
11069 These situations are, of course, totally beyond the control of Gnus.
11070 (Gnus, of course, loves the way you look, always feels great, has angels
11071 fluttering around inside of it, doesn't care about how much cited text
11072 you include, never runs full and never goes down.) So Gnus saves these
11073 articles until some later time when the server feels better.
11075 The rejected articles will automatically be put in a special draft group
11076 (@pxref{Drafts}). When the server comes back up again, you'd then
11077 typically enter that group and send all the articles off.
11079 @node Signing and encrypting
11080 @section Signing and encrypting
11082 @cindex using s/mime
11083 @cindex using smime
11085 Gnus can digitally sign and encrypt your messages, using vanilla PGP
11086 format or PGP/MIME or S/MIME. For decoding such messages, see the
11087 @code{mm-verify-option} and @code{mm-decrypt-option} options
11088 (@pxref{Security}).
11090 For PGP, Gnus supports two external libraries, @sc{gpg.el} and
11091 @sc{Mailcrypt}, you need to install at least one of them. The S/MIME
11092 support in Gnus requires the external program OpenSSL.
11094 Instructing MML to perform security operations on a MIME part is done
11095 using the @code{C-c C-m s} key map for signing and the @code{C-c C-m
11096 c} key map for encryption, as follows.
11101 @kindex C-c C-m s s
11102 @findex mml-secure-sign-smime
11104 Digitally sign current MIME part using S/MIME.
11107 @kindex C-c C-m s o
11108 @findex mml-secure-sign-pgp
11110 Digitally sign current MIME part using PGP.
11113 @kindex C-c C-m s p
11114 @findex mml-secure-sign-pgp
11116 Digitally sign current MIME part using PGP/MIME.
11119 @kindex C-c C-m c s
11120 @findex mml-secure-encrypt-smime
11122 Digitally encrypt current MIME part using S/MIME.
11125 @kindex C-c C-m c o
11126 @findex mml-secure-encrypt-pgp
11128 Digitally encrypt current MIME part using PGP.
11131 @kindex C-c C-m c p
11132 @findex mml-secure-encrypt-pgpmime
11134 Digitally encrypt current MIME part using PGP/MIME.
11138 Also @xref{Security, ,Security, message, Message Manual}.
11140 @node Select Methods
11141 @chapter Select Methods
11142 @cindex foreign groups
11143 @cindex select methods
11145 A @dfn{foreign group} is a group not read by the usual (or
11146 default) means. It could be, for instance, a group from a different
11147 @sc{nntp} server, it could be a virtual group, or it could be your own
11148 personal mail group.
11150 A foreign group (or any group, really) is specified by a @dfn{name} and
11151 a @dfn{select method}. To take the latter first, a select method is a
11152 list where the first element says what back end to use (e.g. @code{nntp},
11153 @code{nnspool}, @code{nnml}) and the second element is the @dfn{server
11154 name}. There may be additional elements in the select method, where the
11155 value may have special meaning for the back end in question.
11157 One could say that a select method defines a @dfn{virtual server}---so
11158 we do just that (@pxref{Server Buffer}).
11160 The @dfn{name} of the group is the name the back end will recognize the
11163 For instance, the group @samp{soc.motss} on the @sc{nntp} server
11164 @samp{some.where.edu} will have the name @samp{soc.motss} and select
11165 method @code{(nntp "some.where.edu")}. Gnus will call this group
11166 @samp{nntp+some.where.edu:soc.motss}, even though the @code{nntp}
11167 back end just knows this group as @samp{soc.motss}.
11169 The different methods all have their peculiarities, of course.
11172 * Server Buffer:: Making and editing virtual servers.
11173 * Getting News:: Reading USENET news with Gnus.
11174 * Getting Mail:: Reading your personal mail with Gnus.
11175 * Browsing the Web:: Getting messages from a plethora of Web sources.
11176 * IMAP:: Using Gnus as a @sc{imap} client.
11177 * Other Sources:: Reading directories, files, SOUP packets.
11178 * Combined Groups:: Combining groups into one group.
11179 * Gnus Unplugged:: Reading news and mail offline.
11183 @node Server Buffer
11184 @section Server Buffer
11186 Traditionally, a @dfn{server} is a machine or a piece of software that
11187 one connects to, and then requests information from. Gnus does not
11188 connect directly to any real servers, but does all transactions through
11189 one back end or other. But that's just putting one layer more between
11190 the actual media and Gnus, so we might just as well say that each
11191 back end represents a virtual server.
11193 For instance, the @code{nntp} back end may be used to connect to several
11194 different actual @sc{nntp} servers, or, perhaps, to many different ports
11195 on the same actual @sc{nntp} server. You tell Gnus which back end to
11196 use, and what parameters to set by specifying a @dfn{select method}.
11198 These select method specifications can sometimes become quite
11199 complicated---say, for instance, that you want to read from the
11200 @sc{nntp} server @samp{news.funet.fi} on port number 13, which
11201 hangs if queried for @sc{nov} headers and has a buggy select. Ahem.
11202 Anyway, if you had to specify that for each group that used this
11203 server, that would be too much work, so Gnus offers a way of naming
11204 select methods, which is what you do in the server buffer.
11206 To enter the server buffer, use the @kbd{^}
11207 (@code{gnus-group-enter-server-mode}) command in the group buffer.
11210 * Server Buffer Format:: You can customize the look of this buffer.
11211 * Server Commands:: Commands to manipulate servers.
11212 * Example Methods:: Examples server specifications.
11213 * Creating a Virtual Server:: An example session.
11214 * Server Variables:: Which variables to set.
11215 * Servers and Methods:: You can use server names as select methods.
11216 * Unavailable Servers:: Some servers you try to contact may be down.
11219 @vindex gnus-server-mode-hook
11220 @code{gnus-server-mode-hook} is run when creating the server buffer.
11223 @node Server Buffer Format
11224 @subsection Server Buffer Format
11225 @cindex server buffer format
11227 @vindex gnus-server-line-format
11228 You can change the look of the server buffer lines by changing the
11229 @code{gnus-server-line-format} variable. This is a @code{format}-like
11230 variable, with some simple extensions:
11235 How the news is fetched---the back end name.
11238 The name of this server.
11241 Where the news is to be fetched from---the address.
11244 The opened/closed/denied status of the server.
11247 @vindex gnus-server-mode-line-format
11248 The mode line can also be customized by using the
11249 @code{gnus-server-mode-line-format} variable (@pxref{Mode Line
11250 Formatting}). The following specs are understood:
11260 Also @pxref{Formatting Variables}.
11263 @node Server Commands
11264 @subsection Server Commands
11265 @cindex server commands
11271 @findex gnus-server-add-server
11272 Add a new server (@code{gnus-server-add-server}).
11276 @findex gnus-server-edit-server
11277 Edit a server (@code{gnus-server-edit-server}).
11280 @kindex SPACE (Server)
11281 @findex gnus-server-read-server
11282 Browse the current server (@code{gnus-server-read-server}).
11286 @findex gnus-server-exit
11287 Return to the group buffer (@code{gnus-server-exit}).
11291 @findex gnus-server-kill-server
11292 Kill the current server (@code{gnus-server-kill-server}).
11296 @findex gnus-server-yank-server
11297 Yank the previously killed server (@code{gnus-server-yank-server}).
11301 @findex gnus-server-copy-server
11302 Copy the current server (@code{gnus-server-copy-server}).
11306 @findex gnus-server-list-servers
11307 List all servers (@code{gnus-server-list-servers}).
11311 @findex gnus-server-scan-server
11312 Request that the server scan its sources for new articles
11313 (@code{gnus-server-scan-server}). This is mainly sensible with mail
11318 @findex gnus-server-regenerate-server
11319 Request that the server regenerate all its data structures
11320 (@code{gnus-server-regenerate-server}). This can be useful if you have
11321 a mail back end that has gotten out of sync.
11326 @node Example Methods
11327 @subsection Example Methods
11329 Most select methods are pretty simple and self-explanatory:
11332 (nntp "news.funet.fi")
11335 Reading directly from the spool is even simpler:
11341 As you can see, the first element in a select method is the name of the
11342 back end, and the second is the @dfn{address}, or @dfn{name}, if you
11345 After these two elements, there may be an arbitrary number of
11346 @code{(@var{variable} @var{form})} pairs.
11348 To go back to the first example---imagine that you want to read from
11349 port 15 on that machine. This is what the select method should
11353 (nntp "news.funet.fi" (nntp-port-number 15))
11356 You should read the documentation to each back end to find out what
11357 variables are relevant, but here's an @code{nnmh} example:
11359 @code{nnmh} is a mail back end that reads a spool-like structure. Say
11360 you have two structures that you wish to access: One is your private
11361 mail spool, and the other is a public one. Here's the possible spec for
11365 (nnmh "private" (nnmh-directory "~/private/mail/"))
11368 (This server is then called @samp{private}, but you may have guessed
11371 Here's the method for a public spool:
11375 (nnmh-directory "/usr/information/spool/")
11376 (nnmh-get-new-mail nil))
11382 If you are behind a firewall and only have access to the @sc{nntp}
11383 server from the firewall machine, you can instruct Gnus to @code{rlogin}
11384 on the firewall machine and telnet from there to the @sc{nntp} server.
11385 Doing this can be rather fiddly, but your virtual server definition
11386 should probably look something like this:
11390 (nntp-open-connection-function nntp-open-via-rlogin-and-telnet)
11391 (nntp-via-address "the.firewall.machine")
11392 (nntp-address "the.real.nntp.host")
11393 (nntp-end-of-line "\n"))
11396 If you want to use the wonderful @code{ssh} program to provide a
11397 compressed connection over the modem line, you could add the following
11398 configuration to the example above:
11401 (nntp-via-rlogin-command "ssh")
11404 If you're behind a firewall, but have direct access to the outside world
11405 through a wrapper command like "runsocks", you could open a socksified
11406 telnet connection to the news server as follows:
11410 (nntp-pre-command "runsocks")
11411 (nntp-open-connection-function nntp-open-via-telnet)
11412 (nntp-address "the.news.server")
11413 (nntp-end-of-line "\n"))
11416 This means that you have to have set up @code{ssh-agent} correctly to
11417 provide automatic authorization, of course. And to get a compressed
11418 connection, you have to have the @samp{Compression} option in the
11419 @code{ssh} @file{config} file.
11422 @node Creating a Virtual Server
11423 @subsection Creating a Virtual Server
11425 If you're saving lots of articles in the cache by using persistent
11426 articles, you may want to create a virtual server to read the cache.
11428 First you need to add a new server. The @kbd{a} command does that. It
11429 would probably be best to use @code{nnspool} to read the cache. You
11430 could also use @code{nnml} or @code{nnmh}, though.
11432 Type @kbd{a nnspool RET cache RET}.
11434 You should now have a brand new @code{nnspool} virtual server called
11435 @samp{cache}. You now need to edit it to have the right definitions.
11436 Type @kbd{e} to edit the server. You'll be entered into a buffer that
11437 will contain the following:
11447 (nnspool-spool-directory "~/News/cache/")
11448 (nnspool-nov-directory "~/News/cache/")
11449 (nnspool-active-file "~/News/cache/active"))
11452 Type @kbd{C-c C-c} to return to the server buffer. If you now press
11453 @kbd{RET} over this virtual server, you should be entered into a browse
11454 buffer, and you should be able to enter any of the groups displayed.
11457 @node Server Variables
11458 @subsection Server Variables
11460 One sticky point when defining variables (both on back ends and in Emacs
11461 in general) is that some variables are typically initialized from other
11462 variables when the definition of the variables is being loaded. If you
11463 change the "base" variable after the variables have been loaded, you
11464 won't change the "derived" variables.
11466 This typically affects directory and file variables. For instance,
11467 @code{nnml-directory} is @file{~/Mail/} by default, and all @code{nnml}
11468 directory variables are initialized from that variable, so
11469 @code{nnml-active-file} will be @file{~/Mail/active}. If you define a
11470 new virtual @code{nnml} server, it will @emph{not} suffice to set just
11471 @code{nnml-directory}---you have to explicitly set all the file
11472 variables to be what you want them to be. For a complete list of
11473 variables for each back end, see each back end's section later in this
11474 manual, but here's an example @code{nnml} definition:
11478 (nnml-directory "~/my-mail/")
11479 (nnml-active-file "~/my-mail/active")
11480 (nnml-newsgroups-file "~/my-mail/newsgroups"))
11484 @node Servers and Methods
11485 @subsection Servers and Methods
11487 Wherever you would normally use a select method
11488 (e.g. @code{gnus-secondary-select-method}, in the group select method,
11489 when browsing a foreign server) you can use a virtual server name
11490 instead. This could potentially save lots of typing. And it's nice all
11494 @node Unavailable Servers
11495 @subsection Unavailable Servers
11497 If a server seems to be unreachable, Gnus will mark that server as
11498 @code{denied}. That means that any subsequent attempt to make contact
11499 with that server will just be ignored. ``It can't be opened,'' Gnus
11500 will tell you, without making the least effort to see whether that is
11501 actually the case or not.
11503 That might seem quite naughty, but it does make sense most of the time.
11504 Let's say you have 10 groups subscribed to on server
11505 @samp{nephelococcygia.com}. This server is located somewhere quite far
11506 away from you and the machine is quite slow, so it takes 1 minute just
11507 to find out that it refuses connection to you today. If Gnus were to
11508 attempt to do that 10 times, you'd be quite annoyed, so Gnus won't
11509 attempt to do that. Once it has gotten a single ``connection refused'',
11510 it will regard that server as ``down''.
11512 So, what happens if the machine was only feeling unwell temporarily?
11513 How do you test to see whether the machine has come up again?
11515 You jump to the server buffer (@pxref{Server Buffer}) and poke it
11516 with the following commands:
11522 @findex gnus-server-open-server
11523 Try to establish connection to the server on the current line
11524 (@code{gnus-server-open-server}).
11528 @findex gnus-server-close-server
11529 Close the connection (if any) to the server
11530 (@code{gnus-server-close-server}).
11534 @findex gnus-server-deny-server
11535 Mark the current server as unreachable
11536 (@code{gnus-server-deny-server}).
11539 @kindex M-o (Server)
11540 @findex gnus-server-open-all-servers
11541 Open the connections to all servers in the buffer
11542 (@code{gnus-server-open-all-servers}).
11545 @kindex M-c (Server)
11546 @findex gnus-server-close-all-servers
11547 Close the connections to all servers in the buffer
11548 (@code{gnus-server-close-all-servers}).
11552 @findex gnus-server-remove-denials
11553 Remove all marks to whether Gnus was denied connection from any servers
11554 (@code{gnus-server-remove-denials}).
11560 @section Getting News
11561 @cindex reading news
11562 @cindex news back ends
11564 A newsreader is normally used for reading news. Gnus currently provides
11565 only two methods of getting news---it can read from an @sc{nntp} server,
11566 or it can read from a local spool.
11569 * NNTP:: Reading news from an @sc{nntp} server.
11570 * News Spool:: Reading news from the local spool.
11575 @subsection @sc{nntp}
11578 Subscribing to a foreign group from an @sc{nntp} server is rather easy.
11579 You just specify @code{nntp} as method and the address of the @sc{nntp}
11580 server as the, uhm, address.
11582 If the @sc{nntp} server is located at a non-standard port, setting the
11583 third element of the select method to this port number should allow you
11584 to connect to the right port. You'll have to edit the group info for
11585 that (@pxref{Foreign Groups}).
11587 The name of the foreign group can be the same as a native group. In
11588 fact, you can subscribe to the same group from as many different servers
11589 you feel like. There will be no name collisions.
11591 The following variables can be used to create a virtual @code{nntp}
11596 @item nntp-server-opened-hook
11597 @vindex nntp-server-opened-hook
11598 @cindex @sc{mode reader}
11600 @cindex authentification
11601 @cindex nntp authentification
11602 @findex nntp-send-authinfo
11603 @findex nntp-send-mode-reader
11604 is run after a connection has been made. It can be used to send
11605 commands to the @sc{nntp} server after it has been contacted. By
11606 default it sends the command @code{MODE READER} to the server with the
11607 @code{nntp-send-mode-reader} function. This function should always be
11608 present in this hook.
11610 @item nntp-authinfo-function
11611 @vindex nntp-authinfo-function
11612 @findex nntp-send-authinfo
11613 @vindex nntp-authinfo-file
11614 This function will be used to send @samp{AUTHINFO} to the @sc{nntp}
11615 server. The default function is @code{nntp-send-authinfo}, which looks
11616 through your @file{~/.authinfo} (or whatever you've set the
11617 @code{nntp-authinfo-file} variable to) for applicable entries. If none
11618 are found, it will prompt you for a login name and a password. The
11619 format of the @file{~/.authinfo} file is (almost) the same as the
11620 @code{ftp} @file{~/.netrc} file, which is defined in the @code{ftp}
11621 manual page, but here are the salient facts:
11625 The file contains one or more line, each of which define one server.
11628 Each line may contain an arbitrary number of token/value pairs.
11630 The valid tokens include @samp{machine}, @samp{login}, @samp{password},
11631 @samp{default}. In addition Gnus introduces two new tokens, not present
11632 in the original @file{.netrc}/@code{ftp} syntax, namely @samp{port} and
11633 @samp{force}. (This is the only way the @file{.authinfo} file format
11634 deviates from the @file{.netrc} file format.) @samp{port} is used to
11635 indicate what port on the server the credentials apply to and
11636 @samp{force} is explained below.
11640 Here's an example file:
11643 machine news.uio.no login larsi password geheimnis
11644 machine nntp.ifi.uio.no login larsi force yes
11647 The token/value pairs may appear in any order; @samp{machine} doesn't
11648 have to be first, for instance.
11650 In this example, both login name and password have been supplied for the
11651 former server, while the latter has only the login name listed, and the
11652 user will be prompted for the password. The latter also has the
11653 @samp{force} tag, which means that the authinfo will be sent to the
11654 @var{nntp} server upon connection; the default (i.e., when there is not
11655 @samp{force} tag) is to not send authinfo to the @var{nntp} server
11656 until the @var{nntp} server asks for it.
11658 You can also add @samp{default} lines that will apply to all servers
11659 that don't have matching @samp{machine} lines.
11665 This will force sending @samp{AUTHINFO} commands to all servers not
11666 previously mentioned.
11668 Remember to not leave the @file{~/.authinfo} file world-readable.
11670 @item nntp-server-action-alist
11671 @vindex nntp-server-action-alist
11672 This is a list of regexps to match on server types and actions to be
11673 taken when matches are made. For instance, if you want Gnus to beep
11674 every time you connect to innd, you could say something like:
11677 (setq nntp-server-action-alist
11678 '(("innd" (ding))))
11681 You probably don't want to do that, though.
11683 The default value is
11686 '(("nntpd 1\\.5\\.11t"
11687 (remove-hook 'nntp-server-opened-hook
11688 'nntp-send-mode-reader)))
11691 This ensures that Gnus doesn't send the @code{MODE READER} command to
11692 nntpd 1.5.11t, since that command chokes that server, I've been told.
11694 @item nntp-maximum-request
11695 @vindex nntp-maximum-request
11696 If the @sc{nntp} server doesn't support @sc{nov} headers, this back end
11697 will collect headers by sending a series of @code{head} commands. To
11698 speed things up, the back end sends lots of these commands without
11699 waiting for reply, and then reads all the replies. This is controlled
11700 by the @code{nntp-maximum-request} variable, and is 400 by default. If
11701 your network is buggy, you should set this to 1.
11703 @item nntp-connection-timeout
11704 @vindex nntp-connection-timeout
11705 If you have lots of foreign @code{nntp} groups that you connect to
11706 regularly, you're sure to have problems with @sc{nntp} servers not
11707 responding properly, or being too loaded to reply within reasonable
11708 time. This is can lead to awkward problems, which can be helped
11709 somewhat by setting @code{nntp-connection-timeout}. This is an integer
11710 that says how many seconds the @code{nntp} back end should wait for a
11711 connection before giving up. If it is @code{nil}, which is the default,
11712 no timeouts are done.
11714 @c @item nntp-command-timeout
11715 @c @vindex nntp-command-timeout
11716 @c @cindex PPP connections
11717 @c @cindex dynamic IP addresses
11718 @c If you're running Gnus on a machine that has a dynamically assigned
11719 @c address, Gnus may become confused. If the address of your machine
11720 @c changes after connecting to the @sc{nntp} server, Gnus will simply sit
11721 @c waiting forever for replies from the server. To help with this
11722 @c unfortunate problem, you can set this command to a number. Gnus will
11723 @c then, if it sits waiting for a reply from the server longer than that
11724 @c number of seconds, shut down the connection, start a new one, and resend
11725 @c the command. This should hopefully be transparent to the user. A
11726 @c likely number is 30 seconds.
11728 @c @item nntp-retry-on-break
11729 @c @vindex nntp-retry-on-break
11730 @c If this variable is non-@code{nil}, you can also @kbd{C-g} if Gnus
11731 @c hangs. This will have much the same effect as the command timeout
11732 @c described above.
11734 @item nntp-server-hook
11735 @vindex nntp-server-hook
11736 This hook is run as the last step when connecting to an @sc{nntp}
11739 @item nntp-buggy-select
11740 @vindex nntp-buggy-select
11741 Set this to non-@code{nil} if your select routine is buggy.
11743 @item nntp-nov-is-evil
11744 @vindex nntp-nov-is-evil
11745 If the @sc{nntp} server does not support @sc{nov}, you could set this
11746 variable to @code{t}, but @code{nntp} usually checks automatically whether @sc{nov}
11749 @item nntp-xover-commands
11750 @vindex nntp-xover-commands
11753 List of strings used as commands to fetch @sc{nov} lines from a
11754 server. The default value of this variable is @code{("XOVER"
11758 @vindex nntp-nov-gap
11759 @code{nntp} normally sends just one big request for @sc{nov} lines to
11760 the server. The server responds with one huge list of lines. However,
11761 if you have read articles 2-5000 in the group, and only want to read
11762 article 1 and 5001, that means that @code{nntp} will fetch 4999 @sc{nov}
11763 lines that you will not need. This variable says how
11764 big a gap between two consecutive articles is allowed to be before the
11765 @code{XOVER} request is split into several request. Note that if your
11766 network is fast, setting this variable to a really small number means
11767 that fetching will probably be slower. If this variable is @code{nil},
11768 @code{nntp} will never split requests. The default is 5.
11770 @item nntp-prepare-server-hook
11771 @vindex nntp-prepare-server-hook
11772 A hook run before attempting to connect to an @sc{nntp} server.
11774 @item nntp-warn-about-losing-connection
11775 @vindex nntp-warn-about-losing-connection
11776 If this variable is non-@code{nil}, some noise will be made when a
11777 server closes connection.
11779 @item nntp-record-commands
11780 @vindex nntp-record-commands
11781 If non-@code{nil}, @code{nntp} will log all commands it sends to the
11782 @sc{nntp} server (along with a timestamp) in the @samp{*nntp-log*}
11783 buffer. This is useful if you are debugging a Gnus/@sc{nntp} connection
11784 that doesn't seem to work.
11786 @item nntp-open-connection-function
11787 @vindex nntp-open-connection-function
11788 It is possible to customize how the connection to the nntp server will
11789 be opened. If you specify an @code{nntp-open-connection-function}
11790 parameter, Gnus will use that function to establish the connection.
11791 Five pre-made functions are supplied. These functions can be grouped in
11792 two categories: direct connection functions (three pre-made), and
11793 indirect ones (two pre-made).
11795 @item nntp-prepare-post-hook
11796 @vindex nntp-prepare-post-hook
11797 A hook run just before posting an article. If there is no
11798 @code{Message-ID} header in the article and the news server provides the
11799 recommended ID, it will be added to the article before running this
11800 hook. It is useful to make @code{Cancel-Lock} headers even if you
11801 inhibit Gnus to add a @code{Message-ID} header, you could say:
11804 (add-hook 'nntp-prepare-post-hook 'canlock-insert-header)
11807 Note that not all servers support the recommended ID. This works for
11808 INN versions 2.3.0 and later, for instance.
11812 * Direct Functions:: Connecting directly to the server.
11813 * Indirect Functions:: Connecting indirectly to the server.
11814 * Common Variables:: Understood by several connection functions.
11818 @node Direct Functions
11819 @subsubsection Direct Functions
11820 @cindex direct connection functions
11822 These functions are called direct because they open a direct connection
11823 between your machine and the @sc{nntp} server. The behavior of these
11824 functions is also affected by commonly understood variables
11825 (@pxref{Common Variables}).
11828 @findex nntp-open-network-stream
11829 @item nntp-open-network-stream
11830 This is the default, and simply connects to some port or other on the
11833 @findex nntp-open-ssl-stream
11834 @item nntp-open-ssl-stream
11835 Opens a connection to a server over a @dfn{secure} channel. To use
11836 this you must have OpenSSL (@uref{http://www.openssl.org}) or SSLeay
11837 installed (@uref{ftp://ftp.psy.uq.oz.au/pub/Crypto/SSL}, and you also
11838 need @file{ssl.el} (from the W3 distribution, for instance). You then
11839 define a server as follows:
11842 ;; Type `C-c C-c' after you've finished editing.
11844 ;; "snews" is port 563 and is predefined in our /etc/services
11846 (nntp "snews.bar.com"
11847 (nntp-open-connection-function nntp-open-ssl-stream)
11848 (nntp-port-number "snews")
11849 (nntp-address "snews.bar.com"))
11852 @findex nntp-open-telnet-stream
11853 @item nntp-open-telnet-stream
11854 Opens a connection to an @sc{nntp} server by simply @samp{telnet}'ing
11855 it. You might wonder why this function exists, since we have the
11856 default @code{nntp-open-network-stream} which would do the job. (One
11857 of) the reason(s) is that if you are behind a firewall but have direct
11858 connections to the outside world thanks to a command wrapper like
11859 @code{runsocks}, you can use it like this:
11863 (nntp-pre-command "runsocks")
11864 (nntp-open-connection-function nntp-open-telnet-stream)
11865 (nntp-address "the.news.server"))
11868 With the default method, you would need to wrap your whole Emacs
11869 session, which is not a good idea.
11873 @node Indirect Functions
11874 @subsubsection Indirect Functions
11875 @cindex indirect connection functions
11877 These functions are called indirect because they connect to an
11878 intermediate host before actually connecting to the @sc{nntp} server.
11879 All of these functions and related variables are also said to belong to
11880 the "via" family of connection: they're all prefixed with "via" to make
11881 things cleaner. The behavior of these functions is also affected by
11882 commonly understood variables (@pxref{Common Variables}).
11885 @item nntp-open-via-rlogin-and-telnet
11886 @findex nntp-open-via-rlogin-and-telnet
11887 Does an @samp{rlogin} on a remote system, and then does a @samp{telnet}
11888 to the real @sc{nntp} server from there. This is useful for instance if
11889 you need to connect to a firewall machine first.
11891 @code{nntp-open-via-rlogin-and-telnet}-specific variables:
11894 @item nntp-via-rlogin-command
11895 @vindex nntp-via-rlogin-command
11896 Command used to log in on the intermediate host. The default is
11897 @samp{rsh}, but @samp{ssh} is a popular alternative.
11900 @item nntp-open-via-telnet-and-telnet
11901 @findex nntp-open-via-telnet-and-telnet
11902 Does essentially the same, but uses @samp{telnet} instead of
11903 @samp{rlogin} to connect to the intermediate host.
11905 @code{nntp-open-via-telnet-and-telnet}-specific variables:
11908 @item nntp-via-telnet-command
11909 @vindex nntp-via-telnet-command
11910 Command used to @code{telnet} the intermediate host. The default is
11913 @item nntp-via-telnet-switches
11914 @vindex nntp-via-telnet-switches
11915 List of strings to be used as the switches to the
11916 @code{nntp-via-telnet-command} command. The default is @samp{("-8")}.
11918 @item nntp-via-user-password
11919 @vindex nntp-via-user-password
11920 Password to use when logging in on the intermediate host.
11922 @item nntp-via-envuser
11923 @vindex nntp-via-envuser
11924 If non-@code{nil}, the intermediate @code{telnet} session (client and
11925 server both) will support the @code{ENVIRON} option and not prompt for
11926 login name. This works for Solaris @code{telnet}, for instance.
11928 @item nntp-via-shell-prompt
11929 @vindex nntp-via-shell-prompt
11930 Regexp matching the shell prompt on the intermediate host. The default
11931 is @samp{bash\\|\$ *\r?$\\|> *\r?}.
11938 Here are some additional variables that are understood by all the above
11943 @item nntp-via-user-name
11944 @vindex nntp-via-user-name
11945 User name to use when connecting to the intermediate host.
11947 @item nntp-via-address
11948 @vindex nntp-via-address
11949 Address of the intermediate host to connect to.
11954 @node Common Variables
11955 @subsubsection Common Variables
11957 The following variables affect the behavior of all, or several of the
11958 pre-made connection functions. When not specified, all functions are
11963 @item nntp-pre-command
11964 @vindex nntp-pre-command
11965 A command wrapper to use when connecting through a non native connection
11966 function (all except @code{nntp-open-network-stream} and
11967 @code{nntp-open-ssl-stream}. This is where you would put a @samp{SOCKS}
11968 wrapper for instance.
11971 @vindex nntp-address
11972 The address of the @sc{nntp} server.
11974 @item nntp-port-number
11975 @vindex nntp-port-number
11976 Port number to connect to the @sc{nntp} server. The default is @samp{nntp}.
11978 @item nntp-end-of-line
11979 @vindex nntp-end-of-line
11980 String to use as end-of-line marker when talking to the @sc{nntp}
11981 server. This is @samp{\r\n} by default, but should be @samp{\n} when
11982 using a non native connection function.
11984 @item nntp-telnet-command
11985 @vindex nntp-telnet-command
11986 Command to use when connecting to the @sc{nntp} server through
11987 @samp{telnet}. This is NOT for an intermediate host. This is just for
11988 the real @sc{nntp} server. The default is @samp{telnet}.
11990 @item nntp-telnet-switches
11991 @vindex nntp-telnet-switches
11992 A list of switches to pass to @code{nntp-telnet-command}. The default
11999 @subsection News Spool
12003 Subscribing to a foreign group from the local spool is extremely easy,
12004 and might be useful, for instance, to speed up reading groups that
12005 contain very big articles---@samp{alt.binaries.pictures.furniture}, for
12008 Anyway, you just specify @code{nnspool} as the method and @code{""} (or
12009 anything else) as the address.
12011 If you have access to a local spool, you should probably use that as the
12012 native select method (@pxref{Finding the News}). It is normally faster
12013 than using an @code{nntp} select method, but might not be. It depends.
12014 You just have to try to find out what's best at your site.
12018 @item nnspool-inews-program
12019 @vindex nnspool-inews-program
12020 Program used to post an article.
12022 @item nnspool-inews-switches
12023 @vindex nnspool-inews-switches
12024 Parameters given to the inews program when posting an article.
12026 @item nnspool-spool-directory
12027 @vindex nnspool-spool-directory
12028 Where @code{nnspool} looks for the articles. This is normally
12029 @file{/usr/spool/news/}.
12031 @item nnspool-nov-directory
12032 @vindex nnspool-nov-directory
12033 Where @code{nnspool} will look for @sc{nov} files. This is normally
12034 @file{/usr/spool/news/over.view/}.
12036 @item nnspool-lib-dir
12037 @vindex nnspool-lib-dir
12038 Where the news lib dir is (@file{/usr/lib/news/} by default).
12040 @item nnspool-active-file
12041 @vindex nnspool-active-file
12042 The path to the active file.
12044 @item nnspool-newsgroups-file
12045 @vindex nnspool-newsgroups-file
12046 The path to the group descriptions file.
12048 @item nnspool-history-file
12049 @vindex nnspool-history-file
12050 The path to the news history file.
12052 @item nnspool-active-times-file
12053 @vindex nnspool-active-times-file
12054 The path to the active date file.
12056 @item nnspool-nov-is-evil
12057 @vindex nnspool-nov-is-evil
12058 If non-@code{nil}, @code{nnspool} won't try to use any @sc{nov} files
12061 @item nnspool-sift-nov-with-sed
12062 @vindex nnspool-sift-nov-with-sed
12064 If non-@code{nil}, which is the default, use @code{sed} to get the
12065 relevant portion from the overview file. If nil, @code{nnspool} will
12066 load the entire file into a buffer and process it there.
12072 @section Getting Mail
12073 @cindex reading mail
12076 Reading mail with a newsreader---isn't that just plain WeIrD? But of
12080 * Mail in a Newsreader:: Important introductory notes.
12081 * Getting Started Reading Mail:: A simple cookbook example.
12082 * Splitting Mail:: How to create mail groups.
12083 * Mail Sources:: How to tell Gnus where to get mail from.
12084 * Mail Back End Variables:: Variables for customizing mail handling.
12085 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
12086 * Group Mail Splitting:: Use group customize to drive mail splitting.
12087 * Incorporating Old Mail:: What about the old mail you have?
12088 * Expiring Mail:: Getting rid of unwanted mail.
12089 * Washing Mail:: Removing gruft from the mail you get.
12090 * Duplicates:: Dealing with duplicated mail.
12091 * Not Reading Mail:: Using mail back ends for reading other files.
12092 * Choosing a Mail Back End:: Gnus can read a variety of mail formats.
12096 @node Mail in a Newsreader
12097 @subsection Mail in a Newsreader
12099 If you are used to traditional mail readers, but have decided to switch
12100 to reading mail with Gnus, you may find yourself experiencing something
12101 of a culture shock.
12103 Gnus does not behave like traditional mail readers. If you want to make
12104 it behave that way, you can, but it's an uphill battle.
12106 Gnus, by default, handles all its groups using the same approach. This
12107 approach is very newsreaderly---you enter a group, see the new/unread
12108 messages, and when you read the messages, they get marked as read, and
12109 you don't see them any more. (Unless you explicitly ask for them.)
12111 In particular, you do not do anything explicitly to delete messages.
12113 Does this mean that all the messages that have been marked as read are
12114 deleted? How awful!
12116 But, no, it means that old messages are @dfn{expired} according to some
12117 scheme or other. For news messages, the expire process is controlled by
12118 the news administrator; for mail, the expire process is controlled by
12119 you. The expire process for mail is covered in depth in @pxref{Expiring
12122 What many Gnus users find, after using it a while for both news and
12123 mail, is that the transport mechanism has very little to do with how
12124 they want to treat a message.
12126 Many people subscribe to several mailing lists. These are transported
12127 via SMTP, and are therefore mail. But we might go for weeks without
12128 answering, or even reading these messages very carefully. We may not
12129 need to save them because if we should need to read one again, they are
12130 archived somewhere else.
12132 Some people have local news groups which have only a handful of readers.
12133 These are transported via @sc{nntp}, and are therefore news. But we may need
12134 to read and answer a large fraction of the messages very carefully in
12135 order to do our work. And there may not be an archive, so we may need
12136 to save the interesting messages the same way we would personal mail.
12138 The important distinction turns out to be not the transport mechanism,
12139 but other factors such as how interested we are in the subject matter,
12140 or how easy it is to retrieve the message if we need to read it again.
12142 Gnus provides many options for sorting mail into ``groups'' which behave
12143 like newsgroups, and for treating each group (whether mail or news)
12146 Some users never get comfortable using the Gnus (ahem) paradigm and wish
12147 that Gnus should grow up and be a male, er, mail reader. It is possible
12148 to whip Gnus into a more mailreaderly being, but, as said before, it's
12149 not easy. People who prefer proper mail readers should try @sc{vm}
12150 instead, which is an excellent, and proper, mail reader.
12152 I don't mean to scare anybody off, but I want to make it clear that you
12153 may be required to learn a new way of thinking about messages. After
12154 you've been subjected to The Gnus Way, you will come to love it. I can
12155 guarantee it. (At least the guy who sold me the Emacs Subliminal
12156 Brain-Washing Functions that I've put into Gnus did guarantee it. You
12157 Will Be Assimilated. You Love Gnus. You Love The Gnus Mail Way.
12161 @node Getting Started Reading Mail
12162 @subsection Getting Started Reading Mail
12164 It's quite easy to use Gnus to read your new mail. You just plonk the
12165 mail back end of your choice into @code{gnus-secondary-select-methods},
12166 and things will happen automatically.
12168 For instance, if you want to use @code{nnml} (which is a "one file per
12169 mail" back end), you could put the following in your @file{.gnus} file:
12172 (setq gnus-secondary-select-methods '((nnml "")))
12175 Now, the next time you start Gnus, this back end will be queried for new
12176 articles, and it will move all the messages in your spool file to its
12177 directory, which is @code{~/Mail/} by default. The new group that will
12178 be created (@samp{mail.misc}) will be subscribed, and you can read it
12179 like any other group.
12181 You will probably want to split the mail into several groups, though:
12184 (setq nnmail-split-methods
12185 '(("junk" "^From:.*Lars Ingebrigtsen")
12186 ("crazy" "^Subject:.*die\\|^Organization:.*flabby")
12190 This will result in three new @code{nnml} mail groups being created:
12191 @samp{nnml:junk}, @samp{nnml:crazy}, and @samp{nnml:other}. All the
12192 mail that doesn't fit into the first two groups will be placed in the
12195 This should be sufficient for reading mail with Gnus. You might want to
12196 give the other sections in this part of the manual a perusal, though.
12197 Especially @pxref{Choosing a Mail Back End} and @pxref{Expiring Mail}.
12200 @node Splitting Mail
12201 @subsection Splitting Mail
12202 @cindex splitting mail
12203 @cindex mail splitting
12205 @vindex nnmail-split-methods
12206 The @code{nnmail-split-methods} variable says how the incoming mail is
12207 to be split into groups.
12210 (setq nnmail-split-methods
12211 '(("mail.junk" "^From:.*Lars Ingebrigtsen")
12212 ("mail.crazy" "^Subject:.*die\\|^Organization:.*flabby")
12213 ("mail.other" "")))
12216 This variable is a list of lists, where the first element of each of
12217 these lists is the name of the mail group (they do not have to be called
12218 something beginning with @samp{mail}, by the way), and the second
12219 element is a regular expression used on the header of each mail to
12220 determine if it belongs in this mail group. The first string may
12221 contain @samp{\\1} forms, like the ones used by @code{replace-match} to
12222 insert sub-expressions from the matched text. For instance:
12225 ("list.\\1" "From:.* \\(.*\\)-list@@majordomo.com")
12228 The second element can also be a function. In that case, it will be
12229 called narrowed to the headers with the first element of the rule as the
12230 argument. It should return a non-@code{nil} value if it thinks that the
12231 mail belongs in that group.
12233 The last of these groups should always be a general one, and the regular
12234 expression should @emph{always} be @samp{} so that it matches any mails
12235 that haven't been matched by any of the other regexps. (These rules are
12236 processed from the beginning of the alist toward the end. The first
12237 rule to make a match will "win", unless you have crossposting enabled.
12238 In that case, all matching rules will "win".)
12240 If you like to tinker with this yourself, you can set this variable to a
12241 function of your choice. This function will be called without any
12242 arguments in a buffer narrowed to the headers of an incoming mail
12243 message. The function should return a list of group names that it
12244 thinks should carry this mail message.
12246 Note that the mail back ends are free to maul the poor, innocent,
12247 incoming headers all they want to. They all add @code{Lines} headers;
12248 some add @code{X-Gnus-Group} headers; most rename the Unix mbox
12249 @code{From<SPACE>} line to something else.
12251 @vindex nnmail-crosspost
12252 The mail back ends all support cross-posting. If several regexps match,
12253 the mail will be ``cross-posted'' to all those groups.
12254 @code{nnmail-crosspost} says whether to use this mechanism or not. Note
12255 that no articles are crossposted to the general (@samp{}) group.
12257 @vindex nnmail-crosspost-link-function
12260 @code{nnmh} and @code{nnml} makes crossposts by creating hard links to
12261 the crossposted articles. However, not all file systems support hard
12262 links. If that's the case for you, set
12263 @code{nnmail-crosspost-link-function} to @code{copy-file}. (This
12264 variable is @code{add-name-to-file} by default.)
12266 @kindex M-x nnmail-split-history
12267 @kindex nnmail-split-history
12268 If you wish to see where the previous mail split put the messages, you
12269 can use the @kbd{M-x nnmail-split-history} command. If you wish to see
12270 where re-spooling messages would put the messages, you can use
12271 @code{gnus-summary-respool-trace} and related commands (@pxref{Mail
12274 Gnus gives you all the opportunity you could possibly want for shooting
12275 yourself in the foot. Let's say you create a group that will contain
12276 all the mail you get from your boss. And then you accidentally
12277 unsubscribe from the group. Gnus will still put all the mail from your
12278 boss in the unsubscribed group, and so, when your boss mails you ``Have
12279 that report ready by Monday or you're fired!'', you'll never see it and,
12280 come Tuesday, you'll still believe that you're gainfully employed while
12281 you really should be out collecting empty bottles to save up for next
12282 month's rent money.
12286 @subsection Mail Sources
12288 Mail can be gotten from many different sources---the mail spool, from a
12289 POP mail server, from a procmail directory, or from a maildir, for
12293 * Mail Source Specifiers:: How to specify what a mail source is.
12294 * Mail Source Customization:: Some variables that influence things.
12295 * Fetching Mail:: Using the mail source specifiers.
12299 @node Mail Source Specifiers
12300 @subsubsection Mail Source Specifiers
12302 @cindex mail server
12305 @cindex mail source
12307 You tell Gnus how to fetch mail by setting @code{mail-sources}
12308 (@pxref{Fetching Mail}) to a @dfn{mail source specifier}.
12313 (pop :server "pop3.mailserver.com" :user "myname")
12316 As can be observed, a mail source specifier is a list where the first
12317 element is a @dfn{mail source type}, followed by an arbitrary number of
12318 @dfn{keywords}. Keywords that are not explicitly specified are given
12321 The following mail source types are available:
12325 Get mail from a single file; typically from the mail spool.
12331 The path of the file. Defaults to the value of the @code{MAIL}
12332 environment variable or @file{/usr/mail/spool/user-name}.
12335 An example file mail source:
12338 (file :path "/usr/spool/mail/user-name")
12341 Or using the default path:
12347 If the mail spool file is not located on the local machine, it's best to
12348 use POP or @sc{imap} or the like to fetch the mail. You can not use ange-ftp
12349 file names here---it has no way to lock the mail spool while moving the
12352 If it's impossible to set up a proper server, you can use ssh instead.
12356 '((file :prescript "ssh host bin/getmail >%t")))
12359 The @samp{getmail} script would look something like the following:
12363 # getmail - move mail from spool to stdout
12366 MOVEMAIL=/usr/lib/emacs/20.3/i386-redhat-linux/movemail
12368 rm -f $TMP; $MOVEMAIL $MAIL $TMP >/dev/null && cat $TMP
12371 Alter this script to fit find the @samp{movemail} you want to use.
12375 Get mail from several files in a directory. This is typically used
12376 when you have procmail split the incoming mail into several files.
12377 That is, mail from the file @file{foo.bar.spool} will be put in the
12378 group @code{foo.bar}. (You can change the suffix to be used instead
12379 of @code{.spool}.) Setting
12380 @code{nnmail-scan-directory-mail-source-once} to non-nil forces Gnus
12381 to scan the mail source only once. This is particularly useful if you
12382 want to scan mail groups at a specified level.
12388 The path of the directory where the files are. There is no default
12392 Only files ending with this suffix are used. The default is
12396 Only files that have this predicate return non-@code{nil} are returned.
12397 The default is @code{identity}. This is used as an additional
12398 filter---only files that have the right suffix @emph{and} satisfy this
12399 predicate are considered.
12403 Script run before/after fetching mail.
12407 An example directory mail source:
12410 (directory :path "/home/user-name/procmail-dir/"
12415 Get mail from a POP server.
12421 The name of the POP server. The default is taken from the
12422 @code{MAILHOST} environment variable.
12425 The port number of the POP server. This can be a number (eg,
12426 @samp{:port 1234}) or a string (eg, @samp{:port "pop3"}). If it is a
12427 string, it should be a service name as listed in @file{/etc/services} on
12428 Unix systems. The default is @samp{"pop3"}. On some systems you might
12429 need to specify it as @samp{"pop-3"} instead.
12432 The user name to give to the POP server. The default is the login
12436 The password to give to the POP server. If not specified, the user is
12440 The program to use to fetch mail from the POP server. This should be
12441 a @code{format}-like string. Here's an example:
12444 fetchmail %u@@%s -P %p %t
12447 The valid format specifier characters are:
12451 The name of the file the mail is to be moved to. This must always be
12452 included in this string.
12455 The name of the server.
12458 The port number of the server.
12461 The user name to use.
12464 The password to use.
12467 The values used for these specs are taken from the values you give the
12468 corresponding keywords.
12471 A script to be run before fetching the mail. The syntax is the same as
12472 the @code{:program} keyword. This can also be a function to be run.
12475 A script to be run after fetching the mail. The syntax is the same as
12476 the @code{:program} keyword. This can also be a function to be run.
12479 The function to use to fetch mail from the POP server. The function is
12480 called with one parameter---the name of the file where the mail should
12483 @item :authentication
12484 This can be either the symbol @code{password} or the symbol @code{apop}
12485 and says what authentication scheme to use. The default is
12490 If the @code{:program} and @code{:function} keywords aren't specified,
12491 @code{pop3-movemail} will be used.
12493 Here are some examples. Fetch from the default POP server, using the
12494 default user name, and default fetcher:
12500 Fetch from a named server with a named user and password:
12503 (pop :server "my.pop.server"
12504 :user "user-name" :password "secret")
12507 Use @samp{movemail} to move the mail:
12510 (pop :program "movemail po:%u %t %p")
12514 Get mail from a maildir. This is a type of mailbox that is supported by
12515 at least qmail and postfix, where each file in a special directory
12516 contains exactly one mail.
12522 The path of the directory where the mails are stored. The default is
12523 taken from the @code{MAILDIR} environment variable or
12526 The subdirectories of the Maildir. The default is
12527 @samp{("new" "cur")}.
12529 @c If you sometimes look at your mail through a pop3 daemon before fetching
12530 @c them with Gnus, you may also have to fetch your mails from the
12531 @c @code{cur} directory inside the maildir, like in the first example
12534 You can also get mails from remote hosts (because maildirs don't suffer
12535 from locking problems).
12539 Two example maildir mail sources:
12542 (maildir :path "/home/user-name/Maildir/"
12543 :subdirs ("cur" "new"))
12547 (maildir :path "/user@@remotehost.org:~/Maildir/"
12552 Get mail from a @sc{imap} server. If you don't want to use @sc{imap}
12553 as intended, as a network mail reading protocol (ie with nnimap), for
12554 some reason or other, Gnus let you treat it similar to a POP server
12555 and fetches articles from a given @sc{imap} mailbox. @xref{IMAP}, for
12558 Note that for the Kerberos, GSSAPI, SSL/TLS and STARTTLS support you
12559 may need external programs and libraries, @xref{IMAP}.
12565 The name of the @sc{imap} server. The default is taken from the
12566 @code{MAILHOST} environment variable.
12569 The port number of the @sc{imap} server. The default is @samp{143}, or
12570 @samp{993} for SSL/TLS connections.
12573 The user name to give to the @sc{imap} server. The default is the login
12577 The password to give to the @sc{imap} server. If not specified, the user is
12581 What stream to use for connecting to the server, this is one of the
12582 symbols in @code{imap-stream-alist}. Right now, this means
12583 @samp{gssapi}, @samp{kerberos4}, @samp{starttls}, @samp{ssl},
12584 @samp{shell} or the default @samp{network}.
12586 @item :authentication
12587 Which authenticator to use for authenticating to the server, this is
12588 one of the symbols in @code{imap-authenticator-alist}. Right now,
12589 this means @samp{gssapi}, @samp{kerberos4}, @samp{digest-md5},
12590 @samp{cram-md5}, @samp{anonymous} or the default @samp{login}.
12593 When using the `shell' :stream, the contents of this variable is
12594 mapped into the `imap-shell-program' variable. This should be a
12595 @code{format}-like string (or list of strings). Here's an example:
12601 The valid format specifier characters are:
12605 The name of the server.
12608 User name from `imap-default-user'.
12611 The port number of the server.
12614 The values used for these specs are taken from the values you give the
12615 corresponding keywords.
12618 The name of the mailbox to get mail from. The default is @samp{INBOX}
12619 which normally is the mailbox which receive incoming mail.
12622 The predicate used to find articles to fetch. The default, @samp{UNSEEN
12623 UNDELETED}, is probably the best choice for most people, but if you
12624 sometimes peek in your mailbox with a @sc{imap} client and mark some
12625 articles as read (or; SEEN) you might want to set this to @samp{nil}.
12626 Then all articles in the mailbox is fetched, no matter what. For a
12627 complete list of predicates, see RFC 2060 §6.4.4.
12630 How to flag fetched articles on the server, the default @samp{\Deleted}
12631 will mark them as deleted, an alternative would be @samp{\Seen} which
12632 would simply mark them as read. These are the two most likely choices,
12633 but more flags are defined in RFC 2060 §2.3.2.
12636 If non-nil, don't remove all articles marked as deleted in the mailbox
12637 after finishing the fetch.
12641 An example @sc{imap} mail source:
12644 (imap :server "mail.mycorp.com"
12646 :fetchflag "\\Seen")
12650 Get mail from a webmail server, such as www.hotmail.com,
12651 webmail.netscape.com, www.netaddress.com, www.my-deja.com.
12653 NOTE: Now mail.yahoo.com provides POP3 service, so @sc{pop} mail source
12656 NOTE: Webmail largely depends cookies. A "one-line-cookie" patch is
12657 required for url "4.0pre.46".
12659 WARNING: Mails may lost. NO WARRANTY.
12665 The type of the webmail server. The default is @code{hotmail}. The
12666 alternatives are @code{netscape}, @code{netaddress}, @code{my-deja}.
12669 The user name to give to the webmail server. The default is the login
12673 The password to give to the webmail server. If not specified, the user is
12677 If non-nil, only fetch unread articles and don't move them to trash
12678 folder after finishing the fetch.
12682 An example webmail source:
12685 (webmail :subtype 'hotmail
12687 :password "secret")
12692 @item Common Keywords
12693 Common keywords can be used in any type of mail source.
12699 If non-nil, fetch the mail even when Gnus is unplugged. If you use
12700 directory source to get mail, you can specify it as in this example:
12704 '((directory :path "/home/pavel/.Spool/"
12709 Gnus will then fetch your mail even when you are unplugged. This is
12710 useful when you use local mail and news.
12715 @subsubsection Function Interface
12717 Some of the above keywords specify a Lisp function to be executed.
12718 For each keyword @code{:foo}, the Lisp variable @code{foo} is bound to
12719 the value of the keyword while the function is executing. For example,
12720 consider the following mail-source setting:
12723 (setq mail-sources '((pop :user "jrl"
12724 :server "pophost" :function fetchfunc)))
12727 While the function @code{fetchfunc} is executing, the symbol @code{user}
12728 is bound to @code{"jrl"}, and the symbol @code{server} is bound to
12729 @code{"pophost"}. The symbols @code{port}, @code{password},
12730 @code{program}, @code{prescript}, @code{postscript}, @code{function},
12731 and @code{authentication} are also bound (to their default values).
12733 See above for a list of keywords for each type of mail source.
12736 @node Mail Source Customization
12737 @subsubsection Mail Source Customization
12739 The following is a list of variables that influence how the mail is
12740 fetched. You would normally not need to set or change any of these
12744 @item mail-source-crash-box
12745 @vindex mail-source-crash-box
12746 File where mail will be stored while processing it. The default is
12747 @file{~/.emacs-mail-crash-box}.
12749 @item mail-source-delete-incoming
12750 @vindex mail-source-delete-incoming
12751 If non-@code{nil}, delete incoming files after handling them.
12753 @item mail-source-directory
12754 @vindex mail-source-directory
12755 Directory where files (if any) will be stored. The default is
12756 @file{~/Mail/}. At present, the only thing this is used for is to say
12757 where the incoming files will be stored if the previous variable is
12760 @item mail-source-incoming-file-prefix
12761 @vindex mail-source-incoming-file-prefix
12762 Prefix for file name for storing incoming mail. The default is
12763 @file{Incoming}, in which case files will end up with names like
12764 @file{Incoming30630D_} or @file{Incoming298602ZD}. This is really only
12765 relevant if @code{mail-source-delete-incoming} is @code{nil}.
12767 @item mail-source-default-file-modes
12768 @vindex mail-source-default-file-modes
12769 All new mail files will get this file mode. The default is 384.
12771 @item mail-source-movemail-program
12772 @vindex mail-source-movemail-program
12773 If non-nil, name of program for fetching new mail. If nil,
12774 @code{movemail} in @var{exec-directory}.
12779 @node Fetching Mail
12780 @subsubsection Fetching Mail
12782 @vindex mail-sources
12783 @vindex nnmail-spool-file
12784 The way to actually tell Gnus where to get new mail from is to set
12785 @code{mail-sources} to a list of mail source specifiers
12786 (@pxref{Mail Source Specifiers}).
12788 If this variable (and the obsolescent @code{nnmail-spool-file}) is
12789 @code{nil}, the mail back ends will never attempt to fetch mail by
12792 If you want to fetch mail both from your local spool as well as a POP
12793 mail server, you'd say something like:
12798 (pop :server "pop3.mail.server"
12799 :password "secret")))
12802 Or, if you don't want to use any of the keyword defaults:
12806 '((file :path "/var/spool/mail/user-name")
12807 (pop :server "pop3.mail.server"
12810 :password "secret")))
12814 When you use a mail back end, Gnus will slurp all your mail from your
12815 inbox and plonk it down in your home directory. Gnus doesn't move any
12816 mail if you're not using a mail back end---you have to do a lot of magic
12817 invocations first. At the time when you have finished drawing the
12818 pentagram, lightened the candles, and sacrificed the goat, you really
12819 shouldn't be too surprised when Gnus moves your mail.
12823 @node Mail Back End Variables
12824 @subsection Mail Back End Variables
12826 These variables are (for the most part) pertinent to all the various
12830 @vindex nnmail-read-incoming-hook
12831 @item nnmail-read-incoming-hook
12832 The mail back ends all call this hook after reading new mail. You can
12833 use this hook to notify any mail watch programs, if you want to.
12835 @vindex nnmail-split-hook
12836 @item nnmail-split-hook
12837 @findex article-decode-encoded-words
12838 @findex RFC 1522 decoding
12839 @findex RFC 2047 decoding
12840 Hook run in the buffer where the mail headers of each message is kept
12841 just before the splitting based on these headers is done. The hook is
12842 free to modify the buffer contents in any way it sees fit---the buffer
12843 is discarded after the splitting has been done, and no changes performed
12844 in the buffer will show up in any files.
12845 @code{gnus-article-decode-encoded-words} is one likely function to add
12848 @vindex nnmail-pre-get-new-mail-hook
12849 @vindex nnmail-post-get-new-mail-hook
12850 @item nnmail-pre-get-new-mail-hook
12851 @itemx nnmail-post-get-new-mail-hook
12852 These are two useful hooks executed when treating new incoming
12853 mail---@code{nnmail-pre-get-new-mail-hook} (is called just before
12854 starting to handle the new mail) and
12855 @code{nnmail-post-get-new-mail-hook} (is called when the mail handling
12856 is done). Here's and example of using these two hooks to change the
12857 default file modes the new mail files get:
12860 (add-hook 'nnmail-pre-get-new-mail-hook
12861 (lambda () (set-default-file-modes 511)))
12863 (add-hook 'nnmail-post-get-new-mail-hook
12864 (lambda () (set-default-file-modes 551)))
12867 @item nnmail-use-long-file-names
12868 @vindex nnmail-use-long-file-names
12869 If non-@code{nil}, the mail back ends will use long file and directory
12870 names. Groups like @samp{mail.misc} will end up in directories
12871 (assuming use of @code{nnml} back end) or files (assuming use of
12872 @code{nnfolder} back end) like @file{mail.misc}. If it is @code{nil},
12873 the same group will end up in @file{mail/misc}.
12875 @item nnmail-delete-file-function
12876 @vindex nnmail-delete-file-function
12877 @findex delete-file
12878 Function called to delete files. It is @code{delete-file} by default.
12880 @item nnmail-cache-accepted-message-ids
12881 @vindex nnmail-cache-accepted-message-ids
12882 If non-@code{nil}, put the @code{Message-ID}s of articles imported into
12883 the back end (via @code{Gcc}, for instance) into the mail duplication
12884 discovery cache. The default is @code{nil}.
12889 @node Fancy Mail Splitting
12890 @subsection Fancy Mail Splitting
12891 @cindex mail splitting
12892 @cindex fancy mail splitting
12894 @vindex nnmail-split-fancy
12895 @findex nnmail-split-fancy
12896 If the rather simple, standard method for specifying how to split mail
12897 doesn't allow you to do what you want, you can set
12898 @code{nnmail-split-methods} to @code{nnmail-split-fancy}. Then you can
12899 play with the @code{nnmail-split-fancy} variable.
12901 Let's look at an example value of this variable first:
12904 ;; Messages from the mailer daemon are not crossposted to any of
12905 ;; the ordinary groups. Warnings are put in a separate group
12906 ;; from real errors.
12907 (| ("from" mail (| ("subject" "warn.*" "mail.warning")
12909 ;; Non-error messages are crossposted to all relevant
12910 ;; groups, but we don't crosspost between the group for the
12911 ;; (ding) list and the group for other (ding) related mail.
12912 (& (| (any "ding@@ifi\\.uio\\.no" "ding.list")
12913 ("subject" "ding" "ding.misc"))
12914 ;; Other mailing lists...
12915 (any "procmail@@informatik\\.rwth-aachen\\.de" "procmail.list")
12916 (any "SmartList@@informatik\\.rwth-aachen\\.de" "SmartList.list")
12917 ;; Both lists below have the same suffix, so prevent
12918 ;; cross-posting to mkpkg.list of messages posted only to
12919 ;; the bugs- list, but allow cross-posting when the
12920 ;; message was really cross-posted.
12921 (any "bugs-mypackage@@somewhere" "mypkg.bugs")
12922 (any "mypackage@@somewhere\" - "bugs-mypackage" "mypkg.list")
12924 (any "larsi@@ifi\\.uio\\.no" "people.Lars_Magne_Ingebrigtsen"))
12925 ;; Unmatched mail goes to the catch all group.
12929 This variable has the format of a @dfn{split}. A split is a (possibly)
12930 recursive structure where each split may contain other splits. Here are
12931 the five possible split syntaxes:
12936 @samp{group}: If the split is a string, that will be taken as a group
12937 name. Normal regexp match expansion will be done. See below for
12941 @code{(@var{field} @var{value} @code{[-} @var{restrict}
12942 @code{[@dots{}]}@code{]} @var{split})}: If the split is a list, the
12943 first element of which is a string, then store the message as
12944 specified by @var{split}, if header @var{field} (a regexp) contains
12945 @var{value} (also a regexp). If @var{restrict} (yet another regexp)
12946 matches some string after @var{field} and before the end of the
12947 matched @var{value}, the @var{split} is ignored. If none of the
12948 @var{restrict} clauses match, @var{split} is processed.
12951 @code{(| @var{split}@dots{})}: If the split is a list, and the first
12952 element is @code{|} (vertical bar), then process each @var{split} until
12953 one of them matches. A @var{split} is said to match if it will cause
12954 the mail message to be stored in one or more groups.
12957 @code{(& @var{split}@dots{})}: If the split is a list, and the first
12958 element is @code{&}, then process all @var{split}s in the list.
12961 @code{junk}: If the split is the symbol @code{junk}, then don't save
12962 (i.e., delete) this message. Use with extreme caution.
12965 @code{(: @var{function} @var{arg1} @var{arg2} @dots{})}: If the split is
12966 a list, and the first element is @code{:}, then the second element will
12967 be called as a function with @var{args} given as arguments. The
12968 function should return a @var{split}.
12971 For instance, the following function could be used to split based on the
12972 body of the messages:
12975 (defun split-on-body ()
12977 (set-buffer " *nnmail incoming*")
12978 (goto-char (point-min))
12979 (when (re-search-forward "Some.*string" nil t)
12983 The @samp{" *nnmail incoming*"} is narrowed to the message in question
12984 when the @code{:} function is run.
12987 @code{(! @var{func} @var{split})}: If the split is a list, and the first
12988 element is @code{!}, then SPLIT will be processed, and FUNC will be
12989 called as a function with the result of SPLIT as argument. FUNC should
12993 @code{nil}: If the split is @code{nil}, it is ignored.
12997 In these splits, @var{field} must match a complete field name.
12998 @var{value} must match a complete word according to the fundamental mode
12999 syntax table. You can use @code{.*} in the regexps to match partial
13000 field names or words. In other words, all @var{value}'s are wrapped in
13001 @samp{\<} and @samp{\>} pairs.
13003 @vindex nnmail-split-abbrev-alist
13004 @var{field} and @var{value} can also be lisp symbols, in that case they
13005 are expanded as specified by the variable
13006 @code{nnmail-split-abbrev-alist}. This is an alist of cons cells, where
13007 the @code{car} of a cell contains the key, and the @code{cdr} contains the associated
13010 @vindex nnmail-split-fancy-syntax-table
13011 @code{nnmail-split-fancy-syntax-table} is the syntax table in effect
13012 when all this splitting is performed.
13014 If you want to have Gnus create groups dynamically based on some
13015 information in the headers (i.e., do @code{replace-match}-like
13016 substitutions in the group names), you can say things like:
13019 (any "debian-\\b\\(\\w+\\)@@lists.debian.org" "mail.debian.\\1")
13022 In this example, messages sent to @samp{debian-foo@@lists.debian.org}
13023 will be filed in @samp{mail.debian.foo}.
13025 If the string contains the element @samp{\&}, then the previously
13026 matched string will be substituted. Similarly, the elements @samp{\\1}
13027 up to @samp{\\9} will be substituted with the text matched by the
13028 groupings 1 through 9.
13030 @findex nnmail-split-fancy-with-parent
13031 @code{nnmail-split-fancy-with-parent} is a function which allows you to
13032 split followups into the same groups their parents are in. Sometimes
13033 you can't make splitting rules for all your mail. For example, your
13034 boss might send you personal mail regarding different projects you are
13035 working on, and as you can't tell your boss to put a distinguishing
13036 string into the subject line, you have to resort to manually moving the
13037 messages into the right group. With this function, you only have to do
13038 it once per thread.
13040 To use this feature, you have to set @code{nnmail-treat-duplicates} and
13041 @code{nnmail-cache-accepted-message-ids} to a non-nil value. And then
13042 you can include @code{nnmail-split-fancy-with-parent} using the colon
13045 (setq nnmail-split-fancy
13046 '(| (: nnmail-split-fancy-with-parent)
13047 ;; other splits go here
13051 This feature works as follows: when @code{nnmail-treat-duplicates} is
13052 non-nil, Gnus records the message id of every message it sees in the
13053 file specified by the variable @code{nnmail-message-id-cache-file},
13054 together with the group it is in (the group is omitted for non-mail
13055 messages). When mail splitting is invoked, the function
13056 @code{nnmail-split-fancy-with-parent} then looks at the References (and
13057 In-Reply-To) header of each message to split and searches the file
13058 specified by @code{nnmail-message-id-cache-file} for the message ids.
13059 When it has found a parent, it returns the corresponding group name
13060 unless the group name matches the regexp
13061 @code{nnmail-split-fancy-with-parent-ignore-groups}. It is recommended
13062 that you set @code{nnmail-message-id-cache-length} to a somewhat higher
13063 number than the default so that the message ids are still in the cache.
13064 (A value of 5000 appears to create a file some 300 kBytes in size.)
13065 @vindex nnmail-cache-accepted-message-ids
13066 When @code{nnmail-cache-accepted-message-ids} is non-@code{nil}, Gnus
13067 also records the message ids of moved articles, so that the followup
13068 messages goes into the new group.
13071 @node Group Mail Splitting
13072 @subsection Group Mail Splitting
13073 @cindex mail splitting
13074 @cindex group mail splitting
13076 @findex gnus-group-split
13077 If you subscribe to dozens of mailing lists but you don't want to
13078 maintain mail splitting rules manually, group mail splitting is for you.
13079 You just have to set @var{to-list} and/or @var{to-address} in group
13080 parameters or group customization and set @code{nnmail-split-methods} to
13081 @code{gnus-group-split}. This splitting function will scan all groups
13082 for those parameters and split mail accordingly, i.e., messages posted
13083 from or to the addresses specified in the parameters @var{to-list} or
13084 @var{to-address} of a mail group will be stored in that group.
13086 Sometimes, mailing lists have multiple addresses, and you may want mail
13087 splitting to recognize them all: just set the @var{extra-aliases} group
13088 parameter to the list of additional addresses and it's done. If you'd
13089 rather use a regular expression, set @var{split-regexp}.
13091 All these parameters in a group will be used to create an
13092 @code{nnmail-split-fancy} split, in which the @var{field} is @samp{any},
13093 the @var{value} is a single regular expression that matches
13094 @var{to-list}, @var{to-address}, all of @var{extra-aliases} and all
13095 matches of @var{split-regexp}, and the @var{split} is the name of the
13096 group. @var{restrict}s are also supported: just set the
13097 @var{split-exclude} parameter to a list of regular expressions.
13099 If you can't get the right split to be generated using all these
13100 parameters, or you just need something fancier, you can set the
13101 parameter @var{split-spec} to an @code{nnmail-split-fancy} split. In
13102 this case, all other aforementioned parameters will be ignored by
13103 @code{gnus-group-split}. In particular, @var{split-spec} may be set to
13104 @code{nil}, in which case the group will be ignored by
13105 @code{gnus-group-split}.
13107 @vindex gnus-group-split-default-catch-all-group
13108 @code{gnus-group-split} will do cross-posting on all groups that match,
13109 by defining a single @code{&} fancy split containing one split for each
13110 group. If a message doesn't match any split, it will be stored in the
13111 group named in @code{gnus-group-split-default-catch-all-group}, unless
13112 some group has @var{split-spec} set to @code{catch-all}, in which case
13113 that group is used as the catch-all group. Even though this variable is
13114 often used just to name a group, it may also be set to an arbitrarily
13115 complex fancy split (after all, a group name is a fancy split), and this
13116 may be useful to split mail that doesn't go to any mailing list to
13117 personal mail folders. Note that this fancy split is added as the last
13118 element of a @code{|} split list that also contains a @code{&} split
13119 with the rules extracted from group parameters.
13121 It's time for an example. Assume the following group parameters have
13126 ((to-address . "bar@@femail.com")
13127 (split-regexp . ".*@@femail\\.com"))
13129 ((to-list . "foo@@nowhere.gov")
13130 (extra-aliases "foo@@localhost" "foo-redist@@home")
13131 (split-exclude "bugs-foo" "rambling-foo")
13132 (admin-address . "foo-request@@nowhere.gov"))
13134 ((split-spec . catch-all))
13137 Setting @code{nnmail-split-methods} to @code{gnus-group-split} will
13138 behave as if @code{nnmail-split-fancy} had been selected and variable
13139 @code{nnmail-split-fancy} had been set as follows:
13142 (| (& (any "\\(bar@@femail\\.com\\|.*@@femail\\.com\\)" "mail.bar")
13143 (any "\\(foo@@nowhere\\.gov\\|foo@@localhost\\|foo-redist@@home\\)"
13144 - "bugs-foo" - "rambling-foo" "mail.foo"))
13148 @findex gnus-group-split-fancy
13149 If you'd rather not use group splitting for all your mail groups, you
13150 may use it for only some of them, by using @code{nnmail-split-fancy}
13154 (: gnus-mlsplt-fancy GROUPS NO-CROSSPOST CATCH-ALL)
13157 @var{groups} may be a regular expression or a list of group names whose
13158 parameters will be scanned to generate the output split.
13159 @var{no-crosspost} can be used to disable cross-posting; in this case, a
13160 single @code{|} split will be output. @var{catch-all} is the fallback
13161 fancy split, used like @var{gnus-group-split-default-catch-all-group}.
13162 If @var{catch-all} is @code{nil}, or if @var{split-regexp} matches the
13163 empty string in any selected group, no catch-all split will be issued.
13164 Otherwise, if some group has @var{split-spec} set to @code{catch-all},
13165 this group will override the value of the @var{catch-all} argument.
13167 @findex gnus-group-split-setup
13168 Unfortunately, scanning all groups and their parameters can be quite
13169 slow, especially considering that it has to be done for every message.
13170 But don't despair! The function @code{gnus-group-split-setup} can be
13171 used to enable @code{gnus-group-split} in a much more efficient way. It
13172 sets @code{nnmail-split-methods} to @code{nnmail-split-fancy} and sets
13173 @code{nnmail-split-fancy} to the split produced by
13174 @code{gnus-group-split-fancy}. Thus, the group parameters are only
13175 scanned once, no matter how many messages are split.
13177 @findex gnus-group-split-update
13178 However, if you change group parameters, you'd have to update
13179 @code{nnmail-split-fancy} manually. You can do it by running
13180 @code{gnus-group-split-update}. If you'd rather have it updated
13181 automatically, just tell @code{gnus-group-split-setup} to do it for
13182 you. For example, add to your @file{.gnus}:
13185 (gnus-group-split-setup AUTO-UPDATE CATCH-ALL)
13188 If @var{auto-update} is non-@code{nil}, @code{gnus-group-split-update}
13189 will be added to @code{nnmail-pre-get-new-mail-hook}, so you won't ever
13190 have to worry about updating @code{nnmail-split-fancy} again. If you
13191 don't omit @var{catch-all} (it's optional, equivalent to @code{nil}),
13192 @code{gnus-group-split-default-catch-all-group} will be set to its
13195 @vindex gnus-group-split-updated-hook
13196 Because you may want to change @code{nnmail-split-fancy} after it is set
13197 by @code{gnus-group-split-update}, this function will run
13198 @code{gnus-group-split-updated-hook} just before finishing.
13200 @node Incorporating Old Mail
13201 @subsection Incorporating Old Mail
13202 @cindex incorporating old mail
13203 @cindex import old mail
13205 Most people have lots of old mail stored in various file formats. If
13206 you have set up Gnus to read mail using one of the spiffy Gnus mail
13207 back ends, you'll probably wish to have that old mail incorporated into
13210 Doing so can be quite easy.
13212 To take an example: You're reading mail using @code{nnml}
13213 (@pxref{Mail Spool}), and have set @code{nnmail-split-methods} to a
13214 satisfactory value (@pxref{Splitting Mail}). You have an old Unix mbox
13215 file filled with important, but old, mail. You want to move it into
13216 your @code{nnml} groups.
13222 Go to the group buffer.
13225 Type `G f' and give the path to the mbox file when prompted to create an
13226 @code{nndoc} group from the mbox file (@pxref{Foreign Groups}).
13229 Type `SPACE' to enter the newly created group.
13232 Type `M P b' to process-mark all articles in this group's buffer
13233 (@pxref{Setting Process Marks}).
13236 Type `B r' to respool all the process-marked articles, and answer
13237 @samp{nnml} when prompted (@pxref{Mail Group Commands}).
13240 All the mail messages in the mbox file will now also be spread out over
13241 all your @code{nnml} groups. Try entering them and check whether things
13242 have gone without a glitch. If things look ok, you may consider
13243 deleting the mbox file, but I wouldn't do that unless I was absolutely
13244 sure that all the mail has ended up where it should be.
13246 Respooling is also a handy thing to do if you're switching from one mail
13247 back end to another. Just respool all the mail in the old mail groups
13248 using the new mail back end.
13251 @node Expiring Mail
13252 @subsection Expiring Mail
13253 @cindex article expiry
13255 Traditional mail readers have a tendency to remove mail articles when
13256 you mark them as read, in some way. Gnus takes a fundamentally
13257 different approach to mail reading.
13259 Gnus basically considers mail just to be news that has been received in
13260 a rather peculiar manner. It does not think that it has the power to
13261 actually change the mail, or delete any mail messages. If you enter a
13262 mail group, and mark articles as ``read'', or kill them in some other
13263 fashion, the mail articles will still exist on the system. I repeat:
13264 Gnus will not delete your old, read mail. Unless you ask it to, of
13267 To make Gnus get rid of your unwanted mail, you have to mark the
13268 articles as @dfn{expirable}. This does not mean that the articles will
13269 disappear right away, however. In general, a mail article will be
13270 deleted from your system if, 1) it is marked as expirable, AND 2) it is
13271 more than one week old. If you do not mark an article as expirable, it
13272 will remain on your system until hell freezes over. This bears
13273 repeating one more time, with some spurious capitalizations: IF you do
13274 NOT mark articles as EXPIRABLE, Gnus will NEVER delete those ARTICLES.
13276 @vindex gnus-auto-expirable-newsgroups
13277 You do not have to mark articles as expirable by hand. Groups that
13278 match the regular expression @code{gnus-auto-expirable-newsgroups} will
13279 have all articles that you read marked as expirable automatically. All
13280 articles marked as expirable have an @samp{E} in the first
13281 column in the summary buffer.
13283 By default, if you have auto expiry switched on, Gnus will mark all the
13284 articles you read as expirable, no matter if they were read or unread
13285 before. To avoid having articles marked as read marked as expirable
13286 automatically, you can put something like the following in your
13289 @vindex gnus-mark-article-hook
13291 (remove-hook 'gnus-mark-article-hook
13292 'gnus-summary-mark-read-and-unread-as-read)
13293 (add-hook 'gnus-mark-article-hook 'gnus-summary-mark-unread-as-read)
13296 Note that making a group auto-expirable doesn't mean that all read
13297 articles are expired---only the articles marked as expirable
13298 will be expired. Also note that using the @kbd{d} command won't make
13299 articles expirable---only semi-automatic marking of articles as read will
13300 mark the articles as expirable in auto-expirable groups.
13302 Let's say you subscribe to a couple of mailing lists, and you want the
13303 articles you have read to disappear after a while:
13306 (setq gnus-auto-expirable-newsgroups
13307 "mail.nonsense-list\\|mail.nice-list")
13310 Another way to have auto-expiry happen is to have the element
13311 @code{auto-expire} in the group parameters of the group.
13313 If you use adaptive scoring (@pxref{Adaptive Scoring}) and
13314 auto-expiring, you'll have problems. Auto-expiring and adaptive scoring
13315 don't really mix very well.
13317 @vindex nnmail-expiry-wait
13318 The @code{nnmail-expiry-wait} variable supplies the default time an
13319 expirable article has to live. Gnus starts counting days from when the
13320 message @emph{arrived}, not from when it was sent. The default is seven
13323 Gnus also supplies a function that lets you fine-tune how long articles
13324 are to live, based on what group they are in. Let's say you want to
13325 have one month expiry period in the @samp{mail.private} group, a one day
13326 expiry period in the @samp{mail.junk} group, and a six day expiry period
13329 @vindex nnmail-expiry-wait-function
13331 (setq nnmail-expiry-wait-function
13333 (cond ((string= group "mail.private")
13335 ((string= group "mail.junk")
13337 ((string= group "important")
13343 The group names this function is fed are ``unadorned'' group
13344 names---no @samp{nnml:} prefixes and the like.
13346 The @code{nnmail-expiry-wait} variable and
13347 @code{nnmail-expiry-wait-function} function can either be a number (not
13348 necessarily an integer) or one of the symbols @code{immediate} or
13351 You can also use the @code{expiry-wait} group parameter to selectively
13352 change the expiry period (@pxref{Group Parameters}).
13354 @vindex nnmail-expiry-target
13355 The normal action taken when expiring articles is to delete them.
13356 However, in some circumstances it might make more sense to move them
13357 to other groups instead of deleting them. The variable
13358 @code{nnmail-expiry-target} (and the @code{expiry-target} group
13359 parameter) controls this. The variable supplies a default value for
13360 all groups, which can be overridden for specific groups by the group
13361 parameter. default value is @code{delete}, but this can also be a
13362 string (which should be the name of the group the message should be
13363 moved to), or a function (which will be called in a buffer narrowed to
13364 the message in question, and with the name of the group being moved
13365 from as its parameter) which should return a target -- either a group
13366 name or @code{delete}.
13368 Here's an example for specifying a group name:
13370 (setq nnmail-expiry-target "nnml:expired")
13373 @findex nnmail-fancy-expiry-target
13374 @vindex nnmail-fancy-expiry-targets
13375 Gnus provides a function @code{nnmail-fancy-expiry-target} which will
13376 expire mail to groups according to the variable
13377 @code{nnmail-fancy-expiry-targets}. Here's an example:
13380 (setq nnmail-expiry-target 'nnmail-fancy-expiry-target
13381 nnmail-fancy-expiry-targets
13382 '((to-from "boss" "nnfolder:Work")
13383 ("subject" "IMPORTANT" "nnfolder:IMPORTANT.%Y.%b")
13384 ("from" ".*" "nnfolder:Archive-%Y")))
13387 With this setup, any mail that has @code{IMPORTANT} in its Subject
13388 header and was sent in the year @code{YYYY} and month @code{MMM}, will
13389 get expired to the group @code{nnfolder:IMPORTANT.YYYY.MMM}. If its
13390 From or To header contains the string @code{boss}, it will get expired
13391 to @code{nnfolder:Work}. All other mail will get expired to
13392 @code{nnfolder:Archive-YYYY}.
13394 @vindex nnmail-keep-last-article
13395 If @code{nnmail-keep-last-article} is non-@code{nil}, Gnus will never
13396 expire the final article in a mail newsgroup. This is to make life
13397 easier for procmail users.
13399 @vindex gnus-total-expirable-newsgroups
13400 By the way: That line up there, about Gnus never expiring non-expirable
13401 articles, is a lie. If you put @code{total-expire} in the group
13402 parameters, articles will not be marked as expirable, but all read
13403 articles will be put through the expiry process. Use with extreme
13404 caution. Even more dangerous is the
13405 @code{gnus-total-expirable-newsgroups} variable. All groups that match
13406 this regexp will have all read articles put through the expiry process,
13407 which means that @emph{all} old mail articles in the groups in question
13408 will be deleted after a while. Use with extreme caution, and don't come
13409 crying to me when you discover that the regexp you used matched the
13410 wrong group and all your important mail has disappeared. Be a
13411 @emph{man}! Or a @emph{woman}! Whatever you feel more comfortable
13414 Most people make most of their mail groups total-expirable, though.
13416 @vindex gnus-inhibit-user-auto-expire
13417 If @code{gnus-inhibit-user-auto-expire} is non-@code{nil}, user marking
13418 commands will not mark an article as expirable, even if the group has
13419 auto-expire turned on.
13423 @subsection Washing Mail
13424 @cindex mail washing
13425 @cindex list server brain damage
13426 @cindex incoming mail treatment
13428 Mailers and list servers are notorious for doing all sorts of really,
13429 really stupid things with mail. ``Hey, RFC 822 doesn't explicitly
13430 prohibit us from adding the string @code{wE aRe ElItE!!!!!1!!} to the
13431 end of all lines passing through our server, so let's do that!!!!1!''
13432 Yes, but RFC 822 wasn't designed to be read by morons. Things that were
13433 considered to be self-evident were not discussed. So. Here we are.
13435 Case in point: The German version of Microsoft Exchange adds @samp{AW:
13436 } to the subjects of replies instead of @samp{Re: }. I could pretend to
13437 be shocked and dismayed by this, but I haven't got the energy. It is to
13440 Gnus provides a plethora of functions for washing articles while
13441 displaying them, but it might be nicer to do the filtering before
13442 storing the mail to disc. For that purpose, we have three hooks and
13443 various functions that can be put in these hooks.
13446 @item nnmail-prepare-incoming-hook
13447 @vindex nnmail-prepare-incoming-hook
13448 This hook is called before doing anything with the mail and is meant for
13449 grand, sweeping gestures. It is called in a buffer that contains all
13450 the new, incoming mail. Functions to be used include:
13453 @item nnheader-ms-strip-cr
13454 @findex nnheader-ms-strip-cr
13455 Remove trailing carriage returns from each line. This is default on
13456 Emacs running on MS machines.
13460 @item nnmail-prepare-incoming-header-hook
13461 @vindex nnmail-prepare-incoming-header-hook
13462 This hook is called narrowed to each header. It can be used when
13463 cleaning up the headers. Functions that can be used include:
13466 @item nnmail-remove-leading-whitespace
13467 @findex nnmail-remove-leading-whitespace
13468 Clear leading white space that ``helpful'' listservs have added to the
13469 headers to make them look nice. Aaah.
13471 @item nnmail-remove-list-identifiers
13472 @findex nnmail-remove-list-identifiers
13473 Some list servers add an identifier---for example, @samp{(idm)}---to the
13474 beginning of all @code{Subject} headers. I'm sure that's nice for
13475 people who use stone age mail readers. This function will remove
13476 strings that match the @code{nnmail-list-identifiers} regexp, which can
13477 also be a list of regexp. @code{nnmail-list-identifiers} may not contain
13480 For instance, if you want to remove the @samp{(idm)} and the
13481 @samp{nagnagnag} identifiers:
13484 (setq nnmail-list-identifiers
13485 '("(idm)" "nagnagnag"))
13488 This can also be done non-destructively with
13489 @code{gnus-list-identifiers}, @xref{Article Hiding}.
13491 @item nnmail-remove-tabs
13492 @findex nnmail-remove-tabs
13493 Translate all @samp{TAB} characters into @samp{SPACE} characters.
13495 @item nnmail-fix-eudora-headers
13496 @findex nnmail-fix-eudora-headers
13498 Eudora produces broken @code{References} headers, but OK
13499 @code{In-Reply-To} headers. This function will get rid of the
13500 @code{References} headers.
13504 @item nnmail-prepare-incoming-message-hook
13505 @vindex nnmail-prepare-incoming-message-hook
13506 This hook is called narrowed to each message. Functions to be used
13510 @item article-de-quoted-unreadable
13511 @findex article-de-quoted-unreadable
13512 Decode Quoted Readable encoding.
13519 @subsection Duplicates
13521 @vindex nnmail-treat-duplicates
13522 @vindex nnmail-message-id-cache-length
13523 @vindex nnmail-message-id-cache-file
13524 @cindex duplicate mails
13525 If you are a member of a couple of mailing lists, you will sometimes
13526 receive two copies of the same mail. This can be quite annoying, so
13527 @code{nnmail} checks for and treats any duplicates it might find. To do
13528 this, it keeps a cache of old @code{Message-ID}s---
13529 @code{nnmail-message-id-cache-file}, which is @file{~/.nnmail-cache} by
13530 default. The approximate maximum number of @code{Message-ID}s stored
13531 there is controlled by the @code{nnmail-message-id-cache-length}
13532 variable, which is 1000 by default. (So 1000 @code{Message-ID}s will be
13533 stored.) If all this sounds scary to you, you can set
13534 @code{nnmail-treat-duplicates} to @code{warn} (which is what it is by
13535 default), and @code{nnmail} won't delete duplicate mails. Instead it
13536 will insert a warning into the head of the mail saying that it thinks
13537 that this is a duplicate of a different message.
13539 This variable can also be a function. If that's the case, the function
13540 will be called from a buffer narrowed to the message in question with
13541 the @code{Message-ID} as a parameter. The function must return either
13542 @code{nil}, @code{warn}, or @code{delete}.
13544 You can turn this feature off completely by setting the variable to
13547 If you want all the duplicate mails to be put into a special
13548 @dfn{duplicates} group, you could do that using the normal mail split
13552 (setq nnmail-split-fancy
13553 '(| ;; Messages duplicates go to a separate group.
13554 ("gnus-warning" "duplicat\\(e\\|ion\\) of message" "duplicate")
13555 ;; Message from daemons, postmaster, and the like to another.
13556 (any mail "mail.misc")
13563 (setq nnmail-split-methods
13564 '(("duplicates" "^Gnus-Warning:.*duplicate")
13569 Here's a neat feature: If you know that the recipient reads her mail
13570 with Gnus, and that she has @code{nnmail-treat-duplicates} set to
13571 @code{delete}, you can send her as many insults as you like, just by
13572 using a @code{Message-ID} of a mail that you know that she's already
13573 received. Think of all the fun! She'll never see any of it! Whee!
13576 @node Not Reading Mail
13577 @subsection Not Reading Mail
13579 If you start using any of the mail back ends, they have the annoying
13580 habit of assuming that you want to read mail with them. This might not
13581 be unreasonable, but it might not be what you want.
13583 If you set @code{mail-sources} and @code{nnmail-spool-file} to
13584 @code{nil}, none of the back ends will ever attempt to read incoming
13585 mail, which should help.
13587 @vindex nnbabyl-get-new-mail
13588 @vindex nnmbox-get-new-mail
13589 @vindex nnml-get-new-mail
13590 @vindex nnmh-get-new-mail
13591 @vindex nnfolder-get-new-mail
13592 This might be too much, if, for instance, you are reading mail quite
13593 happily with @code{nnml} and just want to peek at some old @sc{rmail}
13594 file you have stashed away with @code{nnbabyl}. All back ends have
13595 variables called back-end-@code{get-new-mail}. If you want to disable
13596 the @code{nnbabyl} mail reading, you edit the virtual server for the
13597 group to have a setting where @code{nnbabyl-get-new-mail} to @code{nil}.
13599 All the mail back ends will call @code{nn}*@code{-prepare-save-mail-hook}
13600 narrowed to the article to be saved before saving it when reading
13604 @node Choosing a Mail Back End
13605 @subsection Choosing a Mail Back End
13607 Gnus will read the mail spool when you activate a mail group. The mail
13608 file is first copied to your home directory. What happens after that
13609 depends on what format you want to store your mail in.
13611 There are six different mail back ends in the standard Gnus, and more
13612 back ends are available separately. The mail back end most people use
13613 (because it is possibly the fastest) is @code{nnml} (@pxref{Mail
13614 Spool}). You might notice that only five back ends are listed below;
13615 @code{nnmaildir}'s documentation has not yet been completely
13616 incorporated into this manual. Until it is, you can find it at
13617 @uref{http://multivac.cwru.edu./nnmaildir/}.
13620 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
13621 * Rmail Babyl:: Emacs programs use the rmail babyl format.
13622 * Mail Spool:: Store your mail in a private spool?
13623 * MH Spool:: An mhspool-like back end.
13624 * Mail Folders:: Having one file for each group.
13625 * Comparing Mail Back Ends:: An in-depth looks at pros and cons.
13629 @node Unix Mail Box
13630 @subsubsection Unix Mail Box
13632 @cindex unix mail box
13634 @vindex nnmbox-active-file
13635 @vindex nnmbox-mbox-file
13636 The @dfn{nnmbox} back end will use the standard Un*x mbox file to store
13637 mail. @code{nnmbox} will add extra headers to each mail article to say
13638 which group it belongs in.
13640 Virtual server settings:
13643 @item nnmbox-mbox-file
13644 @vindex nnmbox-mbox-file
13645 The name of the mail box in the user's home directory. Default is
13648 @item nnmbox-active-file
13649 @vindex nnmbox-active-file
13650 The name of the active file for the mail box. Default is
13651 @file{~/.mbox-active}.
13653 @item nnmbox-get-new-mail
13654 @vindex nnmbox-get-new-mail
13655 If non-@code{nil}, @code{nnmbox} will read incoming mail and split it
13656 into groups. Default is @code{t}.
13661 @subsubsection Rmail Babyl
13665 @vindex nnbabyl-active-file
13666 @vindex nnbabyl-mbox-file
13667 The @dfn{nnbabyl} back end will use a babyl mail box (aka. @dfn{rmail
13668 mbox}) to store mail. @code{nnbabyl} will add extra headers to each
13669 mail article to say which group it belongs in.
13671 Virtual server settings:
13674 @item nnbabyl-mbox-file
13675 @vindex nnbabyl-mbox-file
13676 The name of the rmail mbox file. The default is @file{~/RMAIL}
13678 @item nnbabyl-active-file
13679 @vindex nnbabyl-active-file
13680 The name of the active file for the rmail box. The default is
13681 @file{~/.rmail-active}
13683 @item nnbabyl-get-new-mail
13684 @vindex nnbabyl-get-new-mail
13685 If non-@code{nil}, @code{nnbabyl} will read incoming mail. Default is
13691 @subsubsection Mail Spool
13693 @cindex mail @sc{nov} spool
13695 The @dfn{nnml} spool mail format isn't compatible with any other known
13696 format. It should be used with some caution.
13698 @vindex nnml-directory
13699 If you use this back end, Gnus will split all incoming mail into files,
13700 one file for each mail, and put the articles into the corresponding
13701 directories under the directory specified by the @code{nnml-directory}
13702 variable. The default value is @file{~/Mail/}.
13704 You do not have to create any directories beforehand; Gnus will take
13707 If you have a strict limit as to how many files you are allowed to store
13708 in your account, you should not use this back end. As each mail gets its
13709 own file, you might very well occupy thousands of inodes within a few
13710 weeks. If this is no problem for you, and it isn't a problem for you
13711 having your friendly systems administrator walking around, madly,
13712 shouting ``Who is eating all my inodes?! Who? Who!?!'', then you should
13713 know that this is probably the fastest format to use. You do not have
13714 to trudge through a big mbox file just to read your new mail.
13716 @code{nnml} is probably the slowest back end when it comes to article
13717 splitting. It has to create lots of files, and it also generates
13718 @sc{nov} databases for the incoming mails. This makes it the fastest
13719 back end when it comes to reading mail.
13721 @cindex self contained nnml servers
13722 When the marks file is used (which it is by default), @code{nnml}
13723 servers have the property that you may backup them using @code{tar} or
13724 similar, and later be able to restore them into Gnus (by adding the
13725 proper @code{nnml} server) and have all your marks be preserved. Marks
13726 for a group is usually stored in the @code{.marks} file (but see
13727 @code{nnml-marks-file-name}) within each @code{nnml} group's directory.
13728 Individual @code{nnml} groups are also possible to backup, use @kbd{G m}
13729 to restore the group (after restoring the backup into the nnml
13732 If for some reason you believe your @file{.marks} files are screwed
13733 up, you can just delete them all. Gnus will then correctly regenerate
13734 them next time it starts.
13736 Virtual server settings:
13739 @item nnml-directory
13740 @vindex nnml-directory
13741 All @code{nnml} directories will be placed under this directory.
13742 The default is the value of `message-directory' (whose default value is
13745 @item nnml-active-file
13746 @vindex nnml-active-file
13747 The active file for the @code{nnml} server. The default is
13748 @file{~/Mail/active"}.
13750 @item nnml-newsgroups-file
13751 @vindex nnml-newsgroups-file
13752 The @code{nnml} group descriptions file. @xref{Newsgroups File
13753 Format}. The default is @file{~/Mail/newsgroups"}.
13755 @item nnml-get-new-mail
13756 @vindex nnml-get-new-mail
13757 If non-@code{nil}, @code{nnml} will read incoming mail. The default is
13760 @item nnml-nov-is-evil
13761 @vindex nnml-nov-is-evil
13762 If non-@code{nil}, this back end will ignore any @sc{nov} files. The
13763 default is @code{nil}.
13765 @item nnml-nov-file-name
13766 @vindex nnml-nov-file-name
13767 The name of the @sc{nov} files. The default is @file{.overview}.
13769 @item nnml-prepare-save-mail-hook
13770 @vindex nnml-prepare-save-mail-hook
13771 Hook run narrowed to an article before saving.
13773 @item nnml-marks-is-evil
13774 @vindex nnml-marks-is-evil
13775 If non-@code{nil}, this back end will ignore any @sc{marks} files. The
13776 default is @code{nil}.
13778 @item nnml-marks-file-name
13779 @vindex nnml-marks-file-name
13780 The name of the @sc{marks} files. The default is @file{.marks}.
13784 @findex nnml-generate-nov-databases
13785 If your @code{nnml} groups and @sc{nov} files get totally out of whack,
13786 you can do a complete update by typing @kbd{M-x
13787 nnml-generate-nov-databases}. This command will trawl through the
13788 entire @code{nnml} hierarchy, looking at each and every article, so it
13789 might take a while to complete. A better interface to this
13790 functionality can be found in the server buffer (@pxref{Server
13795 @subsubsection MH Spool
13797 @cindex mh-e mail spool
13799 @code{nnmh} is just like @code{nnml}, except that is doesn't generate
13800 @sc{nov} databases and it doesn't keep an active file or marks file.
13801 This makes @code{nnmh} a @emph{much} slower back end than @code{nnml},
13802 but it also makes it easier to write procmail scripts for.
13804 Virtual server settings:
13807 @item nnmh-directory
13808 @vindex nnmh-directory
13809 All @code{nnmh} directories will be located under this directory. The
13810 default is the value of @code{message-directory} (whose default is
13813 @item nnmh-get-new-mail
13814 @vindex nnmh-get-new-mail
13815 If non-@code{nil}, @code{nnmh} will read incoming mail. The default is
13819 @vindex nnmh-be-safe
13820 If non-@code{nil}, @code{nnmh} will go to ridiculous lengths to make
13821 sure that the articles in the folder are actually what Gnus thinks they
13822 are. It will check date stamps and stat everything in sight, so
13823 setting this to @code{t} will mean a serious slow-down. If you never
13824 use anything but Gnus to read the @code{nnmh} articles, you do not have
13825 to set this variable to @code{t}. The default is @code{nil}.
13830 @subsubsection Mail Folders
13832 @cindex mbox folders
13833 @cindex mail folders
13835 @code{nnfolder} is a back end for storing each mail group in a separate
13836 file. Each file is in the standard Un*x mbox format. @code{nnfolder}
13837 will add extra headers to keep track of article numbers and arrival
13840 @cindex self contained nnfolder servers
13841 When the marks file is used (which it is by default), @code{nnfolder}
13842 servers have the property that you may backup them using @code{tar} or
13843 similar, and later be able to restore them into Gnus (by adding the
13844 proper @code{nnfolder} server) and have all your marks be preserved.
13845 Marks for a group is usually stored in a file named as the mbox file
13846 with @code{.mrk} concatenated to it (but see
13847 @code{nnfolder-marks-file-suffix}) within the @code{nnfolder} directory.
13848 Individual @code{nnfolder} groups are also possible to backup, use
13849 @kbd{G m} to restore the group (after restoring the backup into the
13850 @code{nnfolder} directory).
13852 Virtual server settings:
13855 @item nnfolder-directory
13856 @vindex nnfolder-directory
13857 All the @code{nnfolder} mail boxes will be stored under this directory.
13858 The default is the value of @code{message-directory} (whose default is
13861 @item nnfolder-active-file
13862 @vindex nnfolder-active-file
13863 The name of the active file. The default is @file{~/Mail/active}.
13865 @item nnfolder-newsgroups-file
13866 @vindex nnfolder-newsgroups-file
13867 The name of the group descriptions file. @xref{Newsgroups File
13868 Format}. The default is @file{~/Mail/newsgroups"}
13870 @item nnfolder-get-new-mail
13871 @vindex nnfolder-get-new-mail
13872 If non-@code{nil}, @code{nnfolder} will read incoming mail. The default
13875 @item nnfolder-save-buffer-hook
13876 @vindex nnfolder-save-buffer-hook
13877 @cindex backup files
13878 Hook run before saving the folders. Note that Emacs does the normal
13879 backup renaming of files even with the @code{nnfolder} buffers. If you
13880 wish to switch this off, you could say something like the following in
13881 your @file{.emacs} file:
13884 (defun turn-off-backup ()
13885 (set (make-local-variable 'backup-inhibited) t))
13887 (add-hook 'nnfolder-save-buffer-hook 'turn-off-backup)
13890 @item nnfolder-delete-mail-hook
13891 @vindex nnfolder-delete-mail-hook
13892 Hook run in a buffer narrowed to the message that is to be deleted.
13893 This function can be used to copy the message to somewhere else, or to
13894 extract some information from it before removing it.
13896 @item nnfolder-nov-is-evil
13897 @vindex nnfolder-nov-is-evil
13898 If non-@code{nil}, this back end will ignore any @sc{nov} files. The
13899 default is @code{nil}.
13901 @item nnfolder-nov-file-suffix
13902 @vindex nnfolder-nov-file-suffix
13903 The extension for @sc{nov} files. The default is @file{.nov}.
13905 @item nnfolder-nov-directory
13906 @vindex nnfolder-nov-directory
13907 The directory where the @sc{nov} files should be stored. If nil,
13908 @code{nnfolder-directory} is used.
13910 @item nnfolder-marks-is-evil
13911 @vindex nnfolder-marks-is-evil
13912 If non-@code{nil}, this back end will ignore any @sc{marks} files. The
13913 default is @code{nil}.
13915 @item nnfolder-marks-file-suffix
13916 @vindex nnfolder-marks-file-suffix
13917 The extension for @sc{marks} files. The default is @file{.mrk}.
13919 @item nnfolder-marks-directory
13920 @vindex nnfolder-marks-directory
13921 The directory where the @sc{marks} files should be stored. If nil,
13922 @code{nnfolder-directory} is used.
13927 @findex nnfolder-generate-active-file
13928 @kindex M-x nnfolder-generate-active-file
13929 If you have lots of @code{nnfolder}-like files you'd like to read with
13930 @code{nnfolder}, you can use the @kbd{M-x nnfolder-generate-active-file}
13931 command to make @code{nnfolder} aware of all likely files in
13932 @code{nnfolder-directory}. This only works if you use long file names,
13935 @node Comparing Mail Back Ends
13936 @subsubsection Comparing Mail Back Ends
13938 First, just for terminology, the @dfn{back end} is the common word for a
13939 low-level access method---a transport, if you will, by which something
13940 is acquired. The sense is that one's mail has to come from somewhere,
13941 and so selection of a suitable back end is required in order to get that
13942 mail within spitting distance of Gnus.
13944 The same concept exists for Usenet itself: Though access to articles is
13945 typically done by @sc{nntp} these days, once upon a midnight dreary, everyone
13946 in the world got at Usenet by running a reader on the machine where the
13947 articles lay (the machine which today we call an @sc{nntp} server), and
13948 access was by the reader stepping into the articles' directory spool
13949 area directly. One can still select between either the @code{nntp} or
13950 @code{nnspool} back ends, to select between these methods, if one happens
13951 actually to live on the server (or can see its spool directly, anyway,
13954 The goal in selecting a mail back end is to pick one which
13955 simultaneously represents a suitable way of dealing with the original
13956 format plus leaving mail in a form that is convenient to use in the
13957 future. Here are some high and low points on each:
13962 UNIX systems have historically had a single, very common, and well-
13963 defined format. All messages arrive in a single @dfn{spool file}, and
13964 they are delineated by a line whose regular expression matches
13965 @samp{^From_}. (My notational use of @samp{_} is to indicate a space,
13966 to make it clear in this instance that this is not the RFC-specified
13967 @samp{From:} header.) Because Emacs and therefore Gnus emanate
13968 historically from the Unix environment, it is simplest if one does not
13969 mess a great deal with the original mailbox format, so if one chooses
13970 this back end, Gnus' primary activity in getting mail from the real spool
13971 area to Gnus' preferred directory is simply to copy it, with no
13972 (appreciable) format change in the process. It is the ``dumbest'' way
13973 to move mail into availability in the Gnus environment. This makes it
13974 fast to move into place, but slow to parse, when Gnus has to look at
13979 Once upon a time, there was the DEC-10 and DEC-20, running operating
13980 systems called TOPS and related things, and the usual (only?) mail
13981 reading environment was a thing called Babyl. I don't know what format
13982 was used for mail landing on the system, but Babyl had its own internal
13983 format to which mail was converted, primarily involving creating a
13984 spool-file-like entity with a scheme for inserting Babyl-specific
13985 headers and status bits above the top of each message in the file.
13986 RMAIL was Emacs' first mail reader, it was written by Richard Stallman,
13987 and Stallman came out of that TOPS/Babyl environment, so he wrote RMAIL
13988 to understand the mail files folks already had in existence. Gnus (and
13989 VM, for that matter) continue to support this format because it's
13990 perceived as having some good qualities in those mailer-specific
13991 headers/status bits stuff. RMAIL itself still exists as well, of
13992 course, and is still maintained by Stallman.
13994 Both of the above forms leave your mail in a single file on your
13995 filesystem, and they must parse that entire file each time you take a
14000 @code{nnml} is the back end which smells the most as though you were
14001 actually operating with an @code{nnspool}-accessed Usenet system. (In
14002 fact, I believe @code{nnml} actually derived from @code{nnspool} code,
14003 lo these years ago.) One's mail is taken from the original spool file,
14004 and is then cut up into individual message files, 1:1. It maintains a
14005 Usenet-style active file (analogous to what one finds in an INN- or
14006 CNews-based news system in (for instance) @file{/var/lib/news/active},
14007 or what is returned via the @samp{NNTP LIST} verb) and also creates
14008 @dfn{overview} files for efficient group entry, as has been defined for
14009 @sc{nntp} servers for some years now. It is slower in mail-splitting,
14010 due to the creation of lots of files, updates to the @code{nnml} active
14011 file, and additions to overview files on a per-message basis, but it is
14012 extremely fast on access because of what amounts to the indexing support
14013 provided by the active file and overviews.
14015 @code{nnml} costs @dfn{inodes} in a big way; that is, it soaks up the
14016 resource which defines available places in the filesystem to put new
14017 files. Sysadmins take a dim view of heavy inode occupation within
14018 tight, shared filesystems. But if you live on a personal machine where
14019 the filesystem is your own and space is not at a premium, @code{nnml}
14022 It is also problematic using this back end if you are living in a
14023 FAT16-based Windows world, since much space will be wasted on all these
14028 The Rand MH mail-reading system has been around UNIX systems for a very
14029 long time; it operates by splitting one's spool file of messages into
14030 individual files, but with little or no indexing support -- @code{nnmh}
14031 is considered to be semantically equivalent to ``@code{nnml} without
14032 active file or overviews''. This is arguably the worst choice, because
14033 one gets the slowness of individual file creation married to the
14034 slowness of access parsing when learning what's new in one's groups.
14038 Basically the effect of @code{nnfolder} is @code{nnmbox} (the first
14039 method described above) on a per-group basis. That is, @code{nnmbox}
14040 itself puts *all* one's mail in one file; @code{nnfolder} provides a
14041 little bit of optimization to this so that each of one's mail groups has
14042 a Unix mail box file. It's faster than @code{nnmbox} because each group
14043 can be parsed separately, and still provides the simple Unix mail box
14044 format requiring minimal effort in moving the mail around. In addition,
14045 it maintains an ``active'' file making it much faster for Gnus to figure
14046 out how many messages there are in each separate group.
14048 If you have groups that are expected to have a massive amount of
14049 messages, @code{nnfolder} is not the best choice, but if you receive
14050 only a moderate amount of mail, @code{nnfolder} is probably the most
14051 friendly mail back end all over.
14055 @code{nnmaildir} is largely similar to @code{nnml}, with some notable
14056 differences. Each message is stored in a separate file, but the
14057 filename is unrelated to the article number in Gnus. @code{nnmaildir}
14058 also stores the equivalent of @code{nnml}'s overview files in one file
14059 per article, so it uses about twice as many inodes as @code{nnml}. (Use
14060 @code{df -i} to see how plentiful your inode supply is.) If this slows
14061 you down or takes up very much space, consider switching to ReiserFS
14062 (@uref{http://www.namesys.com/}) or another non-block-structured
14065 Since maildirs don't require locking for delivery, the maildirs you use
14066 as groups can also be the maildirs your mail is directly delivered to.
14067 This means you can skip Gnus's mail splitting if your mail is already
14068 organized into different mailboxes during delivery. A @code{directory}
14069 entry in @code{mail-sources} would have a similar effect, but would
14070 require one set of mailboxes for spooling deliveries (in mbox format,
14071 thus damaging message bodies), and another set to be used as groups (in
14072 whatever format you like). A maildir has a built-in spool, in the
14073 @code{new/} subdirectory. Beware that currently, mail moved from
14074 @code{new/} to @code{cur/} instead of via mail splitting will undergo
14075 treatment such as duplicate checking.
14077 An article will not necessarily keep the same number across Gnus
14078 sessions; articles are renumbered starting from 1 for each Gnus session
14079 (more precisely, each time you open the @code{nnmaildir} server). This
14080 way, you don't get gaps in your article number ranges, and when entering
14081 large groups, Gnus is likely to give a more accurate article count. The
14082 price is that @code{nnmaildir} doesn't work with the cache or agent.
14083 This will probably be changed in the future.
14085 @code{nnmaildir} stores article marks for a given group in the
14086 corresponding maildir, in a way designed so that it's easy to manipulate
14087 them from outside Gnus. You can tar up a maildir, unpack it somewhere
14088 else, and still have your marks. @code{nnml} also stores marks, but
14089 it's not as easy to work with them from outside Gnus as with
14092 For configuring expiry and other things, @code{nnmaildir} uses group
14093 parameters slightly different from those of other mail backends.
14095 @code{nnmaildir} uses a significant amount of memory to speed things up.
14096 (It keeps in memory some of the things that @code{nnml} stores in files
14097 and that @code{nnmh} repeatedly parses out of message files.) If this
14098 is a problem for you, you can set the @code{nov-cache-size} group
14099 parameter to somthing small (0 would probably not work, but 1 probably
14100 would) to make it use less memory.
14102 Startup and shutdown are likely to be slower with @code{nnmaildir} than
14103 with other backends. Everything in between is likely to be faster,
14104 depending in part on your filesystem.
14106 @code{nnmaildir} does not use @code{nnoo}, so you cannot use @code{nnoo}
14107 to write an @code{nnmaildir}-derived backend.
14112 @node Browsing the Web
14113 @section Browsing the Web
14115 @cindex browsing the web
14119 Web-based discussion forums are getting more and more popular. On many
14120 subjects, the web-based forums have become the most important forums,
14121 eclipsing the importance of mailing lists and news groups. The reason
14122 is easy to understand---they are friendly to new users; you just point
14123 and click, and there's the discussion. With mailing lists, you have to
14124 go through a cumbersome subscription procedure, and most people don't
14125 even know what a news group is.
14127 The problem with this scenario is that web browsers are not very good at
14128 being newsreaders. They do not keep track of what articles you've read;
14129 they do not allow you to score on subjects you're interested in; they do
14130 not allow off-line browsing; they require you to click around and drive
14131 you mad in the end.
14133 So---if web browsers suck at reading discussion forums, why not use Gnus
14136 Gnus has been getting a bit of a collection of back ends for providing
14137 interfaces to these sources.
14141 * Web Searches:: Creating groups from articles that match a string.
14142 * Slashdot:: Reading the Slashdot comments.
14143 * Ultimate:: The Ultimate Bulletin Board systems.
14144 * Web Archive:: Reading mailing list archived on web.
14145 * RSS:: Reading RDF site summary.
14146 * Customizing w3:: Doing stuff to Emacs/w3 from Gnus.
14149 All the web sources require Emacs/w3 and the url library to work.
14151 The main caveat with all these web sources is that they probably won't
14152 work for a very long time. Gleaning information from the @sc{html} data
14153 is guesswork at best, and when the layout is altered, the Gnus back end
14154 will fail. If you have reasonably new versions of these back ends,
14155 though, you should be ok.
14157 One thing all these Web methods have in common is that the Web sources
14158 are often down, unavailable or just plain too slow to be fun. In those
14159 cases, it makes a lot of sense to let the Gnus Agent (@pxref{Gnus
14160 Unplugged}) handle downloading articles, and then you can read them at
14161 leisure from your local disk. No more World Wide Wait for you.
14163 @node Archiving Mail
14164 @subsection Archiving Mail
14165 @cindex archiving mail
14166 @cindex backup of mail
14168 Some of the back ends, notably nnml and nnfolder, now actually store
14169 the article marks with each group. For these servers, archiving and
14170 restoring a group while preserving marks is fairly simple.
14172 (Preserving the group level and group parameters as well still
14173 requires ritual dancing and sacrifices to the @code{.newsrc.eld} deity
14176 To archive an entire @code{nnml} or @code{nnfolder} server, take a
14177 recursive copy of the server directory. There is no need to shut down
14178 Gnus, so archiving may be invoked by @code{cron} or similar. You
14179 restore the data by restoring the directory tree, and adding a server
14180 definition pointing to that directory in Gnus. The @ref{Article
14181 Backlog}, @ref{Asynchronous Fetching} and other things might interfer
14182 with overwriting data, so you may want to shut down Gnus before you
14185 It is also possible to archive individual @code{nnml} or
14186 @code{nnfolder} groups, while preserving marks. For @code{nnml}, you
14187 copy all files in the group's directory. For @code{nnfolder} you need
14188 to copy both the base folder file itself (@code{FOO}, say), and the
14189 marks file (@code{FOO.mrk} in this example). Restoring the group is
14190 done with @kbd{G m} from the Group buffer. The last step makes Gnus
14191 notice the new directory.
14194 @subsection Web Searches
14198 @cindex InReference
14199 @cindex Usenet searches
14200 @cindex searching the Usenet
14202 It's, like, too neat to search the Usenet for articles that match a
14203 string, but it, like, totally @emph{sucks}, like, totally, to use one of
14204 those, like, Web browsers, and you, like, have to, rilly, like, look at
14205 the commercials, so, like, with Gnus you can do @emph{rad}, rilly,
14206 searches without having to use a browser.
14208 The @code{nnweb} back end allows an easy interface to the mighty search
14209 engine. You create an @code{nnweb} group, enter a search pattern, and
14210 then enter the group and read the articles like you would any normal
14211 group. The @kbd{G w} command in the group buffer (@pxref{Foreign
14212 Groups}) will do this in an easy-to-use fashion.
14214 @code{nnweb} groups don't really lend themselves to being solid
14215 groups---they have a very fleeting idea of article numbers. In fact,
14216 each time you enter an @code{nnweb} group (not even changing the search
14217 pattern), you are likely to get the articles ordered in a different
14218 manner. Not even using duplicate suppression (@pxref{Duplicate
14219 Suppression}) will help, since @code{nnweb} doesn't even know the
14220 @code{Message-ID} of the articles before reading them using some search
14221 engines (DejaNews, for instance). The only possible way to keep track
14222 of which articles you've read is by scoring on the @code{Date}
14223 header---mark all articles posted before the last date you read the
14226 If the search engine changes its output substantially, @code{nnweb}
14227 won't be able to parse it and will fail. One could hardly fault the Web
14228 providers if they were to do this---their @emph{raison d'être} is to
14229 make money off of advertisements, not to provide services to the
14230 community. Since @code{nnweb} washes the ads off all the articles, one
14231 might think that the providers might be somewhat miffed. We'll see.
14233 You must have the @code{url} and @code{w3} package installed to be able
14234 to use @code{nnweb}.
14236 Virtual server variables:
14241 What search engine type is being used. The currently supported types
14242 are @code{dejanews}, @code{dejanewsold}, @code{altavista} and
14246 @vindex nnweb-search
14247 The search string to feed to the search engine.
14249 @item nnweb-max-hits
14250 @vindex nnweb-max-hits
14251 Advisory maximum number of hits per search to display. The default is
14254 @item nnweb-type-definition
14255 @vindex nnweb-type-definition
14256 Type-to-definition alist. This alist says what @code{nnweb} should do
14257 with the various search engine types. The following elements must be
14262 Function to decode the article and provide something that Gnus
14266 Function to create an article number to message header and URL alist.
14269 Function to send the search string to the search engine.
14272 The address the aforementioned function should send the search string
14276 Format string URL to fetch an article by @code{Message-ID}.
14283 @subsection Slashdot
14287 Slashdot (@uref{http://slashdot.org/}) is a popular news site, with
14288 lively discussion following the news articles. @code{nnslashdot} will
14289 let you read this forum in a convenient manner.
14291 The easiest way to read this source is to put something like the
14292 following in your @file{.gnus.el} file:
14295 (setq gnus-secondary-select-methods
14296 '((nnslashdot "")))
14299 This will make Gnus query the @code{nnslashdot} back end for new comments
14300 and groups. The @kbd{F} command will subscribe each new news article as
14301 a new Gnus group, and you can read the comments by entering these
14302 groups. (Note that the default subscription method is to subscribe new
14303 groups as zombies. Other methods are available (@pxref{Subscription
14306 If you want to remove an old @code{nnslashdot} group, the @kbd{G DEL}
14307 command is the most handy tool (@pxref{Foreign Groups}).
14309 When following up to @code{nnslashdot} comments (or posting new
14310 comments), some light @sc{html}izations will be performed. In
14311 particular, text quoted with @samp{> } will be quoted with
14312 @code{blockquote} instead, and signatures will have @code{br} added to
14313 the end of each line. Other than that, you can just write @sc{html}
14314 directly into the message buffer. Note that Slashdot filters out some
14317 The following variables can be altered to change its behavior:
14320 @item nnslashdot-threaded
14321 Whether @code{nnslashdot} should display threaded groups or not. The
14322 default is @code{t}. To be able to display threads, @code{nnslashdot}
14323 has to retrieve absolutely all comments in a group upon entry. If a
14324 threaded display is not required, @code{nnslashdot} will only retrieve
14325 the comments that are actually wanted by the user. Threading is nicer,
14326 but much, much slower than untreaded.
14328 @item nnslashdot-login-name
14329 @vindex nnslashdot-login-name
14330 The login name to use when posting.
14332 @item nnslashdot-password
14333 @vindex nnslashdot-password
14334 The password to use when posting.
14336 @item nnslashdot-directory
14337 @vindex nnslashdot-directory
14338 Where @code{nnslashdot} will store its files. The default is
14339 @samp{~/News/slashdot/}.
14341 @item nnslashdot-active-url
14342 @vindex nnslashdot-active-url
14343 The @sc{url} format string that will be used to fetch the information on
14344 news articles and comments. The default is
14345 @samp{http://slashdot.org/search.pl?section=&min=%d}.
14347 @item nnslashdot-comments-url
14348 @vindex nnslashdot-comments-url
14349 The @sc{url} format string that will be used to fetch comments. The
14351 @samp{http://slashdot.org/comments.pl?sid=%s&threshold=%d&commentsort=%d&mode=flat&startat=%d}.
14353 @item nnslashdot-article-url
14354 @vindex nnslashdot-article-url
14355 The @sc{url} format string that will be used to fetch the news article. The
14357 @samp{http://slashdot.org/article.pl?sid=%s&mode=nocomment}.
14359 @item nnslashdot-threshold
14360 @vindex nnslashdot-threshold
14361 The score threshold. The default is -1.
14363 @item nnslashdot-group-number
14364 @vindex nnslashdot-group-number
14365 The number of old groups, in addition to the ten latest, to keep
14366 updated. The default is 0.
14373 @subsection Ultimate
14375 @cindex Ultimate Bulletin Board
14377 The Ultimate Bulletin Board (@uref{http://www.ultimatebb.com/}) is
14378 probably the most popular Web bulletin board system used. It has a
14379 quite regular and nice interface, and it's possible to get the
14380 information Gnus needs to keep groups updated.
14382 The easiest way to get started with @code{nnultimate} is to say
14383 something like the following in the group buffer: @kbd{B nnultimate RET
14384 http://www.tcj.com/messboard/ubbcgi/ RET}. (Substitute the @sc{url}
14385 (not including @samp{Ultimate.cgi} or the like at the end) for a forum
14386 you're interested in; there's quite a list of them on the Ultimate web
14387 site.) Then subscribe to the groups you're interested in from the
14388 server buffer, and read them from the group buffer.
14390 The following @code{nnultimate} variables can be altered:
14393 @item nnultimate-directory
14394 @vindex nnultimate-directory
14395 The directory where @code{nnultimate} stores its files. The default is
14396 @samp{~/News/ultimate/}.
14401 @subsection Web Archive
14403 @cindex Web Archive
14405 Some mailing lists only have archives on Web servers, such as
14406 @uref{http://www.egroups.com/} and
14407 @uref{http://www.mail-archive.com/}. It has a quite regular and nice
14408 interface, and it's possible to get the information Gnus needs to keep
14411 The easiest way to get started with @code{nnwarchive} is to say
14412 something like the following in the group buffer: @kbd{M-x
14413 gnus-group-make-warchive-group RET an_egroup RET egroups RET
14414 www.egroups.com RET your@@email.address RET}. (Substitute the
14415 @sc{an_egroup} with the mailing list you subscribed, the
14416 @sc{your@@email.address} with your email address.), or to browse the
14417 back end by @kbd{B nnwarchive RET mail-archive RET}.
14419 The following @code{nnwarchive} variables can be altered:
14422 @item nnwarchive-directory
14423 @vindex nnwarchive-directory
14424 The directory where @code{nnwarchive} stores its files. The default is
14425 @samp{~/News/warchive/}.
14427 @item nnwarchive-login
14428 @vindex nnwarchive-login
14429 The account name on the web server.
14431 @item nnwarchive-passwd
14432 @vindex nnwarchive-passwd
14433 The password for your account on the web server.
14441 Some sites have RDF site summary (RSS)
14442 @uref{http://purl.org/rss/1.0/spec}. It has a quite regular and nice
14443 interface, and it's possible to get the information Gnus needs to keep
14446 The easiest way to get started with @code{nnrss} is to say something
14447 like the following in the group buffer: @kbd{B nnrss RET RET}, then
14450 The following @code{nnrss} variables can be altered:
14453 @item nnrss-directory
14454 @vindex nnrss-directory
14455 The directory where @code{nnrss} stores its files. The default is
14456 @samp{~/News/rss/}.
14460 The following code may be helpful, if you want to show the description in
14461 the summary buffer.
14464 (add-to-list 'nnmail-extra-headers nnrss-description-field)
14465 (setq gnus-summary-line-format "%U%R%z%I%(%[%4L: %-15,15f%]%) %s%uX\n")
14467 (defun gnus-user-format-function-X (header)
14469 (assq nnrss-description-field (mail-header-extra header))))
14470 (if descr (concat "\n\t" (cdr descr)) "")))
14473 The following code may be useful to open an nnrss url directly from the
14476 (require 'browse-url)
14478 (defun browse-nnrss-url( arg )
14480 (let ((url (assq nnrss-url-field
14483 (assq (gnus-summary-article-number)
14484 gnus-newsgroup-data))))))
14486 (browse-url (cdr url))
14487 (gnus-summary-scroll-up arg))))
14489 (eval-after-load "gnus"
14490 #'(define-key gnus-summary-mode-map
14491 (kbd "<RET>") 'browse-nnrss-url))
14492 (add-to-list 'nnmail-extra-headers nnrss-url-field)
14495 @node Customizing w3
14496 @subsection Customizing w3
14502 Gnus uses the url library to fetch web pages and Emacs/w3 to display web
14503 pages. Emacs/w3 is documented in its own manual, but there are some
14504 things that may be more relevant for Gnus users.
14506 For instance, a common question is how to make Emacs/w3 follow links
14507 using the @code{browse-url} functions (which will call some external web
14508 browser like Netscape). Here's one way:
14511 (eval-after-load "w3"
14513 (fset 'w3-fetch-orig (symbol-function 'w3-fetch))
14514 (defun w3-fetch (&optional url target)
14515 (interactive (list (w3-read-url-with-default)))
14516 (if (eq major-mode 'gnus-article-mode)
14518 (w3-fetch-orig url target)))))
14521 Put that in your @file{.emacs} file, and hitting links in w3-rendered
14522 @sc{html} in the Gnus article buffers will use @code{browse-url} to
14531 @sc{imap} is a network protocol for reading mail (or news, or ...),
14532 think of it as a modernized @sc{nntp}. Connecting to a @sc{imap}
14533 server is much similar to connecting to a news server, you just
14534 specify the network address of the server.
14536 @sc{imap} has two properties. First, @sc{imap} can do everything that
14537 POP can, it can hence be viewed as a POP++. Secondly, @sc{imap} is a
14538 mail storage protocol, similar to @sc{nntp} being a news storage
14539 protocol -- however, @sc{imap} offers more features than @sc{nntp}
14540 because news is more or less read-only whereas mail is read-write.
14542 If you want to use @sc{imap} as a POP++, use an imap entry in
14543 @code{mail-sources}. With this, Gnus will fetch mails from the
14544 @sc{imap} server and store them on the local disk. This is not the
14545 usage described in this section--@xref{Mail Sources}.
14547 If you want to use @sc{imap} as a mail storage protocol, use an nnimap
14548 entry in @code{gnus-secondary-select-methods}. With this, Gnus will
14549 manipulate mails stored on the @sc{imap} server. This is the kind of
14550 usage explained in this section.
14552 A server configuration in @code{~/.gnus} with a few @sc{imap} servers
14553 might look something like the following. (Note that for SSL/TLS, you
14554 need external programs and libraries, see below.)
14557 (setq gnus-secondary-select-methods
14558 '((nnimap "simpleserver") ; no special configuration
14559 ; perhaps a ssh port forwarded server:
14561 (nnimap-address "localhost")
14562 (nnimap-server-port 1430))
14563 ; a UW server running on localhost
14565 (nnimap-server-port 143)
14566 (nnimap-address "localhost")
14567 (nnimap-list-pattern ("INBOX" "mail/*")))
14568 ; anonymous public cyrus server:
14569 (nnimap "cyrus.andrew.cmu.edu"
14570 (nnimap-authenticator anonymous)
14571 (nnimap-list-pattern "archive.*")
14572 (nnimap-stream network))
14573 ; a ssl server on a non-standard port:
14575 (nnimap-address "vic20.somewhere.com")
14576 (nnimap-server-port 9930)
14577 (nnimap-stream ssl))))
14580 The following variables can be used to create a virtual @code{nnimap}
14585 @item nnimap-address
14586 @vindex nnimap-address
14588 The address of the remote @sc{imap} server. Defaults to the virtual
14589 server name if not specified.
14591 @item nnimap-server-port
14592 @vindex nnimap-server-port
14593 Port on server to contact. Defaults to port 143, or 993 for SSL.
14595 Note that this should be an integer, example server specification:
14598 (nnimap "mail.server.com"
14599 (nnimap-server-port 4711))
14602 @item nnimap-list-pattern
14603 @vindex nnimap-list-pattern
14604 String or list of strings of mailboxes to limit available groups to.
14605 This is used when the server has very many mailboxes and you're only
14606 interested in a few -- some servers export your home directory via
14607 @sc{imap}, you'll probably want to limit the mailboxes to those in
14608 @file{~/Mail/*} then.
14610 The string can also be a cons of REFERENCE and the string as above, what
14611 REFERENCE is used for is server specific, but on the University of
14612 Washington server it's a directory that will be concatenated with the
14615 Example server specification:
14618 (nnimap "mail.server.com"
14619 (nnimap-list-pattern ("INBOX" "Mail/*" "alt.sex.*"
14620 ("~friend/Mail/" . "list/*"))))
14623 @item nnimap-stream
14624 @vindex nnimap-stream
14625 The type of stream used to connect to your server. By default, nnimap
14626 will detect and automatically use all of the below, with the exception
14627 of SSL/TLS. (IMAP over SSL/TLS is being replaced by STARTTLS, which
14628 can be automatically detected, but it's not widely deployed yet.)
14630 Example server specification:
14633 (nnimap "mail.server.com"
14634 (nnimap-stream ssl))
14637 Please note that the value of @code{nnimap-stream} is a symbol!
14641 @dfn{gssapi:} Connect with GSSAPI (usually Kerberos 5). Requires the
14642 @samp{imtest} program.
14644 @dfn{kerberos4:} Connect with Kerberos 4. Requires the @samp{imtest} program.
14646 @dfn{starttls:} Connect via the STARTTLS extension (similar to
14647 SSL). Requires the external library @samp{starttls.el} and program
14650 @dfn{ssl:} Connect through SSL. Requires OpenSSL (the program
14651 @samp{openssl}) or SSLeay (@samp{s_client}) as well as the external
14652 library @samp{ssl.el}.
14654 @dfn{shell:} Use a shell command to start @sc{imap} connection.
14656 @dfn{network:} Plain, TCP/IP network connection.
14659 @vindex imap-kerberos4-program
14660 The @samp{imtest} program is shipped with Cyrus IMAPD. If you're
14661 using @samp{imtest} from Cyrus IMAPD < 2.0.14 (which includes version
14662 1.5.x and 1.6.x) you need to frob @code{imap-process-connection-type}
14663 to make @code{imap.el} use a pty instead of a pipe when communicating
14664 with @samp{imtest}. You will then suffer from a line length
14665 restrictions on IMAP commands, which might make Gnus seem to hang
14666 indefinitely if you have many articles in a mailbox. The variable
14667 @code{imap-kerberos4-program} contain parameters to pass to the imtest
14670 @vindex imap-ssl-program
14671 For SSL connections, the OpenSSL program is available from
14672 @uref{http://www.openssl.org/}. OpenSSL was formerly known as SSLeay,
14673 and nnimap support it too - altough the most recent versions of
14674 SSLeay, 0.9.x, are known to have serious bugs making it
14675 useless. Earlier versions, especially 0.8.x, of SSLeay are known to
14676 work. The variable @code{imap-ssl-program} contain parameters to pass
14677 to OpenSSL/SSLeay. You also need @samp{ssl.el} (from the W3
14678 distribution, for instance).
14680 @vindex imap-shell-program
14681 @vindex imap-shell-host
14682 For @sc{imap} connections using the @code{shell} stream, the variable
14683 @code{imap-shell-program} specify what program to call.
14685 @item nnimap-authenticator
14686 @vindex nnimap-authenticator
14688 The authenticator used to connect to the server. By default, nnimap
14689 will use the most secure authenticator your server is capable of.
14691 Example server specification:
14694 (nnimap "mail.server.com"
14695 (nnimap-authenticator anonymous))
14698 Please note that the value of @code{nnimap-authenticator} is a symbol!
14702 @dfn{gssapi:} GSSAPI (usually kerberos 5) authentication. Requires
14703 external program @code{imtest}.
14705 @dfn{kerberos4:} Kerberos 4 authentication. Requires external program
14708 @dfn{digest-md5:} Encrypted username/password via DIGEST-MD5. Requires
14709 external library @code{digest-md5.el}.
14711 @dfn{cram-md5:} Encrypted username/password via CRAM-MD5.
14713 @dfn{login:} Plain-text username/password via LOGIN.
14715 @dfn{anonymous:} Login as `anonymous', supplying your emailadress as password.
14718 @item nnimap-expunge-on-close
14720 @vindex nnimap-expunge-on-close
14721 Unlike Parmenides the @sc{imap} designers has decided that things that
14722 doesn't exist actually does exist. More specifically, @sc{imap} has
14723 this concept of marking articles @code{Deleted} which doesn't actually
14724 delete them, and this (marking them @code{Deleted}, that is) is what
14725 nnimap does when you delete a article in Gnus (with @kbd{G DEL} or
14728 Since the articles aren't really removed when we mark them with the
14729 @code{Deleted} flag we'll need a way to actually delete them. Feel like
14730 running in circles yet?
14732 Traditionally, nnimap has removed all articles marked as @code{Deleted}
14733 when closing a mailbox but this is now configurable by this server
14736 The possible options are:
14741 The default behavior, delete all articles marked as "Deleted" when
14744 Never actually delete articles. Currently there is no way of showing
14745 the articles marked for deletion in nnimap, but other @sc{imap} clients
14746 may allow you to do this. If you ever want to run the EXPUNGE command
14747 manually, @xref{Expunging mailboxes}.
14749 When closing mailboxes, nnimap will ask if you wish to expunge deleted
14754 @item nnimap-importantize-dormant
14755 @vindex nnimap-importantize-dormant
14757 If non-nil, marks dormant articles as ticked (as well), for other IMAP
14758 clients. Within Gnus, dormant articles will naturally still (only) be
14759 marked as ticked. This is to make dormant articles stand out, just
14760 like ticked articles, in other IMAP clients. (In other words, Gnus has
14761 two ``Tick'' marks and IMAP has only one.)
14763 Probably the only reason for frobing this would be if you're trying
14764 enable per-user persistant dormant flags, using something like:
14767 (setcdr (assq 'dormant nnimap-mark-to-flag-alist)
14768 (format "gnus-dormant-%s" (user-login-name)))
14769 (setcdr (assq 'dormant nnimap-mark-to-predicate-alist)
14770 (format "KEYWORD gnus-dormant-%s" (user-login-name)))
14773 In this case, you would not want the per-user dormant flag showing up
14774 as ticked for other users.
14776 @item nnimap-expunge-search-string
14778 @vindex nnimap-expunge-search-string
14780 This variable contain the IMAP search command sent to server when
14781 searching for articles eligible for expiring. The default is
14782 @code{"UID %s NOT SINCE %s"}, where the first @code{%s} is replaced by
14783 UID set and the second @code{%s} is replaced by a date.
14785 Probably the only useful value to change this to is
14786 @code{"UID %s NOT SENTSINCE %s"}, which makes nnimap use the Date: in
14787 messages instead of the internal article date. See section 6.4.4 of
14788 RFC 2060 for more information on valid strings.
14790 @item nnimap-authinfo-file
14791 @vindex nnimap-authinfo-file
14793 A file containing credentials used to log in on servers. The format is
14794 (almost) the same as the @code{ftp} @file{~/.netrc} file. See the
14795 variable @code{nntp-authinfo-file} for exact syntax; also see
14801 * Splitting in IMAP:: Splitting mail with nnimap.
14802 * Editing IMAP ACLs:: Limiting/enabling other users access to a mailbox.
14803 * Expunging mailboxes:: Equivalent of a "compress mailbox" button.
14808 @node Splitting in IMAP
14809 @subsection Splitting in @sc{imap}
14810 @cindex splitting imap mail
14812 Splitting is something Gnus users has loved and used for years, and now
14813 the rest of the world is catching up. Yeah, dream on, not many
14814 @sc{imap} server has server side splitting and those that have splitting
14815 seem to use some non-standard protocol. This means that @sc{imap}
14816 support for Gnus has to do it's own splitting.
14820 Here are the variables of interest:
14824 @item nnimap-split-crosspost
14825 @cindex splitting, crosspost
14827 @vindex nnimap-split-crosspost
14829 If non-nil, do crossposting if several split methods match the mail. If
14830 nil, the first match in @code{nnimap-split-rule} found will be used.
14832 Nnmail equivalent: @code{nnmail-crosspost}.
14834 @item nnimap-split-inbox
14835 @cindex splitting, inbox
14837 @vindex nnimap-split-inbox
14839 A string or a list of strings that gives the name(s) of @sc{imap}
14840 mailboxes to split from. Defaults to nil, which means that splitting is
14844 (setq nnimap-split-inbox
14845 '("INBOX" ("~/friend/Mail" . "lists/*") "lists.imap"))
14848 No nnmail equivalent.
14850 @item nnimap-split-rule
14851 @cindex Splitting, rules
14852 @vindex nnimap-split-rule
14854 New mail found in @code{nnimap-split-inbox} will be split according to
14857 This variable contains a list of lists, where the first element in the
14858 sublist gives the name of the @sc{imap} mailbox to move articles
14859 matching the regexp in the second element in the sublist. Got that?
14860 Neither did I, we need examples.
14863 (setq nnimap-split-rule
14865 "^Sender: owner-nnimap@@vic20.globalcom.se")
14866 ("INBOX.junk" "^Subject:.*MAKE MONEY")
14867 ("INBOX.private" "")))
14870 This will put all articles from the nnimap mailing list into mailbox
14871 INBOX.nnimap, all articles containing MAKE MONEY in the Subject: line
14872 into INBOX.junk and everything else in INBOX.private.
14874 The first string may contain `\\1' forms, like the ones used by
14875 replace-match to insert sub-expressions from the matched text. For
14879 ("INBOX.lists.\\1" "^Sender: owner-\\([a-z-]+\\)@@")
14882 The second element can also be a function. In that case, it will be
14883 called with the first element of the rule as the argument, in a buffer
14884 containing the headers of the article. It should return a non-nil value
14885 if it thinks that the mail belongs in that group.
14887 Nnmail users might recollect that the last regexp had to be empty to
14888 match all articles (like in the example above). This is not required in
14889 nnimap. Articles not matching any of the regexps will not be moved out
14890 of your inbox. (This might affect performance if you keep lots of
14891 unread articles in your inbox, since the splitting code would go over
14892 them every time you fetch new mail.)
14894 These rules are processed from the beginning of the alist toward the
14895 end. The first rule to make a match will "win", unless you have
14896 crossposting enabled. In that case, all matching rules will "win".
14898 This variable can also have a function as its value, the function will
14899 be called with the headers narrowed and should return a group where it
14900 thinks the article should be split to. See @code{nnimap-split-fancy}.
14902 The splitting code tries to create mailboxes if it needs to.
14904 To allow for different split rules on different virtual servers, and
14905 even different split rules in different inboxes on the same server,
14906 the syntax of this variable have been extended along the lines of:
14909 (setq nnimap-split-rule
14910 '(("my1server" (".*" (("ding" "ding@@gnus.org")
14911 ("junk" "From:.*Simon")))
14912 ("my2server" ("INBOX" nnimap-split-fancy))
14913 ("my[34]server" (".*" (("private" "To:.*Simon")
14914 ("junk" my-junk-func)))))
14917 The virtual server name is in fact a regexp, so that the same rules
14918 may apply to several servers. In the example, the servers
14919 @code{my3server} and @code{my4server} both use the same rules.
14920 Similarly, the inbox string is also a regexp. The actual splitting
14921 rules are as before, either a function, or a list with group/regexp or
14922 group/function elements.
14924 Nnmail equivalent: @code{nnmail-split-methods}.
14926 @item nnimap-split-predicate
14928 @vindex nnimap-split-predicate
14930 Mail matching this predicate in @code{nnimap-split-inbox} will be
14931 split, it is a string and the default is @samp{UNSEEN UNDELETED}.
14933 This might be useful if you use another @sc{imap} client to read mail in
14934 your inbox but would like Gnus to split all articles in the inbox
14935 regardless of readedness. Then you might change this to
14938 @item nnimap-split-fancy
14939 @cindex splitting, fancy
14940 @findex nnimap-split-fancy
14941 @vindex nnimap-split-fancy
14943 It's possible to set @code{nnimap-split-rule} to
14944 @code{nnmail-split-fancy} if you want to use fancy
14945 splitting. @xref{Fancy Mail Splitting}.
14947 However, to be able to have different fancy split rules for nnmail and
14948 nnimap back ends you can set @code{nnimap-split-rule} to
14949 @code{nnimap-split-fancy} and define the nnimap specific fancy split
14950 rule in @code{nnimap-split-fancy}.
14955 (setq nnimap-split-rule 'nnimap-split-fancy
14956 nnimap-split-fancy ...)
14959 Nnmail equivalent: @code{nnmail-split-fancy}.
14963 @node Editing IMAP ACLs
14964 @subsection Editing @sc{imap} ACLs
14965 @cindex editing imap acls
14966 @cindex Access Control Lists
14967 @cindex Editing @sc{imap} ACLs
14969 @findex gnus-group-nnimap-edit-acl
14971 ACL stands for Access Control List. ACLs are used in @sc{imap} for
14972 limiting (or enabling) other users access to your mail boxes. Not all
14973 @sc{imap} servers support this, this function will give an error if it
14976 To edit a ACL for a mailbox, type @kbd{G l}
14977 (@code{gnus-group-edit-nnimap-acl}) and you'll be presented with a ACL
14978 editing window with detailed instructions.
14980 Some possible uses:
14984 Giving "anyone" the "lrs" rights (lookup, read, keep seen/unseen flags)
14985 on your mailing list mailboxes enables other users on the same server to
14986 follow the list without subscribing to it.
14988 At least with the Cyrus server, you are required to give the user
14989 "anyone" posting ("p") capabilities to have "plussing" work (that is,
14990 mail sent to user+mailbox@@domain ending up in the @sc{imap} mailbox
14994 @node Expunging mailboxes
14995 @subsection Expunging mailboxes
14999 @cindex Manual expunging
15001 @findex gnus-group-nnimap-expunge
15003 If you're using the @code{never} setting of @code{nnimap-expunge-on-close},
15004 you may want the option of expunging all deleted articles in a mailbox
15005 manually. This is exactly what @kbd{G x} does.
15007 Currently there is no way of showing deleted articles, you can just
15012 @node Other Sources
15013 @section Other Sources
15015 Gnus can do more than just read news or mail. The methods described
15016 below allow Gnus to view directories and files as if they were
15020 * Directory Groups:: You can read a directory as if it was a newsgroup.
15021 * Anything Groups:: Dired? Who needs dired?
15022 * Document Groups:: Single files can be the basis of a group.
15023 * SOUP:: Reading @sc{soup} packets ``offline''.
15024 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
15028 @node Directory Groups
15029 @subsection Directory Groups
15031 @cindex directory groups
15033 If you have a directory that has lots of articles in separate files in
15034 it, you might treat it as a newsgroup. The files have to have numerical
15037 This might be an opportune moment to mention @code{ange-ftp} (and its
15038 successor @code{efs}), that most wonderful of all wonderful Emacs
15039 packages. When I wrote @code{nndir}, I didn't think much about it---a
15040 back end to read directories. Big deal.
15042 @code{ange-ftp} changes that picture dramatically. For instance, if you
15043 enter the @code{ange-ftp} file name
15044 @file{/ftp.hpc.uh.edu:/pub/emacs/ding-list/} as the directory name,
15045 @code{ange-ftp} or @code{efs} will actually allow you to read this
15046 directory over at @samp{sina} as a newsgroup. Distributed news ahoy!
15048 @code{nndir} will use @sc{nov} files if they are present.
15050 @code{nndir} is a ``read-only'' back end---you can't delete or expire
15051 articles with this method. You can use @code{nnmh} or @code{nnml} for
15052 whatever you use @code{nndir} for, so you could switch to any of those
15053 methods if you feel the need to have a non-read-only @code{nndir}.
15056 @node Anything Groups
15057 @subsection Anything Groups
15060 From the @code{nndir} back end (which reads a single spool-like
15061 directory), it's just a hop and a skip to @code{nneething}, which
15062 pretends that any arbitrary directory is a newsgroup. Strange, but
15065 When @code{nneething} is presented with a directory, it will scan this
15066 directory and assign article numbers to each file. When you enter such
15067 a group, @code{nneething} must create ``headers'' that Gnus can use.
15068 After all, Gnus is a newsreader, in case you're forgetting.
15069 @code{nneething} does this in a two-step process. First, it snoops each
15070 file in question. If the file looks like an article (i.e., the first
15071 few lines look like headers), it will use this as the head. If this is
15072 just some arbitrary file without a head (e.g. a C source file),
15073 @code{nneething} will cobble up a header out of thin air. It will use
15074 file ownership, name and date and do whatever it can with these
15077 All this should happen automatically for you, and you will be presented
15078 with something that looks very much like a newsgroup. Totally like a
15079 newsgroup, to be precise. If you select an article, it will be displayed
15080 in the article buffer, just as usual.
15082 If you select a line that represents a directory, Gnus will pop you into
15083 a new summary buffer for this @code{nneething} group. And so on. You can
15084 traverse the entire disk this way, if you feel like, but remember that
15085 Gnus is not dired, really, and does not intend to be, either.
15087 There are two overall modes to this action---ephemeral or solid. When
15088 doing the ephemeral thing (i.e., @kbd{G D} from the group buffer), Gnus
15089 will not store information on what files you have read, and what files
15090 are new, and so on. If you create a solid @code{nneething} group the
15091 normal way with @kbd{G m}, Gnus will store a mapping table between
15092 article numbers and file names, and you can treat this group like any
15093 other groups. When you activate a solid @code{nneething} group, you will
15094 be told how many unread articles it contains, etc., etc.
15099 @item nneething-map-file-directory
15100 @vindex nneething-map-file-directory
15101 All the mapping files for solid @code{nneething} groups will be stored
15102 in this directory, which defaults to @file{~/.nneething/}.
15104 @item nneething-exclude-files
15105 @vindex nneething-exclude-files
15106 All files that match this regexp will be ignored. Nice to use to exclude
15107 auto-save files and the like, which is what it does by default.
15109 @item nneething-include-files
15110 @vindex nneething-include-files
15111 Regexp saying what files to include in the group. If this variable is
15112 non-@code{nil}, only files matching this regexp will be included.
15114 @item nneething-map-file
15115 @vindex nneething-map-file
15116 Name of the map files.
15120 @node Document Groups
15121 @subsection Document Groups
15123 @cindex documentation group
15126 @code{nndoc} is a cute little thing that will let you read a single file
15127 as a newsgroup. Several files types are supported:
15134 The babyl (rmail) mail box.
15139 The standard Unix mbox file.
15141 @cindex MMDF mail box
15143 The MMDF mail box format.
15146 Several news articles appended into a file.
15149 @cindex rnews batch files
15150 The rnews batch transport format.
15151 @cindex forwarded messages
15154 Forwarded articles.
15157 Netscape mail boxes.
15160 MIME multipart messages.
15162 @item standard-digest
15163 The standard (RFC 1153) digest format.
15166 A MIME digest of messages.
15168 @item lanl-gov-announce
15169 Announcement messages from LANL Gov Announce.
15171 @item rfc822-forward
15172 A message forwarded according to RFC822.
15175 The Outlook mail box.
15178 The Outlook Express dbx mail box.
15181 A bounce message from the Exim MTA.
15184 A message forwarded according to informal rules.
15187 An RFC934-forwarded message.
15193 A digest of Clarinet brief news items.
15196 Non-standard digest format---matches most things, but does it badly.
15199 You can also use the special ``file type'' @code{guess}, which means
15200 that @code{nndoc} will try to guess what file type it is looking at.
15201 @code{digest} means that @code{nndoc} should guess what digest type the
15204 @code{nndoc} will not try to change the file or insert any extra headers into
15205 it---it will simply, like, let you use the file as the basis for a
15206 group. And that's it.
15208 If you have some old archived articles that you want to insert into your
15209 new & spiffy Gnus mail back end, @code{nndoc} can probably help you with
15210 that. Say you have an old @file{RMAIL} file with mail that you now want
15211 to split into your new @code{nnml} groups. You look at that file using
15212 @code{nndoc} (using the @kbd{G f} command in the group buffer
15213 (@pxref{Foreign Groups})), set the process mark on all the articles in
15214 the buffer (@kbd{M P b}, for instance), and then re-spool (@kbd{B r})
15215 using @code{nnml}. If all goes well, all the mail in the @file{RMAIL}
15216 file is now also stored in lots of @code{nnml} directories, and you can
15217 delete that pesky @file{RMAIL} file. If you have the guts!
15219 Virtual server variables:
15222 @item nndoc-article-type
15223 @vindex nndoc-article-type
15224 This should be one of @code{mbox}, @code{babyl}, @code{digest},
15225 @code{news}, @code{rnews}, @code{mmdf}, @code{forward}, @code{rfc934},
15226 @code{rfc822-forward}, @code{mime-parts}, @code{standard-digest},
15227 @code{slack-digest}, @code{clari-briefs}, @code{nsmail},
15228 @code{outlook}, @code{oe-dbx}, and @code{mailman} or @code{guess}.
15230 @item nndoc-post-type
15231 @vindex nndoc-post-type
15232 This variable says whether Gnus is to consider the group a news group or
15233 a mail group. There are two valid values: @code{mail} (the default)
15238 * Document Server Internals:: How to add your own document types.
15242 @node Document Server Internals
15243 @subsubsection Document Server Internals
15245 Adding new document types to be recognized by @code{nndoc} isn't
15246 difficult. You just have to whip up a definition of what the document
15247 looks like, write a predicate function to recognize that document type,
15248 and then hook into @code{nndoc}.
15250 First, here's an example document type definition:
15254 (article-begin . "^\^A\^A\^A\^A\n")
15255 (body-end . "^\^A\^A\^A\^A\n"))
15258 The definition is simply a unique @dfn{name} followed by a series of
15259 regexp pseudo-variable settings. Below are the possible
15260 variables---don't be daunted by the number of variables; most document
15261 types can be defined with very few settings:
15264 @item first-article
15265 If present, @code{nndoc} will skip past all text until it finds
15266 something that match this regexp. All text before this will be
15269 @item article-begin
15270 This setting has to be present in all document type definitions. It
15271 says what the beginning of each article looks like.
15273 @item head-begin-function
15274 If present, this should be a function that moves point to the head of
15277 @item nndoc-head-begin
15278 If present, this should be a regexp that matches the head of the
15281 @item nndoc-head-end
15282 This should match the end of the head of the article. It defaults to
15283 @samp{^$}---the empty line.
15285 @item body-begin-function
15286 If present, this function should move point to the beginning of the body
15290 This should match the beginning of the body of the article. It defaults
15293 @item body-end-function
15294 If present, this function should move point to the end of the body of
15298 If present, this should match the end of the body of the article.
15301 If present, this should match the end of the file. All text after this
15302 regexp will be totally ignored.
15306 So, using these variables @code{nndoc} is able to dissect a document
15307 file into a series of articles, each with a head and a body. However, a
15308 few more variables are needed since not all document types are all that
15309 news-like---variables needed to transform the head or the body into
15310 something that's palatable for Gnus:
15313 @item prepare-body-function
15314 If present, this function will be called when requesting an article. It
15315 will be called with point at the start of the body, and is useful if the
15316 document has encoded some parts of its contents.
15318 @item article-transform-function
15319 If present, this function is called when requesting an article. It's
15320 meant to be used for more wide-ranging transformation of both head and
15321 body of the article.
15323 @item generate-head-function
15324 If present, this function is called to generate a head that Gnus can
15325 understand. It is called with the article number as a parameter, and is
15326 expected to generate a nice head for the article in question. It is
15327 called when requesting the headers of all articles.
15331 Let's look at the most complicated example I can come up with---standard
15336 (first-article . ,(concat "^" (make-string 70 ?-) "\n\n+"))
15337 (article-begin . ,(concat "\n\n" (make-string 30 ?-) "\n\n+"))
15338 (prepare-body-function . nndoc-unquote-dashes)
15339 (body-end-function . nndoc-digest-body-end)
15340 (head-end . "^ ?$")
15341 (body-begin . "^ ?\n")
15342 (file-end . "^End of .*digest.*[0-9].*\n\\*\\*\\|^End of.*Digest *$")
15343 (subtype digest guess))
15346 We see that all text before a 70-width line of dashes is ignored; all
15347 text after a line that starts with that @samp{^End of} is also ignored;
15348 each article begins with a 30-width line of dashes; the line separating
15349 the head from the body may contain a single space; and that the body is
15350 run through @code{nndoc-unquote-dashes} before being delivered.
15352 To hook your own document definition into @code{nndoc}, use the
15353 @code{nndoc-add-type} function. It takes two parameters---the first is
15354 the definition itself and the second (optional) parameter says where in
15355 the document type definition alist to put this definition. The alist is
15356 traversed sequentially, and @code{nndoc-TYPE-type-p} is called for a given type @code{TYPE}. So @code{nndoc-mmdf-type-p} is called to see whether a document
15357 is of @code{mmdf} type, and so on. These type predicates should return
15358 @code{nil} if the document is not of the correct type; @code{t} if it is
15359 of the correct type; and a number if the document might be of the
15360 correct type. A high number means high probability; a low number means
15361 low probability with @samp{0} being the lowest valid number.
15369 In the PC world people often talk about ``offline'' newsreaders. These
15370 are thingies that are combined reader/news transport monstrosities.
15371 With built-in modem programs. Yecchh!
15373 Of course, us Unix Weenie types of human beans use things like
15374 @code{uucp} and, like, @code{nntpd} and set up proper news and mail
15375 transport things like Ghod intended. And then we just use normal
15378 However, it can sometimes be convenient to do something that's a bit
15379 easier on the brain if you have a very slow modem, and you're not really
15380 that interested in doing things properly.
15382 A file format called @sc{soup} has been developed for transporting news
15383 and mail from servers to home machines and back again. It can be a bit
15386 First some terminology:
15391 This is the machine that is connected to the outside world and where you
15392 get news and/or mail from.
15395 This is the machine that you want to do the actual reading and responding
15396 on. It is typically not connected to the rest of the world in any way.
15399 Something that contains messages and/or commands. There are two kinds
15403 @item message packets
15404 These are packets made at the server, and typically contain lots of
15405 messages for you to read. These are called @file{SoupoutX.tgz} by
15406 default, where @var{x} is a number.
15408 @item response packets
15409 These are packets made at the home machine, and typically contains
15410 replies that you've written. These are called @file{SoupinX.tgz} by
15411 default, where @var{x} is a number.
15421 You log in on the server and create a @sc{soup} packet. You can either
15422 use a dedicated @sc{soup} thingie (like the @code{awk} program), or you
15423 can use Gnus to create the packet with its @sc{soup} commands (@kbd{O
15424 s} and/or @kbd{G s b}; and then @kbd{G s p}) (@pxref{SOUP Commands}).
15427 You transfer the packet home. Rail, boat, car or modem will do fine.
15430 You put the packet in your home directory.
15433 You fire up Gnus on your home machine using the @code{nnsoup} back end as
15434 the native or secondary server.
15437 You read articles and mail and answer and followup to the things you
15438 want (@pxref{SOUP Replies}).
15441 You do the @kbd{G s r} command to pack these replies into a @sc{soup}
15445 You transfer this packet to the server.
15448 You use Gnus to mail this packet out with the @kbd{G s s} command.
15451 You then repeat until you die.
15455 So you basically have a bipartite system---you use @code{nnsoup} for
15456 reading and Gnus for packing/sending these @sc{soup} packets.
15459 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
15460 * SOUP Groups:: A back end for reading @sc{soup} packets.
15461 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
15465 @node SOUP Commands
15466 @subsubsection SOUP Commands
15468 These are commands for creating and manipulating @sc{soup} packets.
15472 @kindex G s b (Group)
15473 @findex gnus-group-brew-soup
15474 Pack all unread articles in the current group
15475 (@code{gnus-group-brew-soup}). This command understands the
15476 process/prefix convention.
15479 @kindex G s w (Group)
15480 @findex gnus-soup-save-areas
15481 Save all @sc{soup} data files (@code{gnus-soup-save-areas}).
15484 @kindex G s s (Group)
15485 @findex gnus-soup-send-replies
15486 Send all replies from the replies packet
15487 (@code{gnus-soup-send-replies}).
15490 @kindex G s p (Group)
15491 @findex gnus-soup-pack-packet
15492 Pack all files into a @sc{soup} packet (@code{gnus-soup-pack-packet}).
15495 @kindex G s r (Group)
15496 @findex nnsoup-pack-replies
15497 Pack all replies into a replies packet (@code{nnsoup-pack-replies}).
15500 @kindex O s (Summary)
15501 @findex gnus-soup-add-article
15502 This summary-mode command adds the current article to a @sc{soup} packet
15503 (@code{gnus-soup-add-article}). It understands the process/prefix
15504 convention (@pxref{Process/Prefix}).
15509 There are a few variables to customize where Gnus will put all these
15514 @item gnus-soup-directory
15515 @vindex gnus-soup-directory
15516 Directory where Gnus will save intermediate files while composing
15517 @sc{soup} packets. The default is @file{~/SoupBrew/}.
15519 @item gnus-soup-replies-directory
15520 @vindex gnus-soup-replies-directory
15521 This is what Gnus will use as a temporary directory while sending our
15522 reply packets. @file{~/SoupBrew/SoupReplies/} is the default.
15524 @item gnus-soup-prefix-file
15525 @vindex gnus-soup-prefix-file
15526 Name of the file where Gnus stores the last used prefix. The default is
15527 @samp{gnus-prefix}.
15529 @item gnus-soup-packer
15530 @vindex gnus-soup-packer
15531 A format string command for packing a @sc{soup} packet. The default is
15532 @samp{tar cf - %s | gzip > $HOME/Soupout%d.tgz}.
15534 @item gnus-soup-unpacker
15535 @vindex gnus-soup-unpacker
15536 Format string command for unpacking a @sc{soup} packet. The default is
15537 @samp{gunzip -c %s | tar xvf -}.
15539 @item gnus-soup-packet-directory
15540 @vindex gnus-soup-packet-directory
15541 Where Gnus will look for reply packets. The default is @file{~/}.
15543 @item gnus-soup-packet-regexp
15544 @vindex gnus-soup-packet-regexp
15545 Regular expression matching @sc{soup} reply packets in
15546 @code{gnus-soup-packet-directory}.
15552 @subsubsection @sc{soup} Groups
15555 @code{nnsoup} is the back end for reading @sc{soup} packets. It will
15556 read incoming packets, unpack them, and put them in a directory where
15557 you can read them at leisure.
15559 These are the variables you can use to customize its behavior:
15563 @item nnsoup-tmp-directory
15564 @vindex nnsoup-tmp-directory
15565 When @code{nnsoup} unpacks a @sc{soup} packet, it does it in this
15566 directory. (@file{/tmp/} by default.)
15568 @item nnsoup-directory
15569 @vindex nnsoup-directory
15570 @code{nnsoup} then moves each message and index file to this directory.
15571 The default is @file{~/SOUP/}.
15573 @item nnsoup-replies-directory
15574 @vindex nnsoup-replies-directory
15575 All replies will be stored in this directory before being packed into a
15576 reply packet. The default is @file{~/SOUP/replies/"}.
15578 @item nnsoup-replies-format-type
15579 @vindex nnsoup-replies-format-type
15580 The @sc{soup} format of the replies packets. The default is @samp{?n}
15581 (rnews), and I don't think you should touch that variable. I probably
15582 shouldn't even have documented it. Drats! Too late!
15584 @item nnsoup-replies-index-type
15585 @vindex nnsoup-replies-index-type
15586 The index type of the replies packet. The default is @samp{?n}, which
15587 means ``none''. Don't fiddle with this one either!
15589 @item nnsoup-active-file
15590 @vindex nnsoup-active-file
15591 Where @code{nnsoup} stores lots of information. This is not an ``active
15592 file'' in the @code{nntp} sense; it's an Emacs Lisp file. If you lose
15593 this file or mess it up in any way, you're dead. The default is
15594 @file{~/SOUP/active}.
15596 @item nnsoup-packer
15597 @vindex nnsoup-packer
15598 Format string command for packing a reply @sc{soup} packet. The default
15599 is @samp{tar cf - %s | gzip > $HOME/Soupin%d.tgz}.
15601 @item nnsoup-unpacker
15602 @vindex nnsoup-unpacker
15603 Format string command for unpacking incoming @sc{soup} packets. The
15604 default is @samp{gunzip -c %s | tar xvf -}.
15606 @item nnsoup-packet-directory
15607 @vindex nnsoup-packet-directory
15608 Where @code{nnsoup} will look for incoming packets. The default is
15611 @item nnsoup-packet-regexp
15612 @vindex nnsoup-packet-regexp
15613 Regular expression matching incoming @sc{soup} packets. The default is
15616 @item nnsoup-always-save
15617 @vindex nnsoup-always-save
15618 If non-@code{nil}, save the replies buffer after each posted message.
15624 @subsubsection SOUP Replies
15626 Just using @code{nnsoup} won't mean that your postings and mailings end
15627 up in @sc{soup} reply packets automagically. You have to work a bit
15628 more for that to happen.
15630 @findex nnsoup-set-variables
15631 The @code{nnsoup-set-variables} command will set the appropriate
15632 variables to ensure that all your followups and replies end up in the
15635 In specific, this is what it does:
15638 (setq message-send-news-function 'nnsoup-request-post)
15639 (setq message-send-mail-function 'nnsoup-request-mail)
15642 And that's it, really. If you only want news to go into the @sc{soup}
15643 system you just use the first line. If you only want mail to be
15644 @sc{soup}ed you use the second.
15647 @node Mail-To-News Gateways
15648 @subsection Mail-To-News Gateways
15649 @cindex mail-to-news gateways
15652 If your local @code{nntp} server doesn't allow posting, for some reason
15653 or other, you can post using one of the numerous mail-to-news gateways.
15654 The @code{nngateway} back end provides the interface.
15656 Note that you can't read anything from this back end---it can only be
15662 @item nngateway-address
15663 @vindex nngateway-address
15664 This is the address of the mail-to-news gateway.
15666 @item nngateway-header-transformation
15667 @vindex nngateway-header-transformation
15668 News headers often have to be transformed in some odd way or other
15669 for the mail-to-news gateway to accept it. This variable says what
15670 transformation should be called, and defaults to
15671 @code{nngateway-simple-header-transformation}. The function is called
15672 narrowed to the headers to be transformed and with one parameter---the
15675 This default function just inserts a new @code{To} header based on the
15676 @code{Newsgroups} header and the gateway address.
15677 For instance, an article with this @code{Newsgroups} header:
15680 Newsgroups: alt.religion.emacs
15683 will get this @code{From} header inserted:
15686 To: alt-religion-emacs@@GATEWAY
15689 The following pre-defined functions exist:
15691 @findex nngateway-simple-header-transformation
15694 @item nngateway-simple-header-transformation
15695 Creates a @code{To} header that looks like
15696 @var{newsgroup}@@@code{nngateway-address}.
15698 @findex nngateway-mail2news-header-transformation
15700 @item nngateway-mail2news-header-transformation
15701 Creates a @code{To} header that looks like
15702 @code{nngateway-address}.
15707 (setq gnus-post-method
15709 "mail2news@@replay.com"
15710 (nngateway-header-transformation
15711 nngateway-mail2news-header-transformation)))
15719 So, to use this, simply say something like:
15722 (setq gnus-post-method '(nngateway "GATEWAY.ADDRESS"))
15727 @node Combined Groups
15728 @section Combined Groups
15730 Gnus allows combining a mixture of all the other group types into bigger
15734 * Virtual Groups:: Combining articles from many groups.
15735 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
15739 @node Virtual Groups
15740 @subsection Virtual Groups
15742 @cindex virtual groups
15743 @cindex merging groups
15745 An @dfn{nnvirtual group} is really nothing more than a collection of
15748 For instance, if you are tired of reading many small groups, you can
15749 put them all in one big group, and then grow tired of reading one
15750 big, unwieldy group. The joys of computing!
15752 You specify @code{nnvirtual} as the method. The address should be a
15753 regexp to match component groups.
15755 All marks in the virtual group will stick to the articles in the
15756 component groups. So if you tick an article in a virtual group, the
15757 article will also be ticked in the component group from whence it
15758 came. (And vice versa---marks from the component groups will also be
15759 shown in the virtual group.). To create an empty virtual group, run
15760 @kbd{G V} (@code{gnus-group-make-empty-virtual}) in the group buffer
15761 and edit the method regexp with @kbd{M-e}
15762 (@code{gnus-group-edit-group-method})
15764 Here's an example @code{nnvirtual} method that collects all Andrea Dworkin
15765 newsgroups into one, big, happy newsgroup:
15768 (nnvirtual "^alt\\.fan\\.andrea-dworkin$\\|^rec\\.dworkin.*")
15771 The component groups can be native or foreign; everything should work
15772 smoothly, but if your computer explodes, it was probably my fault.
15774 Collecting the same group from several servers might actually be a good
15775 idea if users have set the Distribution header to limit distribution.
15776 If you would like to read @samp{soc.motss} both from a server in Japan
15777 and a server in Norway, you could use the following as the group regexp:
15780 "^nntp\\+server\\.jp:soc\\.motss$\\|^nntp\\+server\\.no:soc\\.motss$"
15783 (Remember, though, that if you're creating the group with @kbd{G m}, you
15784 shouldn't double the backslashes, and you should leave off the quote
15785 characters at the beginning and the end of the string.)
15787 This should work kinda smoothly---all articles from both groups should
15788 end up in this one, and there should be no duplicates. Threading (and
15789 the rest) will still work as usual, but there might be problems with the
15790 sequence of articles. Sorting on date might be an option here
15791 (@pxref{Selecting a Group}).
15793 One limitation, however---all groups included in a virtual
15794 group have to be alive (i.e., subscribed or unsubscribed). Killed or
15795 zombie groups can't be component groups for @code{nnvirtual} groups.
15797 @vindex nnvirtual-always-rescan
15798 If the @code{nnvirtual-always-rescan} is non-@code{nil},
15799 @code{nnvirtual} will always scan groups for unread articles when
15800 entering a virtual group. If this variable is @code{nil} (which is the
15801 default) and you read articles in a component group after the virtual
15802 group has been activated, the read articles from the component group
15803 will show up when you enter the virtual group. You'll also see this
15804 effect if you have two virtual groups that have a component group in
15805 common. If that's the case, you should set this variable to @code{t}.
15806 Or you can just tap @code{M-g} on the virtual group every time before
15807 you enter it---it'll have much the same effect.
15809 @code{nnvirtual} can have both mail and news groups as component groups.
15810 When responding to articles in @code{nnvirtual} groups, @code{nnvirtual}
15811 has to ask the back end of the component group the article comes from
15812 whether it is a news or mail back end. However, when you do a @kbd{^},
15813 there is typically no sure way for the component back end to know this,
15814 and in that case @code{nnvirtual} tells Gnus that the article came from a
15815 not-news back end. (Just to be on the safe side.)
15817 @kbd{C-c C-n} in the message buffer will insert the @code{Newsgroups}
15818 line from the article you respond to in these cases.
15820 @code{nnvirtual} groups do not inherit anything but articles and marks
15821 from component groups---group parameters, for instance, are not
15825 @node Kibozed Groups
15826 @subsection Kibozed Groups
15830 @dfn{Kibozing} is defined by @sc{oed} as ``grepping through (parts of)
15831 the news feed''. @code{nnkiboze} is a back end that will do this for
15832 you. Oh joy! Now you can grind any @sc{nntp} server down to a halt
15833 with useless requests! Oh happiness!
15835 @kindex G k (Group)
15836 To create a kibozed group, use the @kbd{G k} command in the group
15839 The address field of the @code{nnkiboze} method is, as with
15840 @code{nnvirtual}, a regexp to match groups to be ``included'' in the
15841 @code{nnkiboze} group. That's where most similarities between @code{nnkiboze}
15842 and @code{nnvirtual} end.
15844 In addition to this regexp detailing component groups, an @code{nnkiboze} group
15845 must have a score file to say what articles are to be included in
15846 the group (@pxref{Scoring}).
15848 @kindex M-x nnkiboze-generate-groups
15849 @findex nnkiboze-generate-groups
15850 You must run @kbd{M-x nnkiboze-generate-groups} after creating the
15851 @code{nnkiboze} groups you want to have. This command will take time. Lots of
15852 time. Oodles and oodles of time. Gnus has to fetch the headers from
15853 all the articles in all the component groups and run them through the
15854 scoring process to determine if there are any articles in the groups
15855 that are to be part of the @code{nnkiboze} groups.
15857 Please limit the number of component groups by using restrictive
15858 regexps. Otherwise your sysadmin may become annoyed with you, and the
15859 @sc{nntp} site may throw you off and never let you back in again.
15860 Stranger things have happened.
15862 @code{nnkiboze} component groups do not have to be alive---they can be dead,
15863 and they can be foreign. No restrictions.
15865 @vindex nnkiboze-directory
15866 The generation of an @code{nnkiboze} group means writing two files in
15867 @code{nnkiboze-directory}, which is @file{~/News/} by default. One
15868 contains the @sc{nov} header lines for all the articles in the group,
15869 and the other is an additional @file{.newsrc} file to store information
15870 on what groups have been searched through to find component articles.
15872 Articles marked as read in the @code{nnkiboze} group will have
15873 their @sc{nov} lines removed from the @sc{nov} file.
15876 @node Gnus Unplugged
15877 @section Gnus Unplugged
15882 @cindex Gnus Unplugged
15884 In olden times (ca. February '88), people used to run their newsreaders
15885 on big machines with permanent connections to the net. News transport
15886 was dealt with by news servers, and all the newsreaders had to do was to
15887 read news. Believe it or not.
15889 Nowadays most people read news and mail at home, and use some sort of
15890 modem to connect to the net. To avoid running up huge phone bills, it
15891 would be nice to have a way to slurp down all the news and mail, hang up
15892 the phone, read for several hours, and then upload any responses you
15893 have to make. And then you repeat the procedure.
15895 Of course, you can use news servers for doing this as well. I've used
15896 @code{inn} together with @code{slurp}, @code{pop} and @code{sendmail}
15897 for some years, but doing that's a bore. Moving the news server
15898 functionality up to the newsreader makes sense if you're the only person
15899 reading news on a machine.
15901 Using Gnus as an ``offline'' newsreader is quite simple.
15905 First, set up Gnus as you would do if you were running it on a machine
15906 that has full connection to the net. Go ahead. I'll still be waiting
15910 Then, put the following magical incantation at the end of your
15911 @file{.gnus.el} file:
15918 That's it. Gnus is now an ``offline'' newsreader.
15920 Of course, to use it as such, you have to learn a few new commands.
15923 * Agent Basics:: How it all is supposed to work.
15924 * Agent Categories:: How to tell the Gnus Agent what to download.
15925 * Agent Commands:: New commands for all the buffers.
15926 * Agent Expiry:: How to make old articles go away.
15927 * Agent and IMAP:: How to use the Agent with IMAP.
15928 * Outgoing Messages:: What happens when you post/mail something?
15929 * Agent Variables:: Customizing is fun.
15930 * Example Setup:: An example @file{.gnus.el} file for offline people.
15931 * Batching Agents:: How to fetch news from a @code{cron} job.
15932 * Agent Caveats:: What you think it'll do and what it does.
15937 @subsection Agent Basics
15939 First, let's get some terminology out of the way.
15941 The Gnus Agent is said to be @dfn{unplugged} when you have severed the
15942 connection to the net (and notified the Agent that this is the case).
15943 When the connection to the net is up again (and Gnus knows this), the
15944 Agent is @dfn{plugged}.
15946 The @dfn{local} machine is the one you're running on, and which isn't
15947 connected to the net continuously.
15949 @dfn{Downloading} means fetching things from the net to your local
15950 machine. @dfn{Uploading} is doing the opposite.
15952 Let's take a typical Gnus session using the Agent.
15957 You start Gnus with @code{gnus-unplugged}. This brings up the Gnus
15958 Agent in a disconnected state. You can read all the news that you have
15959 already fetched while in this mode.
15962 You then decide to see whether any new news has arrived. You connect
15963 your machine to the net (using PPP or whatever), and then hit @kbd{J j}
15964 to make Gnus become @dfn{plugged} and use @kbd{g} to check for new mail
15965 as usual. To check for new mail in unplugged mode, see (@pxref{Mail
15966 Source Specifiers}).
15969 You can then read the new news immediately, or you can download the news
15970 onto your local machine. If you want to do the latter, you press @kbd{g}
15971 to check if there are any new news and then @kbd{J
15972 s} to fetch all the eligible articles in all the groups. (To let Gnus
15973 know which articles you want to download, @pxref{Agent Categories}.)
15976 After fetching the articles, you press @kbd{J j} to make Gnus become
15977 unplugged again, and you shut down the PPP thing (or whatever). And
15978 then you read the news offline.
15981 And then you go to step 2.
15984 Here are some things you should do the first time (or so) that you use
15990 Decide which servers should be covered by the Agent. If you have a mail
15991 back end, it would probably be nonsensical to have it covered by the
15992 Agent. Go to the server buffer (@kbd{^} in the group buffer) and press
15993 @kbd{J a} the server (or servers) that you wish to have covered by the
15994 Agent (@pxref{Server Agent Commands}). This will typically be only the
15995 primary select method, which is listed on the bottom in the buffer.
15998 Decide on download policy. @xref{Agent Categories}.
16005 @node Agent Categories
16006 @subsection Agent Categories
16008 One of the main reasons to integrate the news transport layer into the
16009 newsreader is to allow greater control over what articles to download.
16010 There's not much point in downloading huge amounts of articles, just to
16011 find out that you're not interested in reading any of them. It's better
16012 to be somewhat more conservative in choosing what to download, and then
16013 mark the articles for downloading manually if it should turn out that
16014 you're interested in the articles anyway.
16016 The main way to control what is to be downloaded is to create a
16017 @dfn{category} and then assign some (or all) groups to this category.
16018 Groups that do not belong in any other category belong to the
16019 @code{default} category. Gnus has its own buffer for creating and
16020 managing categories.
16023 * Category Syntax:: What a category looks like.
16024 * Category Buffer:: A buffer for maintaining categories.
16025 * Category Variables:: Customize'r'Us.
16029 @node Category Syntax
16030 @subsubsection Category Syntax
16032 A category consists of two things.
16036 A predicate which (generally) gives a rough outline of which articles
16037 are eligible for downloading; and
16040 a score rule which (generally) gives you a finer granularity when
16041 deciding what articles to download. (Note that this @dfn{download
16042 score} is not necessarily related to normal scores.)
16045 A predicate in its simplest form can be a single predicate such as
16046 @code{true} or @code{false}. These two will download every available
16047 article or nothing respectively. In the case of these two special
16048 predicates an additional score rule is superfluous.
16050 Predicates of @code{high} or @code{low} download articles in respect of
16051 their scores in relationship to @code{gnus-agent-high-score} and
16052 @code{gnus-agent-low-score} as described below.
16054 To gain even finer control of what is to be regarded eligible for
16055 download a predicate can consist of a number of predicates with logical
16056 operators sprinkled in between.
16058 Perhaps some examples are in order.
16060 Here's a simple predicate. (It's the default predicate, in fact, used
16061 for all groups that don't belong to any other category.)
16067 Quite simple, eh? This predicate is true if and only if the article is
16068 short (for some value of ``short'').
16070 Here's a more complex predicate:
16079 This means that an article should be downloaded if it has a high score,
16080 or if the score is not low and the article is not long. You get the
16083 The available logical operators are @code{or}, @code{and} and
16084 @code{not}. (If you prefer, you can use the more ``C''-ish operators
16085 @samp{|}, @code{&} and @code{!} instead.)
16087 The following predicates are pre-defined, but if none of these fit what
16088 you want to do, you can write your own.
16092 True iff the article is shorter than @code{gnus-agent-short-article}
16093 lines; default 100.
16096 True iff the article is longer than @code{gnus-agent-long-article}
16097 lines; default 200.
16100 True iff the article has a download score less than
16101 @code{gnus-agent-low-score}; default 0.
16104 True iff the article has a download score greater than
16105 @code{gnus-agent-high-score}; default 0.
16108 True iff the Gnus Agent guesses that the article is spam. The
16109 heuristics may change over time, but at present it just computes a
16110 checksum and sees whether articles match.
16119 If you want to create your own predicate function, here's what you have
16120 to know: The functions are called with no parameters, but the
16121 @code{gnus-headers} and @code{gnus-score} dynamic variables are bound to
16124 For example, you could decide that you don't want to download articles
16125 that were posted more than a certain number of days ago (e.g. posted
16126 more than @code{gnus-agent-expire-days} ago) you might write a function
16127 something along the lines of the following:
16130 (defun my-article-old-p ()
16131 "Say whether an article is old."
16132 (< (time-to-days (date-to-time (mail-header-date gnus-headers)))
16133 (- (time-to-days (current-time)) gnus-agent-expire-days)))
16136 with the predicate then defined as:
16139 (not my-article-old-p)
16142 or you could append your predicate to the predefined
16143 @code{gnus-category-predicate-alist} in your @file{~/.gnus.el} or
16144 wherever. (Note: this would have to be at a point *after*
16145 @code{gnus-agent} has been loaded via @code{(gnus-agentize)})
16148 (setq gnus-category-predicate-alist
16149 (append gnus-category-predicate-alist
16150 '((old . my-article-old-p))))
16153 and simply specify your predicate as:
16159 If/when using something like the above, be aware that there are many
16160 misconfigured systems/mailers out there and so an article's date is not
16161 always a reliable indication of when it was posted. Hell, some people
16162 just don't give a damn.
16164 The above predicates apply to *all* the groups which belong to the
16165 category. However, if you wish to have a specific predicate for an
16166 individual group within a category, or you're just too lazy to set up a
16167 new category, you can enter a group's individual predicate in it's group
16168 parameters like so:
16171 (agent-predicate . short)
16174 This is the group parameter equivalent of the agent category default.
16175 Note that when specifying a single word predicate like this, the
16176 @code{agent-predicate} specification must be in dotted pair notation.
16178 The equivalent of the longer example from above would be:
16181 (agent-predicate or high (and (not low) (not long)))
16184 The outer parenthesis required in the category specification are not
16185 entered here as, not being in dotted pair notation, the value of the
16186 predicate is assumed to be a list.
16189 Now, the syntax of the download score is the same as the syntax of
16190 normal score files, except that all elements that require actually
16191 seeing the article itself are verboten. This means that only the
16192 following headers can be scored on: @code{Subject}, @code{From},
16193 @code{Date}, @code{Message-ID}, @code{References}, @code{Chars},
16194 @code{Lines}, and @code{Xref}.
16196 As with predicates, the specification of the @code{download score rule}
16197 to use in respect of a group can be in either the category definition if
16198 it's to be applicable to all groups in therein, or a group's parameters
16199 if it's to be specific to that group.
16201 In both of these places the @code{download score rule} can take one of
16208 This has the same syntax as a normal gnus score file except only a
16209 subset of scoring keywords are available as mentioned above.
16215 Category specification
16219 ("Lars Ingebrigtsen" 1000000 nil s))
16225 Group Parameter specification
16228 (agent-score ("from"
16229 ("Lars Ingebrigtsen" 1000000 nil s))
16234 Again, note the omission of the outermost parenthesis here.
16240 These score files must *only* contain the permitted scoring keywords
16247 Category specification
16250 ("~/News/agent.SCORE")
16256 ("~/News/agent.SCORE" "~/News/agent.group.SCORE")
16260 Group Parameter specification
16263 (agent-score "~/News/agent.SCORE")
16266 Additional score files can be specified as above. Need I say anything
16271 Use @code{normal} score files
16273 If you don't want to maintain two sets of scoring rules for a group, and
16274 your desired @code{downloading} criteria for a group are the same as your
16275 @code{reading} criteria then you can tell the agent to refer to your
16276 @code{normal} score files when deciding what to download.
16278 These directives in either the category definition or a group's
16279 parameters will cause the agent to read in all the applicable score
16280 files for a group, *filtering out* those sections that do not
16281 relate to one of the permitted subset of scoring keywords.
16285 Category Specification
16292 Group Parameter specification
16295 (agent-score . file)
16300 @node Category Buffer
16301 @subsubsection Category Buffer
16303 You'd normally do all category maintenance from the category buffer.
16304 When you enter it for the first time (with the @kbd{J c} command from
16305 the group buffer), you'll only see the @code{default} category.
16307 The following commands are available in this buffer:
16311 @kindex q (Category)
16312 @findex gnus-category-exit
16313 Return to the group buffer (@code{gnus-category-exit}).
16316 @kindex k (Category)
16317 @findex gnus-category-kill
16318 Kill the current category (@code{gnus-category-kill}).
16321 @kindex c (Category)
16322 @findex gnus-category-copy
16323 Copy the current category (@code{gnus-category-copy}).
16326 @kindex a (Category)
16327 @findex gnus-category-add
16328 Add a new category (@code{gnus-category-add}).
16331 @kindex p (Category)
16332 @findex gnus-category-edit-predicate
16333 Edit the predicate of the current category
16334 (@code{gnus-category-edit-predicate}).
16337 @kindex g (Category)
16338 @findex gnus-category-edit-groups
16339 Edit the list of groups belonging to the current category
16340 (@code{gnus-category-edit-groups}).
16343 @kindex s (Category)
16344 @findex gnus-category-edit-score
16345 Edit the download score rule of the current category
16346 (@code{gnus-category-edit-score}).
16349 @kindex l (Category)
16350 @findex gnus-category-list
16351 List all the categories (@code{gnus-category-list}).
16355 @node Category Variables
16356 @subsubsection Category Variables
16359 @item gnus-category-mode-hook
16360 @vindex gnus-category-mode-hook
16361 Hook run in category buffers.
16363 @item gnus-category-line-format
16364 @vindex gnus-category-line-format
16365 Format of the lines in the category buffer (@pxref{Formatting
16366 Variables}). Valid elements are:
16370 The name of the category.
16373 The number of groups in the category.
16376 @item gnus-category-mode-line-format
16377 @vindex gnus-category-mode-line-format
16378 Format of the category mode line (@pxref{Mode Line Formatting}).
16380 @item gnus-agent-short-article
16381 @vindex gnus-agent-short-article
16382 Articles that have fewer lines than this are short. Default 100.
16384 @item gnus-agent-long-article
16385 @vindex gnus-agent-long-article
16386 Articles that have more lines than this are long. Default 200.
16388 @item gnus-agent-low-score
16389 @vindex gnus-agent-low-score
16390 Articles that have a score lower than this have a low score. Default
16393 @item gnus-agent-high-score
16394 @vindex gnus-agent-high-score
16395 Articles that have a score higher than this have a high score. Default
16401 @node Agent Commands
16402 @subsection Agent Commands
16404 All the Gnus Agent commands are on the @kbd{J} submap. The @kbd{J j}
16405 (@code{gnus-agent-toggle-plugged}) command works in all modes, and
16406 toggles the plugged/unplugged state of the Gnus Agent.
16410 * Group Agent Commands::
16411 * Summary Agent Commands::
16412 * Server Agent Commands::
16415 You can run a complete batch command from the command line with the
16416 following incantation:
16418 @cindex gnus-agent-batch
16420 $ emacs -batch -l ~/.gnus.el -f gnus-agent-batch
16425 @node Group Agent Commands
16426 @subsubsection Group Agent Commands
16430 @kindex J u (Agent Group)
16431 @findex gnus-agent-fetch-groups
16432 Fetch all eligible articles in the current group
16433 (@code{gnus-agent-fetch-groups}).
16436 @kindex J c (Agent Group)
16437 @findex gnus-enter-category-buffer
16438 Enter the Agent category buffer (@code{gnus-enter-category-buffer}).
16441 @kindex J s (Agent Group)
16442 @findex gnus-agent-fetch-session
16443 Fetch all eligible articles in all groups
16444 (@code{gnus-agent-fetch-session}).
16447 @kindex J S (Agent Group)
16448 @findex gnus-group-send-queue
16449 Send all sendable messages in the queue group
16450 (@code{gnus-group-send-queue}). @xref{Drafts}.
16453 @kindex J a (Agent Group)
16454 @findex gnus-agent-add-group
16455 Add the current group to an Agent category
16456 (@code{gnus-agent-add-group}). This command understands the
16457 process/prefix convention (@pxref{Process/Prefix}).
16460 @kindex J r (Agent Group)
16461 @findex gnus-agent-remove-group
16462 Remove the current group from its category, if any
16463 (@code{gnus-agent-remove-group}). This command understands the
16464 process/prefix convention (@pxref{Process/Prefix}).
16467 @kindex J Y (Agent Group)
16468 @findex gnus-agent-synchronize-flags
16469 Synchronize flags changed while unplugged with remote server, if any.
16475 @node Summary Agent Commands
16476 @subsubsection Summary Agent Commands
16480 @kindex J # (Agent Summary)
16481 @findex gnus-agent-mark-article
16482 Mark the article for downloading (@code{gnus-agent-mark-article}).
16485 @kindex J M-# (Agent Summary)
16486 @findex gnus-agent-unmark-article
16487 Remove the downloading mark from the article
16488 (@code{gnus-agent-unmark-article}).
16491 @kindex @@ (Agent Summary)
16492 @findex gnus-agent-toggle-mark
16493 Toggle whether to download the article (@code{gnus-agent-toggle-mark}).
16496 @kindex J c (Agent Summary)
16497 @findex gnus-agent-catchup
16498 Mark all undownloaded articles as read (@code{gnus-agent-catchup}).
16501 @kindex J u (Agent Summary)
16502 @findex gnus-agent-summary-fetch-group
16503 Download all downloadable articles in the current group
16504 (@code{gnus-agent-summary-fetch-group}).
16509 @node Server Agent Commands
16510 @subsubsection Server Agent Commands
16514 @kindex J a (Agent Server)
16515 @findex gnus-agent-add-server
16516 Add the current server to the list of servers covered by the Gnus Agent
16517 (@code{gnus-agent-add-server}).
16520 @kindex J r (Agent Server)
16521 @findex gnus-agent-remove-server
16522 Remove the current server from the list of servers covered by the Gnus
16523 Agent (@code{gnus-agent-remove-server}).
16529 @subsection Agent Expiry
16531 @vindex gnus-agent-expire-days
16532 @findex gnus-agent-expire
16533 @kindex M-x gnus-agent-expire
16534 @cindex Agent expiry
16535 @cindex Gnus Agent expiry
16538 @code{nnagent} doesn't handle expiry. Instead, there's a special
16539 @code{gnus-agent-expire} command that will expire all read articles that
16540 are older than @code{gnus-agent-expire-days} days. It can be run
16541 whenever you feel that you're running out of space. It's not
16542 particularly fast or efficient, and it's not a particularly good idea to
16543 interrupt it (with @kbd{C-g} or anything else) once you've started it.
16545 @code{gnus-agent-expire-days} can also be a list of regexp/day pairs.
16546 The regexps will be matched against group names to allow differing
16547 expiry in different groups.
16550 (setq gnus-agent-expire-days
16556 If you use the list form, the last element must always be the default
16557 method---it must always match all groups.
16559 @vindex gnus-agent-expire-all
16560 if @code{gnus-agent-expire-all} is non-@code{nil}, this command will
16561 expire all articles---unread, read, ticked and dormant. If @code{nil}
16562 (which is the default), only read articles are eligible for expiry, and
16563 unread, ticked and dormant articles will be kept indefinitely.
16566 @node Agent and IMAP
16567 @subsection Agent and IMAP
16569 The Agent work with any Gnus back end, including nnimap. However,
16570 since there are some conceptual differences between @sc{nntp} and
16571 @sc{imap}, this section (should) provide you with some information to
16572 make Gnus Agent work smoother as a @sc{imap} Disconnected Mode client.
16574 The first thing to keep in mind is that all flags (read, ticked, etc)
16575 are kept on the @sc{imap} server, rather than in @code{.newsrc} as is the
16576 case for nntp. Thus Gnus need to remember flag changes when
16577 disconnected, and synchronize these flags when you plug back in.
16579 Gnus keep track of flag changes when reading nnimap groups under the
16580 Agent by default. When you plug back in, by default Gnus will check if
16581 you have any changed any flags and ask if you wish to synchronize these
16582 with the server. This behavior is customizable with
16583 @code{gnus-agent-synchronize-flags}.
16585 @vindex gnus-agent-synchronize-flags
16586 If @code{gnus-agent-synchronize-flags} is @code{nil}, the Agent will
16587 never automatically synchronize flags. If it is @code{ask}, the
16588 default, the Agent will check if you made any changes and if so ask if
16589 you wish to synchronize these when you re-connect. If it has any other
16590 value, all flags will be synchronized automatically.
16592 If you do not wish to automatically synchronize flags when you
16593 re-connect, this can be done manually with the
16594 @code{gnus-agent-synchronize-flags} command that is bound to @kbd{J Y}
16595 in the group buffer by default.
16597 Some things are currently not implemented in the Agent that you'd might
16598 expect from a disconnected @sc{imap} client, including:
16603 Copying/moving articles into nnimap groups when unplugged.
16606 Creating/deleting nnimap groups when unplugged.
16610 Technical note: the synchronization algorithm does not work by "pushing"
16611 all local flags to the server, but rather incrementally update the
16612 server view of flags by changing only those flags that were changed by
16613 the user. Thus, if you set one flag on a article, quit the group and
16614 re-select the group and remove the flag; the flag will be set and
16615 removed from the server when you "synchronize". The queued flag
16616 operations can be found in the per-server @code{flags} file in the Agent
16617 directory. It's emptied when you synchronize flags.
16620 @node Outgoing Messages
16621 @subsection Outgoing Messages
16623 When Gnus is unplugged, all outgoing messages (both mail and news) are
16624 stored in the draft groups (@pxref{Drafts}). You can view them there
16625 after posting, and edit them at will.
16627 When Gnus is plugged again, you can send the messages either from the
16628 draft group with the special commands available there, or you can use
16629 the @kbd{J S} command in the group buffer to send all the sendable
16630 messages in the draft group.
16634 @node Agent Variables
16635 @subsection Agent Variables
16638 @item gnus-agent-directory
16639 @vindex gnus-agent-directory
16640 Where the Gnus Agent will store its files. The default is
16641 @file{~/News/agent/}.
16643 @item gnus-agent-handle-level
16644 @vindex gnus-agent-handle-level
16645 Groups on levels (@pxref{Group Levels}) higher than this variable will
16646 be ignored by the Agent. The default is @code{gnus-level-subscribed},
16647 which means that only subscribed group will be considered by the Agent
16650 @item gnus-agent-plugged-hook
16651 @vindex gnus-agent-plugged-hook
16652 Hook run when connecting to the network.
16654 @item gnus-agent-unplugged-hook
16655 @vindex gnus-agent-unplugged-hook
16656 Hook run when disconnecting from the network.
16658 @item gnus-agent-fetched-hook
16659 @vindex gnus-agent-fetched-hook
16660 Hook run when after finishing fetching articles.
16662 @item gnus-agent-cache
16663 @vindex gnus-agent-cache
16664 Variable to control whether use the locally stored NOV and articles when
16667 @item gnus-agent-go-online
16668 @vindex gnus-agent-go-online
16669 If @code{gnus-agent-go-online} is @code{nil}, the Agent will never
16670 automatically switch offline servers into online status. If it is
16671 @code{ask}, the default, the Agent will ask if you wish to switch
16672 offline servers into online status when you re-connect. If it has any
16673 other value, all offline servers will be automatically switched into
16679 @node Example Setup
16680 @subsection Example Setup
16682 If you don't want to read this manual, and you have a fairly standard
16683 setup, you may be able to use something like the following as your
16684 @file{.gnus.el} file to get started.
16687 ;;; Define how Gnus is to fetch news. We do this over @sc{nntp}
16688 ;;; from your ISP's server.
16689 (setq gnus-select-method '(nntp "news.your-isp.com"))
16691 ;;; Define how Gnus is to read your mail. We read mail from
16692 ;;; your ISP's POP server.
16693 (setq mail-sources '((pop :server "pop.your-isp.com")))
16695 ;;; Say how Gnus is to store the mail. We use nnml groups.
16696 (setq gnus-secondary-select-methods '((nnml "")))
16698 ;;; Make Gnus into an offline newsreader.
16702 That should be it, basically. Put that in your @file{~/.gnus.el} file,
16703 edit to suit your needs, start up PPP (or whatever), and type @kbd{M-x
16706 If this is the first time you've run Gnus, you will be subscribed
16707 automatically to a few default newsgroups. You'll probably want to
16708 subscribe to more groups, and to do that, you have to query the
16709 @sc{nntp} server for a complete list of groups with the @kbd{A A}
16710 command. This usually takes quite a while, but you only have to do it
16713 After reading and parsing a while, you'll be presented with a list of
16714 groups. Subscribe to the ones you want to read with the @kbd{u}
16715 command. @kbd{l} to make all the killed groups disappear after you've
16716 subscribe to all the groups you want to read. (@kbd{A k} will bring
16717 back all the killed groups.)
16719 You can now read the groups at once, or you can download the articles
16720 with the @kbd{J s} command. And then read the rest of this manual to
16721 find out which of the other gazillion things you want to customize.
16724 @node Batching Agents
16725 @subsection Batching Agents
16727 Having the Gnus Agent fetch articles (and post whatever messages you've
16728 written) is quite easy once you've gotten things set up properly. The
16729 following shell script will do everything that is necessary:
16733 emacs -batch -l ~/.emacs -f gnus-agent-batch >/dev/null
16737 @node Agent Caveats
16738 @subsection Agent Caveats
16740 The Gnus Agent doesn't seem to work like most other offline
16741 newsreaders. Here are some common questions that some imaginary people
16745 @item If I read an article while plugged, do they get entered into the Agent?
16749 @item If I read an article while plugged, and the article already exists in the Agent, will it get downloaded once more?
16751 @strong{No}, unless @code{gnus-agent-cache} is `nil'.
16755 In short, when Gnus is unplugged, it only looks into the locally stored
16756 articles; when it's plugged, it only talks to your ISP and also uses the
16757 locally stored articles.
16764 Other people use @dfn{kill files}, but we here at Gnus Towers like
16765 scoring better than killing, so we'd rather switch than fight. They do
16766 something completely different as well, so sit up straight and pay
16769 @vindex gnus-summary-mark-below
16770 All articles have a default score (@code{gnus-summary-default-score}),
16771 which is 0 by default. This score may be raised or lowered either
16772 interactively or by score files. Articles that have a score lower than
16773 @code{gnus-summary-mark-below} are marked as read.
16775 Gnus will read any @dfn{score files} that apply to the current group
16776 before generating the summary buffer.
16778 There are several commands in the summary buffer that insert score
16779 entries based on the current article. You can, for instance, ask Gnus to
16780 lower or increase the score of all articles with a certain subject.
16782 There are two sorts of scoring entries: Permanent and temporary.
16783 Temporary score entries are self-expiring entries. Any entries that are
16784 temporary and have not been used for, say, a week, will be removed
16785 silently to help keep the sizes of the score files down.
16788 * Summary Score Commands:: Adding score entries for the current group.
16789 * Group Score Commands:: General score commands.
16790 * Score Variables:: Customize your scoring. (My, what terminology).
16791 * Score File Format:: What a score file may contain.
16792 * Score File Editing:: You can edit score files by hand as well.
16793 * Adaptive Scoring:: Big Sister Gnus knows what you read.
16794 * Home Score File:: How to say where new score entries are to go.
16795 * Followups To Yourself:: Having Gnus notice when people answer you.
16796 * Scoring On Other Headers:: Scoring on non-standard headers.
16797 * Scoring Tips:: How to score effectively.
16798 * Reverse Scoring:: That problem child of old is not problem.
16799 * Global Score Files:: Earth-spanning, ear-splitting score files.
16800 * Kill Files:: They are still here, but they can be ignored.
16801 * Converting Kill Files:: Translating kill files to score files.
16802 * GroupLens:: Getting predictions on what you like to read.
16803 * Advanced Scoring:: Using logical expressions to build score rules.
16804 * Score Decays:: It can be useful to let scores wither away.
16808 @node Summary Score Commands
16809 @section Summary Score Commands
16810 @cindex score commands
16812 The score commands that alter score entries do not actually modify real
16813 score files. That would be too inefficient. Gnus maintains a cache of
16814 previously loaded score files, one of which is considered the
16815 @dfn{current score file alist}. The score commands simply insert
16816 entries into this list, and upon group exit, this list is saved.
16818 The current score file is by default the group's local score file, even
16819 if no such score file actually exists. To insert score commands into
16820 some other score file (e.g. @file{all.SCORE}), you must first make this
16821 score file the current one.
16823 General score commands that don't actually change the score file:
16828 @kindex V s (Summary)
16829 @findex gnus-summary-set-score
16830 Set the score of the current article (@code{gnus-summary-set-score}).
16833 @kindex V S (Summary)
16834 @findex gnus-summary-current-score
16835 Display the score of the current article
16836 (@code{gnus-summary-current-score}).
16839 @kindex V t (Summary)
16840 @findex gnus-score-find-trace
16841 Display all score rules that have been used on the current article
16842 (@code{gnus-score-find-trace}).
16845 @kindex V R (Summary)
16846 @findex gnus-summary-rescore
16847 Run the current summary through the scoring process
16848 (@code{gnus-summary-rescore}). This might be useful if you're playing
16849 around with your score files behind Gnus' back and want to see the
16850 effect you're having.
16853 @kindex V c (Summary)
16854 @findex gnus-score-change-score-file
16855 Make a different score file the current
16856 (@code{gnus-score-change-score-file}).
16859 @kindex V e (Summary)
16860 @findex gnus-score-edit-current-scores
16861 Edit the current score file (@code{gnus-score-edit-current-scores}).
16862 You will be popped into a @code{gnus-score-mode} buffer (@pxref{Score
16866 @kindex V f (Summary)
16867 @findex gnus-score-edit-file
16868 Edit a score file and make this score file the current one
16869 (@code{gnus-score-edit-file}).
16872 @kindex V F (Summary)
16873 @findex gnus-score-flush-cache
16874 Flush the score cache (@code{gnus-score-flush-cache}). This is useful
16875 after editing score files.
16878 @kindex V C (Summary)
16879 @findex gnus-score-customize
16880 Customize a score file in a visually pleasing manner
16881 (@code{gnus-score-customize}).
16885 The rest of these commands modify the local score file.
16890 @kindex V m (Summary)
16891 @findex gnus-score-set-mark-below
16892 Prompt for a score, and mark all articles with a score below this as
16893 read (@code{gnus-score-set-mark-below}).
16896 @kindex V x (Summary)
16897 @findex gnus-score-set-expunge-below
16898 Prompt for a score, and add a score rule to the current score file to
16899 expunge all articles below this score
16900 (@code{gnus-score-set-expunge-below}).
16903 The keystrokes for actually making score entries follow a very regular
16904 pattern, so there's no need to list all the commands. (Hundreds of
16907 @findex gnus-summary-increase-score
16908 @findex gnus-summary-lower-score
16912 The first key is either @kbd{I} (upper case i) for increasing the score
16913 or @kbd{L} for lowering the score.
16915 The second key says what header you want to score on. The following
16916 keys are available:
16920 Score on the author name.
16923 Score on the subject line.
16926 Score on the @code{Xref} line---i.e., the cross-posting line.
16929 Score on the @code{References} line.
16935 Score on the number of lines.
16938 Score on the @code{Message-ID} header.
16941 Score on followups---this matches the author name, and adds scores to
16942 the followups to this author. (Using this key leads to the creation of
16943 @file{ADAPT} files.)
16952 Score on thread. (Using this key leads to the creation of @file{ADAPT}
16958 The third key is the match type. Which match types are valid depends on
16959 what headers you are scoring on.
16971 Substring matching.
16974 Fuzzy matching (@pxref{Fuzzy Matching}).
17003 Greater than number.
17008 The fourth and final key says whether this is a temporary (i.e., expiring)
17009 score entry, or a permanent (i.e., non-expiring) score entry, or whether
17010 it is to be done immediately, without adding to the score file.
17014 Temporary score entry.
17017 Permanent score entry.
17020 Immediately scoring.
17025 So, let's say you want to increase the score on the current author with
17026 exact matching permanently: @kbd{I a e p}. If you want to lower the
17027 score based on the subject line, using substring matching, and make a
17028 temporary score entry: @kbd{L s s t}. Pretty easy.
17030 To make things a bit more complicated, there are shortcuts. If you use
17031 a capital letter on either the second or third keys, Gnus will use
17032 defaults for the remaining one or two keystrokes. The defaults are
17033 ``substring'' and ``temporary''. So @kbd{I A} is the same as @kbd{I a s
17034 t}, and @kbd{I a R} is the same as @kbd{I a r t}.
17036 These functions take both the numerical prefix and the symbolic prefix
17037 (@pxref{Symbolic Prefixes}). A numerical prefix says how much to lower
17038 (or increase) the score of the article. A symbolic prefix of @code{a}
17039 says to use the @file{all.SCORE} file for the command instead of the
17040 current score file.
17042 @vindex gnus-score-mimic-keymap
17043 The @code{gnus-score-mimic-keymap} says whether these commands will
17044 pretend they are keymaps or not.
17047 @node Group Score Commands
17048 @section Group Score Commands
17049 @cindex group score commands
17051 There aren't many of these as yet, I'm afraid.
17056 @kindex W f (Group)
17057 @findex gnus-score-flush-cache
17058 Gnus maintains a cache of score alists to avoid having to reload them
17059 all the time. This command will flush the cache
17060 (@code{gnus-score-flush-cache}).
17064 You can do scoring from the command line by saying something like:
17066 @findex gnus-batch-score
17067 @cindex batch scoring
17069 $ emacs -batch -l ~/.emacs -l ~/.gnus.el -f gnus-batch-score
17073 @node Score Variables
17074 @section Score Variables
17075 @cindex score variables
17079 @item gnus-use-scoring
17080 @vindex gnus-use-scoring
17081 If @code{nil}, Gnus will not check for score files, and will not, in
17082 general, do any score-related work. This is @code{t} by default.
17084 @item gnus-kill-killed
17085 @vindex gnus-kill-killed
17086 If this variable is @code{nil}, Gnus will never apply score files to
17087 articles that have already been through the kill process. While this
17088 may save you lots of time, it also means that if you apply a kill file
17089 to a group, and then change the kill file and want to run it over you
17090 group again to kill more articles, it won't work. You have to set this
17091 variable to @code{t} to do that. (It is @code{t} by default.)
17093 @item gnus-kill-files-directory
17094 @vindex gnus-kill-files-directory
17095 All kill and score files will be stored in this directory, which is
17096 initialized from the @code{SAVEDIR} environment variable by default.
17097 This is @file{~/News/} by default.
17099 @item gnus-score-file-suffix
17100 @vindex gnus-score-file-suffix
17101 Suffix to add to the group name to arrive at the score file name
17102 (@samp{SCORE} by default.)
17104 @item gnus-score-uncacheable-files
17105 @vindex gnus-score-uncacheable-files
17106 @cindex score cache
17107 All score files are normally cached to avoid excessive re-loading of
17108 score files. However, if this might make your Emacs grow big and
17109 bloated, so this regexp can be used to weed out score files unlikely to be needed again. It would be a bad idea to deny caching of
17110 @file{all.SCORE}, while it might be a good idea to not cache
17111 @file{comp.infosystems.www.authoring.misc.ADAPT}. In fact, this
17112 variable is @samp{ADAPT$} by default, so no adaptive score files will
17115 @item gnus-save-score
17116 @vindex gnus-save-score
17117 If you have really complicated score files, and do lots of batch
17118 scoring, then you might set this variable to @code{t}. This will make
17119 Gnus save the scores into the @file{.newsrc.eld} file.
17121 If you do not set this to @code{t}, then manual scores (like those set
17122 with @kbd{V s} (@code{gnus-summary-set-score})) will not be preserved
17123 across group visits.
17125 @item gnus-score-interactive-default-score
17126 @vindex gnus-score-interactive-default-score
17127 Score used by all the interactive raise/lower commands to raise/lower
17128 score with. Default is 1000, which may seem excessive, but this is to
17129 ensure that the adaptive scoring scheme gets enough room to play with.
17130 We don't want the small changes from the adaptive scoring to overwrite
17131 manually entered data.
17133 @item gnus-summary-default-score
17134 @vindex gnus-summary-default-score
17135 Default score of an article, which is 0 by default.
17137 @item gnus-summary-expunge-below
17138 @vindex gnus-summary-expunge-below
17139 Don't display the summary lines of articles that have scores lower than
17140 this variable. This is @code{nil} by default, which means that no
17141 articles will be hidden. This variable is local to the summary buffers,
17142 and has to be set from @code{gnus-summary-mode-hook}.
17144 @item gnus-score-over-mark
17145 @vindex gnus-score-over-mark
17146 Mark (in the third column) used for articles with a score over the
17147 default. Default is @samp{+}.
17149 @item gnus-score-below-mark
17150 @vindex gnus-score-below-mark
17151 Mark (in the third column) used for articles with a score below the
17152 default. Default is @samp{-}.
17154 @item gnus-score-find-score-files-function
17155 @vindex gnus-score-find-score-files-function
17156 Function used to find score files for the current group. This function
17157 is called with the name of the group as the argument.
17159 Predefined functions available are:
17162 @item gnus-score-find-single
17163 @findex gnus-score-find-single
17164 Only apply the group's own score file.
17166 @item gnus-score-find-bnews
17167 @findex gnus-score-find-bnews
17168 Apply all score files that match, using bnews syntax. This is the
17169 default. If the current group is @samp{gnu.emacs.gnus}, for instance,
17170 @file{all.emacs.all.SCORE}, @file{not.alt.all.SCORE} and
17171 @file{gnu.all.SCORE} would all apply. In short, the instances of
17172 @samp{all} in the score file names are translated into @samp{.*}, and
17173 then a regexp match is done.
17175 This means that if you have some score entries that you want to apply to
17176 all groups, then you put those entries in the @file{all.SCORE} file.
17178 The score files are applied in a semi-random order, although Gnus will
17179 try to apply the more general score files before the more specific score
17180 files. It does this by looking at the number of elements in the score
17181 file names---discarding the @samp{all} elements.
17183 @item gnus-score-find-hierarchical
17184 @findex gnus-score-find-hierarchical
17185 Apply all score files from all the parent groups. This means that you
17186 can't have score files like @file{all.SCORE}, but you can have
17187 @file{SCORE}, @file{comp.SCORE} and @file{comp.emacs.SCORE} for each
17191 This variable can also be a list of functions. In that case, all
17192 these functions will be called with the group name as argument, and
17193 all the returned lists of score files will be applied. These
17194 functions can also return lists of lists of score alists directly. In
17195 that case, the functions that return these non-file score alists
17196 should probably be placed before the ``real'' score file functions, to
17197 ensure that the last score file returned is the local score file.
17200 For example, to do hierarchical scoring but use a non-server-specific
17201 overall score file, you could use the value
17203 (list (lambda (group) ("all.SCORE"))
17204 'gnus-score-find-hierarchical)
17207 @item gnus-score-expiry-days
17208 @vindex gnus-score-expiry-days
17209 This variable says how many days should pass before an unused score file
17210 entry is expired. If this variable is @code{nil}, no score file entries
17211 are expired. It's 7 by default.
17213 @item gnus-update-score-entry-dates
17214 @vindex gnus-update-score-entry-dates
17215 If this variable is non-@code{nil}, temporary score entries that have
17216 been triggered (matched) will have their dates updated. (This is how Gnus
17217 controls expiry---all non-matched-entries will become too old while
17218 matched entries will stay fresh and young.) However, if you set this
17219 variable to @code{nil}, even matched entries will grow old and will
17220 have to face that oh-so grim reaper.
17222 @item gnus-score-after-write-file-function
17223 @vindex gnus-score-after-write-file-function
17224 Function called with the name of the score file just written.
17226 @item gnus-score-thread-simplify
17227 @vindex gnus-score-thread-simplify
17228 If this variable is non-@code{nil}, article subjects will be simplified
17229 for subject scoring purposes in the same manner as with
17230 threading---according to the current value of
17231 gnus-simplify-subject-functions. If the scoring entry uses
17232 @code{substring} or @code{exact} matching, the match will also be
17233 simplified in this manner.
17238 @node Score File Format
17239 @section Score File Format
17240 @cindex score file format
17242 A score file is an @code{emacs-lisp} file that normally contains just a
17243 single form. Casual users are not expected to edit these files;
17244 everything can be changed from the summary buffer.
17246 Anyway, if you'd like to dig into it yourself, here's an example:
17250 ("Lars Ingebrigtsen" -10000)
17252 ("larsi\\|lmi" -50000 nil R))
17254 ("Ding is Badd" nil 728373))
17256 ("alt.politics" -1000 728372 s))
17261 (mark-and-expunge -10)
17265 (files "/hom/larsi/News/gnu.SCORE")
17266 (exclude-files "all.SCORE")
17267 (local (gnus-newsgroup-auto-expire t)
17268 (gnus-summary-make-false-root empty))
17272 This example demonstrates most score file elements. For a different
17273 approach, see @pxref{Advanced Scoring}.
17275 Even though this looks much like lisp code, nothing here is actually
17276 @code{eval}ed. The lisp reader is used to read this form, though, so it
17277 has to be valid syntactically, if not semantically.
17279 Six keys are supported by this alist:
17284 If the key is a string, it is the name of the header to perform the
17285 match on. Scoring can only be performed on these eight headers:
17286 @code{From}, @code{Subject}, @code{References}, @code{Message-ID},
17287 @code{Xref}, @code{Lines}, @code{Chars} and @code{Date}. In addition to
17288 these headers, there are three strings to tell Gnus to fetch the entire
17289 article and do the match on larger parts of the article: @code{Body}
17290 will perform the match on the body of the article, @code{Head} will
17291 perform the match on the head of the article, and @code{All} will
17292 perform the match on the entire article. Note that using any of these
17293 last three keys will slow down group entry @emph{considerably}. The
17294 final ``header'' you can score on is @code{Followup}. These score
17295 entries will result in new score entries being added for all follow-ups
17296 to articles that matches these score entries.
17298 Following this key is a arbitrary number of score entries, where each
17299 score entry has one to four elements.
17303 The first element is the @dfn{match element}. On most headers this will
17304 be a string, but on the Lines and Chars headers, this must be an
17308 If the second element is present, it should be a number---the @dfn{score
17309 element}. This number should be an integer in the neginf to posinf
17310 interval. This number is added to the score of the article if the match
17311 is successful. If this element is not present, the
17312 @code{gnus-score-interactive-default-score} number will be used
17313 instead. This is 1000 by default.
17316 If the third element is present, it should be a number---the @dfn{date
17317 element}. This date says when the last time this score entry matched,
17318 which provides a mechanism for expiring the score entries. It this
17319 element is not present, the score entry is permanent. The date is
17320 represented by the number of days since December 31, 1 BCE.
17323 If the fourth element is present, it should be a symbol---the @dfn{type
17324 element}. This element specifies what function should be used to see
17325 whether this score entry matches the article. What match types that can
17326 be used depends on what header you wish to perform the match on.
17329 @item From, Subject, References, Xref, Message-ID
17330 For most header types, there are the @code{r} and @code{R} (regexp), as
17331 well as @code{s} and @code{S} (substring) types, and @code{e} and
17332 @code{E} (exact match), and @code{w} (word match) types. If this
17333 element is not present, Gnus will assume that substring matching should
17334 be used. @code{R}, @code{S}, and @code{E} differ from the others in
17335 that the matches will be done in a case-sensitive manner. All these
17336 one-letter types are really just abbreviations for the @code{regexp},
17337 @code{string}, @code{exact}, and @code{word} types, which you can use
17338 instead, if you feel like.
17341 These two headers use different match types: @code{<}, @code{>},
17342 @code{=}, @code{>=} and @code{<=}.
17344 These predicates are true if
17347 (PREDICATE HEADER MATCH)
17350 evaluates to non-@code{nil}. For instance, the advanced match
17351 @code{("lines" 4 <)} (@pxref{Advanced Scoring}) will result in the
17358 Or to put it another way: When using @code{<} on @code{Lines} with 4 as
17359 the match, we get the score added if the article has less than 4 lines.
17360 (It's easy to get confused and think it's the other way around. But
17361 it's not. I think.)
17363 When matching on @code{Lines}, be careful because some back ends (like
17364 @code{nndir}) do not generate @code{Lines} header, so every article ends
17365 up being marked as having 0 lines. This can lead to strange results if
17366 you happen to lower score of the articles with few lines.
17369 For the Date header we have three kinda silly match types:
17370 @code{before}, @code{at} and @code{after}. I can't really imagine this
17371 ever being useful, but, like, it would feel kinda silly not to provide
17372 this function. Just in case. You never know. Better safe than sorry.
17373 Once burnt, twice shy. Don't judge a book by its cover. Never not have
17374 sex on a first date. (I have been told that at least one person, and I
17375 quote, ``found this function indispensable'', however.)
17379 A more useful match type is @code{regexp}. With it, you can match the
17380 date string using a regular expression. The date is normalized to
17381 ISO8601 compact format first---@var{YYYYMMDD}@code{T}@var{HHMMSS}. If
17382 you want to match all articles that have been posted on April 1st in
17383 every year, you could use @samp{....0401.........} as a match string,
17384 for instance. (Note that the date is kept in its original time zone, so
17385 this will match articles that were posted when it was April 1st where
17386 the article was posted from. Time zones are such wholesome fun for the
17389 @item Head, Body, All
17390 These three match keys use the same match types as the @code{From} (etc)
17394 This match key is somewhat special, in that it will match the
17395 @code{From} header, and affect the score of not only the matching
17396 articles, but also all followups to the matching articles. This allows
17397 you e.g. increase the score of followups to your own articles, or
17398 decrease the score of followups to the articles of some known
17399 trouble-maker. Uses the same match types as the @code{From} header
17400 uses. (Using this match key will lead to creation of @file{ADAPT}
17404 This match key works along the same lines as the @code{Followup} match
17405 key. If you say that you want to score on a (sub-)thread started by an
17406 article with a @code{Message-ID} @var{x}, then you add a @samp{thread}
17407 match. This will add a new @samp{thread} match for each article that
17408 has @var{x} in its @code{References} header. (These new @samp{thread}
17409 matches will use the @code{Message-ID}s of these matching articles.)
17410 This will ensure that you can raise/lower the score of an entire thread,
17411 even though some articles in the thread may not have complete
17412 @code{References} headers. Note that using this may lead to
17413 undeterministic scores of the articles in the thread. (Using this match
17414 key will lead to creation of @file{ADAPT} files.)
17418 @cindex Score File Atoms
17420 The value of this entry should be a number. Any articles with a score
17421 lower than this number will be marked as read.
17424 The value of this entry should be a number. Any articles with a score
17425 lower than this number will be removed from the summary buffer.
17427 @item mark-and-expunge
17428 The value of this entry should be a number. Any articles with a score
17429 lower than this number will be marked as read and removed from the
17432 @item thread-mark-and-expunge
17433 The value of this entry should be a number. All articles that belong to
17434 a thread that has a total score below this number will be marked as read
17435 and removed from the summary buffer. @code{gnus-thread-score-function}
17436 says how to compute the total score for a thread.
17439 The value of this entry should be any number of file names. These files
17440 are assumed to be score files as well, and will be loaded the same way
17443 @item exclude-files
17444 The clue of this entry should be any number of files. These files will
17445 not be loaded, even though they would normally be so, for some reason or
17449 The value of this entry will be @code{eval}el. This element will be
17450 ignored when handling global score files.
17453 Read-only score files will not be updated or saved. Global score files
17454 should feature this atom (@pxref{Global Score Files}). (Note:
17455 @dfn{Global} here really means @dfn{global}; not your personal
17456 apply-to-all-groups score files.)
17459 The value of this entry should be a number. Articles that do not have
17460 parents will get this number added to their scores. Imagine you follow
17461 some high-volume newsgroup, like @samp{comp.lang.c}. Most likely you
17462 will only follow a few of the threads, also want to see any new threads.
17464 You can do this with the following two score file entries:
17468 (mark-and-expunge -100)
17471 When you enter the group the first time, you will only see the new
17472 threads. You then raise the score of the threads that you find
17473 interesting (with @kbd{I T} or @kbd{I S}), and ignore (@kbd{C y}) the
17474 rest. Next time you enter the group, you will see new articles in the
17475 interesting threads, plus any new threads.
17477 I.e.---the orphan score atom is for high-volume groups where a few
17478 interesting threads which can't be found automatically by ordinary
17479 scoring rules exist.
17482 This entry controls the adaptive scoring. If it is @code{t}, the
17483 default adaptive scoring rules will be used. If it is @code{ignore}, no
17484 adaptive scoring will be performed on this group. If it is a list, this
17485 list will be used as the adaptive scoring rules. If it isn't present,
17486 or is something other than @code{t} or @code{ignore}, the default
17487 adaptive scoring rules will be used. If you want to use adaptive
17488 scoring on most groups, you'd set @code{gnus-use-adaptive-scoring} to
17489 @code{t}, and insert an @code{(adapt ignore)} in the groups where you do
17490 not want adaptive scoring. If you only want adaptive scoring in a few
17491 groups, you'd set @code{gnus-use-adaptive-scoring} to @code{nil}, and
17492 insert @code{(adapt t)} in the score files of the groups where you want
17496 All adaptive score entries will go to the file named by this entry. It
17497 will also be applied when entering the group. This atom might be handy
17498 if you want to adapt on several groups at once, using the same adaptive
17499 file for a number of groups.
17502 @cindex local variables
17503 The value of this entry should be a list of @code{(VAR VALUE)} pairs.
17504 Each @var{var} will be made buffer-local to the current summary buffer,
17505 and set to the value specified. This is a convenient, if somewhat
17506 strange, way of setting variables in some groups if you don't like hooks
17507 much. Note that the @var{value} won't be evaluated.
17511 @node Score File Editing
17512 @section Score File Editing
17514 You normally enter all scoring commands from the summary buffer, but you
17515 might feel the urge to edit them by hand as well, so we've supplied you
17516 with a mode for that.
17518 It's simply a slightly customized @code{emacs-lisp} mode, with these
17519 additional commands:
17524 @kindex C-c C-c (Score)
17525 @findex gnus-score-edit-done
17526 Save the changes you have made and return to the summary buffer
17527 (@code{gnus-score-edit-done}).
17530 @kindex C-c C-d (Score)
17531 @findex gnus-score-edit-insert-date
17532 Insert the current date in numerical format
17533 (@code{gnus-score-edit-insert-date}). This is really the day number, if
17534 you were wondering.
17537 @kindex C-c C-p (Score)
17538 @findex gnus-score-pretty-print
17539 The adaptive score files are saved in an unformatted fashion. If you
17540 intend to read one of these files, you want to @dfn{pretty print} it
17541 first. This command (@code{gnus-score-pretty-print}) does that for
17546 Type @kbd{M-x gnus-score-mode} to use this mode.
17548 @vindex gnus-score-mode-hook
17549 @code{gnus-score-menu-hook} is run in score mode buffers.
17551 In the summary buffer you can use commands like @kbd{V f} and @kbd{V
17552 e} to begin editing score files.
17555 @node Adaptive Scoring
17556 @section Adaptive Scoring
17557 @cindex adaptive scoring
17559 If all this scoring is getting you down, Gnus has a way of making it all
17560 happen automatically---as if by magic. Or rather, as if by artificial
17561 stupidity, to be precise.
17563 @vindex gnus-use-adaptive-scoring
17564 When you read an article, or mark an article as read, or kill an
17565 article, you leave marks behind. On exit from the group, Gnus can sniff
17566 these marks and add score elements depending on what marks it finds.
17567 You turn on this ability by setting @code{gnus-use-adaptive-scoring} to
17568 @code{t} or @code{(line)}. If you want score adaptively on separate
17569 words appearing in the subjects, you should set this variable to
17570 @code{(word)}. If you want to use both adaptive methods, set this
17571 variable to @code{(word line)}.
17573 @vindex gnus-default-adaptive-score-alist
17574 To give you complete control over the scoring process, you can customize
17575 the @code{gnus-default-adaptive-score-alist} variable. For instance, it
17576 might look something like this:
17579 (setq gnus-default-adaptive-score-alist
17580 '((gnus-unread-mark)
17581 (gnus-ticked-mark (from 4))
17582 (gnus-dormant-mark (from 5))
17583 (gnus-del-mark (from -4) (subject -1))
17584 (gnus-read-mark (from 4) (subject 2))
17585 (gnus-expirable-mark (from -1) (subject -1))
17586 (gnus-killed-mark (from -1) (subject -3))
17587 (gnus-kill-file-mark)
17588 (gnus-ancient-mark)
17589 (gnus-low-score-mark)
17590 (gnus-catchup-mark (from -1) (subject -1))))
17593 As you see, each element in this alist has a mark as a key (either a
17594 variable name or a ``real'' mark---a character). Following this key is
17595 a arbitrary number of header/score pairs. If there are no header/score
17596 pairs following the key, no adaptive scoring will be done on articles
17597 that have that key as the article mark. For instance, articles with
17598 @code{gnus-unread-mark} in the example above will not get adaptive score
17601 Each article can have only one mark, so just a single of these rules
17602 will be applied to each article.
17604 To take @code{gnus-del-mark} as an example---this alist says that all
17605 articles that have that mark (i.e., are marked with @samp{D}) will have a
17606 score entry added to lower based on the @code{From} header by -4, and
17607 lowered by @code{Subject} by -1. Change this to fit your prejudices.
17609 If you have marked 10 articles with the same subject with
17610 @code{gnus-del-mark}, the rule for that mark will be applied ten times.
17611 That means that that subject will get a score of ten times -1, which
17612 should be, unless I'm much mistaken, -10.
17614 If you have auto-expirable (mail) groups (@pxref{Expiring Mail}), all
17615 the read articles will be marked with the @samp{E} mark. This'll
17616 probably make adaptive scoring slightly impossible, so auto-expiring and
17617 adaptive scoring doesn't really mix very well.
17619 The headers you can score on are @code{from}, @code{subject},
17620 @code{message-id}, @code{references}, @code{xref}, @code{lines},
17621 @code{chars} and @code{date}. In addition, you can score on
17622 @code{followup}, which will create an adaptive score entry that matches
17623 on the @code{References} header using the @code{Message-ID} of the
17624 current article, thereby matching the following thread.
17626 You can also score on @code{thread}, which will try to score all
17627 articles that appear in a thread. @code{thread} matches uses a
17628 @code{Message-ID} to match on the @code{References} header of the
17629 article. If the match is made, the @code{Message-ID} of the article is
17630 added to the @code{thread} rule. (Think about it. I'd recommend two
17631 aspirins afterwards.)
17633 If you use this scheme, you should set the score file atom @code{mark}
17634 to something small---like -300, perhaps, to avoid having small random
17635 changes result in articles getting marked as read.
17637 After using adaptive scoring for a week or so, Gnus should start to
17638 become properly trained and enhance the authors you like best, and kill
17639 the authors you like least, without you having to say so explicitly.
17641 You can control what groups the adaptive scoring is to be performed on
17642 by using the score files (@pxref{Score File Format}). This will also
17643 let you use different rules in different groups.
17645 @vindex gnus-adaptive-file-suffix
17646 The adaptive score entries will be put into a file where the name is the
17647 group name with @code{gnus-adaptive-file-suffix} appended. The default
17650 @vindex gnus-score-exact-adapt-limit
17651 When doing adaptive scoring, substring or fuzzy matching would probably
17652 give you the best results in most cases. However, if the header one
17653 matches is short, the possibility for false positives is great, so if
17654 the length of the match is less than
17655 @code{gnus-score-exact-adapt-limit}, exact matching will be used. If
17656 this variable is @code{nil}, exact matching will always be used to avoid
17659 @vindex gnus-default-adaptive-word-score-alist
17660 As mentioned above, you can adapt either on individual words or entire
17661 headers. If you adapt on words, the
17662 @code{gnus-default-adaptive-word-score-alist} variable says what score
17663 each instance of a word should add given a mark.
17666 (setq gnus-default-adaptive-word-score-alist
17667 `((,gnus-read-mark . 30)
17668 (,gnus-catchup-mark . -10)
17669 (,gnus-killed-mark . -20)
17670 (,gnus-del-mark . -15)))
17673 This is the default value. If you have adaption on words enabled, every
17674 word that appears in subjects of articles marked with
17675 @code{gnus-read-mark} will result in a score rule that increase the
17676 score with 30 points.
17678 @vindex gnus-default-ignored-adaptive-words
17679 @vindex gnus-ignored-adaptive-words
17680 Words that appear in the @code{gnus-default-ignored-adaptive-words} list
17681 will be ignored. If you wish to add more words to be ignored, use the
17682 @code{gnus-ignored-adaptive-words} list instead.
17684 @vindex gnus-adaptive-word-length-limit
17685 Some may feel that short words shouldn't count when doing adaptive
17686 scoring. If so, you may set @code{gnus-adaptive-word-length-limit} to
17687 an integer. Words shorter than this number will be ignored. This
17688 variable defaults til @code{nil}.
17690 @vindex gnus-adaptive-word-syntax-table
17691 When the scoring is done, @code{gnus-adaptive-word-syntax-table} is the
17692 syntax table in effect. It is similar to the standard syntax table, but
17693 it considers numbers to be non-word-constituent characters.
17695 @vindex gnus-adaptive-word-minimum
17696 If @code{gnus-adaptive-word-minimum} is set to a number, the adaptive
17697 word scoring process will never bring down the score of an article to
17698 below this number. The default is @code{nil}.
17700 @vindex gnus-adaptive-word-no-group-words
17701 If @code{gnus-adaptive-word-no-group-words} is set to @code{t}, gnus
17702 won't adaptively word score any of the words in the group name. Useful
17703 for groups like @samp{comp.editors.emacs}, where most of the subject
17704 lines contain the word @samp{emacs}.
17706 After using this scheme for a while, it might be nice to write a
17707 @code{gnus-psychoanalyze-user} command to go through the rules and see
17708 what words you like and what words you don't like. Or perhaps not.
17710 Note that the adaptive word scoring thing is highly experimental and is
17711 likely to change in the future. Initial impressions seem to indicate
17712 that it's totally useless as it stands. Some more work (involving more
17713 rigorous statistical methods) will have to be done to make this useful.
17716 @node Home Score File
17717 @section Home Score File
17719 The score file where new score file entries will go is called the
17720 @dfn{home score file}. This is normally (and by default) the score file
17721 for the group itself. For instance, the home score file for
17722 @samp{gnu.emacs.gnus} is @file{gnu.emacs.gnus.SCORE}.
17724 However, this may not be what you want. It is often convenient to share
17725 a common home score file among many groups---all @samp{emacs} groups
17726 could perhaps use the same home score file.
17728 @vindex gnus-home-score-file
17729 The variable that controls this is @code{gnus-home-score-file}. It can
17734 A string. Then this file will be used as the home score file for all
17738 A function. The result of this function will be used as the home score
17739 file. The function will be called with the name of the group as the
17743 A list. The elements in this list can be:
17747 @code{(@var{regexp} @var{file-name})}. If the @var{regexp} matches the
17748 group name, the @var{file-name} will be used as the home score file.
17751 A function. If the function returns non-nil, the result will be used as
17752 the home score file.
17755 A string. Use the string as the home score file.
17758 The list will be traversed from the beginning towards the end looking
17763 So, if you want to use just a single score file, you could say:
17766 (setq gnus-home-score-file
17767 "my-total-score-file.SCORE")
17770 If you want to use @file{gnu.SCORE} for all @samp{gnu} groups and
17771 @file{rec.SCORE} for all @samp{rec} groups (and so on), you can say:
17773 @findex gnus-hierarchial-home-score-file
17775 (setq gnus-home-score-file
17776 'gnus-hierarchial-home-score-file)
17779 This is a ready-made function provided for your convenience.
17780 Other functions include
17783 @item gnus-current-home-score-file
17784 @findex gnus-current-home-score-file
17785 Return the ``current'' regular score file. This will make scoring
17786 commands add entry to the ``innermost'' matching score file.
17790 If you want to have one score file for the @samp{emacs} groups and
17791 another for the @samp{comp} groups, while letting all other groups use
17792 their own home score files:
17795 (setq gnus-home-score-file
17796 ;; All groups that match the regexp "\\.emacs"
17797 '(("\\.emacs" "emacs.SCORE")
17798 ;; All the comp groups in one score file
17799 ("^comp" "comp.SCORE")))
17802 @vindex gnus-home-adapt-file
17803 @code{gnus-home-adapt-file} works exactly the same way as
17804 @code{gnus-home-score-file}, but says what the home adaptive score file
17805 is instead. All new adaptive file entries will go into the file
17806 specified by this variable, and the same syntax is allowed.
17808 In addition to using @code{gnus-home-score-file} and
17809 @code{gnus-home-adapt-file}, you can also use group parameters
17810 (@pxref{Group Parameters}) and topic parameters (@pxref{Topic
17811 Parameters}) to achieve much the same. Group and topic parameters take
17812 precedence over this variable.
17815 @node Followups To Yourself
17816 @section Followups To Yourself
17818 Gnus offers two commands for picking out the @code{Message-ID} header in
17819 the current buffer. Gnus will then add a score rule that scores using
17820 this @code{Message-ID} on the @code{References} header of other
17821 articles. This will, in effect, increase the score of all articles that
17822 respond to the article in the current buffer. Quite useful if you want
17823 to easily note when people answer what you've said.
17827 @item gnus-score-followup-article
17828 @findex gnus-score-followup-article
17829 This will add a score to articles that directly follow up your own
17832 @item gnus-score-followup-thread
17833 @findex gnus-score-followup-thread
17834 This will add a score to all articles that appear in a thread ``below''
17838 @vindex message-sent-hook
17839 These two functions are both primarily meant to be used in hooks like
17840 @code{message-sent-hook}, like this:
17842 (add-hook 'message-sent-hook 'gnus-score-followup-thread)
17846 If you look closely at your own @code{Message-ID}, you'll notice that
17847 the first two or three characters are always the same. Here's two of
17851 <x6u3u47icf.fsf@@eyesore.no>
17852 <x6sp9o7ibw.fsf@@eyesore.no>
17855 So ``my'' ident on this machine is @samp{x6}. This can be
17856 exploited---the following rule will raise the score on all followups to
17861 ("<x6[0-9a-z]+\\.fsf\\(_-_\\)?@@.*eyesore\\.no>"
17865 Whether it's the first two or first three characters that are ``yours''
17866 is system-dependent.
17869 @node Scoring On Other Headers
17870 @section Scoring On Other Headers
17871 @cindex scoring on other headers
17873 Gnus is quite fast when scoring the ``traditional''
17874 headers---@samp{From}, @samp{Subject} and so on. However, scoring
17875 other headers requires writing a @code{head} scoring rule, which means
17876 that Gnus has to request every single article from the back end to find
17877 matches. This takes a long time in big groups.
17879 Now, there's not much you can do about this for news groups, but for
17880 mail groups, you have greater control. In the @pxref{To From
17881 Newsgroups} section of the manual, it's explained in greater detail what
17882 this mechanism does, but here's a cookbook example for @code{nnml} on
17883 how to allow scoring on the @samp{To} and @samp{Cc} headers.
17885 Put the following in your @file{.gnus.el} file.
17888 (setq gnus-extra-headers '(To Cc Newsgroups Keywords)
17889 nnmail-extra-headers gnus-extra-headers)
17892 Restart Gnus and rebuild your @code{nnml} overview files with the
17893 @kbd{M-x nnml-generate-nov-databases} command. This will take a long
17894 time if you have much mail.
17896 Now you can score on @samp{To} and @samp{Cc} as ``extra headers'' like
17897 so: @kbd{I e s p To RET <your name> RET}.
17903 @section Scoring Tips
17904 @cindex scoring tips
17910 @cindex scoring crossposts
17911 If you want to lower the score of crossposts, the line to match on is
17912 the @code{Xref} header.
17914 ("xref" (" talk.politics.misc:" -1000))
17917 @item Multiple crossposts
17918 If you want to lower the score of articles that have been crossposted to
17919 more than, say, 3 groups:
17922 ("[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+"
17926 @item Matching on the body
17927 This is generally not a very good idea---it takes a very long time.
17928 Gnus actually has to fetch each individual article from the server. But
17929 you might want to anyway, I guess. Even though there are three match
17930 keys (@code{Head}, @code{Body} and @code{All}), you should choose one
17931 and stick with it in each score file. If you use any two, each article
17932 will be fetched @emph{twice}. If you want to match a bit on the
17933 @code{Head} and a bit on the @code{Body}, just use @code{All} for all
17936 @item Marking as read
17937 You will probably want to mark articles that have scores below a certain
17938 number as read. This is most easily achieved by putting the following
17939 in your @file{all.SCORE} file:
17943 You may also consider doing something similar with @code{expunge}.
17945 @item Negated character classes
17946 If you say stuff like @code{[^abcd]*}, you may get unexpected results.
17947 That will match newlines, which might lead to, well, The Unknown. Say
17948 @code{[^abcd\n]*} instead.
17952 @node Reverse Scoring
17953 @section Reverse Scoring
17954 @cindex reverse scoring
17956 If you want to keep just articles that have @samp{Sex with Emacs} in the
17957 subject header, and expunge all other articles, you could put something
17958 like this in your score file:
17962 ("Sex with Emacs" 2))
17967 So, you raise all articles that match @samp{Sex with Emacs} and mark the
17968 rest as read, and expunge them to boot.
17971 @node Global Score Files
17972 @section Global Score Files
17973 @cindex global score files
17975 Sure, other newsreaders have ``global kill files''. These are usually
17976 nothing more than a single kill file that applies to all groups, stored
17977 in the user's home directory. Bah! Puny, weak newsreaders!
17979 What I'm talking about here are Global Score Files. Score files from
17980 all over the world, from users everywhere, uniting all nations in one
17981 big, happy score file union! Ange-score! New and untested!
17983 @vindex gnus-global-score-files
17984 All you have to do to use other people's score files is to set the
17985 @code{gnus-global-score-files} variable. One entry for each score file,
17986 or each score file directory. Gnus will decide by itself what score
17987 files are applicable to which group.
17989 To use the score file
17990 @file{/ftp@@ftp.gnus.org:/pub/larsi/ding/score/soc.motss.SCORE} and
17991 all score files in the @file{/ftp@@ftp.some-where:/pub/score} directory,
17995 (setq gnus-global-score-files
17996 '("/ftp@@ftp.gnus.org:/pub/larsi/ding/score/soc.motss.SCORE"
17997 "/ftp@@ftp.some-where:/pub/score/"))
18000 @findex gnus-score-search-global-directories
18002 Simple, eh? Directory names must end with a @samp{/}. These
18003 directories are typically scanned only once during each Gnus session.
18004 If you feel the need to manually re-scan the remote directories, you can
18005 use the @code{gnus-score-search-global-directories} command.
18007 Note that, at present, using this option will slow down group entry
18008 somewhat. (That is---a lot.)
18010 If you want to start maintaining score files for other people to use,
18011 just put your score file up for anonymous ftp and announce it to the
18012 world. Become a retro-moderator! Participate in the retro-moderator
18013 wars sure to ensue, where retro-moderators battle it out for the
18014 sympathy of the people, luring them to use their score files on false
18015 premises! Yay! The net is saved!
18017 Here are some tips for the would-be retro-moderator, off the top of my
18023 Articles heavily crossposted are probably junk.
18025 To lower a single inappropriate article, lower by @code{Message-ID}.
18027 Particularly brilliant authors can be raised on a permanent basis.
18029 Authors that repeatedly post off-charter for the group can safely be
18030 lowered out of existence.
18032 Set the @code{mark} and @code{expunge} atoms to obliterate the nastiest
18033 articles completely.
18036 Use expiring score entries to keep the size of the file down. You
18037 should probably have a long expiry period, though, as some sites keep
18038 old articles for a long time.
18041 ... I wonder whether other newsreaders will support global score files
18042 in the future. @emph{Snicker}. Yup, any day now, newsreaders like Blue
18043 Wave, xrn and 1stReader are bound to implement scoring. Should we start
18044 holding our breath yet?
18048 @section Kill Files
18051 Gnus still supports those pesky old kill files. In fact, the kill file
18052 entries can now be expiring, which is something I wrote before Daniel
18053 Quinlan thought of doing score files, so I've left the code in there.
18055 In short, kill processing is a lot slower (and I do mean @emph{a lot})
18056 than score processing, so it might be a good idea to rewrite your kill
18057 files into score files.
18059 Anyway, a kill file is a normal @code{emacs-lisp} file. You can put any
18060 forms into this file, which means that you can use kill files as some
18061 sort of primitive hook function to be run on group entry, even though
18062 that isn't a very good idea.
18064 Normal kill files look like this:
18067 (gnus-kill "From" "Lars Ingebrigtsen")
18068 (gnus-kill "Subject" "ding")
18072 This will mark every article written by me as read, and remove the
18073 marked articles from the summary buffer. Very useful, you'll agree.
18075 Other programs use a totally different kill file syntax. If Gnus
18076 encounters what looks like a @code{rn} kill file, it will take a stab at
18079 Two summary functions for editing a GNUS kill file:
18084 @kindex M-k (Summary)
18085 @findex gnus-summary-edit-local-kill
18086 Edit this group's kill file (@code{gnus-summary-edit-local-kill}).
18089 @kindex M-K (Summary)
18090 @findex gnus-summary-edit-global-kill
18091 Edit the general kill file (@code{gnus-summary-edit-global-kill}).
18094 Two group mode functions for editing the kill files:
18099 @kindex M-k (Group)
18100 @findex gnus-group-edit-local-kill
18101 Edit this group's kill file (@code{gnus-group-edit-local-kill}).
18104 @kindex M-K (Group)
18105 @findex gnus-group-edit-global-kill
18106 Edit the general kill file (@code{gnus-group-edit-global-kill}).
18109 Kill file variables:
18112 @item gnus-kill-file-name
18113 @vindex gnus-kill-file-name
18114 A kill file for the group @samp{soc.motss} is normally called
18115 @file{soc.motss.KILL}. The suffix appended to the group name to get
18116 this file name is detailed by the @code{gnus-kill-file-name} variable.
18117 The ``global'' kill file (not in the score file sense of ``global'', of
18118 course) is just called @file{KILL}.
18120 @vindex gnus-kill-save-kill-file
18121 @item gnus-kill-save-kill-file
18122 If this variable is non-@code{nil}, Gnus will save the
18123 kill file after processing, which is necessary if you use expiring
18126 @item gnus-apply-kill-hook
18127 @vindex gnus-apply-kill-hook
18128 @findex gnus-apply-kill-file-unless-scored
18129 @findex gnus-apply-kill-file
18130 A hook called to apply kill files to a group. It is
18131 @code{(gnus-apply-kill-file)} by default. If you want to ignore the
18132 kill file if you have a score file for the same group, you can set this
18133 hook to @code{(gnus-apply-kill-file-unless-scored)}. If you don't want
18134 kill files to be processed, you should set this variable to @code{nil}.
18136 @item gnus-kill-file-mode-hook
18137 @vindex gnus-kill-file-mode-hook
18138 A hook called in kill-file mode buffers.
18143 @node Converting Kill Files
18144 @section Converting Kill Files
18146 @cindex converting kill files
18148 If you have loads of old kill files, you may want to convert them into
18149 score files. If they are ``regular'', you can use
18150 the @file{gnus-kill-to-score.el} package; if not, you'll have to do it
18153 The kill to score conversion package isn't included in Gnus by default.
18154 You can fetch it from
18155 @uref{http://www.stud.ifi.uio.no/~larsi/ding-various/gnus-kill-to-score.el}.
18157 If your old kill files are very complex---if they contain more
18158 non-@code{gnus-kill} forms than not, you'll have to convert them by
18159 hand. Or just let them be as they are. Gnus will still use them as
18167 GroupLens (@uref{http://www.cs.umn.edu/Research/GroupLens/}) is a
18168 collaborative filtering system that helps you work together with other
18169 people to find the quality news articles out of the huge volume of
18170 news articles generated every day.
18172 To accomplish this the GroupLens system combines your opinions about
18173 articles you have already read with the opinions of others who have done
18174 likewise and gives you a personalized prediction for each unread news
18175 article. Think of GroupLens as a matchmaker. GroupLens watches how you
18176 rate articles, and finds other people that rate articles the same way.
18177 Once it has found some people you agree with it tells you, in the form
18178 of a prediction, what they thought of the article. You can use this
18179 prediction to help you decide whether or not you want to read the
18182 @sc{Note:} Unfortunately the GroupLens system seems to have shut down,
18183 so this section is mostly of historical interest.
18186 * Using GroupLens:: How to make Gnus use GroupLens.
18187 * Rating Articles:: Letting GroupLens know how you rate articles.
18188 * Displaying Predictions:: Displaying predictions given by GroupLens.
18189 * GroupLens Variables:: Customizing GroupLens.
18193 @node Using GroupLens
18194 @subsection Using GroupLens
18196 To use GroupLens you must register a pseudonym with your local Better
18198 @uref{http://www.cs.umn.edu/Research/GroupLens/bbb.html} is the only
18199 better bit in town at the moment.
18201 Once you have registered you'll need to set a couple of variables.
18205 @item gnus-use-grouplens
18206 @vindex gnus-use-grouplens
18207 Setting this variable to a non-@code{nil} value will make Gnus hook into
18208 all the relevant GroupLens functions.
18210 @item grouplens-pseudonym
18211 @vindex grouplens-pseudonym
18212 This variable should be set to the pseudonym you got when registering
18213 with the Better Bit Bureau.
18215 @item grouplens-newsgroups
18216 @vindex grouplens-newsgroups
18217 A list of groups that you want to get GroupLens predictions for.
18221 That's the minimum of what you need to get up and running with GroupLens.
18222 Once you've registered, GroupLens will start giving you scores for
18223 articles based on the average of what other people think. But, to get
18224 the real benefit of GroupLens you need to start rating articles
18225 yourself. Then the scores GroupLens gives you will be personalized for
18226 you, based on how the people you usually agree with have already rated.
18229 @node Rating Articles
18230 @subsection Rating Articles
18232 In GroupLens, an article is rated on a scale from 1 to 5, inclusive.
18233 Where 1 means something like this article is a waste of bandwidth and 5
18234 means that the article was really good. The basic question to ask
18235 yourself is, "on a scale from 1 to 5 would I like to see more articles
18238 There are four ways to enter a rating for an article in GroupLens.
18243 @kindex r (GroupLens)
18244 @findex bbb-summary-rate-article
18245 This function will prompt you for a rating on a scale of one to five.
18248 @kindex k (GroupLens)
18249 @findex grouplens-score-thread
18250 This function will prompt you for a rating, and rate all the articles in
18251 the thread. This is really useful for some of those long running giant
18252 threads in rec.humor.
18256 The next two commands, @kbd{n} and @kbd{,} take a numerical prefix to be
18257 the score of the article you're reading.
18262 @kindex n (GroupLens)
18263 @findex grouplens-next-unread-article
18264 Rate the article and go to the next unread article.
18267 @kindex , (GroupLens)
18268 @findex grouplens-best-unread-article
18269 Rate the article and go to the next unread article with the highest score.
18273 If you want to give the current article a score of 4 and then go to the
18274 next article, just type @kbd{4 n}.
18277 @node Displaying Predictions
18278 @subsection Displaying Predictions
18280 GroupLens makes a prediction for you about how much you will like a
18281 news article. The predictions from GroupLens are on a scale from 1 to
18282 5, where 1 is the worst and 5 is the best. You can use the predictions
18283 from GroupLens in one of three ways controlled by the variable
18284 @code{gnus-grouplens-override-scoring}.
18286 @vindex gnus-grouplens-override-scoring
18287 There are three ways to display predictions in grouplens. You may
18288 choose to have the GroupLens scores contribute to, or override the
18289 regular gnus scoring mechanism. override is the default; however, some
18290 people prefer to see the Gnus scores plus the grouplens scores. To get
18291 the separate scoring behavior you need to set
18292 @code{gnus-grouplens-override-scoring} to @code{'separate}. To have the
18293 GroupLens predictions combined with the grouplens scores set it to
18294 @code{'override} and to combine the scores set
18295 @code{gnus-grouplens-override-scoring} to @code{'combine}. When you use
18296 the combine option you will also want to set the values for
18297 @code{grouplens-prediction-offset} and
18298 @code{grouplens-score-scale-factor}.
18300 @vindex grouplens-prediction-display
18301 In either case, GroupLens gives you a few choices for how you would like
18302 to see your predictions displayed. The display of predictions is
18303 controlled by the @code{grouplens-prediction-display} variable.
18305 The following are valid values for that variable.
18308 @item prediction-spot
18309 The higher the prediction, the further to the right an @samp{*} is
18312 @item confidence-interval
18313 A numeric confidence interval.
18315 @item prediction-bar
18316 The higher the prediction, the longer the bar.
18318 @item confidence-bar
18319 Numerical confidence.
18321 @item confidence-spot
18322 The spot gets bigger with more confidence.
18324 @item prediction-num
18325 Plain-old numeric value.
18327 @item confidence-plus-minus
18328 Prediction +/- confidence.
18333 @node GroupLens Variables
18334 @subsection GroupLens Variables
18338 @item gnus-summary-grouplens-line-format
18339 The summary line format used in GroupLens-enhanced summary buffers. It
18340 accepts the same specs as the normal summary line format (@pxref{Summary
18341 Buffer Lines}). The default is @samp{%U%R%z%l%I%(%[%4L: %-23,23n%]%)
18344 @item grouplens-bbb-host
18345 Host running the bbbd server. @samp{grouplens.cs.umn.edu} is the
18348 @item grouplens-bbb-port
18349 Port of the host running the bbbd server. The default is 9000.
18351 @item grouplens-score-offset
18352 Offset the prediction by this value. In other words, subtract the
18353 prediction value by this number to arrive at the effective score. The
18356 @item grouplens-score-scale-factor
18357 This variable allows the user to magnify the effect of GroupLens scores.
18358 The scale factor is applied after the offset. The default is 1.
18363 @node Advanced Scoring
18364 @section Advanced Scoring
18366 Scoring on Subjects and From headers is nice enough, but what if you're
18367 really interested in what a person has to say only when she's talking
18368 about a particular subject? Or what if you really don't want to
18369 read what person A has to say when she's following up to person B, but
18370 want to read what she says when she's following up to person C?
18372 By using advanced scoring rules you may create arbitrarily complex
18376 * Advanced Scoring Syntax:: A definition.
18377 * Advanced Scoring Examples:: What they look like.
18378 * Advanced Scoring Tips:: Getting the most out of it.
18382 @node Advanced Scoring Syntax
18383 @subsection Advanced Scoring Syntax
18385 Ordinary scoring rules have a string as the first element in the rule.
18386 Advanced scoring rules have a list as the first element. The second
18387 element is the score to be applied if the first element evaluated to a
18388 non-@code{nil} value.
18390 These lists may consist of three logical operators, one redirection
18391 operator, and various match operators.
18398 This logical operator will evaluate each of its arguments until it finds
18399 one that evaluates to @code{false}, and then it'll stop. If all arguments
18400 evaluate to @code{true} values, then this operator will return
18405 This logical operator will evaluate each of its arguments until it finds
18406 one that evaluates to @code{true}. If no arguments are @code{true},
18407 then this operator will return @code{false}.
18412 This logical operator only takes a single argument. It returns the
18413 logical negation of the value of its argument.
18417 There is an @dfn{indirection operator} that will make its arguments
18418 apply to the ancestors of the current article being scored. For
18419 instance, @code{1-} will make score rules apply to the parent of the
18420 current article. @code{2-} will make score rules apply to the
18421 grandparent of the current article. Alternatively, you can write
18422 @code{^^}, where the number of @code{^}s (carets) says how far back into
18423 the ancestry you want to go.
18425 Finally, we have the match operators. These are the ones that do the
18426 real work. Match operators are header name strings followed by a match
18427 and a match type. A typical match operator looks like @samp{("from"
18428 "Lars Ingebrigtsen" s)}. The header names are the same as when using
18429 simple scoring, and the match types are also the same.
18432 @node Advanced Scoring Examples
18433 @subsection Advanced Scoring Examples
18435 Please note that the following examples are score file rules. To
18436 make a complete score file from them, surround them with another pair
18439 Let's say you want to increase the score of articles written by Lars
18440 when he's talking about Gnus:
18444 ("from" "Lars Ingebrigtsen")
18445 ("subject" "Gnus"))
18451 When he writes long articles, he sometimes has something nice to say:
18455 ("from" "Lars Ingebrigtsen")
18462 However, when he responds to things written by Reig Eigil Logge, you
18463 really don't want to read what he's written:
18467 ("from" "Lars Ingebrigtsen")
18468 (1- ("from" "Reig Eigir Logge")))
18472 Everybody that follows up Redmondo when he writes about disappearing
18473 socks should have their scores raised, but only when they talk about
18474 white socks. However, when Lars talks about socks, it's usually not
18481 ("from" "redmondo@@.*no" r)
18482 ("body" "disappearing.*socks" t)))
18483 (! ("from" "Lars Ingebrigtsen"))
18484 ("body" "white.*socks"))
18488 The possibilities are endless.
18491 @node Advanced Scoring Tips
18492 @subsection Advanced Scoring Tips
18494 The @code{&} and @code{|} logical operators do short-circuit logic.
18495 That is, they stop processing their arguments when it's clear what the
18496 result of the operation will be. For instance, if one of the arguments
18497 of an @code{&} evaluates to @code{false}, there's no point in evaluating
18498 the rest of the arguments. This means that you should put slow matches
18499 (@samp{body}, @samp{header}) last and quick matches (@samp{from},
18500 @samp{subject}) first.
18502 The indirection arguments (@code{1-} and so on) will make their
18503 arguments work on previous generations of the thread. If you say
18514 Then that means "score on the from header of the grandparent of the
18515 current article". An indirection is quite fast, but it's better to say:
18521 ("subject" "Gnus")))
18528 (1- ("from" "Lars"))
18529 (1- ("subject" "Gnus")))
18534 @section Score Decays
18535 @cindex score decays
18538 You may find that your scores have a tendency to grow without
18539 bounds, especially if you're using adaptive scoring. If scores get too
18540 big, they lose all meaning---they simply max out and it's difficult to
18541 use them in any sensible way.
18543 @vindex gnus-decay-scores
18544 @findex gnus-decay-score
18545 @vindex gnus-decay-score-function
18546 Gnus provides a mechanism for decaying scores to help with this problem.
18547 When score files are loaded and @code{gnus-decay-scores} is
18548 non-@code{nil}, Gnus will run the score files through the decaying
18549 mechanism thereby lowering the scores of all non-permanent score rules.
18550 The decay itself if performed by the @code{gnus-decay-score-function}
18551 function, which is @code{gnus-decay-score} by default. Here's the
18552 definition of that function:
18555 (defun gnus-decay-score (score)
18557 This is done according to `gnus-score-decay-constant'
18558 and `gnus-score-decay-scale'."
18561 (* (if (< score 0) 1 -1)
18563 (max gnus-score-decay-constant
18565 gnus-score-decay-scale)))))))
18568 @vindex gnus-score-decay-scale
18569 @vindex gnus-score-decay-constant
18570 @code{gnus-score-decay-constant} is 3 by default and
18571 @code{gnus-score-decay-scale} is 0.05. This should cause the following:
18575 Scores between -3 and 3 will be set to 0 when this function is called.
18578 Scores with magnitudes between 3 and 60 will be shrunk by 3.
18581 Scores with magnitudes greater than 60 will be shrunk by 5% of the
18585 If you don't like this decay function, write your own. It is called
18586 with the score to be decayed as its only parameter, and it should return
18587 the new score, which should be an integer.
18589 Gnus will try to decay scores once a day. If you haven't run Gnus for
18590 four days, Gnus will decay the scores four times, for instance.
18595 @include message.texi
18596 @chapter Emacs MIME
18597 @include emacs-mime.texi
18599 @include sieve.texi
18607 * Process/Prefix:: A convention used by many treatment commands.
18608 * Interactive:: Making Gnus ask you many questions.
18609 * Symbolic Prefixes:: How to supply some Gnus functions with options.
18610 * Formatting Variables:: You can specify what buffers should look like.
18611 * Window Layout:: Configuring the Gnus buffer windows.
18612 * Faces and Fonts:: How to change how faces look.
18613 * Compilation:: How to speed Gnus up.
18614 * Mode Lines:: Displaying information in the mode lines.
18615 * Highlighting and Menus:: Making buffers look all nice and cozy.
18616 * Buttons:: Get tendinitis in ten easy steps!
18617 * Daemons:: Gnus can do things behind your back.
18618 * NoCeM:: How to avoid spam and other fatty foods.
18619 * Undo:: Some actions can be undone.
18620 * Predicate Specifiers:: Specifying predicates.
18621 * Moderation:: What to do if you're a moderator.
18622 * Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
18623 * Fuzzy Matching:: What's the big fuzz?
18624 * Thwarting Email Spam:: A how-to on avoiding unsolicited commercial email.
18625 * Various Various:: Things that are really various.
18629 @node Process/Prefix
18630 @section Process/Prefix
18631 @cindex process/prefix convention
18633 Many functions, among them functions for moving, decoding and saving
18634 articles, use what is known as the @dfn{Process/Prefix convention}.
18636 This is a method for figuring out what articles the user wants the
18637 command to be performed on.
18641 If the numeric prefix is N, perform the operation on the next N
18642 articles, starting with the current one. If the numeric prefix is
18643 negative, perform the operation on the previous N articles, starting
18644 with the current one.
18646 @vindex transient-mark-mode
18647 If @code{transient-mark-mode} in non-@code{nil} and the region is
18648 active, all articles in the region will be worked upon.
18650 If there is no numeric prefix, but some articles are marked with the
18651 process mark, perform the operation on the articles marked with
18654 If there is neither a numeric prefix nor any articles marked with the
18655 process mark, just perform the operation on the current article.
18657 Quite simple, really, but it needs to be made clear so that surprises
18660 Commands that react to the process mark will push the current list of
18661 process marked articles onto a stack and will then clear all process
18662 marked articles. You can restore the previous configuration with the
18663 @kbd{M P y} command (@pxref{Setting Process Marks}).
18665 @vindex gnus-summary-goto-unread
18666 One thing that seems to shock & horrify lots of people is that, for
18667 instance, @kbd{3 d} does exactly the same as @kbd{d} @kbd{d} @kbd{d}.
18668 Since each @kbd{d} (which marks the current article as read) by default
18669 goes to the next unread article after marking, this means that @kbd{3 d}
18670 will mark the next three unread articles as read, no matter what the
18671 summary buffer looks like. Set @code{gnus-summary-goto-unread} to
18672 @code{nil} for a more straightforward action.
18674 Many commands do not use the process/prefix convention. All commands
18675 that do explicitly say so in this manual. To apply the process/prefix
18676 convention to commands that do not use it, you can use the @kbd{M-&}
18677 command. For instance, to mark all the articles in the group as
18678 expirable, you could say `M P b M-& E'.
18682 @section Interactive
18683 @cindex interaction
18687 @item gnus-novice-user
18688 @vindex gnus-novice-user
18689 If this variable is non-@code{nil}, you are either a newcomer to the
18690 World of Usenet, or you are very cautious, which is a nice thing to be,
18691 really. You will be given questions of the type ``Are you sure you want
18692 to do this?'' before doing anything dangerous. This is @code{t} by
18695 @item gnus-expert-user
18696 @vindex gnus-expert-user
18697 If this variable is non-@code{nil}, you will seldom be asked any
18698 questions by Gnus. It will simply assume you know what you're doing, no
18699 matter how strange.
18701 @item gnus-interactive-catchup
18702 @vindex gnus-interactive-catchup
18703 Require confirmation before catching up a group if non-@code{nil}. It
18704 is @code{t} by default.
18706 @item gnus-interactive-exit
18707 @vindex gnus-interactive-exit
18708 Require confirmation before exiting Gnus. This variable is @code{t} by
18713 @node Symbolic Prefixes
18714 @section Symbolic Prefixes
18715 @cindex symbolic prefixes
18717 Quite a lot of Emacs commands react to the (numeric) prefix. For
18718 instance, @kbd{C-u 4 C-f} moves point four characters forward, and
18719 @kbd{C-u 9 0 0 I s s p} adds a permanent @code{Subject} substring score
18720 rule of 900 to the current article.
18722 This is all nice and well, but what if you want to give a command some
18723 additional information? Well, what most commands do is interpret the
18724 ``raw'' prefix in some special way. @kbd{C-u 0 C-x C-s} means that one
18725 doesn't want a backup file to be created when saving the current buffer,
18726 for instance. But what if you want to save without making a backup
18727 file, and you want Emacs to flash lights and play a nice tune at the
18728 same time? You can't, and you're probably perfectly happy that way.
18730 @kindex M-i (Summary)
18731 @findex gnus-symbolic-argument
18732 I'm not, so I've added a second prefix---the @dfn{symbolic prefix}. The
18733 prefix key is @kbd{M-i} (@code{gnus-symbolic-argument}), and the next
18734 character typed in is the value. You can stack as many @kbd{M-i}
18735 prefixes as you want. @kbd{M-i a C-M-u} means ``feed the @kbd{C-M-u}
18736 command the symbolic prefix @code{a}''. @kbd{M-i a M-i b C-M-u} means
18737 ``feed the @kbd{C-M-u} command the symbolic prefixes @code{a} and
18738 @code{b}''. You get the drift.
18740 Typing in symbolic prefixes to commands that don't accept them doesn't
18741 hurt, but it doesn't do any good either. Currently not many Gnus
18742 functions make use of the symbolic prefix.
18744 If you're interested in how Gnus implements this, @pxref{Extended
18748 @node Formatting Variables
18749 @section Formatting Variables
18750 @cindex formatting variables
18752 Throughout this manual you've probably noticed lots of variables called
18753 things like @code{gnus-group-line-format} and
18754 @code{gnus-summary-mode-line-format}. These control how Gnus is to
18755 output lines in the various buffers. There's quite a lot of them.
18756 Fortunately, they all use the same syntax, so there's not that much to
18759 Here's an example format spec (from the group buffer): @samp{%M%S%5y:
18760 %(%g%)\n}. We see that it is indeed extremely ugly, and that there are
18761 lots of percentages everywhere.
18764 * Formatting Basics:: A formatting variable is basically a format string.
18765 * Mode Line Formatting:: Some rules about mode line formatting variables.
18766 * Advanced Formatting:: Modifying output in various ways.
18767 * User-Defined Specs:: Having Gnus call your own functions.
18768 * Formatting Fonts:: Making the formatting look colorful and nice.
18769 * Positioning Point:: Moving point to a position after an operation.
18770 * Tabulation:: Tabulating your output.
18771 * Wide Characters:: Dealing with wide characters.
18774 Currently Gnus uses the following formatting variables:
18775 @code{gnus-group-line-format}, @code{gnus-summary-line-format},
18776 @code{gnus-server-line-format}, @code{gnus-topic-line-format},
18777 @code{gnus-group-mode-line-format},
18778 @code{gnus-summary-mode-line-format},
18779 @code{gnus-article-mode-line-format},
18780 @code{gnus-server-mode-line-format}, and
18781 @code{gnus-summary-pick-line-format}.
18783 All these format variables can also be arbitrary elisp forms. In that
18784 case, they will be @code{eval}ed to insert the required lines.
18786 @kindex M-x gnus-update-format
18787 @findex gnus-update-format
18788 Gnus includes a command to help you while creating your own format
18789 specs. @kbd{M-x gnus-update-format} will @code{eval} the current form,
18790 update the spec in question and pop you to a buffer where you can
18791 examine the resulting lisp code to be run to generate the line.
18795 @node Formatting Basics
18796 @subsection Formatting Basics
18798 Each @samp{%} element will be replaced by some string or other when the
18799 buffer in question is generated. @samp{%5y} means ``insert the @samp{y}
18800 spec, and pad with spaces to get a 5-character field''.
18802 As with normal C and Emacs Lisp formatting strings, the numerical
18803 modifier between the @samp{%} and the formatting type character will
18804 @dfn{pad} the output so that it is always at least that long.
18805 @samp{%5y} will make the field always (at least) five characters wide by
18806 padding with spaces to the left. If you say @samp{%-5y}, it will pad to
18809 You may also wish to limit the length of the field to protect against
18810 particularly wide values. For that you can say @samp{%4,6y}, which
18811 means that the field will never be more than 6 characters wide and never
18812 less than 4 characters wide.
18814 Also Gnus supports some extended format specifications, such as
18815 @samp{%&user-date;}.
18818 @node Mode Line Formatting
18819 @subsection Mode Line Formatting
18821 Mode line formatting variables (e.g.,
18822 @code{gnus-summary-mode-line-format}) follow the same rules as other,
18823 buffer line oriented formatting variables (@pxref{Formatting Basics})
18824 with the following two differences:
18829 There must be no newline (@samp{\n}) at the end.
18832 The special @samp{%%b} spec can be used to display the buffer name.
18833 Well, it's no spec at all, really---@samp{%%} is just a way to quote
18834 @samp{%} to allow it to pass through the formatting machinery unmangled,
18835 so that Emacs receives @samp{%b}, which is something the Emacs mode line
18836 display interprets to mean ``show the buffer name''. For a full list of
18837 mode line specs Emacs understands, see the documentation of the
18838 @code{mode-line-format} variable.
18843 @node Advanced Formatting
18844 @subsection Advanced Formatting
18846 It is frequently useful to post-process the fields in some way.
18847 Padding, limiting, cutting off parts and suppressing certain values can
18848 be achieved by using @dfn{tilde modifiers}. A typical tilde spec might
18849 look like @samp{%~(cut 3)~(ignore "0")y}.
18851 These are the valid modifiers:
18856 Pad the field to the left with spaces until it reaches the required
18860 Pad the field to the right with spaces until it reaches the required
18865 Cut off characters from the left until it reaches the specified length.
18868 Cut off characters from the right until it reaches the specified
18873 Cut off the specified number of characters from the left.
18876 Cut off the specified number of characters from the right.
18879 Return an empty string if the field is equal to the specified value.
18882 Use the specified form as the field value when the @samp{@@} spec is
18888 "~(form (current-time-string))@@"
18893 Let's take an example. The @samp{%o} spec in the summary mode lines
18894 will return a date in compact ISO8601 format---@samp{19960809T230410}.
18895 This is quite a mouthful, so we want to shave off the century number and
18896 the time, leaving us with a six-character date. That would be
18897 @samp{%~(cut-left 2)~(max-right 6)~(pad 6)o}. (Cutting is done before
18898 maxing, and we need the padding to ensure that the date is never less
18899 than 6 characters to make it look nice in columns.)
18901 Ignoring is done first; then cutting; then maxing; and then as the very
18902 last operation, padding.
18904 If you use lots of these advanced thingies, you'll find that Gnus gets
18905 quite slow. This can be helped enormously by running @kbd{M-x
18906 gnus-compile} when you are satisfied with the look of your lines.
18907 @xref{Compilation}.
18910 @node User-Defined Specs
18911 @subsection User-Defined Specs
18913 All the specs allow for inserting user defined specifiers---@samp{u}.
18914 The next character in the format string should be a letter. Gnus
18915 will call the function @code{gnus-user-format-function-}@samp{X}, where
18916 @samp{X} is the letter following @samp{%u}. The function will be passed
18917 a single parameter---what the parameter means depends on what buffer
18918 it's being called from. The function should return a string, which will
18919 be inserted into the buffer just like information from any other
18920 specifier. This function may also be called with dummy values, so it
18921 should protect against that.
18923 Also Gnus supports extended user-defined specs, such as @samp{%u&foo;}.
18924 Gnus will call the function @code{gnus-user-format-function-}@samp{foo}.
18926 You can also use tilde modifiers (@pxref{Advanced Formatting} to achieve
18927 much the same without defining new functions. Here's an example:
18928 @samp{%~(form (count-lines (point-min) (point)))@@}. The form
18929 given here will be evaluated to yield the current line number, and then
18933 @node Formatting Fonts
18934 @subsection Formatting Fonts
18936 There are specs for highlighting, and these are shared by all the format
18937 variables. Text inside the @samp{%(} and @samp{%)} specifiers will get
18938 the special @code{mouse-face} property set, which means that it will be
18939 highlighted (with @code{gnus-mouse-face}) when you put the mouse pointer
18942 Text inside the @samp{%@{} and @samp{%@}} specifiers will have their
18943 normal faces set using @code{gnus-face-0}, which is @code{bold} by
18944 default. If you say @samp{%1@{}, you'll get @code{gnus-face-1} instead,
18945 and so on. Create as many faces as you wish. The same goes for the
18946 @code{mouse-face} specs---you can say @samp{%3(hello%)} to have
18947 @samp{hello} mouse-highlighted with @code{gnus-mouse-face-3}.
18949 Text inside the @samp{%<} and @samp{%>} specifiers will get the special
18950 @code{balloon-help} property set to @code{gnus-balloon-face-0}. If you
18951 say @samp{%1<}, you'll get @code{gnus-balloon-face-1} and so on. The
18952 @code{gnus-balloon-face-*} variables should be either strings or symbols
18953 naming functions that return a string. Under @code{balloon-help-mode},
18954 when the mouse passes over text with this property set, a balloon window
18955 will appear and display the string. Please refer to the doc string of
18956 @code{balloon-help-mode} for more information on this.
18958 Here's an alternative recipe for the group buffer:
18961 ;; Create three face types.
18962 (setq gnus-face-1 'bold)
18963 (setq gnus-face-3 'italic)
18965 ;; We want the article count to be in
18966 ;; a bold and green face. So we create
18967 ;; a new face called `my-green-bold'.
18968 (copy-face 'bold 'my-green-bold)
18970 (set-face-foreground 'my-green-bold "ForestGreen")
18971 (setq gnus-face-2 'my-green-bold)
18973 ;; Set the new & fancy format.
18974 (setq gnus-group-line-format
18975 "%M%S%3@{%5y%@}%2[:%] %(%1@{%g%@}%)\n")
18978 I'm sure you'll be able to use this scheme to create totally unreadable
18979 and extremely vulgar displays. Have fun!
18981 Note that the @samp{%(} specs (and friends) do not make any sense on the
18982 mode-line variables.
18984 @node Positioning Point
18985 @subsection Positioning Point
18987 Gnus usually moves point to a pre-defined place on each line in most
18988 buffers. By default, point move to the first colon character on the
18989 line. You can customize this behaviour in three different ways.
18991 You can move the colon character to somewhere else on the line.
18993 @findex gnus-goto-colon
18994 You can redefine the function that moves the point to the colon. The
18995 function is called @code{gnus-goto-colon}.
18997 But perhaps the most convenient way to deal with this, if you don't want
18998 to have a colon in your line, is to use the @samp{%C} specifier. If you
18999 put a @samp{%C} somewhere in your format line definition, Gnus will
19004 @subsection Tabulation
19006 You can usually line up your displays by padding and cutting your
19007 strings. However, when combining various strings of different size, it
19008 can often be more convenient to just output the strings, and then worry
19009 about lining up the following text afterwards.
19011 To do that, Gnus supplies tabulator specs--@samp{%=}. There are two
19012 different types---@dfn{hard tabulators} and @dfn{soft tabulators}.
19014 @samp{%50=} will insert space characters to pad the line up to column
19015 50. If the text is already past column 50, nothing will be inserted.
19016 This is the soft tabulator.
19018 @samp{%-50=} will insert space characters to pad the line up to column
19019 50. If the text is already past column 50, the excess text past column
19020 50 will be removed. This is the hard tabulator.
19023 @node Wide Characters
19024 @subsection Wide Characters
19026 Proportional fonts in most countries have characters of the same width.
19027 Some countries, however, use Latin characters mixed with wider
19028 characters---most notable East Asian countries.
19030 The problem is that when formatting, Gnus assumes that if a string is 10
19031 characters wide, it'll be 10 Latin characters wide on the screen. In
19032 these coutries, that's not true.
19034 @vindex gnus-use-correct-string-widths
19035 To help fix this, you can set @code{gnus-use-correct-string-widths} to
19036 @code{t}. This makes buffer generation slower, but the results will be
19037 prettieer. The default value is @code{t}.
19041 @node Window Layout
19042 @section Window Layout
19043 @cindex window layout
19045 No, there's nothing here about X, so be quiet.
19047 @vindex gnus-use-full-window
19048 If @code{gnus-use-full-window} non-@code{nil}, Gnus will delete all
19049 other windows and occupy the entire Emacs screen by itself. It is
19050 @code{t} by default.
19052 Setting this variable to @code{nil} kinda works, but there are
19053 glitches. Use at your own peril.
19055 @vindex gnus-buffer-configuration
19056 @code{gnus-buffer-configuration} describes how much space each Gnus
19057 buffer should be given. Here's an excerpt of this variable:
19060 ((group (vertical 1.0 (group 1.0 point)
19061 (if gnus-carpal (group-carpal 4))))
19062 (article (vertical 1.0 (summary 0.25 point)
19066 This is an alist. The @dfn{key} is a symbol that names some action or
19067 other. For instance, when displaying the group buffer, the window
19068 configuration function will use @code{group} as the key. A full list of
19069 possible names is listed below.
19071 The @dfn{value} (i.e., the @dfn{split}) says how much space each buffer
19072 should occupy. To take the @code{article} split as an example -
19075 (article (vertical 1.0 (summary 0.25 point)
19079 This @dfn{split} says that the summary buffer should occupy 25% of upper
19080 half of the screen, and that it is placed over the article buffer. As
19081 you may have noticed, 100% + 25% is actually 125% (yup, I saw y'all
19082 reaching for that calculator there). However, the special number
19083 @code{1.0} is used to signal that this buffer should soak up all the
19084 rest of the space available after the rest of the buffers have taken
19085 whatever they need. There should be only one buffer with the @code{1.0}
19086 size spec per split.
19088 Point will be put in the buffer that has the optional third element
19089 @code{point}. In a @code{frame} split, the last subsplit having a leaf
19090 split where the tag @code{frame-focus} is a member (i.e. is the third or
19091 fourth element in the list, depending on whether the @code{point} tag is
19092 present) gets focus.
19094 Here's a more complicated example:
19097 (article (vertical 1.0 (group 4)
19098 (summary 0.25 point)
19099 (if gnus-carpal (summary-carpal 4))
19103 If the size spec is an integer instead of a floating point number,
19104 then that number will be used to say how many lines a buffer should
19105 occupy, not a percentage.
19107 If the @dfn{split} looks like something that can be @code{eval}ed (to be
19108 precise---if the @code{car} of the split is a function or a subr), this
19109 split will be @code{eval}ed. If the result is non-@code{nil}, it will
19110 be used as a split. This means that there will be three buffers if
19111 @code{gnus-carpal} is @code{nil}, and four buffers if @code{gnus-carpal}
19114 Not complicated enough for you? Well, try this on for size:
19117 (article (horizontal 1.0
19122 (summary 0.25 point)
19127 Whoops. Two buffers with the mystery 100% tag. And what's that
19128 @code{horizontal} thingie?
19130 If the first element in one of the split is @code{horizontal}, Gnus will
19131 split the window horizontally, giving you two windows side-by-side.
19132 Inside each of these strips you may carry on all you like in the normal
19133 fashion. The number following @code{horizontal} says what percentage of
19134 the screen is to be given to this strip.
19136 For each split, there @emph{must} be one element that has the 100% tag.
19137 The splitting is never accurate, and this buffer will eat any leftover
19138 lines from the splits.
19140 To be slightly more formal, here's a definition of what a valid split
19144 split = frame | horizontal | vertical | buffer | form
19145 frame = "(frame " size *split ")"
19146 horizontal = "(horizontal " size *split ")"
19147 vertical = "(vertical " size *split ")"
19148 buffer = "(" buf-name " " size *[ "point" ] *[ "frame-focus"] ")"
19149 size = number | frame-params
19150 buf-name = group | article | summary ...
19153 The limitations are that the @code{frame} split can only appear as the
19154 top-level split. @var{form} should be an Emacs Lisp form that should
19155 return a valid split. We see that each split is fully recursive, and
19156 may contain any number of @code{vertical} and @code{horizontal} splits.
19158 @vindex gnus-window-min-width
19159 @vindex gnus-window-min-height
19160 @cindex window height
19161 @cindex window width
19162 Finding the right sizes can be a bit complicated. No window may be less
19163 than @code{gnus-window-min-height} (default 1) characters high, and all
19164 windows must be at least @code{gnus-window-min-width} (default 1)
19165 characters wide. Gnus will try to enforce this before applying the
19166 splits. If you want to use the normal Emacs window width/height limit,
19167 you can just set these two variables to @code{nil}.
19169 If you're not familiar with Emacs terminology, @code{horizontal} and
19170 @code{vertical} splits may work the opposite way of what you'd expect.
19171 Windows inside a @code{horizontal} split are shown side-by-side, and
19172 windows within a @code{vertical} split are shown above each other.
19174 @findex gnus-configure-frame
19175 If you want to experiment with window placement, a good tip is to call
19176 @code{gnus-configure-frame} directly with a split. This is the function
19177 that does all the real work when splitting buffers. Below is a pretty
19178 nonsensical configuration with 5 windows; two for the group buffer and
19179 three for the article buffer. (I said it was nonsensical.) If you
19180 @code{eval} the statement below, you can get an idea of how that would
19181 look straight away, without going through the normal Gnus channels.
19182 Play with it until you're satisfied, and then use
19183 @code{gnus-add-configuration} to add your new creation to the buffer
19184 configuration list.
19187 (gnus-configure-frame
19191 (article 0.3 point))
19199 You might want to have several frames as well. No prob---just use the
19200 @code{frame} split:
19203 (gnus-configure-frame
19206 (summary 0.25 point frame-focus)
19208 (vertical ((height . 5) (width . 15)
19209 (user-position . t)
19210 (left . -1) (top . 1))
19215 This split will result in the familiar summary/article window
19216 configuration in the first (or ``main'') frame, while a small additional
19217 frame will be created where picons will be shown. As you can see,
19218 instead of the normal @code{1.0} top-level spec, each additional split
19219 should have a frame parameter alist as the size spec.
19220 @xref{Frame Parameters, , Frame Parameters, elisp, The GNU Emacs Lisp
19221 Reference Manual}. Under XEmacs, a frame property list will be
19222 accepted, too---for instance, @code{(height 5 width 15 left -1 top 1)}
19224 The list of all possible keys for @code{gnus-buffer-configuration} can
19225 be found in its default value.
19227 Note that the @code{message} key is used for both
19228 @code{gnus-group-mail} and @code{gnus-summary-mail-other-window}. If
19229 it is desirable to distinguish between the two, something like this
19233 (message (horizontal 1.0
19234 (vertical 1.0 (message 1.0 point))
19236 (if (buffer-live-p gnus-summary-buffer)
19241 One common desire for a multiple frame split is to have a separate frame
19242 for composing mail and news while leaving the original frame intact. To
19243 accomplish that, something like the following can be done:
19248 (if (not (buffer-live-p gnus-summary-buffer))
19249 (car (cdr (assoc 'group gnus-buffer-configuration)))
19250 (car (cdr (assoc 'summary gnus-buffer-configuration))))
19251 (vertical ((user-position . t) (top . 1) (left . 1)
19252 (name . "Message"))
19253 (message 1.0 point))))
19256 @findex gnus-add-configuration
19257 Since the @code{gnus-buffer-configuration} variable is so long and
19258 complicated, there's a function you can use to ease changing the config
19259 of a single setting: @code{gnus-add-configuration}. If, for instance,
19260 you want to change the @code{article} setting, you could say:
19263 (gnus-add-configuration
19264 '(article (vertical 1.0
19266 (summary .25 point)
19270 You'd typically stick these @code{gnus-add-configuration} calls in your
19271 @file{.gnus.el} file or in some startup hook---they should be run after
19272 Gnus has been loaded.
19274 @vindex gnus-always-force-window-configuration
19275 If all windows mentioned in the configuration are already visible, Gnus
19276 won't change the window configuration. If you always want to force the
19277 ``right'' window configuration, you can set
19278 @code{gnus-always-force-window-configuration} to non-@code{nil}.
19280 If you're using tree displays (@pxref{Tree Display}), and the tree
19281 window is displayed vertically next to another window, you may also want
19282 to fiddle with @code{gnus-tree-minimize-window} to avoid having the
19285 @subsection Example Window Configurations
19289 Narrow left hand side occupied by group buffer. Right hand side split
19290 between summary buffer (top one-sixth) and article buffer (bottom).
19305 (gnus-add-configuration
19308 (vertical 25 (group 1.0))
19310 (summary 0.16 point)
19313 (gnus-add-configuration
19316 (vertical 25 (group 1.0))
19317 (vertical 1.0 (summary 1.0 point)))))
19323 @node Faces and Fonts
19324 @section Faces and Fonts
19329 Fiddling with fonts and faces used to be very difficult, but these days
19330 it is very simple. You simply say @kbd{M-x customize-face}, pick out
19331 the face you want to alter, and alter it via the standard Customize
19336 @section Compilation
19337 @cindex compilation
19338 @cindex byte-compilation
19340 @findex gnus-compile
19342 Remember all those line format specification variables?
19343 @code{gnus-summary-line-format}, @code{gnus-group-line-format}, and so
19344 on. Now, Gnus will of course heed whatever these variables are, but,
19345 unfortunately, changing them will mean a quite significant slow-down.
19346 (The default values of these variables have byte-compiled functions
19347 associated with them, while the user-generated versions do not, of
19350 To help with this, you can run @kbd{M-x gnus-compile} after you've
19351 fiddled around with the variables and feel that you're (kind of)
19352 satisfied. This will result in the new specs being byte-compiled, and
19353 you'll get top speed again. Gnus will save these compiled specs in the
19354 @file{.newsrc.eld} file. (User-defined functions aren't compiled by
19355 this function, though---you should compile them yourself by sticking
19356 them into the @code{.gnus.el} file and byte-compiling that file.)
19360 @section Mode Lines
19363 @vindex gnus-updated-mode-lines
19364 @code{gnus-updated-mode-lines} says what buffers should keep their mode
19365 lines updated. It is a list of symbols. Supported symbols include
19366 @code{group}, @code{article}, @code{summary}, @code{server},
19367 @code{browse}, and @code{tree}. If the corresponding symbol is present,
19368 Gnus will keep that mode line updated with information that may be
19369 pertinent. If this variable is @code{nil}, screen refresh may be
19372 @cindex display-time
19374 @vindex gnus-mode-non-string-length
19375 By default, Gnus displays information on the current article in the mode
19376 lines of the summary and article buffers. The information Gnus wishes
19377 to display (e.g. the subject of the article) is often longer than the
19378 mode lines, and therefore have to be cut off at some point. The
19379 @code{gnus-mode-non-string-length} variable says how long the other
19380 elements on the line is (i.e., the non-info part). If you put
19381 additional elements on the mode line (e.g. a clock), you should modify
19384 @c Hook written by Francesco Potorti` <pot@cnuce.cnr.it>
19386 (add-hook 'display-time-hook
19387 (lambda () (setq gnus-mode-non-string-length
19389 (if line-number-mode 5 0)
19390 (if column-number-mode 4 0)
19391 (length display-time-string)))))
19394 If this variable is @code{nil} (which is the default), the mode line
19395 strings won't be chopped off, and they won't be padded either. Note
19396 that the default is unlikely to be desirable, as even the percentage
19397 complete in the buffer may be crowded off the mode line; the user should
19398 configure this variable appropriately for her configuration.
19401 @node Highlighting and Menus
19402 @section Highlighting and Menus
19404 @cindex highlighting
19407 @vindex gnus-visual
19408 The @code{gnus-visual} variable controls most of the Gnus-prettifying
19409 aspects. If @code{nil}, Gnus won't attempt to create menus or use fancy
19410 colors or fonts. This will also inhibit loading the @file{gnus-vis.el}
19413 This variable can be a list of visual properties that are enabled. The
19414 following elements are valid, and are all included by default:
19417 @item group-highlight
19418 Do highlights in the group buffer.
19419 @item summary-highlight
19420 Do highlights in the summary buffer.
19421 @item article-highlight
19422 Do highlights in the article buffer.
19424 Turn on highlighting in all buffers.
19426 Create menus in the group buffer.
19428 Create menus in the summary buffers.
19430 Create menus in the article buffer.
19432 Create menus in the browse buffer.
19434 Create menus in the server buffer.
19436 Create menus in the score buffers.
19438 Create menus in all buffers.
19441 So if you only want highlighting in the article buffer and menus in all
19442 buffers, you could say something like:
19445 (setq gnus-visual '(article-highlight menu))
19448 If you want highlighting only and no menus whatsoever, you'd say:
19451 (setq gnus-visual '(highlight))
19454 If @code{gnus-visual} is @code{t}, highlighting and menus will be used
19455 in all Gnus buffers.
19457 Other general variables that influence the look of all buffers include:
19460 @item gnus-mouse-face
19461 @vindex gnus-mouse-face
19462 This is the face (i.e., font) used for mouse highlighting in Gnus. No
19463 mouse highlights will be done if @code{gnus-visual} is @code{nil}.
19467 There are hooks associated with the creation of all the different menus:
19471 @item gnus-article-menu-hook
19472 @vindex gnus-article-menu-hook
19473 Hook called after creating the article mode menu.
19475 @item gnus-group-menu-hook
19476 @vindex gnus-group-menu-hook
19477 Hook called after creating the group mode menu.
19479 @item gnus-summary-menu-hook
19480 @vindex gnus-summary-menu-hook
19481 Hook called after creating the summary mode menu.
19483 @item gnus-server-menu-hook
19484 @vindex gnus-server-menu-hook
19485 Hook called after creating the server mode menu.
19487 @item gnus-browse-menu-hook
19488 @vindex gnus-browse-menu-hook
19489 Hook called after creating the browse mode menu.
19491 @item gnus-score-menu-hook
19492 @vindex gnus-score-menu-hook
19493 Hook called after creating the score mode menu.
19504 Those new-fangled @dfn{mouse} contraptions is very popular with the
19505 young, hep kids who don't want to learn the proper way to do things
19506 these days. Why, I remember way back in the summer of '89, when I was
19507 using Emacs on a Tops 20 system. Three hundred users on one single
19508 machine, and every user was running Simula compilers. Bah!
19512 @vindex gnus-carpal
19513 Well, you can make Gnus display bufferfuls of buttons you can click to
19514 do anything by setting @code{gnus-carpal} to @code{t}. Pretty simple,
19515 really. Tell the chiropractor I sent you.
19520 @item gnus-carpal-mode-hook
19521 @vindex gnus-carpal-mode-hook
19522 Hook run in all carpal mode buffers.
19524 @item gnus-carpal-button-face
19525 @vindex gnus-carpal-button-face
19526 Face used on buttons.
19528 @item gnus-carpal-header-face
19529 @vindex gnus-carpal-header-face
19530 Face used on carpal buffer headers.
19532 @item gnus-carpal-group-buffer-buttons
19533 @vindex gnus-carpal-group-buffer-buttons
19534 Buttons in the group buffer.
19536 @item gnus-carpal-summary-buffer-buttons
19537 @vindex gnus-carpal-summary-buffer-buttons
19538 Buttons in the summary buffer.
19540 @item gnus-carpal-server-buffer-buttons
19541 @vindex gnus-carpal-server-buffer-buttons
19542 Buttons in the server buffer.
19544 @item gnus-carpal-browse-buffer-buttons
19545 @vindex gnus-carpal-browse-buffer-buttons
19546 Buttons in the browse buffer.
19549 All the @code{buttons} variables are lists. The elements in these list
19550 are either cons cells where the @code{car} contains a text to be displayed and
19551 the @code{cdr} contains a function symbol, or a simple string.
19559 Gnus, being larger than any program ever written (allegedly), does lots
19560 of strange stuff that you may wish to have done while you're not
19561 present. For instance, you may want it to check for new mail once in a
19562 while. Or you may want it to close down all connections to all servers
19563 when you leave Emacs idle. And stuff like that.
19565 Gnus will let you do stuff like that by defining various
19566 @dfn{handlers}. Each handler consists of three elements: A
19567 @var{function}, a @var{time}, and an @var{idle} parameter.
19569 Here's an example of a handler that closes connections when Emacs has
19570 been idle for thirty minutes:
19573 (gnus-demon-close-connections nil 30)
19576 Here's a handler that scans for PGP headers every hour when Emacs is
19580 (gnus-demon-scan-pgp 60 t)
19583 This @var{time} parameter and than @var{idle} parameter work together
19584 in a strange, but wonderful fashion. Basically, if @var{idle} is
19585 @code{nil}, then the function will be called every @var{time} minutes.
19587 If @var{idle} is @code{t}, then the function will be called after
19588 @var{time} minutes only if Emacs is idle. So if Emacs is never idle,
19589 the function will never be called. But once Emacs goes idle, the
19590 function will be called every @var{time} minutes.
19592 If @var{idle} is a number and @var{time} is a number, the function will
19593 be called every @var{time} minutes only when Emacs has been idle for
19594 @var{idle} minutes.
19596 If @var{idle} is a number and @var{time} is @code{nil}, the function
19597 will be called once every time Emacs has been idle for @var{idle}
19600 And if @var{time} is a string, it should look like @samp{07:31}, and
19601 the function will then be called once every day somewhere near that
19602 time. Modified by the @var{idle} parameter, of course.
19604 @vindex gnus-demon-timestep
19605 (When I say ``minute'' here, I really mean @code{gnus-demon-timestep}
19606 seconds. This is 60 by default. If you change that variable,
19607 all the timings in the handlers will be affected.)
19609 So, if you want to add a handler, you could put something like this in
19610 your @file{.gnus} file:
19612 @findex gnus-demon-add-handler
19614 (gnus-demon-add-handler 'gnus-demon-close-connections 30 t)
19617 @findex gnus-demon-add-nocem
19618 @findex gnus-demon-add-scanmail
19619 @findex gnus-demon-add-rescan
19620 @findex gnus-demon-add-scan-timestamps
19621 @findex gnus-demon-add-disconnection
19622 Some ready-made functions to do this have been created:
19623 @code{gnus-demon-add-nocem}, @code{gnus-demon-add-disconnection},
19624 @code{gnus-demon-add-nntp-close-connection},
19625 @code{gnus-demon-add-scan-timestamps}, @code{gnus-demon-add-rescan}, and
19626 @code{gnus-demon-add-scanmail}. Just put those functions in your
19627 @file{.gnus} if you want those abilities.
19629 @findex gnus-demon-init
19630 @findex gnus-demon-cancel
19631 @vindex gnus-demon-handlers
19632 If you add handlers to @code{gnus-demon-handlers} directly, you should
19633 run @code{gnus-demon-init} to make the changes take hold. To cancel all
19634 daemons, you can use the @code{gnus-demon-cancel} function.
19636 Note that adding daemons can be pretty naughty if you over do it. Adding
19637 functions that scan all news and mail from all servers every two seconds
19638 is a sure-fire way of getting booted off any respectable system. So
19647 @dfn{Spamming} is posting the same article lots and lots of times.
19648 Spamming is bad. Spamming is evil.
19650 Spamming is usually canceled within a day or so by various anti-spamming
19651 agencies. These agencies usually also send out @dfn{NoCeM} messages.
19652 NoCeM is pronounced ``no see-'em'', and means what the name
19653 implies---these are messages that make the offending articles, like, go
19656 What use are these NoCeM messages if the articles are canceled anyway?
19657 Some sites do not honor cancel messages and some sites just honor cancels
19658 from a select few people. Then you may wish to make use of the NoCeM
19659 messages, which are distributed in the @samp{alt.nocem.misc} newsgroup.
19661 Gnus can read and parse the messages in this group automatically, and
19662 this will make spam disappear.
19664 There are some variables to customize, of course:
19667 @item gnus-use-nocem
19668 @vindex gnus-use-nocem
19669 Set this variable to @code{t} to set the ball rolling. It is @code{nil}
19672 @item gnus-nocem-groups
19673 @vindex gnus-nocem-groups
19674 Gnus will look for NoCeM messages in the groups in this list. The
19675 default is @code{("news.lists.filters" "news.admin.net-abuse.bulletins"
19676 "alt.nocem.misc" "news.admin.net-abuse.announce")}.
19678 @item gnus-nocem-issuers
19679 @vindex gnus-nocem-issuers
19680 There are many people issuing NoCeM messages. This list says what
19681 people you want to listen to. The default is @code{("Automoose-1"
19682 "clewis@@ferret.ocunix.on.ca" "cosmo.roadkill" "SpamHippo"
19683 "hweede@@snafu.de")}; fine, upstanding citizens all of them.
19685 Known despammers that you can put in this list are listed at
19686 @uref{http://www.xs4all.nl/~rosalind/nocemreg/nocemreg.html}.
19688 You do not have to heed NoCeM messages from all these people---just the
19689 ones you want to listen to. You also don't have to accept all NoCeM
19690 messages from the people you like. Each NoCeM message has a @dfn{type}
19691 header that gives the message a (more or less, usually less) rigorous
19692 definition. Common types are @samp{spam}, @samp{spew}, @samp{mmf},
19693 @samp{binary}, and @samp{troll}. To specify this, you have to use
19694 @code{(@var{issuer} @var{conditions} @dots{})} elements in the list.
19695 Each condition is either a string (which is a regexp that matches types
19696 you want to use) or a list on the form @code{(not @var{string})}, where
19697 @var{string} is a regexp that matches types you don't want to use.
19699 For instance, if you want all NoCeM messages from Chris Lewis except his
19700 @samp{troll} messages, you'd say:
19703 ("clewis@@ferret.ocunix.on.ca" ".*" (not "troll"))
19706 On the other hand, if you just want nothing but his @samp{spam} and
19707 @samp{spew} messages, you'd say:
19710 ("clewis@@ferret.ocunix.on.ca" (not ".*") "spew" "spam")
19713 The specs are applied left-to-right.
19716 @item gnus-nocem-verifyer
19717 @vindex gnus-nocem-verifyer
19719 This should be a function for verifying that the NoCeM issuer is who she
19720 says she is. The default is @code{mc-verify}, which is a Mailcrypt
19721 function. If this is too slow and you don't care for verification
19722 (which may be dangerous), you can set this variable to @code{nil}.
19724 If you want signed NoCeM messages to be verified and unsigned messages
19725 not to be verified (but used anyway), you could do something like:
19728 (setq gnus-nocem-verifyer 'my-gnus-mc-verify)
19730 (defun my-gnus-mc-verify ()
19738 This might be dangerous, though.
19740 @item gnus-nocem-directory
19741 @vindex gnus-nocem-directory
19742 This is where Gnus will store its NoCeM cache files. The default is
19743 @file{~/News/NoCeM/}.
19745 @item gnus-nocem-expiry-wait
19746 @vindex gnus-nocem-expiry-wait
19747 The number of days before removing old NoCeM entries from the cache.
19748 The default is 15. If you make it shorter Gnus will be faster, but you
19749 might then see old spam.
19751 @item gnus-nocem-check-from
19752 @vindex gnus-nocem-check-from
19753 Non-@code{nil} means check for valid issuers in message bodies.
19754 Otherwise don't bother fetching articles unless their author matches a
19755 valid issuer; that is much faster if you are selective about the
19758 @item gnus-nocem-check-article-limit
19759 @vindex gnus-nocem-check-article-limit
19760 If non-@code{nil}, the maximum number of articles to check in any NoCeM
19761 group. NoCeM groups can be huge and very slow to process.
19765 Using NoCeM could potentially be a memory hog. If you have many living
19766 (i. e., subscribed or unsubscribed groups), your Emacs process will grow
19767 big. If this is a problem, you should kill off all (or most) of your
19768 unsubscribed groups (@pxref{Subscription Commands}).
19775 It is very useful to be able to undo actions one has done. In normal
19776 Emacs buffers, it's easy enough---you just push the @code{undo} button.
19777 In Gnus buffers, however, it isn't that simple.
19779 The things Gnus displays in its buffer is of no value whatsoever to
19780 Gnus---it's all just data designed to look nice to the user.
19781 Killing a group in the group buffer with @kbd{C-k} makes the line
19782 disappear, but that's just a side-effect of the real action---the
19783 removal of the group in question from the internal Gnus structures.
19784 Undoing something like that can't be done by the normal Emacs
19785 @code{undo} function.
19787 Gnus tries to remedy this somewhat by keeping track of what the user
19788 does and coming up with actions that would reverse the actions the user
19789 takes. When the user then presses the @code{undo} key, Gnus will run
19790 the code to reverse the previous action, or the previous actions.
19791 However, not all actions are easily reversible, so Gnus currently offers
19792 a few key functions to be undoable. These include killing groups,
19793 yanking groups, and changing the list of read articles of groups.
19794 That's it, really. More functions may be added in the future, but each
19795 added function means an increase in data to be stored, so Gnus will
19796 never be totally undoable.
19798 @findex gnus-undo-mode
19799 @vindex gnus-use-undo
19801 The undoability is provided by the @code{gnus-undo-mode} minor mode. It
19802 is used if @code{gnus-use-undo} is non-@code{nil}, which is the
19803 default. The @kbd{C-M-_} key performs the @code{gnus-undo}
19804 command, which should feel kinda like the normal Emacs @code{undo}
19808 @node Predicate Specifiers
19809 @section Predicate Specifiers
19810 @cindex predicate specifiers
19812 Some Gnus variables are @dfn{predicate specifiers}. This is a special
19813 form that allows flexible specification of predicates without having
19814 to type all that much.
19816 These specifiers are lists consisting of functions, symbols and lists.
19821 (or gnus-article-unseen-p
19822 gnus-article-unread-p)
19825 The available symbols are @code{or}, @code{and} and @code{not}. The
19826 functions all take one parameter.
19828 @findex gnus-make-predicate
19829 Internally, Gnus calls @code{gnus-make-predicate} on these specifiers
19830 to create a function that can be called. This input parameter to this
19831 function will be passed along to all the functions in the predicate
19836 @section Moderation
19839 If you are a moderator, you can use the @file{gnus-mdrtn.el} package.
19840 It is not included in the standard Gnus package. Write a mail to
19841 @samp{larsi@@gnus.org} and state what group you moderate, and you'll
19844 The moderation package is implemented as a minor mode for summary
19848 (add-hook 'gnus-summary-mode-hook 'gnus-moderate)
19851 in your @file{.gnus.el} file.
19853 If you are the moderator of @samp{rec.zoofle}, this is how it's
19858 You split your incoming mail by matching on
19859 @samp{Newsgroups:.*rec.zoofle}, which will put all the to-be-posted
19860 articles in some mail group---for instance, @samp{nnml:rec.zoofle}.
19863 You enter that group once in a while and post articles using the @kbd{e}
19864 (edit-and-post) or @kbd{s} (just send unedited) commands.
19867 If, while reading the @samp{rec.zoofle} newsgroup, you happen upon some
19868 articles that weren't approved by you, you can cancel them with the
19872 To use moderation mode in these two groups, say:
19875 (setq gnus-moderated-list
19876 "^nnml:rec.zoofle$\\|^rec.zoofle$")
19880 @node Image Enhancements
19881 @section Image Enhancements
19883 XEmacs, as well as Emacs 21, is able to display pictures and stuff, so
19884 Gnus has taken advantage of that.
19887 * Picons:: How to display pictures of what you're reading.
19888 * Smileys:: Show all those happy faces the way they were meant to be shown.
19889 * X-Face:: Display a funky, teensy black-and-white image.
19890 * Toolbar:: Click'n'drool.
19891 * XVarious:: Other XEmacsy Gnusey variables.
19904 So@dots{} You want to slow down your news reader even more! This is a
19905 good way to do so. Its also a great way to impress people staring
19906 over your shoulder as you read news.
19909 * Picon Basics:: What are picons and How do I get them.
19910 * Picon Requirements:: Don't go further if you aren't using XEmacs.
19911 * Easy Picons:: Displaying Picons---the easy way.
19912 * Hard Picons:: The way you should do it. You'll learn something.
19913 * Picon Useless Configuration:: Other variables you can trash/tweak/munge/play with.
19918 @subsubsection Picon Basics
19920 What are Picons? To quote directly from the Picons Web site:
19929 @dfn{Picons} is short for ``personal icons''. They're small,
19930 constrained images used to represent users and domains on the net,
19931 organized into databases so that the appropriate image for a given
19932 e-mail address can be found. Besides users and domains, there are picon
19933 databases for Usenet newsgroups and weather forecasts. The picons are
19934 in either monochrome @code{XBM} format or color @code{XPM} and
19935 @code{GIF} formats.
19938 @vindex gnus-picons-piconsearch-url
19939 If you have a permanent connection to the Internet you can use Steve
19940 Kinzler's Picons Search engine by setting
19941 @code{gnus-picons-piconsearch-url} to the string @*
19942 @uref{http://www.cs.indiana.edu/picons/search.html}.
19944 @vindex gnus-picons-database
19945 Otherwise you need a local copy of his database. For instructions on
19946 obtaining and installing the picons databases, point your Web browser at @*
19947 @uref{http://www.cs.indiana.edu/picons/ftp/index.html}. Gnus expects
19948 picons to be installed into a location pointed to by
19949 @code{gnus-picons-database}.
19951 If you are using Debian GNU/Linux, saying @samp{apt-get install
19952 picons.*} will install the picons where Gnus can find them.
19955 @node Picon Requirements
19956 @subsubsection Picon Requirements
19958 To have Gnus display Picons for you, you must have @code{x} support
19959 compiled into XEmacs. To display color picons which are much nicer
19960 than the black & white one, you also need one of @code{xpm} or
19961 @code{gif} compiled into XEmacs.
19963 @vindex gnus-picons-convert-x-face
19964 If you want to display faces from @code{X-Face} headers, you should have
19965 the @code{xface} support compiled into XEmacs. Otherwise you must have
19966 the @code{netpbm} utilities installed, or munge the
19967 @code{gnus-picons-convert-x-face} variable to use something else.
19968 (NOTE: @code{x-face} is used in the variable name, not @code{xface})
19971 @subsubsection Easy Picons
19973 To enable displaying picons, simply put the following line in your
19974 @file{~/.gnus} file and start Gnus.
19977 (setq gnus-use-picons t)
19978 (setq gnus-treat-display-picons t)
19981 and make sure @code{gnus-picons-database} points to the directory
19982 containing the Picons databases.
19984 Alternatively if you want to use the web piconsearch engine add this:
19987 (setq gnus-picons-piconsearch-url
19988 "http://www.cs.indiana.edu:800/piconsearch")
19993 @subsubsection Hard Picons
20001 Gnus can display picons for you as you enter and leave groups and
20002 articles. It knows how to interact with three sections of the picons
20003 database. Namely, it can display the picons newsgroup pictures,
20004 author's face picture(s), and the authors domain. To enable this
20005 feature, you need to select where to get the picons from, and where to
20010 @item gnus-picons-database
20011 @vindex gnus-picons-database
20012 The location of the picons database. Should point to a directory
20013 containing the @file{news}, @file{domains}, @file{users} (and so on)
20014 subdirectories. This is only useful if
20015 @code{gnus-picons-piconsearch-url} is @code{nil}. Defaults to
20016 @file{/usr/local/faces/}.
20018 @item gnus-picons-piconsearch-url
20019 @vindex gnus-picons-piconsearch-url
20020 The URL for the web picons search engine. The only currently known
20021 engine is @uref{http://www.cs.indiana.edu:800/piconsearch}. To
20022 workaround network delays, icons will be fetched in the background. If
20023 this is @code{nil} 'the default), then picons are fetched from local
20024 database indicated by @code{gnus-picons-database}.
20026 @item gnus-picons-display-where
20027 @vindex gnus-picons-display-where
20028 Where the picon images should be displayed. It is @code{picons} by
20029 default (which by default maps to the buffer @samp{*Picons*}). Other
20030 valid places could be @code{article}, @code{summary}, or
20031 @samp{*scratch*} for all I care. Just make sure that you've made the
20032 buffer visible using the standard Gnus window configuration
20033 routines---@pxref{Window Layout}.
20035 @item gnus-picons-group-excluded-groups
20036 @vindex gnus-picons-group-excluded-groups
20037 Groups that are matched by this regexp won't have their group icons
20042 Note: If you set @code{gnus-use-picons} to @code{t}, it will set up your
20043 window configuration for you to include the @code{picons} buffer.
20045 Now that you've made those decision, you need to add the following
20046 functions to the appropriate hooks so these pictures will get displayed
20049 @vindex gnus-picons-display-where
20051 @item gnus-article-display-picons
20052 @findex gnus-article-display-picons
20053 Looks up and displays the picons for the author and the author's domain
20054 in the @code{gnus-picons-display-where} buffer.
20056 @item gnus-picons-article-display-x-face
20057 @findex gnus-picons-article-display-x-face
20058 Decodes and displays the X-Face header if present.
20059 (NOTE: @code{x-face} is used in the function name, not @code{xface})
20065 @node Picon Useless Configuration
20066 @subsubsection Picon Useless Configuration
20074 The following variables offer further control over how things are
20075 done, where things are located, and other useless stuff you really
20076 don't need to worry about.
20080 @item gnus-picons-news-directories
20081 @vindex gnus-picons-news-directories
20082 List of subdirectories to search in @code{gnus-picons-database} for
20083 newsgroups faces. @code{("news")} is the default.
20085 @item gnus-picons-user-directories
20086 @vindex gnus-picons-user-directories
20087 List of subdirectories to search in @code{gnus-picons-database} for user
20088 faces. @code{("local" "users" "usenix" "misc")} is the default.
20090 @item gnus-picons-domain-directories
20091 @vindex gnus-picons-domain-directories
20092 List of subdirectories to search in @code{gnus-picons-database} for
20093 domain name faces. Defaults to @code{("domains")}. Some people may
20094 want to add @samp{"unknown"} to this list.
20096 @item gnus-picons-convert-x-face
20097 @vindex gnus-picons-convert-x-face
20098 If you don't have @code{xface} support builtin XEmacs, this is the
20099 command to use to convert the @code{X-Face} header to an X bitmap
20100 (@code{xbm}). Defaults to @code{(format "@{ echo '/* Width=48,
20101 Height=48 */'; uncompface; @} | icontopbm | pbmtoxbm > %s"
20102 gnus-picons-x-face-file-name)}
20103 (NOTE: @code{x-face} is used in the variable name, not @code{xface})
20105 @item gnus-picons-x-face-file-name
20106 @vindex gnus-picons-x-face-file-name
20107 Names a temporary file to store the @code{X-Face} bitmap in. Defaults
20108 to @code{(format "/tmp/picon-xface.%s.xbm" (user-login-name))}.
20109 (NOTE: @code{x-face} is used in the variable name, not @code{xface})
20111 @item gnus-picons-has-modeline-p
20112 @vindex gnus-picons-has-modeline-p
20113 If you have set @code{gnus-picons-display-where} to @code{picons}, your
20114 XEmacs frame will become really cluttered. To alleviate this a bit you
20115 can set @code{gnus-picons-has-modeline-p} to @code{nil}; this will
20116 remove the mode line from the Picons buffer. This is only useful if
20117 @code{gnus-picons-display-where} is @code{picons}.
20119 @item gnus-picons-refresh-before-display
20120 @vindex gnus-picons-refresh-before-display
20121 If non-nil, display the article buffer before computing the picons.
20122 Defaults to @code{nil}.
20124 @item gnus-picons-display-as-address
20125 @vindex gnus-picons-display-as-address
20126 If @code{t} display textual email addresses along with pictures.
20127 Defaults to @code{t}.
20129 @item gnus-picons-file-suffixes
20130 @vindex gnus-picons-file-suffixes
20131 Ordered list of suffixes on picon file names to try. Defaults to
20132 @code{("xpm" "gif" "xbm")} minus those not builtin your XEmacs.
20134 @item gnus-picons-setup-hook
20135 @vindex gnus-picons-setup-hook
20136 Hook run in the picon buffer, if that is displayed.
20138 @item gnus-picons-display-article-move-p
20139 @vindex gnus-picons-display-article-move-p
20140 Whether to move point to first empty line when displaying picons. This
20141 has only an effect if `gnus-picons-display-where' has value `article'.
20143 If @code{nil}, display the picons in the @code{From} and
20144 @code{Newsgroups} lines. This is the default.
20146 @item gnus-picons-clear-cache-on-shutdown
20147 @vindex gnus-picons-clear-cache-on-shutdown
20148 Whether to clear the picons cache when exiting gnus. Gnus caches every
20149 picons it finds while it is running. This saves some time in the search
20150 process but eats some memory. If this variable is set to @code{nil},
20151 Gnus will never clear the cache itself; you will have to manually call
20152 @code{gnus-picons-clear-cache} to clear it. Otherwise the cache will be
20153 cleared every time you exit Gnus. Defaults to @code{t}.
20164 @subsection Smileys
20169 \gnusfig{-3cm}{0.5cm}{\epsfig{figure=ps/BigFace,height=20cm}}
20174 @dfn{Smiley} is a package separate from Gnus, but since Gnus is
20175 currently the only package that uses Smiley, it is documented here.
20177 In short---to use Smiley in Gnus, put the following in your
20178 @file{.gnus.el} file:
20181 (setq gnus-treat-display-smileys t)
20184 Smiley maps text smiley faces---@samp{:-)}, @samp{:-=}, @samp{:-(} and
20185 the like---to pictures and displays those instead of the text smiley
20186 faces. The conversion is controlled by a list of regexps that matches
20187 text and maps that to file names.
20189 @vindex smiley-nosey-regexp-alist
20190 @vindex smiley-deformed-regexp-alist
20191 Smiley supplies two example conversion alists by default:
20192 @code{smiley-deformed-regexp-alist} (which matches @samp{:)}, @samp{:(}
20193 and so on), and @code{smiley-nosey-regexp-alist} (which matches
20194 @samp{:-)}, @samp{:-(} and so on).
20196 The alist used is specified by the @code{smiley-regexp-alist} variable,
20197 which defaults to the value of @code{smiley-deformed-regexp-alist}.
20199 The first item in each element is the regexp to be matched; the second
20200 element is the regexp match group that is to be replaced by the picture;
20201 and the third element is the name of the file to be displayed.
20203 The following variables customize where Smiley will look for these
20204 files, as well as the color to be used and stuff:
20208 @item smiley-data-directory
20209 @vindex smiley-data-directory
20210 Where Smiley will look for smiley faces files.
20212 @item smiley-flesh-color
20213 @vindex smiley-flesh-color
20214 Skin color. The default is @samp{yellow}, which is really racist.
20216 @item smiley-features-color
20217 @vindex smiley-features-color
20218 Color of the features of the face. The default is @samp{black}.
20220 @item smiley-tongue-color
20221 @vindex smiley-tongue-color
20222 Color of the tongue. The default is @samp{red}.
20224 @item smiley-circle-color
20225 @vindex smiley-circle-color
20226 Color of the circle around the face. The default is @samp{black}.
20228 @item smiley-mouse-face
20229 @vindex smiley-mouse-face
20230 Face used for mouse highlighting over the smiley face.
20239 @code{X-Face} headers describe a 48x48 pixel black-and-white (1 bit
20240 depth) image that's supposed to represent the author of the message.
20241 It seems to be supported by an ever-growing number of mail and news
20245 @findex gnus-article-display-x-face
20246 @findex gnus-article-x-face-command
20247 @vindex gnus-article-x-face-command
20248 @vindex gnus-article-x-face-too-ugly
20256 Decoding an @code{X-Face} header either requires an Emacs that has
20257 @samp{compface} support (which most XEmacs versions has), or that you
20258 have @samp{compface} installed on your system. If either is true,
20259 Gnus will default to displaying @code{X-Face} headers.
20261 The variable that controls this is the
20262 @code{gnus-article-x-face-command} variable. If this variable is a
20263 string, this string will be executed in a sub-shell. If it is a
20264 function, this function will be called with the face as the argument.
20265 If the @code{gnus-article-x-face-too-ugly} (which is a regexp) matches
20266 the @code{From} header, the face will not be shown.
20268 The default action under Emacs 20 is to fork off the @code{display}
20269 program@footnote{@code{display} is from the ImageMagick package. For
20270 the @code{uncompface} and @code{icontopbm} programs look for a package
20271 like @code{compface} or @code{faces-xface} on a GNU/Linux system.} to
20274 Under XEmacs or Emacs 21+ with suitable image support, the default
20275 action is to display the face before the @code{From} header. (It's
20276 nicer if XEmacs has been compiled with @code{X-Face} support---that
20277 will make display somewhat faster. If there's no native @code{X-Face}
20278 support, Gnus will try to convert the @code{X-Face} header using
20279 external programs from the @code{pbmplus} package and
20280 friends.@footnote{On a GNU/Linux system look for packages with names
20281 like @code{netpbm}, @code{libgr-progs} and @code{compface}.})
20283 (NOTE: @code{x-face} is used in the variable/function names, not
20286 Gnus provides a few convenience functions and variables to allow
20287 easier insertion of X-Face headers in outgoing messages.
20289 @findex gnus-random-x-face
20290 @code{gnus-random-x-face} goes through all the @samp{pbm} files
20291 in @code{gnus-x-face-directory} and picks one at random, and then
20292 converts it to the X-Face format by using the
20293 @code{gnus-convert-pbm-to-x-face-command} shell command. The
20294 @samp{pbm} files should be 48x48 pixels big.
20296 @code{gnus-x-face-from-file} takes a file as the parameter, and then
20297 converts the file to X-Face format by using the
20298 @code{gnus-convert-image-to-x-face-command} shell command.
20300 Here's how you would typically use the former function. Put something
20301 like the folllowing in your @file{.gnus.el} file:
20304 (setq message-required-news-headers
20305 (nconc message-required-news-headers
20306 (list '(X-Face . gnus-random-x-face))))
20309 Using the latter function would be something like this:
20312 (setq message-required-news-headers
20313 (nconc message-required-news-headers
20314 (list '(X-Face . (lambda ()
20315 (gnus-x-face-from-file
20316 "~/My-face.gif"))))))
20321 @subsection Toolbar
20331 @item gnus-use-toolbar
20332 @vindex gnus-use-toolbar
20333 If @code{nil}, don't display toolbars. If non-@code{nil}, it should be
20334 one of @code{default-toolbar}, @code{top-toolbar}, @code{bottom-toolbar},
20335 @code{right-toolbar}, or @code{left-toolbar}.
20337 @item gnus-group-toolbar
20338 @vindex gnus-group-toolbar
20339 The toolbar in the group buffer.
20341 @item gnus-summary-toolbar
20342 @vindex gnus-summary-toolbar
20343 The toolbar in the summary buffer.
20345 @item gnus-summary-mail-toolbar
20346 @vindex gnus-summary-mail-toolbar
20347 The toolbar in the summary buffer of mail groups.
20353 @subsection Various XEmacs Variables
20356 @item gnus-xmas-glyph-directory
20357 @vindex gnus-xmas-glyph-directory
20358 This is where Gnus will look for pictures. Gnus will normally
20359 auto-detect this directory, but you may set it manually if you have an
20360 unusual directory structure.
20362 @item gnus-xmas-logo-color-alist
20363 @vindex gnus-xmas-logo-color-alist
20364 This is an alist where the key is a type symbol and the values are the
20365 foreground and background color of the splash page glyph.
20367 @item gnus-xmas-logo-color-style
20368 @vindex gnus-xmas-logo-color-style
20369 This is the key used to look up the color in the alist described above.
20370 Valid values include @code{flame}, @code{pine}, @code{moss},
20371 @code{irish}, @code{sky}, @code{tin}, @code{velvet}, @code{grape},
20372 @code{labia}, @code{berry}, @code{neutral}, and @code{september}.
20374 @item gnus-xmas-modeline-glyph
20375 @vindex gnus-xmas-modeline-glyph
20376 A glyph displayed in all Gnus mode lines. It is a tiny gnu head by
20390 @node Fuzzy Matching
20391 @section Fuzzy Matching
20392 @cindex fuzzy matching
20394 Gnus provides @dfn{fuzzy matching} of @code{Subject} lines when doing
20395 things like scoring, thread gathering and thread comparison.
20397 As opposed to regular expression matching, fuzzy matching is very fuzzy.
20398 It's so fuzzy that there's not even a definition of what @dfn{fuzziness}
20399 means, and the implementation has changed over time.
20401 Basically, it tries to remove all noise from lines before comparing.
20402 @samp{Re: }, parenthetical remarks, white space, and so on, are filtered
20403 out of the strings before comparing the results. This often leads to
20404 adequate results---even when faced with strings generated by text
20405 manglers masquerading as newsreaders.
20408 @node Thwarting Email Spam
20409 @section Thwarting Email Spam
20413 @cindex unsolicited commercial email
20415 In these last days of the Usenet, commercial vultures are hanging about
20416 and grepping through news like crazy to find email addresses they can
20417 foist off their scams and products to. As a reaction to this, many
20418 people have started putting nonsense addresses into their @code{From}
20419 lines. I think this is counterproductive---it makes it difficult for
20420 people to send you legitimate mail in response to things you write, as
20421 well as making it difficult to see who wrote what. This rewriting may
20422 perhaps be a bigger menace than the unsolicited commercial email itself
20425 The biggest problem I have with email spam is that it comes in under
20426 false pretenses. I press @kbd{g} and Gnus merrily informs me that I
20427 have 10 new emails. I say ``Golly gee! Happy is me!'' and select the
20428 mail group, only to find two pyramid schemes, seven advertisements
20429 (``New! Miracle tonic for growing full, lustrous hair on your toes!'')
20430 and one mail asking me to repent and find some god.
20434 The way to deal with this is having Gnus split out all spam into a
20435 @samp{spam} mail group (@pxref{Splitting Mail}).
20437 First, pick one (1) valid mail address that you can be reached at, and
20438 put it in your @code{From} header of all your news articles. (I've
20439 chosen @samp{larsi@@trym.ifi.uio.no}, but for many addresses on the form
20440 @samp{larsi+usenet@@ifi.uio.no} will be a better choice. Ask your
20441 sysadmin whether your sendmail installation accepts keywords in the local
20442 part of the mail address.)
20445 (setq message-default-news-headers
20446 "From: Lars Magne Ingebrigtsen <larsi@@trym.ifi.uio.no>\n")
20449 Then put the following split rule in @code{nnmail-split-fancy}
20450 (@pxref{Fancy Mail Splitting}):
20455 (to "larsi@@trym.ifi.uio.no"
20456 (| ("subject" "re:.*" "misc")
20457 ("references" ".*@@.*" "misc")
20463 This says that all mail to this address is suspect, but if it has a
20464 @code{Subject} that starts with a @samp{Re:} or has a @code{References}
20465 header, it's probably ok. All the rest goes to the @samp{spam} group.
20466 (This idea probably comes from Tim Pierce.)
20468 In addition, many mail spammers talk directly to your @code{smtp} server
20469 and do not include your email address explicitly in the @code{To}
20470 header. Why they do this is unknown---perhaps it's to thwart this
20471 thwarting scheme? In any case, this is trivial to deal with---you just
20472 put anything not addressed to you in the @samp{spam} group by ending
20473 your fancy split rule in this way:
20478 (to "larsi" "misc")
20482 In my experience, this will sort virtually everything into the right
20483 group. You still have to check the @samp{spam} group from time to time to
20484 check for legitimate mail, though. If you feel like being a good net
20485 citizen, you can even send off complaints to the proper authorities on
20486 each unsolicited commercial email---at your leisure.
20488 If you are also a lazy net citizen, you will probably prefer complaining
20489 automatically with the @file{gnus-junk.el} package, available FOR FREE
20490 at @* @uref{http://stud2.tuwien.ac.at/~e9426626/gnus-junk.html}.
20491 Since most e-mail spam is sent automatically, this may reconcile the
20492 cosmic balance somewhat.
20494 This works for me. It allows people an easy way to contact me (they can
20495 just press @kbd{r} in the usual way), and I'm not bothered at all with
20496 spam. It's a win-win situation. Forging @code{From} headers to point
20497 to non-existent domains is yucky, in my opinion.
20500 @node Various Various
20501 @section Various Various
20507 @item gnus-home-directory
20508 All Gnus path variables will be initialized from this variable, which
20509 defaults to @file{~/}.
20511 @item gnus-directory
20512 @vindex gnus-directory
20513 Most Gnus storage path variables will be initialized from this variable,
20514 which defaults to the @samp{SAVEDIR} environment variable, or
20515 @file{~/News/} if that variable isn't set.
20517 Note that Gnus is mostly loaded when the @file{.gnus.el} file is read.
20518 This means that other directory variables that are initialized from this
20519 variable won't be set properly if you set this variable in
20520 @file{.gnus.el}. Set this variable in @file{.emacs} instead.
20522 @item gnus-default-directory
20523 @vindex gnus-default-directory
20524 Not related to the above variable at all---this variable says what the
20525 default directory of all Gnus buffers should be. If you issue commands
20526 like @kbd{C-x C-f}, the prompt you'll get starts in the current buffer's
20527 default directory. If this variable is @code{nil} (which is the
20528 default), the default directory will be the default directory of the
20529 buffer you were in when you started Gnus.
20532 @vindex gnus-verbose
20533 This variable is an integer between zero and ten. The higher the value,
20534 the more messages will be displayed. If this variable is zero, Gnus
20535 will never flash any messages, if it is seven (which is the default),
20536 most important messages will be shown, and if it is ten, Gnus won't ever
20537 shut up, but will flash so many messages it will make your head swim.
20539 @item gnus-verbose-backends
20540 @vindex gnus-verbose-backends
20541 This variable works the same way as @code{gnus-verbose}, but it applies
20542 to the Gnus back ends instead of Gnus proper.
20544 @item nnheader-max-head-length
20545 @vindex nnheader-max-head-length
20546 When the back ends read straight heads of articles, they all try to read
20547 as little as possible. This variable (default 4096) specifies
20548 the absolute max length the back ends will try to read before giving up
20549 on finding a separator line between the head and the body. If this
20550 variable is @code{nil}, there is no upper read bound. If it is
20551 @code{t}, the back ends won't try to read the articles piece by piece,
20552 but read the entire articles. This makes sense with some versions of
20553 @code{ange-ftp} or @code{efs}.
20555 @item nnheader-head-chop-length
20556 @vindex nnheader-head-chop-length
20557 This variable (default 2048) says how big a piece of each article to
20558 read when doing the operation described above.
20560 @item nnheader-file-name-translation-alist
20561 @vindex nnheader-file-name-translation-alist
20563 @cindex invalid characters in file names
20564 @cindex characters in file names
20565 This is an alist that says how to translate characters in file names.
20566 For instance, if @samp{:} is invalid as a file character in file names
20567 on your system (you OS/2 user you), you could say something like:
20570 (setq nnheader-file-name-translation-alist
20574 In fact, this is the default value for this variable on OS/2 and MS
20575 Windows (phooey) systems.
20577 @item gnus-hidden-properties
20578 @vindex gnus-hidden-properties
20579 This is a list of properties to use to hide ``invisible'' text. It is
20580 @code{(invisible t intangible t)} by default on most systems, which
20581 makes invisible text invisible and intangible.
20583 @item gnus-parse-headers-hook
20584 @vindex gnus-parse-headers-hook
20585 A hook called before parsing headers. It can be used, for instance, to
20586 gather statistics on the headers fetched, or perhaps you'd like to prune
20587 some headers. I don't see why you'd want that, though.
20589 @item gnus-shell-command-separator
20590 @vindex gnus-shell-command-separator
20591 String used to separate two shell commands. The default is @samp{;}.
20593 @item gnus-invalid-group-regexp
20594 @vindex gnus-invalid-group-regexp
20596 Regexp to match ``invalid'' group names when querying user for a group
20597 name. The default value catches some @strong{really} invalid group
20598 names who could possibly mess up Gnus internally (like allowing
20599 @samp{:} in a group name, which is normally used to delimit method and
20602 @sc{imap} users might want to allow @samp{/} in group names though.
20610 Well, that's the manual---you can get on with your life now. Keep in
20611 touch. Say hello to your cats from me.
20613 My @strong{ghod}---I just can't stand goodbyes. Sniffle.
20615 Ol' Charles Reznikoff said it pretty well, so I leave the floor to him:
20621 Not because of victories @*
20624 but for the common sunshine,@*
20626 the largess of the spring.
20630 but for the day's work done@*
20631 as well as I was able;@*
20632 not for a seat upon the dais@*
20633 but at the common table.@*
20638 @chapter Appendices
20641 * XEmacs:: Requirements for installing under XEmacs.
20642 * History:: How Gnus got where it is today.
20643 * On Writing Manuals:: Why this is not a beginner's guide.
20644 * Terminology:: We use really difficult, like, words here.
20645 * Customization:: Tailoring Gnus to your needs.
20646 * Troubleshooting:: What you might try if things do not work.
20647 * Gnus Reference Guide:: Rilly, rilly technical stuff.
20648 * Emacs for Heathens:: A short introduction to Emacsian terms.
20649 * Frequently Asked Questions::
20656 @cindex Installing under XEmacs
20658 XEmacs is distributed as a collection of packages. You should install
20659 whatever packages the Gnus XEmacs package requires. The current
20660 requirements are @samp{gnus}, @samp{w3}, @samp{mh-e},
20661 @samp{mailcrypt}, @samp{rmail}, @samp{eterm}, @samp{mail-lib},
20662 @samp{xemacs-base}, and @samp{fsf-compat}.
20669 @sc{gnus} was written by Masanobu @sc{Umeda}. When autumn crept up in
20670 '94, Lars Magne Ingebrigtsen grew bored and decided to rewrite Gnus.
20672 If you want to investigate the person responsible for this outrage,
20673 you can point your (feh!) web browser to
20674 @uref{http://quimby.gnus.org/}. This is also the primary
20675 distribution point for the new and spiffy versions of Gnus, and is
20676 known as The Site That Destroys Newsrcs And Drives People Mad.
20678 During the first extended alpha period of development, the new Gnus was
20679 called ``(ding) Gnus''. @dfn{(ding)} is, of course, short for
20680 @dfn{ding is not Gnus}, which is a total and utter lie, but who cares?
20681 (Besides, the ``Gnus'' in this abbreviation should probably be
20682 pronounced ``news'' as @sc{Umeda} intended, which makes it a more
20683 appropriate name, don't you think?)
20685 In any case, after spending all that energy on coming up with a new and
20686 spunky name, we decided that the name was @emph{too} spunky, so we
20687 renamed it back again to ``Gnus''. But in mixed case. ``Gnus'' vs.
20688 ``@sc{gnus}''. New vs. old.
20691 * Gnus Versions:: What Gnus versions have been released.
20692 * Other Gnus Versions:: Other Gnus versions that also have been released.
20693 * Why?:: What's the point of Gnus?
20694 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
20695 * Conformity:: Gnus tries to conform to all standards.
20696 * Emacsen:: Gnus can be run on a few modern Emacsen.
20697 * Gnus Development:: How Gnus is developed.
20698 * Contributors:: Oodles of people.
20699 * New Features:: Pointers to some of the new stuff in Gnus.
20703 @node Gnus Versions
20704 @subsection Gnus Versions
20706 @cindex September Gnus
20708 @cindex Quassia Gnus
20709 @cindex Pterodactyl Gnus
20713 The first ``proper'' release of Gnus 5 was done in November 1995 when it
20714 was included in the Emacs 19.30 distribution (132 (ding) Gnus releases
20715 plus 15 Gnus 5.0 releases).
20717 In May 1996 the next Gnus generation (aka. ``September Gnus'' (after 99
20718 releases)) was released under the name ``Gnus 5.2'' (40 releases).
20720 On July 28th 1996 work on Red Gnus was begun, and it was released on
20721 January 25th 1997 (after 84 releases) as ``Gnus 5.4'' (67 releases).
20723 On September 13th 1997, Quassia Gnus was started and lasted 37 releases.
20724 If was released as ``Gnus 5.6'' on March 8th 1998 (46 releases).
20726 Gnus 5.6 begat Pterodactyl Gnus on August 29th 1998 and was released as
20727 ``Gnus 5.8'' (after 99 releases and a CVS repository) on December 3rd
20730 On the 26th of October 2000, Oort Gnus was begun.
20732 If you happen upon a version of Gnus that has a prefixed name --
20733 ``(ding) Gnus'', ``September Gnus'', ``Red Gnus'', ``Quassia Gnus'',
20734 ``Pterodactyl Gnus'', ``Oort Gnus'' -- don't panic. Don't let it know
20735 that you're frightened. Back away. Slowly. Whatever you do, don't
20736 run. Walk away, calmly, until you're out of its reach. Find a proper
20737 released version of Gnus and snuggle up to that instead.
20740 @node Other Gnus Versions
20741 @subsection Other Gnus Versions
20744 In addition to the versions of Gnus which have had their releases
20745 coordinated by Lars, one major development has been Semi-gnus from
20746 Japan. It's based on a library called @sc{semi}, which provides
20747 @sc{mime} capabilities.
20749 These Gnusae are based mainly on Gnus 5.6 and Pterodactyl Gnus.
20750 Collectively, they are called ``Semi-gnus'', and different strains are
20751 called T-gnus, ET-gnus, Nana-gnus and Chaos. These provide powerful
20752 @sc{mime} and multilingualization things, especially important for
20759 What's the point of Gnus?
20761 I want to provide a ``rad'', ``happening'', ``way cool'' and ``hep''
20762 newsreader, that lets you do anything you can think of. That was my
20763 original motivation, but while working on Gnus, it has become clear to
20764 me that this generation of newsreaders really belong in the stone age.
20765 Newsreaders haven't developed much since the infancy of the net. If the
20766 volume continues to rise with the current rate of increase, all current
20767 newsreaders will be pretty much useless. How do you deal with
20768 newsgroups that have thousands of new articles each day? How do you
20769 keep track of millions of people who post?
20771 Gnus offers no real solutions to these questions, but I would very much
20772 like to see Gnus being used as a testing ground for new methods of
20773 reading and fetching news. Expanding on @sc{Umeda}-san's wise decision
20774 to separate the newsreader from the back ends, Gnus now offers a simple
20775 interface for anybody who wants to write new back ends for fetching mail
20776 and news from different sources. I have added hooks for customizations
20777 everywhere I could imagine it being useful. By doing so, I'm inviting
20778 every one of you to explore and invent.
20780 May Gnus never be complete. @kbd{C-u 100 M-x all-hail-emacs} and
20781 @kbd{C-u 100 M-x all-hail-xemacs}.
20784 @node Compatibility
20785 @subsection Compatibility
20787 @cindex compatibility
20788 Gnus was designed to be fully compatible with @sc{gnus}. Almost all key
20789 bindings have been kept. More key bindings have been added, of course,
20790 but only in one or two obscure cases have old bindings been changed.
20795 @center In a cloud bones of steel.
20799 All commands have kept their names. Some internal functions have changed
20802 The @code{gnus-uu} package has changed drastically. @xref{Decoding
20805 One major compatibility question is the presence of several summary
20806 buffers. All variables relevant while reading a group are
20807 buffer-local to the summary buffer they belong in. Although many
20808 important variables have their values copied into their global
20809 counterparts whenever a command is executed in the summary buffer, this
20810 change might lead to incorrect values being used unless you are careful.
20812 All code that relies on knowledge of @sc{gnus} internals will probably
20813 fail. To take two examples: Sorting @code{gnus-newsrc-alist} (or
20814 changing it in any way, as a matter of fact) is strictly verboten. Gnus
20815 maintains a hash table that points to the entries in this alist (which
20816 speeds up many functions), and changing the alist directly will lead to
20820 @cindex highlighting
20821 Old hilit19 code does not work at all. In fact, you should probably
20822 remove all hilit code from all Gnus hooks
20823 (@code{gnus-group-prepare-hook} and @code{gnus-summary-prepare-hook}).
20824 Gnus provides various integrated functions for highlighting. These are
20825 faster and more accurate. To make life easier for everybody, Gnus will
20826 by default remove all hilit calls from all hilit hooks. Uncleanliness!
20829 Packages like @code{expire-kill} will no longer work. As a matter of
20830 fact, you should probably remove all old @sc{gnus} packages (and other
20831 code) when you start using Gnus. More likely than not, Gnus already
20832 does what you have written code to make @sc{gnus} do. (Snicker.)
20834 Even though old methods of doing things are still supported, only the
20835 new methods are documented in this manual. If you detect a new method of
20836 doing something while reading this manual, that does not mean you have
20837 to stop doing it the old way.
20839 Gnus understands all @sc{gnus} startup files.
20841 @kindex M-x gnus-bug
20843 @cindex reporting bugs
20845 Overall, a casual user who hasn't written much code that depends on
20846 @sc{gnus} internals should suffer no problems. If problems occur,
20847 please let me know by issuing that magic command @kbd{M-x gnus-bug}.
20849 @vindex gnus-bug-create-help-buffer
20850 If you are in the habit of sending bug reports @emph{very} often, you
20851 may find the helpful help buffer annoying after a while. If so, set
20852 @code{gnus-bug-create-help-buffer} to @code{nil} to avoid having it pop
20857 @subsection Conformity
20859 No rebels without a clue here, ma'am. We conform to all standards known
20860 to (wo)man. Except for those standards and/or conventions we disagree
20868 There are no known breaches of this standard.
20872 There are no known breaches of this standard, either.
20874 @item Son-of-RFC 1036
20875 @cindex Son-of-RFC 1036
20876 We do have some breaches to this one.
20882 These are considered to be ``vanity headers'', while I consider them
20883 to be consumer information. After seeing so many badly formatted
20884 articles coming from @code{tin} and @code{Netscape} I know not to use
20885 either of those for posting articles. I would not have known that if
20886 it wasn't for the @code{X-Newsreader} header.
20891 USEFOR is an IETF working group writing a successor to RFC 1036, based
20892 on Son-of-RFC 1036. They have produced a number of drafts proposing
20893 various changes to the format of news articles. The Gnus towers will
20894 look into implementing the changes when the draft is accepted as an RFC.
20896 @item MIME - RFC 2045-2049 etc
20898 All the various MIME RFCs are supported.
20900 @item Disposition Notifications - RFC 2298
20901 Message Mode is able to request notifications from the receiver.
20903 @item PGP - RFC 1991 and RFC 2440
20906 RFC 1991 is the original PGP message specification, published as a
20907 Information RFC. RFC 2440 was the follow-up, now called Open PGP, and
20908 put on the Standards Track. Both document a non-MIME aware PGP
20909 format. Gnus supports both encoding (signing and encryption) and
20910 decoding (verification and decryption).
20912 @item PGP/MIME - RFC 2015/3156
20913 RFC 2015 (superceded by 3156 which references RFC 2440 instead of RFC
20914 1991) describes the MIME-wrapping around the RF 1991/2440 format.
20915 Gnus supports both encoding and decoding.
20917 @item S/MIME - RFC 2633
20918 RFC 2633 describes the S/MIME format.
20920 @item IMAP - RFC 1730/2060, RFC 2195, RFC 2086, RFC 2359, RFC 2595, RFC 1731
20921 RFC 1730 is IMAP version 4, updated somewhat by RFC 2060 (IMAP 4
20922 revision 1). RFC 2195 describes CRAM-MD5 authentication for IMAP. RFC
20923 2086 describes access control lists (ACLs) for IMAP. RFC 2359
20924 describes a IMAP protocol enhancement. RFC 2595 describes the proper
20925 TLS integration (STARTTLS) with IMAP. RFC 1731 describes the
20926 GSSAPI/Kerberos4 mechanisms for IMAP.
20930 If you ever notice Gnus acting non-compliant with regards to the texts
20931 mentioned above, don't hesitate to drop a note to Gnus Towers and let us
20936 @subsection Emacsen
20942 Gnus should work on :
20950 XEmacs 20.4 and up.
20954 This Gnus version will absolutely not work on any Emacsen older than
20955 that. Not reliably, at least. Older versions of Gnus may work on older
20958 There are some vague differences between Gnus on the various
20959 platforms---XEmacs features more graphics (a logo and a toolbar)---but
20960 other than that, things should look pretty much the same under all
20964 @node Gnus Development
20965 @subsection Gnus Development
20967 Gnus is developed in a two-phased cycle. The first phase involves much
20968 discussion on the @samp{ding@@gnus.org} mailing list, where people
20969 propose changes and new features, post patches and new back ends. This
20970 phase is called the @dfn{alpha} phase, since the Gnusae released in this
20971 phase are @dfn{alpha releases}, or (perhaps more commonly in other
20972 circles) @dfn{snapshots}. During this phase, Gnus is assumed to be
20973 unstable and should not be used by casual users. Gnus alpha releases
20974 have names like ``Red Gnus'' and ``Quassia Gnus''.
20976 After futzing around for 50-100 alpha releases, Gnus is declared
20977 @dfn{frozen}, and only bug fixes are applied. Gnus loses the prefix,
20978 and is called things like ``Gnus 5.6.32'' instead. Normal people are
20979 supposed to be able to use these, and these are mostly discussed on the
20980 @samp{gnu.emacs.gnus} newsgroup.
20983 @vindex mail-source-delete-incoming
20984 Some variable defaults differ between alpha Gnusae and released Gnusae.
20985 In particular, @code{mail-source-delete-incoming} defaults to @code{nil} in
20986 alpha Gnusae and @code{t} in released Gnusae. This is to prevent
20987 lossage of mail if an alpha release hiccups while handling the mail.
20989 The division of discussion between the ding mailing list and the Gnus
20990 newsgroup is not purely based on publicity concerns. It's true that
20991 having people write about the horrible things that an alpha Gnus release
20992 can do (sometimes) in a public forum may scare people off, but more
20993 importantly, talking about new experimental features that have been
20994 introduced may confuse casual users. New features are frequently
20995 introduced, fiddled with, and judged to be found wanting, and then
20996 either discarded or totally rewritten. People reading the mailing list
20997 usually keep up with these rapid changes, while people on the newsgroup
20998 can't be assumed to do so.
21003 @subsection Contributors
21004 @cindex contributors
21006 The new Gnus version couldn't have been done without the help of all the
21007 people on the (ding) mailing list. Every day for over a year I have
21008 gotten billions of nice bug reports from them, filling me with joy,
21009 every single one of them. Smooches. The people on the list have been
21010 tried beyond endurance, what with my ``oh, that's a neat idea <type
21011 type>, yup, I'll release it right away <ship off> no wait, that doesn't
21012 work at all <type type>, yup, I'll ship that one off right away <ship
21013 off> no, wait, that absolutely does not work'' policy for releases.
21014 Micro$oft---bah. Amateurs. I'm @emph{much} worse. (Or is that
21015 ``worser''? ``much worser''? ``worsest''?)
21017 I would like to take this opportunity to thank the Academy for... oops,
21023 Masanobu @sc{Umeda}---the writer of the original @sc{gnus}.
21026 Shenghuo Zhu---uudecode.el, mm-uu.el, rfc1843.el, webmail.el,
21027 nnwarchive and many, many other things connected with @sc{mime} and
21028 other types of en/decoding, as well as general bug fixing, new
21029 functionality and stuff.
21032 Per Abrahamsen---custom, scoring, highlighting and @sc{soup} code (as
21033 well as numerous other things).
21036 Luis Fernandes---design and graphics.
21039 Joe Reiss---creator of the smiley faces.
21042 Justin Sheehy--the FAQ maintainer.
21045 Erik Naggum---help, ideas, support, code and stuff.
21048 Wes Hardaker---@file{gnus-picon.el} and the manual section on
21049 @dfn{picons} (@pxref{Picons}).
21052 Kim-Minh Kaplan---further work on the picon code.
21055 Brad Miller---@file{gnus-gl.el} and the GroupLens manual section
21056 (@pxref{GroupLens}).
21059 Sudish Joseph---innumerable bug fixes.
21062 Ilja Weis---@file{gnus-topic.el}.
21065 Steven L. Baur---lots and lots and lots of bugs detections and fixes.
21068 Vladimir Alexiev---the refcard and reference booklets.
21071 Felix Lee & Jamie Zawinski---I stole some pieces from the XGnus
21072 distribution by Felix Lee and JWZ.
21075 Scott Byer---@file{nnfolder.el} enhancements & rewrite.
21078 Peter Mutsaers---orphan article scoring code.
21081 Ken Raeburn---POP mail support.
21084 Hallvard B Furuseth---various bits and pieces, especially dealing with
21088 Brian Edmonds---@file{gnus-bbdb.el}.
21091 David Moore---rewrite of @file{nnvirtual.el} and many other things.
21094 Kevin Davidson---came up with the name @dfn{ding}, so blame him.
21097 François Pinard---many, many interesting and thorough bug reports, as
21098 well as autoconf support.
21102 This manual was proof-read by Adrian Aichner, with Ricardo Nassif, Mark
21103 Borges, and Jost Krieger proof-reading parts of the manual.
21105 The following people have contributed many patches and suggestions:
21114 Jason L. Tibbitts, III,
21118 Also thanks to the following for patches and stuff:
21128 Alexei V. Barantsev,
21143 Massimo Campostrini,
21148 Jae-you Chung, @c ?
21149 James H. Cloos, Jr.,
21153 Andrew J. Cosgriff,
21156 Geoffrey T. Dairiki,
21162 Michael Welsh Duggan,
21167 Enami Tsugutomo, @c Enami
21171 Nelson Jose dos Santos Ferreira,
21179 Arne Georg Gleditsch,
21181 Michelangelo Grigni,
21185 Kenichi Handa, @c Handa
21187 Yoshiki Hayashi, @c ?
21189 Hisashige Kenji, @c Hisashige
21196 François Felix Ingrand,
21197 Tatsuya Ichikawa, @c ?
21198 Ishikawa Ichiro, @c Ishikawa
21200 Iwamuro Motonori, @c Iwamuro
21211 Peter Skov Knudsen,
21212 Shuhei Kobayashi, @c Kobayashi
21214 Koseki Yoshinori, @c Koseki
21215 Thor Kristoffersen,
21218 Seokchan Lee, @c Lee
21236 Morioka Tomohiko, @c Morioka
21237 Erik Toubro Nielsen,
21244 Masaharu Onishi, @c Onishi
21249 Jens-Ulrik Holger Petersen,
21253 John McClary Prevost,
21259 Lars Balker Rasmussen,
21264 Christian von Roques,
21267 Wolfgang Rupprecht,
21274 Philippe Schnoebelen,
21276 Randal L. Schwartz,
21290 Kiyokazu Suto, @c Suto
21295 Tozawa Akihiko, @c Tozawa
21311 Katsumi Yamaoka @c Yamaoka
21316 For a full overview of what each person has done, the ChangeLogs
21317 included in the Gnus alpha distributions should give ample reading
21318 (550kB and counting).
21320 Apologies to everybody that I've forgotten, of which there are many, I'm
21323 Gee, that's quite a list of people. I guess that must mean that there
21324 actually are people who are using Gnus. Who'd'a thunk it!
21328 @subsection New Features
21329 @cindex new features
21332 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
21333 * September Gnus:: The Thing Formally Known As Gnus 5.2/5.3.
21334 * Red Gnus:: Third time best---Gnus 5.4/5.5.
21335 * Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
21336 * Pterodactyl Gnus:: Pentad also starts with P, AKA Gnus 5.8/5.9.
21339 These lists are, of course, just @emph{short} overviews of the
21340 @emph{most} important new features. No, really. There are tons more.
21341 Yes, we have feeping creaturism in full effect.
21344 @subsubsection (ding) Gnus
21346 New features in Gnus 5.0/5.1:
21351 The look of all buffers can be changed by setting format-like variables
21352 (@pxref{Group Buffer Format} and @pxref{Summary Buffer Format}).
21355 Local spool and several @sc{nntp} servers can be used at once
21356 (@pxref{Select Methods}).
21359 You can combine groups into virtual groups (@pxref{Virtual Groups}).
21362 You can read a number of different mail formats (@pxref{Getting Mail}).
21363 All the mail back ends implement a convenient mail expiry scheme
21364 (@pxref{Expiring Mail}).
21367 Gnus can use various strategies for gathering threads that have lost
21368 their roots (thereby gathering loose sub-threads into one thread) or it
21369 can go back and retrieve enough headers to build a complete thread
21370 (@pxref{Customizing Threading}).
21373 Killed groups can be displayed in the group buffer, and you can read
21374 them as well (@pxref{Listing Groups}).
21377 Gnus can do partial group updates---you do not have to retrieve the
21378 entire active file just to check for new articles in a few groups
21379 (@pxref{The Active File}).
21382 Gnus implements a sliding scale of subscribedness to groups
21383 (@pxref{Group Levels}).
21386 You can score articles according to any number of criteria
21387 (@pxref{Scoring}). You can even get Gnus to find out how to score
21388 articles for you (@pxref{Adaptive Scoring}).
21391 Gnus maintains a dribble buffer that is auto-saved the normal Emacs
21392 manner, so it should be difficult to lose much data on what you have
21393 read if your machine should go down (@pxref{Auto Save}).
21396 Gnus now has its own startup file (@file{.gnus}) to avoid cluttering up
21397 the @file{.emacs} file.
21400 You can set the process mark on both groups and articles and perform
21401 operations on all the marked items (@pxref{Process/Prefix}).
21404 You can grep through a subset of groups and create a group from the
21405 results (@pxref{Kibozed Groups}).
21408 You can list subsets of groups according to, well, anything
21409 (@pxref{Listing Groups}).
21412 You can browse foreign servers and subscribe to groups from those
21413 servers (@pxref{Browse Foreign Server}).
21416 Gnus can fetch articles, asynchronously, on a second connection to the
21417 server (@pxref{Asynchronous Fetching}).
21420 You can cache articles locally (@pxref{Article Caching}).
21423 The uudecode functions have been expanded and generalized
21424 (@pxref{Decoding Articles}).
21427 You can still post uuencoded articles, which was a little-known feature
21428 of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
21431 Fetching parents (and other articles) now actually works without
21432 glitches (@pxref{Finding the Parent}).
21435 Gnus can fetch FAQs and group descriptions (@pxref{Group Information}).
21438 Digests (and other files) can be used as the basis for groups
21439 (@pxref{Document Groups}).
21442 Articles can be highlighted and customized (@pxref{Customizing
21446 URLs and other external references can be buttonized (@pxref{Article
21450 You can do lots of strange stuff with the Gnus window & frame
21451 configuration (@pxref{Window Layout}).
21454 You can click on buttons instead of using the keyboard
21460 @node September Gnus
21461 @subsubsection September Gnus
21465 \gnusfig{-28cm}{0cm}{\epsfig{figure=ps/september,height=20cm}}
21469 New features in Gnus 5.2/5.3:
21474 A new message composition mode is used. All old customization variables
21475 for @code{mail-mode}, @code{rnews-reply-mode} and @code{gnus-msg} are
21479 Gnus is now able to generate @dfn{sparse} threads---threads where
21480 missing articles are represented by empty nodes (@pxref{Customizing
21484 (setq gnus-build-sparse-threads 'some)
21488 Outgoing articles are stored on a special archive server
21489 (@pxref{Archived Messages}).
21492 Partial thread regeneration now happens when articles are
21496 Gnus can make use of GroupLens predictions (@pxref{GroupLens}).
21499 Picons (personal icons) can be displayed under XEmacs (@pxref{Picons}).
21502 A @code{trn}-like tree buffer can be displayed (@pxref{Tree Display}).
21505 (setq gnus-use-trees t)
21509 An @code{nn}-like pick-and-read minor mode is available for the summary
21510 buffers (@pxref{Pick and Read}).
21513 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
21517 In binary groups you can use a special binary minor mode (@pxref{Binary
21521 Groups can be grouped in a folding topic hierarchy (@pxref{Group
21525 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
21529 Gnus can re-send and bounce mail (@pxref{Summary Mail Commands}).
21532 Groups can now have a score, and bubbling based on entry frequency
21533 is possible (@pxref{Group Score}).
21536 (add-hook 'gnus-summary-exit-hook 'gnus-summary-bubble-group)
21540 Groups can be process-marked, and commands can be performed on
21541 groups of groups (@pxref{Marking Groups}).
21544 Caching is possible in virtual groups.
21547 @code{nndoc} now understands all kinds of digests, mail boxes, rnews
21548 news batches, ClariNet briefs collections, and just about everything
21549 else (@pxref{Document Groups}).
21552 Gnus has a new back end (@code{nnsoup}) to create/read SOUP packets
21556 The Gnus cache is much faster.
21559 Groups can be sorted according to many criteria (@pxref{Sorting
21563 New group parameters have been introduced to set list-addresses and
21564 expiry times (@pxref{Group Parameters}).
21567 All formatting specs allow specifying faces to be used
21568 (@pxref{Formatting Fonts}).
21571 There are several more commands for setting/removing/acting on process
21572 marked articles on the @kbd{M P} submap (@pxref{Setting Process Marks}).
21575 The summary buffer can be limited to show parts of the available
21576 articles based on a wide range of criteria. These commands have been
21577 bound to keys on the @kbd{/} submap (@pxref{Limiting}).
21580 Articles can be made persistent with the @kbd{*} command
21581 (@pxref{Persistent Articles}).
21584 All functions for hiding article elements are now toggles.
21587 Article headers can be buttonized (@pxref{Article Washing}).
21590 All mail back ends support fetching articles by @code{Message-ID}.
21593 Duplicate mail can now be treated properly (@pxref{Duplicates}).
21596 All summary mode commands are available directly from the article
21597 buffer (@pxref{Article Keymap}).
21600 Frames can be part of @code{gnus-buffer-configuration} (@pxref{Window
21604 Mail can be re-scanned by a daemonic process (@pxref{Daemons}).
21607 \marginpar[\mbox{}\hfill\epsfig{figure=ps/fseptember,height=5cm}]{\epsfig{figure=ps/fseptember,height=5cm}}
21612 Gnus can make use of NoCeM files to weed out spam (@pxref{NoCeM}).
21615 (setq gnus-use-nocem t)
21619 Groups can be made permanently visible (@pxref{Listing Groups}).
21622 (setq gnus-permanently-visible-groups "^nnml:")
21626 Many new hooks have been introduced to make customizing easier.
21629 Gnus respects the @code{Mail-Copies-To} header.
21632 Threads can be gathered by looking at the @code{References} header
21633 (@pxref{Customizing Threading}).
21636 (setq gnus-summary-thread-gathering-function
21637 'gnus-gather-threads-by-references)
21641 Read articles can be stored in a special backlog buffer to avoid
21642 refetching (@pxref{Article Backlog}).
21645 (setq gnus-keep-backlog 50)
21649 A clean copy of the current article is always stored in a separate
21650 buffer to allow easier treatment.
21653 Gnus can suggest where to save articles (@pxref{Saving Articles}).
21656 Gnus doesn't have to do as much prompting when saving (@pxref{Saving
21660 (setq gnus-prompt-before-saving t)
21664 @code{gnus-uu} can view decoded files asynchronously while fetching
21665 articles (@pxref{Other Decode Variables}).
21668 (setq gnus-uu-grabbed-file-functions 'gnus-uu-grab-view)
21672 Filling in the article buffer now works properly on cited text
21673 (@pxref{Article Washing}).
21676 Hiding cited text adds buttons to toggle hiding, and how much
21677 cited text to hide is now customizable (@pxref{Article Hiding}).
21680 (setq gnus-cited-lines-visible 2)
21684 Boring headers can be hidden (@pxref{Article Hiding}).
21687 Default scoring values can now be set from the menu bar.
21690 Further syntax checking of outgoing articles have been added.
21696 @subsubsection Red Gnus
21698 New features in Gnus 5.4/5.5:
21702 \gnusfig{-5.5cm}{-4cm}{\epsfig{figure=ps/red,height=20cm}}
21709 @file{nntp.el} has been totally rewritten in an asynchronous fashion.
21712 Article prefetching functionality has been moved up into
21713 Gnus (@pxref{Asynchronous Fetching}).
21716 Scoring can now be performed with logical operators like @code{and},
21717 @code{or}, @code{not}, and parent redirection (@pxref{Advanced
21721 Article washing status can be displayed in the
21722 article mode line (@pxref{Misc Article}).
21725 @file{gnus.el} has been split into many smaller files.
21728 Suppression of duplicate articles based on Message-ID can be done
21729 (@pxref{Duplicate Suppression}).
21732 (setq gnus-suppress-duplicates t)
21736 New variables for specifying what score and adapt files are to be
21737 considered home score and adapt files (@pxref{Home Score File}) have
21741 @code{nndoc} was rewritten to be easily extendable (@pxref{Document
21742 Server Internals}).
21745 Groups can inherit group parameters from parent topics (@pxref{Topic
21749 Article editing has been revamped and is now actually usable.
21752 Signatures can be recognized in more intelligent fashions
21753 (@pxref{Article Signature}).
21756 Summary pick mode has been made to look more @code{nn}-like. Line
21757 numbers are displayed and the @kbd{.} command can be used to pick
21758 articles (@code{Pick and Read}).
21761 Commands for moving the @file{.newsrc.eld} from one server to
21762 another have been added (@pxref{Changing Servers}).
21765 There's a way now to specify that ``uninteresting'' fields be suppressed
21766 when generating lines in buffers (@pxref{Advanced Formatting}).
21769 Several commands in the group buffer can be undone with @kbd{C-M-_}
21773 Scoring can be done on words using the new score type @code{w}
21774 (@pxref{Score File Format}).
21777 Adaptive scoring can be done on a Subject word-by-word basis
21778 (@pxref{Adaptive Scoring}).
21781 (setq gnus-use-adaptive-scoring '(word))
21785 Scores can be decayed (@pxref{Score Decays}).
21788 (setq gnus-decay-scores t)
21792 Scoring can be performed using a regexp on the Date header. The Date is
21793 normalized to compact ISO 8601 format first (@pxref{Score File Format}).
21796 A new command has been added to remove all data on articles from
21797 the native server (@pxref{Changing Servers}).
21800 A new command for reading collections of documents
21801 (@code{nndoc} with @code{nnvirtual} on top) has been added---@kbd{C-M-d}
21802 (@pxref{Really Various Summary Commands}).
21805 Process mark sets can be pushed and popped (@pxref{Setting Process
21809 A new mail-to-news back end makes it possible to post even when the @sc{nntp}
21810 server doesn't allow posting (@pxref{Mail-To-News Gateways}).
21813 A new back end for reading searches from Web search engines
21814 (@dfn{DejaNews}, @dfn{Alta Vista}, @dfn{InReference}) has been added
21815 (@pxref{Web Searches}).
21818 Groups inside topics can now be sorted using the standard sorting
21819 functions, and each topic can be sorted independently (@pxref{Topic
21823 Subsets of the groups can be sorted independently (@code{Sorting
21827 Cached articles can be pulled into the groups (@pxref{Summary Generation
21831 \marginpar[\mbox{}\hfill\epsfig{figure=ps/fred,width=3cm}]{\epsfig{figure=ps/fred,width=3cm}}
21836 Score files are now applied in a more reliable order (@pxref{Score
21840 Reports on where mail messages end up can be generated (@pxref{Splitting
21844 More hooks and functions have been added to remove junk from incoming
21845 mail before saving the mail (@pxref{Washing Mail}).
21848 Emphasized text can be properly fontisized:
21854 @subsubsection Quassia Gnus
21856 New features in Gnus 5.6:
21861 New functionality for using Gnus as an offline newsreader has been
21862 added. A plethora of new commands and modes have been added. See
21863 @pxref{Gnus Unplugged} for the full story.
21866 The @code{nndraft} back end has returned, but works differently than
21867 before. All Message buffers are now also articles in the @code{nndraft}
21868 group, which is created automatically.
21871 @code{gnus-alter-header-function} can now be used to alter header
21875 @code{gnus-summary-goto-article} now accept Message-ID's.
21878 A new Message command for deleting text in the body of a message
21879 outside the region: @kbd{C-c C-v}.
21882 You can now post to component group in @code{nnvirtual} groups with
21886 @code{nntp-rlogin-program}---new variable to ease customization.
21889 @code{C-u C-c C-c} in @code{gnus-article-edit-mode} will now inhibit
21890 re-highlighting of the article buffer.
21893 New element in @code{gnus-boring-article-headers}---@code{long-to}.
21896 @kbd{M-i} symbolic prefix command. See the section "Symbolic
21897 Prefixes" in the Gnus manual for details.
21900 @kbd{L} and @kbd{I} in the summary buffer now take the symbolic prefix
21901 @kbd{a} to add the score rule to the "all.SCORE" file.
21904 @code{gnus-simplify-subject-functions} variable to allow greater
21905 control over simplification.
21908 @kbd{A T}---new command for fetching the current thread.
21911 @kbd{/ T}---new command for including the current thread in the
21915 @kbd{M-RET} is a new Message command for breaking cited text.
21918 @samp{\\1}-expressions are now valid in @code{nnmail-split-methods}.
21921 The @code{custom-face-lookup} function has been removed.
21922 If you used this function in your initialization files, you must
21923 rewrite them to use @code{face-spec-set} instead.
21926 Canceling now uses the current select method. Symbolic prefix
21927 @kbd{a} forces normal posting method.
21930 New command to translate M******** sm*rtq**t*s into proper
21934 For easier debugging of @code{nntp}, you can set
21935 @code{nntp-record-commands} to a non-@code{nil} value.
21938 @code{nntp} now uses @file{~/.authinfo}, a @file{.netrc}-like file, for
21939 controlling where and how to send @sc{authinfo} to @sc{nntp} servers.
21942 A command for editing group parameters from the summary buffer
21946 A history of where mails have been split is available.
21949 A new article date command has been added---@code{article-date-iso8601}.
21952 Subjects can be simplified when threading by setting
21953 @code{gnus-score-thread-simplify}.
21956 A new function for citing in Message has been
21957 added---@code{message-cite-original-without-signature}.
21960 @code{article-strip-all-blank-lines}---new article command.
21963 A new Message command to kill to the end of the article has
21967 A minimum adaptive score can be specified by using the
21968 @code{gnus-adaptive-word-minimum} variable.
21971 The "lapsed date" article header can be kept continually
21972 updated by the @code{gnus-start-date-timer} command.
21975 Web listserv archives can be read with the @code{nnlistserv} back end.
21978 Old dejanews archives can now be read by @code{nnweb}.
21982 @node Pterodactyl Gnus
21983 @subsubsection Pterodactyl Gnus
21985 New features in Gnus 5.8:
21990 The mail-fetching functions have changed. See the manual for the
21991 many details. In particular, all procmail fetching variables are gone.
21993 If you used procmail like in
21996 (setq nnmail-use-procmail t)
21997 (setq nnmail-spool-file 'procmail)
21998 (setq nnmail-procmail-directory "~/mail/incoming/")
21999 (setq nnmail-procmail-suffix "\\.in")
22002 this now has changed to
22006 '((directory :path "~/mail/incoming/"
22010 More information is available in the info doc at Select Methods ->
22011 Getting Mail -> Mail Sources
22014 Gnus is now a MIME-capable reader. This affects many parts of
22015 Gnus, and adds a slew of new commands. See the manual for details.
22018 Gnus has also been multilingualized. This also affects too
22019 many parts of Gnus to summarize here, and adds many new variables.
22022 @code{gnus-auto-select-first} can now be a function to be
22023 called to position point.
22026 The user can now decide which extra headers should be included in
22027 summary buffers and NOV files.
22030 @code{gnus-article-display-hook} has been removed. Instead, a number
22031 of variables starting with @code{gnus-treat-} have been added.
22034 The Gnus posting styles have been redone again and now works in a
22035 subtly different manner.
22038 New web-based back ends have been added: @code{nnslashdot},
22039 @code{nnwarchive} and @code{nnultimate}. nnweb has been revamped,
22040 again, to keep up with ever-changing layouts.
22043 Gnus can now read IMAP mail via @code{nnimap}.
22051 @section The Manual
22055 This manual was generated from a TeXinfo file and then run through
22056 either @code{texi2dvi}
22058 or my own home-brewed TeXinfo to \LaTeX\ transformer,
22059 and then run through @code{latex} and @code{dvips}
22061 to get what you hold in your hands now.
22063 The following conventions have been used:
22068 This is a @samp{string}
22071 This is a @kbd{keystroke}
22074 This is a @file{file}
22077 This is a @code{symbol}
22081 So if I were to say ``set @code{flargnoze} to @samp{yes}'', that would
22085 (setq flargnoze "yes")
22088 If I say ``set @code{flumphel} to @code{yes}'', that would mean:
22091 (setq flumphel 'yes)
22094 @samp{yes} and @code{yes} are two @emph{very} different things---don't
22095 ever get them confused.
22099 Of course, everything in this manual is of vital interest, so you should
22100 read it all. Several times. However, if you feel like skimming the
22101 manual, look for that gnu head you should see in the margin over
22102 there---it means that what's being discussed is of more importance than
22103 the rest of the stuff. (On the other hand, if everything is infinitely
22104 important, how can anything be more important than that? Just one more
22105 of the mysteries of this world, I guess.)
22111 @node On Writing Manuals
22112 @section On Writing Manuals
22114 I guess most manuals are written after-the-fact; documenting a program
22115 that's already there. This is not how this manual is written. When
22116 implementing something, I write the manual entry for that something
22117 straight away. I then see that it's difficult to explain the
22118 functionality, so I write how it's supposed to be, and then I change the
22119 implementation. Writing the documentation and writing the code goes
22122 This, of course, means that this manual has no, or little, flow. It
22123 documents absolutely everything in Gnus, but often not where you're
22124 looking for it. It is a reference manual, and not a guide to how to get
22127 That would be a totally different book, that should be written using the
22128 reference manual as source material. It would look quite differently.
22133 @section Terminology
22135 @cindex terminology
22140 This is what you are supposed to use this thing for---reading news.
22141 News is generally fetched from a nearby @sc{nntp} server, and is
22142 generally publicly available to everybody. If you post news, the entire
22143 world is likely to read just what you have written, and they'll all
22144 snigger mischievously. Behind your back.
22148 Everything that's delivered to you personally is mail. Some news/mail
22149 readers (like Gnus) blur the distinction between mail and news, but
22150 there is a difference. Mail is private. News is public. Mailing is
22151 not posting, and replying is not following up.
22155 Send a mail to the person who has written what you are reading.
22159 Post an article to the current newsgroup responding to the article you
22164 Gnus gets fed articles from a number of back ends, both news and mail
22165 back ends. Gnus does not handle the underlying media, so to speak---this
22166 is all done by the back ends.
22170 Gnus will always use one method (and back end) as the @dfn{native}, or
22171 default, way of getting news.
22175 You can also have any number of foreign groups active at the same time.
22176 These are groups that use non-native non-secondary back ends for getting
22181 Secondary back ends are somewhere half-way between being native and being
22182 foreign, but they mostly act like they are native.
22186 A message that has been posted as news.
22189 @cindex mail message
22190 A message that has been mailed.
22194 A mail message or news article
22198 The top part of a message, where administrative information (etc.) is
22203 The rest of an article. Everything not in the head is in the
22208 A line from the head of an article.
22212 A collection of such lines, or a collection of heads. Or even a
22213 collection of @sc{nov} lines.
22217 When Gnus enters a group, it asks the back end for the headers of all
22218 unread articles in the group. Most servers support the News OverView
22219 format, which is more compact and much faster to read and parse than the
22220 normal @sc{head} format.
22224 Each group is subscribed at some @dfn{level} or other (1-9). The ones
22225 that have a lower level are ``more'' subscribed than the groups with a
22226 higher level. In fact, groups on levels 1-5 are considered
22227 @dfn{subscribed}; 6-7 are @dfn{unsubscribed}; 8 are @dfn{zombies}; and 9
22228 are @dfn{killed}. Commands for listing groups and scanning for new
22229 articles will all use the numeric prefix as @dfn{working level}.
22231 @item killed groups
22232 @cindex killed groups
22233 No information on killed groups is stored or updated, which makes killed
22234 groups much easier to handle than subscribed groups.
22236 @item zombie groups
22237 @cindex zombie groups
22238 Just like killed groups, only slightly less dead.
22241 @cindex active file
22242 The news server has to keep track of what articles it carries, and what
22243 groups exist. All this information in stored in the active file, which
22244 is rather large, as you might surmise.
22247 @cindex bogus groups
22248 A group that exists in the @file{.newsrc} file, but isn't known to the
22249 server (i.e., it isn't in the active file), is a @emph{bogus group}.
22250 This means that the group probably doesn't exist (any more).
22253 @cindex activating groups
22254 The act of asking the server for info on a group and computing the
22255 number of unread articles is called @dfn{activating the group}.
22256 Un-activated groups are listed with @samp{*} in the group buffer.
22260 A machine one can connect to and get news (or mail) from.
22262 @item select method
22263 @cindex select method
22264 A structure that specifies the back end, the server and the virtual
22267 @item virtual server
22268 @cindex virtual server
22269 A named select method. Since a select method defines all there is to
22270 know about connecting to a (physical) server, taking the thing as a
22271 whole is a virtual server.
22275 Taking a buffer and running it through a filter of some sort. The
22276 result will (more often than not) be cleaner and more pleasing than the
22279 @item ephemeral groups
22280 @cindex ephemeral groups
22281 Most groups store data on what articles you have read. @dfn{Ephemeral}
22282 groups are groups that will have no data stored---when you exit the
22283 group, it'll disappear into the aether.
22286 @cindex solid groups
22287 This is the opposite of ephemeral groups. All groups listed in the
22288 group buffer are solid groups.
22290 @item sparse articles
22291 @cindex sparse articles
22292 These are article placeholders shown in the summary buffer when
22293 @code{gnus-build-sparse-threads} has been switched on.
22297 To put responses to articles directly after the articles they respond
22298 to---in a hierarchical fashion.
22302 @cindex thread root
22303 The first article in a thread is the root. It is the ancestor of all
22304 articles in the thread.
22308 An article that has responses.
22312 An article that responds to a different article---its parent.
22316 A collection of messages in one file. The most common digest format is
22317 specified by RFC 1153.
22323 @node Customization
22324 @section Customization
22325 @cindex general customization
22327 All variables are properly documented elsewhere in this manual. This
22328 section is designed to give general pointers on how to customize Gnus
22329 for some quite common situations.
22332 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
22333 * Slow Terminal Connection:: You run a remote Emacs.
22334 * Little Disk Space:: You feel that having large setup files is icky.
22335 * Slow Machine:: You feel like buying a faster machine.
22339 @node Slow/Expensive Connection
22340 @subsection Slow/Expensive @sc{nntp} Connection
22342 If you run Emacs on a machine locally, and get your news from a machine
22343 over some very thin strings, you want to cut down on the amount of data
22344 Gnus has to get from the @sc{nntp} server.
22348 @item gnus-read-active-file
22349 Set this to @code{nil}, which will inhibit Gnus from requesting the
22350 entire active file from the server. This file is often v. large. You
22351 also have to set @code{gnus-check-new-newsgroups} and
22352 @code{gnus-check-bogus-newsgroups} to @code{nil} to make sure that Gnus
22353 doesn't suddenly decide to fetch the active file anyway.
22355 @item gnus-nov-is-evil
22356 This one has to be @code{nil}. If not, grabbing article headers from
22357 the @sc{nntp} server will not be very fast. Not all @sc{nntp} servers
22358 support @sc{xover}; Gnus will detect this by itself.
22362 @node Slow Terminal Connection
22363 @subsection Slow Terminal Connection
22365 Let's say you use your home computer for dialing up the system that runs
22366 Emacs and Gnus. If your modem is slow, you want to reduce (as much as
22367 possible) the amount of data sent over the wires.
22371 @item gnus-auto-center-summary
22372 Set this to @code{nil} to inhibit Gnus from re-centering the summary
22373 buffer all the time. If it is @code{vertical}, do only vertical
22374 re-centering. If it is neither @code{nil} nor @code{vertical}, do both
22375 horizontal and vertical recentering.
22377 @item gnus-visible-headers
22378 Cut down on the headers included in the articles to the
22379 minimum. You can, in fact, make do without them altogether---most of the
22380 useful data is in the summary buffer, anyway. Set this variable to
22381 @samp{^NEVVVVER} or @samp{From:}, or whatever you feel you need.
22383 Set this hook to all the available hiding commands:
22385 (setq gnus-treat-hide-headers 'head
22386 gnus-treat-hide-signature t
22387 gnus-treat-hide-citation t)
22390 @item gnus-use-full-window
22391 By setting this to @code{nil}, you can make all the windows smaller.
22392 While this doesn't really cut down much generally, it means that you
22393 have to see smaller portions of articles before deciding that you didn't
22394 want to read them anyway.
22396 @item gnus-thread-hide-subtree
22397 If this is non-@code{nil}, all threads in the summary buffer will be
22401 @item gnus-updated-mode-lines
22402 If this is @code{nil}, Gnus will not put information in the buffer mode
22403 lines, which might save some time.
22407 @node Little Disk Space
22408 @subsection Little Disk Space
22411 The startup files can get rather large, so you may want to cut their
22412 sizes a bit if you are running out of space.
22416 @item gnus-save-newsrc-file
22417 If this is @code{nil}, Gnus will never save @file{.newsrc}---it will
22418 only save @file{.newsrc.eld}. This means that you will not be able to
22419 use any other newsreaders than Gnus. This variable is @code{t} by
22422 @item gnus-read-newsrc-file
22423 If this is @code{nil}, Gnus will never read @file{.newsrc}---it will
22424 only read @file{.newsrc.eld}. This means that you will not be able to
22425 use any other newsreaders than Gnus. This variable is @code{t} by
22428 @item gnus-save-killed-list
22429 If this is @code{nil}, Gnus will not save the list of dead groups. You
22430 should also set @code{gnus-check-new-newsgroups} to @code{ask-server}
22431 and @code{gnus-check-bogus-newsgroups} to @code{nil} if you set this
22432 variable to @code{nil}. This variable is @code{t} by default.
22438 @subsection Slow Machine
22439 @cindex slow machine
22441 If you have a slow machine, or are just really impatient, there are a
22442 few things you can do to make Gnus run faster.
22444 Set @code{gnus-check-new-newsgroups} and
22445 @code{gnus-check-bogus-newsgroups} to @code{nil} to make startup faster.
22447 Set @code{gnus-show-threads}, @code{gnus-use-cross-reference} and
22448 @code{gnus-nov-is-evil} to @code{nil} to make entering and exiting the
22449 summary buffer faster.
22453 @node Troubleshooting
22454 @section Troubleshooting
22455 @cindex troubleshooting
22457 Gnus works @emph{so} well straight out of the box---I can't imagine any
22465 Make sure your computer is switched on.
22468 Make sure that you really load the current Gnus version. If you have
22469 been running @sc{gnus}, you need to exit Emacs and start it up again before
22473 Try doing an @kbd{M-x gnus-version}. If you get something that looks
22474 like @samp{Gnus v5.46; nntp 4.0} you have the right files loaded. If,
22475 on the other hand, you get something like @samp{NNTP 3.x} or @samp{nntp
22476 flee}, you have some old @file{.el} files lying around. Delete these.
22479 Read the help group (@kbd{G h} in the group buffer) for a FAQ and a
22483 @vindex max-lisp-eval-depth
22484 Gnus works on many recursive structures, and in some extreme (and very
22485 rare) cases Gnus may recurse down ``too deeply'' and Emacs will beep at
22486 you. If this happens to you, set @code{max-lisp-eval-depth} to 500 or
22487 something like that.
22490 If all else fails, report the problem as a bug.
22493 @cindex reporting bugs
22495 @kindex M-x gnus-bug
22497 If you find a bug in Gnus, you can report it with the @kbd{M-x gnus-bug}
22498 command. @kbd{M-x set-variable RET debug-on-error RET t RET}, and send
22499 me the backtrace. I will fix bugs, but I can only fix them if you send
22500 me a precise description as to how to reproduce the bug.
22502 You really can never be too detailed in a bug report. Always use the
22503 @kbd{M-x gnus-bug} command when you make bug reports, even if it creates
22504 a 10Kb mail each time you use it, and even if you have sent me your
22505 environment 500 times before. I don't care. I want the full info each
22508 It is also important to remember that I have no memory whatsoever. If
22509 you send a bug report, and I send you a reply, and then you just send
22510 back ``No, it's not! Moron!'', I will have no idea what you are
22511 insulting me about. Always over-explain everything. It's much easier
22512 for all of us---if I don't have all the information I need, I will just
22513 mail you and ask for more info, and everything takes more time.
22515 If the problem you're seeing is very visual, and you can't quite explain
22516 it, copy the Emacs window to a file (with @code{xwd}, for instance), put
22517 it somewhere it can be reached, and include the URL of the picture in
22521 If you would like to contribute a patch to fix bugs or make
22522 improvements, please produce the patch using @samp{diff -u}.
22524 If you just need help, you are better off asking on
22525 @samp{gnu.emacs.gnus}. I'm not very helpful.
22527 @cindex gnu.emacs.gnus
22528 @cindex ding mailing list
22529 You can also ask on the ding mailing list---@samp{ding@@gnus.org}.
22530 Write to @samp{ding-request@@gnus.org} to subscribe.
22534 @node Gnus Reference Guide
22535 @section Gnus Reference Guide
22537 It is my hope that other people will figure out smart stuff that Gnus
22538 can do, and that other people will write those smart things as well. To
22539 facilitate that I thought it would be a good idea to describe the inner
22540 workings of Gnus. And some of the not-so-inner workings, while I'm at
22543 You can never expect the internals of a program not to change, but I
22544 will be defining (in some details) the interface between Gnus and its
22545 back ends (this is written in stone), the format of the score files
22546 (ditto), data structures (some are less likely to change than others)
22547 and general methods of operation.
22550 * Gnus Utility Functions:: Common functions and variable to use.
22551 * Back End Interface:: How Gnus communicates with the servers.
22552 * Score File Syntax:: A BNF definition of the score file standard.
22553 * Headers:: How Gnus stores headers internally.
22554 * Ranges:: A handy format for storing mucho numbers.
22555 * Group Info:: The group info format.
22556 * Extended Interactive:: Symbolic prefixes and stuff.
22557 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
22558 * Various File Formats:: Formats of files that Gnus use.
22562 @node Gnus Utility Functions
22563 @subsection Gnus Utility Functions
22564 @cindex Gnus utility functions
22565 @cindex utility functions
22567 @cindex internal variables
22569 When writing small functions to be run from hooks (and stuff), it's
22570 vital to have access to the Gnus internal functions and variables.
22571 Below is a list of the most common ones.
22575 @item gnus-newsgroup-name
22576 @vindex gnus-newsgroup-name
22577 This variable holds the name of the current newsgroup.
22579 @item gnus-find-method-for-group
22580 @findex gnus-find-method-for-group
22581 A function that returns the select method for @var{group}.
22583 @item gnus-group-real-name
22584 @findex gnus-group-real-name
22585 Takes a full (prefixed) Gnus group name, and returns the unprefixed
22588 @item gnus-group-prefixed-name
22589 @findex gnus-group-prefixed-name
22590 Takes an unprefixed group name and a select method, and returns the full
22591 (prefixed) Gnus group name.
22593 @item gnus-get-info
22594 @findex gnus-get-info
22595 Returns the group info list for @var{group}.
22597 @item gnus-group-unread
22598 @findex gnus-group-unread
22599 The number of unread articles in @var{group}, or @code{t} if that is
22603 @findex gnus-active
22604 The active entry for @var{group}.
22606 @item gnus-set-active
22607 @findex gnus-set-active
22608 Set the active entry for @var{group}.
22610 @item gnus-add-current-to-buffer-list
22611 @findex gnus-add-current-to-buffer-list
22612 Adds the current buffer to the list of buffers to be killed on Gnus
22615 @item gnus-continuum-version
22616 @findex gnus-continuum-version
22617 Takes a Gnus version string as a parameter and returns a floating point
22618 number. Earlier versions will always get a lower number than later
22621 @item gnus-group-read-only-p
22622 @findex gnus-group-read-only-p
22623 Says whether @var{group} is read-only or not.
22625 @item gnus-news-group-p
22626 @findex gnus-news-group-p
22627 Says whether @var{group} came from a news back end.
22629 @item gnus-ephemeral-group-p
22630 @findex gnus-ephemeral-group-p
22631 Says whether @var{group} is ephemeral or not.
22633 @item gnus-server-to-method
22634 @findex gnus-server-to-method
22635 Returns the select method corresponding to @var{server}.
22637 @item gnus-server-equal
22638 @findex gnus-server-equal
22639 Says whether two virtual servers are equal.
22641 @item gnus-group-native-p
22642 @findex gnus-group-native-p
22643 Says whether @var{group} is native or not.
22645 @item gnus-group-secondary-p
22646 @findex gnus-group-secondary-p
22647 Says whether @var{group} is secondary or not.
22649 @item gnus-group-foreign-p
22650 @findex gnus-group-foreign-p
22651 Says whether @var{group} is foreign or not.
22653 @item group-group-find-parameter
22654 @findex group-group-find-parameter
22655 Returns the parameter list of @var{group}. If given a second parameter,
22656 returns the value of that parameter for @var{group}.
22658 @item gnus-group-set-parameter
22659 @findex gnus-group-set-parameter
22660 Takes three parameters; @var{group}, @var{parameter} and @var{value}.
22662 @item gnus-narrow-to-body
22663 @findex gnus-narrow-to-body
22664 Narrows the current buffer to the body of the article.
22666 @item gnus-check-backend-function
22667 @findex gnus-check-backend-function
22668 Takes two parameters, @var{function} and @var{group}. If the back end
22669 @var{group} comes from supports @var{function}, return non-@code{nil}.
22672 (gnus-check-backend-function "request-scan" "nnml:misc")
22676 @item gnus-read-method
22677 @findex gnus-read-method
22678 Prompts the user for a select method.
22683 @node Back End Interface
22684 @subsection Back End Interface
22686 Gnus doesn't know anything about @sc{nntp}, spools, mail or virtual
22687 groups. It only knows how to talk to @dfn{virtual servers}. A virtual
22688 server is a @dfn{back end} and some @dfn{back end variables}. As examples
22689 of the first, we have @code{nntp}, @code{nnspool} and @code{nnmbox}. As
22690 examples of the latter we have @code{nntp-port-number} and
22691 @code{nnmbox-directory}.
22693 When Gnus asks for information from a back end---say @code{nntp}---on
22694 something, it will normally include a virtual server name in the
22695 function parameters. (If not, the back end should use the ``current''
22696 virtual server.) For instance, @code{nntp-request-list} takes a virtual
22697 server as its only (optional) parameter. If this virtual server hasn't
22698 been opened, the function should fail.
22700 Note that a virtual server name has no relation to some physical server
22701 name. Take this example:
22705 (nntp-address "ifi.uio.no")
22706 (nntp-port-number 4324))
22709 Here the virtual server name is @samp{odd-one} while the name of
22710 the physical server is @samp{ifi.uio.no}.
22712 The back ends should be able to switch between several virtual servers.
22713 The standard back ends implement this by keeping an alist of virtual
22714 server environments that they pull down/push up when needed.
22716 There are two groups of interface functions: @dfn{required functions},
22717 which must be present, and @dfn{optional functions}, which Gnus will
22718 always check for presence before attempting to call 'em.
22720 All these functions are expected to return data in the buffer
22721 @code{nntp-server-buffer} (@samp{ *nntpd*}), which is somewhat
22722 unfortunately named, but we'll have to live with it. When I talk about
22723 @dfn{resulting data}, I always refer to the data in that buffer. When I
22724 talk about @dfn{return value}, I talk about the function value returned by
22725 the function call. Functions that fail should return @code{nil} as the
22728 Some back ends could be said to be @dfn{server-forming} back ends, and
22729 some might be said not to be. The latter are back ends that generally
22730 only operate on one group at a time, and have no concept of ``server''
22731 -- they have a group, and they deliver info on that group and nothing
22734 Gnus identifies each message by way of group name and article number. A
22735 few remarks about these article numbers might be useful. First of all,
22736 the numbers are positive integers. Secondly, it is normally not
22737 possible for later articles to `re-use' older article numbers without
22738 confusing Gnus. That is, if a group has ever contained a message
22739 numbered 42, then no other message may get that number, or Gnus will get
22740 mightily confused.@footnote{See the function
22741 @code{nnchoke-request-update-info}, @ref{Optional Back End Functions}.}
22742 Third, article numbers must be assigned in order of arrival in the
22743 group; this is not necessarily the same as the date of the message.
22745 The previous paragraph already mentions all the `hard' restrictions that
22746 article numbers must fulfill. But it seems that it might be useful to
22747 assign @emph{consecutive} article numbers, for Gnus gets quite confused
22748 if there are holes in the article numbering sequence. However, due to
22749 the `no-reuse' restriction, holes cannot be avoided altogether. It's
22750 also useful for the article numbers to start at 1 to avoid running out
22751 of numbers as long as possible.
22753 In the examples and definitions I will refer to the imaginary back end
22756 @cindex @code{nnchoke}
22759 * Required Back End Functions:: Functions that must be implemented.
22760 * Optional Back End Functions:: Functions that need not be implemented.
22761 * Error Messaging:: How to get messages and report errors.
22762 * Writing New Back Ends:: Extending old back ends.
22763 * Hooking New Back Ends Into Gnus:: What has to be done on the Gnus end.
22764 * Mail-like Back Ends:: Some tips on mail back ends.
22768 @node Required Back End Functions
22769 @subsubsection Required Back End Functions
22773 @item (nnchoke-retrieve-headers ARTICLES &optional GROUP SERVER FETCH-OLD)
22775 @var{articles} is either a range of article numbers or a list of
22776 @code{Message-ID}s. Current back ends do not fully support either---only
22777 sequences (lists) of article numbers, and most back ends do not support
22778 retrieval of @code{Message-ID}s. But they should try for both.
22780 The result data should either be HEADs or NOV lines, and the result
22781 value should either be @code{headers} or @code{nov} to reflect this.
22782 This might later be expanded to @code{various}, which will be a mixture
22783 of HEADs and NOV lines, but this is currently not supported by Gnus.
22785 If @var{fetch-old} is non-@code{nil} it says to try fetching "extra
22786 headers", in some meaning of the word. This is generally done by
22787 fetching (at most) @var{fetch-old} extra headers less than the smallest
22788 article number in @code{articles}, and filling the gaps as well. The
22789 presence of this parameter can be ignored if the back end finds it
22790 cumbersome to follow the request. If this is non-@code{nil} and not a
22791 number, do maximum fetches.
22793 Here's an example HEAD:
22796 221 1056 Article retrieved.
22797 Path: ifi.uio.no!sturles
22798 From: sturles@@ifi.uio.no (Sturle Sunde)
22799 Newsgroups: ifi.discussion
22800 Subject: Re: Something very droll
22801 Date: 27 Oct 1994 14:02:57 +0100
22802 Organization: Dept. of Informatics, University of Oslo, Norway
22804 Message-ID: <38o8e1$a0o@@holmenkollen.ifi.uio.no>
22805 References: <38jdmq$4qu@@visbur.ifi.uio.no>
22806 NNTP-Posting-Host: holmenkollen.ifi.uio.no
22810 So a @code{headers} return value would imply that there's a number of
22811 these in the data buffer.
22813 Here's a BNF definition of such a buffer:
22817 head = error / valid-head
22818 error-message = [ "4" / "5" ] 2number " " <error message> eol
22819 valid-head = valid-message *header "." eol
22820 valid-message = "221 " <number> " Article retrieved." eol
22821 header = <text> eol
22824 If the return value is @code{nov}, the data buffer should contain
22825 @dfn{network overview database} lines. These are basically fields
22829 nov-buffer = *nov-line
22830 nov-line = 8*9 [ field <TAB> ] eol
22831 field = <text except TAB>
22834 For a closer look at what should be in those fields,
22838 @item (nnchoke-open-server SERVER &optional DEFINITIONS)
22840 @var{server} is here the virtual server name. @var{definitions} is a
22841 list of @code{(VARIABLE VALUE)} pairs that define this virtual server.
22843 If the server can't be opened, no error should be signaled. The back end
22844 may then choose to refuse further attempts at connecting to this
22845 server. In fact, it should do so.
22847 If the server is opened already, this function should return a
22848 non-@code{nil} value. There should be no data returned.
22851 @item (nnchoke-close-server &optional SERVER)
22853 Close connection to @var{server} and free all resources connected
22854 to it. Return @code{nil} if the server couldn't be closed for some
22857 There should be no data returned.
22860 @item (nnchoke-request-close)
22862 Close connection to all servers and free all resources that the back end
22863 have reserved. All buffers that have been created by that back end
22864 should be killed. (Not the @code{nntp-server-buffer}, though.) This
22865 function is generally only called when Gnus is shutting down.
22867 There should be no data returned.
22870 @item (nnchoke-server-opened &optional SERVER)
22872 If @var{server} is the current virtual server, and the connection to the
22873 physical server is alive, then this function should return a
22874 non-@code{nil} vlue. This function should under no circumstances
22875 attempt to reconnect to a server we have lost connection to.
22877 There should be no data returned.
22880 @item (nnchoke-status-message &optional SERVER)
22882 This function should return the last error message from @var{server}.
22884 There should be no data returned.
22887 @item (nnchoke-request-article ARTICLE &optional GROUP SERVER TO-BUFFER)
22889 The result data from this function should be the article specified by
22890 @var{article}. This might either be a @code{Message-ID} or a number.
22891 It is optional whether to implement retrieval by @code{Message-ID}, but
22892 it would be nice if that were possible.
22894 If @var{to-buffer} is non-@code{nil}, the result data should be returned
22895 in this buffer instead of the normal data buffer. This is to make it
22896 possible to avoid copying large amounts of data from one buffer to
22897 another, while Gnus mainly requests articles to be inserted directly
22898 into its article buffer.
22900 If it is at all possible, this function should return a cons cell where
22901 the @code{car} is the group name the article was fetched from, and the @code{cdr} is
22902 the article number. This will enable Gnus to find out what the real
22903 group and article numbers are when fetching articles by
22904 @code{Message-ID}. If this isn't possible, @code{t} should be returned
22905 on successful article retrieval.
22908 @item (nnchoke-request-group GROUP &optional SERVER FAST)
22910 Get data on @var{group}. This function also has the side effect of
22911 making @var{group} the current group.
22913 If @var{fast}, don't bother to return useful data, just make @var{group}
22916 Here's an example of some result data and a definition of the same:
22919 211 56 1000 1059 ifi.discussion
22922 The first number is the status, which should be 211. Next is the
22923 total number of articles in the group, the lowest article number, the
22924 highest article number, and finally the group name. Note that the total
22925 number of articles may be less than one might think while just
22926 considering the highest and lowest article numbers, but some articles
22927 may have been canceled. Gnus just discards the total-number, so
22928 whether one should take the bother to generate it properly (if that is a
22929 problem) is left as an exercise to the reader.
22932 group-status = [ error / info ] eol
22933 error = [ "4" / "5" ] 2<number> " " <Error message>
22934 info = "211 " 3* [ <number> " " ] <string>
22938 @item (nnchoke-close-group GROUP &optional SERVER)
22940 Close @var{group} and free any resources connected to it. This will be
22941 a no-op on most back ends.
22943 There should be no data returned.
22946 @item (nnchoke-request-list &optional SERVER)
22948 Return a list of all groups available on @var{server}. And that means
22951 Here's an example from a server that only carries two groups:
22954 ifi.test 0000002200 0000002000 y
22955 ifi.discussion 3324 3300 n
22958 On each line we have a group name, then the highest article number in
22959 that group, the lowest article number, and finally a flag.
22962 active-file = *active-line
22963 active-line = name " " <number> " " <number> " " flags eol
22965 flags = "n" / "y" / "m" / "x" / "j" / "=" name
22968 The flag says whether the group is read-only (@samp{n}), is moderated
22969 (@samp{m}), is dead (@samp{x}), is aliased to some other group
22970 (@samp{=other-group}) or none of the above (@samp{y}).
22973 @item (nnchoke-request-post &optional SERVER)
22975 This function should post the current buffer. It might return whether
22976 the posting was successful or not, but that's not required. If, for
22977 instance, the posting is done asynchronously, it has generally not been
22978 completed by the time this function concludes. In that case, this
22979 function should set up some kind of sentinel to beep the user loud and
22980 clear if the posting could not be completed.
22982 There should be no result data from this function.
22987 @node Optional Back End Functions
22988 @subsubsection Optional Back End Functions
22992 @item (nnchoke-retrieve-groups GROUPS &optional SERVER)
22994 @var{groups} is a list of groups, and this function should request data
22995 on all those groups. How it does it is of no concern to Gnus, but it
22996 should attempt to do this in a speedy fashion.
22998 The return value of this function can be either @code{active} or
22999 @code{group}, which says what the format of the result data is. The
23000 former is in the same format as the data from
23001 @code{nnchoke-request-list}, while the latter is a buffer full of lines
23002 in the same format as @code{nnchoke-request-group} gives.
23005 group-buffer = *active-line / *group-status
23009 @item (nnchoke-request-update-info GROUP INFO &optional SERVER)
23011 A Gnus group info (@pxref{Group Info}) is handed to the back end for
23012 alterations. This comes in handy if the back end really carries all the
23013 information (as is the case with virtual and imap groups). This
23014 function should destructively alter the info to suit its needs, and
23015 should return the (altered) group info.
23017 There should be no result data from this function.
23020 @item (nnchoke-request-type GROUP &optional ARTICLE)
23022 When the user issues commands for ``sending news'' (@kbd{F} in the
23023 summary buffer, for instance), Gnus has to know whether the article the
23024 user is following up on is news or mail. This function should return
23025 @code{news} if @var{article} in @var{group} is news, @code{mail} if it
23026 is mail and @code{unknown} if the type can't be decided. (The
23027 @var{article} parameter is necessary in @code{nnvirtual} groups which
23028 might very well combine mail groups and news groups.) Both @var{group}
23029 and @var{article} may be @code{nil}.
23031 There should be no result data from this function.
23034 @item (nnchoke-request-set-mark GROUP ACTION &optional SERVER)
23036 Set/remove/add marks on articles. Normally Gnus handles the article
23037 marks (such as read, ticked, expired etc) internally, and store them in
23038 @code{~/.newsrc.eld}. Some back ends (such as @sc{imap}) however carry
23039 all information about the articles on the server, so Gnus need to
23040 propagate the mark information to the server.
23042 ACTION is a list of mark setting requests, having this format:
23045 (RANGE ACTION MARK)
23048 RANGE is a range of articles you wish to update marks on. ACTION is
23049 @code{add} or @code{del}, used to add marks or remove marks
23050 (preserving all marks not mentioned). MARK is a list of marks; where
23051 each mark is a symbol. Currently used marks are @code{read},
23052 @code{tick}, @code{reply}, @code{expire}, @code{killed},
23053 @code{dormant}, @code{save}, @code{download}, @code{unsend},
23054 @code{forward} and @code{recent}, but your back end should, if
23055 possible, not limit itself to these.
23057 Given contradictory actions, the last action in the list should be the
23058 effective one. That is, if your action contains a request to add the
23059 @code{tick} mark on article 1 and, later in the list, a request to
23060 remove the mark on the same article, the mark should in fact be removed.
23062 An example action list:
23065 (((5 12 30) 'del '(tick))
23066 ((10 . 90) 'add '(read expire))
23067 ((92 94) 'del '(read)))
23070 The function should return a range of articles it wasn't able to set the
23071 mark on (currently not used for anything).
23073 There should be no result data from this function.
23075 @item (nnchoke-request-update-mark GROUP ARTICLE MARK)
23077 If the user tries to set a mark that the back end doesn't like, this
23078 function may change the mark. Gnus will use whatever this function
23079 returns as the mark for @var{article} instead of the original
23080 @var{mark}. If the back end doesn't care, it must return the original
23081 @var{mark}, and not @code{nil} or any other type of garbage.
23083 The only use for this I can see is what @code{nnvirtual} does with
23084 it---if a component group is auto-expirable, marking an article as read
23085 in the virtual group should result in the article being marked as
23088 There should be no result data from this function.
23091 @item (nnchoke-request-scan &optional GROUP SERVER)
23093 This function may be called at any time (by Gnus or anything else) to
23094 request that the back end check for incoming articles, in one way or
23095 another. A mail back end will typically read the spool file or query the
23096 POP server when this function is invoked. The @var{group} doesn't have
23097 to be heeded---if the back end decides that it is too much work just
23098 scanning for a single group, it may do a total scan of all groups. It
23099 would be nice, however, to keep things local if that's practical.
23101 There should be no result data from this function.
23104 @item (nnchoke-request-group-description GROUP &optional SERVER)
23106 The result data from this function should be a description of
23110 description-line = name <TAB> description eol
23112 description = <text>
23115 @item (nnchoke-request-list-newsgroups &optional SERVER)
23117 The result data from this function should be the description of all
23118 groups available on the server.
23121 description-buffer = *description-line
23125 @item (nnchoke-request-newgroups DATE &optional SERVER)
23127 The result data from this function should be all groups that were
23128 created after @samp{date}, which is in normal human-readable date format
23129 (i.e., the date format used in mail and news headers, and returned by
23130 the function @code{message-make-date} by default). The data should be
23131 in the active buffer format.
23133 It is okay for this function to return `too many' groups; some back ends
23134 might find it cheaper to return the full list of groups, rather than
23135 just the new groups. But don't do this for back ends with many groups.
23136 Normally, if the user creates the groups herself, there won't be too
23137 many groups, so nnml and the like are probably safe. But for back ends
23138 like nntp, where the groups have been created by the server, it is quite
23139 likely that there can be many groups.
23142 @item (nnchoke-request-create-group GROUP &optional SERVER)
23144 This function should create an empty group with name @var{group}.
23146 There should be no return data.
23149 @item (nnchoke-request-expire-articles ARTICLES &optional GROUP SERVER FORCE)
23151 This function should run the expiry process on all articles in the
23152 @var{articles} range (which is currently a simple list of article
23153 numbers.) It is left up to the back end to decide how old articles
23154 should be before they are removed by this function. If @var{force} is
23155 non-@code{nil}, all @var{articles} should be deleted, no matter how new
23158 This function should return a list of articles that it did not/was not
23161 There should be no result data returned.
23164 @item (nnchoke-request-move-article ARTICLE GROUP SERVER ACCEPT-FORM
23167 This function should move @var{article} (which is a number) from
23168 @var{group} by calling @var{accept-form}.
23170 This function should ready the article in question for moving by
23171 removing any header lines it has added to the article, and generally
23172 should ``tidy up'' the article. Then it should @code{eval}
23173 @var{accept-form} in the buffer where the ``tidy'' article is. This
23174 will do the actual copying. If this @code{eval} returns a
23175 non-@code{nil} value, the article should be removed.
23177 If @var{last} is @code{nil}, that means that there is a high likelihood
23178 that there will be more requests issued shortly, so that allows some
23181 The function should return a cons where the @code{car} is the group name and
23182 the @code{cdr} is the article number that the article was entered as.
23184 There should be no data returned.
23187 @item (nnchoke-request-accept-article GROUP &optional SERVER LAST)
23189 This function takes the current buffer and inserts it into @var{group}.
23190 If @var{last} in @code{nil}, that means that there will be more calls to
23191 this function in short order.
23193 The function should return a cons where the @code{car} is the group name and
23194 the @code{cdr} is the article number that the article was entered as.
23196 There should be no data returned.
23199 @item (nnchoke-request-replace-article ARTICLE GROUP BUFFER)
23201 This function should remove @var{article} (which is a number) from
23202 @var{group} and insert @var{buffer} there instead.
23204 There should be no data returned.
23207 @item (nnchoke-request-delete-group GROUP FORCE &optional SERVER)
23209 This function should delete @var{group}. If @var{force}, it should
23210 really delete all the articles in the group, and then delete the group
23211 itself. (If there is such a thing as ``the group itself''.)
23213 There should be no data returned.
23216 @item (nnchoke-request-rename-group GROUP NEW-NAME &optional SERVER)
23218 This function should rename @var{group} into @var{new-name}. All
23219 articles in @var{group} should move to @var{new-name}.
23221 There should be no data returned.
23226 @node Error Messaging
23227 @subsubsection Error Messaging
23229 @findex nnheader-report
23230 @findex nnheader-get-report
23231 The back ends should use the function @code{nnheader-report} to report
23232 error conditions---they should not raise errors when they aren't able to
23233 perform a request. The first argument to this function is the back end
23234 symbol, and the rest are interpreted as arguments to @code{format} if
23235 there are multiple of them, or just a string if there is one of them.
23236 This function must always returns @code{nil}.
23239 (nnheader-report 'nnchoke "You did something totally bogus")
23241 (nnheader-report 'nnchoke "Could not request group %s" group)
23244 Gnus, in turn, will call @code{nnheader-get-report} when it gets a
23245 @code{nil} back from a server, and this function returns the most
23246 recently reported message for the back end in question. This function
23247 takes one argument---the server symbol.
23249 Internally, these functions access @var{back-end}@code{-status-string},
23250 so the @code{nnchoke} back end will have its error message stored in
23251 @code{nnchoke-status-string}.
23254 @node Writing New Back Ends
23255 @subsubsection Writing New Back Ends
23257 Many back ends are quite similar. @code{nnml} is just like
23258 @code{nnspool}, but it allows you to edit the articles on the server.
23259 @code{nnmh} is just like @code{nnml}, but it doesn't use an active file,
23260 and it doesn't maintain overview databases. @code{nndir} is just like
23261 @code{nnml}, but it has no concept of ``groups'', and it doesn't allow
23264 It would make sense if it were possible to ``inherit'' functions from
23265 back ends when writing new back ends. And, indeed, you can do that if you
23266 want to. (You don't have to if you don't want to, of course.)
23268 All the back ends declare their public variables and functions by using a
23269 package called @code{nnoo}.
23271 To inherit functions from other back ends (and allow other back ends to
23272 inherit functions from the current back end), you should use the
23278 This macro declares the first parameter to be a child of the subsequent
23279 parameters. For instance:
23282 (nnoo-declare nndir
23286 @code{nndir} has declared here that it intends to inherit functions from
23287 both @code{nnml} and @code{nnmh}.
23290 This macro is equivalent to @code{defvar}, but registers the variable as
23291 a public server variable. Most state-oriented variables should be
23292 declared with @code{defvoo} instead of @code{defvar}.
23294 In addition to the normal @code{defvar} parameters, it takes a list of
23295 variables in the parent back ends to map the variable to when executing
23296 a function in those back ends.
23299 (defvoo nndir-directory nil
23300 "Where nndir will look for groups."
23301 nnml-current-directory nnmh-current-directory)
23304 This means that @code{nnml-current-directory} will be set to
23305 @code{nndir-directory} when an @code{nnml} function is called on behalf
23306 of @code{nndir}. (The same with @code{nnmh}.)
23308 @item nnoo-define-basics
23309 This macro defines some common functions that almost all back ends should
23313 (nnoo-define-basics nndir)
23317 This macro is just like @code{defun} and takes the same parameters. In
23318 addition to doing the normal @code{defun} things, it registers the
23319 function as being public so that other back ends can inherit it.
23321 @item nnoo-map-functions
23322 This macro allows mapping of functions from the current back end to
23323 functions from the parent back ends.
23326 (nnoo-map-functions nndir
23327 (nnml-retrieve-headers 0 nndir-current-group 0 0)
23328 (nnmh-request-article 0 nndir-current-group 0 0))
23331 This means that when @code{nndir-retrieve-headers} is called, the first,
23332 third, and fourth parameters will be passed on to
23333 @code{nnml-retrieve-headers}, while the second parameter is set to the
23334 value of @code{nndir-current-group}.
23337 This macro allows importing functions from back ends. It should be the
23338 last thing in the source file, since it will only define functions that
23339 haven't already been defined.
23345 nnmh-request-newgroups)
23349 This means that calls to @code{nndir-request-list} should just be passed
23350 on to @code{nnmh-request-list}, while all public functions from
23351 @code{nnml} that haven't been defined in @code{nndir} yet should be
23356 Below is a slightly shortened version of the @code{nndir} back end.
23359 ;;; nndir.el --- single directory newsgroup access for Gnus
23360 ;; Copyright (C) 1995,96 Free Software Foundation, Inc.
23364 (require 'nnheader)
23368 (eval-when-compile (require 'cl))
23370 (nnoo-declare nndir
23373 (defvoo nndir-directory nil
23374 "Where nndir will look for groups."
23375 nnml-current-directory nnmh-current-directory)
23377 (defvoo nndir-nov-is-evil nil
23378 "*Non-nil means that nndir will never retrieve NOV headers."
23381 (defvoo nndir-current-group ""
23383 nnml-current-group nnmh-current-group)
23384 (defvoo nndir-top-directory nil nil nnml-directory nnmh-directory)
23385 (defvoo nndir-get-new-mail nil nil nnml-get-new-mail nnmh-get-new-mail)
23387 (defvoo nndir-status-string "" nil nnmh-status-string)
23388 (defconst nndir-version "nndir 1.0")
23390 ;;; Interface functions.
23392 (nnoo-define-basics nndir)
23394 (deffoo nndir-open-server (server &optional defs)
23395 (setq nndir-directory
23396 (or (cadr (assq 'nndir-directory defs))
23398 (unless (assq 'nndir-directory defs)
23399 (push `(nndir-directory ,server) defs))
23400 (push `(nndir-current-group
23401 ,(file-name-nondirectory
23402 (directory-file-name nndir-directory)))
23404 (push `(nndir-top-directory
23405 ,(file-name-directory (directory-file-name nndir-directory)))
23407 (nnoo-change-server 'nndir server defs))
23409 (nnoo-map-functions nndir
23410 (nnml-retrieve-headers 0 nndir-current-group 0 0)
23411 (nnmh-request-article 0 nndir-current-group 0 0)
23412 (nnmh-request-group nndir-current-group 0 0)
23413 (nnmh-close-group nndir-current-group 0))
23417 nnmh-status-message
23419 nnmh-request-newgroups))
23425 @node Hooking New Back Ends Into Gnus
23426 @subsubsection Hooking New Back Ends Into Gnus
23428 @vindex gnus-valid-select-methods
23429 @findex gnus-declare-backend
23430 Having Gnus start using your new back end is rather easy---you just
23431 declare it with the @code{gnus-declare-backend} functions. This will
23432 enter the back end into the @code{gnus-valid-select-methods} variable.
23434 @code{gnus-declare-backend} takes two parameters---the back end name and
23435 an arbitrary number of @dfn{abilities}.
23440 (gnus-declare-backend "nnchoke" 'mail 'respool 'address)
23443 The above line would then go in the @file{nnchoke.el} file.
23445 The abilities can be:
23449 This is a mailish back end---followups should (probably) go via mail.
23451 This is a newsish back end---followups should (probably) go via news.
23453 This back end supports both mail and news.
23455 This is neither a post nor mail back end---it's something completely
23458 It supports respooling---or rather, it is able to modify its source
23459 articles and groups.
23461 The name of the server should be in the virtual server name. This is
23462 true for almost all back ends.
23463 @item prompt-address
23464 The user should be prompted for an address when doing commands like
23465 @kbd{B} in the group buffer. This is true for back ends like
23466 @code{nntp}, but not @code{nnmbox}, for instance.
23470 @node Mail-like Back Ends
23471 @subsubsection Mail-like Back Ends
23473 One of the things that separate the mail back ends from the rest of the
23474 back ends is the heavy dependence by the mail back ends on common
23475 functions in @file{nnmail.el}. For instance, here's the definition of
23476 @code{nnml-request-scan}:
23479 (deffoo nnml-request-scan (&optional group server)
23480 (setq nnml-article-file-alist nil)
23481 (nnmail-get-new-mail 'nnml 'nnml-save-nov nnml-directory group))
23484 It simply calls @code{nnmail-get-new-mail} with a few parameters,
23485 and @code{nnmail} takes care of all the moving and splitting of the
23488 This function takes four parameters.
23492 This should be a symbol to designate which back end is responsible for
23495 @item exit-function
23496 This function should be called after the splitting has been performed.
23498 @item temp-directory
23499 Where the temporary files should be stored.
23502 This optional argument should be a group name if the splitting is to be
23503 performed for one group only.
23506 @code{nnmail-get-new-mail} will call @var{back-end}@code{-save-mail} to
23507 save each article. @var{back-end}@code{-active-number} will be called to
23508 find the article number assigned to this article.
23510 The function also uses the following variables:
23511 @var{back-end}@code{-get-new-mail} (to see whether to get new mail for
23512 this back end); and @var{back-end}@code{-group-alist} and
23513 @var{back-end}@code{-active-file} to generate the new active file.
23514 @var{back-end}@code{-group-alist} should be a group-active alist, like
23518 (("a-group" (1 . 10))
23519 ("some-group" (34 . 39)))
23523 @node Score File Syntax
23524 @subsection Score File Syntax
23526 Score files are meant to be easily parseable, but yet extremely
23527 mallable. It was decided that something that had the same read syntax
23528 as an Emacs Lisp list would fit that spec.
23530 Here's a typical score file:
23534 ("win95" -10000 nil s)
23541 BNF definition of a score file:
23544 score-file = "" / "(" *element ")"
23545 element = rule / atom
23546 rule = string-rule / number-rule / date-rule
23547 string-rule = "(" quote string-header quote space *string-match ")"
23548 number-rule = "(" quote number-header quote space *number-match ")"
23549 date-rule = "(" quote date-header quote space *date-match ")"
23551 string-header = "subject" / "from" / "references" / "message-id" /
23552 "xref" / "body" / "head" / "all" / "followup"
23553 number-header = "lines" / "chars"
23554 date-header = "date"
23555 string-match = "(" quote <string> quote [ "" / [ space score [ "" /
23556 space date [ "" / [ space string-match-t ] ] ] ] ] ")"
23557 score = "nil" / <integer>
23558 date = "nil" / <natural number>
23559 string-match-t = "nil" / "s" / "substring" / "S" / "Substring" /
23560 "r" / "regex" / "R" / "Regex" /
23561 "e" / "exact" / "E" / "Exact" /
23562 "f" / "fuzzy" / "F" / "Fuzzy"
23563 number-match = "(" <integer> [ "" / [ space score [ "" /
23564 space date [ "" / [ space number-match-t ] ] ] ] ] ")"
23565 number-match-t = "nil" / "=" / "<" / ">" / ">=" / "<="
23566 date-match = "(" quote <string> quote [ "" / [ space score [ "" /
23567 space date [ "" / [ space date-match-t ] ] ] ] ")"
23568 date-match-t = "nil" / "at" / "before" / "after"
23569 atom = "(" [ required-atom / optional-atom ] ")"
23570 required-atom = mark / expunge / mark-and-expunge / files /
23571 exclude-files / read-only / touched
23572 optional-atom = adapt / local / eval
23573 mark = "mark" space nil-or-number
23574 nil-or-number = "nil" / <integer>
23575 expunge = "expunge" space nil-or-number
23576 mark-and-expunge = "mark-and-expunge" space nil-or-number
23577 files = "files" *[ space <string> ]
23578 exclude-files = "exclude-files" *[ space <string> ]
23579 read-only = "read-only" [ space "nil" / space "t" ]
23580 adapt = "adapt" [ space "ignore" / space "t" / space adapt-rule ]
23581 adapt-rule = "(" *[ <string> *[ "(" <string> <integer> ")" ] ")"
23582 local = "local" *[ space "(" <string> space <form> ")" ]
23583 eval = "eval" space <form>
23584 space = *[ " " / <TAB> / <NEWLINE> ]
23587 Any unrecognized elements in a score file should be ignored, but not
23590 As you can see, white space is needed, but the type and amount of white
23591 space is irrelevant. This means that formatting of the score file is
23592 left up to the programmer---if it's simpler to just spew it all out on
23593 one looong line, then that's ok.
23595 The meaning of the various atoms are explained elsewhere in this
23596 manual (@pxref{Score File Format}).
23600 @subsection Headers
23602 Internally Gnus uses a format for storing article headers that
23603 corresponds to the @sc{nov} format in a mysterious fashion. One could
23604 almost suspect that the author looked at the @sc{nov} specification and
23605 just shamelessly @emph{stole} the entire thing, and one would be right.
23607 @dfn{Header} is a severely overloaded term. ``Header'' is used in
23608 RFC 1036 to talk about lines in the head of an article (e.g.,
23609 @code{From}). It is used by many people as a synonym for
23610 ``head''---``the header and the body''. (That should be avoided, in my
23611 opinion.) And Gnus uses a format internally that it calls ``header'',
23612 which is what I'm talking about here. This is a 9-element vector,
23613 basically, with each header (ouch) having one slot.
23615 These slots are, in order: @code{number}, @code{subject}, @code{from},
23616 @code{date}, @code{id}, @code{references}, @code{chars}, @code{lines},
23617 @code{xref}, and @code{extra}. There are macros for accessing and
23618 setting these slots---they all have predictable names beginning with
23619 @code{mail-header-} and @code{mail-header-set-}, respectively.
23621 All these slots contain strings, except the @code{extra} slot, which
23622 contains an alist of header/value pairs (@pxref{To From Newsgroups}).
23628 @sc{gnus} introduced a concept that I found so useful that I've started
23629 using it a lot and have elaborated on it greatly.
23631 The question is simple: If you have a large amount of objects that are
23632 identified by numbers (say, articles, to take a @emph{wild} example)
23633 that you want to qualify as being ``included'', a normal sequence isn't
23634 very useful. (A 200,000 length sequence is a bit long-winded.)
23636 The solution is as simple as the question: You just collapse the
23640 (1 2 3 4 5 6 10 11 12)
23643 is transformed into
23646 ((1 . 6) (10 . 12))
23649 To avoid having those nasty @samp{(13 . 13)} elements to denote a
23650 lonesome object, a @samp{13} is a valid element:
23653 ((1 . 6) 7 (10 . 12))
23656 This means that comparing two ranges to find out whether they are equal
23657 is slightly tricky:
23660 ((1 . 5) 7 8 (10 . 12))
23666 ((1 . 5) (7 . 8) (10 . 12))
23669 are equal. In fact, any non-descending list is a range:
23675 is a perfectly valid range, although a pretty long-winded one. This is
23682 and is equal to the previous range.
23684 Here's a BNF definition of ranges. Of course, one must remember the
23685 semantic requirement that the numbers are non-descending. (Any number
23686 of repetition of the same number is allowed, but apt to disappear in
23690 range = simple-range / normal-range
23691 simple-range = "(" number " . " number ")"
23692 normal-range = "(" start-contents ")"
23693 contents = "" / simple-range *[ " " contents ] /
23694 number *[ " " contents ]
23697 Gnus currently uses ranges to keep track of read articles and article
23698 marks. I plan on implementing a number of range operators in C if The
23699 Powers That Be are willing to let me. (I haven't asked yet, because I
23700 need to do some more thinking on what operators I need to make life
23701 totally range-based without ever having to convert back to normal
23706 @subsection Group Info
23708 Gnus stores all permanent info on groups in a @dfn{group info} list.
23709 This list is from three to six elements (or more) long and exhaustively
23710 describes the group.
23712 Here are two example group infos; one is a very simple group while the
23713 second is a more complex one:
23716 ("no.group" 5 ((1 . 54324)))
23718 ("nnml:my.mail" 3 ((1 . 5) 9 (20 . 55))
23719 ((tick (15 . 19)) (replied 3 6 (19 . 3)))
23721 ((auto-expire . t) (to-address . "ding@@gnus.org")))
23724 The first element is the @dfn{group name}---as Gnus knows the group,
23725 anyway. The second element is the @dfn{subscription level}, which
23726 normally is a small integer. (It can also be the @dfn{rank}, which is a
23727 cons cell where the @code{car} is the level and the @code{cdr} is the
23728 score.) The third element is a list of ranges of read articles. The
23729 fourth element is a list of lists of article marks of various kinds.
23730 The fifth element is the select method (or virtual server, if you like).
23731 The sixth element is a list of @dfn{group parameters}, which is what
23732 this section is about.
23734 Any of the last three elements may be missing if they are not required.
23735 In fact, the vast majority of groups will normally only have the first
23736 three elements, which saves quite a lot of cons cells.
23738 Here's a BNF definition of the group info format:
23741 info = "(" group space ralevel space read
23742 [ "" / [ space marks-list [ "" / [ space method [ "" /
23743 space parameters ] ] ] ] ] ")"
23744 group = quote <string> quote
23745 ralevel = rank / level
23746 level = <integer in the range of 1 to inf>
23747 rank = "(" level "." score ")"
23748 score = <integer in the range of 1 to inf>
23750 marks-lists = nil / "(" *marks ")"
23751 marks = "(" <string> range ")"
23752 method = "(" <string> *elisp-forms ")"
23753 parameters = "(" *elisp-forms ")"
23756 Actually that @samp{marks} rule is a fib. A @samp{marks} is a
23757 @samp{<string>} consed on to a @samp{range}, but that's a bitch to say
23760 If you have a Gnus info and want to access the elements, Gnus offers a
23761 series of macros for getting/setting these elements.
23764 @item gnus-info-group
23765 @itemx gnus-info-set-group
23766 @findex gnus-info-group
23767 @findex gnus-info-set-group
23768 Get/set the group name.
23770 @item gnus-info-rank
23771 @itemx gnus-info-set-rank
23772 @findex gnus-info-rank
23773 @findex gnus-info-set-rank
23774 Get/set the group rank (@pxref{Group Score}).
23776 @item gnus-info-level
23777 @itemx gnus-info-set-level
23778 @findex gnus-info-level
23779 @findex gnus-info-set-level
23780 Get/set the group level.
23782 @item gnus-info-score
23783 @itemx gnus-info-set-score
23784 @findex gnus-info-score
23785 @findex gnus-info-set-score
23786 Get/set the group score (@pxref{Group Score}).
23788 @item gnus-info-read
23789 @itemx gnus-info-set-read
23790 @findex gnus-info-read
23791 @findex gnus-info-set-read
23792 Get/set the ranges of read articles.
23794 @item gnus-info-marks
23795 @itemx gnus-info-set-marks
23796 @findex gnus-info-marks
23797 @findex gnus-info-set-marks
23798 Get/set the lists of ranges of marked articles.
23800 @item gnus-info-method
23801 @itemx gnus-info-set-method
23802 @findex gnus-info-method
23803 @findex gnus-info-set-method
23804 Get/set the group select method.
23806 @item gnus-info-params
23807 @itemx gnus-info-set-params
23808 @findex gnus-info-params
23809 @findex gnus-info-set-params
23810 Get/set the group parameters.
23813 All the getter functions take one parameter---the info list. The setter
23814 functions take two parameters---the info list and the new value.
23816 The last three elements in the group info aren't mandatory, so it may be
23817 necessary to extend the group info before setting the element. If this
23818 is necessary, you can just pass on a non-@code{nil} third parameter to
23819 the three final setter functions to have this happen automatically.
23822 @node Extended Interactive
23823 @subsection Extended Interactive
23824 @cindex interactive
23825 @findex gnus-interactive
23827 Gnus extends the standard Emacs @code{interactive} specification
23828 slightly to allow easy use of the symbolic prefix (@pxref{Symbolic
23829 Prefixes}). Here's an example of how this is used:
23832 (defun gnus-summary-increase-score (&optional score symp)
23833 (interactive (gnus-interactive "P\ny"))
23838 The best thing to do would have been to implement
23839 @code{gnus-interactive} as a macro which would have returned an
23840 @code{interactive} form, but this isn't possible since Emacs checks
23841 whether a function is interactive or not by simply doing an @code{assq}
23842 on the lambda form. So, instead we have @code{gnus-interactive}
23843 function that takes a string and returns values that are usable to
23844 @code{interactive}.
23846 This function accepts (almost) all normal @code{interactive} specs, but
23851 @vindex gnus-current-prefix-symbol
23852 The current symbolic prefix---the @code{gnus-current-prefix-symbol}
23856 @vindex gnus-current-prefix-symbols
23857 A list of the current symbolic prefixes---the
23858 @code{gnus-current-prefix-symbol} variable.
23861 The current article number---the @code{gnus-summary-article-number}
23865 The current article header---the @code{gnus-summary-article-header}
23869 The current group name---the @code{gnus-group-group-name}
23875 @node Emacs/XEmacs Code
23876 @subsection Emacs/XEmacs Code
23880 While Gnus runs under Emacs, XEmacs and Mule, I decided that one of the
23881 platforms must be the primary one. I chose Emacs. Not because I don't
23882 like XEmacs or Mule, but because it comes first alphabetically.
23884 This means that Gnus will byte-compile under Emacs with nary a warning,
23885 while XEmacs will pump out gigabytes of warnings while byte-compiling.
23886 As I use byte-compilation warnings to help me root out trivial errors in
23887 Gnus, that's very useful.
23889 I've also consistently used Emacs function interfaces, but have used
23890 Gnusey aliases for the functions. To take an example: Emacs defines a
23891 @code{run-at-time} function while XEmacs defines a @code{start-itimer}
23892 function. I then define a function called @code{gnus-run-at-time} that
23893 takes the same parameters as the Emacs @code{run-at-time}. When running
23894 Gnus under Emacs, the former function is just an alias for the latter.
23895 However, when running under XEmacs, the former is an alias for the
23896 following function:
23899 (defun gnus-xmas-run-at-time (time repeat function &rest args)
23903 (,function ,@@args))
23907 This sort of thing has been done for bunches of functions. Gnus does
23908 not redefine any native Emacs functions while running under XEmacs---it
23909 does this @code{defalias} thing with Gnus equivalents instead. Cleaner
23912 In the cases where the XEmacs function interface was obviously cleaner,
23913 I used it instead. For example @code{gnus-region-active-p} is an alias
23914 for @code{region-active-p} in XEmacs, whereas in Emacs it is a function.
23916 Of course, I could have chosen XEmacs as my native platform and done
23917 mapping functions the other way around. But I didn't. The performance
23918 hit these indirections impose on Gnus under XEmacs should be slight.
23921 @node Various File Formats
23922 @subsection Various File Formats
23925 * Active File Format:: Information on articles and groups available.
23926 * Newsgroups File Format:: Group descriptions.
23930 @node Active File Format
23931 @subsubsection Active File Format
23933 The active file lists all groups available on the server in
23934 question. It also lists the highest and lowest current article numbers
23937 Here's an excerpt from a typical active file:
23940 soc.motss 296030 293865 y
23941 alt.binaries.pictures.fractals 3922 3913 n
23942 comp.sources.unix 1605 1593 m
23943 comp.binaries.ibm.pc 5097 5089 y
23944 no.general 1000 900 y
23947 Here's a pseudo-BNF definition of this file:
23950 active = *group-line
23951 group-line = group spc high-number spc low-number spc flag <NEWLINE>
23952 group = <non-white-space string>
23954 high-number = <non-negative integer>
23955 low-number = <positive integer>
23956 flag = "y" / "n" / "m" / "j" / "x" / "=" group
23959 For a full description of this file, see the manual pages for
23960 @samp{innd}, in particular @samp{active(5)}.
23963 @node Newsgroups File Format
23964 @subsubsection Newsgroups File Format
23966 The newsgroups file lists groups along with their descriptions. Not all
23967 groups on the server have to be listed, and not all groups in the file
23968 have to exist on the server. The file is meant purely as information to
23971 The format is quite simple; a group name, a tab, and the description.
23972 Here's the definition:
23976 line = group tab description <NEWLINE>
23977 group = <non-white-space string>
23979 description = <string>
23984 @node Emacs for Heathens
23985 @section Emacs for Heathens
23987 Believe it or not, but some people who use Gnus haven't really used
23988 Emacs much before they embarked on their journey on the Gnus Love Boat.
23989 If you are one of those unfortunates whom ``@kbd{C-M-a}'', ``kill the
23990 region'', and ``set @code{gnus-flargblossen} to an alist where the key
23991 is a regexp that is used for matching on the group name'' are magical
23992 phrases with little or no meaning, then this appendix is for you. If
23993 you are already familiar with Emacs, just ignore this and go fondle your
23997 * Keystrokes:: Entering text and executing commands.
23998 * Emacs Lisp:: The built-in Emacs programming language.
24003 @subsection Keystrokes
24007 Q: What is an experienced Emacs user?
24010 A: A person who wishes that the terminal had pedals.
24013 Yes, when you use Emacs, you are apt to use the control key, the shift
24014 key and the meta key a lot. This is very annoying to some people
24015 (notably @code{vi}le users), and the rest of us just love the hell out
24016 of it. Just give up and submit. Emacs really does stand for
24017 ``Escape-Meta-Alt-Control-Shift'', and not ``Editing Macros'', as you
24018 may have heard from other disreputable sources (like the Emacs author).
24020 The shift keys are normally located near your pinky fingers, and are
24021 normally used to get capital letters and stuff. You probably use it all
24022 the time. The control key is normally marked ``CTRL'' or something like
24023 that. The meta key is, funnily enough, never marked as such on any
24024 keyboard. The one I'm currently at has a key that's marked ``Alt'',
24025 which is the meta key on this keyboard. It's usually located somewhere
24026 to the left hand side of the keyboard, usually on the bottom row.
24028 Now, us Emacs people don't say ``press the meta-control-m key'',
24029 because that's just too inconvenient. We say ``press the @kbd{C-M-m}
24030 key''. @kbd{M-} is the prefix that means ``meta'' and ``C-'' is the
24031 prefix that means ``control''. So ``press @kbd{C-k}'' means ``press
24032 down the control key, and hold it down while you press @kbd{k}''.
24033 ``Press @kbd{C-M-k}'' means ``press down and hold down the meta key and
24034 the control key and then press @kbd{k}''. Simple, ay?
24036 This is somewhat complicated by the fact that not all keyboards have a
24037 meta key. In that case you can use the ``escape'' key. Then @kbd{M-k}
24038 means ``press escape, release escape, press @kbd{k}''. That's much more
24039 work than if you have a meta key, so if that's the case, I respectfully
24040 suggest you get a real keyboard with a meta key. You can't live without
24046 @subsection Emacs Lisp
24048 Emacs is the King of Editors because it's really a Lisp interpreter.
24049 Each and every key you tap runs some Emacs Lisp code snippet, and since
24050 Emacs Lisp is an interpreted language, that means that you can configure
24051 any key to run any arbitrary code. You just, like, do it.
24053 Gnus is written in Emacs Lisp, and is run as a bunch of interpreted
24054 functions. (These are byte-compiled for speed, but it's still
24055 interpreted.) If you decide that you don't like the way Gnus does
24056 certain things, it's trivial to have it do something a different way.
24057 (Well, at least if you know how to write Lisp code.) However, that's
24058 beyond the scope of this manual, so we are simply going to talk about
24059 some common constructs that you normally use in your @file{.emacs} file
24062 If you want to set the variable @code{gnus-florgbnize} to four (4), you
24063 write the following:
24066 (setq gnus-florgbnize 4)
24069 This function (really ``special form'') @code{setq} is the one that can
24070 set a variable to some value. This is really all you need to know. Now
24071 you can go and fill your @code{.emacs} file with lots of these to change
24074 If you have put that thing in your @code{.emacs} file, it will be read
24075 and @code{eval}ed (which is lisp-ese for ``run'') the next time you
24076 start Emacs. If you want to change the variable right away, simply say
24077 @kbd{C-x C-e} after the closing parenthesis. That will @code{eval} the
24078 previous ``form'', which is a simple @code{setq} statement here.
24080 Go ahead---just try it, if you're located at your Emacs. After you
24081 @kbd{C-x C-e}, you will see @samp{4} appear in the echo area, which
24082 is the return value of the form you @code{eval}ed.
24086 If the manual says ``set @code{gnus-read-active-file} to @code{some}'',
24090 (setq gnus-read-active-file 'some)
24093 On the other hand, if the manual says ``set @code{gnus-nntp-server} to
24094 @samp{nntp.ifi.uio.no}'', that means:
24097 (setq gnus-nntp-server "nntp.ifi.uio.no")
24100 So be careful not to mix up strings (the latter) with symbols (the
24101 former). The manual is unambiguous, but it can be confusing.
24104 @include gnus-faq.texi
24124 @c Local Variables:
24126 @c coding: iso-8859-1
24128 % LocalWords: BNF mucho detailmenu cindex kindex kbd
24129 % LocalWords: findex Gnusae vindex dfn dfn samp nntp setq nnspool nntpserver
24130 % LocalWords: nnmbox newusers Blllrph NEWGROUPS dingnusdingnusdingnus
24131 % LocalWords: pre fab rec comp nnslashdot regex ga ga sci nnml nnbabyl nnmh
24132 % LocalWords: nnfolder emph looong eld newsreaders defun init elc pxref