1 \input texinfo @c -*-texinfo-*-
4 @settitle Red Gnus 0.23 Manual
11 @setchapternewpage odd
15 \documentclass[twoside,a4paper,openright]{book}
16 \usepackage[latin1]{inputenc}
17 % \usepackage{fontenc}
19 \usepackage{pagestyle}
21 % \usepackage{ifitricks}
22 \fontfamily{bembo}\selectfont
27 \newcommand{\gnuschaptername}{}
28 \newcommand{\gnussectionname}{}
30 \newcommand{\gnusbackslash}{/}
32 \newcommand{\gnusxref}[1]{See ``#1'' on page \pageref{#1}}
33 \newcommand{\gnuspxref}[1]{see ``#1'' on page \pageref{#1}}
35 \newcommand{\gnuskindex}[1]{\index{#1}}
36 \newcommand{\gnusindex}[1]{\index{#1}}
38 \newcommand{\gnustt}[1]{{\textbf{\textsf{#1}}}}
39 \newcommand{\gnuscode}[1]{\gnustt{#1}}
40 \newcommand{\gnussamp}[1]{``\gnustt{#1}''}
41 \newcommand{\gnuslisp}[1]{\gnustt{#1}}
42 \newcommand{\gnuskbd}[1]{`\gnustt{#1}'}
43 \newcommand{\gnusfile}[1]{`\gnustt{#1}'}
44 \newcommand{\gnusdfn}[1]{\textit{#1}}
45 \newcommand{\gnusi}[1]{\textit{#1}}
46 \newcommand{\gnusstrong}[1]{\textbf{#1}}
47 \newcommand{\gnusemph}[1]{\textit{#1}}
48 \newcommand{\gnusvar}[1]{\textsl{\textsf{#1}}}
49 \newcommand{\gnussc}[1]{\textsc{#1}}
50 \newcommand{\gnustitle}[1]{{\huge\textbf{#1}}}
51 \newcommand{\gnusauthor}[1]{{\large\textbf{#1}}}
53 \newcommand{\gnusbullet}{{${\bullet}$}}
54 \newcommand{\gnusdollar}{\$}
55 \newcommand{\gnusampersand}{\&}
56 \newcommand{\gnuspercent}{\%}
57 \newcommand{\gnushash}{\#}
58 \newcommand{\gnushat}{\symbol{"5E}}
59 \newcommand{\gnusunderline}{\symbol{"5F}}
60 \newcommand{\gnustilde}{\symbol{"7E}}
61 \newcommand{\gnusless}{{$<$}}
62 \newcommand{\gnusgreater}{{$>$}}
64 \newcommand{\gnushead}{\raisebox{-1cm}{\epsfig{figure=gnus-head.eps,height=1cm}}}
65 \newcommand{\gnusinteresting}{
66 \marginpar[\hspace{2.5cm}\gnushead]{\gnushead}
69 \newcommand{\gnuschapter}[1]{
70 \renewcommand{\gnussectionname}{}
72 \renewcommand{\gnuschaptername}{#1}
74 % \epsfig{figure=gnus-herd-\arabic{chapter}.eps,height=15cm}
78 \newcommand{\gnusitemx}[1]{\vspace{-\itemsep}\item#1}
80 \newcommand{\gnussection}[1]{
81 \renewcommand{\gnussectionname}{#1}
85 \newenvironment{codelist}%
90 \newenvironment{kbdlist}%
96 \newenvironment{dfnlist}%
101 \newenvironment{stronglist}%
106 \newenvironment{samplist}%
111 \newenvironment{varlist}%
116 \newenvironment{emphlist}%
128 \makebox[\headtextwidth]{
130 \textbf{\arabic{chapter}.\arabic{section}}
131 \textbf{\gnussectionname\hfill\arabic{page}}
139 \makebox[\headtextwidth]{
140 \textbf{\arabic{page}\hfill\gnuschaptername}
149 \raisebox{-0.5cm}{\epsfig{figure=gnus-big-logo.eps,height=1cm}}
151 \raisebox{-0.5cm}{\epsfig{figure=gnus-big-logo.eps,height=1cm}}
165 %\addtolength{\oddsidemargin}{-5cm}
166 %\addtolength{\evensidemargin}{-5cm}
168 \addtolength{\textheight}{2cm}
170 \gnustitle{\gnustitlename}\\
173 \hspace*{-1cm}\epsfig{figure=gnus-big-logo.eps,height=15cm}
176 \gnusauthor{by Lars Magne Ingebrigtsen}
183 \thispagestyle{empty}
185 Copyright \copyright{} 1995,96 Free Software Foundation, Inc.
187 Permission is granted to make and distribute verbatim copies of
188 this manual provided the copyright notice and this permission notice
189 are preserved on all copies.
191 Permission is granted to copy and distribute modified versions of this
192 manual under the conditions for verbatim copying, provided that the
193 entire resulting derived work is distributed under the terms of a
194 permission notice identical to this one.
196 Permission is granted to copy and distribute translations of this manual
197 into another language, under the above conditions for modified versions.
206 This file documents Gnus, the GNU Emacs newsreader.
208 Copyright (C) 1995,96 Free Software Foundation, Inc.
210 Permission is granted to make and distribute verbatim copies of
211 this manual provided the copyright notice and this permission notice
212 are preserved on all copies.
215 Permission is granted to process this file through Tex and print the
216 results, provided the printed document carries copying permission
217 notice identical to this one except for the removal of this paragraph
218 (this paragraph not being relevant to the printed manual).
221 Permission is granted to copy and distribute modified versions of this
222 manual under the conditions for verbatim copying, provided also that the
223 entire resulting derived work is distributed under the terms of a
224 permission notice identical to this one.
226 Permission is granted to copy and distribute translations of this manual
227 into another language, under the above conditions for modified versions.
233 @title Red Gnus 0.23 Manual
235 @author by Lars Magne Ingebrigtsen
238 @vskip 0pt plus 1filll
239 Copyright @copyright{} 1995,96 Free Software Foundation, Inc.
241 Permission is granted to make and distribute verbatim copies of
242 this manual provided the copyright notice and this permission notice
243 are preserved on all copies.
245 Permission is granted to copy and distribute modified versions of this
246 manual under the conditions for verbatim copying, provided that the
247 entire resulting derived work is distributed under the terms of a
248 permission notice identical to this one.
250 Permission is granted to copy and distribute translations of this manual
251 into another language, under the above conditions for modified versions.
260 @top The Red Gnus Newsreader
264 You can read news (and mail) from within Emacs by using Gnus. The news
265 can be gotten by any nefarious means you can think of---@sc{nntp}, local
266 spool or your mbox file. All at the same time, if you want to push your
274 \thispagestyle{empty}
277 Gnus is the advanced, self-documenting, customizable, extensible
278 unreal-time newsreader for GNU Emacs.
280 Oops. That sounds oddly familiar, so let's start over again to avoid
281 being accused of plagiarism:
283 Gnus is a message-reading laboratory. It will let you look at just
284 about anything as if it were a newsgroup. You can read mail with it,
285 you can browse directories with it, you can @code{ftp} with it---you can
286 even read news with it!
288 Gnus tries to empower people who read news the same way Emacs empowers
289 people who edit text. Gnus sets no limits to what the user should be
290 allowed to do. Users are encouraged to extend Gnus to make it behave
291 like they want it to behave. A program should not control people;
292 people should be empowered to do what they want by using (or abusing)
299 * Starting Up:: Finding news can be a pain.
300 * The Group Buffer:: Selecting, subscribing and killing groups.
301 * The Summary Buffer:: Reading, saving and posting articles.
302 * The Article Buffer:: Displaying and handling articles.
303 * Composing Messages:: Information on sending mail and news.
304 * Select Methods:: Gnus reads all messages from various select methods.
305 * Scoring:: Assigning values to articles.
306 * Various:: General purpose settings.
307 * The End:: Farewell and goodbye.
308 * Appendices:: Terminology, Emacs intro, FAQ, History, Internals.
309 * Index:: Variable, function and concept index.
310 * Key Index:: Key Index.
316 @chapter Starting Gnus
321 If your system administrator has set things up properly, starting Gnus
322 and reading news is extremely easy---you just type @kbd{M-x gnus} in
325 @findex gnus-other-frame
326 @kindex M-x gnus-other-frame
327 If you want to start Gnus in a different frame, you can use the command
328 @kbd{M-x gnus-other-frame} instead.
330 If things do not go smoothly at startup, you have to twiddle some
334 * Finding the News:: Choosing a method for getting news.
335 * The First Time:: What does Gnus do the first time you start it?
336 * The Server is Down:: How can I read my mail then?
337 * Slave Gnusae:: You can have more than one Gnus active at a time.
338 * Fetching a Group:: Starting Gnus just to read a group.
339 * New Groups:: What is Gnus supposed to do with new groups?
340 * Startup Files:: Those pesky startup files---@file{.newsrc}.
341 * Auto Save:: Recovering from a crash.
342 * The Active File:: Reading the active file over a slow line Takes Time.
343 * Changing Servers:: You may want to move from one server to another.
344 * Startup Variables:: Other variables you might change.
348 @node Finding the News
349 @section Finding the News
351 @vindex gnus-select-method
353 The @code{gnus-select-method} variable says where Gnus should look for
354 news. This variable should be a list where the first element says
355 @dfn{how} and the second element says @dfn{where}. This method is your
356 native method. All groups that are not fetched with this method are
359 For instance, if the @samp{news.somewhere.edu} @sc{nntp} server is where
360 you want to get your daily dosage of news from, you'd say:
363 (setq gnus-select-method '(nntp "news.somewhere.edu"))
366 If you want to read directly from the local spool, say:
369 (setq gnus-select-method '(nnspool ""))
372 If you can use a local spool, you probably should, as it will almost
373 certainly be much faster.
375 @vindex gnus-nntpserver-file
377 @cindex @sc{nntp} server
378 If this variable is not set, Gnus will take a look at the
379 @code{NNTPSERVER} environment variable. If that variable isn't set,
380 Gnus will see whether @code{gnus-nntpserver-file}
381 (@file{/etc/nntpserver} by default) has any opinions on the matter. If
382 that fails as well, Gnus will will try to use the machine that is
383 running Emacs as an @sc{nntp} server. That's a long-shot, though.
385 @vindex gnus-nntp-server
386 If @code{gnus-nntp-server} is set, this variable will override
387 @code{gnus-select-method}. You should therefore set
388 @code{gnus-nntp-server} to @code{nil}, which is what it is by default.
390 @vindex gnus-secondary-servers
391 You can also make Gnus prompt you interactively for the name of an
392 @sc{nntp} server. If you give a non-numerical prefix to @code{gnus}
393 (i.e., @kbd{C-u M-x gnus}), Gnus will let you choose between the servers
394 in the @code{gnus-secondary-servers} list (if any). You can also just
395 type in the name of any server you feel like visiting.
397 @findex gnus-group-browse-foreign-server
399 However, if you use one @sc{nntp} server regularly and are just
400 interested in a couple of groups from a different server, you would be
401 better served by using the @kbd{B} command in the group buffer. It will
402 let you have a look at what groups are available, and you can subscribe
403 to any of the groups you want to. This also makes @file{.newsrc}
404 maintenance much tidier. @xref{Foreign Groups}.
406 @vindex gnus-secondary-select-methods
408 A slightly different approach to foreign groups is to set the
409 @code{gnus-secondary-select-methods} variable. The select methods
410 listed in this variable are in many ways just as native as the
411 @code{gnus-select-method} server. They will also be queried for active
412 files during startup (if that's required), and new newsgroups that
413 appear on these servers will be subscribed (or not) just as native
416 For instance, if you use the @code{nnmbox} backend to read your mail, you
417 would typically set this variable to
420 (setq gnus-secondary-select-methods '((nnmbox "")))
425 @section The First Time
426 @cindex first time usage
428 If no startup files exist, Gnus will try to determine what groups should
429 be subscribed by default.
431 @vindex gnus-default-subscribed-newsgroups
432 If the variable @code{gnus-default-subscribed-newsgroups} is set, Gnus
433 will subscribe you to just those groups in that list, leaving the rest
434 killed. Your system administrator should have set this variable to
437 Since she hasn't, Gnus will just subscribe you to a few arbitrarily
438 picked groups (i.e., @samp{*.newusers}). (@dfn{Arbitrary} is here
439 defined as @dfn{whatever Lars thinks you should read}.)
441 You'll also be subscribed to the Gnus documentation group, which should
442 help you with most common problems.
444 If @code{gnus-default-subscribed-newsgroups} is @code{t}, Gnus will just
445 use the normal functions for handling new groups, and not do anything
449 @node The Server is Down
450 @section The Server is Down
451 @cindex server errors
453 If the default server is down, Gnus will understandably have some
454 problems starting. However, if you have some mail groups in addition to
455 the news groups, you may want to start Gnus anyway.
457 Gnus, being the trusting sort of program, will ask whether to proceed
458 without a native select method if that server can't be contacted. This
459 will happen whether the server doesn't actually exist (i.e., you have
460 given the wrong address) or the server has just momentarily taken ill
461 for some reason or other. If you decide to continue and have no foreign
462 groups, you'll find it difficult to actually do anything in the group
463 buffer. But, hey, that's your problem. Blllrph!
465 @findex gnus-no-server
466 @kindex M-x gnus-no-server
468 If you know that the server is definitely down, or you just want to read
469 your mail without bothering with the server at all, you can use the
470 @code{gnus-no-server} command to start Gnus. That might come in handy
471 if you're in a hurry as well. This command will not attempt to contact
472 your primary server---instead, it will just activate all groups on level
473 1 and 2. (You should preferrably keep no native groups on those two
478 @section Slave Gnusae
481 You might want to run more than one Emacs with more than one Gnus at the
482 same time. If you are using different @file{.newsrc} files (eg., if you
483 are using the two different Gnusae to read from two different servers),
484 that is no problem whatsoever. You just do it.
486 The problem appears when you want to run two Gnusae that use the same
489 To work around that problem some, we here at the Think-Tank at the Gnus
490 Towers have come up with a new concept: @dfn{Masters} and
491 @dfn{servants}. (We have applied for a patent on this concept, and have
492 taken out a copyright on those words. If you wish to use those words in
493 conjunction with each other, you have to send $1 per usage instance to
494 me. Usage of the patent (@dfn{Master/Slave Relationships In Computer
495 Applications}) will be much more expensive, of course.)
497 Anyways, you start one Gnus up the normal way with @kbd{M-x gnus} (or
498 however you do it). Each subsequent slave Gnusae should be started with
499 @kbd{M-x gnus-slave}. These slaves won't save normal @file{.newsrc}
500 files, but instead save @dfn{slave files} that contains information only
501 on what groups have been read in the slave session. When a master Gnus
502 starts, it will read (and delete) these slave files, incorporating all
503 information from them. (The slave files will be read in the sequence
504 they were created, so the latest changes will have precedence.)
506 Information from the slave files has, of course, precedence over the
507 information in the normal (i. e., master) @code{.newsrc} file.
510 @node Fetching a Group
511 @section Fetching a Group
513 @findex gnus-fetch-group
514 It it sometime convenient to be able to just say ``I want to read this
515 group and I don't care whether Gnus has been started or not''. This is
516 perhaps more useful for people who write code than for users, but the
517 command @code{gnus-fetch-group} provides this functionality in any case.
518 It takes the group name as a parameter.
525 @vindex gnus-subscribe-newsgroup-method
526 What Gnus does when it encounters a new group is determined by the
527 @code{gnus-subscribe-newsgroup-method} variable.
529 This variable should contain a function. Some handy pre-fab values
534 @item gnus-subscribe-zombies
535 @vindex gnus-subscribe-zombies
536 Make all new groups zombies. You can browse the zombies later (with
537 @kbd{A z}) and either kill them all off properly, or subscribe to them.
540 @item gnus-subscribe-randomly
541 @vindex gnus-subscribe-randomly
542 Subscribe all new groups randomly.
544 @item gnus-subscribe-alphabetically
545 @vindex gnus-subscribe-alphabetically
546 Subscribe all new groups alphabetically.
548 @item gnus-subscribe-hierarchically
549 @vindex gnus-subscribe-hierarchically
550 Subscribe all new groups hierarchically. The difference between this
551 function and @code{gnus-subscribe-alphabetically} is slight.
552 @code{gnus-subscribe-alphabetically} will subscribe new groups in a strictly
553 alphabetical fashion, while this function will enter groups into it's
554 hierarchy. So if you want to have the @samp{rec} hierarchy before the
555 @samp{comp} hierarchy, this function will not mess that configuration
556 up. Or something like that.
558 @item gnus-subscribe-interactively
559 @vindex gnus-subscribe-interactively
560 Subscribe new groups interactively. This means that Gnus will ask
561 you about @strong{all} new groups.
563 @item gnus-subscribe-killed
564 @vindex gnus-subscribe-killed
569 @vindex gnus-subscribe-hierarchical-interactive
570 A closely related variable is
571 @code{gnus-subscribe-hierarchical-interactive}. (That's quite a
572 mouthful.) If this variable is non-@code{nil}, Gnus will ask you in a
573 hierarchical fashion whether to subscribe to new groups or not. Gnus
574 will ask you for each sub-hierarchy whether you want to descend the
577 One common mistake is to set the variable a few paragraphs above to
578 @code{gnus-subscribe-hierarchical-interactive}. This is an error. This
579 will not work. This is ga-ga. So don't do it.
581 A nice and portable way to control which new newsgroups should be
582 subscribed (or ignored) is to put an @dfn{options} line at the start of
583 the @file{.newsrc} file. Here's an example:
586 options -n !alt.all !rec.all sci.all
589 @vindex gnus-subscribe-options-newsgroup-method
590 This line obviously belongs to a serious-minded intellectual scientific
591 person (or she may just be plain old boring), because it says that all
592 groups that have names beginning with @samp{alt} and @samp{rec} should
593 be ignored, and all groups with names beginning with @samp{sci} should
594 be subscribed. Gnus will not use the normal subscription method for
595 subscribing these groups.
596 @code{gnus-subscribe-options-newsgroup-method} is used instead. This
597 variable defaults to @code{gnus-subscribe-alphabetically}.
599 @vindex gnus-options-not-subscribe
600 @vindex gnus-options-subscribe
601 If you don't want to mess with your @file{.newsrc} file, you can just
602 set the two variables @code{gnus-options-subscribe} and
603 @code{gnus-options-not-subscribe}. These two variables do exactly the
604 same as the @file{.newsrc} @samp{options -n} trick. Both are regexps,
605 and if the the new group matches the former, it will be unconditionally
606 subscribed, and if it matches the latter, it will be ignored.
608 @vindex gnus-auto-subscribed-groups
609 Yet another variable that meddles here is
610 @code{gnus-auto-subscribed-groups}. It works exactly like
611 @code{gnus-options-subscribe}, and is therefore really superfluous, but I
612 thought it would be nice to have two of these. This variable is more
613 meant for setting some ground rules, while the other variable is used
614 more for user fiddling. By default this variable makes all new groups
615 that come from mail backends (@code{nnml}, @code{nnbabyl},
616 @code{nnfolder}, @code{nnmbox}, and @code{nnmh}) subscribed. If you
617 don't like that, just set this variable to @code{nil}.
619 @vindex gnus-check-new-newsgroups
620 If you are satisfied that you really never want to see any new groups,
621 you could set @code{gnus-check-new-newsgroups} to @code{nil}. This will
622 also save you some time at startup. Even if this variable is
623 @code{nil}, you can always subscribe to the new groups just by pressing
624 @kbd{U} in the group buffer (@pxref{Group Maintenance}). This variable
625 is @code{t} by default.
627 Gnus normally determines whether a group is new or not by comparing the
628 list of groups from the active file(s) with the lists of subscribed and
629 dead groups. This isn't a particularly fast method. If
630 @code{gnus-check-new-newsgroups} is @code{ask-server}, Gnus will ask the
631 server for new groups since the last time. This is both faster &
632 cheaper. This also means that you can get rid of the list of killed
633 groups altogether, so you may set @code{gnus-save-killed-list} to
634 @code{nil}, which will save time both at startup, at exit, and all over.
635 Saves disk space, too. Why isn't this the default, then?
636 Unfortunately, not all servers support this command.
638 I bet I know what you're thinking now: How do I find out whether my
639 server supports @code{ask-server}? No? Good, because I don't have a
640 fail-safe answer. I would suggest just setting this variable to
641 @code{ask-server} and see whether any new groups appear within the next
642 few days. If any do, then it works. If any don't, then it doesn't
643 work. I could write a function to make Gnus guess whether the server
644 supports @code{ask-server}, but it would just be a guess. So I won't.
645 You could @code{telnet} to the server and say @code{HELP} and see
646 whether it lists @samp{NEWGROUPS} among the commands it understands. If
647 it does, then it might work. (But there are servers that lists
648 @samp{NEWGROUPS} without supporting the function properly.)
650 This variable can also be a list of select methods. If so, Gnus will
651 issue an @code{ask-server} command to each of the select methods, and
652 subscribe them (or not) using the normal methods. This might be handy
653 if you are monitoring a few servers for new groups. A side effect is
654 that startup will take much longer, so you can meditate while waiting.
655 Use the mantra ``dingnusdingnusdingnus'' to achieve permanent bliss.
658 @node Changing Servers
659 @section Changing Servers
661 Sometimes it is necessary to move from one @sc{nntp} server to another.
662 This happens very rarely, but perhaps you change jobs, or one server is
663 very flake and you want to use another.
665 Changing the server is pretty easy, right? You just change
666 @code{gnus-select-method} to point to the new server?
670 Article numbers are not (in any way) kept synchronized between different
671 @sc{nntp} servers, and the only way Gnus keeps track of what articles
672 you have read is by keeping track of article numbers. So when you
673 change @code{gnus-select-method}, your @file{.newsrc} file becomes
676 Gnus provides a few functions to attempt to translate a @file{.newsrc}
677 file from one server to another. They all have one thing in
678 common---they take a looong time to run. You don't want to use these
679 functions more than absolutely necessary.
681 @kindex M-x gnus-change-server
682 @findex gnus-change-server
683 If you have access to both servers, Gnus can request the headers for all
684 the articles you have read and compare @code{Message-ID}s and map
685 reads and article marks. The @kbd{M-x gnus-change-server} command will
686 do this for all your native groups. It will prompt for the method you
689 @kindex M-x gnus-group-move-group-to-server
690 @findex gnus-group-move-group-to-server
691 You can also move individual groups with the @kbd{M-x
692 gnus-group-move-group-to-server} command. This is useful if you want to
693 move a (foreign) group from one server to another.
695 @kindex M-x gnus-group-clear-data-on-native-groups
696 @findex gnus-group-clear-data-on-native-groups
697 If you don't have access to both the old and new server, all your marks
698 and read ranges have become worthless. You can use the @kbd{M-x
699 gnus-group-clear-data-on-native-groups} command to clear out all data
700 that you have on your native groups. Use with caution.
704 @section Startup Files
705 @cindex startup files
708 Now, you all know about the @file{.newsrc} file. All subscription
709 information is traditionally stored in this file.
711 Things got a bit more complicated with @sc{gnus}. In addition to
712 keeping the @file{.newsrc} file updated, it also used a file called
713 @file{.newsrc.el} for storing all the information that didn't fit into
714 the @file{.newsrc} file. (Actually, it also duplicated everything in
715 the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
716 files was the most recently saved, which enabled people to swap between
717 @sc{gnus} and other newsreaders.
719 That was kinda silly, so Gnus went one better: In addition to the
720 @file{.newsrc} and @file{.newsrc.el} files, Gnus also has a file called
721 @file{.newsrc.eld}. It will read whichever of these files that are most
722 recent, but it will never write a @file{.newsrc.el} file.
724 @vindex gnus-save-newsrc-file
725 You can turn off writing the @file{.newsrc} file by setting
726 @code{gnus-save-newsrc-file} to @code{nil}, which means you can delete
727 the file and save some space, as well as making exit from Gnus faster.
728 However, this will make it impossible to use other newsreaders than
729 Gnus. But hey, who would want to, right?
731 @vindex gnus-save-killed-list
732 If @code{gnus-save-killed-list} (default @code{t}) is @code{nil}, Gnus
733 will not save the list of killed groups to the startup file. This will
734 save both time (when starting and quitting) and space (on disk). It
735 will also means that Gnus has no record of what groups are new or old,
736 so the automatic new groups subscription methods become meaningless.
737 You should always set @code{gnus-check-new-newsgroups} to @code{nil} or
738 @code{ask-server} if you set this variable to @code{nil} (@pxref{New
739 Groups}). This variable can also be a regular expression. If that's
740 the case, remove all groups that do not match this regexp before
741 saving. This can be useful in certain obscure situations that involve
742 several servers where not all servers support @code{ask-server}.
744 @vindex gnus-startup-file
745 The @code{gnus-startup-file} variable says where the startup files are.
746 The default value is @file{~/.newsrc}, with the Gnus (El Dingo) startup
747 file being whatever that one is with a @samp{.eld} appended.
749 @vindex gnus-save-newsrc-hook
750 @vindex gnus-save-quick-newsrc-hook
751 @vindex gnus-save-standard-newsrc-hook
752 @code{gnus-save-newsrc-hook} is called before saving any of the newsrc
753 files, while @code{gnus-save-quick-newsrc-hook} is called just before
754 saving the @file{.newsrc.eld} file, and
755 @code{gnus-save-standard-newsrc-hook} is called just before saving the
756 @file{.newsrc} file. The latter two are commonly used to turn version
757 control on or off. Version control is off by default when saving the
760 @vindex gnus-init-file
761 When Gnus starts, it will read the @code{gnus-site-init-file} (default
762 @file{.../site-lisp/gnus.el}) and @code{gnus-init-file} (default
763 @file{~/.gnus.el}) files. These are normal Emacs Lisp files and can be
764 used to avoid cluttering your @file{.emacs} and @file{site-init} files
773 Whenever you do something that changes the Gnus data (reading articles,
774 catching up, killing/subscribing groups), the change is added to a
775 special @dfn{dribble buffer}. This buffer is auto-saved the normal
776 Emacs way. If your Emacs should crash before you have saved the
777 @file{.newsrc} files, all changes you have made can be recovered from
780 If Gnus detects this file at startup, it will ask the user whether to
781 read it. The auto save file is deleted whenever the real startup file is
784 @vindex gnus-use-dribble-file
785 If @code{gnus-use-dribble-file} is @code{nil}, Gnus won't create and
786 maintain a dribble buffer. The default is @code{t}.
788 @vindex gnus-dribble-directory
789 Gnus will put the dribble file(s) in @code{gnus-dribble-directory}. If
790 this variable is @code{nil}, which it is by default, Gnus will dribble
791 into the directory where the @file{.newsrc} file is located. (This is
792 normally the user's home directory.) The dribble file will get the same
793 file permissions as the @code{.newsrc} file.
796 @node The Active File
797 @section The Active File
799 @cindex ignored groups
801 When Gnus starts, or indeed whenever it tries to determine whether new
802 articles have arrived, it reads the active file. This is a very large
803 file that lists all the active groups and articles on the server.
805 @vindex gnus-ignored-newsgroups
806 Before examining the active file, Gnus deletes all lines that match the
807 regexp @code{gnus-ignored-newsgroups}. This is done primarily to reject
808 any groups with bogus names, but you can use this variable to make Gnus
809 ignore hierarchies you aren't ever interested in. However, this is not
810 recommended. In fact, it's highly discouraged. Instead, @pxref{New
811 Groups} for an overview of other variables that can be used instead.
814 @c @code{nil} by default, and will slow down active file handling somewhat
815 @c if you set it to anything else.
817 @vindex gnus-read-active-file
819 The active file can be rather Huge, so if you have a slow network, you
820 can set @code{gnus-read-active-file} to @code{nil} to prevent Gnus from
821 reading the active file. This variable is @code{t} by default.
823 Gnus will try to make do by getting information just on the groups that
824 you actually subscribe to.
826 Note that if you subscribe to lots and lots of groups, setting this
827 variable to @code{nil} will probably make Gnus slower, not faster. At
828 present, having this variable @code{nil} will slow Gnus down
829 considerably, unless you read news over a 2400 baud modem.
831 This variable can also have the value @code{some}. Gnus will then
832 attempt to read active info only on the subscribed groups. On some
833 servers this is quite fast (on sparkling, brand new INN servers that
834 support the @code{LIST ACTIVE group} command), on others this isn't fast
835 at all. In any case, @code{some} should be faster than @code{nil}, and
836 is certainly faster than @code{t} over slow lines.
838 If this variable is @code{nil}, Gnus will ask for group info in total
839 lock-step, which isn't very fast. If it is @code{some} and you use an
840 @sc{nntp} server, Gnus will pump out commands as fast as it can, and
841 read all the replies in one swoop. This will normally result in better
842 performance, but if the server does not support the aforementioned
843 @code{LIST ACTIVE group} command, this isn't very nice to the server.
845 In any case, if you use @code{some} or @code{nil}, you should definitely
846 kill all groups that you aren't interested in to speed things up.
849 @node Startup Variables
850 @section Startup Variables
855 @vindex gnus-load-hook
856 A hook that is run while Gnus is being loaded. Note that this hook will
857 normally be run just once in each Emacs session, no matter how many
858 times you start Gnus.
860 @item gnus-startup-hook
861 @vindex gnus-startup-hook
862 A hook that is run after starting up Gnus successfully.
864 @item gnus-check-bogus-newsgroups
865 @vindex gnus-check-bogus-newsgroups
866 If non-@code{nil}, Gnus will check for and delete all bogus groups at
867 startup. A @dfn{bogus group} is a group that you have in your
868 @file{.newsrc} file, but doesn't exist on the news server. Checking for
869 bogus groups can take quite a while, so to save time and resources it's
870 best to leave this option off, and do the checking for bogus groups once
871 in a while from the group buffer instead (@pxref{Group Maintenance}).
873 @item gnus-inhibit-startup-message
874 @vindex gnus-inhibit-startup-message
875 If non-@code{nil}, the startup message won't be displayed. That way,
876 your boss might not notice that you are reading news instead of doing
879 @item gnus-no-groups-message
880 @vindex gnus-no-groups-message
881 Message displayed by Gnus when no groups are available.
885 @node The Group Buffer
886 @chapter The Group Buffer
889 The @dfn{group buffer} lists all (or parts) of the available groups. It
890 is the first buffer shown when Gnus starts, and will never be killed as
891 long as Gnus is active.
894 * Group Buffer Format:: Information listed and how you can change it.
895 * Group Maneuvering:: Commands for moving in the group buffer.
896 * Selecting a Group:: Actually reading news.
897 * Subscription Commands:: Unsubscribing, killing, subscribing.
898 * Group Levels:: Levels? What are those, then?
899 * Group Score:: A mechanism for finding out what groups you like.
900 * Marking Groups:: You can mark groups for later processing.
901 * Foreign Groups:: Creating and editing groups.
902 * Group Parameters:: Each group may have different parameters set.
903 * Listing Groups:: Gnus can list various subsets of the groups.
904 * Sorting Groups:: Re-arrange the group order.
905 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
906 * Browse Foreign Server:: You can browse a server. See what it has to offer.
907 * Exiting Gnus:: Stop reading news and get some work done.
908 * Group Topics:: A folding group mode divided into topics.
909 * Misc Group Stuff:: Other stuff that you can to do.
913 @node Group Buffer Format
914 @section Group Buffer Format
915 @cindex group buffer format
918 * Group Line Specification:: Deciding how the group buffer is to look.
919 * Group Modeline Specification:: The group buffer modeline.
920 * Group Highlighting:: Having nice colors in the group buffer.
924 @node Group Line Specification
925 @subsection Group Line Specification
927 The default format of the group buffer is nice and dull, but you can
928 make it as exciting and ugly as you feel like.
930 Here's a couple of example group lines:
933 25: news.announce.newusers
934 * 0: alt.fan.andrea-dworkin
939 You can see that there are 25 unread articles in
940 @samp{news.announce.newusers}. There are no unread articles, but some
941 ticked articles, in @samp{alt.fan.andrea-dworkin} (see that little
942 asterisk at the beginning of the line?)
944 @vindex gnus-group-line-format
945 You can change that format to whatever you want by fiddling with the
946 @code{gnus-group-line-format} variable. This variable works along the
947 lines of a @code{format} specification, which is pretty much the same as
948 a @code{printf} specifications, for those of you who use (feh!) C.
949 @xref{Formatting Variables}.
951 The default value that produced those lines above is
952 @samp{%M%S%5y: %(%g%)\n}.
954 There should always be a colon on the line; the cursor always moves to
955 the colon after performing an operation. Nothing else is required---not
956 even the group name. All displayed text is just window dressing, and is
957 never examined by Gnus. Gnus stores all real information it needs using
960 (Note that if you make a really strange, wonderful, spreadsheet-like
961 layout, everybody will believe you are hard at work with the accounting
962 instead of wasting time reading news.)
964 Here's a list of all available format characters:
969 Only marked articles.
972 Whether the group is subscribed.
975 Level of subscribedness.
978 Number of unread articles.
981 Number of dormant articles.
984 Number of ticked articles.
987 Number of read articles.
990 Estimated total number of articles. (This is really @var{max-number}
991 minus @var{min-number} plus 1.)
994 Number of unread, unticked, non-dormant articles.
997 Number of ticked and dormant articles.
1006 Newsgroup description.
1009 @samp{m} if moderated.
1012 @samp{(m)} if moderated.
1021 A string that looks like @samp{<%s:%n>} if a foreign select method is
1025 Indentation based on the level of the topic (@pxref{Group Topics}).
1028 @vindex gnus-group-uncollapsed-levels
1029 Short (collapsed) group name. The @code{gnus-group-uncollapsed-levels}
1030 variable says how many levels to leave at the end of the group name.
1031 The default is @code{1}.
1034 User defined specifier. The next character in the format string should
1035 be a letter. @sc{gnus} will call the function
1036 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
1037 following @samp{%u}. The function will be passed the current headers as
1038 argument. The function should return a string, which will be inserted
1039 into the buffer just like information from any other specifier.
1043 All the ``number-of'' specs will be filled with an asterisk (@samp{*})
1044 if no info is available---for instance, if it is a non-activated foreign
1045 group, or a bogus (or semi-bogus) native group.
1048 @node Group Modeline Specification
1049 @subsection Group Modeline Specification
1051 @vindex gnus-group-mode-line-format
1052 The mode line can be changed by setting
1053 @code{gnus-group-mode-line-format} (@pxref{Formatting Variables}). It
1054 doesn't understand that many format specifiers:
1058 The native news server.
1060 The native select method.
1064 @node Group Highlighting
1065 @subsection Group Highlighting
1067 @vindex gnus-group-highlight
1068 Highlighting in the group buffer is controlled by the
1069 @code{gnus-group-highlight} variable. This is an alist with elements
1070 that look like @var{(form . face)}. If @var{form} evaluates to
1071 something non-@code{nil}, the @var{face} will be used on the line.
1073 Here's an example value for this variable that might look nice if the
1077 (setq gnus-group-highlight
1079 ,(custom-face-lookup "Red" nil nil t nil nil))
1080 ((and (< level 3) (zerop unread)) .
1081 ,(custom-face-lookup "SeaGreen" nil nil t nil nil))
1083 ,(custom-face-lookup "SpringGreen" nil nil t nil nil))
1085 ,(custom-face-lookup "SteelBlue" nil nil t nil nil))
1087 ,(custom-face-lookup "SkyBlue" nil nil t nil nil))
1091 Variables that are dynamically bound when the forms are evaluated
1098 The number of unread articles in the group.
1102 Whether the group is a mail group.
1104 The level of the group.
1106 The score of the group.
1108 The number of ticked articles in the group.
1110 The total number of articles in the group. Or rather, MAX-NUMBER minus
1113 When using the topic minor mode, this variable is bound to the current
1114 topic being inserted.
1117 When the forms are @code{eval}ed, point is at the beginning of the line
1118 of the group in question, so you can use many of the normal Gnus
1119 functions for snarfing info on the group.
1121 @vindex gnus-group-update-hook
1122 @findex gnus-group-highlight-line
1123 @code{gnus-group-update-hook} is called when a group line is changed.
1124 It will not be called when @code{gnus-visual} is @code{nil}. This hook
1125 calls @code{gnus-group-highlight-line} by default.
1128 @node Group Maneuvering
1129 @section Group Maneuvering
1130 @cindex group movement
1132 All movement commands understand the numeric prefix and will behave as
1133 expected, hopefully.
1139 @findex gnus-group-next-unread-group
1140 Go to the next group that has unread articles
1141 (@code{gnus-group-next-unread-group}).
1148 @findex gnus-group-prev-unread-group
1149 Go to the previous group group that has unread articles
1150 (@code{gnus-group-prev-unread-group}).
1154 @findex gnus-group-next-group
1155 Go to the next group (@code{gnus-group-next-group}).
1159 @findex gnus-group-prev-group
1160 Go to the previous group (@code{gnus-group-prev-group}).
1164 @findex gnus-group-next-unread-group-same-level
1165 Go to the next unread group on the same level (or lower)
1166 (@code{gnus-group-next-unread-group-same-level}).
1170 @findex gnus-group-prev-unread-group-same-level
1171 Go to the previous unread group on the same level (or lower)
1172 (@code{gnus-group-prev-unread-group-same-level}).
1175 Three commands for jumping to groups:
1181 @findex gnus-group-jump-to-group
1182 Jump to a group (and make it visible if it isn't already)
1183 (@code{gnus-group-jump-to-group}). Killed groups can be jumped to, just
1188 @findex gnus-group-best-unread-group
1189 Jump to the unread group with the lowest level
1190 (@code{gnus-group-best-unread-group}).
1194 @findex gnus-group-first-unread-group
1195 Jump to the first group with unread articles
1196 (@code{gnus-group-first-unread-group}).
1199 @vindex gnus-group-goto-unread
1200 If @code{gnus-group-goto-unread} is @code{nil}, all the movement
1201 commands will move to the next group, not the next unread group. Even
1202 the commands that say they move to the next unread group. The default
1206 @node Selecting a Group
1207 @section Selecting a Group
1208 @cindex group selection
1213 @kindex SPACE (Group)
1214 @findex gnus-group-read-group
1215 Select the current group, switch to the summary buffer and display the
1216 first unread article (@code{gnus-group-read-group}). If there are no
1217 unread articles in the group, or if you give a non-numerical prefix to
1218 this command, Gnus will offer to fetch all the old articles in this
1219 group from the server. If you give a numerical prefix @var{N}, Gnus
1220 will fetch @var{N} number of articles. If @var{N} is positive, fetch
1221 the @var{N} newest articles, if @var{N} is negative, fetch the
1222 @var{abs(N)} oldest articles.
1226 @findex gnus-group-select-group
1227 Select the current group and switch to the summary buffer
1228 (@code{gnus-group-select-group}). Takes the same arguments as
1229 @code{gnus-group-read-group}---the only difference is that this command
1230 does not display the first unread article automatically upon group
1234 @kindex M-RET (Group)
1235 @findex gnus-group-quick-select-group
1236 This does the same as the command above, but tries to do it with the
1237 minimum amount off fuzz (@code{gnus-group-quick-select-group}). No
1238 scoring/killing will be performed, there will be no highlights and no
1239 expunging. This might be useful if you're in a real hurry and have to
1240 enter some humongous group. If you give a 0 prefix to this command
1241 (i. e., @kbd{0 M-RET}), Gnus won't even generate the summary buffer.
1242 This might be useful if you want to toggle threading before entering the
1246 @kindex M-SPACE (Group)
1247 @findex gnus-group-visible-select-group
1248 This is yet one more command that does the same as the one above, but
1249 this one does it without expunging and hiding dormants
1250 (@code{gnus-group-visible-select-group}).
1254 @findex gnus-group-catchup-current
1255 @vindex gnus-group-catchup-group-hook
1256 Mark all unticked articles in this group as read
1257 (@code{gnus-group-catchup-current}).
1258 @code{gnus-group-catchup-group-hook} is when catching up a group from
1263 @findex gnus-group-catchup-current-all
1264 Mark all articles in this group, even the ticked ones, as read
1265 (@code{gnus-group-catchup-current-all}).
1269 @findex gnus-group-clear-data
1270 Clear the data from the current group---nix out marks and the list of
1271 read articles (@code{gnus-group-clear-data}).
1273 @item M-x gnus-group-clear-data-on-native-groups
1274 @kindex M-x gnus-group-clear-data-on-native-groups
1275 @findex gnus-group-clear-data-on-native-groups
1276 If you have switced from one @sc{nntp} server to another, all your marks
1277 and read ranges have become worthless. You can use this command to
1278 clear out all data that you have on your native groups. Use with
1283 @vindex gnus-large-newsgroup
1284 The @code{gnus-large-newsgroup} variable says what Gnus should consider
1285 to be a big group. This is 200 by default. If the group has more
1286 unread articles than this, Gnus will query the user before entering the
1287 group. The user can then specify how many articles should be fetched
1288 from the server. If the user specifies a negative number (@code{-n}),
1289 the @code{n} oldest articles will be fetched. If it is positive, the
1290 @code{n} articles that have arrived most recently will be fetched.
1292 @vindex gnus-select-group-hook
1293 @vindex gnus-auto-select-first
1294 @code{gnus-auto-select-first} control whether any articles are selected
1295 automatically when entering a group.
1300 Don't select any articles when entering the group. Just display the
1301 full summary buffer.
1304 Select the first unread article when entering the group.
1307 Select the most high-scored article in the group when entering the
1311 If you want to prevent automatic selection in some group (say, in a
1312 binary group with Huge articles) you can set this variable to @code{nil}
1313 in @code{gnus-select-group-hook}, which is called when a group is
1317 @node Subscription Commands
1318 @section Subscription Commands
1327 @findex gnus-group-unsubscribe-current-group
1328 Toggle subscription to the current group
1329 (@code{gnus-group-unsubscribe-current-group}).
1335 @findex gnus-group-unsubscribe-group
1336 Prompt for a group to subscribe, and then subscribe it. If it was
1337 subscribed already, unsubscribe it instead
1338 (@code{gnus-group-unsubscribe-group}).
1344 @findex gnus-group-kill-group
1345 Kill the current group (@code{gnus-group-kill-group}).
1351 @findex gnus-group-yank-group
1352 Yank the last killed group (@code{gnus-group-yank-group}).
1355 @kindex C-x C-t (Group)
1356 @findex gnus-group-transpose-groups
1357 Transpose two groups (@code{gnus-group-transpose-groups}). This isn't
1358 really a subscription command, but you can use it instead of a
1359 kill-and-yank sequence sometimes.
1365 @findex gnus-group-kill-region
1366 Kill all groups in the region (@code{gnus-group-kill-region}).
1370 @findex gnus-group-kill-all-zombies
1371 Kill all zombie groups (@code{gnus-group-kill-all-zombies}).
1374 @kindex S C-k (Group)
1375 @findex gnus-group-kill-level
1376 Kill all groups on a certain level (@code{gnus-group-kill-level}).
1377 These groups can't be yanked back after killing, so this command should
1378 be used with some caution. The only thing where this command comes in
1379 really handy is when you have a @file{.newsrc} with lots of unsubscribed
1380 groups that you want to get rid off. @kbd{S C-k} on level @code{7} will
1381 kill off all unsubscribed groups that do not have message numbers in the
1382 @file{.newsrc} file.
1386 Also @pxref{Group Levels}.
1390 @section Group Levels
1393 All groups have a level of @dfn{subscribedness}. For instance, if a
1394 group is on level 2, it is more subscribed than a group on level 5. You
1395 can ask Gnus to just list groups on a given level or lower
1396 (@pxref{Listing Groups}), or to just check for new articles in groups on
1397 a given level or lower (@pxref{Scanning New Messages}).
1399 Remember: The higher the level of the group, the less important it is.
1405 @findex gnus-group-set-current-level
1406 Set the level of the current group. If a numeric prefix is given, the
1407 next @var{n} groups will have their levels set. The user will be
1408 prompted for a level.
1411 @vindex gnus-level-killed
1412 @vindex gnus-level-zombie
1413 @vindex gnus-level-unsubscribed
1414 @vindex gnus-level-subscribed
1415 Gnus considers groups on between levels 1 and
1416 @code{gnus-level-subscribed} (inclusive) (default 5) to be subscribed,
1417 @code{gnus-level-subscribed} (exclusive) and
1418 @code{gnus-level-unsubscribed} (inclusive) (default 7) to be
1419 unsubscribed, @code{gnus-level-zombie} to be zombies (walking dead)
1420 (default 8) and @code{gnus-level-killed} to be killed (default 9),
1421 completely dead. Gnus treats subscribed and unsubscribed groups exactly
1422 the same, but zombie and killed groups have no information on what
1423 articles you have read, etc, stored. This distinction between dead and
1424 living groups isn't done because it is nice or clever, it is done purely
1425 for reasons of efficiency.
1427 It is recommended that you keep all your mail groups (if any) on quite
1428 low levels (eg. 1 or 2).
1430 If you want to play with the level variables, you should show some care.
1431 Set them once, and don't touch them ever again. Better yet, don't touch
1432 them at all unless you know exactly what you're doing.
1434 @vindex gnus-level-default-unsubscribed
1435 @vindex gnus-level-default-subscribed
1436 Two closely related variables are @code{gnus-level-default-subscribed}
1437 (default 3) and @code{gnus-level-default-unsubscribed} (default 6),
1438 which are the levels that new groups will be put on if they are
1439 (un)subscribed. These two variables should, of course, be inside the
1440 relevant legal ranges.
1442 @vindex gnus-keep-same-level
1443 If @code{gnus-keep-same-level} is non-@code{nil}, some movement commands
1444 will only move to groups that are of the same level (or lower). In
1445 particular, going from the last article in one group to the next group
1446 will go to the next group of the same level (or lower). This might be
1447 handy if you want to read the most important groups before you read the
1450 @vindex gnus-group-default-list-level
1451 All groups with a level less than or equal to
1452 @code{gnus-group-default-list-level} will be listed in the group buffer
1455 @vindex gnus-group-list-inactive-groups
1456 If @code{gnus-group-list-inactive-groups} is non-@code{nil}, non-active
1457 groups will be listed along with the unread groups. This variable is
1458 @code{t} by default. If it is @code{nil}, inactive groups won't be
1461 @vindex gnus-group-use-permanent-levels
1462 If @code{gnus-group-use-permanent-levels} is non-@code{nil}, once you
1463 give a level prefix to @kbd{g} or @kbd{l}, all subsequent commands will
1464 use this level as the ``work'' level.
1466 @vindex gnus-activate-level
1467 Gnus will normally just activate groups that are on level
1468 @code{gnus-activate-level} or less. If you don't want to activate
1469 unsubscribed groups, for instance, you might set this variable to
1474 @section Group Score
1477 You would normally keep important groups on high levels, but that scheme
1478 is somewhat restrictive. Don't you wish you could have Gnus sort the
1479 group buffer according to how often you read groups, perhaps? Within
1482 This is what @dfn{group score} is for. You can assign a score to each
1483 group. You can then sort the group buffer based on this score.
1484 Alternatively, you can sort on score and then level. (Taken together,
1485 the level and the score is called the @dfn{rank} of the group. A group
1486 that is on level 4 and has a score of 1 has a higher rank than a group
1487 on level 5 that has a score of 300. (The level is the most significant
1488 part and the score is the least significant part.)
1490 @findex gnus-summary-bubble-group
1491 If you want groups you read often to get higher scores than groups you
1492 read seldom you can add the @code{gnus-summary-bubble-group} function to
1493 the @code{gnus-summary-exit-hook} hook. This will result (after
1494 sorting) in a bubbling sort of action. If you want to see that in
1495 action after each summary exit, you can add
1496 @code{gnus-group-sort-groups-by-rank} or
1497 @code{gnus-group-sort-groups-by-score} to the same hook, but that will
1498 slow things down somewhat.
1501 @node Marking Groups
1502 @section Marking Groups
1503 @cindex marking groups
1505 If you want to perform some command on several groups, and they appear
1506 subsequently in the group buffer, you would normally just give a
1507 numerical prefix to the command. Most group commands will then do your
1508 bidding on those groups.
1510 However, if the groups are not in sequential order, you can still
1511 perform a command on several groups. You simply mark the groups first
1512 with the process mark and then execute the command.
1520 @findex gnus-group-mark-group
1521 Set the mark on the current group (@code{gnus-group-mark-group}).
1527 @findex gnus-group-unmark-group
1528 Remove the mark from the current group
1529 (@code{gnus-group-unmark-group}).
1533 @findex gnus-group-unmark-all-groups
1534 Remove the mark from all groups (@code{gnus-group-unmark-all-groups}).
1538 @findex gnus-group-mark-region
1539 Mark all groups between point and mark (@code{gnus-group-mark-region}).
1543 @findex gnus-group-mark-buffer
1544 Mark all groups in the buffer (@code{gnus-group-mark-buffer}).
1548 @findex gnus-group-mark-regexp
1549 Mark all groups that match some regular expression
1550 (@code{gnus-group-mark-regexp}).
1553 Also @pxref{Process/Prefix}.
1555 @findex gnus-group-universal-argument
1556 If you want to execute some command on all groups that have been marked
1557 with the process mark, you can use the @kbd{M-&}
1558 (@code{gnus-group-universal-argument}) command. It will prompt you for
1559 the command to be executed.
1562 @node Foreign Groups
1563 @section Foreign Groups
1565 Below are some group mode commands for making and editing general foreign
1566 groups, as well as commands to ease the creation of a few
1567 special-purpose groups. All these commands insert the newly created
1568 groups under point---@code{gnus-subscribe-newsgroup-method} is not
1575 @findex gnus-group-make-group
1576 Make a new group (@code{gnus-group-make-group}). Gnus will prompt you
1577 for a name, a method and possibly an @dfn{address}. For an easier way
1578 to subscribe to @sc{nntp} groups, @pxref{Browse Foreign Server}.
1582 @findex gnus-group-rename-group
1583 Rename the current group to something else
1584 (@code{gnus-group-rename-group}). This is legal only on some
1585 groups---mail groups mostly. This command might very well be quite slow
1590 @findex gnus-group-edit-group-method
1591 Enter a buffer where you can edit the select method of the current
1592 group (@code{gnus-group-edit-group-method}).
1596 @findex gnus-group-edit-group-parameters
1597 Enter a buffer where you can edit the group parameters
1598 (@code{gnus-group-edit-group-parameters}).
1602 @findex gnus-group-edit-group
1603 Enter a buffer where you can edit the group info
1604 (@code{gnus-group-edit-group}).
1608 @findex gnus-group-make-directory-group
1609 Make a directory group (@pxref{Directory Groups}). You will be prompted
1610 for a directory name (@code{gnus-group-make-directory-group}).
1614 @findex gnus-group-make-help-group
1615 Make the Gnus help group (@code{gnus-group-make-help-group}).
1619 @findex gnus-group-make-archive-group
1620 @vindex gnus-group-archive-directory
1621 @vindex gnus-group-recent-archive-directory
1622 Make a Gnus archive group (@code{gnus-group-make-archive-group}). By
1623 default a group pointing to the most recent articles will be created
1624 (@code{gnus-group-recent-archive-directory}), but given a prefix, a full
1625 group will be created from @code{gnus-group-archive-directory}.
1629 @findex gnus-group-make-kiboze-group
1630 Make a kiboze group. You will be prompted for a name, for a regexp to
1631 match groups to be ``included'' in the kiboze group, and a series of
1632 strings to match on headers (@code{gnus-group-make-kiboze-group}).
1633 @xref{Kibozed Groups}
1637 @findex gnus-group-enter-directory
1638 Read an arbitrary directory as if with were a newsgroup with the
1639 @code{nneething} backend (@code{gnus-group-enter-directory}).
1640 @xref{Anything Groups}.
1644 @findex gnus-group-make-doc-group
1645 @cindex ClariNet Briefs
1646 Make a group based on some file or other
1647 (@code{gnus-group-make-doc-group}). If you give a prefix to this
1648 command, you will be prompted for a file name and a file type.
1649 Currently supported types are @code{babyl}, @code{mbox}, @code{digest},
1650 @code{mmdf}, @code{news}, @code{rnews}, @code{clari-briefs}, and
1651 @code{forward}. If you run this command without a prefix, Gnus will
1652 guess at the file type. @xref{Document Groups}.
1656 @findex gnus-group-make-web-group
1660 Make an ephemeral group based on a web search
1661 (@code{gnus-group-make-web-group}). If you give a prefix to this
1662 command, make a solid group instead. You will be prompted for the
1663 search engine type and the search string. Legal search engine types
1664 include @code{dejanews}, @code{altavista} and @code{reference}.
1665 @xref{Web Searches}.
1668 @kindex G DEL (Group)
1669 @findex gnus-group-delete-group
1670 This function will delete the current group
1671 (@code{gnus-group-delete-group}). If given a prefix, this function will
1672 actually delete all the articles in the group, and forcibly remove the
1673 group itself from the face of the Earth. Use a prefix only if you are
1674 absolutely sure of what you are doing.
1678 @findex gnus-group-make-empty-virtual
1679 Make a new, fresh, empty @code{nnvirtual} group
1680 (@code{gnus-group-make-empty-virtual}). @xref{Virtual Groups}.
1684 @findex gnus-group-add-to-virtual
1685 Add the current group to an @code{nnvirtual} group
1686 (@code{gnus-group-add-to-virtual}). Uses the process/prefix convention.
1689 @xref{Select Methods} for more information on the various select
1692 @vindex gnus-activate-foreign-newsgroups
1693 If the @code{gnus-activate-foreign-newsgroups} is a positive number,
1694 Gnus will check all foreign groups with this level or lower at startup.
1695 This might take quite a while, especially if you subscribe to lots of
1696 groups from different @sc{nntp} servers.
1699 @node Group Parameters
1700 @section Group Parameters
1701 @cindex group parameters
1703 Gnus stores all information on a group in a list that is usually known
1704 as the @dfn{group info}. This list has from three to six elements.
1705 Here's an example info.
1708 ("nnml:mail.ding" 3 ((1 . 232) 244 (256 . 270)) ((tick 246 249))
1709 (nnml "private") ((to-address . "ding@@ifi.uio.no")))
1712 The first element is the @dfn{group name}, as Gnus knows the group,
1713 anyway. The second element is the @dfn{subscription level}, which
1714 normally is a small integer. The third element is a list of ranges of
1715 read articles. The fourth element is a list of lists of article marks
1716 of various kinds. The fifth element is the select method (or virtual
1717 server, if you like). The sixth element is a list of @dfn{group
1718 parameters}, which is what this section is about.
1720 Any of the last three elements may be missing if they are not required.
1721 In fact, the vast majority of groups will normally only have the first
1722 three elements, which saves quite a lot of cons cells.
1724 The group parameters store information local to a particular group:
1729 If the group parameter list contains an element that looks like
1730 @code{(to-address . "some@@where.com")}, that address will be used by
1731 the backend when doing followups and posts. This is primarily useful in
1732 mail groups that represent closed mailing lists---mailing lists where
1733 it's expected that everybody that writes to the mailing list is
1734 subscribed to it. Since using this parameter ensures that the mail only
1735 goes to the mailing list itself, it means that members won't receive two
1736 copies of your followups.
1738 Using @code{to-address} will actually work whether the group is foreign
1739 or not. Let's say there's a group on the server that is called
1740 @samp{fa.4ad-l}. This is a real newsgroup, but the server has gotten
1741 the articles from a mail-to-news gateway. Posting directly to this
1742 group is therefore impossible---you have to send mail to the mailing
1743 list address instead.
1747 If the group parameter list has an element that looks like
1748 @code{(to-list . "some@@where.com")}, that address will be used when
1749 doing a @kbd{a} in any group. It is totally ignored when doing a
1750 followup---except that if it is present in a news group, you'll get mail
1751 group semantics when doing @kbd{f}.
1753 @item broken-reply-to
1754 @cindex broken-reply-to
1755 Elements like @code{(broken-reply-to . t)} signals that @code{Reply-To}
1756 headers in this group are to be ignored. This can be useful if you're
1757 reading a mailing list group where the listserv has inserted
1758 @code{Reply-To} headers that point back to the listserv itself. This is
1759 broken behavior. So there!
1763 If the group parameter list contains an element like @code{(to-group
1764 . "some.group.name")}, all posts will be sent to that group.
1768 If this symbol is present in the group parameter list and set to
1769 @code{t}, new composed messages will be @code{Gcc}'d to the current
1770 group. If it is present and set to @code{none}, no @code{Gcc:} header
1771 will be generated, if it is present and a string, this string will be
1772 inserted literally as a @code{gcc} header (this symbol takes precedence over
1773 any default @code{Gcc} rules as described later).
1777 If this symbol is present in the group parameter list, all articles that
1778 are read will be marked as expirable. For an alternative approach,
1779 @pxref{Expiring Mail}.
1782 @cindex total-expire
1783 If this symbol is present, all read articles will be put through the
1784 expiry process, even if they are not marked as expirable. Use with
1789 @vindex nnmail-expiry-wait-function
1790 If the group parameter has an element that looks like @code{(expiry-wait
1791 . 10)}, this value will override any @code{nnmail-expiry-wait} and
1792 @code{nnmail-expiry-wait-function} when expiring expirable messages.
1793 The value can either be a number of days (not necessarily an integer) or
1794 the symbols @code{never} or @code{immediate}.
1797 @cindex score file group parameter
1798 Elements that look like @code{(score-file . "file")} will make
1799 @file{file} into the current score file for the group in question. This
1800 means that all score commands you issue will end up in that file.
1803 @cindex adapt file group parameter
1804 Elements that look like @code{(adapt-file . "file")} will make
1805 @file{file} into the current adaptive file for the group in question.
1806 All adaptive score entries will be put into this file.
1809 When unsubscribing to a mailing list you should never send the
1810 unsubscription notice to the mailing list itself. Instead, you'd send
1811 messages to the administrative address. This parameter allows you to
1812 put the admin address somewhere convenient.
1815 Elements that look like @code{(display . MODE)} says which articles to
1816 display on entering the group. Legal values are:
1820 Display all articles, both read and unread.
1823 Display the default visible articles, which normally includes unread and
1828 This parameter allows you to enter a arbitrary comment on the group.
1830 @item @var{(variable form)}
1831 You can use the group parameters to set variables local to the group you
1832 are entering. Say you want to turn threading off in
1833 @samp{news.answers}. You'd then put @code{(gnus-show-threads nil)} in
1834 the group parameters of that group. @code{gnus-show-threads} will be
1835 made into a local variable in the summary buffer you enter, and the form
1836 @code{nil} will be @code{eval}ed there.
1838 This can also be used as a group-specific hook function, if you'd like.
1839 If you want to hear a beep when you enter the group
1840 @samp{alt.binaries.pictures.furniture}, you could put something like
1841 @code{(dummy-variable (ding))} in the parameters of that group.
1842 @code{dummy-variable} will be set to the result of the @code{(ding)}
1843 form, but who cares?
1847 Use the @kbd{G p} command to edit group parameters of a group.
1849 Also @xref{Topic Parameters}.
1852 @node Listing Groups
1853 @section Listing Groups
1854 @cindex group listing
1856 These commands all list various slices of the groups that are available.
1864 @findex gnus-group-list-groups
1865 List all groups that have unread articles
1866 (@code{gnus-group-list-groups}). If the numeric prefix is used, this
1867 command will list only groups of level ARG and lower. By default, it
1868 only lists groups of level five or lower (i.e., just subscribed groups).
1874 @findex gnus-group-list-all-groups
1875 List all groups, whether they have unread articles or not
1876 (@code{gnus-group-list-all-groups}). If the numeric prefix is used,
1877 this command will list only groups of level ARG and lower. By default,
1878 it lists groups of level seven or lower (i.e., just subscribed and
1879 unsubscribed groups).
1883 @findex gnus-group-list-level
1884 List all unread groups on a specific level
1885 (@code{gnus-group-list-level}). If given a prefix, also list the groups
1886 with no unread articles.
1890 @findex gnus-group-list-killed
1891 List all killed groups (@code{gnus-group-list-killed}). If given a
1892 prefix argument, really list all groups that are available, but aren't
1893 currently (un)subscribed. This could entail reading the active file
1898 @findex gnus-group-list-zombies
1899 List all zombie groups (@code{gnus-group-list-zombies}).
1903 @findex gnus-group-list-matching
1904 List all unread, subscribed groups with names that match a regexp
1905 (@code{gnus-group-list-matching}).
1909 @findex gnus-group-list-all-matching
1910 List groups that match a regexp (@code{gnus-group-list-all-matching}).
1914 @findex gnus-group-list-active
1915 List absolutely all groups that are in the active file(s) of the
1916 server(s) you are connected to (@code{gnus-group-list-active}). This
1917 might very well take quite a while. It might actually be a better idea
1918 to do a @kbd{A m} to list all matching, and just give @samp{.} as the
1919 thing to match on. Also note that this command may list group that
1920 don't exist (yet)---these will be listed as if they are killed groups.
1921 Take the output with some grains of salt.
1925 @findex gnus-group-apropos
1926 List all groups that have names that match a regexp
1927 (@code{gnus-group-apropos}).
1931 @findex gnus-group-description-apropos
1932 List all groups that have names or descriptions that match a regexp
1933 (@code{gnus-group-description-apropos}).
1937 @vindex gnus-permanently-visible-groups
1938 @cindex visible group parameter
1939 Groups that match the @code{gnus-permanently-visible-groups} regexp will
1940 always be shown, whether they have unread articles or not. You can also
1941 add the @code{visible} element to the group parameters in question to
1942 get the same effect.
1944 @vindex gnus-list-groups-with-ticked-articles
1945 Groups that have just ticked articles in it are normally listed in the
1946 group buffer. If @code{gnus-list-groups-with-ticked-articles} is
1947 @code{nil}, these groups will be treated just like totally empty
1948 groups. It is @code{t} by default.
1951 @node Sorting Groups
1952 @section Sorting Groups
1953 @cindex sorting groups
1955 @kindex C-c C-s (Group)
1956 @findex gnus-group-sort-groups
1957 @vindex gnus-group-sort-function
1958 The @kbd{C-c C-s} (@code{gnus-group-sort-groups}) command sorts the
1959 group buffer according to the function(s) given by the
1960 @code{gnus-group-sort-function} variable. Available sorting functions
1965 @item gnus-group-sort-by-alphabet
1966 @findex gnus-group-sort-by-alphabet
1967 Sort the group names alphabetically. This is the default.
1969 @item gnus-group-sort-by-real-name
1970 @findex gnus-group-sort-by-real-name
1971 Sort the group alphabetically on the real (unprefixed) group names.
1973 @item gnus-group-sort-by-level
1974 @findex gnus-group-sort-by-level
1975 Sort by group level.
1977 @item gnus-group-sort-by-score
1978 @findex gnus-group-sort-by-score
1979 Sort by group score.
1981 @item gnus-group-sort-by-rank
1982 @findex gnus-group-sort-by-rank
1983 Sort by group score and then the group level. The level and the score
1984 are, when taken together, the group's @dfn{rank}.
1986 @item gnus-group-sort-by-unread
1987 @findex gnus-group-sort-by-unread
1988 Sort by number of unread articles.
1990 @item gnus-group-sort-by-method
1991 @findex gnus-group-sort-by-method
1992 Sort by alphabetically on the select method.
1997 @code{gnus-group-sort-function} can also be a list of sorting
1998 functions. In that case, the most significant sort key function must be
2002 There are also a number of commands for sorting directly according to
2003 some sorting criteria:
2007 @kindex G S a (Group)
2008 @findex gnus-group-sort-groups-by-alphabet
2009 Sort the group buffer alphabetically by group name
2010 (@code{gnus-group-sort-groups-by-alphabet}).
2013 @kindex G S u (Group)
2014 @findex gnus-group-sort-groups-by-unread
2015 Sort the group buffer by the number of unread articles
2016 (@code{gnus-group-sort-groups-by-unread}).
2019 @kindex G S l (Group)
2020 @findex gnus-group-sort-groups-by-level
2021 Sort the group buffer by group level
2022 (@code{gnus-group-sort-groups-by-level}).
2025 @kindex G S v (Group)
2026 @findex gnus-group-sort-groups-by-score
2027 Sort the group buffer by group score
2028 (@code{gnus-group-sort-groups-by-score}).
2031 @kindex G S r (Group)
2032 @findex gnus-group-sort-groups-by-rank
2033 Sort the group buffer by group level
2034 (@code{gnus-group-sort-groups-by-rank}).
2037 @kindex G S m (Group)
2038 @findex gnus-group-sort-groups-by-method
2039 Sort the group buffer alphabetically by backend name
2040 (@code{gnus-group-sort-groups-by-method}).
2044 When given a prefix, all these commands will sort in reverse order.
2047 @node Group Maintenance
2048 @section Group Maintenance
2049 @cindex bogus groups
2054 @findex gnus-group-check-bogus-groups
2055 Find bogus groups and delete them
2056 (@code{gnus-group-check-bogus-groups}).
2060 @findex gnus-find-new-newsgroups
2061 Find new groups and process them (@code{gnus-find-new-newsgroups}). If
2062 given a prefix, use the @code{ask-server} method to query the server for
2066 @kindex C-c C-x (Group)
2067 @findex gnus-group-expire-articles
2068 Run all expirable articles in the current group through the expiry
2069 process (if any) (@code{gnus-group-expire-articles}).
2072 @kindex C-c M-C-x (Group)
2073 @findex gnus-group-expire-all-groups
2074 Run all articles in all groups through the expiry process
2075 (@code{gnus-group-expire-all-groups}).
2080 @node Browse Foreign Server
2081 @section Browse Foreign Server
2082 @cindex foreign servers
2083 @cindex browsing servers
2088 @findex gnus-group-browse-foreign-server
2089 You will be queried for a select method and a server name. Gnus will
2090 then attempt to contact this server and let you browse the groups there
2091 (@code{gnus-group-browse-foreign-server}).
2094 @findex gnus-browse-mode
2095 A new buffer with a list of available groups will appear. This buffer
2096 will be use the @code{gnus-browse-mode}. This buffer looks a bit
2097 (well, a lot) like a normal group buffer, but with one major difference
2098 - you can't enter any of the groups. If you want to read any of the
2099 news available on that server, you have to subscribe to the groups you
2100 think may be interesting, and then you have to exit this buffer. The
2101 new groups will be added to the group buffer, and then you can read them
2102 as you would any other group.
2104 Future versions of Gnus may possibly permit reading groups straight from
2107 Here's a list of keystrokes available in the browse mode:
2112 @findex gnus-group-next-group
2113 Go to the next group (@code{gnus-group-next-group}).
2117 @findex gnus-group-prev-group
2118 Go to the previous group (@code{gnus-group-prev-group}).
2121 @kindex SPACE (Browse)
2122 @findex gnus-browse-read-group
2123 Enter the current group and display the first article
2124 (@code{gnus-browse-read-group}).
2127 @kindex RET (Browse)
2128 @findex gnus-browse-select-group
2129 Enter the current group (@code{gnus-browse-select-group}).
2133 @findex gnus-browse-unsubscribe-current-group
2134 Unsubscribe to the current group, or, as will be the case here,
2135 subscribe to it (@code{gnus-browse-unsubscribe-current-group}).
2141 @findex gnus-browse-exit
2142 Exit browse mode (@code{gnus-browse-exit}).
2146 @findex gnus-browse-describe-briefly
2147 Describe browse mode briefly (well, there's not much to describe, is
2148 there) (@code{gnus-browse-describe-briefly}).
2153 @section Exiting Gnus
2154 @cindex exiting Gnus
2156 Yes, Gnus is ex(c)iting.
2161 @findex gnus-group-suspend
2162 Suspend Gnus (@code{gnus-group-suspend}). This doesn't really exit Gnus,
2163 but it kills all buffers except the Group buffer. I'm not sure why this
2164 is a gain, but then who am I to judge?
2168 @findex gnus-group-exit
2169 Quit Gnus (@code{gnus-group-exit}).
2173 @findex gnus-group-quit
2174 Quit Gnus without saving any startup files (@code{gnus-group-quit}).
2177 @vindex gnus-exit-gnus-hook
2178 @vindex gnus-suspend-gnus-hook
2179 @code{gnus-suspend-gnus-hook} is called when you suspend Gnus and
2180 @code{gnus-exit-gnus-hook} is called when you quit Gnus, while
2181 @code{gnus-after-exiting-gnus-hook} is called as the final item when
2186 If you wish to completely unload Gnus and all its adherents, you can use
2187 the @code{gnus-unload} command. This command is also very handy when
2188 trying to customize meta-variables.
2193 Miss Lisa Cannifax, while sitting in English class, feels her feet go
2194 numbly heavy and herself fall into a hazy trance as the boy sitting
2195 behind her drew repeated lines with his pencil across the back of her
2201 @section Group Topics
2204 If you read lots and lots of groups, it might be convenient to group
2205 them hierarchically according to topics. You put your Emacs groups over
2206 here, your sex groups over there, and the rest (what, two groups or so?)
2207 you put in some misc section that you never bother with anyway. You can
2208 even group the Emacs sex groups as a sub-topic to either the Emacs
2209 groups or the sex groups---or both! Go wild!
2211 @findex gnus-topic-mode
2213 To get this @emph{fab} functionality you simply turn on (ooh!) the
2214 @code{gnus-topic} minor mode---type @kbd{t} in the group buffer. (This
2215 is a toggling command.)
2217 Go ahead, just try it. I'll still be here when you get back. La de
2218 dum... Nice tune, that... la la la... What, you're back? Yes, and now
2219 press @kbd{l}. There. All your groups are now listed under
2220 @samp{misc}. Doesn't that make you feel all warm and fuzzy? Hot and
2223 If you want this permanently enabled, you should add that minor mode to
2224 the hook for the group mode:
2227 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
2231 * Topic Variables:: How to customize the topics the Lisp Way.
2232 * Topic Commands:: Interactive E-Z commands.
2233 * Topic Topology:: A map of the world.
2234 * Topic Parameters:: Parameters that apply to all groups in a topic.
2238 @node Topic Variables
2239 @subsection Topic Variables
2240 @cindex topic variables
2242 Now, if you select a topic, if will fold/unfold that topic, which is
2243 really neat, I think.
2245 @vindex gnus-topic-line-format
2246 The topic lines themselves are created according to the
2247 @code{gnus-topic-line-format} variable (@pxref{Formatting Variables}).
2260 Number of groups in the topic.
2262 Number of unread articles in the topic.
2264 Number of unread articles in the topic and all its subtopics.
2267 @vindex gnus-topic-indent-level
2268 Each sub-topic (and the groups in the sub-topics) will be indented with
2269 @code{gnus-topic-indent-level} times the topic level number of spaces.
2270 The default is @code{2}.
2272 @vindex gnus-topic-mode-hook
2273 @code{gnus-topic-mode-hook} is called in topic minor mode buffers.
2275 @vindex gnus-topic-display-empty-topics
2276 The @code{gnus-topic-display-empty-topics} says whether to display even
2277 topics that have no unread articles in them. The default is @code{t}.
2280 @node Topic Commands
2281 @subsection Topic Commands
2282 @cindex topic commands
2284 When the topic minor mode is turned on, a new @kbd{T} submap will be
2285 available. In addition, a few of the standard keys change their
2286 definitions slightly.
2292 @findex gnus-topic-create-topic
2293 Prompt for a new topic name and create it
2294 (@code{gnus-topic-create-topic}).
2298 @findex gnus-topic-move-group
2299 Move the current group to some other topic
2300 (@code{gnus-topic-move-group}). This command understands the
2301 process/prefix convention (@pxref{Process/Prefix}).
2305 @findex gnus-topic-copy-group
2306 Copy the current group to some other topic
2307 (@code{gnus-topic-copy-group}). This command understands the
2308 process/prefix convention (@pxref{Process/Prefix}).
2312 @findex gnus-topic-remove-group
2313 Remove a group from the current topic (@code{gnus-topic-remove-group}).
2314 This command understands the process/prefix convention
2315 (@pxref{Process/Prefix}).
2319 @findex gnus-topic-move-matching
2320 Move all groups that match some regular expression to a topic
2321 (@code{gnus-topic-move-matching}).
2325 @findex gnus-topic-copy-matching
2326 Copy all groups that match some regular expression to a topic
2327 (@code{gnus-topic-copy-matching}).
2331 @findex gnus-topic-mark-topic
2332 Mark all groups in the current topic with the process mark
2333 (@code{gnus-topic-mark-topic}).
2336 @kindex T M-# (Topic)
2337 @findex gnus-topic-unmark-topic
2338 Remove the process mark from all groups in the current topic
2339 (@code{gnus-topic-unmark-topic}).
2343 @findex gnus-topic-select-group
2345 Either select a group or fold a topic (@code{gnus-topic-select-group}).
2346 When you perform this command on a group, you'll enter the group, as
2347 usual. When done on a topic line, the topic will be folded (if it was
2348 visible) or unfolded (if it was folded already). So it's basically a
2349 toggling command on topics. In addition, if you give a numerical
2350 prefix, group on that level (and lower) will be displayed.
2353 @kindex T TAB (Topic)
2354 @findex gnus-topic-indent
2355 ``Indent'' the current topic so that it becomes a sub-topic of the
2356 previous topic (@code{gnus-topic-indent}). If given a prefix,
2357 ``un-indent'' the topic instead.
2361 @findex gnus-topic-kill-group
2362 Kill a group or topic (@code{gnus-topic-kill-group}).
2366 @findex gnus-topic-yank-group
2367 Yank the previously killed group or topic (@code{gnus-topic-yank-group}).
2368 Note that all topics will be yanked before all groups.
2372 @findex gnus-topic-rename
2373 Rename a topic (@code{gnus-topic-rename}).
2376 @kindex T DEL (Topic)
2377 @findex gnus-topic-delete
2378 Delete an empty topic (@code{gnus-topic-delete}).
2382 @findex gnus-topic-list-active
2383 List all groups that Gnus knows about in a topics-ified way
2384 (@code{gnus-topic-list-active}).
2388 @findex gnus-topic-edit-parameters
2389 @cindex group parameters
2390 @cindex topic parameters
2392 Edit the topic parameters (@code{gnus-topic-edit-parameters}).
2393 @xref{Topic Parameters}.
2398 @node Topic Topology
2399 @subsection Topic Topology
2400 @cindex topic topology
2403 So, let's have a look at an example group buffer:
2409 2: alt.religion.emacs
2412 0: comp.talk.emacs.recovery
2414 8: comp.binaries.fractals
2415 13: comp.sources.unix
2418 So, here we have one top-level topic, two topics under that, and one
2419 sub-topic under one of the sub-topics. (There is always just one (1)
2420 top-level topic). This topology can be expressed as follows:
2424 (("Emacs -- I wuw it!" visible)
2425 (("Naughty Emacs" visible)))
2429 @vindex gnus-topic-topology
2430 This is in fact how the variable @code{gnus-topic-topology} would look
2431 for the display above. That variable is saved in the @file{.newsrc.eld}
2432 file, and shouldn't be messed with manually---unless you really want
2433 to. Since this variable is read from the @file{.newsrc.eld} file,
2434 setting it in any other startup files will have no effect.
2436 This topology shows what topics are sub-topics of what topics (right),
2437 and which topics are visible. Two settings are currently
2438 allowed---@code{visible} and @code{invisible}.
2441 @node Topic Parameters
2442 @subsection Topic Parameters
2444 All groups in a topic will inherit group parameters from the parent (and
2445 ancestor) topic parameters. All legal group parameters are legal topic
2446 parameters (@pxref{Group Parameters}).
2448 Group parameters (of course) override topic parameters, and topic
2449 parameters in sub-topics override topic parameters in super-topics. You
2450 know. Normal inheretance rules. (@dfn{Rules} is here a noun, not a
2451 verb, although you may feel free to disagree with me here.)
2457 2: alt.religion.emacs
2461 0: comp.talk.emacs.recovery
2463 8: comp.binaries.fractals
2464 13: comp.sources.unix
2468 Now, the @samp{Emacs} topic has the topic parameter
2469 @code{(score-file . "emacs.SCORE")}; the @samp{Relief} topic has the topic
2470 parameter @code{(score-file . "relief.SCORE")}; and the @samp{Misc}
2471 topic has the topic parameter @code{(score-file . "emacs.SCORE")}. In
2472 addition, @samp{alt.religion.emacs} has the group parameter
2473 @code{(score-file . "religion.SCORE")}.
2475 Now, when you enter @samp{alt.sex.emacs} in the @samp{Relief} topic, you
2476 will get the @file{relief.SCORE} home score file. If you enter the same
2477 group in the @samp{Emacs} topic, you'll get the @file{emacs.SCORE} home
2478 score file. If you enter @samp{alt.religion.emacs}, you'll get the
2479 @file{religion.SCORE} home score file.
2481 This seems rather simple and self-evident, doesn't it? Well, yes. But
2482 there are some problems, especially with the @code{total-expiry}
2483 parameter. Say you have a mail group in two topics; one with
2484 @code{total-expiry} and one without. What happens when you do @kbd{M-x
2485 gnus-expire-all-expirable-groups}? Gnus has no way of telling which one
2486 of these topics you mean to expire articles from, so anything may
2487 happen. In fact, I hereby declare that it is @dfn{undefined} what
2488 happens. You just have to be careful if you do stuff like that.
2491 @node Misc Group Stuff
2492 @section Misc Group Stuff
2495 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
2496 * Group Information:: Information and help on groups and Gnus.
2497 * File Commands:: Reading and writing the Gnus files.
2504 @findex gnus-group-enter-server-mode
2505 Enter the server buffer (@code{gnus-group-enter-server-mode}). @xref{The
2510 @findex gnus-group-post-news
2511 Post an article to a group (@code{gnus-group-post-news}). The current
2512 group name will be used as the default.
2516 @findex gnus-group-mail
2517 Mail a message somewhere (@code{gnus-group-mail}).
2521 Variables for the group buffer:
2525 @item gnus-group-mode-hook
2526 @vindex gnus-group-mode-hook
2527 @code{gnus-group-mode-hook} is called after the group buffer has been
2530 @item gnus-group-prepare-hook
2531 @vindex gnus-group-prepare-hook
2532 @code{gnus-group-prepare-hook} is called after the group buffer is
2533 generated. It may be used to modify the buffer in some strange,
2536 @item gnus-permanently-visible-groups
2537 @vindex gnus-permanently-visible-groups
2538 Groups matching this regexp will always be listed in the group buffer,
2539 whether they are empty or not.
2544 @node Scanning New Messages
2545 @subsection Scanning New Messages
2546 @cindex new messages
2547 @cindex scanning new news
2553 @findex gnus-group-get-new-news
2554 Check the server(s) for new articles. If the numerical prefix is used,
2555 this command will check only groups of level @var{arg} and lower
2556 (@code{gnus-group-get-new-news}). If given a non-numerical prefix, this
2557 command will force a total rereading of the active file(s) from the
2562 @findex gnus-group-get-new-news-this-group
2563 @vindex gnus-goto-next-group-when-activating
2564 Check whether new articles have arrived in the current group
2565 (@code{gnus-group-get-new-news-this-group}). The
2566 @code{gnus-goto-next-group-when-activating} variable controls whether
2567 this command is to move point to the next group or not. It is @code{t}
2570 @findex gnus-activate-all-groups
2571 @cindex activating groups
2573 @kindex C-c M-g (Group)
2574 Activate absolutely all groups (@code{gnus-activate-all-groups}).
2579 @findex gnus-group-restart
2580 Restart Gnus (@code{gnus-group-restart}).
2584 @vindex gnus-get-new-news-hook
2585 @code{gnus-get-new-news-hook} is run just before checking for new news.
2587 @vindex gnus-after-getting-new-news-hook
2588 @code{gnus-after-getting-new-news-hook} is run after checking for new
2592 @node Group Information
2593 @subsection Group Information
2594 @cindex group information
2595 @cindex information on groups
2601 @findex gnus-group-fetch-faq
2602 @vindex gnus-group-faq-directory
2605 Try to fetch the FAQ for the current group
2606 (@code{gnus-group-fetch-faq}). Gnus will try to get the FAQ from
2607 @code{gnus-group-faq-directory}, which is usually a directory on a
2608 remote machine. This variable can also be a list of directories. In
2609 that case, giving a prefix to this command will allow you to choose
2610 between the various sites. @code{ange-ftp} will be used for fetching
2613 If fetching from the first site is unsuccessful, Gnus will attempt to go
2614 through @code{gnus-group-faq-directory} and try to open them one by one.
2618 @cindex describing groups
2619 @cindex group description
2620 @findex gnus-group-describe-group
2621 Describe the current group (@code{gnus-group-describe-group}). If given
2622 a prefix, force Gnus to re-read the description from the server.
2626 @findex gnus-group-describe-all-groups
2627 Describe all groups (@code{gnus-group-describe-all-groups}). If given a
2628 prefix, force Gnus to re-read the description file from the server.
2633 @findex gnus-version
2634 Display current Gnus version numbers (@code{gnus-version}).
2638 @findex gnus-group-describe-briefly
2639 Give a very short help message (@code{gnus-group-describe-briefly}).
2642 @kindex C-c C-i (Group)
2645 @findex gnus-info-find-node
2646 Go to the Gnus info node (@code{gnus-info-find-node}).
2651 @subsection File Commands
2652 @cindex file commands
2658 @findex gnus-group-read-init-file
2659 @vindex gnus-init-file
2660 @cindex reading init file
2661 Read the init file (@code{gnus-init-file}, which defaults to
2662 @file{~/.gnus}) (@code{gnus-group-read-init-file}).
2666 @findex gnus-group-save-newsrc
2667 @cindex saving .newsrc
2668 Save the @file{.newsrc.eld} file (and @file{.newsrc} if wanted)
2669 (@code{gnus-group-save-newsrc}). If given a prefix, force saving the
2670 file(s) whether Gnus thinks it is necessary or not.
2673 @c @kindex Z (Group)
2674 @c @findex gnus-group-clear-dribble
2675 @c Clear the dribble buffer (@code{gnus-group-clear-dribble}).
2680 @node The Summary Buffer
2681 @chapter The Summary Buffer
2682 @cindex summary buffer
2684 A line for each article is displayed in the summary buffer. You can
2685 move around, read articles, post articles and reply to articles.
2688 * Summary Buffer Format:: Deciding how the summary buffer is to look.
2689 * Summary Maneuvering:: Moving around the summary buffer.
2690 * Choosing Articles:: Reading articles.
2691 * Paging the Article:: Scrolling the current article.
2692 * Reply Followup and Post:: Posting articles.
2693 * Canceling and Superseding:: ``Whoops, I shouldn't have called him that.''
2694 * Marking Articles:: Marking articles as read, expirable, etc.
2695 * Limiting:: You can limit the summary buffer.
2696 * Threading:: How threads are made.
2697 * Sorting:: How articles and threads are sorted.
2698 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
2699 * Article Caching:: You may store articles in a cache.
2700 * Persistent Articles:: Making articles expiry-resistant.
2701 * Article Backlog:: Having already read articles hang around.
2702 * Saving Articles:: Ways of customizing article saving.
2703 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
2704 * Article Treatment:: The article buffer can be mangled at will.
2705 * Summary Sorting:: Sorting the summary buffer in various ways.
2706 * Finding the Parent:: No child support? Get the parent.
2707 * Alternative Approaches:: Reading using non-default summaries.
2708 * Tree Display:: A more visual display of threads.
2709 * Mail Group Commands:: Some commands can only be used in mail groups.
2710 * Various Summary Stuff:: What didn't fit anywhere else.
2711 * Exiting the Summary Buffer:: Returning to the Group buffer.
2712 * Crosspost Handling:: How crossposted articles are dealt with.
2713 * Duplicate Suppression:: An alternative when crosspost handling fails.
2717 @node Summary Buffer Format
2718 @section Summary Buffer Format
2719 @cindex summary buffer format
2722 * Summary Buffer Lines:: You can specify how summary lines should look.
2723 * Summary Buffer Mode Line:: You can say how the mode line should look.
2724 * Summary Highlighting:: Making the summary buffer all pretty and nice.
2727 @findex mail-extract-address-components
2728 @findex gnus-extract-address-components
2729 @vindex gnus-extract-address-components
2730 Gnus will use the value of the @code{gnus-extract-address-components}
2731 variable as a function for getting the name and address parts of a
2732 @code{From} header. Two pre-defined function exist:
2733 @code{gnus-extract-address-components}, which is the default, quite
2734 fast, and too simplistic solution; and
2735 @code{mail-extract-address-components}, which works very nicely, but is
2736 slower. The default function will return the wrong answer in 5% of the
2737 cases. If this is unacceptable to you, use the other function instead.
2739 @vindex gnus-summary-same-subject
2740 @code{gnus-summary-same-subject} is a string indicating that the current
2741 article has the same subject as the previous. This string will be used
2742 with those specs that require it. The default is @samp{}.
2745 @node Summary Buffer Lines
2746 @subsection Summary Buffer Lines
2748 @vindex gnus-summary-line-format
2749 You can change the format of the lines in the summary buffer by changing
2750 the @code{gnus-summary-line-format} variable. It works along the same
2751 lines a a normal @code{format} string, with some extensions
2752 (@pxref{Formatting Variables}).
2754 The default string is @samp{%U%R%z%I%(%[%4L: %-20,20n%]%) %s\n}.
2756 The following format specification characters are understood:
2764 Subject if the article is the root or the previous article had a
2765 different subject, @code{gnus-summary-same-subject} otherwise.
2766 (@code{gnus-summary-same-subject} defaults to @samp{}.)
2768 Full @code{From} header.
2770 The name (from the @code{From} header).
2772 The name (from the @code{From} header). This differs from the @code{n}
2773 spec in that it uses @code{gnus-extract-address-components}, which is
2774 slower, but may be more thorough.
2776 The address (from the @code{From} header). This works the same way as
2779 Number of lines in the article.
2781 Number of characters in the article.
2783 Indentation based on thread level (@pxref{Customizing Threading}).
2785 Nothing if the article is a root and lots of spaces if it isn't (it
2786 pushes everything after it off the screen).
2788 Opening bracket, which is normally @samp{\[}, but can also be @samp{<}
2789 for adopted articles (@pxref{Customizing Threading}).
2791 Closing bracket, which is normally @samp{\]}, but can also be @samp{>}
2792 for adopted articles.
2794 One space for each thread level.
2796 Twenty minus thread level spaces.
2804 @vindex gnus-summary-zcore-fuzz
2805 Zcore, @samp{+} if above the default level and @samp{-} if below the
2806 default level. If the difference between
2807 @code{gnus-summary-default-level} and the score is less than
2808 @code{gnus-summary-zcore-fuzz}, this spec will not be used.
2816 The @code{Date} in @code{YY-MMM} format.
2818 The @code{Date} in @code{YYYYMMDDTHHMMSS} format.
2824 Number of articles in the current sub-thread. Using this spec will slow
2825 down summary buffer generation somewhat.
2827 A single character will be displayed if the article has any children.
2831 User defined specifier. The next character in the format string should
2832 be a letter. @sc{gnus} will call the function
2833 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
2834 following @samp{%u}. The function will be passed the current header as
2835 argument. The function should return a string, which will be inserted
2836 into the summary just like information from any other summary specifier.
2839 The @samp{%U} (status), @samp{%R} (replied) and @samp{%z} (zcore) specs
2840 have to be handled with care. For reasons of efficiency, Gnus will
2841 compute what column these characters will end up in, and ``hard-code''
2842 that. This means that it is illegal to have these specs after a
2843 variable-length spec. Well, you might not be arrested, but your summary
2844 buffer will look strange, which is bad enough.
2846 The smart choice is to have these specs as far to the left as possible.
2847 (Isn't that the case with everything, though? But I digress.)
2849 This restriction may disappear in later versions of Gnus.
2852 @node Summary Buffer Mode Line
2853 @subsection Summary Buffer Mode Line
2855 @vindex gnus-summary-mode-line-format
2856 You can also change the format of the summary mode bar. Set
2857 @code{gnus-summary-mode-line-format} to whatever you like. Here are the
2858 elements you can play with:
2864 Unprefixed group name.
2866 Current article number.
2870 Number of unread articles in this group.
2872 Number of unselected articles in this group.
2874 A string with the number of unread and unselected articles represented
2875 either as @samp{<%U(+%u) more>} if there are both unread and unselected
2876 articles, and just as @samp{<%U more>} if there are just unread articles
2877 and no unselected ones.
2879 Shortish group name. For instance, @samp{rec.arts.anime} will be
2880 shortened to @samp{r.a.anime}.
2882 Subject of the current article.
2886 Name of the current score file.
2888 Number of dormant articles.
2890 Number of ticked articles.
2892 Number of articles that have been marked as read in this session.
2894 Number of articles expunged by the score files.
2898 @node Summary Highlighting
2899 @subsection Summary Highlighting
2903 @item gnus-visual-mark-article-hook
2904 @vindex gnus-visual-mark-article-hook
2905 This hook is run after selecting an article. It is meant to be used for
2906 highlighting the article in some way. It is not run if
2907 @code{gnus-visual} is @code{nil}.
2909 @item gnus-summary-update-hook
2910 @vindex gnus-summary-update-hook
2911 This hook is called when a summary line is changed. It is not run if
2912 @code{gnus-visual} is @code{nil}.
2914 @item gnus-summary-selected-face
2915 @vindex gnus-summary-selected-face
2916 This is the face (or @dfn{font} as some people call it) that is used to
2917 highlight the current article in the summary buffer.
2919 @item gnus-summary-highlight
2920 @vindex gnus-summary-highlight
2921 Summary lines are highlighted according to this variable, which is a
2922 list where the elements are on the format @code{(FORM . FACE)}. If you
2923 would, for instance, like ticked articles to be italic and high-scored
2924 articles to be bold, you could set this variable to something like
2926 (((eq mark gnus-ticked-mark) . italic)
2927 ((> score default) . bold))
2929 As you may have guessed, if @var{FORM} returns a non-@code{nil} value,
2930 @var{FACE} will be applied to the line.
2934 @node Summary Maneuvering
2935 @section Summary Maneuvering
2936 @cindex summary movement
2938 All the straight movement commands understand the numeric prefix and
2939 behave pretty much as you'd expect.
2941 None of these commands select articles.
2946 @kindex M-n (Summary)
2947 @kindex G M-n (Summary)
2948 @findex gnus-summary-next-unread-subject
2949 Go to the next summary line of an unread article
2950 (@code{gnus-summary-next-unread-subject}).
2954 @kindex M-p (Summary)
2955 @kindex G M-p (Summary)
2956 @findex gnus-summary-prev-unread-subject
2957 Go to the previous summary line of an unread article
2958 (@code{gnus-summary-prev-unread-subject}).
2963 @kindex G j (Summary)
2964 @findex gnus-summary-goto-article
2965 Ask for an article number and then go that article
2966 (@code{gnus-summary-goto-article}).
2969 @kindex G g (Summary)
2970 @findex gnus-summary-goto-subject
2971 Ask for an article number and then go the summary line of that article
2972 (@code{gnus-summary-goto-subject}).
2975 If Gnus asks you to press a key to confirm going to the next group, you
2976 can use the @kbd{C-n} and @kbd{C-p} keys to move around the group
2977 buffer, searching for the next group to read without actually returning
2978 to the group buffer.
2980 Variables related to summary movement:
2984 @vindex gnus-auto-select-next
2985 @item gnus-auto-select-next
2986 If you are at the end of the group and issue one of the movement
2987 commands, Gnus will offer to go to the next group. If this variable is
2988 @code{t} and the next group is empty, Gnus will exit summary mode and
2989 return to the group buffer. If this variable is neither @code{t} nor
2990 @code{nil}, Gnus will select the next group, no matter whether it has
2991 any unread articles or not. As a special case, if this variable is
2992 @code{quietly}, Gnus will select the next group without asking for
2993 confirmation. If this variable is @code{almost-quietly}, the same will
2994 happen only if you are located on the last article in the group.
2995 Finally, if this variable is @code{slightly-quietly}, the @kbd{Z n}
2996 command will go to the next group without confirmation. Also
2997 @pxref{Group Levels}.
2999 @item gnus-auto-select-same
3000 @vindex gnus-auto-select-same
3001 If non-@code{nil}, all the movement commands will try to go to the next
3002 article with the same subject as the current. (@dfn{Same} here might
3003 mean @dfn{roughly equal}. See @code{gnus-summary-gather-subject-limit}
3004 for details (@pxref{Customizing Threading}).) This variable is not
3005 particularly useful if you use a threaded display.
3007 @item gnus-summary-check-current
3008 @vindex gnus-summary-check-current
3009 If non-@code{nil}, all the ``unread'' movement commands will not proceed
3010 to the next (or previous) article if the current article is unread.
3011 Instead, they will choose the current article.
3013 @item gnus-auto-center-summary
3014 @vindex gnus-auto-center-summary
3015 If non-@code{nil}, Gnus will keep the point in the summary buffer
3016 centered at all times. This makes things quite tidy, but if you have a
3017 slow network connection, or simply do not like this un-Emacsism, you can
3018 set this variable to @code{nil} to get the normal Emacs scrolling
3019 action. This will also inhibit horizontal re-centering of the summary
3020 buffer, which might make it more inconvenient to read extremely long
3026 @node Choosing Articles
3027 @section Choosing Articles
3028 @cindex selecting articles
3030 None of the following movement commands understand the numeric prefix,
3031 and they all select and display an article.
3035 @kindex SPACE (Summary)
3036 @findex gnus-summary-next-page
3037 Select the current article, or, if that one's read already, the next
3038 unread article (@code{gnus-summary-next-page}).
3043 @kindex G n (Summary)
3044 @findex gnus-summary-next-unread-article
3045 Go to next unread article (@code{gnus-summary-next-unread-article}).
3050 @findex gnus-summary-prev-unread-article
3051 Go to previous unread article (@code{gnus-summary-prev-unread-article}).
3056 @kindex G N (Summary)
3057 @findex gnus-summary-next-article
3058 Go to the next article (@code{gnus-summary-next-article}).
3063 @kindex G P (Summary)
3064 @findex gnus-summary-prev-article
3065 Go to the previous article (@code{gnus-summary-prev-article}).
3068 @kindex G C-n (Summary)
3069 @findex gnus-summary-next-same-subject
3070 Go to the next article with the same subject
3071 (@code{gnus-summary-next-same-subject}).
3074 @kindex G C-p (Summary)
3075 @findex gnus-summary-prev-same-subject
3076 Go to the previous article with the same subject
3077 (@code{gnus-summary-prev-same-subject}).
3081 @kindex G f (Summary)
3083 @findex gnus-summary-first-unread-article
3084 Go to the first unread article
3085 (@code{gnus-summary-first-unread-article}).
3089 @kindex G b (Summary)
3091 @findex gnus-summary-best-unread-article
3092 Go to the article with the highest score
3093 (@code{gnus-summary-best-unread-article}).
3098 @kindex G l (Summary)
3099 @findex gnus-summary-goto-last-article
3100 Go to the previous article read (@code{gnus-summary-goto-last-article}).
3103 @kindex G p (Summary)
3104 @findex gnus-summary-pop-article
3105 Pop an article off the summary history and go to this article
3106 (@code{gnus-summary-pop-article}). This command differs from the
3107 command above in that you can pop as many previous articles off the
3108 history as you like.
3111 Some variables that are relevant for moving and selecting articles:
3114 @item gnus-auto-extend-newsgroup
3115 @vindex gnus-auto-extend-newsgroup
3116 All the movement commands will try to go to the previous (or next)
3117 article, even if that article isn't displayed in the Summary buffer if
3118 this variable is non-@code{nil}. Gnus will then fetch the article from
3119 the server and display it in the article buffer.
3121 @item gnus-select-article-hook
3122 @vindex gnus-select-article-hook
3123 This hook is called whenever an article is selected. By default it
3124 exposes any threads hidden under the selected article.
3126 @item gnus-mark-article-hook
3127 @vindex gnus-mark-article-hook
3128 @findex gnus-summary-mark-unread-as-read
3129 @findex gnus-summary-mark-read-and-unread-as-read
3130 @findex gnus-unread-mark
3131 This hook is called whenever an article is selected. It is intended to
3132 be used for marking articles as read. The default value is
3133 @code{gnus-summary-mark-read-and-unread-as-read}, and will change the
3134 mark of almost any article you read to @code{gnus-unread-mark}. The
3135 only articles not affected by this function are ticked, dormant, and
3136 expirable articles. If you'd instead like to just have unread articles
3137 marked as read, you can use @code{gnus-summary-mark-unread-as-read}
3138 instead. It will leave marks like @code{gnus-low-score-mark},
3139 @code{gnus-del-mark} (and so on) alone.
3144 @node Paging the Article
3145 @section Scrolling the Article
3146 @cindex article scrolling
3151 @kindex SPACE (Summary)
3152 @findex gnus-summary-next-page
3153 Pressing @kbd{SPACE} will scroll the current article forward one page,
3154 or, if you have come to the end of the current article, will choose the
3155 next article (@code{gnus-summary-next-page}).
3158 @kindex DEL (Summary)
3159 @findex gnus-summary-prev-page
3160 Scroll the current article back one page (@code{gnus-summary-prev-page}).
3163 @kindex RET (Summary)
3164 @findex gnus-summary-scroll-up
3165 Scroll the current article one line forward
3166 (@code{gnus-summary-scroll-up}).
3170 @kindex A g (Summary)
3172 @findex gnus-summary-show-article
3173 (Re)fetch the current article (@code{gnus-summary-show-article}). If
3174 given a prefix, fetch the current article, but don't run any of the
3175 article treatment functions. This will give you a ``raw'' article, just
3176 the way it came from the server.
3181 @kindex A < (Summary)
3182 @findex gnus-summary-beginning-of-article
3183 Scroll to the beginning of the article
3184 (@code{gnus-summary-beginning-of-article}).
3189 @kindex A > (Summary)
3190 @findex gnus-summary-end-of-article
3191 Scroll to the end of the article (@code{gnus-summary-end-of-article}).
3194 @kindex A s (Summary)
3195 @findex gnus-summary-isearch-article
3196 Perform an isearch in the article buffer
3197 (@code{gnus-summary-isearch-article}).
3202 @node Reply Followup and Post
3203 @section Reply, Followup and Post
3206 * Summary Mail Commands:: Sending mail.
3207 * Summary Post Commands:: Sending news.
3211 @node Summary Mail Commands
3212 @subsection Summary Mail Commands
3214 @cindex composing mail
3216 Commands for composing a mail message:
3222 @kindex S r (Summary)
3224 @findex gnus-summary-reply
3225 Mail a reply to the author of the current article
3226 (@code{gnus-summary-reply}).
3231 @kindex S R (Summary)
3232 @findex gnus-summary-reply-with-original
3233 Mail a reply to the author of the current article and include the
3234 original message (@code{gnus-summary-reply-with-original}). This
3235 command uses the process/prefix convention.
3238 @kindex S o m (Summary)
3239 @findex gnus-summary-mail-forward
3240 Forward the current article to some other person
3241 (@code{gnus-summary-mail-forward}).
3244 @kindex S o p (Summary)
3245 @findex gnus-summary-post-forward
3246 Forward the current article to a newsgroup
3247 (@code{gnus-summary-post-forward}).
3252 @kindex S m (Summary)
3253 @findex gnus-summary-mail-other-window
3254 Send a mail to some other person
3255 (@code{gnus-summary-mail-other-window}).
3258 @kindex S D b (Summary)
3259 @findex gnus-summary-resend-bounced-mail
3260 @cindex bouncing mail
3261 If you have sent a mail, but the mail was bounced back to you for some
3262 reason (wrong address, transient failure), you can use this command to
3263 resend that bounced mail (@code{gnus-summary-resend-bounced-mail}). You
3264 will be popped into a mail buffer where you can edit the headers before
3265 sending the mail off again. If you give a prefix to this command, and
3266 the bounced mail is a reply to some other mail, Gnus will try to fetch
3267 that mail and display it for easy perusal of its headers. This might
3268 very well fail, though.
3271 @kindex S D r (Summary)
3272 @findex gnus-summary-resend-message
3273 Not to be confused with the previous command,
3274 @code{gnus-summary-resend-message} will prompt you for an address to
3275 send the current message off to, and then send it to that place. The
3276 headers of the message won't be altered---but lots of headers that say
3277 @code{Resent-To}, @code{Resent-From} and so on will be added. This
3278 means that you actually send a mail to someone that has a @code{To}
3279 header that (probably) points to yourself. This will confuse people.
3280 So, natcherly you'll only do that if you're really eVIl.
3282 This command is mainly used if you have several accounts and want to
3283 ship a mail to a different account of yours. (If you're both
3284 @code{root} and @code{postmaster} and get a mail for @code{postmaster}
3285 to the @code{root} account, you may want to resend it to
3286 @code{postmaster}. Ordnung muss sein!
3289 @kindex S O m (Summary)
3290 @findex gnus-uu-digest-mail-forward
3291 Digest the current series and forward the result using mail
3292 (@code{gnus-uu-digest-mail-forward}). This command uses the
3293 process/prefix convention (@pxref{Process/Prefix}).
3296 @kindex S O p (Summary)
3297 @findex gnus-uu-digest-post-forward
3298 Digest the current series and forward the result to a newsgroup
3299 (@code{gnus-uu-digest-mail-forward}).
3302 @kindex S M-c (Summary)
3303 @findex gnus-summary-mail-crosspost-complaint
3304 @cindex crossposting
3305 @cindex excessive crossposting
3306 Send a complaint about excessive crossposting to the author of the
3307 current article (@code{gnus-summary-mail-crosspost-complaint}).
3309 @findex gnus-crosspost-complaint
3310 This command is provided as a way to fight back agains the current
3311 crossposting pandemic that's sweeping Usenet. It will compose a reply
3312 using the @code{gnus-crosspost-complaint} variable as a preamble. This
3313 command understands the process/prefix convention
3314 (@pxref{Process/Prefix}) and will prompt you before sending each mail.
3319 @node Summary Post Commands
3320 @subsection Summary Post Commands
3322 @cindex composing news
3324 Commands for posting an article:
3330 @kindex S p (Summary)
3331 @findex gnus-summary-post-news
3332 Post an article to the current group
3333 (@code{gnus-summary-post-news}).
3338 @kindex S f (Summary)
3339 @findex gnus-summary-followup
3340 Post a followup to the current article (@code{gnus-summary-followup}).
3344 @kindex S F (Summary)
3346 @findex gnus-summary-followup-with-original
3347 Post a followup to the current article and include the original message
3348 (@code{gnus-summary-followup-with-original}). This command uses the
3349 process/prefix convention.
3352 @kindex S u (Summary)
3353 @findex gnus-uu-post-news
3354 Uuencode a file, split it into parts, and post it as a series
3355 (@code{gnus-uu-post-news}). (@pxref{Uuencoding and Posting}).
3359 @node Canceling and Superseding
3360 @section Canceling Articles
3361 @cindex canceling articles
3362 @cindex superseding articles
3364 Have you ever written something, and then decided that you really,
3365 really, really wish you hadn't posted that?
3367 Well, you can't cancel mail, but you can cancel posts.
3369 @findex gnus-summary-cancel-article
3371 Find the article you wish to cancel (you can only cancel your own
3372 articles, so don't try any funny stuff). Then press @kbd{C} or @kbd{S
3373 c} (@code{gnus-summary-cancel-article}). Your article will be
3374 canceled---machines all over the world will be deleting your article.
3376 Be aware, however, that not all sites honor cancels, so your article may
3377 live on here and there, while most sites will delete the article in
3380 If you discover that you have made some mistakes and want to do some
3381 corrections, you can post a @dfn{superseding} article that will replace
3382 your original article.
3384 @findex gnus-summary-supersede-article
3386 Go to the original article and press @kbd{S s}
3387 (@code{gnus-summary-supersede-article}). You will be put in a buffer
3388 where you can edit the article all you want before sending it off the
3391 The same goes for superseding as for canceling, only more so: Some
3392 sites do not honor superseding. On those sites, it will appear that you
3393 have posted almost the same article twice.
3395 If you have just posted the article, and change your mind right away,
3396 there is a trick you can use to cancel/supersede the article without
3397 waiting for the article to appear on your site first. You simply return
3398 to the post buffer (which is called @code{*post-buf*}). There you will
3399 find the article you just posted, with all the headers intact. Change
3400 the @code{Message-ID} header to a @code{Cancel} or @code{Supersedes}
3401 header by substituting one of those words for @code{Message-ID}. Then
3402 just press @kbd{C-c C-c} to send the article as you would do normally.
3403 The previous article will be canceled/superseded.
3405 Just remember, kids: There is no 'c' in 'supersede'.
3408 @node Marking Articles
3409 @section Marking Articles
3410 @cindex article marking
3411 @cindex article ticking
3414 There are several marks you can set on an article.
3416 You have marks that decide the @dfn{readedness} (whoo, neato-keano
3417 neologism ohoy!) of the article. Alphabetic marks generally mean
3418 @dfn{read}, while non-alphabetic characters generally mean @dfn{unread}.
3420 In addition, you also have marks that do not affect readedness.
3423 * Unread Articles:: Marks for unread articles.
3424 * Read Articles:: Marks for read articles.
3425 * Other Marks:: Marks that do not affect readedness.
3429 There's a plethora of commands for manipulating these marks:
3433 * Setting Marks:: How to set and remove marks.
3434 * Setting Process Marks:: How to mark articles for later processing.
3438 @node Unread Articles
3439 @subsection Unread Articles
3441 The following marks mark articles as unread, in one form or other.
3443 @vindex gnus-dormant-mark
3444 @vindex gnus-ticked-mark
3447 @dfn{Ticked articles} are articles that will remain visible always. If
3448 you see an article that you find interesting, or you want to put off
3449 reading it, or replying to it, until sometime later, you'd typically
3450 tick it. However, articles can be expired, so if you want to keep an
3451 article forever, you'll have to save it. Ticked articles have a
3452 @samp{!} (@code{gnus-ticked-mark}) in the first column.
3455 @vindex gnus-dormant-mark
3456 A @dfn{dormant} article is marked with a @samp{?}
3457 (@code{gnus-dormant-mark}), and will only appear in the summary buffer
3458 if there are followups to it.
3461 @vindex gnus-unread-mark
3462 An @dfn{unread} article is marked with a @samp{SPACE}
3463 (@code{gnus-unread-mark}). These are articles that haven't been read at
3469 @subsection Read Articles
3470 @cindex expirable mark
3472 All the following marks mark articles as read.
3477 @vindex gnus-del-mark
3478 Articles that are marked as read. They have a @samp{r}
3479 (@code{gnus-del-mark}) in the first column. These are articles that the
3480 user has marked as read more or less manually.
3483 @vindex gnus-read-mark
3484 Articles that are actually read are marked with @samp{R}
3485 (@code{gnus-read-mark}).
3488 @vindex gnus-ancient-mark
3489 Articles that were marked as read in previous sessions are now
3490 @dfn{old} and marked with @samp{O} (@code{gnus-ancient-mark}).
3493 @vindex gnus-killed-mark
3494 Marked as killed (@code{gnus-killed-mark}).
3497 @vindex gnus-kill-file-mark
3498 Marked as killed by kill files (@code{gnus-kill-file-mark}).
3501 @vindex gnus-low-score-mark
3502 Marked as read by having a too low score (@code{gnus-low-score-mark}).
3505 @vindex gnus-catchup-mark
3506 Marked as read by a catchup (@code{gnus-catchup-mark}).
3509 @vindex gnus-canceled-mark
3510 Canceled article (@code{gnus-canceled-mark})
3513 @vindex gnus-souped-mark
3514 @sc{SOUP}ed article (@code{gnus-souped-mark}). @xref{SOUP}
3517 @vindex gnus-sparse-mark
3518 Sparsely reffed article (@code{gnus-sparse-mark}). @xref{Customizing
3522 @vindex gnus-duplicate-mark
3523 Article marked as read by duplicate suppression
3524 (@code{gnus-duplicated-mark}). @xref{Duplicate Suppression}
3528 All these marks just mean that the article is marked as read, really.
3529 They are interpreted differently by the adaptive scoring scheme,
3532 One more special mark, though:
3536 @vindex gnus-expirable-mark
3537 You can also mark articles as @dfn{expirable} (or have them marked as
3538 such automatically). That doesn't make much sense in normal groups,
3539 because a user does not control the expiring of news articles, but in
3540 mail groups, for instance, articles that are marked as @dfn{expirable}
3541 can be deleted by Gnus at any time. Expirable articles are marked with
3542 @samp{E} (@code{gnus-expirable-mark}).
3547 @subsection Other Marks
3548 @cindex process mark
3551 There are some marks that have nothing to do with whether the article is
3557 You can set a bookmark in the current article. Say you are reading a
3558 long thesis on cats' urinary tracts, and have to go home for dinner
3559 before you've finished reading the thesis. You can then set a bookmark
3560 in the article, and Gnus will jump to this bookmark the next time it
3561 encounters the article.
3564 @vindex gnus-replied-mark
3565 All articles that you have replied to or made a followup to (i.e., have
3566 answered) will be marked with an @samp{A} in the second column
3567 (@code{gnus-replied-mark}).
3570 @vindex gnus-cached-mark
3571 Articles that are stored in the article cache will be marked with an
3572 @samp{*} in the second column (@code{gnus-cached-mark}).
3575 @vindex gnus-saved-mark
3576 Articles that are ``saved'' (in some manner or other; not necessarily
3577 religiously) are marked with an @samp{S} in the second column
3578 (@code{gnus-saved-mark}.
3581 @vindex gnus-not-empty-thread-mark
3582 @vindex gnus-empty-thread-mark
3583 It the @samp{%e} spec is used, the presence of threads or not will be
3584 marked with @code{gnus-not-empty-thread-mark} and
3585 @code{gnus-empty-thread-mark} in the third column, respectively.
3588 @vindex gnus-process-mark
3589 Finally we have the @dfn{process mark} (@code{gnus-process-mark}. A
3590 variety of commands react to the presence of the process mark. For
3591 instance, @kbd{X u} (@code{gnus-uu-decode-uu}) will uudecode and view
3592 all articles that have been marked with the process mark. Articles
3593 marked with the process mark have a @samp{#} in the second column.
3597 You might have noticed that most of these ``non-readedness'' marks
3598 appear in the second column by default. So if you have a cached, saved,
3599 replied article that you have process-marked, what will that look like?
3601 Nothing much. The precedence rules go as follows: process -> cache ->
3602 replied -> saved. So if the article is in the cache and is replied,
3603 you'll only see the cache mark and not the replied mark.
3607 @subsection Setting Marks
3608 @cindex setting marks
3610 All the marking commands understand the numeric prefix.
3616 @kindex M t (Summary)
3617 @findex gnus-summary-tick-article-forward
3618 Tick the current article (@code{gnus-summary-tick-article-forward}).
3623 @kindex M ? (Summary)
3624 @findex gnus-summary-mark-as-dormant
3625 Mark the current article as dormant
3626 (@code{gnus-summary-mark-as-dormant}).
3630 @kindex M d (Summary)
3632 @findex gnus-summary-mark-as-read-forward
3633 Mark the current article as read
3634 (@code{gnus-summary-mark-as-read-forward}).
3638 @findex gnus-summary-mark-as-read-backward
3639 Mark the current article as read and move point to the previous line
3640 (@code{gnus-summary-mark-as-read-backward}).
3645 @kindex M k (Summary)
3646 @findex gnus-summary-kill-same-subject-and-select
3647 Mark all articles that have the same subject as the current one as read,
3648 and then select the next unread article
3649 (@code{gnus-summary-kill-same-subject-and-select}).
3653 @kindex M K (Summary)
3654 @kindex C-k (Summary)
3655 @findex gnus-summary-kill-same-subject
3656 Mark all articles that have the same subject as the current one as read
3657 (@code{gnus-summary-kill-same-subject}).
3660 @kindex M C (Summary)
3661 @findex gnus-summary-catchup
3662 Mark all unread articles in the group as read
3663 (@code{gnus-summary-catchup}).
3666 @kindex M C-c (Summary)
3667 @findex gnus-summary-catchup-all
3668 Mark all articles in the group as read---even the ticked and dormant
3669 articles (@code{gnus-summary-catchup-all}).
3672 @kindex M H (Summary)
3673 @findex gnus-summary-catchup-to-here
3674 Catchup the current group to point
3675 (@code{gnus-summary-catchup-to-here}).
3678 @kindex C-w (Summary)
3679 @findex gnus-summary-mark-region-as-read
3680 Mark all articles between point and mark as read
3681 (@code{gnus-summary-mark-region-as-read}).
3684 @kindex M V k (Summary)
3685 @findex gnus-summary-kill-below
3686 Kill all articles with scores below the default score (or below the
3687 numeric prefix) (@code{gnus-summary-kill-below}).
3691 @kindex M c (Summary)
3692 @kindex M-u (Summary)
3693 @findex gnus-summary-clear-mark-forward
3694 Clear all readedness-marks from the current article
3695 (@code{gnus-summary-clear-mark-forward}).
3699 @kindex M e (Summary)
3701 @findex gnus-summary-mark-as-expirable
3702 Mark the current article as expirable
3703 (@code{gnus-summary-mark-as-expirable}).
3706 @kindex M b (Summary)
3707 @findex gnus-summary-set-bookmark
3708 Set a bookmark in the current article
3709 (@code{gnus-summary-set-bookmark}).
3712 @kindex M B (Summary)
3713 @findex gnus-summary-remove-bookmark
3714 Remove the bookmark from the current article
3715 (@code{gnus-summary-remove-bookmark}).
3718 @kindex M V c (Summary)
3719 @findex gnus-summary-clear-above
3720 Clear all marks from articles with scores over the default score (or
3721 over the numeric prefix) (@code{gnus-summary-clear-above}).
3724 @kindex M V u (Summary)
3725 @findex gnus-summary-tick-above
3726 Tick all articles with scores over the default score (or over the
3727 numeric prefix) (@code{gnus-summary-tick-above}).
3730 @kindex M V m (Summary)
3731 @findex gnus-summary-mark-above
3732 Prompt for a mark, and mark all articles with scores over the default
3733 score (or over the numeric prefix) with this mark
3734 (@code{gnus-summary-clear-above}).
3737 @vindex gnus-summary-goto-unread
3738 The @code{gnus-summary-goto-unread} variable controls what action should
3739 be taken after setting a mark. If non-@code{nil}, point will move to
3740 the next/previous unread article. If @code{nil}, point will just move
3741 one line up or down. As a special case, if this variable is
3742 @code{never}, all the marking commands as well as other commands (like
3743 @kbd{SPACE}) will move to the next article, whether it is unread or not.
3744 The default is @code{t}.
3747 @node Setting Process Marks
3748 @subsection Setting Process Marks
3749 @cindex setting process marks
3756 @kindex M P p (Summary)
3757 @findex gnus-summary-mark-as-processable
3758 Mark the current article with the process mark
3759 (@code{gnus-summary-mark-as-processable}).
3760 @findex gnus-summary-unmark-as-processable
3764 @kindex M P u (Summary)
3765 @kindex M-# (Summary)
3766 Remove the process mark, if any, from the current article
3767 (@code{gnus-summary-unmark-as-processable}).
3770 @kindex M P U (Summary)
3771 @findex gnus-summary-unmark-all-processable
3772 Remove the process mark from all articles
3773 (@code{gnus-summary-unmark-all-processable}).
3776 @kindex M P R (Summary)
3777 @findex gnus-uu-mark-by-regexp
3778 Mark articles by a regular expression (@code{gnus-uu-mark-by-regexp}).
3781 @kindex M P r (Summary)
3782 @findex gnus-uu-mark-region
3783 Mark articles in region (@code{gnus-uu-mark-region}).
3786 @kindex M P t (Summary)
3787 @findex gnus-uu-mark-thread
3788 Mark all articles in the current (sub)thread
3789 (@code{gnus-uu-mark-thread}).
3792 @kindex M P T (Summary)
3793 @findex gnus-uu-unmark-thread
3794 Unmark all articles in the current (sub)thread
3795 (@code{gnus-uu-unmark-thread}).
3798 @kindex M P v (Summary)
3799 @findex gnus-uu-mark-over
3800 Mark all articles that have a score above the prefix argument
3801 (@code{gnus-uu-mark-over}).
3804 @kindex M P s (Summary)
3805 @findex gnus-uu-mark-series
3806 Mark all articles in the current series (@code{gnus-uu-mark-series}).
3809 @kindex M P S (Summary)
3810 @findex gnus-uu-mark-sparse
3811 Mark all series that have already had some articles marked
3812 (@code{gnus-uu-mark-sparse}).
3815 @kindex M P a (Summary)
3816 @findex gnus-uu-mark-all
3817 Mark all articles in series order (@code{gnus-uu-mark-series}).
3820 @kindex M P b (Summary)
3821 @findex gnus-uu-mark-buffer
3822 Mark all articles in the buffer in the order they appear
3823 (@code{gnus-uu-mark-buffer}).
3826 @kindex M P k (Summary)
3827 @findex gnus-summary-kill-process-mark
3828 Push the current process mark set onto the stack and unmark all articles
3829 (@code{gnus-summary-kill-process-mark}).
3832 @kindex M P y (Summary)
3833 @findex gnus-summary-yank-process-mark
3834 Pop the previous process mark set from the stack and restore it
3835 (@code{gnus-summary-yank-process-mark}).
3838 @kindex M P w (Summary)
3839 @findex gnus-summary-save-process-mark
3840 Push the current process mark set onto the stack
3841 (@code{gnus-summary-save-process-mark}).
3850 It can be convenient to limit the summary buffer to just show some
3851 subset of the articles currently in the group. The effect most limit
3852 commands have is to remove a few (or many) articles from the summary
3859 @kindex / / (Summary)
3860 @findex gnus-summary-limit-to-subject
3861 Limit the summary buffer to articles that match some subject
3862 (@code{gnus-summary-limit-to-subject}).
3865 @kindex / a (Summary)
3866 @findex gnus-summary-limit-to-author
3867 Limit the summary buffer to articles that match some author
3868 (@code{gnus-summary-limit-to-author}).
3872 @kindex / u (Summary)
3874 @findex gnus-summary-limit-to-unread
3875 Limit the summary buffer to articles that are not marked as read
3876 (@code{gnus-summary-limit-to-unread}). If given a prefix, limit the
3877 buffer to articles that are strictly unread. This means that ticked and
3878 dormant articles will also be excluded.
3881 @kindex / m (Summary)
3882 @findex gnus-summary-limit-to-marks
3883 Ask for a mark and then limit to all articles that have not been marked
3884 with that mark (@code{gnus-summary-limit-to-marks}).
3887 @kindex / n (Summary)
3888 @findex gnus-summary-limit-to-articles
3889 Limit the summary buffer to the current article
3890 (@code{gnus-summary-limit-to-articles}). Uses the process/prefix
3891 convention (@pxref{Process/Prefix}).
3894 @kindex / w (Summary)
3895 @findex gnus-summary-pop-limit
3896 Pop the previous limit off the stack and restore it
3897 (@code{gnus-summary-pop-limit}). If given a prefix, pop all limits off
3901 @kindex / v (Summary)
3902 @findex gnus-summary-limit-to-score
3903 Limit the summary buffer to articles that have a score at or above some
3904 score (@code{gnus-summary-limit-to-score}).
3908 @kindex M S (Summary)
3909 @kindex / E (Summary)
3910 @findex gnus-summary-limit-include-expunged
3911 Display all expunged articles
3912 (@code{gnus-summary-limit-include-expunged}).
3915 @kindex / D (Summary)
3916 @findex gnus-summary-limit-include-dormant
3917 Display all dormant articles (@code{gnus-summary-limit-include-dormant}).
3920 @kindex / d (Summary)
3921 @findex gnus-summary-limit-exclude-dormant
3922 Hide all dormant articles (@code{gnus-summary-limit-exclude-dormant}).
3925 @kindex / c (Summary)
3926 @findex gnus-summary-limit-exclude-childless-dormant
3927 Hide all dormant articles that have no children
3928 (@code{gnus-summary-limit-exclude-childless-dormant}).
3931 @kindex / C (Summary)
3932 @findex gnus-summary-limit-mark-excluded-as-read
3933 Mark all excluded unread articles as read
3934 (@code{gnus-summary-limit-mark-excluded-as-read}). If given a prefix,
3935 also mark excluded ticked and dormant articles as read.
3943 @cindex article threading
3945 Gnus threads articles by default. @dfn{To thread} is to put replies to
3946 articles directly after the articles they reply to---in a hierarchical
3950 * Customizing Threading:: Variables you can change to affect the threading.
3951 * Thread Commands:: Thread based commands in the summary buffer.
3955 @node Customizing Threading
3956 @subsection Customizing Threading
3957 @cindex customizing threading
3963 @item gnus-show-threads
3964 @vindex gnus-show-threads
3965 If this variable is @code{nil}, no threading will be done, and all of
3966 the rest of the variables here will have no effect. Turning threading
3967 off will speed group selection up a bit, but it is sure to make reading
3968 slower and more awkward.
3970 @item gnus-fetch-old-headers
3971 @vindex gnus-fetch-old-headers
3972 If non-@code{nil}, Gnus will attempt to build old threads by fetching
3973 more old headers---headers to articles that are marked as read. If you
3974 would like to display as few summary lines as possible, but still
3975 connect as many loose threads as possible, you should set this variable
3976 to @code{some} or a number. If you set it to a number, no more than
3977 that number of extra old headers will be fetched. In either case,
3978 fetching old headers only works if the backend you are using carries
3979 overview files---this would normally be @code{nntp}, @code{nnspool} and
3980 @code{nnml}. Also remember that if the root of the thread has been
3981 expired by the server, there's not much Gnus can do about that.
3983 @item gnus-build-sparse-threads
3984 @vindex gnus-build-sparse-threads
3985 Fetching old headers can be slow. A low-rent similar effect can be
3986 gotten by setting this variable to @code{some}. Gnus will then look at
3987 the complete @code{References} headers of all articles and try to string
3988 articles that belong in the same thread together. This will leave
3989 @dfn{gaps} in the threading display where Gnus guesses that an article
3990 is missing from the thread. (These gaps appear like normal summary
3991 lines. If you select a gap, Gnus will try to fetch the article in
3992 question.) If this variable is @code{t}, Gnus will display all these
3993 ``gaps'' without regard for whether they are useful for completing the
3994 thread or not. Finally, if this variable is @code{more}, Gnus won't cut
3995 off sparse leaf nodes that don't lead anywhere. This variable is
3996 @code{nil} by default.
3998 @item gnus-summary-gather-subject-limit
3999 @vindex gnus-summary-gather-subject-limit
4000 Loose threads are gathered by comparing subjects of articles. If this
4001 variable is @code{nil}, Gnus requires an exact match between the
4002 subjects of the loose threads before gathering them into one big
4003 super-thread. This might be too strict a requirement, what with the
4004 presence of stupid newsreaders that chop off long subjects lines. If
4005 you think so, set this variable to, say, 20 to require that only the
4006 first 20 characters of the subjects have to match. If you set this
4007 variable to a really low number, you'll find that Gnus will gather
4008 everything in sight into one thread, which isn't very helpful.
4010 @cindex fuzzy article gathering
4011 If you set this variable to the special value @code{fuzzy}, Gnus will
4012 use a fuzzy string comparison algorithm on the subjects.
4014 @item gnus-simplify-subject-fuzzy-regexp
4015 @vindex gnus-simplify-subject-fuzzy-regexp
4016 This can either be a regular expression or list of regular expressions
4017 that match strings that will be removed from subjects if fuzzy subject
4018 simplification is used.
4020 @item gnus-simplify-ignored-prefixes
4021 @vindex gnus-simplify-ignored-prefixes
4022 If you set @code{gnus-summary-gather-subject-limit} to something as low
4023 as 10, you might consider setting this variable to something sensible:
4025 @c Written by Michael Ernst <mernst@cs.rice.edu>
4027 (setq gnus-simplify-ignored-prefixes
4030 (mapconcat 'identity
4032 "wanted" "followup" "summary\\( of\\)?"
4033 "help" "query" "problem" "question"
4034 "answer" "reference" "announce"
4035 "How can I" "How to" "Comparison of"
4040 (mapconcat 'identity
4041 '("for" "for reference" "with" "about")
4043 "\\)?\\]?:?[ \t]*"))
4046 All words that match this regexp will be removed before comparing two
4049 @item gnus-summary-gather-exclude-subject
4050 @vindex gnus-summary-gather-exclude-subject
4051 Since loose thread gathering is done on subjects only, that might lead
4052 to many false hits, especially with certain common subjects like
4053 @samp{} and @samp{(none)}. To make the situation slightly better,
4054 you can use the regexp @code{gnus-summary-gather-exclude-subject} to say
4055 what subjects should be excluded from the gathering process. The
4056 default is @samp{^ *$\\|^(none)$}.
4058 @item gnus-summary-thread-gathering-function
4059 @vindex gnus-summary-thread-gathering-function
4060 Gnus gathers threads by looking at @code{Subject} headers. This means
4061 that totally unrelated articles may end up in the same ``thread'', which
4062 is confusing. An alternate approach is to look at all the
4063 @code{Message-ID}s in all the @code{References} headers to find matches.
4064 This will ensure that no gathered threads ever includes unrelated
4065 articles, but it's also means that people who have posted with broken
4066 newsreaders won't be gathered properly. The choice is yours---plague or
4070 @item gnus-gather-threads-by-subject
4071 @findex gnus-gather-threads-by-subject
4072 This function is the default gathering function and looks at
4073 @code{Subject}s exclusively.
4075 @item gnus-gather-threads-by-references
4076 @findex gnus-gather-threads-by-references
4077 This function looks at @code{References} headers exclusively.
4080 If you want to test gathering by @code{References}, you could say
4084 (setq gnus-summary-thread-gathering-function
4085 'gnus-gather-threads-by-references)
4088 @item gnus-summary-make-false-root
4089 @vindex gnus-summary-make-false-root
4090 If non-@code{nil}, Gnus will gather all loose subtrees into one big tree
4091 and create a dummy root at the top. (Wait a minute. Root at the top?
4092 Yup.) Loose subtrees occur when the real root has expired, or you've
4093 read or killed the root in a previous session.
4095 When there is no real root of a thread, Gnus will have to fudge
4096 something. This variable says what fudging method Gnus should use.
4097 There are four possible values:
4099 @cindex adopting articles
4104 Gnus will make the first of the orphaned articles the parent. This
4105 parent will adopt all the other articles. The adopted articles will be
4106 marked as such by pointy brackets (@samp{<>}) instead of the standard
4107 square brackets (@samp{[]}). This is the default method.
4110 @vindex gnus-summary-dummy-line-format
4111 Gnus will create a dummy summary line that will pretend to be the
4112 parent. This dummy line does not correspond to any real article, so
4113 selecting it will just select the first real article after the dummy
4114 article. @code{gnus-summary-dummy-line-format} is used to specify the
4115 format of the dummy roots. It accepts only one format spec: @samp{S},
4116 which is the subject of the article. @xref{Formatting Variables}.
4119 Gnus won't actually make any article the parent, but simply leave the
4120 subject field of all orphans except the first empty. (Actually, it will
4121 use @code{gnus-summary-same-subject} as the subject (@pxref{Summary
4125 Don't make any article parent at all. Just gather the threads and
4126 display them after one another.
4129 Don't gather loose threads.
4132 @item gnus-thread-hide-subtree
4133 @vindex gnus-thread-hide-subtree
4134 If non-@code{nil}, all threads will be hidden when the summary buffer is
4137 @item gnus-thread-hide-killed
4138 @vindex gnus-thread-hide-killed
4139 if you kill a thread and this variable is non-@code{nil}, the subtree
4142 @item gnus-thread-ignore-subject
4143 @vindex gnus-thread-ignore-subject
4144 Sometimes somebody changes the subject in the middle of a thread. If
4145 this variable is non-@code{nil}, the subject change is ignored. If it
4146 is @code{nil}, which is the default, a change in the subject will result
4149 @item gnus-thread-indent-level
4150 @vindex gnus-thread-indent-level
4151 This is a number that says how much each sub-thread should be indented.
4152 The default is @code{4}.
4156 @node Thread Commands
4157 @subsection Thread Commands
4158 @cindex thread commands
4164 @kindex T k (Summary)
4165 @kindex M-C-k (Summary)
4166 @findex gnus-summary-kill-thread
4167 Mark all articles in the current sub-thread as read
4168 (@code{gnus-summary-kill-thread}). If the prefix argument is positive,
4169 remove all marks instead. If the prefix argument is negative, tick
4174 @kindex T l (Summary)
4175 @kindex M-C-l (Summary)
4176 @findex gnus-summary-lower-thread
4177 Lower the score of the current thread
4178 (@code{gnus-summary-lower-thread}).
4181 @kindex T i (Summary)
4182 @findex gnus-summary-raise-thread
4183 Increase the score of the current thread
4184 (@code{gnus-summary-raise-thread}).
4187 @kindex T # (Summary)
4188 @findex gnus-uu-mark-thread
4189 Set the process mark on the current thread
4190 (@code{gnus-uu-mark-thread}).
4193 @kindex T M-# (Summary)
4194 @findex gnus-uu-unmark-thread
4195 Remove the process mark from the current thread
4196 (@code{gnus-uu-unmark-thread}).
4199 @kindex T T (Summary)
4200 @findex gnus-summary-toggle-threads
4201 Toggle threading (@code{gnus-summary-toggle-threads}).
4204 @kindex T s (Summary)
4205 @findex gnus-summary-show-thread
4206 Expose the thread hidden under the current article, if any
4207 (@code{gnus-summary-show-thread}).
4210 @kindex T h (Summary)
4211 @findex gnus-summary-hide-thread
4212 Hide the current (sub)thread (@code{gnus-summary-hide-thread}).
4215 @kindex T S (Summary)
4216 @findex gnus-summary-show-all-threads
4217 Expose all hidden threads (@code{gnus-summary-show-all-threads}).
4220 @kindex T H (Summary)
4221 @findex gnus-summary-hide-all-threads
4222 Hide all threads (@code{gnus-summary-hide-all-threads}).
4225 @kindex T t (Summary)
4226 @findex gnus-summary-rethread-current
4227 Re-thread the thread the current article is part of
4228 (@code{gnus-summary-rethread-current}). This works even when the
4229 summary buffer is otherwise unthreaded.
4232 @kindex T ^ (Summary)
4233 @findex gnus-summary-reparent-thread
4234 Make the current article the child of the marked (or previous) article
4235 (@code{gnus-summary-reparent-thread}.
4239 The following commands are thread movement commands. They all
4240 understand the numeric prefix.
4245 @kindex T n (Summary)
4246 @findex gnus-summary-next-thread
4247 Go to the next thread (@code{gnus-summary-next-thread}).
4250 @kindex T p (Summary)
4251 @findex gnus-summary-prev-thread
4252 Go to the previous thread (@code{gnus-summary-prev-thread}).
4255 @kindex T d (Summary)
4256 @findex gnus-summary-down-thread
4257 Descend the thread (@code{gnus-summary-down-thread}).
4260 @kindex T u (Summary)
4261 @findex gnus-summary-up-thread
4262 Ascend the thread (@code{gnus-summary-up-thread}).
4265 @kindex T o (Summary)
4266 @findex gnus-summary-top-thread
4267 Go to the top of the thread (@code{gnus-summary-top-thread}).
4270 @vindex gnus-thread-operation-ignore-subject
4271 If you ignore subject while threading, you'll naturally end up with
4272 threads that have several different subjects in them. If you then issue
4273 a command like `T k' (@code{gnus-summary-kill-thread}) you might not
4274 wish to kill the entire thread, but just those parts of the thread that
4275 have the same subject as the current article. If you like this idea,
4276 you can fiddle with @code{gnus-thread-operation-ignore-subject}. If is
4277 is non-@code{nil} (which it is by default), subjects will be ignored
4278 when doing thread commands. If this variable is @code{nil}, articles in
4279 the same thread with different subjects will not be included in the
4280 operation in question. If this variable is @code{fuzzy}, only articles
4281 that have subjects that are fuzzily equal will be included.
4287 @findex gnus-thread-sort-by-total-score
4288 @findex gnus-thread-sort-by-date
4289 @findex gnus-thread-sort-by-score
4290 @findex gnus-thread-sort-by-subject
4291 @findex gnus-thread-sort-by-author
4292 @findex gnus-thread-sort-by-number
4293 @vindex gnus-thread-sort-functions
4294 If you are using a threaded summary display, you can sort the threads by
4295 setting @code{gnus-thread-sort-functions}, which is a list of functions.
4296 By default, sorting is done on article numbers. Ready-made sorting
4297 predicate functions include @code{gnus-thread-sort-by-number},
4298 @code{gnus-thread-sort-by-author}, @code{gnus-thread-sort-by-subject},
4299 @code{gnus-thread-sort-by-date}, @code{gnus-thread-sort-by-score}, and
4300 @code{gnus-thread-sort-by-total-score}.
4302 Each function takes two threads and return non-@code{nil} if the first
4303 thread should be sorted before the other. Note that sorting really is
4304 normally done by looking only at the roots of each thread. If you use
4305 more than one function, the primary sort key should be the last function
4306 in the list. You should probably always include
4307 @code{gnus-thread-sort-by-number} in the list of sorting
4308 functions---preferably first. This will ensure that threads that are
4309 equal with respect to the other sort criteria will be displayed in
4310 ascending article order.
4312 If you would like to sort by score, then by subject, and finally by
4313 number, you could do something like:
4316 (setq gnus-thread-sort-functions
4317 '(gnus-thread-sort-by-number
4318 gnus-thread-sort-by-subject
4319 gnus-thread-sort-by-score))
4322 The threads that have highest score will be displayed first in the
4323 summary buffer. When threads have the same score, they will be sorted
4324 alphabetically. The threads that have the same score and the same
4325 subject will be sorted by number, which is (normally) the sequence in
4326 which the articles arrived.
4328 If you want to sort by score and then reverse arrival order, you could
4332 (setq gnus-thread-sort-functions
4334 (not (gnus-thread-sort-by-number t1 t2)))
4335 gnus-thread-sort-by-score))
4338 @vindex gnus-thread-score-function
4339 The function in the @code{gnus-thread-score-function} variable (default
4340 @code{+}) is used for calculating the total score of a thread. Useful
4341 functions might be @code{max}, @code{min}, or squared means, or whatever
4344 @findex gnus-article-sort-functions
4345 @findex gnus-article-sort-by-date
4346 @findex gnus-article-sort-by-score
4347 @findex gnus-article-sort-by-subject
4348 @findex gnus-article-sort-by-author
4349 @findex gnus-article-sort-by-number
4350 If you are using an unthreaded display for some strange reason or other,
4351 you have to fiddle with the @code{gnus-article-sort-functions} variable.
4352 It is very similar to the @code{gnus-thread-sort-functions}, except that
4353 is uses slightly different functions for article comparison. Available
4354 sorting predicate functions are @code{gnus-article-sort-by-number},
4355 @code{gnus-article-sort-by-author}, @code{gnus-article-sort-by-subject},
4356 @code{gnus-article-sort-by-date}, and @code{gnus-article-sort-by-score}.
4358 If you want to sort an unthreaded summary display by subject, you could
4362 (setq gnus-article-sort-functions
4363 '(gnus-article-sort-by-number
4364 gnus-article-sort-by-subject))
4369 @node Asynchronous Fetching
4370 @section Asynchronous Article Fetching
4371 @cindex asynchronous article fetching
4373 If you read your news from an @sc{nntp} server that's far away, the
4374 network latencies may make reading articles a chore. You have to wait
4375 for a while after pressing @kbd{n} to go to the next article before the
4376 article appears. Why can't Gnus just go ahead and fetch the article
4377 while you are reading the previous one? Why not, indeed.
4379 First, some caveats. There are some pitfalls to using asynchronous
4380 article fetching, especially the way Gnus does it.
4382 Let's say you are reading article 1, which is short, and article 2 is
4383 quite long, and you are not interested in reading that. Gnus does not
4384 know this, so it goes ahead and fetches article 2. You decide to read
4385 article 3, but since Gnus is in the process of fetching article 2, the
4386 connection is blocked.
4388 To avoid these situations, Gnus will open two (count 'em two)
4389 connections to the server. Some people may think this isn't a very nice
4390 thing to do, but I don't see any real alternatives. Setting up that
4391 extra connection takes some time, so Gnus startup will be slower.
4393 Gnus will fetch more articles than you will read. This will mean that
4394 the link between your machine and the @sc{nntp} server will become more
4395 loaded than if you didn't use article pre-fetch. The server itself will
4396 also become more loaded---both with the extra article requests, and the
4399 Ok, so now you know that you shouldn't really use this thing... unless
4402 @vindex gnus-asynchronous
4403 Here's how: Set @code{gnus-asynchronous} to @code{t}. The rest should
4404 happen automatically.
4406 @vindex gnus-use-article-prefetch
4407 You can control how many articles that are to be pre-fetched by setting
4408 @code{gnus-use-article-prefetch}. This is 30 by default, which means
4409 that when you read an article in the group, the backend will pre-fetch
4410 the next 30 articles. If this variable is @code{t}, the backend will
4411 pre-fetch all the articles that it can without bound. If it is
4412 @code{nil}, no pre-fetching will be made.
4414 @vindex gnus-prefetched-article-deletion-strategy
4415 Articles have to be removed from the asynch buffer sooner or later. The
4416 @code{gnus-prefetched-article-deletion-strategy} says when to remove
4417 articles. This is a list that may contain the following elements:
4421 Remove articles when they are read.
4424 Remove articles when exiting the group.
4427 The default value is @code{(read exit)}.
4429 @vindex gnus-use-header-prefetch
4430 If @code{gnus-use-header-prefetch} is non-@code{nil}, prefetch articles
4431 from the next group.
4434 @node Article Caching
4435 @section Article Caching
4436 @cindex article caching
4439 If you have an @emph{extremely} slow @sc{nntp} connection, you may
4440 consider turning article caching on. Each article will then be stored
4441 locally under your home directory. As you may surmise, this could
4442 potentially use @emph{huge} amounts of disk space, as well as eat up all
4443 your inodes so fast it will make your head swim. In vodka.
4445 Used carefully, though, it could be just an easier way to save articles.
4447 @vindex gnus-use-long-file-name
4448 @vindex gnus-cache-directory
4449 @vindex gnus-use-cache
4450 To turn caching on, set @code{gnus-use-cache} to @code{t}. By default,
4451 all articles that are ticked or marked as dormant will then be copied
4452 over to your local cache (@code{gnus-cache-directory}). Whether this
4453 cache is flat or hierarchal is controlled by the
4454 @code{gnus-use-long-file-name} variable, as usual.
4456 When re-select a ticked or dormant article, it will be fetched from the
4457 cache instead of from the server. As articles in your cache will never
4458 expire, this might serve as a method of saving articles while still
4459 keeping them where they belong. Just mark all articles you want to save
4460 as dormant, and don't worry.
4462 When an article is marked as read, is it removed from the cache.
4464 @vindex gnus-cache-remove-articles
4465 @vindex gnus-cache-enter-articles
4466 The entering/removal of articles from the cache is controlled by the
4467 @code{gnus-cache-enter-articles} and @code{gnus-cache-remove-articles}
4468 variables. Both are lists of symbols. The first is @code{(ticked
4469 dormant)} by default, meaning that ticked and dormant articles will be
4470 put in the cache. The latter is @code{(read)} by default, meaning that
4471 articles that are marked as read are removed from the cache. Possibly
4472 symbols in these two lists are @code{ticked}, @code{dormant},
4473 @code{unread} and @code{read}.
4475 @findex gnus-jog-cache
4476 So where does the massive article-fetching and storing come into the
4477 picture? The @code{gnus-jog-cache} command will go through all
4478 subscribed newsgroups, request all unread articles, and store them in
4479 the cache. You should only ever, ever ever ever, use this command if 1)
4480 your connection to the @sc{nntp} server is really, really, really slow
4481 and 2) you have a really, really, really huge disk. Seriously.
4483 @vindex gnus-uncacheable-groups
4484 It is likely that you do not want caching on some groups. For instance,
4485 if your @code{nnml} mail is located under your home directory, it makes no
4486 sense to cache it somewhere else under your home directory. Unless you
4487 feel that it's neat to use twice as much space. To limit the caching,
4488 you could set the @code{gnus-uncacheable-groups} regexp to
4489 @samp{^nnml}, for instance. This variable is @code{nil} by
4492 @findex gnus-cache-generate-nov-databases
4493 @findex gnus-cache-generate-active
4494 @vindex gnus-cache-active-file
4495 The cache stores information on what articles it contains in its active
4496 file (@code{gnus-cache-active-file}). If this file (or any other parts
4497 of the cache) becomes all messed up for some reason or other, Gnus
4498 offers two functions that will try to set things right. @kbd{M-x
4499 gnus-cache-generate-nov-databases} will (re)build all the @sc{nov}
4500 files, and @kbd{gnus-cache-generate-active} will (re)generate the active
4504 @node Persistent Articles
4505 @section Persistent Articles
4506 @cindex persistent articles
4508 Closely related to article caching, we have @dfn{persistent articles}.
4509 In fact, it's just a different way of looking at caching, and much more
4510 useful in my opinion.
4512 Say you're reading a newsgroup, and you happen on to some valuable gem
4513 that you want to keep and treasure forever. You'd normally just save it
4514 (using one of the many saving commands) in some file. The problem with
4515 that is that it's just, well, yucky. Ideally you'd prefer just having
4516 the article remain in the group where you found it forever; untouched by
4517 the expiry going on at the news server.
4519 This is what a @dfn{persistent article} is---an article that just won't
4520 be deleted. It's implemented using the normal cache functions, but
4521 you use two explicit commands for managing persistent articles:
4527 @findex gnus-cache-enter-article
4528 Make the current article persistent (@code{gnus-cache-enter-article}).
4531 @kindex M-* (Summary)
4532 @findex gnus-cache-remove-article
4533 Remove the current article from the persistent articles
4534 (@code{gnus-cache-remove-article}). This will normally delete the
4538 Both these commands understand the process/prefix convention.
4540 To avoid having all ticked articles (and stuff) entered into the cache,
4541 you should set @code{gnus-use-cache} to @code{passive} if you're just
4542 interested in persistent articles:
4545 (setq gnus-use-cache 'passive)
4549 @node Article Backlog
4550 @section Article Backlog
4552 @cindex article backlog
4554 If you have a slow connection, but the idea of using caching seems
4555 unappealing to you (and it is, really), you can help the situation some
4556 by switching on the @dfn{backlog}. This is where Gnus will buffer
4557 already read articles so that it doesn't have to re-fetch articles
4558 you've already read. This only helps if you are in the habit of
4559 re-selecting articles you've recently read, of course. If you never do
4560 that, turning the backlog on will slow Gnus down a little bit, and
4561 increase memory usage some.
4563 @vindex gnus-keep-backlog
4564 If you set @code{gnus-keep-backlog} to a number @var{n}, Gnus will store
4565 at most @var{n} old articles in a buffer for later re-fetching. If this
4566 variable is non-@code{nil} and is not a number, Gnus will store
4567 @emph{all} read articles, which means that your Emacs will grow without
4568 bound before exploding and taking your machine down with you. I put
4569 that in there just to keep y'all on your toes.
4571 This variable is @code{nil} by default.
4574 @node Saving Articles
4575 @section Saving Articles
4576 @cindex saving articles
4578 Gnus can save articles in a number of ways. Below is the documentation
4579 for saving articles in a fairly straight-forward fashion (i.e., little
4580 processing of the article is done before it is saved). For a different
4581 approach (uudecoding, unsharing) you should use @code{gnus-uu}
4582 (@pxref{Decoding Articles}).
4584 @vindex gnus-save-all-headers
4585 If @code{gnus-save-all-headers} is non-@code{nil}, Gnus will not delete
4586 unwanted headers before saving the article.
4588 @vindex gnus-saved-headers
4589 If the preceding variable is @code{nil}, all headers that match the
4590 @code{gnus-saved-headers} regexp will be kept, while the rest will be
4591 deleted before saving.
4597 @kindex O o (Summary)
4599 @findex gnus-summary-save-article
4600 Save the current article using the default article saver
4601 (@code{gnus-summary-save-article}).
4604 @kindex O m (Summary)
4605 @findex gnus-summary-save-article-mail
4606 Save the current article in mail format
4607 (@code{gnus-summary-save-article-mail}).
4610 @kindex O r (Summary)
4611 @findex gnus-summary-save-article-rmail
4612 Save the current article in rmail format
4613 (@code{gnus-summary-save-article-rmail}).
4616 @kindex O f (Summary)
4617 @findex gnus-summary-save-article-file
4618 Save the current article in plain file format
4619 (@code{gnus-summary-save-article-file}).
4622 @kindex O b (Summary)
4623 @findex gnus-summary-save-article-body-file
4624 Save the current article body in plain file format
4625 (@code{gnus-summary-save-article-body-file}).
4628 @kindex O h (Summary)
4629 @findex gnus-summary-save-article-folder
4630 Save the current article in mh folder format
4631 (@code{gnus-summary-save-article-folder}).
4634 @kindex O v (Summary)
4635 @findex gnus-summary-save-article-vm
4636 Save the current article in a VM folder
4637 (@code{gnus-summary-save-article-vm}).
4640 @kindex O p (Summary)
4641 @findex gnus-summary-pipe-output
4642 Save the current article in a pipe. Uhm, like, what I mean is---Pipe
4643 the current article to a process (@code{gnus-summary-pipe-output}).
4646 @vindex gnus-prompt-before-saving
4647 All these commands use the process/prefix convention
4648 (@pxref{Process/Prefix}). If you save bunches of articles using these
4649 functions, you might get tired of being prompted for files to save each
4650 and every article in. The prompting action is controlled by
4651 the @code{gnus-prompt-before-saving} variable, which is @code{always} by
4652 default, giving you that excessive prompting action you know and
4653 loathe. If you set this variable to @code{t} instead, you'll be prompted
4654 just once for each series of articles you save. If you like to really
4655 have Gnus do all your thinking for you, you can even set this variable
4656 to @code{nil}, which means that you will never be prompted for files to
4657 save articles in. Gnus will simply save all the articles in the default
4661 @vindex gnus-default-article-saver
4662 You can customize the @code{gnus-default-article-saver} variable to make
4663 Gnus do what you want it to. You can use any of the four ready-made
4664 functions below, or you can create your own.
4668 @item gnus-summary-save-in-rmail
4669 @findex gnus-summary-save-in-rmail
4670 @vindex gnus-rmail-save-name
4671 @findex gnus-plain-save-name
4672 This is the default format, @dfn{babyl}. Uses the function in the
4673 @code{gnus-rmail-save-name} variable to get a file name to save the
4674 article in. The default is @code{gnus-plain-save-name}.
4676 @item gnus-summary-save-in-mail
4677 @findex gnus-summary-save-in-mail
4678 @vindex gnus-mail-save-name
4679 Save in a Unix mail (mbox) file. Uses the function in the
4680 @code{gnus-mail-save-name} variable to get a file name to save the
4681 article in. The default is @code{gnus-plain-save-name}.
4683 @item gnus-summary-save-in-file
4684 @findex gnus-summary-save-in-file
4685 @vindex gnus-file-save-name
4686 @findex gnus-numeric-save-name
4687 Append the article straight to an ordinary file. Uses the function in
4688 the @code{gnus-file-save-name} variable to get a file name to save the
4689 article in. The default is @code{gnus-numeric-save-name}.
4691 @item gnus-summary-save-body-in-file
4692 @findex gnus-summary-save-body-in-file
4693 Append the article body to an ordinary file. Uses the function in the
4694 @code{gnus-file-save-name} variable to get a file name to save the
4695 article in. The default is @code{gnus-numeric-save-name}.
4697 @item gnus-summary-save-in-folder
4698 @findex gnus-summary-save-in-folder
4699 @findex gnus-folder-save-name
4700 @findex gnus-Folder-save-name
4701 @vindex gnus-folder-save-name
4704 Save the article to an MH folder using @code{rcvstore} from the MH
4705 library. Uses the function in the @code{gnus-folder-save-name} variable
4706 to get a file name to save the article in. The default is
4707 @code{gnus-folder-save-name}, but you can also use
4708 @code{gnus-Folder-save-name}. The former creates capitalized names, and
4709 the latter does not.
4711 @item gnus-summary-save-in-vm
4712 @findex gnus-summary-save-in-vm
4713 Save the article in a VM folder. You have to have the VM mail
4714 reader to use this setting.
4717 @vindex gnus-article-save-directory
4718 All of these functions, except for the last one, will save the article
4719 in the @code{gnus-article-save-directory}, which is initialized from the
4720 @code{SAVEDIR} environment variable. This is @file{~/News/} by
4723 As you can see above, the functions use different functions to find a
4724 suitable name of a file to save the article in. Below is a list of
4725 available functions that generate names:
4729 @item gnus-Numeric-save-name
4730 @findex gnus-Numeric-save-name
4731 Generates file names that look like @file{~/News/Alt.andrea-dworkin/45}.
4733 @item gnus-numeric-save-name
4734 @findex gnus-numeric-save-name
4735 Generates file names that look like @file{~/News/alt.andrea-dworkin/45}.
4737 @item gnus-Plain-save-name
4738 @findex gnus-Plain-save-name
4739 Generates file names that look like @file{~/News/Alt.andrea-dworkin}.
4741 @item gnus-plain-save-name
4742 @findex gnus-plain-save-name
4743 Generates file names that look like @file{~/News/alt.andrea-dworkin}.
4746 @vindex gnus-split-methods
4747 You can have Gnus suggest where to save articles by plonking a regexp into
4748 the @code{gnus-split-methods} alist. For instance, if you would like to
4749 save articles related to Gnus in the file @file{gnus-stuff}, and articles
4750 related to VM in @code{vm-stuff}, you could set this variable to something
4754 (("^Subject:.*gnus\\|^Newsgroups:.*gnus" "gnus-stuff")
4755 ("^Subject:.*vm\\|^Xref:.*vm" "vm-stuff")
4756 (my-choosing-function "../other-dir/my-stuff")
4757 ((equal gnus-newsgroup-name "mail.misc") "mail-stuff"))
4760 We see that this is a list where each element is a list that has two
4761 elements---the @dfn{match} and the @dfn{file}. The match can either be
4762 a string (in which case it is used as a regexp to match on the article
4763 head); it can be a symbol (which will be called as a function with the
4764 group name as a parameter); or it can be a list (which will be
4765 @code{eval}ed). If any of these actions have a non-@code{nil} result,
4766 the @dfn{file} will be used as a default prompt. In addition, the
4767 result of the operation itself will be used if the function or form
4768 called returns a string or a list of strings.
4770 You basically end up with a list of file names that might be used when
4771 saving the current article. (All ``matches'' will be used.) You will
4772 then be prompted for what you really want to use as a name, with file
4773 name completion over the results from applying this variable.
4775 This variable is @code{((gnus-article-archive-name))} by default, which
4776 means that Gnus will look at the articles it saves for an
4777 @code{Archive-name} line and use that as a suggestion for the file
4780 @vindex gnus-use-long-file-name
4781 Finally, you have the @code{gnus-use-long-file-name} variable. If it is
4782 @code{nil}, all the preceding functions will replace all periods
4783 (@samp{.}) in the group names with slashes (@samp{/})---which means that
4784 the functions will generate hierarchies of directories instead of having
4785 all the files in the toplevel directory
4786 (@file{~/News/alt/andrea-dworkin} instead of
4787 @file{~/News/alt.andrea-dworkin}.) This variable is @code{t} by default
4788 on most systems. However, for historical reasons, this is @code{nil} on
4789 Xenix and usg-unix-v machines by default.
4791 This function also affects kill and score file names. If this variable
4792 is a list, and the list contains the element @code{not-score}, long file
4793 names will not be used for score files, if it contains the element
4794 @code{not-save}, long file names will not be used for saving, and if it
4795 contains the element @code{not-kill}, long file names will not be used
4798 If you'd like to save articles in a hierarchy that looks something like
4802 (setq gnus-use-long-file-name '(not-save)) ; to get a hierarchy
4803 (setq gnus-default-article-save 'gnus-summary-save-in-file) ; no encoding
4806 Then just save with @kbd{o}. You'd then read this hierarchy with
4807 ephemeral @code{nneething} groups---@kbd{G D} in the group buffer, and
4808 the toplevel directory as the argument (@file{~/News/}). Then just walk
4809 around to the groups/directories with @code{nneething}.
4812 @node Decoding Articles
4813 @section Decoding Articles
4814 @cindex decoding articles
4816 Sometime users post articles (or series of articles) that have been
4817 encoded in some way or other. Gnus can decode them for you.
4820 * Uuencoded Articles:: Uudecode articles.
4821 * Shared Articles:: Unshar articles.
4822 * PostScript Files:: Split PostScript.
4823 * Decoding Variables:: Variables for a happy decoding.
4824 * Viewing Files:: You want to look at the result of the decoding?
4827 All these functions use the process/prefix convention
4828 (@pxref{Process/Prefix}) for finding out what articles to work on, with
4829 the extension that a ``single article'' means ``a single series''. Gnus
4830 can find out by itself what articles belong to a series, decode all the
4831 articles and unpack/view/save the resulting file(s).
4833 Gnus guesses what articles are in the series according to the following
4834 simplish rule: The subjects must be (nearly) identical, except for the
4835 last two numbers of the line. (Spaces are largely ignored, however.)
4837 For example: If you choose a subject called @samp{cat.gif (2/3)}, Gnus
4838 will find all the articles that match the regexp @samp{^cat.gif
4839 ([0-9]+/[0-9]+).*$}.
4841 Subjects that are nonstandard, like @samp{cat.gif (2/3) Part 6 of a
4842 series}, will not be properly recognized by any of the automatic viewing
4843 commands, and you have to mark the articles manually with @kbd{#}.
4846 @node Uuencoded Articles
4847 @subsection Uuencoded Articles
4849 @cindex uuencoded articles
4854 @kindex X u (Summary)
4855 @findex gnus-uu-decode-uu
4856 Uudecodes the current series (@code{gnus-uu-decode-uu}).
4859 @kindex X U (Summary)
4860 @findex gnus-uu-decode-uu-and-save
4861 Uudecodes and saves the current series
4862 (@code{gnus-uu-decode-uu-and-save}).
4865 @kindex X v u (Summary)
4866 @findex gnus-uu-decode-uu-view
4867 Uudecodes and views the current series (@code{gnus-uu-decode-uu-view}).
4870 @kindex X v U (Summary)
4871 @findex gnus-uu-decode-uu-and-save-view
4872 Uudecodes, views and saves the current series
4873 (@code{gnus-uu-decode-uu-and-save-view}).
4876 Remember that these all react to the presence of articles marked with
4877 the process mark. If, for instance, you'd like to decode and save an
4878 entire newsgroup, you'd typically do @kbd{M P a}
4879 (@code{gnus-uu-mark-all}) and then @kbd{X U}
4880 (@code{gnus-uu-decode-uu-and-save}).
4882 All this is very much different from how @code{gnus-uu} worked with
4883 @sc{gnus 4.1}, where you had explicit keystrokes for everything under
4884 the sun. This version of @code{gnus-uu} generally assumes that you mark
4885 articles in some way (@pxref{Setting Process Marks}) and then press
4888 @vindex gnus-uu-notify-files
4889 Note: When trying to decode articles that have names matching
4890 @code{gnus-uu-notify-files}, which is hard-coded to
4891 @samp{[Cc][Ii][Nn][Dd][Yy][0-9]+.\\(gif\\|jpg\\)}, @code{gnus-uu} will
4892 automatically post an article on @samp{comp.unix.wizards} saying that
4893 you have just viewed the file in question. This feature can't be turned
4897 @node Shared Articles
4898 @subsection Shared Articles
4900 @cindex shared articles
4905 @kindex X s (Summary)
4906 @findex gnus-uu-decode-unshar
4907 Unshars the current series (@code{gnus-uu-decode-unshar}).
4910 @kindex X S (Summary)
4911 @findex gnus-uu-decode-unshar-and-save
4912 Unshars and saves the current series (@code{gnus-uu-decode-unshar-and-save}).
4915 @kindex X v s (Summary)
4916 @findex gnus-uu-decode-unshar-view
4917 Unshars and views the current series (@code{gnus-uu-decode-unshar-view}).
4920 @kindex X v S (Summary)
4921 @findex gnus-uu-decode-unshar-and-save-view
4922 Unshars, views and saves the current series
4923 (@code{gnus-uu-decode-unshar-and-save-view}).
4927 @node PostScript Files
4928 @subsection PostScript Files
4934 @kindex X p (Summary)
4935 @findex gnus-uu-decode-postscript
4936 Unpack the current PostScript series (@code{gnus-uu-decode-postscript}).
4939 @kindex X P (Summary)
4940 @findex gnus-uu-decode-postscript-and-save
4941 Unpack and save the current PostScript series
4942 (@code{gnus-uu-decode-postscript-and-save}).
4945 @kindex X v p (Summary)
4946 @findex gnus-uu-decode-postscript-view
4947 View the current PostScript series
4948 (@code{gnus-uu-decode-postscript-view}).
4951 @kindex X v P (Summary)
4952 @findex gnus-uu-decode-postscript-and-save-view
4953 View and save the current PostScript series
4954 (@code{gnus-uu-decode-postscript-and-save-view}).
4958 @node Decoding Variables
4959 @subsection Decoding Variables
4961 Adjective, not verb.
4964 * Rule Variables:: Variables that say how a file is to be viewed.
4965 * Other Decode Variables:: Other decode variables.
4966 * Uuencoding and Posting:: Variables for customizing uuencoding.
4970 @node Rule Variables
4971 @subsubsection Rule Variables
4972 @cindex rule variables
4974 Gnus uses @dfn{rule variables} to decide how to view a file. All these
4975 variables are on the form
4978 (list '(regexp1 command2)
4985 @item gnus-uu-user-view-rules
4986 @vindex gnus-uu-user-view-rules
4988 This variable is consulted first when viewing files. If you wish to use,
4989 for instance, @code{sox} to convert an @samp{.au} sound file, you could
4992 (setq gnus-uu-user-view-rules
4993 (list '(\"\\\\.au$\" \"sox %s -t .aiff > /dev/audio\")))
4996 @item gnus-uu-user-view-rules-end
4997 @vindex gnus-uu-user-view-rules-end
4998 This variable is consulted if Gnus couldn't make any matches from the
4999 user and default view rules.
5001 @item gnus-uu-user-archive-rules
5002 @vindex gnus-uu-user-archive-rules
5003 This variable can be used to say what commands should be used to unpack
5008 @node Other Decode Variables
5009 @subsubsection Other Decode Variables
5012 @vindex gnus-uu-grabbed-file-functions
5014 @item gnus-uu-grabbed-file-functions
5015 All functions in this list will be called right each file has been
5016 successfully decoded---so that you can move or view files right away,
5017 and don't have to wait for all files to be decoded before you can do
5018 anything. Ready-made functions you can put in this list are:
5022 @item gnus-uu-grab-view
5023 @findex gnus-uu-grab-view
5026 @item gnus-uu-grab-move
5027 @findex gnus-uu-grab-move
5028 Move the file (if you're using a saving function.)
5031 @item gnus-uu-ignore-files-by-name
5032 @vindex gnus-uu-ignore-files-by-name
5033 Files with name matching this regular expression won't be viewed.
5035 @item gnus-uu-ignore-files-by-type
5036 @vindex gnus-uu-ignore-files-by-type
5037 Files with a @sc{mime} type matching this variable won't be viewed.
5038 Note that Gnus tries to guess what type the file is based on the name.
5039 @code{gnus-uu} is not a @sc{mime} package (yet), so this is slightly
5042 @item gnus-uu-tmp-dir
5043 @vindex gnus-uu-tmp-dir
5044 Where @code{gnus-uu} does its work.
5046 @item gnus-uu-do-not-unpack-archives
5047 @vindex gnus-uu-do-not-unpack-archives
5048 Non-@code{nil} means that @code{gnus-uu} won't peek inside archives
5049 looking for files to display.
5051 @item gnus-uu-view-and-save
5052 @vindex gnus-uu-view-and-save
5053 Non-@code{nil} means that the user will always be asked to save a file
5056 @item gnus-uu-ignore-default-view-rules
5057 @vindex gnus-uu-ignore-default-view-rules
5058 Non-@code{nil} means that @code{gnus-uu} will ignore the default viewing
5061 @item gnus-uu-ignore-default-archive-rules
5062 @vindex gnus-uu-ignore-default-archive-rules
5063 Non-@code{nil} means that @code{gnus-uu} will ignore the default archive
5066 @item gnus-uu-kill-carriage-return
5067 @vindex gnus-uu-kill-carriage-return
5068 Non-@code{nil} means that @code{gnus-uu} will strip all carriage returns
5071 @item gnus-uu-unmark-articles-not-decoded
5072 @vindex gnus-uu-unmark-articles-not-decoded
5073 Non-@code{nil} means that @code{gnus-uu} will mark articles that were
5074 unsuccessfully decoded as unread.
5076 @item gnus-uu-correct-stripped-uucode
5077 @vindex gnus-uu-correct-stripped-uucode
5078 Non-@code{nil} means that @code{gnus-uu} will @emph{try} to fix
5079 uuencoded files that have had trailing spaces deleted.
5081 @item gnus-uu-view-with-metamail
5082 @vindex gnus-uu-view-with-metamail
5084 Non-@code{nil} means that @code{gnus-uu} will ignore the viewing
5085 commands defined by the rule variables and just fudge a @sc{mime}
5086 content type based on the file name. The result will be fed to
5087 @code{metamail} for viewing.
5089 @item gnus-uu-save-in-digest
5090 @vindex gnus-uu-save-in-digest
5091 Non-@code{nil} means that @code{gnus-uu}, when asked to save without
5092 decoding, will save in digests. If this variable is @code{nil},
5093 @code{gnus-uu} will just save everything in a file without any
5094 embellishments. The digesting almost conforms to RFC1153---no easy way
5095 to specify any meaningful volume and issue numbers were found, so I
5096 simply dropped them.
5101 @node Uuencoding and Posting
5102 @subsubsection Uuencoding and Posting
5106 @item gnus-uu-post-include-before-composing
5107 @vindex gnus-uu-post-include-before-composing
5108 Non-@code{nil} means that @code{gnus-uu} will ask for a file to encode
5109 before you compose the article. If this variable is @code{t}, you can
5110 either include an encoded file with @kbd{C-c C-i} or have one included
5111 for you when you post the article.
5113 @item gnus-uu-post-length
5114 @vindex gnus-uu-post-length
5115 Maximum length of an article. The encoded file will be split into how
5116 many articles it takes to post the entire file.
5118 @item gnus-uu-post-threaded
5119 @vindex gnus-uu-post-threaded
5120 Non-@code{nil} means that @code{gnus-uu} will post the encoded file in a
5121 thread. This may not be smart, as no other decoder I have seen are able
5122 to follow threads when collecting uuencoded articles. (Well, I have
5123 seen one package that does that---@code{gnus-uu}, but somehow, I don't
5124 think that counts...) Default is @code{nil}.
5126 @item gnus-uu-post-separate-description
5127 @vindex gnus-uu-post-separate-description
5128 Non-@code{nil} means that the description will be posted in a separate
5129 article. The first article will typically be numbered (0/x). If this
5130 variable is @code{nil}, the description the user enters will be included
5131 at the beginning of the first article, which will be numbered (1/x).
5132 Default is @code{t}.
5138 @subsection Viewing Files
5139 @cindex viewing files
5140 @cindex pseudo-articles
5142 After decoding, if the file is some sort of archive, Gnus will attempt
5143 to unpack the archive and see if any of the files in the archive can be
5144 viewed. For instance, if you have a gzipped tar file @file{pics.tar.gz}
5145 containing the files @file{pic1.jpg} and @file{pic2.gif}, Gnus will
5146 uncompress and de-tar the main file, and then view the two pictures.
5147 This unpacking process is recursive, so if the archive contains archives
5148 of archives, it'll all be unpacked.
5150 Finally, Gnus will normally insert a @dfn{pseudo-article} for each
5151 extracted file into the summary buffer. If you go to these
5152 ``articles'', you will be prompted for a command to run (usually Gnus
5153 will make a suggestion), and then the command will be run.
5155 @vindex gnus-view-pseudo-asynchronously
5156 If @code{gnus-view-pseudo-asynchronously} is @code{nil}, Emacs will wait
5157 until the viewing is done before proceeding.
5159 @vindex gnus-view-pseudos
5160 If @code{gnus-view-pseudos} is @code{automatic}, Gnus will not insert
5161 the pseudo-articles into the summary buffer, but view them
5162 immediately. If this variable is @code{not-confirm}, the user won't even
5163 be asked for a confirmation before viewing is done.
5165 @vindex gnus-view-pseudos-separately
5166 If @code{gnus-view-pseudos-separately} is non-@code{nil}, one
5167 pseudo-article will be created for each file to be viewed. If
5168 @code{nil}, all files that use the same viewing command will be given as
5169 a list of parameters to that command.
5171 @vindex gnus-insert-pseudo-articles
5172 If @code{gnus-insert-pseudo-articles} is non-@code{nil}, insert
5173 pseudo-articles when decoding. It is @code{t} by default.
5175 So; there you are, reading your @emph{pseudo-articles} in your
5176 @emph{virtual newsgroup} from the @emph{virtual server}; and you think:
5177 Why isn't anything real anymore? How did we get here?
5180 @node Article Treatment
5181 @section Article Treatment
5183 Reading through this huge manual, you may have quite forgotten that the
5184 object of newsreaders are to actually, like, read what people have
5185 written. Reading articles. Unfortunately, people are quite bad at
5186 writing, so there are tons of functions and variables to make reading
5187 these articles easier.
5190 * Article Highlighting:: You want to make the article look like fruit salad.
5191 * Article Hiding:: You also want to make certain info go away.
5192 * Article Washing:: Lots of way-neat functions to make life better.
5193 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
5194 * Article Date:: Grumble, UT!
5195 * Article Signature:: What is a signature?
5199 @node Article Highlighting
5200 @subsection Article Highlighting
5203 Not only do you want your article buffer to look like fruit salad, but
5204 you want it to look like technicolor fruit salad.
5209 @kindex W H a (Summary)
5210 @findex gnus-article-highlight
5211 Highlight the current article (@code{gnus-article-highlight}).
5214 @kindex W H h (Summary)
5215 @findex gnus-article-highlight-headers
5216 @vindex gnus-header-face-alist
5217 Highlight the headers (@code{gnus-article-highlight-headers}). The
5218 highlighting will be done according to the @code{gnus-header-face-alist}
5219 variable, which is a list where each element has the form @var{(regexp
5220 name content)}. @var{regexp} is a regular expression for matching the
5221 header, @var{name} is the face used for highlighting the header name and
5222 @var{content} is the face for highlighting the header value. The first
5223 match made will be used. Note that @var{regexp} shouldn't have @samp{^}
5224 prepended---Gnus will add one.
5227 @kindex W H c (Summary)
5228 @findex gnus-article-highlight-citation
5229 Highlight cited text (@code{gnus-article-highlight-citation}).
5231 Some variables to customize the citation highlights:
5234 @vindex gnus-cite-parse-max-size
5236 @item gnus-cite-parse-max-size
5237 If the article size if bigger than this variable (which is 25000 by
5238 default), no citation highlighting will be performed.
5240 @item gnus-cite-prefix-regexp
5241 @vindex gnus-cite-prefix-regexp
5242 Regexp matching the longest possible citation prefix on a line.
5244 @item gnus-cite-max-prefix
5245 @vindex gnus-cite-max-prefix
5246 Maximum possible length for a citation prefix (default 20).
5248 @item gnus-cite-face-list
5249 @vindex gnus-cite-face-list
5250 List of faces used for highlighting citations. When there are citations
5251 from multiple articles in the same message, Gnus will try to give each
5252 citation from each article its own face. This should make it easier to
5255 @item gnus-supercite-regexp
5256 @vindex gnus-supercite-regexp
5257 Regexp matching normal Supercite attribution lines.
5259 @item gnus-supercite-secondary-regexp
5260 @vindex gnus-supercite-secondary-regexp
5261 Regexp matching mangled Supercite attribution lines.
5263 @item gnus-cite-minimum-match-count
5264 @vindex gnus-cite-minimum-match-count
5265 Minimum number of identical prefixes we have to see before we believe
5266 that it's a citation.
5268 @item gnus-cite-attribution-prefix
5269 @vindex gnus-cite-attribution-prefix
5270 Regexp matching the beginning of an attribution line.
5272 @item gnus-cite-attribution-suffix
5273 @vindex gnus-cite-attribution-suffix
5274 Regexp matching the end of an attribution line.
5276 @item gnus-cite-attribution-face
5277 @vindex gnus-cite-attribution-face
5278 Face used for attribution lines. It is merged with the face for the
5279 cited text belonging to the attribution.
5285 @kindex W H s (Summary)
5286 @vindex gnus-signature-separator
5287 @vindex gnus-signature-face
5288 @findex gnus-article-highlight-signature
5289 Highlight the signature (@code{gnus-article-highlight-signature}).
5290 Everything after @code{gnus-signature-separator} (@pxref{Article
5291 Signature}) in an article will be considered a signature and will be
5292 highlighted with @code{gnus-signature-face}, which is @code{italic} by
5298 @node Article Hiding
5299 @subsection Article Hiding
5300 @cindex article hiding
5302 Or rather, hiding certain things in each article. There usually is much
5303 too much cruft in most articles.
5308 @kindex W W a (Summary)
5309 @findex gnus-article-hide
5310 Do maximum hiding on the summary buffer (@kbd{gnus-article-hide}).
5313 @kindex W W h (Summary)
5314 @findex gnus-article-hide-headers
5315 Hide headers (@code{gnus-article-hide-headers}). @xref{Hiding
5319 @kindex W W b (Summary)
5320 @findex gnus-article-hide-boring-headers
5321 Hide headers that aren't particularly interesting
5322 (@code{gnus-article-hide-boring-headers}). @xref{Hiding Headers}.
5325 @kindex W W s (Summary)
5326 @findex gnus-article-hide-signature
5327 Hide signature (@code{gnus-article-hide-signature}). @xref{Article
5331 @kindex W W p (Summary)
5332 @findex gnus-article-hide-pgp
5333 Hide @sc{pgp} signatures (@code{gnus-article-hide-pgp}).
5336 @kindex W W P (Summary)
5337 @findex gnus-article-hide-pem
5338 Hide @sc{pem} (privacy enhavnced hessages) gruft
5339 (@code{gnus-article-hide-pem}).
5342 @kindex W W c (Summary)
5343 @findex gnus-article-hide-citation
5344 Hide citation (@code{gnus-article-hide-citation}). Some variables for
5345 customizing the hiding:
5349 @item gnus-cite-hide-percentage
5350 @vindex gnus-cite-hide-percentage
5351 If the cited text is of a bigger percentage than this variable (default
5352 50), hide the cited text.
5354 @item gnus-cite-hide-absolute
5355 @vindex gnus-cite-hide-absolute
5356 The cited text must be have at least this length (default 10) before it
5359 @item gnus-cited-text-button-line-format
5360 @vindex gnus-cited-text-button-line-format
5361 Gnus adds buttons show where the cited text has been hidden, and to
5362 allow toggle hiding the text. The format of the variable is specified
5363 by this format-like variable (@pxref{Formatting Variables}). These
5368 Start point of the hidden text.
5370 End point of the hidden text.
5372 Length of the hidden text.
5375 @item gnus-cited-lines-visible
5376 @vindex gnus-cited-lines-visible
5377 The number of lines at the beginning of the cited text to leave shown.
5382 @kindex W W C (Summary)
5383 @findex gnus-article-hide-citation-in-followups
5384 Hide cited text in articles that aren't roots
5385 (@code{gnus-article-hide-citation-in-followups}). This isn't very
5386 useful as an interactive command, but might be a handy function to stick
5387 in @code{gnus-article-display-hook} (@pxref{Customizing Articles}).
5391 All these ``hiding'' commands are toggles, but if you give a negative
5392 prefix to these commands, they will show what they have previously
5393 hidden. If you give a positive prefix, they will always hide.
5395 Also @pxref{Article Highlighting} for further variables for
5396 citation customization.
5399 @node Article Washing
5400 @subsection Article Washing
5402 @cindex article washing
5404 We call this ``article washing'' for a really good reason. Namely, the
5405 @kbd{A} key was taken, so we had to use the @kbd{W} key instead.
5407 @dfn{Washing} is defined by us as ``changing something from something to
5408 something else'', but normally results in something looking better.
5414 @kindex W l (Summary)
5415 @findex gnus-summary-stop-page-breaking
5416 Remove page breaks from the current article
5417 (@code{gnus-summary-stop-page-breaking}).
5420 @kindex W r (Summary)
5421 @findex gnus-summary-caesar-message
5422 Do a Caesar rotate (rot13) on the article buffer
5423 (@code{gnus-summary-caesar-message}).
5426 @kindex W t (Summary)
5427 @findex gnus-summary-toggle-header
5428 Toggle whether to display all headers in the article buffer
5429 (@code{gnus-summary-toggle-header}).
5432 @kindex W v (Summary)
5433 @findex gnus-summary-verbose-header
5434 Toggle whether to display all headers in the article buffer permanently
5435 (@code{gnus-summary-verbose-header}).
5438 @kindex W m (Summary)
5439 @findex gnus-summary-toggle-mime
5440 Toggle whether to run the article through @sc{mime} before displaying
5441 (@code{gnus-summary-toggle-mime}).
5444 @kindex W o (Summary)
5445 @findex gnus-article-treat-overstrike
5446 Treat overstrike (@code{gnus-article-treat-overstrike}).
5449 @kindex W w (Summary)
5450 @findex gnus-article-fill-cited-article
5451 Do word wrap (@code{gnus-article-fill-cited-article}). If you use this
5452 function in @code{gnus-article-display-hook}, it should be run fairly
5453 late and certainly after any highlighting.
5456 @kindex W c (Summary)
5457 @findex gnus-article-remove-cr
5458 Remove CR (@code{gnus-article-remove-cr}).
5461 @kindex W q (Summary)
5462 @findex gnus-article-de-quoted-unreadable
5463 Treat quoted-printable (@code{gnus-article-de-quoted-unreadable}).
5466 @kindex W f (Summary)
5468 @findex gnus-article-display-x-face
5469 @findex gnus-article-x-face-command
5470 @vindex gnus-article-x-face-command
5471 @vindex gnus-article-x-face-too-ugly
5472 Look for and display any X-Face headers
5473 (@code{gnus-article-display-x-face}). The command executed by this
5474 function is given by the @code{gnus-article-x-face-command} variable.
5475 If this variable is a string, this string will be executed in a
5476 sub-shell. If it is a function, this function will be called with the
5477 face as the argument. If the @code{gnus-article-x-face-too-ugly} (which
5478 is a regexp) matches the @code{From} header, the face will not be shown.
5479 The default action under Emacs is to fork off an @code{xv} to view the
5480 face; under XEmacs the default action is to display the face before the
5481 @code{From} header. (It's nicer if XEmacs has been compiled with X-Face
5482 support---that will make display somewhat faster. If there's no native
5483 X-Face support, Gnus will try to convert the @code{X-Face} header using
5484 external programs from the @code{pbmplus} package and friends.) If you
5485 want to have this function in the display hook, it should probably come
5489 @kindex W b (Summary)
5490 @findex gnus-article-add-buttons
5491 Add clickable buttons to the article (@code{gnus-article-add-buttons}).
5494 @kindex W B (Summary)
5495 @findex gnus-article-add-buttons-to-head
5496 Add clickable buttons to the article headers
5497 (@code{gnus-article-add-buttons-to-head}).
5500 @kindex W E l (Summary)
5501 @findex gnus-article-strip-leading-blank-lines
5502 Remove all blank lines from the beginning of the article
5503 (@code{gnus-article-strip-leading-blank-lines}).
5506 @kindex W E m (Summary)
5507 @findex gnus-article-strip-multiple-blank-lines
5508 Replace all blank lines with empty lines and then all multiple empty
5509 lines with a single empty line.
5510 (@code{gnus-article-strip-multiple-blank-lines}).
5513 @kindex W E t (Summary)
5514 @findex gnus-article-remove-trailing-blank-lines
5515 Remove all blank lines at the end of the article
5516 (@code{gnus-article-remove-trailing-blank-lines}).
5519 @kindex W E a (Summary)
5520 @findex gnus-article-strip-blank-lines
5521 Do all the three commands above
5522 (@code{gnus-article-strip-blank-lines}).
5527 @node Article Buttons
5528 @subsection Article Buttons
5531 People often include references to other stuff in articles, and it would
5532 be nice if Gnus could just fetch whatever it is that people talk about
5533 with the minimum of fuzz.
5535 Gnus adds @dfn{buttons} to certain standard references by default:
5536 Well-formed URLs, mail addresses and Message-IDs. This is controlled by
5537 two variables, one that handles article bodies and one that handles
5542 @item gnus-button-alist
5543 @vindex gnus-button-alist
5544 This is an alist where each entry has this form:
5547 (REGEXP BUTTON-PAR USE-P FUNCTION DATA-PAR)
5553 All text that match this regular expression will be considered an
5554 external reference. Here's a typical regexp that match embedded URLs:
5555 @samp{<URL:\\([^\n\r>]*\\)>}.
5558 Gnus has to know which parts of the match is to be highlighted. This is
5559 a number that says what sub-expression of the regexp that is to be
5560 highlighted. If you want it all highlighted, you use @code{0} here.
5563 This form will be @code{eval}ed, and if the result is non-@code{nil},
5564 this is considered a match. This is useful if you want extra sifting to
5565 avoid false matches.
5568 This function will be called when you click on this button.
5571 As with @var{button-par}, this is a sub-expression number, but this one
5572 says which part of the match is to be sent as data to @var{function}.
5576 So the full entry for buttonizing URLs is then
5579 ("<URL:\\([^\n\r>]*\\)>" 0 t gnus-button-url 1)
5582 @item gnus-header-button-alist
5583 @vindex gnus-header-button-alist
5584 This is just like the other alist, except that it is applied to the
5585 article head only, and that each entry has an additional element that is
5586 used to say what headers to apply the buttonize coding to:
5589 (HEADER REGEXP BUTTON-PAR USE-P FUNCTION DATA-PAR)
5592 @var{header} is a regular expression.
5594 @item gnus-button-url-regexp
5595 @vindex gnus-button-url-regexp
5596 A regular expression that matches embedded URLs. It is used in the
5597 default values of the variables above.
5599 @item gnus-article-button-face
5600 @vindex gnus-article-button-face
5601 Face used on bottons.
5603 @item gnus-article-mouse-face
5604 @vindex gnus-article-mouse-face
5605 Face is used when the mouse cursor is over a button.
5611 @subsection Article Date
5613 The date is most likely generated in some obscure timezone you've never
5614 heard of, so it's quite nice to be able to find out what the time was
5615 when the article was sent.
5620 @kindex W T u (Summary)
5621 @findex gnus-article-date-ut
5622 Display the date in UT (aka. GMT, aka ZULU)
5623 (@code{gnus-article-date-ut}).
5626 @kindex W T l (Summary)
5627 @findex gnus-article-date-local
5628 Display the date in the local timezone (@code{gnus-article-date-local}).
5631 @kindex W T e (Summary)
5632 @findex gnus-article-date-lapsed
5633 Say how much time has (e)lapsed between the article was posted and now
5634 (@code{gnus-article-date-lapsed}).
5637 @kindex W T o (Summary)
5638 @findex gnus-article-date-original
5639 Display the original date (@code{gnus-article-date-original}). This can
5640 be useful if you normally use some other conversion function and is
5641 worried that it might be doing something totally wrong. Say, claiming
5642 that the article was posted in 1854. Although something like that is
5643 @emph{totally} impossible. Don't you trust me? *titter*
5648 @node Article Signature
5649 @subsection Article Signature
5651 @cindex article signature
5653 @vindex gnus-signature-separator
5654 Each article is divided into two parts---the head and the body. The
5655 body can be divided into a signature part and a text part. The variable
5656 that says what is to be considered a signature is
5657 @code{gnus-signature-separator}. This is normally the standard
5658 @samp{"^-- $"} as mandated by son-of-RFC 1036. However, many people use
5659 non-standard signature separators, so this variable can also be a list
5660 of regular expressions to be tested, one by one. (Searches are done
5661 from the end of the body towards the beginning.) One likely value is:
5664 (setq gnus-signature-separator
5665 '("^-- $" ; The standard
5666 "^-- *$" ; A common mangling
5667 "^-------*$" ; Many people just use a looong
5668 ; line of dashes. Shame!
5669 "^ *--------*$" ; Double-shame!
5670 "^________*$" ; Underscores are also popular
5671 "^========*$")) ; Pervert!
5674 The more permissive you are, the more likely it is that you'll get false
5677 @vindex gnus-signature-limit
5678 @code{gnus-signature-limit} provides a limit to what is considered a
5683 If it is an integer, no signature may be longer (in characters) than
5686 If it is a floating point number, no signature may be longer (in lines)
5689 If it is a function, the function will be called without any parameters,
5690 and if it returns @code{nil}, there is no signature in the buffer.
5692 If it is a string, it will be used as a regexp. If it matches, the text
5693 in question is not a signature.
5696 This variable can also be a list where the elements may be of the types
5700 @node Summary Sorting
5701 @section Summary Sorting
5702 @cindex summary sorting
5704 You can have the summary buffer sorted in various ways, even though I
5705 can't really see why you'd want that.
5710 @kindex C-c C-s C-n (Summary)
5711 @findex gnus-summary-sort-by-number
5712 Sort by article number (@code{gnus-summary-sort-by-number}).
5715 @kindex C-c C-s C-a (Summary)
5716 @findex gnus-summary-sort-by-author
5717 Sort by author (@code{gnus-summary-sort-by-author}).
5720 @kindex C-c C-s C-s (Summary)
5721 @findex gnus-summary-sort-by-subject
5722 Sort by subject (@code{gnus-summary-sort-by-subject}).
5725 @kindex C-c C-s C-d (Summary)
5726 @findex gnus-summary-sort-by-date
5727 Sort by date (@code{gnus-summary-sort-by-date}).
5730 @kindex C-c C-s C-i (Summary)
5731 @findex gnus-summary-sort-by-score
5732 Sort by score (@code{gnus-summary-sort-by-score}).
5735 These functions will work both when you use threading and when you don't
5736 use threading. In the latter case, all summary lines will be sorted,
5737 line by line. In the former case, sorting will be done on a
5738 root-by-root basis, which might not be what you were looking for. To
5739 toggle whether to use threading, type @kbd{T T} (@pxref{Thread
5743 @node Finding the Parent
5744 @section Finding the Parent
5745 @cindex parent articles
5746 @cindex referring articles
5748 @findex gnus-summary-refer-parent-article
5750 If you'd like to read the parent of the current article, and it is not
5751 displayed in the summary buffer, you might still be able to. That is,
5752 if the current group is fetched by @sc{nntp}, the parent hasn't expired
5753 and the @code{References} in the current article are not mangled, you
5754 can just press @kbd{^} or @kbd{A r}
5755 (@code{gnus-summary-refer-parent-article}). If everything goes well,
5756 you'll get the parent. If the parent is already displayed in the
5757 summary buffer, point will just move to this article.
5759 If given a positive numerical prefix, fetch that many articles back into
5760 the ancestry. If given a negative numerical prefix, fetch just that
5761 ancestor. So if you say @kbd{3 ^}, Gnus will fetch the parent, the
5762 grandparent and the grandgrandparent of the current article. If you say
5763 @kbd{-3 ^}, Gnus will only fetch the grandgrandparent of the current
5766 @findex gnus-summary-refer-references
5767 @kindex A R (Summary)
5768 You can have Gnus fetch all articles mentioned in the @code{References}
5769 header of the article by pushing @kbd{A R}
5770 (@code{gnus-summary-refer-references}).
5772 @findex gnus-summary-refer-article
5773 @kindex M-^ (Summary)
5774 You can also ask the @sc{nntp} server for an arbitrary article, no
5775 matter what group it belongs to. @kbd{M-^}
5776 (@code{gnus-summary-refer-article}) will ask you for a
5777 @code{Message-ID}, which is one of those long thingies that look
5778 something like @samp{<38o6up$6f2@@hymir.ifi.uio.no>}. You have to get
5779 it all exactly right. No fuzzy searches, I'm afraid.
5781 @vindex gnus-refer-article-method
5782 If the group you are reading is located on a backend that does not
5783 support fetching by @code{Message-ID} very well (like @code{nnspool}),
5784 you can set @code{gnus-refer-article-method} to an @sc{nntp} method. It
5785 would, perhaps, be best if the @sc{nntp} server you consult is the same
5786 as the one that keeps the spool you are reading from updated, but that's
5787 not really necessary.
5789 Most of the mail backends support fetching by @code{Message-ID}, but do
5790 not do a particularly excellent job of it. That is, @code{nnmbox} and
5791 @code{nnbabyl} are able to locate articles from any groups, while
5792 @code{nnml} and @code{nnfolder} are only able to locate articles that
5793 have been posted to the current group. (Anything else would be too time
5794 consuming.) @code{nnmh} does not support this at all.
5797 @node Alternative Approaches
5798 @section Alternative Approaches
5800 Different people like to read news using different methods. This being
5801 Gnus, we offer a small selection of minor modes for the summary buffers.
5804 * Pick and Read:: First mark articles and then read them.
5805 * Binary Groups:: Auto-decode all articles.
5810 @subsection Pick and Read
5811 @cindex pick and read
5813 Some newsreaders (like @code{nn} and, uhm, @code{nn}) use a two-phased
5814 reading interface. The user first marks the articles she wants to read
5815 from a summary buffer. Then she starts reading the articles with just
5816 an article buffer displayed.
5818 @findex gnus-pick-mode
5819 @kindex M-x gnus-pick-mode
5820 Gnus provides a summary buffer minor mode that allows
5821 this---@code{gnus-pick-mode}. This basically means that a few process
5822 mark commands become one-keystroke commands to allow easy marking, and
5823 it makes one additional command for switching to the summary buffer
5826 Here are the available keystrokes when using pick mode:
5831 @findex gnus-summary-mark-as-processable
5832 Pick the article on the current line
5833 (@code{gnus-summary-mark-as-processable}). If given a numerical prefix,
5834 go to the article on that line and pick that article. (The line number
5835 is normally displayed on the beginning of the summary pick lines.)
5838 @kindex SPACE (Pick)
5839 @findex gnus-pick-next-page
5840 Scroll the summary buffer up one page (@code{gnus-pick-next-page}). If
5841 at the end of the buffer, start reading the picked articles.
5845 @findex gnus-summary-unmark-as-processable
5846 Unpick the article (@code{gnus-summary-unmark-as-processable}).
5850 @findex gnus-summary-unmark-all-processable
5851 Unpick all articles (@code{gnus-summary-unmark-all-processable}).
5855 @findex gnus-uu-mark-thread
5856 Pick the thread (@code{gnus-uu-mark-thread}).
5860 @findex gnus-uu-unmark-thread
5861 Unpick the thread (@code{gnus-uu-unmark-thread}).
5865 @findex gnus-uu-mark-region
5866 Pick the region (@code{gnus-uu-mark-region}).
5870 @findex gnus-uu-unmark-region
5871 Unpick the region (@code{gnus-uu-unmark-region}).
5875 @findex gnus-uu-mark-by-regexp
5876 Pick articles that match a regexp (@code{gnus-uu-mark-by-regexp}).
5880 @findex gnus-uu-unmark-by-regexp
5881 Unpick articles that match a regexp (@code{gnus-uu-unmark-by-regexp}).
5885 @findex gnus-uu-mark-buffer
5886 Pick the buffer (@code{gnus-uu-mark-buffer}).
5890 @findex gnus-uu-unmark-buffer
5891 Unpick the buffer (@code{gnus-uu-unmark-buffer}).
5895 @findex gnus-pick-start-reading
5896 @vindex gnus-pick-display-summary
5897 Start reading the picked articles (@code{gnus-pick-start-reading}). If
5898 given a prefix, mark all unpicked articles as read first. If
5899 @code{gnus-pick-display-summary} is non-@code{nil}, the summary buffer
5900 will still be visible when you are reading.
5904 If this sounds like a good idea to you, you could say:
5907 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
5910 @vindex gnus-pick-mode-hook
5911 @code{gnus-pick-mode-hook} is run in pick minor mode buffers.
5913 @vindex gnus-mark-unpicked-articles-as-read
5914 If @code{gnus-mark-unpicked-articles-as-read} is non-@code{nil}, mark
5915 all unpicked articles as read. The default is @code{nil}.
5917 @vindex gnus-summary-pick-line-format
5918 The summary line format in pick mode is slightly different than the
5919 standard format. At the beginning of each line the line number is
5920 displayed. The pick mode line format is controlled by the
5921 @code{gnus-summary-pick-line-format} variable (@pxref{Formatting
5922 Variables}). It accepts the same format specs that
5923 @code{gnus-summary-line-format} does (@pxref{Summary Buffer Lines}).
5927 @subsection Binary Groups
5928 @cindex binary groups
5930 @findex gnus-binary-mode
5931 @kindex M-x gnus-binary-mode
5932 If you spend much time in binary groups, you may grow tired of hitting
5933 @kbd{X u}, @kbd{n}, @kbd{RET} all the time. @kbd{M-x gnus-binary-mode}
5934 is a minor mode for summary buffers that makes all ordinary Gnus article
5935 selection functions uudecode series of articles and display the result
5936 instead of just displaying the articles the normal way.
5939 @findex gnus-binary-show-article
5940 In fact, the only way to see the actual articles if you have turned this
5941 mode on is the @kbd{g} command (@code{gnus-binary-show-article}).
5943 @vindex gnus-binary-mode-hook
5944 @code{gnus-binary-mode-hook} is called in binary minor mode buffers.
5948 @section Tree Display
5951 @vindex gnus-use-trees
5952 If you don't like the normal Gnus summary display, you might try setting
5953 @code{gnus-use-trees} to @code{t}. This will create (by default) an
5954 additional @dfn{tree buffer}. You can execute all summary mode commands
5957 There are a few variables to customize the tree display, of course:
5960 @item gnus-tree-mode-hook
5961 @vindex gnus-tree-mode-hook
5962 A hook called in all tree mode buffers.
5964 @item gnus-tree-mode-line-format
5965 @vindex gnus-tree-mode-line-format
5966 A format string for the mode bar in the tree mode buffers. The default
5967 is @samp{Gnus: %%b [%A] %Z}. For a list of legal specs, @pxref{Summary
5970 @item gnus-selected-tree-face
5971 @vindex gnus-selected-tree-face
5972 Face used for highlighting the selected article in the tree buffer. The
5973 default is @code{modeline}.
5975 @item gnus-tree-line-format
5976 @vindex gnus-tree-line-format
5977 A format string for the tree nodes. The name is a bit of a misnomer,
5978 though---it doesn't define a line, but just the node. The default value
5979 is @samp{%(%[%3,3n%]%)}, which displays the first three characters of
5980 the name of the poster. It is vital that all nodes are of the same
5981 length, so you @emph{must} use @samp{%4,4n}-like specifiers.
5987 The name of the poster.
5989 The @code{From} header.
5991 The number of the article.
5993 The opening bracket.
5995 The closing bracket.
6000 @xref{Formatting Variables}.
6002 Variables related to the display are:
6005 @item gnus-tree-brackets
6006 @vindex gnus-tree-brackets
6007 This is used for differentiating between ``real'' articles and
6008 ``sparse'' articles. The format is @var{((real-open . real-close)
6009 (sparse-open . sparse-close) (dummy-open . dummy-close))}, and the
6010 default is @code{((?[ . ?]) (?( . ?)) (?@{ . ?@}))}.
6012 @item gnus-tree-parent-child-edges
6013 @vindex gnus-tree-parent-child-edges
6014 This is a list that contains the characters used for connecting parent
6015 nodes to their children. The default is @code{(?- ?\\ ?|)}.
6019 @item gnus-tree-minimize-window
6020 @vindex gnus-tree-minimize-window
6021 If this variable is non-@code{nil}, Gnus will try to keep the tree
6022 buffer as small as possible to allow more room for the other Gnus
6023 windows. If this variable is a number, the tree buffer will never be
6024 higher than that number. The default is @code{t}.
6026 @item gnus-generate-tree-function
6027 @vindex gnus-generate-tree-function
6028 @findex gnus-generate-horizontal-tree
6029 @findex gnus-generate-vertical-tree
6030 The function that actually generates the thread tree. Two predefined
6031 functions are available: @code{gnus-generate-horizontal-tree} and
6032 @code{gnus-generate-vertical-tree} (which is the default).
6036 Here's and example from a horizontal tree buffer:
6039 @{***@}-(***)-[odd]-[Gun]
6049 Here's the same thread displayed in a vertical tree buffer:
6053 |--------------------------\-----\-----\
6054 (***) [Bjo] [Gun] [Gun]
6056 [odd] [Jan] [odd] (***) [Jor]
6058 [Gun] [Eri] [Eri] [odd]
6064 @node Mail Group Commands
6065 @section Mail Group Commands
6066 @cindex mail group commands
6068 Some commands only make sense in mail groups. If these commands are
6069 illegal in the current group, they will raise a hell and let you know.
6071 All these commands (except the expiry and edit commands) use the
6072 process/prefix convention (@pxref{Process/Prefix}).
6077 @kindex B e (Summary)
6078 @findex gnus-summary-expire-articles
6079 Expire all expirable articles in the group
6080 (@code{gnus-summary-expire-articles}).
6083 @kindex B M-C-e (Summary)
6084 @findex gnus-summary-expire-articles-now
6085 Expunge all the expirable articles in the group
6086 (@code{gnus-summary-expire-articles-now}). This means that @strong{all}
6087 articles that are eligible for expiry in the current group will
6088 disappear forever into that big @file{/dev/null} in the sky.
6091 @kindex B DEL (Summary)
6092 @findex gnus-summary-delete-article
6093 Delete the mail article. This is ``delete'' as in ``delete it from your
6094 disk forever and ever, never to return again.'' Use with caution.
6095 (@code{gnus-summary-delete-article}).
6098 @kindex B m (Summary)
6100 @findex gnus-summary-move-article
6101 Move the article from one mail group to another
6102 (@code{gnus-summary-move-article}).
6105 @kindex B c (Summary)
6107 @findex gnus-summary-copy-article
6108 Copy the article from one group (mail group or not) to a mail group
6109 (@code{gnus-summary-copy-article}).
6112 @kindex B C (Summary)
6113 @cindex crosspost mail
6114 @findex gnus-summary-crosspost-article
6115 Crosspost the current article to some other group
6116 (@code{gnus-summary-crosspost-article}). This will create a new copy of
6117 the article in the other group, and the Xref headers of the article will
6118 be properly updated.
6121 @kindex B i (Summary)
6122 @findex gnus-summary-import-article
6123 Import an arbitrary file into the current mail newsgroup
6124 (@code{gnus-summary-import-article}). You will be prompted for a file
6125 name, a @code{From} header and a @code{Subject} header.
6128 @kindex B r (Summary)
6129 @findex gnus-summary-respool-article
6130 Respool the mail article (@code{gnus-summary-move-article}).
6134 @kindex B w (Summary)
6136 @findex gnus-summary-edit-article
6137 @kindex C-c C-c (Article)
6138 Edit the current article (@code{gnus-summary-edit-article}). To finish
6139 editing and make the changes permanent, type @kbd{C-c C-c}
6140 (@kbd{gnus-summary-edit-article-done}).
6143 @kindex B q (Summary)
6144 @findex gnus-summary-respool-query
6145 If you want to re-spool an article, you might be curious as to what group
6146 the article will end up in before you do the re-spooling. This command
6147 will tell you (@code{gnus-summary-respool-query}).
6150 @kindex B p (Summary)
6151 @findex gnus-summary-article-posted-p
6152 Some people have a tendency to send you "courtesy" copies when they
6153 follow up to articles you have posted. These usually have a
6154 @code{Newsgroups} header in them, but not always. This command
6155 (@code{gnus-summary-article-posted-p}) will try to fetch the current
6156 article from your news server (or rather, from
6157 @code{gnus-refer-article-method} or @code{gnus-select-method}) and will
6158 report back whether it found the article or not. Even if it says that
6159 it didn't find the article, it may have been posted anyway---mail
6160 propagation is much faster than news propagation, and the news copy may
6161 just not have arrived yet.
6165 @vindex gnus-move-split-methods
6166 @cindex moving articles
6167 If you move (or copy) articles regularly, you might wish to have Gnus
6168 suggest where to put the articles. @code{gnus-move-split-methods} is a
6169 variable that uses the same syntax as @code{gnus-split-methods}
6170 (@pxref{Saving Articles}). You may customize that variable to create
6171 suggestions you find reasonable.
6174 @node Various Summary Stuff
6175 @section Various Summary Stuff
6178 * Summary Group Information:: Information oriented commands.
6179 * Searching for Articles:: Multiple article commands.
6180 * Really Various Summary Commands:: Those pesky non-conformant commands.
6184 @vindex gnus-summary-mode-hook
6185 @item gnus-summary-mode-hook
6186 This hook is called when creating a summary mode buffer.
6188 @vindex gnus-summary-generate-hook
6189 @item gnus-summary-generate-hook
6190 This is called as the last thing before doing the threading and the
6191 generation of the summary buffer. It's quite convenient for customizing
6192 the threading variables based on what data the newsgroup has. This hook
6193 is called from the summary buffer after most summary buffer variables
6196 @vindex gnus-summary-prepare-hook
6197 @item gnus-summary-prepare-hook
6198 Is is called after the summary buffer has been generated. You might use
6199 it to, for instance, highlight lines or modify the look of the buffer in
6200 some other ungodly manner. I don't care.
6205 @node Summary Group Information
6206 @subsection Summary Group Information
6211 @kindex H f (Summary)
6212 @findex gnus-summary-fetch-faq
6213 @vindex gnus-group-faq-directory
6214 Try to fetch the FAQ (list of frequently asked questions) for the
6215 current group (@code{gnus-summary-fetch-faq}). Gnus will try to get the
6216 FAQ from @code{gnus-group-faq-directory}, which is usually a directory
6217 on a remote machine. This variable can also be a list of directories.
6218 In that case, giving a prefix to this command will allow you to choose
6219 between the various sites. @code{ange-ftp} probably will be used for
6223 @kindex H d (Summary)
6224 @findex gnus-summary-describe-group
6225 Give a brief description of the current group
6226 (@code{gnus-summary-describe-group}). If given a prefix, force
6227 rereading the description from the server.
6230 @kindex H h (Summary)
6231 @findex gnus-summary-describe-briefly
6232 Give a very brief description of the most important summary keystrokes
6233 (@code{gnus-summary-describe-briefly}).
6236 @kindex H i (Summary)
6237 @findex gnus-info-find-node
6238 Go to the Gnus info node (@code{gnus-info-find-node}).
6242 @node Searching for Articles
6243 @subsection Searching for Articles
6248 @kindex M-s (Summary)
6249 @findex gnus-summary-search-article-forward
6250 Search through all subsequent articles for a regexp
6251 (@code{gnus-summary-search-article-forward}).
6254 @kindex M-r (Summary)
6255 @findex gnus-summary-search-article-backward
6256 Search through all previous articles for a regexp
6257 (@code{gnus-summary-search-article-backward}).
6261 @findex gnus-summary-execute-command
6262 This command will prompt you for a header field, a regular expression to
6263 match on this field, and a command to be executed if the match is made
6264 (@code{gnus-summary-execute-command}).
6267 @kindex M-& (Summary)
6268 @findex gnus-summary-universal-argument
6269 Perform any operation on all articles that have been marked with
6270 the process mark (@code{gnus-summary-universal-argument}).
6274 @node Really Various Summary Commands
6275 @subsection Really Various Summary Commands
6280 @kindex C-d (Summary)
6281 @findex gnus-summary-enter-digest-group
6282 If the current article is a collection of other articles (for instance,
6283 a digest), you might use this command to enter a group based on the that
6284 article (@code{gnus-summary-enter-digest-group}). Gnus will try to
6285 guess what article type is currently displayed unless you give a prefix
6286 to this command, which forces a ``digest'' interpretation. Basically,
6287 whenever you see a message that is a collection of other messages on
6288 some format, you @kbd{C-d} and read these messages in a more convenient
6292 @kindex M-C-d (Summary)
6293 @findex gnus-summary-read-document
6294 This command is very similar to the one above, but lets you gather
6295 several documents into one biiig group
6296 (@code{gnus-summary-read-document}). It does this by opening several
6297 @code{nndoc} groups for each document, and then opening an
6298 @code{nnvirtual} group on top of these @code{nndoc} groups. This
6299 command understands the process/prefix convention
6300 (@pxref{Process/Prefix}).
6303 @kindex C-t (Summary)
6304 @findex gnus-summary-toggle-truncation
6305 Toggle truncation of summary lines
6306 (@code{gnus-summary-toggle-truncation}). This will probably confuse the
6307 line centering function in the summary buffer, so it's not a good idea
6308 to have truncation switched off while reading articles.
6312 @findex gnus-summary-expand-window
6313 Expand the summary buffer window (@code{gnus-summary-expand-window}).
6314 If given a prefix, force an @code{article} window configuration.
6317 @kindex M-C-g (Summary)
6318 @findex gnus-summary-prepare
6319 Regenerate the current summary buffer (@code{gnus-summary-prepare}).
6324 @node Exiting the Summary Buffer
6325 @section Exiting the Summary Buffer
6326 @cindex summary exit
6327 @cindex exiting groups
6329 Exiting from the summary buffer will normally update all info on the
6330 group and return you to the group buffer.
6336 @kindex Z Z (Summary)
6338 @findex gnus-summary-exit
6339 @vindex gnus-summary-exit-hook
6340 @vindex gnus-summary-prepare-exit-hook
6341 Exit the current group and update all information on the group
6342 (@code{gnus-summary-exit}). @code{gnus-summary-prepare-exit-hook} is
6343 called before doing much of the exiting, and calls
6344 @code{gnus-summary-expire-articles} by default.
6345 @code{gnus-summary-exit-hook} is called after finishing the exiting
6350 @kindex Z E (Summary)
6352 @findex gnus-summary-exit-no-update
6353 Exit the current group without updating any information on the group
6354 (@code{gnus-summary-exit-no-update}).
6358 @kindex Z c (Summary)
6360 @findex gnus-summary-catchup-and-exit
6361 Mark all unticked articles in the group as read and then exit
6362 (@code{gnus-summary-catchup-and-exit}).
6365 @kindex Z C (Summary)
6366 @findex gnus-summary-catchup-all-and-exit
6367 Mark all articles, even the ticked ones, as read and then exit
6368 (@code{gnus-summary-catchup-all-and-exit}).
6371 @kindex Z n (Summary)
6372 @findex gnus-summary-catchup-and-goto-next-group
6373 Mark all articles as read and go to the next group
6374 (@code{gnus-summary-catchup-and-goto-next-group}).
6377 @kindex Z R (Summary)
6378 @findex gnus-summary-reselect-current-group
6379 Exit this group, and then enter it again
6380 (@code{gnus-summary-reselect-current-group}). If given a prefix, select
6381 all articles, both read and unread.
6385 @kindex Z G (Summary)
6386 @kindex M-g (Summary)
6387 @findex gnus-summary-rescan-group
6388 Exit the group, check for new articles in the group, and select the
6389 group (@code{gnus-summary-rescan-group}). If given a prefix, select all
6390 articles, both read and unread.
6393 @kindex Z N (Summary)
6394 @findex gnus-summary-next-group
6395 Exit the group and go to the next group
6396 (@code{gnus-summary-next-group}).
6399 @kindex Z P (Summary)
6400 @findex gnus-summary-prev-group
6401 Exit the group and go to the previous group
6402 (@code{gnus-summary-prev-group}).
6405 @vindex gnus-exit-group-hook
6406 @code{gnus-exit-group-hook} is called when you exit the current
6409 @findex gnus-summary-wake-up-the-dead
6410 @findex gnus-dead-summary-mode
6411 @vindex gnus-kill-summary-on-exit
6412 If you're in the habit of exiting groups, and then changing your mind
6413 about it, you might set @code{gnus-kill-summary-on-exit} to @code{nil}.
6414 If you do that, Gnus won't kill the summary buffer when you exit it.
6415 (Quelle surprise!) Instead it will change the name of the buffer to
6416 something like @samp{*Dead Summary ... *} and install a minor mode
6417 called @code{gnus-dead-summary-mode}. Now, if you switch back to this
6418 buffer, you'll find that all keys are mapped to a function called
6419 @code{gnus-summary-wake-up-the-dead}. So tapping any keys in a dead
6420 summary buffer will result in a live, normal summary buffer.
6422 There will never be more than one dead summary buffer at any one time.
6424 @vindex gnus-use-cross-reference
6425 The data on the current group will be updated (which articles you have
6426 read, which articles you have replied to, etc.) when you exit the
6427 summary buffer. If the @code{gnus-use-cross-reference} variable is
6428 @code{t} (which is the default), articles that are cross-referenced to
6429 this group and are marked as read, will also be marked as read in the
6430 other subscribed groups they were cross-posted to. If this variable is
6431 neither @code{nil} nor @code{t}, the article will be marked as read in
6432 both subscribed and unsubscribed groups (@pxref{Crosspost Handling}).
6435 @node Crosspost Handling
6436 @section Crosspost Handling
6440 Marking cross-posted articles as read ensures that you'll never have to
6441 read the same article more than once. Unless, of course, somebody has
6442 posted it to several groups separately. Posting the same article to
6443 several groups (not cross-posting) is called @dfn{spamming}, and you are
6444 by law required to send nasty-grams to anyone who perpetrates such a
6445 heinous crime. You may want to try NoCeM handling to filter out spam
6448 Remember: Cross-posting is kinda ok, but posting the same article
6449 separately to several groups is not. Massive cross-posting (aka.
6450 @dfn{velveeta}) is to be avoided at all costs, and you can even use the
6451 @code{gnus-summary-mail-crosspost-complaint} command to complain about
6452 excessive crossposting (@pxref{Summary Mail Commands}).
6454 @cindex cross-posting
6457 One thing that may cause Gnus to not do the cross-posting thing
6458 correctly is if you use an @sc{nntp} server that supports @sc{xover}
6459 (which is very nice, because it speeds things up considerably) which
6460 does not include the @code{Xref} header in its @sc{nov} lines. This is
6461 Evil, but all too common, alas, alack. Gnus tries to Do The Right Thing
6462 even with @sc{xover} by registering the @code{Xref} lines of all
6463 articles you actually read, but if you kill the articles, or just mark
6464 them as read without reading them, Gnus will not get a chance to snoop
6465 the @code{Xref} lines out of these articles, and will be unable to use
6466 the cross reference mechanism.
6468 @cindex LIST overview.fmt
6469 @cindex overview.fmt
6470 To check whether your @sc{nntp} server includes the @code{Xref} header
6471 in its overview files, try @samp{telnet your.nntp.server nntp},
6472 @samp{MODE READER} on @code{inn} servers, and then say @samp{LIST
6473 overview.fmt}. This may not work, but if it does, and the last line you
6474 get does not read @samp{Xref:full}, then you should shout and whine at
6475 your news admin until she includes the @code{Xref} header in the
6478 @vindex gnus-nov-is-evil
6479 If you want Gnus to get the @code{Xref}s right all the time, you have to
6480 set @code{gnus-nov-is-evil} to @code{t}, which slows things down
6485 For an alternative approach, @xref{Duplicate Suppression}.
6488 @node Duplicate Suppression
6489 @section Duplicate Suppression
6491 By default, Gnus tries to make sure that you don't have to read the same
6492 article more than once by utilizing the crossposing mechanism
6493 (@pxref{Crosspost Handling}). However, that simple and efficient
6494 approach may not work satisfactorily for some users for various
6499 The @sc{nntp} server may fail to generate the @code{Xref} header. This
6500 is evil and not very common.
6503 The @sc{nntp} server may fail to include the @code{Xref} header in the
6504 @file{.overview} data bases. This is evil and all too common, alas.
6507 You may be reading the same group (or several related groups) from
6508 different @sc{nntp} servers.
6511 You may be getting mail that duplicates articles posted to groups.
6514 I'm sure there are other situations that @code{Xref} handling fails as
6515 well, but these four are the most common situations.
6517 If, and only if, @code{Xref} handling fails for you, then you may
6518 consider switching on @dfn{duplicate suppression}. If you do so, Gnus
6519 will remember the @code{Message-ID}s of all articles you have read or
6520 otherwise marked as read, and then, as if by magic, mark them as read
6521 all subsequent times you see them---in @emph{all} groups. Using this
6522 mechanism is quite likely to be somewhat inefficient, but not overly
6523 so. It's certainly preferrable to reading the same articles more than
6526 Duplicate suppression is not a very subtle instrument. It's more like a
6527 sledge hammer than anything else. It works in a very simple
6528 fashion---if you have marked an article as read, it adds this Message-ID
6529 to a cache. The next time it sees this Message-ID, it will mark the
6530 article as read the the @samp{M} mark. It doesn't care what group it
6534 @item gnus-suppress-duplicates
6535 @vindex gnus-suppress-duplicates
6536 If non-@code{nil}, suppress duplicates.
6538 @item gnus-save-duplicate-list
6539 @vindex gnus-save-duplicate-list
6540 If non-@code{nil}, save the list of duplicates to a file. This will
6541 make startup and shutdown take longer, so the default is @code{nil}.
6542 However, this means that only duplicate articles that is read in a
6543 single Gnus session are suppressed.
6545 @item gnus-duplicate-list-length
6546 @vindex gnus-duplicate-list-length
6547 This variables says how many @code{Message-ID}s to keep in the duplicate
6548 suppression list. The default is 10000.
6550 @item gnus-duplicate-file
6551 @vindex gnus-duplicate-file
6552 The name of the file to store the duplicate suppression list. The
6553 default is @file{~/News/suppression}.
6556 If you have a tendency to stop and start Gnus often, setting
6557 @code{gnus-save-duplicate-list} to @code{t} is probably a good idea. If
6558 you leave Gnus running for weeks on end, you may have it @code{nil}. On
6559 the other hand, saving the list makes startup and shutdown much slower,
6560 so that means that if you stop and start Gnus often, you should set
6561 @code{gnus-save-duplicate-list} to @code{nil}. Uhm. I'll leave this up
6562 to you to figure out, I think.
6565 @node The Article Buffer
6566 @chapter The Article Buffer
6567 @cindex article buffer
6569 The articles are displayed in the article buffer, of which there is only
6570 one. All the summary buffers share the same article buffer unless you
6571 tell Gnus otherwise.
6574 * Hiding Headers:: Deciding what headers should be displayed.
6575 * Using MIME:: Pushing articles through @sc{mime} before reading them.
6576 * Customizing Articles:: Tailoring the look of the articles.
6577 * Article Keymap:: Keystrokes available in the article buffer
6578 * Misc Article:: Other stuff.
6582 @node Hiding Headers
6583 @section Hiding Headers
6584 @cindex hiding headers
6585 @cindex deleting headers
6587 The top section of each article is the @dfn{head}. (The rest is the
6588 @dfn{body}, but you may have guessed that already.)
6590 @vindex gnus-show-all-headers
6591 There is a lot of useful information in the head: the name of the person
6592 who wrote the article, the date it was written and the subject of the
6593 article. That's well and nice, but there's also lots of information
6594 most people do not want to see---what systems the article has passed
6595 through before reaching you, the @code{Message-ID}, the
6596 @code{References}, etc. ad nauseum---and you'll probably want to get rid
6597 of some of those lines. If you want to keep all those lines in the
6598 article buffer, you can set @code{gnus-show-all-headers} to @code{t}.
6600 Gnus provides you with two variables for sifting headers:
6604 @item gnus-visible-headers
6605 @vindex gnus-visible-headers
6606 If this variable is non-@code{nil}, it should be a regular expression
6607 that says what headers you wish to keep in the article buffer. All
6608 headers that do not match this variable will be hidden.
6610 For instance, if you only want to see the name of the person who wrote
6611 the article and the subject, you'd say:
6614 (setq gnus-visible-headers "^From:\\|^Subject:")
6617 This variable can also be a list of regexps to match headers that are to
6620 @item gnus-ignored-headers
6621 @vindex gnus-ignored-headers
6622 This variable is the reverse of @code{gnus-visible-headers}. If this
6623 variable is set (and @code{gnus-visible-headers} is @code{nil}), it
6624 should be a regular expression that matches all lines that you want to
6625 hide. All lines that do not match this variable will remain visible.
6627 For instance, if you just want to get rid of the @code{References} line
6628 and the @code{Xref} line, you might say:
6631 (setq gnus-ignored-headers "^References:\\|^Xref:")
6634 This variable can also be a list of regexps to match headers that are to
6637 Note that if @code{gnus-visible-headers} is non-@code{nil}, this
6638 variable will have no effect.
6642 @vindex gnus-sorted-header-list
6643 Gnus can also sort the headers for you. (It does this by default.) You
6644 can control the sorting by setting the @code{gnus-sorted-header-list}
6645 variable. It is a list of regular expressions that says in what order
6646 the headers are to be displayed.
6648 For instance, if you want the name of the author of the article first,
6649 and then the subject, you might say something like:
6652 (setq gnus-sorted-header-list '("^From:" "^Subject:"))
6655 Any headers that are to remain visible, but are not listed in this
6656 variable, will be displayed in random order after all the headers that
6657 are listed in this variable.
6659 @findex gnus-article-hide-boring-headers
6660 @vindex gnus-article-display-hook
6661 @vindex gnus-boring-article-headers
6662 You can hide further boring headers by entering
6663 @code{gnus-article-hide-boring-headers} into
6664 @code{gnus-article-display-hook}. What this function does depends on
6665 the @code{gnus-boring-article-headers} variable. It's a list, but this
6666 list doesn't actually contain header names. Instead is lists various
6667 @dfn{boring conditions} that Gnus can check and remove from sight.
6669 These conditions are:
6672 Remove all empty headers.
6674 Remove the @code{Newsgroups} header if it only contains the current group
6677 Remove the @code{Followup-To} header if it is identical to the
6678 @code{Newsgroups} header.
6680 Remove the @code{Reply-To} header if it lists the same address as the
6683 Remove the @code{Date} header if the article is less than three days
6687 To include the four first elements, you could say something like;
6690 (setq gnus-boring-article-headers
6691 '(empty newsgroups followup-to reply-to))
6694 This is also the default value for this variable.
6698 @section Using @sc{mime}
6701 Mime is a standard for waving your hands through the air, aimlessly,
6702 while people stand around yawning.
6704 @sc{mime}, however, is a standard for encoding your articles, aimlessly,
6705 while all newsreaders die of fear.
6707 @sc{mime} may specify what character set the article uses, the encoding
6708 of the characters, and it also makes it possible to embed pictures and
6709 other naughty stuff in innocent-looking articles.
6711 @vindex gnus-show-mime
6712 @vindex gnus-show-mime-method
6713 @vindex gnus-strict-mime
6714 @findex metamail-buffer
6715 Gnus handles @sc{mime} by shoving the articles through
6716 @code{gnus-show-mime-method}, which is @code{metamail-buffer} by
6717 default. Set @code{gnus-show-mime} to @code{t} if you want to use
6718 @sc{mime} all the time. However, if @code{gnus-strict-mime} is
6719 non-@code{nil}, the @sc{mime} method will only be used if there are
6720 @sc{mime} headers in the article.
6722 It might be best to just use the toggling functions from the summary
6723 buffer to avoid getting nasty surprises. (For instance, you enter the
6724 group @samp{alt.sing-a-long} and, before you know it, @sc{mime} has
6725 decoded the sound file in the article and some horrible sing-a-long song
6726 comes streaming out out your speakers, and you can't find the volume
6727 button, because there isn't one, and people are starting to look at you,
6728 and you try to stop the program, but you can't, and you can't find the
6729 program to control the volume, and everybody else in the room suddenly
6730 decides to look at you disdainfully, and you'll feel rather stupid.)
6732 Any similarity to real events and people is purely coincidental. Ahem.
6735 @node Customizing Articles
6736 @section Customizing Articles
6737 @cindex article customization
6739 @vindex gnus-article-display-hook
6740 The @code{gnus-article-display-hook} is called after the article has
6741 been inserted into the article buffer. It is meant to handle all
6742 treatment of the article before it is displayed.
6744 @findex gnus-article-maybe-highlight
6745 By default it contains @code{gnus-article-hide-headers},
6746 @code{gnus-article-treat-overstrike}, and
6747 @code{gnus-article-maybe-highlight}, but there are thousands, nay
6748 millions, of functions you can put in this hook. For an overview of
6749 functions @pxref{Article Highlighting}, @pxref{Article Hiding},
6750 @pxref{Article Washing}, @pxref{Article Buttons} and @pxref{Article
6753 You can, of course, write your own functions. The functions are called
6754 from the article buffer, and you can do anything you like, pretty much.
6755 There is no information that you have to keep in the buffer---you can
6756 change everything. However, you shouldn't delete any headers. Instead
6757 make them invisible if you want to make them go away.
6760 @node Article Keymap
6761 @section Article Keymap
6763 Most of the keystrokes in the summary buffer can also be used in the
6764 article buffer. They should behave as if you typed them in the summary
6765 buffer, which means that you don't actually have to have a summary
6766 buffer displayed while reading. You can do it all from the article
6769 A few additional keystrokes are available:
6774 @kindex SPACE (Article)
6775 @findex gnus-article-next-page
6776 Scroll forwards one page (@code{gnus-article-next-page}).
6779 @kindex DEL (Article)
6780 @findex gnus-article-prev-page
6781 Scroll backwards one page (@code{gnus-article-prev-page}).
6784 @kindex C-c ^ (Article)
6785 @findex gnus-article-refer-article
6786 If point is in the neighborhood of a @code{Message-ID} and you press
6787 @kbd{r}, Gnus will try to get that article from the server
6788 (@code{gnus-article-refer-article}).
6791 @kindex C-c C-m (Article)
6792 @findex gnus-article-mail
6793 Send a reply to the address near point (@code{gnus-article-mail}). If
6794 given a prefix, include the mail.
6798 @findex gnus-article-show-summary
6799 Reconfigure the buffers so that the summary buffer becomes visible
6800 (@code{gnus-article-show-summary}).
6804 @findex gnus-article-describe-briefly
6805 Give a very brief description of the available keystrokes
6806 (@code{gnus-article-describe-briefly}).
6809 @kindex TAB (Article)
6810 @findex gnus-article-next-button
6811 Go to the next button, if any (@code{gnus-article-next-button}. This
6812 only makes sense if you have buttonizing turned on.
6815 @kindex M-TAB (Article)
6816 @findex gnus-article-prev-button
6817 Go to the previous button, if any (@code{gnus-article-prev-button}.
6823 @section Misc Article
6827 @item gnus-single-article-buffer
6828 @vindex gnus-single-article-buffer
6829 If non-@code{nil}, use the same article buffer for all the groups.
6830 (This is the default.) If @code{nil}, each group will have its own
6833 @vindex gnus-article-prepare-hook
6834 @item gnus-article-prepare-hook
6835 This hook is called right after the article has been inserted into the
6836 article buffer. It is mainly intended for functions that do something
6837 depending on the contents; it should probably not be used for changing
6838 the contents of the article buffer.
6840 @vindex gnus-article-display-hook
6841 @item gnus-article-display-hook
6842 This hook is called as the last thing when displaying an article, and is
6843 intended for modifying the contents of the buffer, doing highlights,
6844 hiding headers, and the like.
6846 @item gnus-article-mode-hook
6847 @vindex gnus-article-mode-hook
6848 Hook called in article mode buffers.
6850 @vindex gnus-article-mode-line-format
6851 @item gnus-article-mode-line-format
6852 This variable is a format string along the same lines as
6853 @code{gnus-summary-mode-line-format}. It accepts the same
6854 format specifications as that variable, with one extension:
6858 The @dfn{wash status} of the article. This is a short string with one
6859 character for each possible article wash operation that may have been
6863 @vindex gnus-break-pages
6865 @item gnus-break-pages
6866 Controls whether @dfn{page breaking} is to take place. If this variable
6867 is non-@code{nil}, the articles will be divided into pages whenever a
6868 page delimiter appears in the article. If this variable is @code{nil},
6869 paging will not be done.
6871 @item gnus-page-delimiter
6872 @vindex gnus-page-delimiter
6873 This is the delimiter mentioned above. By default, it is @samp{^L}
6878 @node Composing Messages
6879 @chapter Composing Messages
6884 @kindex C-c C-c (Post)
6885 All commands for posting and mailing will put you in a message buffer
6886 where you can edit the article all you like, before you send the article
6887 by pressing @kbd{C-c C-c}. @xref{Top, , Top, message, The Message
6888 Manual}. If you are in a foreign news group, and you wish to post the
6889 article using the foreign server, you can give a prefix to @kbd{C-c C-c}
6890 to make Gnus try to post using the foreign server.
6893 * Mail:: Mailing and replying.
6894 * Post:: Posting and following up.
6895 * Posting Server:: What server should you post via?
6896 * Mail and Post:: Mailing and posting at the same time.
6897 * Archived Messages:: Where Gnus stores the messages you've sent.
6898 @c * Posting Styles:: An easier way to configure some key elements.
6899 @c * Drafts:: Postponing messages and rejected messages.
6900 @c * Rejected Articles:: What happens if the server doesn't like your article?
6903 Also see @pxref{Canceling and Superseding} for information on how to
6904 remove articles you shouldn't have posted.
6910 Variables for customizing outgoing mail:
6913 @item gnus-uu-digest-headers
6914 @vindex gnus-uu-digest-headers
6915 List of regexps to match headers included in digested messages. The
6916 headers will be included in the sequence they are matched.
6924 Variables for composing news articles:
6927 @item gnus-sent-message-ids-file
6928 @vindex gnus-sent-message-ids-file
6929 Gnus will keep a @code{Message-ID} history file of all the mails it has
6930 sent. If it discovers that it has already sent a mail, it will ask the
6931 user whether to re-send the mail. (This is primarily useful when
6932 dealing with @sc{soup} packets and the like where one is apt to sent the
6933 same packet multiple times.) This variable says what the name of this
6934 history file is. It is @file{~/News/Sent-Message-IDs} by default. Set
6935 this variable to @code{nil} if you don't want Gnus to keep a history
6938 @item gnus-sent-message-ids-length
6939 @vindex gnus-sent-message-ids-length
6940 This variable says how many @code{Message-ID}s to keep in the history
6941 file. It is 1000 by default.
6946 @node Posting Server
6947 @section Posting Server
6949 When you press those magical @kbd{C-c C-c} keys to ship off your latest
6950 (extremely intelligent, of course) article, where does it go?
6952 Thank you for asking. I hate you.
6954 @vindex gnus-post-method
6956 It can be quite complicated. Normally, Gnus will use the same native
6957 server. However. If your native server doesn't allow posting, just
6958 reading, you probably want to use some other server to post your
6959 (extremely intelligent and fabulously interesting) articles. You can
6960 then set the @code{gnus-post-method} to some other method:
6963 (setq gnus-post-method '(nnspool ""))
6966 Now, if you've done this, and then this server rejects your article, or
6967 this server is down, what do you do then? To override this variable you
6968 can use a non-zero prefix to the @kbd{C-c C-c} command to force using
6969 the ``current'' server for posting.
6971 If you give a zero prefix (i. e., @kbd{C-u 0 C-c C-c}) to that command,
6972 Gnus will prompt you for what method to use for posting.
6974 You can also set @code{gnus-post-method} to a list of select methods.
6975 If that's the case, Gnus will always prompt you for what method to use
6980 @section Mail and Post
6982 Here's a list of variables that are relevant to both mailing and
6986 @item gnus-mailing-list-groups
6987 @findex gnus-mailing-list-groups
6988 @cindex mailing lists
6990 If your news server offers groups that are really mailing lists that are
6991 gatewayed to the @sc{nntp} server, you can read those groups without
6992 problems, but you can't post/followup to them without some difficulty.
6993 One solution is to add a @code{to-address} to the group parameters
6994 (@pxref{Group Parameters}). An easier thing to do is set the
6995 @code{gnus-mailing-list-groups} to a regexp that match the groups that
6996 really are mailing lists. Then, at least, followups to the mailing
6997 lists will work most of the time. Posting to these groups (@kbd{a}) is
6998 still a pain, though.
7002 You may want to do spell-checking on messages that you send out. Or, if
7003 you don't want to spell-check by hand, you could add automatic
7004 spell-checking via the @code{ispell} package:
7007 @findex ispell-message
7009 (add-hook 'message-send-hook 'ispell-message)
7013 @node Archived Messages
7014 @section Archived Messages
7015 @cindex archived messages
7016 @cindex sent messages
7018 Gnus provides a few different methods for storing the mail you send.
7019 The default method is to use the @dfn{archive virtual server} to store
7020 the mail. If you want to disable this completely, you should set
7021 @code{gnus-message-archive-group} to @code{nil}.
7023 @vindex gnus-message-archive-method
7024 @code{gnus-message-archive-method} says what virtual server Gnus is to
7025 use to store sent messages. It is @code{(nnfolder "archive"
7026 (nnfolder-directory "~/Mail/archive/"))} by default, but you can use any
7027 mail select method (@code{nnml}, @code{nnmbox}, etc.). However,
7028 @code{nnfolder} is a quite likeable select method for doing this sort of
7029 thing. If you don't like the default directory chosen, you could say
7033 (setq gnus-message-archive-method
7034 '(nnfolder "archive"
7035 (nnfolder-inhibit-expiry t)
7036 (nnfolder-active-file "~/News/sent-mail/active")
7037 (nnfolder-directory "~/News/sent-mail/")))
7040 @vindex gnus-message-archive-group
7042 Gnus will insert @code{Gcc} headers in all outgoing messages that point
7043 to one or more group(s) on that server. Which group to use is
7044 determined by the @code{gnus-message-archive-group} variable.
7046 This variable can be:
7050 Messages will be saved in that group.
7051 @item a list of strings
7052 Messages will be saved in all those groups.
7053 @item an alist of regexps, functions and forms
7054 When a key ``matches'', the result is used.
7056 No message archiving will take place. This is the default.
7061 Just saving to a single group called @samp{MisK}:
7063 (setq gnus-message-archive-group "MisK")
7066 Saving to two groups, @samp{MisK} and @samp{safe}:
7068 (setq gnus-message-archive-group '("MisK" "safe"))
7071 Save to different groups based on what group you are in:
7073 (setq gnus-message-archive-group
7074 '(("^alt" "sent-to-alt")
7075 ("mail" "sent-to-mail")
7076 (".*" "sent-to-misc")))
7081 (setq gnus-message-archive-group
7082 '((if (message-news-p)
7087 How about storing all news messages in one file, but storing all mail
7088 messages in one file per month:
7091 (setq gnus-message-archive-group
7092 '((if (message-news-p)
7094 (concat "mail." (format-time-string
7095 "%Y-%m" (current-time))))))
7098 Now, when you send a message off, it will be stored in the appropriate
7099 group. (If you want to disable storing for just one particular message,
7100 you can just remove the @code{Gcc} header that has been inserted.) The
7101 archive group will appear in the group buffer the next time you start
7102 Gnus, or the next time you press @kbd{F} in the group buffer. You can
7103 enter it and read the articles in it just like you'd read any other
7104 group. If the group gets really big and annoying, you can simply rename
7105 if (using @kbd{G r} in the group buffer) to something
7106 nice---@samp{misc-mail-september-1995}, or whatever. New messages will
7107 continue to be stored in the old (now empty) group.
7109 That's the default method of archiving sent mail. Gnus also offers two
7110 other variables for the people who don't like the default method. In
7111 that case you should set @code{gnus-message-archive-group} to
7112 @code{nil}; this will disable archiving.
7114 XEmacs 19.13 doesn't have @code{format-time-string}, so you'll have to
7115 use a different value for @code{gnus-message-archive-group} there.
7119 @item gnus-outgoing-message-group
7120 @vindex gnus-outgoing-message-group
7121 All outgoing messages will be put in this group. If you want to store
7122 all your outgoing mail and articles in the group @samp{nnml:archive},
7123 you set this variable to that value. This variable can also be a list of
7126 If you want to have greater control over what group to put each
7127 message in, you can set this variable to a function that checks the
7128 current newsgroup name and then returns a suitable group name (or list
7133 @c @node Posting Styles
7134 @c @section Posting Styles
7135 @c @cindex posting styles
7138 @c All them variables, they make my head swim.
7140 @c So what if you want a different @code{Organization} and signature based
7141 @c on what groups you post to? And you post both from your home machine
7142 @c and your work machine, and you want different @code{From} lines, and so
7145 @c @vindex gnus-posting-styles
7146 @c One way to do stuff like that is to write clever hooks that change the
7147 @c variables you need to have changed. That's a bit boring, so somebody
7148 @c came up with the bright idea of letting the user specify these things in
7149 @c a handy alist. Here's an example of a @code{gnus-posting-styles}
7154 @c (signature . "Peace and happiness")
7155 @c (organization . "What me?"))
7157 @c (signature . "Death to everybody"))
7158 @c ("comp.emacs.i-love-it"
7159 @c (organization . "Emacs is it")))
7162 @c As you might surmise from this example, this alist consists of several
7163 @c @dfn{styles}. Each style will be applicable if the first element
7164 @c ``matches'', in some form or other. The entire alist will be iterated
7165 @c over, from the beginning towards the end, and each match will be
7166 @c applied, which means that attributes in later styles that match override
7167 @c the same attributes in earlier matching styles. So
7168 @c @samp{comp.programming.literate} will have the @samp{Death to everybody}
7169 @c signature and the @samp{What me?} @code{Organization} header.
7171 @c The first element in each style is called the @code{match}. If it's a
7172 @c string, then Gnus will try to regexp match it against the group name.
7173 @c If it's a function symbol, that function will be called with no
7174 @c arguments. If it's a variable symbol, then the variable will be
7175 @c referenced. If it's a list, then that list will be @code{eval}ed. In
7176 @c any case, if this returns a non-@code{nil} value, then the style is said
7179 @c Each style may contain a arbitrary amount of @dfn{attributes}. Each
7180 @c attribute consists of a @var{(name . value)} pair. The attribute name
7181 @c can be one of @code{signature}, @code{organization} or @code{from}. The
7182 @c attribute name can also be a string. In that case, this will be used as
7183 @c a header name, and the value will be inserted in the headers of the
7186 @c The attribute value can be a string (used verbatim), a function (the
7187 @c return value will be used), a variable (its value will be used) or a
7188 @c list (it will be @code{eval}ed and the return value will be used).
7190 @c So here's a new example:
7193 @c (setq gnus-posting-styles
7195 @c (signature . "~/.signature")
7196 @c (from . "user@@foo (user)")
7197 @c ("X-Home-Page" . (getenv "WWW_HOME"))
7198 @c (organization . "People's Front Against MWM"))
7200 @c (signature . my-funny-signature-randomizer))
7201 @c ((equal (system-name) "gnarly")
7202 @c (signature . my-quote-randomizer))
7203 @c (posting-from-work-p
7204 @c (signature . "~/.work-signature")
7205 @c (from . "user@@bar.foo (user)")
7206 @c (organization . "Important Work, Inc"))
7208 @c (signature . "~/.mail-signature"))))
7215 @c If you are writing a message (mail or news) and suddenly remember that
7216 @c you have a steak in the oven (or some pesto in the food processor, you
7217 @c craazy vegetarians), you'll probably wish there was a method to save the
7218 @c message you are writing so that you can continue editing it some other
7219 @c day, and send it when you feel its finished.
7221 @c Well, don't worry about it. Whenever you start composing a message of
7222 @c some sort using the Gnus mail and post commands, the buffer you get will
7223 @c automatically associate to an article in a special @dfn{draft} group.
7224 @c If you save the buffer the normal way (@kbd{C-x C-s}, for instance), the
7225 @c article will be saved there. (Auto-save files also go to the draft
7229 @c @vindex gnus-draft-group-directory
7230 @c The draft group is a special group (which is implemented as an
7231 @c @code{nndraft} group, if you absolutely have to know) called
7232 @c @samp{nndraft:drafts}. The variable @code{gnus-draft-group-directory}
7233 @c controls both the name of the group and the location---the leaf element
7234 @c in the path will be used as the name of the group. What makes this
7235 @c group special is that you can't tick any articles in it or mark any
7236 @c articles as read---all articles in the group are permanently unread.
7238 @c If the group doesn't exist, it will be created and you'll be subscribed
7241 @c @findex gnus-dissociate-buffer-from-draft
7242 @c @kindex C-c M-d (Mail)
7243 @c @kindex C-c M-d (Post)
7244 @c @findex gnus-associate-buffer-with-draft
7245 @c @kindex C-c C-d (Mail)
7246 @c @kindex C-c C-d (Post)
7247 @c If you're writing some super-secret message that you later want to
7248 @c encode with PGP before sending, you may wish to turn the auto-saving
7249 @c (and association with the draft group) off. You never know who might be
7250 @c interested in reading all your extremely valuable and terribly horrible
7251 @c and interesting secrets. The @kbd{C-c M-d}
7252 @c (@code{gnus-dissociate-buffer-from-draft}) command does that for you.
7253 @c If you change your mind and want to turn the auto-saving back on again,
7254 @c @kbd{C-c C-d} (@code{gnus-associate-buffer-with-draft} does that.
7256 @c @vindex gnus-use-draft
7257 @c To leave association with the draft group off by default, set
7258 @c @code{gnus-use-draft} to @code{nil}. It is @code{t} by default.
7260 @c @findex gnus-summary-send-draft
7261 @c @kindex S D c (Summary)
7262 @c When you want to continue editing the article, you simply enter the
7263 @c draft group and push @kbd{S D c} (@code{gnus-summary-send-draft}) to do
7264 @c that. You will be placed in a buffer where you left off.
7266 @c Rejected articles will also be put in this draft group (@pxref{Rejected
7269 @c @findex gnus-summary-send-all-drafts
7270 @c If you have lots of rejected messages you want to post (or mail) without
7271 @c doing further editing, you can use the @kbd{S D a} command
7272 @c (@code{gnus-summary-send-all-drafts}). This command understands the
7273 @c process/prefix convention (@pxref{Process/Prefix}).
7276 @c @node Rejected Articles
7277 @c @section Rejected Articles
7278 @c @cindex rejected articles
7280 @c Sometimes a news server will reject an article. Perhaps the server
7281 @c doesn't like your face. Perhaps it just feels miserable. Perhaps
7282 @c @emph{there be demons}. Perhaps you have included too much cited text.
7283 @c Perhaps the disk is full. Perhaps the server is down.
7285 @c These situations are, of course, totally beyond the control of Gnus.
7286 @c (Gnus, of course, loves the way you look, always feels great, has angels
7287 @c fluttering around inside of it, doesn't care about how much cited text
7288 @c you include, never runs full and never goes down.) So Gnus saves these
7289 @c articles until some later time when the server feels better.
7291 @c The rejected articles will automatically be put in a special draft group
7292 @c (@pxref{Drafts}). When the server comes back up again, you'd then
7293 @c typically enter that group and send all the articles off.
7296 @node Select Methods
7297 @chapter Select Methods
7298 @cindex foreign groups
7299 @cindex select methods
7301 A @dfn{foreign group} is a group that is not read by the usual (or
7302 default) means. It could be, for instance, a group from a different
7303 @sc{nntp} server, it could be a virtual group, or it could be your own
7304 personal mail group.
7306 A foreign group (or any group, really) is specified by a @dfn{name} and
7307 a @dfn{select method}. To take the latter first, a select method is a
7308 list where the first element says what backend to use (eg. @code{nntp},
7309 @code{nnspool}, @code{nnml}) and the second element is the @dfn{server
7310 name}. There may be additional elements in the select method, where the
7311 value may have special meaning for the backend in question.
7313 One could say that a select method defines a @dfn{virtual server}---so
7314 we do just that (@pxref{The Server Buffer}).
7316 The @dfn{name} of the group is the name the backend will recognize the
7319 For instance, the group @samp{soc.motss} on the @sc{nntp} server
7320 @samp{some.where.edu} will have the name @samp{soc.motss} and select
7321 method @code{(nntp "some.where.edu")}. Gnus will call this group, in
7322 all circumstances, @samp{nntp+some.where.edu:soc.motss}, even though the
7323 @code{nntp} backend just knows this group as @samp{soc.motss}.
7325 The different methods all have their peculiarities, of course.
7328 * The Server Buffer:: Making and editing virtual servers.
7329 * Getting News:: Reading USENET news with Gnus.
7330 * Getting Mail:: Reading your personal mail with Gnus.
7331 * Other Sources:: Reading directories, files, SOUP packets.
7332 * Combined Groups:: Combining groups into one group.
7336 @node The Server Buffer
7337 @section The Server Buffer
7339 Traditionally, a @dfn{server} is a machine or a piece of software that
7340 one connects to, and then requests information from. Gnus does not
7341 connect directly to any real servers, but does all transactions through
7342 one backend or other. But that's just putting one layer more between
7343 the actual media and Gnus, so we might just as well say that each
7344 backend represents a virtual server.
7346 For instance, the @code{nntp} backend may be used to connect to several
7347 different actual @sc{nntp} servers, or, perhaps, to many different ports
7348 on the same actual @sc{nntp} server. You tell Gnus which backend to
7349 use, and what parameters to set by specifying a @dfn{select method}.
7351 These select methods specifications can sometimes become quite
7352 complicated---say, for instance, that you want to read from the
7353 @sc{nntp} server @samp{news.funet.fi} on port number @code{13}, which
7354 hangs if queried for @sc{nov} headers and has a buggy select. Ahem.
7355 Anyways, if you had to specify that for each group that used this
7356 server, that would be too much work, so Gnus offers a way of naming
7357 select methods, which is what you do in the server buffer.
7359 To enter the server buffer, user the @kbd{^}
7360 (@code{gnus-group-enter-server-mode}) command in the group buffer.
7363 * Server Buffer Format:: You can customize the look of this buffer.
7364 * Server Commands:: Commands to manipulate servers.
7365 * Example Methods:: Examples server specifications.
7366 * Creating a Virtual Server:: An example session.
7367 * Servers and Methods:: You can use server names as select methods.
7368 * Unavailable Servers:: Some servers you try to contact may be down.
7371 @vindex gnus-server-mode-hook
7372 @code{gnus-server-mode-hook} is run when creating the server buffer.
7375 @node Server Buffer Format
7376 @subsection Server Buffer Format
7377 @cindex server buffer format
7379 @vindex gnus-server-line-format
7380 You can change the look of the server buffer lines by changing the
7381 @code{gnus-server-line-format} variable. This is a @code{format}-like
7382 variable, with some simple extensions:
7387 How the news is fetched---the backend name.
7390 The name of this server.
7393 Where the news is to be fetched from---the address.
7396 The opened/closed/denied status of the server.
7399 @vindex gnus-server-mode-line-format
7400 The mode line can also be customized by using the
7401 @code{gnus-server-mode-line-format} variable. The following specs are
7412 Also @pxref{Formatting Variables}.
7415 @node Server Commands
7416 @subsection Server Commands
7417 @cindex server commands
7423 @findex gnus-server-add-server
7424 Add a new server (@code{gnus-server-add-server}).
7428 @findex gnus-server-edit-server
7429 Edit a server (@code{gnus-server-edit-server}).
7432 @kindex SPACE (Server)
7433 @findex gnus-server-read-server
7434 Browse the current server (@code{gnus-server-read-server}).
7438 @findex gnus-server-exit
7439 Return to the group buffer (@code{gnus-server-exit}).
7443 @findex gnus-server-kill-server
7444 Kill the current server (@code{gnus-server-kill-server}).
7448 @findex gnus-server-yank-server
7449 Yank the previously killed server (@code{gnus-server-yank-server}).
7453 @findex gnus-server-copy-server
7454 Copy the current server (@code{gnus-server-copy-server}).
7458 @findex gnus-server-list-servers
7459 List all servers (@code{gnus-server-list-servers}).
7463 @findex gnus-server-scan-server
7464 Request that the server scan its sources for new articles
7465 (@code{gnus-server-scan-server}). This is mainly sensible with mail
7471 @node Example Methods
7472 @subsection Example Methods
7474 Most select methods are pretty simple and self-explanatory:
7477 (nntp "news.funet.fi")
7480 Reading directly from the spool is even simpler:
7486 As you can see, the first element in a select method is the name of the
7487 backend, and the second is the @dfn{address}, or @dfn{name}, if you
7490 After these two elements, there may be a arbitrary number of
7491 @var{(variable form)} pairs.
7493 To go back to the first example---imagine that you want to read from
7494 port @code{15} from that machine. This is what the select method should
7498 (nntp "news.funet.fi" (nntp-port-number 15))
7501 You should read the documentation to each backend to find out what
7502 variables are relevant, but here's an @code{nnmh} example.
7504 @code{nnmh} is a mail backend that reads a spool-like structure. Say
7505 you have two structures that you wish to access: One is your private
7506 mail spool, and the other is a public one. Here's the possible spec for
7510 (nnmh "private" (nnmh-directory "~/private/mail/"))
7513 (This server is then called @samp{private}, but you may have guessed
7516 Here's the method for a public spool:
7520 (nnmh-directory "/usr/information/spool/")
7521 (nnmh-get-new-mail nil))
7525 @node Creating a Virtual Server
7526 @subsection Creating a Virtual Server
7528 If you're saving lots of articles in the cache by using persistent
7529 articles, you may want to create a virtual server to read the cache.
7531 First you need to add a new server. The @kbd{a} command does that. It
7532 would probably be best to use @code{nnspool} to read the cache. You
7533 could also use @code{nnml} or @code{nnmh}, though.
7535 Type @kbd{a nnspool RET cache RET}.
7537 You should now have a brand new @code{nnspool} virtual server called
7538 @samp{cache}. You now need to edit it to have the right definitions.
7539 Type @kbd{e} to edit the server. You'll be entered into a buffer that
7540 will contain the following:
7550 (nnspool-spool-directory "~/News/cache/")
7551 (nnspool-nov-directory "~/News/cache/")
7552 (nnspool-active-file "~/News/cache/active"))
7555 Type @kbd{C-c C-c} to return to the server buffer. If you now press
7556 @kbd{RET} over this virtual server, you should be entered into a browse
7557 buffer, and you should be able to enter any of the groups displayed.
7560 @node Servers and Methods
7561 @subsection Servers and Methods
7563 Wherever you would normally use a select method
7564 (eg. @code{gnus-secondary-select-method}, in the group select method,
7565 when browsing a foreign server) you can use a virtual server name
7566 instead. This could potentially save lots of typing. And it's nice all
7570 @node Unavailable Servers
7571 @subsection Unavailable Servers
7573 If a server seems to be unreachable, Gnus will mark that server as
7574 @code{denied}. That means that any subsequent attempt to make contact
7575 with that server will just be ignored. ``It can't be opened,'' Gnus
7576 will tell you, without making the least effort to see whether that is
7577 actually the case or not.
7579 That might seem quite naughty, but it does make sense most of the time.
7580 Let's say you have 10 groups subscribed to the server
7581 @samp{nepholococcygia.com}. This server is located somewhere quite far
7582 away from you, the machine is quite, so it takes 1 minute just to find
7583 out that it refuses connection from you today. If Gnus were to attempt
7584 to do that 10 times, you'd be quite annoyed, so Gnus won't attempt to do
7585 that. Once it has gotten a single ``connection refused'', it will
7586 regard that server as ``down''.
7588 So, what happens if the machine was only feeling unwell temporarily?
7589 How do you test to see whether the machine has come up again?
7591 You jump to the server buffer (@pxref{The Server Buffer}) and poke it
7592 with the following commands:
7598 @findex gnus-server-open-server
7599 Try to establish connection to the server on the current line
7600 (@code{gnus-server-open-server}).
7604 @findex gnus-server-close-server
7605 Close the connection (if any) to the server
7606 (@code{gnus-server-close-server}).
7610 @findex gnus-server-deny-server
7611 Mark the current server as unreachable
7612 (@code{gnus-server-deny-server}).
7615 @kindex M-o (Server)
7616 @findex gnus-server-open-all-servers
7617 Open the connections to all servers in the buffer
7618 (@code{gnus-server-open-all-servers}).
7621 @kindex M-c (Server)
7622 @findex gnus-server-close-all-servers
7623 Close the connections to all servers in the buffer
7624 (@code{gnus-server-close-all-servers}).
7628 @findex gnus-server-remove-denials
7629 Remove all marks to whether Gnus was denied connection from all servers
7630 (@code{gnus-server-remove-denials}).
7636 @section Getting News
7637 @cindex reading news
7638 @cindex news backends
7640 A newsreader is normally used for reading news. Gnus currently provides
7641 only two methods of getting news---it can read from an @sc{nntp} server,
7642 or it can read from a local spool.
7645 * NNTP:: Reading news from an @sc{nntp} server.
7646 * News Spool:: Reading news from the local spool.
7651 @subsection @sc{nntp}
7654 Subscribing to a foreign group from an @sc{nntp} server is rather easy.
7655 You just specify @code{nntp} as method and the address of the @sc{nntp}
7656 server as the, uhm, address.
7658 If the @sc{nntp} server is located at a non-standard port, setting the
7659 third element of the select method to this port number should allow you
7660 to connect to the right port. You'll have to edit the group info for
7661 that (@pxref{Foreign Groups}).
7663 The name of the foreign group can be the same as a native group. In
7664 fact, you can subscribe to the same group from as many different servers
7665 you feel like. There will be no name collisions.
7667 The following variables can be used to create a virtual @code{nntp}
7672 @item nntp-server-opened-hook
7673 @vindex nntp-server-opened-hook
7674 @cindex @sc{mode reader}
7676 @cindex authentification
7677 @cindex nntp authentification
7678 @findex nntp-send-authinfo
7679 @findex nntp-send-mode-reader
7680 @code{nntp-server-opened-hook} is run after a connection has been made.
7681 It can be used to send commands to the @sc{nntp} server after it has
7682 been contacted. By default is sends the command @code{MODE READER} to
7683 the server with the @code{nntp-send-mode-reader} function.
7685 @item nntp-authinfo-function
7686 @vindex nntp-authinfo-function
7687 This function will be used to send @samp{AUTHINFO} to the @sc{nntp}
7688 server. Available functions include:
7691 @item nntp-send-authinfo
7692 @findex nntp-send-authinfo
7693 This function will used you current login name as the user name and will
7694 prompt you for the password. This is the default.
7696 @item nntp-send-nosy-authinfo
7697 @findex nntp-send-nosy-authinfo
7698 This function will prompt you for both user name and password.
7700 @item nntp-send-authinfo-from-file
7701 @findex nntp-send-authinfo-from-file
7702 This function will use your current login name as the user name and will
7703 read the @sc{nntp} password from @file{~/.nntp-authinfo}.
7706 @item nntp-server-action-alist
7707 @vindex nntp-server-action-alist
7708 This is an list of regexps to match on server types and actions to be
7709 taken when matches are made. For instance, if you want Gnus to beep
7710 every time you connect to innd, you could say something like:
7713 (setq nntp-server-action-alist
7717 You probably don't want to do that, though.
7719 The default value is
7722 '(("nntpd 1\\.5\\.11t"
7723 (remove-hook 'nntp-server-opened-hook nntp-send-mode-reader)))
7726 This ensures that Gnus doesn't send the @code{MODE READER} command to
7727 nntpd 1.5.11t, since that command chokes that server, I've been told.
7729 @item nntp-maximum-request
7730 @vindex nntp-maximum-request
7731 If the @sc{nntp} server doesn't support @sc{nov} headers, this backend
7732 will collect headers by sending a series of @code{head} commands. To
7733 speed things up, the backend sends lots of these commands without
7734 waiting for reply, and then reads all the replies. This is controlled
7735 by the @code{nntp-maximum-request} variable, and is 400 by default. If
7736 your network is buggy, you should set this to 1.
7738 @item nntp-connection-timeout
7739 @vindex nntp-connection-timeout
7740 If you have lots of foreign @code{nntp} groups that you connect to
7741 regularly, you're sure to have problems with @sc{nntp} servers not
7742 responding properly, or being too loaded to reply within reasonable
7743 time. This is can lead to awkward problems, which can be helped
7744 somewhat by setting @code{nntp-connection-timeout}. This is an integer
7745 that says how many seconds the @code{nntp} backend should wait for a
7746 connection before giving up. If it is @code{nil}, which is the default,
7747 no timeouts are done.
7749 @item nntp-command-timeout
7750 @vindex nntp-command-timeout
7751 @cindex PPP connections
7752 @cindex dynamic IP addresses
7753 If you're running Gnus on a machine that has a dynamically assigned
7754 address, Gnus may become confused. If the address of your machine
7755 changes after connecting to the @sc{nntp} server, Gnus will simply sit
7756 waiting forever for replies from the server. To help with this
7757 unfortunate problem, you can set this command to a number. Gnus will
7758 then, if it sits waiting longer than that number of seconds for a reply
7759 from the server, shut down the connection, start a new one, and resend
7760 the command. This should hopefully be transparent to the user. A
7761 likely number is 30 seconds.
7763 @item nntp-retry-on-break
7764 @vindex nntp-retry-on-break
7765 If this variable is non-@code{nil}, you can also @kbd{C-g} if Gnus
7766 hangs. This will have much the same effect as the command timeout
7769 @item nntp-server-hook
7770 @vindex nntp-server-hook
7771 This hook is run as the last step when connecting to an @sc{nntp}
7774 @findex nntp-open-rlogin
7775 @findex nntp-open-network-stream
7776 @item nntp-open-server-function
7777 @vindex nntp-open-server-function
7778 This function is used to connect to the remote system. Two pre-made
7779 functions are @code{nntp-open-network-stream}, which is the default, and
7780 simply connects to some port or other on the remote system. The other
7781 is @code{nntp-open-rlogin}, which does an rlogin on the remote system,
7782 and then does a telnet to the @sc{nntp} server available there.
7784 @item nntp-rlogin-parameters
7785 @vindex nntp-rlogin-parameters
7786 If you use @code{nntp-open-rlogin} as the
7787 @code{nntp-open-server-function}, this list will be used as the
7788 parameter list given to @code{rsh}.
7790 @item nntp-end-of-line
7791 @vindex nntp-end-of-line
7792 String to use as end-of-line markers when talking to the @sc{nntp}
7793 server. This is @samp{\r\n} by default, but should be @samp{\n} when
7794 using @code{rlogin} to talk to the server.
7796 @item nntp-rlogin-user-name
7797 @vindex nntp-rlogin-user-name
7798 User name on the remote system when using the @code{rlogin} connect
7802 @vindex nntp-address
7803 The address of the remote system running the @sc{nntp} server.
7805 @item nntp-port-number
7806 @vindex nntp-port-number
7807 Port number to connect to when using the @code{nntp-open-network-stream}
7810 @item nntp-buggy-select
7811 @vindex nntp-buggy-select
7812 Set this to non-@code{nil} if your select routine is buggy.
7814 @item nntp-nov-is-evil
7815 @vindex nntp-nov-is-evil
7816 If the @sc{nntp} server does not support @sc{nov}, you could set this
7817 variable to @code{t}, but @code{nntp} usually checks whether @sc{nov}
7818 can be used automatically.
7820 @item nntp-xover-commands
7821 @vindex nntp-xover-commands
7824 List of strings that are used as commands to fetch @sc{nov} lines from a
7825 server. The default value of this variable is @code{("XOVER"
7829 @vindex nntp-nov-gap
7830 @code{nntp} normally sends just one big request for @sc{nov} lines to
7831 the server. The server responds with one huge list of lines. However,
7832 if you have read articles 2-5000 in the group, and only want to read
7833 article 1 and 5001, that means that @code{nntp} will fetch 4999 @sc{nov}
7834 lines that you do not want, and will not use. This variable says how
7835 big a gap between two consecutive articles is allowed to be before the
7836 @code{XOVER} request is split into several request. Note that if your
7837 network is fast, setting this variable to a really small number means
7838 that fetching will probably be slower. If this variable is @code{nil},
7839 @code{nntp} will never split requests.
7841 @item nntp-prepare-server-hook
7842 @vindex nntp-prepare-server-hook
7843 A hook run before attempting to connect to an @sc{nntp} server.
7845 @item nntp-warn-about-losing-connection
7846 @vindex nntp-warn-about-losing-connection
7847 If this variable is non-@code{nil}, some noise will be made when a
7848 server closes connection.
7854 @subsection News Spool
7858 Subscribing to a foreign group from the local spool is extremely easy,
7859 and might be useful, for instance, to speed up reading groups like
7860 @samp{alt.binaries.pictures.furniture}.
7862 Anyways, you just specify @code{nnspool} as the method and @samp{} (or
7863 anything else) as the address.
7865 If you have access to a local spool, you should probably use that as the
7866 native select method (@pxref{Finding the News}). It is normally faster
7867 than using an @code{nntp} select method, but might not be. It depends.
7868 You just have to try to find out what's best at your site.
7872 @item nnspool-inews-program
7873 @vindex nnspool-inews-program
7874 Program used to post an article.
7876 @item nnspool-inews-switches
7877 @vindex nnspool-inews-switches
7878 Parameters given to the inews program when posting an article.
7880 @item nnspool-spool-directory
7881 @vindex nnspool-spool-directory
7882 Where @code{nnspool} looks for the articles. This is normally
7883 @file{/usr/spool/news/}.
7885 @item nnspool-nov-directory
7886 @vindex nnspool-nov-directory
7887 Where @code{nnspool} will look for @sc{nov} files. This is normally
7888 @file{/usr/spool/news/over.view/}.
7890 @item nnspool-lib-dir
7891 @vindex nnspool-lib-dir
7892 Where the news lib dir is (@file{/usr/lib/news/} by default).
7894 @item nnspool-active-file
7895 @vindex nnspool-active-file
7896 The path of the active file.
7898 @item nnspool-newsgroups-file
7899 @vindex nnspool-newsgroups-file
7900 The path of the group descriptions file.
7902 @item nnspool-history-file
7903 @vindex nnspool-history-file
7904 The path of the news history file.
7906 @item nnspool-active-times-file
7907 @vindex nnspool-active-times-file
7908 The path of the active date file.
7910 @item nnspool-nov-is-evil
7911 @vindex nnspool-nov-is-evil
7912 If non-@code{nil}, @code{nnspool} won't try to use any @sc{nov} files
7915 @item nnspool-sift-nov-with-sed
7916 @vindex nnspool-sift-nov-with-sed
7918 If non-@code{nil}, which is the default, use @code{sed} to get the
7919 relevant portion from the overview file. If nil, @code{nnspool} will
7920 load the entire file into a buffer and process it there.
7926 @section Getting Mail
7927 @cindex reading mail
7930 Reading mail with a newsreader---isn't that just plain WeIrD? But of
7934 * Getting Started Reading Mail:: A simple cookbook example.
7935 * Splitting Mail:: How to create mail groups.
7936 * Mail Backend Variables:: Variables for customizing mail handling.
7937 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
7938 * Mail and Procmail:: Reading mail groups that procmail create.
7939 * Incorporating Old Mail:: What about the old mail you have?
7940 * Expiring Mail:: Getting rid of unwanted mail.
7941 * Washing Mail:: Removing gruft from the mail you get.
7942 * Duplicates:: Dealing with duplicated mail.
7943 * Not Reading Mail:: Using mail backends for reading other files.
7944 * Choosing a Mail Backend:: Gnus can read a variety of mail formats.
7948 @node Getting Started Reading Mail
7949 @subsection Getting Started Reading Mail
7951 It's quite easy to use Gnus to read your new mail. You just plonk the
7952 mail backend of your choice into @code{gnus-secondary-select-methods},
7953 and things will happen automatically.
7955 For instance, if you want to use @code{nnml} (which is a one file per
7956 mail backend), you could put the following in your @file{.gnus} file:
7959 (setq gnus-secondary-select-methods
7960 '((nnml "private")))
7963 Now, the next time you start Gnus, this backend will be queried for new
7964 articles, and it will move all the messages in your spool file to its
7965 directory, which is @code{~/Mail/} by default. The new group that will
7966 be created (@samp{mail.misc}) will be subscribed, and you can read it
7967 like any other group.
7969 You will probably want to split the mail into several groups, though:
7972 (setq nnmail-split-methods
7973 '(("junk" "^From:.*Lars Ingebrigtsen")
7974 ("crazy" "^Subject:.*die\\|^Organization:.*flabby")
7978 This will result in three new mail groups being created:
7979 @samp{nnml:junk}, @samp{nnml:crazy}, and @samp{nnml:other}. All the
7980 mail that doesn't fit into the first two groups will be placed in the
7983 This should be sufficient for reading mail with Gnus. You might want to
7984 give the other sections in this part of the manual a perusal, though,
7985 especially @pxref{Choosing a Mail Backend} and @pxref{Expiring Mail}.
7988 @node Splitting Mail
7989 @subsection Splitting Mail
7990 @cindex splitting mail
7991 @cindex mail splitting
7993 @vindex nnmail-split-methods
7994 The @code{nnmail-split-methods} variable says how the incoming mail is
7995 to be split into groups.
7998 (setq nnmail-split-methods
7999 '(("mail.junk" "^From:.*Lars Ingebrigtsen")
8000 ("mail.crazy" "^Subject:.*die\\|^Organization:.*flabby")
8004 This variable is a list of lists, where the first element of each of
8005 these lists is the name of the mail group (they do not have to be called
8006 something beginning with @samp{mail}, by the way), and the second
8007 element is a regular expression used on the header of each mail to
8008 determine if it belongs in this mail group.
8010 If the first element is the special symbol @code{junk}, then messages
8011 that match the regexp will disappear into the aether. Use with
8014 The second element can also be a function. In that case, it will be
8015 called narrowed to the headers with the first element of the rule as the
8016 argument. It should return a non-@code{nil} value if it thinks that the
8017 mail belongs in that group.
8019 The last of these groups should always be a general one, and the regular
8020 expression should @emph{always} be @samp{} so that it matches any
8021 mails that haven't been matched by any of the other regexps.
8023 If you like to tinker with this yourself, you can set this variable to a
8024 function of your choice. This function will be called without any
8025 arguments in a buffer narrowed to the headers of an incoming mail
8026 message. The function should return a list of groups names that it
8027 thinks should carry this mail message.
8029 Note that the mail backends are free to maul the poor, innocent
8030 incoming headers all they want to. They all add @code{Lines} headers;
8031 some add @code{X-Gnus-Group} headers; most rename the Unix mbox
8032 @code{From<SPACE>} line to something else.
8034 @vindex nnmail-crosspost
8035 The mail backends all support cross-posting. If several regexps match,
8036 the mail will be ``cross-posted'' to all those groups.
8037 @code{nnmail-crosspost} says whether to use this mechanism or not. Note
8038 that no articles are crossposted to the general (@samp{}) group.
8040 @vindex nnmail-crosspost-link-function
8043 @code{nnmh} and @code{nnml} makes crossposts by creating hard links to
8044 the crossposted articles. However, not all files systems support hard
8045 links. If that's the case for you, set
8046 @code{nnmail-crosspost-link-function} to @code{copy-file}. (This
8047 variable is @code{add-name-to-file} by default.)
8049 Gnus gives you all the opportunity you could possibly want for shooting
8050 yourself in the foot. Let's say you create a group that will contain
8051 all the mail you get from your boss. And then you accidentally
8052 unsubscribe from the group. Gnus will still put all the mail from your
8053 boss in the unsubscribed group, and so, when your boss mails you ``Have
8054 that report ready by Monday or you're fired!'', you'll never see it and,
8055 come Tuesday, you'll still believe that you're gainfully employed while
8056 you really should be out collecting empty bottles to save up for next
8060 @node Mail Backend Variables
8061 @subsection Mail Backend Variables
8063 These variables are (for the most part) pertinent to all the various
8067 @vindex nnmail-read-incoming-hook
8068 @item nnmail-read-incoming-hook
8069 The mail backends all call this hook after reading new mail. You can
8070 use this hook to notify any mail watch programs, if you want to.
8072 @vindex nnmail-spool-file
8073 @item nnmail-spool-file
8077 @vindex nnmail-pop-password
8078 @vindex nnmail-pop-password-required
8079 The backends will look for new mail in this file. If this variable is
8080 @code{nil}, the mail backends will never attempt to fetch mail by
8081 themselves. If you are using a POP mail server and your name is
8082 @samp{larsi}, you should set this variable to @samp{po:larsi}. If
8083 your name is not @samp{larsi}, you should probably modify that
8084 slightly, but you may have guessed that already, you smart & handsome
8085 devil! You can also set this variable to @code{pop}, and Gnus will try
8086 to figure out the POP mail string by itself. In any case, Gnus will
8087 call @code{movemail} which will contact the POP server named in the
8088 @code{MAILHOST} environment variable. If the POP server needs a
8089 password, you can either set @code{nnmail-pop-password-required} to
8090 @code{t} and be prompted for the password, or set
8091 @code{nnmail-pop-password} to the password itself.
8093 When you use a mail backend, Gnus will slurp all your mail from your
8094 inbox and plonk it down in your home directory. Gnus doesn't move any
8095 mail if you're not using a mail backend---you have to do a lot of magic
8096 invocations first. At the time when you have finished drawing the
8097 pentagram, lightened the candles, and sacrificed the goat, you really
8098 shouldn't be too surprised when Gnus moves your mail.
8100 @vindex nnmail-use-procmail
8101 @vindex nnmail-procmail-suffix
8102 @item nnmail-use-procmail
8103 If non-@code{nil}, the mail backends will look in
8104 @code{nnmail-procmail-directory} for incoming mail. All the files in
8105 that directory that have names ending in @code{nnmail-procmail-suffix}
8106 will be considered incoming mailboxes, and will be searched for new
8109 @vindex nnmail-crash-box
8110 @item nnmail-crash-box
8111 When the mail backends read a spool file, it is first moved to this
8112 file, which is @file{~/.gnus-crash-box} by default. If this file
8113 already exists, it will always be read (and incorporated) before any
8116 @vindex nnmail-prepare-incoming-hook
8117 @item nnmail-prepare-incoming-hook
8118 This is run in a buffer that holds all the new incoming mail, and can be
8119 used for, well, anything, really.
8121 @vindex nnmail-split-hook
8122 @item nnmail-split-hook
8123 @findex article-decode-rfc1522
8124 @findex RFC1522 decoding
8125 Hook run in the buffer where the mail headers of each message is kept
8126 just before the splitting based on these headers is done. The hook is
8127 free to modify the buffer contents in any way it sees fit---the buffer
8128 is discarded after the splitting has been done, and no changes performed
8129 in the buffer will show up in any files. @code{article-decode-rfc1522}
8130 is one likely function to add to this hook.
8132 @vindex nnmail-pre-get-new-mail-hook
8133 @vindex nnmail-post-get-new-mail-hook
8134 @item nnmail-pre-get-new-mail-hook
8135 @itemx nnmail-post-get-new-mail-hook
8136 These are two useful hooks executed when treating new incoming
8137 mail---@code{nnmail-pre-get-new-mail-hook} (is called just before
8138 starting to handle the new mail) and
8139 @code{nnmail-post-get-new-mail-hook} (is called when the mail handling
8140 is done). Here's and example of using these two hooks to change the
8141 default file modes the new mail files get:
8144 (add-hook 'gnus-pre-get-new-mail-hook
8145 (lambda () (set-default-file-modes 511)))
8147 (add-hook 'gnus-post-get-new-mail-hook
8148 (lambda () (set-default-file-modes 551)))
8151 @item nnmail-tmp-directory
8152 @vindex nnmail-tmp-directory
8153 This variable says where to move the incoming mail to while processing
8154 it. This is usually done in the same directory that the mail backend
8155 inhabits (i.e., @file{~/Mail/}), but if this variable is non-@code{nil},
8156 it will be used instead.
8158 @item nnmail-movemail-program
8159 @vindex nnmail-movemail-program
8160 This program is executed to move mail from the user's inbox to her home
8161 directory. The default is @samp{movemail}.
8163 This can also be a function. In that case, the function will be called
8164 with two parameters -- the name of the inbox, and the file to be moved
8167 @item nnmail-delete-incoming
8168 @vindex nnmail-delete-incoming
8169 @cindex incoming mail files
8170 @cindex deleting incoming files
8171 If non-@code{nil}, the mail backends will delete the temporary incoming
8172 file after splitting mail into the proper groups. This is @code{nil} by
8173 default for reasons of security.
8175 Since Red Gnus is an alpha release, it is to be expected to lose mail.
8176 (No Gnus release since (ding) Gnus 0.10 (or something like that) have
8177 lost mail, I think, but that's not the point.) By not deleting the
8178 Incoming* files, one can be sure to not lose mail -- if Gnus totally
8179 whacks out, one can always recover what was lost.
8181 Delete the @file{Incoming*} files at will.
8183 @item nnmail-use-long-file-names
8184 @vindex nnmail-use-long-file-names
8185 If non-@code{nil}, the mail backends will use long file and directory
8186 names. Groups like @samp{mail.misc} will end up in directories like
8187 @file{mail.misc/}. If it is @code{nil}, the same group will end up in
8190 @item nnmail-delete-file-function
8191 @vindex nnmail-delete-file-function
8193 Function called to delete files. It is @code{delete-file} by default.
8198 @node Fancy Mail Splitting
8199 @subsection Fancy Mail Splitting
8200 @cindex mail splitting
8201 @cindex fancy mail splitting
8203 @vindex nnmail-split-fancy
8204 @findex nnmail-split-fancy
8205 If the rather simple, standard method for specifying how to split mail
8206 doesn't allow you to do what you want, you can set
8207 @code{nnmail-split-methods} to @code{nnmail-split-fancy}. Then you can
8208 play with the @code{nnmail-split-fancy} variable.
8210 Let's look at an example value of this variable first:
8213 ;; Messages from the mailer daemon are not crossposted to any of
8214 ;; the ordinary groups. Warnings are put in a separate group
8215 ;; from real errors.
8216 (| ("from" mail (| ("subject" "warn.*" "mail.warning")
8218 ;; Non-error messages are crossposted to all relevant
8219 ;; groups, but we don't crosspost between the group for the
8220 ;; (ding) list and the group for other (ding) related mail.
8221 (& (| (any "ding@@ifi\\.uio\\.no" "ding.list")
8222 ("subject" "ding" "ding.misc"))
8223 ;; Other mailing lists...
8224 (any "procmail@@informatik\\.rwth-aachen\\.de" "procmail.list")
8225 (any "SmartList@@informatik\\.rwth-aachen\\.de" "SmartList.list")
8227 (any "larsi@@ifi\\.uio\\.no" "people.Lars Magne Ingebrigtsen"))
8228 ;; Unmatched mail goes to the catch all group.
8232 This variable has the format of a @dfn{split}. A split is a (possibly)
8233 recursive structure where each split may contain other splits. Here are
8234 the five possible split syntaxes:
8239 @samp{group}: If the split is a string, that will be taken as a group name.
8242 @code{(FIELD VALUE SPLIT)}: If the split is a list, and the first
8243 element is a string, then that means that if header FIELD (a regexp)
8244 contains VALUE (also a regexp), then store the message as specified by
8248 @code{(| SPLIT...)}: If the split is a list, and the first element is
8249 @code{|} (vertical bar), then process each SPLIT until one of them
8250 matches. A SPLIT is said to match if it will cause the mail message to
8251 be stored in one or more groups.
8254 @code{(& SPLIT...)}: If the split is a list, and the first element is
8255 @code{&}, then process all SPLITs in the list.
8258 @code{junk}: If the split is the symbol @code{junk}, then don't save
8259 this message anywhere.
8263 In these splits, FIELD must match a complete field name. VALUE must
8264 match a complete word according to the fundamental mode syntax table.
8265 You can use @code{.*} in the regexps to match partial field names or
8268 @vindex nnmail-split-abbrev-alist
8269 FIELD and VALUE can also be lisp symbols, in that case they are expanded
8270 as specified by the variable @code{nnmail-split-abbrev-alist}. This is
8271 an alist of cons cells, where the car of the cells contains the key, and
8272 the cdr contains a string.
8274 @vindex nnmail-split-fancy-syntax-table
8275 @code{nnmail-split-fancy-syntax-table} is the syntax table in effect
8276 when all this splitting is performed.
8279 @node Mail and Procmail
8280 @subsection Mail and Procmail
8285 Many people use @code{procmail} (or some other mail filter program or
8286 external delivery agent---@code{slocal}, @code{elm}, etc) to split
8287 incoming mail into groups. If you do that, you should set
8288 @code{nnmail-spool-file} to @code{procmail} to ensure that the mail
8289 backends never ever try to fetch mail by themselves.
8291 This also means that you probably don't want to set
8292 @code{nnmail-split-methods} either, which has some, perhaps, unexpected
8295 When a mail backend is queried for what groups it carries, it replies
8296 with the contents of that variable, along with any groups it has figured
8297 out that it carries by other means. None of the backends (except
8298 @code{nnmh}) actually go out to the disk and check what groups actually
8299 exist. (It's not trivial to distinguish between what the user thinks is
8300 a basis for a newsgroup and what is just a plain old file or directory.)
8302 This means that you have to tell Gnus (and the backends) what groups
8305 Let's take the @code{nnmh} backend as an example.
8307 The folders are located in @code{nnmh-directory}, say, @file{~/Mail/}.
8308 There are three folders, @file{foo}, @file{bar} and @file{mail.baz}.
8310 Go to the group buffer and type @kbd{G m}. When prompted, answer
8311 @samp{foo} for the name and @samp{nnmh} for the method. Repeat
8312 twice for the two other groups, @samp{bar} and @samp{mail.baz}. Be sure
8313 to include all your mail groups.
8315 That's it. You are now set to read your mail. An active file for this
8316 method will be created automatically.
8318 @vindex nnmail-procmail-suffix
8319 @vindex nnmail-procmail-directory
8320 If you use @code{nnfolder} or any other backend that store more than a
8321 single article in each file, you should never have procmail add mails to
8322 the file that Gnus sees. Instead, procmail should put all incoming mail
8323 in @code{nnmail-procmail-directory}. To arrive at the file name to put
8324 the incoming mail in, append @code{nnmail-procmail-suffix} to the group
8325 name. The mail backends will read the mail from these files.
8327 @vindex nnmail-resplit-incoming
8328 When Gnus reads a file called @file{mail.misc.spool}, this mail will be
8329 put in the @code{mail.misc}, as one would expect. However, if you want
8330 Gnus to split the mail the normal way, you could set
8331 @code{nnmail-resplit-incoming} to @code{t}.
8333 @vindex nnmail-keep-last-article
8334 If you use @code{procmail} to split things directory into an @code{nnmh}
8335 directory (which you shouldn't do), you should set
8336 @code{nnmail-keep-last-article} to non-@code{nil} to prevent Gnus from
8337 ever expiring the final article in a mail newsgroup. This is quite,
8341 @node Incorporating Old Mail
8342 @subsection Incorporating Old Mail
8344 Most people have lots of old mail stored in various file formats. If
8345 you have set up Gnus to read mail using one of the spiffy Gnus mail
8346 backends, you'll probably wish to have that old mail incorporated into
8349 Doing so can be quite easy.
8351 To take an example: You're reading mail using @code{nnml}
8352 (@pxref{Mail Spool}), and have set @code{nnmail-split-methods} to a
8353 satisfactory value (@pxref{Splitting Mail}). You have an old Unix mbox
8354 file filled with important, but old, mail. You want to move it into
8355 your @code{nnml} groups.
8361 Go to the group buffer.
8364 Type `G f' and give the path of the mbox file when prompted to create an
8365 @code{nndoc} group from the mbox file (@pxref{Foreign Groups}).
8368 Type `SPACE' to enter the newly created group.
8371 Type `M P b' to process-mark all articles in this group (@pxref{Setting
8375 Type `B r' to respool all the process-marked articles, and answer
8376 @samp{nnml} when prompted (@pxref{Mail Group Commands}).
8379 All the mail messages in the mbox file will now also be spread out over
8380 all your @code{nnml} groups. Try entering them and check whether things
8381 have gone without a glitch. If things look ok, you may consider
8382 deleting the mbox file, but I wouldn't do that unless I was absolutely
8383 sure that all the mail has ended up where it should be.
8385 Respooling is also a handy thing to do if you're switching from one mail
8386 backend to another. Just respool all the mail in the old mail groups
8387 using the new mail backend.
8391 @subsection Expiring Mail
8392 @cindex article expiry
8394 Traditional mail readers have a tendency to remove mail articles when
8395 you mark them as read, in some way. Gnus takes a fundamentally
8396 different approach to mail reading.
8398 Gnus basically considers mail just to be news that has been received in
8399 a rather peculiar manner. It does not think that it has the power to
8400 actually change the mail, or delete any mail messages. If you enter a
8401 mail group, and mark articles as ``read'', or kill them in some other
8402 fashion, the mail articles will still exist on the system. I repeat:
8403 Gnus will not delete your old, read mail. Unless you ask it to, of
8406 To make Gnus get rid of your unwanted mail, you have to mark the
8407 articles as @dfn{expirable}. This does not mean that the articles will
8408 disappear right away, however. In general, a mail article will be
8409 deleted from your system if, 1) it is marked as expirable, AND 2) it is
8410 more than one week old. If you do not mark an article as expirable, it
8411 will remain on your system until hell freezes over. This bears
8412 repeating one more time, with some spurious capitalizations: IF you do
8413 NOT mark articles as EXPIRABLE, Gnus will NEVER delete those ARTICLES.
8415 @vindex gnus-auto-expirable-newsgroups
8416 You do not have to mark articles as expirable by hand. Groups that
8417 match the regular expression @code{gnus-auto-expirable-newsgroups} will
8418 have all articles that you read marked as expirable automatically. All
8419 articles that are marked as expirable have an @samp{E} in the first
8420 column in the summary buffer.
8422 Let's say you subscribe to a couple of mailing lists, and you want the
8423 articles you have read to disappear after a while:
8426 (setq gnus-auto-expirable-newsgroups
8427 "mail.nonsense-list\\|mail.nice-list")
8430 Another way to have auto-expiry happen is to have the element
8431 @code{auto-expire} in the group parameters of the group.
8433 @vindex nnmail-expiry-wait
8434 The @code{nnmail-expiry-wait} variable supplies the default time an
8435 expirable article has to live. The default is seven days.
8437 Gnus also supplies a function that lets you fine-tune how long articles
8438 are to live, based on what group they are in. Let's say you want to
8439 have one month expiry period in the @samp{mail.private} group, a one day
8440 expiry period in the @samp{mail.junk} group, and a six day expiry period
8443 @vindex nnmail-expiry-wait-function
8445 (setq nnmail-expiry-wait-function
8447 (cond ((string= group "mail.private")
8449 ((string= group "mail.junk")
8451 ((string= group "important")
8457 The group names that this function is fed are ``unadorned'' group
8458 names---no @samp{nnml:} prefixes and the like.
8460 The @code{nnmail-expiry-wait} variable and
8461 @code{nnmail-expiry-wait-function} function can be either a number (not
8462 necessarily an integer) or the symbols @code{immediate} or
8465 You can also use the @code{expiry-wait} group parameter to selectively
8466 change the expiry period (@pxref{Group Parameters}).
8468 @vindex nnmail-keep-last-article
8469 If @code{nnmail-keep-last-article} is non-@code{nil}, Gnus will never
8470 expire the final article in a mail newsgroup. This is to make life
8471 easier for procmail users.
8473 @vindex gnus-total-expirable-newsgroups
8474 By the way, that line up there about Gnus never expiring non-expirable
8475 articles is a lie. If you put @code{total-expire} in the group
8476 parameters, articles will not be marked as expirable, but all read
8477 articles will be put through the expiry process. Use with extreme
8478 caution. Even more dangerous is the
8479 @code{gnus-total-expirable-newsgroups} variable. All groups that match
8480 this regexp will have all read articles put through the expiry process,
8481 which means that @emph{all} old mail articles in the groups in question
8482 will be deleted after a while. Use with extreme caution, and don't come
8483 crying to me when you discover that the regexp you used matched the
8484 wrong group and all your important mail has disappeared. Be a
8485 @emph{man}! Or a @emph{woman}! Whatever you feel more comfortable
8490 @subsection Washing Mail
8491 @cindex mail washing
8492 @cindex list server brain damage
8493 @cindex incoming mail treatment
8495 Mailers and list servers are notorious for doing all sorts of really,
8496 really stupid things with mail. ``Hey, RFC822 doesn't explicitly
8497 prohibit us from adding the string @code{wE aRe ElItE!!!!!1!!} to the
8498 end of all lines passing through our server, so let's do that!!!!1!''
8499 Yes, but RFC822 wasn't designed to be read by morons. Things that were
8500 considered to be self-evident were not discussed. So. Here we are.
8502 Case in point: The German version of Microsoft Exchange adds @samp{AW:
8503 } to the subjects of replies instead of @samp{Re: }. I could pretend to
8504 be shocked and dismayed by this, but I haven't got the energy. It is to
8507 Gnus provides a plethora of functions for washing articles while
8508 displaying them, but it might be nicer to do the filtering before
8509 storing the mail to disc. For that purpose, we have three hooks and
8510 various functions that can be put in these hooks.
8513 @item nnmail-prepare-incoming-hook
8514 @vindex nnmail-prepare-incoming-hook
8515 This hook is called before doing anything with the mail and is meant for
8516 grand, sweeping gestures. Functions to be used include:
8519 @item nnheader-ms-strip-cr
8520 @findex nnheader-ms-strip-cr
8521 Remove trailing carriage returns from each line. This is default on
8522 Emacs running on MS machines.
8526 @item nnmail-prepare-incoming-header-hook
8527 @vindex nnmail-prepare-incoming-header-hook
8528 This hook is called narrowed to each header. It can be used when
8529 cleaning up the headers. Functions that can be used include:
8532 @item nnmail-remove-leading-whitespace
8533 @findex nnmail-remove-leading-whitespace
8534 Clear leading white space that ``helpful'' listservs have added to the
8535 headers too make them look nice. Aaah.
8537 @item nnmail-remove-list-identifiers
8538 @findex nnmail-remove-list-identifiers
8539 Some list servers add an identifier---for example, @samp{(idm)}---to the
8540 beginning of all @code{Subject} headers. I'm sure that's nice for
8541 people who use stone age mail readers. This function will remove
8542 strings that match the @code{nnmail-list-identifiers} regexp, which can
8543 also be a list of regexp.
8545 For instance, if you want to remove the @samp{(idm)} and the
8546 @samp{nagnagnag} identifiers:
8549 (setq nnmail-list-identifiers
8550 '("(idm)" "nagnagnag"))
8553 @item nnmail-remove-tabs
8554 @findex nnmail-remove-tabs
8555 Translate all @samp{TAB} characters into @samp{SPACE} characters.
8559 @item nnmail-prepare-incoming-message-hook
8560 @vindex nnmail-prepare-incoming-message-hook
8561 This hook is called narrowed to each message. Functions to be used
8565 @item article-de-quoted-unreadable
8566 @findex article-de-quoted-unreadable
8567 Decode Quoted Readable encoding.
8574 @subsection Duplicates
8576 @vindex nnmail-treat-duplicates
8577 @vindex nnmail-message-id-cache-length
8578 @vindex nnmail-message-id-cache-file
8579 @cindex duplicate mails
8580 If you are a member of a couple of mailing list, you will sometime
8581 receive two copies of the same mail. This can be quite annoying, so
8582 @code{nnmail} checks for and treats any duplicates it might find. To do
8583 this, it keeps a cache of old @code{Message-ID}s---
8584 @code{nnmail-message-id-cache-file}, which is @file{~/.nnmail-cache} by
8585 default. The approximate maximum number of @code{Message-ID}s stored
8586 there is controlled by the @code{nnmail-message-id-cache-length}
8587 variable, which is 1000 by default. (So 1000 @code{Message-ID}s will be
8588 stored.) If all this sounds scary to you, you can set
8589 @code{nnmail-treat-duplicates} to @code{warn} (which is what it is by
8590 default), and @code{nnmail} won't delete duplicate mails. Instead it
8591 will generate a brand new @code{Message-ID} for the mail and insert a
8592 warning into the head of the mail saying that it thinks that this is a
8593 duplicate of a different message.
8595 This variable can also be a function. If that's the case, the function
8596 will be called from a buffer narrowed to the message in question with
8597 the @code{Message-ID} as a parameter. The function must return either
8598 @code{nil}, @code{warn}, or @code{delete}.
8600 You can turn this feature off completely by setting the variable to
8603 If you want all the duplicate mails to be put into a special
8604 @dfn{duplicates} group, you could do that using the normal mail split
8608 (setq nnmail-split-fancy
8609 '(| ;; Messages duplicates go to a separate group.
8610 ("gnus-warning" "duplication of message" "duplicate")
8611 ;; Message from daemons, postmaster, and the like to another.
8612 (any mail "mail.misc")
8619 (setq nnmail-split-methods
8620 '(("duplicates" "^Gnus-Warning:")
8625 Here's a neat feature: If you know that the recipient reads her mail
8626 with Gnus, and that she has @code{nnmail-treat-duplicates} set to
8627 @code{delete}, you can send her as many insults as you like, just by
8628 using a @code{Message-ID} of a mail that you know that she's already
8629 received. Think of all the fun! She'll never see any of it! Whee!
8632 @node Not Reading Mail
8633 @subsection Not Reading Mail
8635 If you start using any of the mail backends, they have the annoying
8636 habit of assuming that you want to read mail with them. This might not
8637 be unreasonable, but it might not be what you want.
8639 If you set @code{nnmail-spool-file} to @code{nil}, none of the backends
8640 will ever attempt to read incoming mail, which should help.
8642 @vindex nnbabyl-get-new-mail
8643 @vindex nnmbox-get-new-mail
8644 @vindex nnml-get-new-mail
8645 @vindex nnmh-get-new-mail
8646 @vindex nnfolder-get-new-mail
8647 This might be too much, if, for instance, you are reading mail quite
8648 happily with @code{nnml} and just want to peek at some old @sc{rmail}
8649 file you have stashed away with @code{nnbabyl}. All backends have
8650 variables called backend-@code{get-new-mail}. If you want to disable
8651 the @code{nnbabyl} mail reading, you edit the virtual server for the
8652 group to have a setting where @code{nnbabyl-get-new-mail} to @code{nil}.
8654 All the mail backends will call @code{nn}*@code{-prepare-save-mail-hook}
8655 narrowed to the article to be saved before saving it when reading
8659 @node Choosing a Mail Backend
8660 @subsection Choosing a Mail Backend
8662 Gnus will read the mail spool when you activate a mail group. The mail
8663 file is first copied to your home directory. What happens after that
8664 depends on what format you want to store your mail in.
8667 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
8668 * Rmail Babyl:: Emacs programs use the rmail babyl format.
8669 * Mail Spool:: Store your mail in a private spool?
8670 * MH Spool:: An mhspool-like backend.
8671 * Mail Folders:: Having one file for each group.
8676 @subsubsection Unix Mail Box
8678 @cindex unix mail box
8680 @vindex nnmbox-active-file
8681 @vindex nnmbox-mbox-file
8682 The @dfn{nnmbox} backend will use the standard Un*x mbox file to store
8683 mail. @code{nnmbox} will add extra headers to each mail article to say
8684 which group it belongs in.
8686 Virtual server settings:
8689 @item nnmbox-mbox-file
8690 @vindex nnmbox-mbox-file
8691 The name of the mail box in the user's home directory.
8693 @item nnmbox-active-file
8694 @vindex nnmbox-active-file
8695 The name of the active file for the mail box.
8697 @item nnmbox-get-new-mail
8698 @vindex nnmbox-get-new-mail
8699 If non-@code{nil}, @code{nnmbox} will read incoming mail and split it
8705 @subsubsection Rmail Babyl
8709 @vindex nnbabyl-active-file
8710 @vindex nnbabyl-mbox-file
8711 The @dfn{nnbabyl} backend will use a babyl mail box (aka. @dfn{rmail
8712 mbox}) to store mail. @code{nnbabyl} will add extra headers to each mail
8713 article to say which group it belongs in.
8715 Virtual server settings:
8718 @item nnbabyl-mbox-file
8719 @vindex nnbabyl-mbox-file
8720 The name of the rmail mbox file.
8722 @item nnbabyl-active-file
8723 @vindex nnbabyl-active-file
8724 The name of the active file for the rmail box.
8726 @item nnbabyl-get-new-mail
8727 @vindex nnbabyl-get-new-mail
8728 If non-@code{nil}, @code{nnbabyl} will read incoming mail.
8733 @subsubsection Mail Spool
8735 @cindex mail @sc{nov} spool
8737 The @dfn{nnml} spool mail format isn't compatible with any other known
8738 format. It should be used with some caution.
8740 @vindex nnml-directory
8741 If you use this backend, Gnus will split all incoming mail into files;
8742 one file for each mail, and put the articles into the correct
8743 directories under the directory specified by the @code{nnml-directory}
8744 variable. The default value is @file{~/Mail/}.
8746 You do not have to create any directories beforehand; Gnus will take
8749 If you have a strict limit as to how many files you are allowed to store
8750 in your account, you should not use this backend. As each mail gets its
8751 own file, you might very well occupy thousands of inodes within a few
8752 weeks. If this is no problem for you, and it isn't a problem for you
8753 having your friendly systems administrator walking around, madly,
8754 shouting ``Who is eating all my inodes?! Who? Who!?!'', then you should
8755 know that this is probably the fastest format to use. You do not have
8756 to trudge through a big mbox file just to read your new mail.
8758 @code{nnml} is probably the slowest backend when it comes to article
8759 splitting. It has to create lots of files, and it also generates
8760 @sc{nov} databases for the incoming mails. This makes is the fastest
8761 backend when it comes to reading mail.
8763 Virtual server settings:
8766 @item nnml-directory
8767 @vindex nnml-directory
8768 All @code{nnml} directories will be placed under this directory.
8770 @item nnml-active-file
8771 @vindex nnml-active-file
8772 The active file for the @code{nnml} server.
8774 @item nnml-newsgroups-file
8775 @vindex nnml-newsgroups-file
8776 The @code{nnml} group descriptions file. @xref{Newsgroups File
8779 @item nnml-get-new-mail
8780 @vindex nnml-get-new-mail
8781 If non-@code{nil}, @code{nnml} will read incoming mail.
8783 @item nnml-nov-is-evil
8784 @vindex nnml-nov-is-evil
8785 If non-@code{nil}, this backend will ignore any @sc{nov} files.
8787 @item nnml-nov-file-name
8788 @vindex nnml-nov-file-name
8789 The name of the @sc{nov} files. The default is @file{.overview}.
8791 @item nnml-prepare-save-mail-hook
8792 @vindex nnml-prepare-save-mail-hook
8793 Hook run narrowed to an article before saving.
8797 @findex nnml-generate-nov-databases
8798 If your @code{nnml} groups and @sc{nov} files get totally out of whack,
8799 you can do a complete update by typing @kbd{M-x
8800 nnml-generate-nov-databases}. This command will trawl through the
8801 entire @code{nnml} hierarchy, looking at each and every article, so it
8802 might take a while to complete.
8806 @subsubsection MH Spool
8808 @cindex mh-e mail spool
8810 @code{nnmh} is just like @code{nnml}, except that is doesn't generate
8811 @sc{nov} databases and it doesn't keep an active file. This makes
8812 @code{nnmh} a @emph{much} slower backend than @code{nnml}, but it also
8813 makes it easier to write procmail scripts for.
8815 Virtual server settings:
8818 @item nnmh-directory
8819 @vindex nnmh-directory
8820 All @code{nnmh} directories will be located under this directory.
8822 @item nnmh-get-new-mail
8823 @vindex nnmh-get-new-mail
8824 If non-@code{nil}, @code{nnmh} will read incoming mail.
8827 @vindex nnmh-be-safe
8828 If non-@code{nil}, @code{nnmh} will go to ridiculous lengths to make
8829 sure that the articles in the folder are actually what Gnus thinks they
8830 are. It will check date stamps and stat everything in sight, so
8831 setting this to @code{t} will mean a serious slow-down. If you never
8832 use anything but Gnus to read the @code{nnmh} articles, you do not have
8833 to set this variable to @code{t}.
8838 @subsubsection Mail Folders
8840 @cindex mbox folders
8841 @cindex mail folders
8843 @code{nnfolder} is a backend for storing each mail group in a separate
8844 file. Each file is in the standard Un*x mbox format. @code{nnfolder}
8845 will add extra headers to keep track of article numbers and arrival
8848 Virtual server settings:
8851 @item nnfolder-directory
8852 @vindex nnfolder-directory
8853 All the @code{nnfolder} mail boxes will be stored under this directory.
8855 @item nnfolder-active-file
8856 @vindex nnfolder-active-file
8857 The name of the active file.
8859 @item nnfolder-newsgroups-file
8860 @vindex nnfolder-newsgroups-file
8861 The name of the group descriptions file. @xref{Newsgroups File Format}.
8863 @item nnfolder-get-new-mail
8864 @vindex nnfolder-get-new-mail
8865 If non-@code{nil}, @code{nnfolder} will read incoming mail.
8868 @findex nnfolder-generate-active-file
8869 @kindex M-x nnfolder-generate-active-file
8870 If you have lots of @code{nnfolder}-like files you'd like to read with
8871 @code{nnfolder}, you can use the @kbd{M-x nnfolder-generate-active-file}
8872 command to make @code{nnfolder} aware of all likely files in
8873 @code{nnfolder-directory}.
8877 @section Other Sources
8879 Gnus can do more than just read news or mail. The methods described
8880 below allow Gnus to view directories and files as if they were
8884 * Directory Groups:: You can read a directory as if it was a newsgroup.
8885 * Anything Groups:: Dired? Who needs dired?
8886 * Document Groups:: Single files can be the basis of a group.
8887 * SOUP:: Reading @sc{SOUP} packets ``offline''.
8888 * Web Searches:: Creating groups from articles that match a string.
8889 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
8893 @node Directory Groups
8894 @subsection Directory Groups
8896 @cindex directory groups
8898 If you have a directory that has lots of articles in separate files in
8899 it, you might treat it as a newsgroup. The files have to have numerical
8902 This might be an opportune moment to mention @code{ange-ftp}, that most
8903 wonderful of all wonderful Emacs packages. When I wrote @code{nndir}, I
8904 didn't think much about it---a backend to read directories. Big deal.
8906 @code{ange-ftp} changes that picture dramatically. For instance, if you
8907 enter @file{"/ftp.hpc.uh.edu:/pub/emacs/ding-list/"} as the the
8908 directory name, ange-ftp will actually allow you to read this directory
8909 over at @samp{sina} as a newsgroup. Distributed news ahoy!
8911 @code{nndir} will use @sc{nov} files if they are present.
8913 @code{nndir} is a ``read-only'' backend---you can't delete or expire
8914 articles with this method. You can use @code{nnmh} or @code{nnml} for
8915 whatever you use @code{nndir} for, so you could switch to any of those
8916 methods if you feel the need to have a non-read-only @code{nndir}.
8919 @node Anything Groups
8920 @subsection Anything Groups
8923 From the @code{nndir} backend (which reads a single spool-like
8924 directory), it's just a hop and a skip to @code{nneething}, which
8925 pretends that any arbitrary directory is a newsgroup. Strange, but
8928 When @code{nneething} is presented with a directory, it will scan this
8929 directory and assign article numbers to each file. When you enter such
8930 a group, @code{nneething} must create ``headers'' that Gnus can use.
8931 After all, Gnus is a newsreader, in case you're
8932 forgetting. @code{nneething} does this in a two-step process. First, it
8933 snoops each file in question. If the file looks like an article (i.e.,
8934 the first few lines look like headers), it will use this as the head.
8935 If this is just some arbitrary file without a head (eg. a C source
8936 file), @code{nneething} will cobble up a header out of thin air. It
8937 will use file ownership, name and date and do whatever it can with these
8940 All this should happen automatically for you, and you will be presented
8941 with something that looks very much like a newsgroup. Totally like a
8942 newsgroup, to be precise. If you select an article, it will be displayed
8943 in the article buffer, just as usual.
8945 If you select a line that represents a directory, Gnus will pop you into
8946 a new summary buffer for this @code{nneething} group. And so on. You can
8947 traverse the entire disk this way, if you feel like, but remember that
8948 Gnus is not dired, really, and does not intend to be, either.
8950 There are two overall modes to this action---ephemeral or solid. When
8951 doing the ephemeral thing (i.e., @kbd{G D} from the group buffer), Gnus
8952 will not store information on what files you have read, and what files
8953 are new, and so on. If you create a solid @code{nneething} group the
8954 normal way with @kbd{G m}, Gnus will store a mapping table between
8955 article numbers and file names, and you can treat this group like any
8956 other groups. When you activate a solid @code{nneething} group, you will
8957 be told how many unread articles it contains, etc., etc.
8962 @item nneething-map-file-directory
8963 @vindex nneething-map-file-directory
8964 All the mapping files for solid @code{nneething} groups will be stored
8965 in this directory, which defaults to @file{~/.nneething/}.
8967 @item nneething-exclude-files
8968 @vindex nneething-exclude-files
8969 All files that match this regexp will be ignored. Nice to use to exclude
8970 auto-save files and the like, which is what it does by default.
8972 @item nneething-map-file
8973 @vindex nneething-map-file
8974 Name of the map files.
8978 @node Document Groups
8979 @subsection Document Groups
8981 @cindex documentation group
8984 @code{nndoc} is a cute little thing that will let you read a single file
8985 as a newsgroup. Several files types are supported:
8992 The babyl (rmail) mail box.
8997 The standard Unix mbox file.
8999 @cindex MMDF mail box
9001 The MMDF mail box format.
9004 Several news articles appended into a file.
9007 @cindex rnews batch files
9008 The rnews batch transport format.
9009 @cindex forwarded messages
9018 @cindex RFC 1153 digest
9019 @cindex RFC 341 digest
9020 MIME (RFC 1341) digest format.
9022 @item standard-digest
9023 The standard (RFC 1153) digest format.
9026 Non-standard digest format---matches most things, but does it badly.
9029 You can also use the special ``file type'' @code{guess}, which means
9030 that @code{nndoc} will try to guess what file type it is looking at.
9031 @code{digest} means that @code{nndoc} should guess what digest type the
9034 @code{nndoc} will not try to change the file or insert any extra headers into
9035 it---it will simply, like, let you use the file as the basis for a
9036 group. And that's it.
9038 If you have some old archived articles that you want to insert into your
9039 new & spiffy Gnus mail backend, @code{nndoc} can probably help you with
9040 that. Say you have an old @file{RMAIL} file with mail that you now want
9041 to split into your new @code{nnml} groups. You look at that file using
9042 @code{nndoc} (using the @kbd{G f} command in the group buffer
9043 (@pxref{Foreign Groups})), set the process mark on all the articles in
9044 the buffer (@kbd{M P b}, for instance), and then re-spool (@kbd{B r})
9045 using @code{nnml}. If all goes well, all the mail in the @file{RMAIL}
9046 file is now also stored in lots of @code{nnml} directories, and you can
9047 delete that pesky @file{RMAIL} file. If you have the guts!
9049 Virtual server variables:
9052 @item nndoc-article-type
9053 @vindex nndoc-article-type
9054 This should be one of @code{mbox}, @code{babyl}, @code{digest},
9055 @code{mmdf}, @code{forward}, @code{news}, @code{rnews},
9056 @code{mime-digest}, @code{clari-briefs}, or @code{guess}.
9058 @item nndoc-post-type
9059 @vindex nndoc-post-type
9060 This variable says whether Gnus is to consider the group a news group or
9061 a mail group. There are two legal values: @code{mail} (the default)
9066 * Document Server Internals:: How to add your own document types.
9070 @node Document Server Internals
9071 @subsubsection Document Server Internals
9073 Adding new document types to be recognized by @code{nndoc} isn't
9074 difficult. You just have to whip up a definition of what the document
9075 looks like, write a predicate function to recognize that document type,
9076 and then hook into @code{nndoc}.
9078 First, here's an example document type definition:
9082 (article-begin . "^\^A\^A\^A\^A\n")
9083 (body-end . "^\^A\^A\^A\^A\n"))
9086 The definition is simply a unique @dfn{name} followed by a series of
9087 regexp pseudo-variable settings. Below are the possible
9088 variables---don't be daunted by the number of variables; most document
9089 types can be defined with very few settings:
9093 If present, @code{nndoc} will skip past all text until it finds
9094 something that match this regexp. All text before this will be
9098 This setting has to be present in all document type definitions. It
9099 says what the beginning of each article looks like.
9101 @item head-begin-function
9102 If present, this should be a function that moves point to the head of
9105 @item nndoc-head-begin
9106 If present, this should be a regexp that matches the head of the
9109 @item nndoc-head-end
9110 This should match the end of the head of the article. It defaults to
9111 @samp{"^$"}---the empty line.
9113 @item body-begin-function
9114 If present, this function should move point to the beginning of the body
9118 This should match the beginning of the body of the article. It defaults
9121 @item body-end-function
9122 If present, this function should move point to the end of the body of
9126 If present, this should match the end of the body of the article.
9128 @item nndoc-file-end
9129 If present, this should match the end of the file. All text after this
9130 regexp will be totally ignored.
9134 So, using these variables @code{nndoc} is able to dissect a document
9135 file into a series of articles, each with a head and a body. However, a
9136 few more variables are needed since not all document types are all that
9137 news-like---variables needed to transform the head or the body into
9138 something that's palatable for Gnus:
9141 @item prepare-body-function
9142 If present, this function will be called when requesting an article. It
9143 will be called with point at the start of the body, and is useful if the
9144 document has encoded some parts of its contents.
9146 @item article-transform-function
9147 If present, this function is called when requesting an article. It's
9148 meant to be used how more wide-ranging transformation of both head and
9149 body of the article.
9151 @item generate-head-function
9152 If present, this function is called to generate a head that Gnus can
9153 understand. It is called with the article number as a parameter, and is
9154 expected to generate a nice head for the article in question. It is
9155 called when requesting the headers of all articles.
9159 Let's look at the most complicated example I can come up with---standard
9164 (first-article . ,(concat "^" (make-string 70 ?-) "\n\n+"))
9165 (article-begin . ,(concat "\n\n" (make-string 30 ?-) "\n\n+"))
9166 (prepare-body-function . nndoc-unquote-dashes)
9167 (body-end-function . nndoc-digest-body-end)
9169 (body-begin . "^ ?\n")
9170 (file-end . "^End of .*digest.*[0-9].*\n\\*\\*\\|^End of.*Digest *$")
9171 (subtype digest guess))
9174 We see that all text before a 70-width line of dashes is ignored; all
9175 text after a line that starts with that @samp{^End of} is also ignored;
9176 each article begins with a 30-width line of dashes; the line separating
9177 the head from the body may contain a single spcae; and that the body is
9178 run through @code{nndoc-unquote-dashes} before being delivered.
9180 To hook your own document definition into @code{nndoc}, use the
9181 @code{nndoc-add-type} function. It takes two parameters---the first is
9182 the definition itself and the second (optional) parameter says where in
9183 the document type definition alist to put this definition. The alist is
9184 traversed sequentially, and @code{nndoc-TYPE-type-p} is called for each
9185 type. So @code{nndoc-mmdf-type-p} is called to see whether a document
9186 is of @code{mmdf} type, and so on. These type predicates should return
9187 @code{nil} if the document is not of the correct type; @code{t} if it is
9188 of the correct type; and a number if the document might be of the
9189 correct type. A high number means high probability; a low number means
9190 low probability with @samp{0} being the lowest legal number.
9198 In the PC world people often talk about ``offline'' newsreaders. These
9199 are thingies that are combined reader/news transport monstrosities.
9200 With built-in modem programs. Yecchh!
9202 Of course, us Unix Weenie types of human beans use things like
9203 @code{uucp} and, like, @code{nntpd} and set up proper news and mail
9204 transport things like Ghod intended. And then we just use normal
9207 However, it can sometimes be convenient to do something a that's a bit
9208 easier on the brain if you have a very slow modem, and you're not really
9209 that interested in doing things properly.
9211 A file format called @sc{soup} has been developed for transporting news
9212 and mail from servers to home machines and back again. It can be a bit
9218 You log in on the server and create a @sc{soup} packet. You can either
9219 use a dedicated @sc{soup} thingie, or you can use Gnus to create the
9220 packet with the @kbd{O s} command.
9223 You transfer the packet home. Rail, boat, car or modem will do fine.
9226 You put the packet in your home directory.
9229 You fire up Gnus using the @code{nnsoup} backend as the native server.
9232 You read articles and mail and answer and followup to the things you
9236 You do the @kbd{G s r} command to pack these replies into a @sc{soup}
9240 You transfer this packet to the server.
9243 You use Gnus to mail this packet out with the @kbd{G s s} command.
9246 You then repeat until you die.
9250 So you basically have a bipartite system---you use @code{nnsoup} for
9251 reading and Gnus for packing/sending these @sc{soup} packets.
9254 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
9255 * SOUP Groups:: A backend for reading @sc{soup} packets.
9256 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
9261 @subsubsection SOUP Commands
9265 @kindex G s b (Group)
9266 @findex gnus-group-brew-soup
9267 Pack all unread articles in the current group
9268 (@code{gnus-group-brew-soup}). This command understands the
9269 process/prefix convention.
9272 @kindex G s w (Group)
9273 @findex gnus-soup-save-areas
9274 Save all data files (@code{gnus-soup-save-areas}).
9277 @kindex G s s (Group)
9278 @findex gnus-soup-send-replies
9279 Send all replies from the replies packet
9280 (@code{gnus-soup-send-replies}).
9283 @kindex G s p (Group)
9284 @findex gnus-soup-pack-packet
9285 Pack all files into a @sc{soup} packet (@code{gnus-soup-pack-packet}).
9288 @kindex G s r (Group)
9289 @findex nnsoup-pack-replies
9290 Pack all replies into a replies packet (@code{nnsoup-pack-replies}).
9293 @kindex O s (Summary)
9294 @findex gnus-soup-add-article
9295 This summary-mode command adds the current article to a @sc{soup} packet
9296 (@code{gnus-soup-add-article}). It understands the process/prefix
9302 There are a few variables to customize where Gnus will put all these
9307 @item gnus-soup-directory
9308 @vindex gnus-soup-directory
9309 Directory where Gnus will save intermediate files while composing
9310 @sc{soup} packets. The default is @file{~/SoupBrew/}.
9312 @item gnus-soup-replies-directory
9313 @vindex gnus-soup-replies-directory
9314 This is what Gnus will use as a temporary directory while sending our
9315 reply packets. The default is @file{~/SoupBrew/SoupReplies/}.
9317 @item gnus-soup-prefix-file
9318 @vindex gnus-soup-prefix-file
9319 Name of the file where Gnus stores the last used prefix. The default is
9322 @item gnus-soup-packer
9323 @vindex gnus-soup-packer
9324 A format string command for packing a @sc{soup} packet. The default is
9325 @samp{tar cf - %s | gzip > $HOME/Soupout%d.tgz}.
9327 @item gnus-soup-unpacker
9328 @vindex gnus-soup-unpacker
9329 Format string command for unpacking a @sc{soup} packet. The default is
9330 @samp{gunzip -c %s | tar xvf -}.
9332 @item gnus-soup-packet-directory
9333 @vindex gnus-soup-packet-directory
9334 Where Gnus will look for reply packets. The default is @file{~/}.
9336 @item gnus-soup-packet-regexp
9337 @vindex gnus-soup-packet-regexp
9338 Regular expression matching @sc{soup} reply packets in
9339 @code{gnus-soup-packet-directory}.
9345 @subsubsection @sc{soup} Groups
9348 @code{nnsoup} is the backend for reading @sc{soup} packets. It will
9349 read incoming packets, unpack them, and put them in a directory where
9350 you can read them at leisure.
9352 These are the variables you can use to customize its behavior:
9356 @item nnsoup-tmp-directory
9357 @vindex nnsoup-tmp-directory
9358 When @code{nnsoup} unpacks a @sc{soup} packet, it does it in this
9359 directory. (@file{/tmp/} by default.)
9361 @item nnsoup-directory
9362 @vindex nnsoup-directory
9363 @code{nnsoup} then moves each message and index file to this directory.
9364 The default is @file{~/SOUP/}.
9366 @item nnsoup-replies-directory
9367 @vindex nnsoup-replies-directory
9368 All replies will stored in this directory before being packed into a
9369 reply packet. The default is @file{~/SOUP/replies/"}.
9371 @item nnsoup-replies-format-type
9372 @vindex nnsoup-replies-format-type
9373 The @sc{soup} format of the replies packets. The default is @samp{?n}
9374 (rnews), and I don't think you should touch that variable. I probably
9375 shouldn't even have documented it. Drats! Too late!
9377 @item nnsoup-replies-index-type
9378 @vindex nnsoup-replies-index-type
9379 The index type of the replies packet. The is @samp{?n}, which means
9380 ``none''. Don't fiddle with this one either!
9382 @item nnsoup-active-file
9383 @vindex nnsoup-active-file
9384 Where @code{nnsoup} stores lots of information. This is not an ``active
9385 file'' in the @code{nntp} sense; it's an Emacs Lisp file. If you lose
9386 this file or mess it up in any way, you're dead. The default is
9387 @file{~/SOUP/active}.
9390 @vindex nnsoup-packer
9391 Format string command for packing a reply @sc{soup} packet. The default
9392 is @samp{tar cf - %s | gzip > $HOME/Soupin%d.tgz}.
9394 @item nnsoup-unpacker
9395 @vindex nnsoup-unpacker
9396 Format string command for unpacking incoming @sc{soup} packets. The
9397 default is @samp{gunzip -c %s | tar xvf -}.
9399 @item nnsoup-packet-directory
9400 @vindex nnsoup-packet-directory
9401 Where @code{nnsoup} will look for incoming packets. The default is
9404 @item nnsoup-packet-regexp
9405 @vindex nnsoup-packet-regexp
9406 Regular expression matching incoming @sc{soup} packets. The default is
9413 @subsubsection SOUP Replies
9415 Just using @code{nnsoup} won't mean that your postings and mailings end
9416 up in @sc{soup} reply packets automagically. You have to work a bit
9417 more for that to happen.
9419 @findex nnsoup-set-variables
9420 The @code{nnsoup-set-variables} command will set the appropriate
9421 variables to ensure that all your followups and replies end up in the
9424 In specific, this is what it does:
9427 (setq message-send-news-function 'nnsoup-request-post)
9428 (setq message-send-mail-function 'nnsoup-request-mail)
9431 And that's it, really. If you only want news to go into the @sc{soup}
9432 system you just use the first line. If you only want mail to be
9433 @sc{soup}ed you use the second.
9437 @subsection Web Searches
9442 @cindex Usenet searches
9443 @cindex searching the Usenet
9445 It's, like, too neat to search the Usenet for articles that match a
9446 string, but it, like, totally @emph{sucks}, like, totally, to use one of
9447 those, like, Web browsers, and you, like, have to, rilly, like, look at
9448 the commercials, so, like, with Gnus you can do @emph{rad}, rilly,
9449 searches without having to use a browser.
9451 The @code{nnweb} backend allows an easy interface to the mighty search
9452 engine. You create an @code{nnweb} group, enter a search pattern, and
9453 then enter the group and read the articles like you would any normal
9454 group. The @kbd{G n} command in the group buffer (@pxref{Foreign
9455 Groups}) will do this in an easy-to-use fashion.
9457 @code{nnweb} groups don't really lend themselves to being solid
9458 groups---they have a very fleeting idea of article numbers. In fact,
9459 each time you enter an @code{nnweb} group (not even changing the search
9460 pattern), you are likely to get the articles ordered in a different
9461 manner. Not even using duplicate suppression (@code{Duplicate
9462 Suppression}) will help, since @code{nnweb} doesn't even know the
9463 @code{Message-ID} of the articles before reading them using some search
9464 engines (DejaNews, for instance). The only possible way to keep track
9465 of which articles you've read is by scoring on the @code{Date}
9466 header---mark all articles that were posted before the last date you
9467 read the group as read.
9469 If the search engine changes its output substantially, @code{nnweb}
9470 won't be able to parse it and will fail. One could hardly fault the Web
9471 providers if they were to do this---their @emph{raison d'être} is to
9472 make money off of advertisements, not to provide services to the
9473 community. Since @code{nnweb} washes the ads off all the articles, one
9474 might think that the providers might be somewhat miffed. We'll see.
9476 You must have the @code{url} and @code{w3} package installed to be able
9477 to use @code{nnweb}.
9479 Virtual server variables:
9484 What search engine type is being used. The currently supported types
9485 are @code{dejanews}, @code{altavista} and @code{reference}.
9488 @vindex nnweb-search
9489 The search string to feed to the search engine.
9491 @item nnweb-max-hits
9492 @vindex nnweb-max-hits
9493 Advisory maximum number of hits per search to display. The default is
9496 @item nnweb-type-definition
9497 @vindex nnweb-type-definition
9498 Type-to-definition alist. This alist says what @code{nnweb} should do
9499 with the various search engine types. The following elements must be
9504 Function to decode the article and provide something that Gnus
9508 Function to create an article number to message header and URL alist.
9511 Function to send the search string to the search engine.
9514 The address the aforementioned function should send the search string
9518 Format string URL to fetch an article by @code{Message-ID}.
9525 @node Mail-To-News Gateways
9526 @subsection Mail-To-News Gateways
9527 @cindex mail-to-news gateways
9530 If your local @code{nntp} server doesn't allow posting, for some reason
9531 or other, you can post using one of the numerous mail-to-news gateways.
9532 The @code{nngateway} backend provides the interface.
9534 Note that you can't read anything from this backend---it can only be
9540 @item nngateway-address
9541 @vindex nngateway-address
9542 This is the address of the mail-to-news gateway.
9544 @item nngateway-header-transformation
9545 @vindex nngateway-header-transformation
9546 News headers have often have to be transformed in some odd way or other
9547 for the mail-to-news gateway to accept it. This variable says what
9548 transformation should be called, and defaults to
9549 @code{nngateway-simple-header-transformation}. The function is called
9550 narrowed to the headers to be transformed and with one parameter---the
9553 This default function just inserts a new @code{To} header based on the
9554 @code{Newsgroups} header and the gateway address---an article with this
9555 @code{Newsgroups} header:
9558 Newsgroups: alt.religion.emacs
9561 will get this @code{From} header inserted:
9564 To: alt-religion-emacs@@GATEWAY
9569 So, to use this, simply say something like:
9572 (setq gnus-post-method '(nngateway "GATEWAY.ADDRESS"))
9576 @node Combined Groups
9577 @section Combined Groups
9579 Gnus allows combining a mixture of all the other group types into bigger
9583 * Virtual Groups:: Combining articles from many groups.
9584 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
9588 @node Virtual Groups
9589 @subsection Virtual Groups
9591 @cindex virtual groups
9593 An @dfn{nnvirtual group} is really nothing more than a collection of
9596 For instance, if you are tired of reading many small group, you can
9597 put them all in one big group, and then grow tired of reading one
9598 big, unwieldy group. The joys of computing!
9600 You specify @code{nnvirtual} as the method. The address should be a
9601 regexp to match component groups.
9603 All marks in the virtual group will stick to the articles in the
9604 component groups. So if you tick an article in a virtual group, the
9605 article will also be ticked in the component group from whence it came.
9606 (And vice versa---marks from the component groups will also be shown in
9609 Here's an example @code{nnvirtual} method that collects all Andrea Dworkin
9610 newsgroups into one, big, happy newsgroup:
9613 (nnvirtual "^alt\\.fan\\.andrea-dworkin$\\|^rec\\.dworkin.*")
9616 The component groups can be native or foreign; everything should work
9617 smoothly, but if your computer explodes, it was probably my fault.
9619 Collecting the same group from several servers might actually be a good
9620 idea if users have set the Distribution header to limit distribution.
9621 If you would like to read @samp{soc.motss} both from a server in Japan
9622 and a server in Norway, you could use the following as the group regexp:
9625 "^nntp+some.server.jp:soc.motss$\\|^nntp+some.server.no:soc.motss$"
9628 This should work kinda smoothly---all articles from both groups should
9629 end up in this one, and there should be no duplicates. Threading (and
9630 the rest) will still work as usual, but there might be problems with the
9631 sequence of articles. Sorting on date might be an option here
9632 (@pxref{Selecting a Group}.
9634 One limitation, however---all groups that are included in a virtual
9635 group has to be alive (i.e., subscribed or unsubscribed). Killed or
9636 zombie groups can't be component groups for @code{nnvirtual} groups.
9638 @vindex nnvirtual-always-rescan
9639 If the @code{nnvirtual-always-rescan} is non-@code{nil},
9640 @code{nnvirtual} will always scan groups for unread articles when
9641 entering a virtual group. If this variable is @code{nil} (which is the
9642 default) and you read articles in a component group after the virtual
9643 group has been activated, the read articles from the component group
9644 will show up when you enter the virtual group. You'll also see this
9645 effect if you have two virtual groups that contain the same component
9646 group. If that's the case, you should set this variable to @code{t}.
9647 Or you can just tap @code{M-g} on the virtual group every time before
9648 you enter it---it'll have much the same effect.
9651 @node Kibozed Groups
9652 @subsection Kibozed Groups
9656 @dfn{Kibozing} is defined by @sc{oed} as ``grepping through (parts of)
9657 the news feed''. @code{nnkiboze} is a backend that will do this for
9658 you. Oh joy! Now you can grind any @sc{nntp} server down to a halt
9659 with useless requests! Oh happiness!
9662 To create a kibozed group, use the @kbd{G k} command in the group
9665 The address field of the @code{nnkiboze} method is, as with
9666 @code{nnvirtual}, a regexp to match groups to be ``included'' in the
9667 @code{nnkiboze} group. There most similarities between @code{nnkiboze}
9668 and @code{nnvirtual} ends.
9670 In addition to this regexp detailing component groups, an @code{nnkiboze} group
9671 must have a score file to say what articles that are to be included in
9672 the group (@pxref{Scoring}).
9674 @kindex M-x nnkiboze-generate-groups
9675 @findex nnkiboze-generate-groups
9676 You must run @kbd{M-x nnkiboze-generate-groups} after creating the
9677 @code{nnkiboze} groups you want to have. This command will take time. Lots of
9678 time. Oodles and oodles of time. Gnus has to fetch the headers from
9679 all the articles in all the components groups and run them through the
9680 scoring process to determine if there are any articles in the groups
9681 that are to be part of the @code{nnkiboze} groups.
9683 Please limit the number of component groups by using restrictive
9684 regexps. Otherwise your sysadmin may become annoyed with you, and the
9685 @sc{nntp} site may throw you off and never let you back in again.
9686 Stranger things have happened.
9688 @code{nnkiboze} component groups do not have to be alive---they can be dead,
9689 and they can be foreign. No restrictions.
9691 @vindex nnkiboze-directory
9692 The generation of an @code{nnkiboze} group means writing two files in
9693 @code{nnkiboze-directory}, which is @file{~/News/} by default. One
9694 contains the @sc{nov} header lines for all the articles in the group,
9695 and the other is an additional @file{.newsrc} file to store information
9696 on what groups that have been searched through to find component
9699 Articles that are marked as read in the @code{nnkiboze} group will have their
9700 @sc{nov} lines removed from the @sc{nov} file.
9707 Other people use @dfn{kill files}, but we here at Gnus Towers like
9708 scoring better than killing, so we'd rather switch than fight. They do
9709 something completely different as well, so sit up straight and pay
9712 @vindex gnus-summary-mark-below
9713 All articles have a default score (@code{gnus-summary-default-score}),
9714 which is 0 by default. This score may be raised or lowered either
9715 interactively or by score files. Articles that have a score lower than
9716 @code{gnus-summary-mark-below} are marked as read.
9718 Gnus will read any @dfn{score files} that apply to the current group
9719 before generating the summary buffer.
9721 There are several commands in the summary buffer that insert score
9722 entries based on the current article. You can, for instance, ask Gnus to
9723 lower or increase the score of all articles with a certain subject.
9725 There are two sorts of scoring entries: Permanent and temporary.
9726 Temporary score entries are self-expiring entries. Any entries that are
9727 temporary and have not been used for, say, a week, will be removed
9728 silently to help keep the sizes of the score files down.
9731 * Summary Score Commands:: Adding score entries for the current group.
9732 * Group Score Commands:: General score commands.
9733 * Score Variables:: Customize your scoring. (My, what terminology).
9734 * Score File Format:: What a score file may contain.
9735 * Score File Editing:: You can edit score files by hand as well.
9736 * Adaptive Scoring:: Big Sister Gnus @emph{knows} what you read.
9737 * Home Score File:: How to say where new score entries are to go.
9738 * Followups To Yourself:: Having Gnus notice when people answer you.
9739 * Scoring Tips:: How to score effectively.
9740 * Reverse Scoring:: That problem child of old is not problem.
9741 * Global Score Files:: Earth-spanning, ear-splitting score files.
9742 * Kill Files:: They are still here, but they can be ignored.
9743 * GroupLens:: Getting predictions on what you like to read.
9744 * Advanced Scoring:: Using logical expressions to build score rules.
9745 * Score Decays:: It can be useful to let scores wither away.
9749 @node Summary Score Commands
9750 @section Summary Score Commands
9751 @cindex score commands
9753 The score commands that alter score entries do not actually modify real
9754 score files. That would be too inefficient. Gnus maintains a cache of
9755 previously loaded score files, one of which is considered the
9756 @dfn{current score file alist}. The score commands simply insert
9757 entries into this list, and upon group exit, this list is saved.
9759 The current score file is by default the group's local score file, even
9760 if no such score file actually exists. To insert score commands into
9761 some other score file (eg. @file{all.SCORE}), you must first make this
9762 score file the current one.
9764 General score commands that don't actually change the score file:
9769 @kindex V s (Summary)
9770 @findex gnus-summary-set-score
9771 Set the score of the current article (@code{gnus-summary-set-score}).
9774 @kindex V S (Summary)
9775 @findex gnus-summary-current-score
9776 Display the score of the current article
9777 (@code{gnus-summary-current-score}).
9780 @kindex V t (Summary)
9781 @findex gnus-score-find-trace
9782 Display all score rules that have been used on the current article
9783 (@code{gnus-score-find-trace}).
9786 @cindex V R (Summary)
9787 @findex gnus-summary-rescore
9788 Run the current summary through the scoring process
9789 (@code{gnus-summary-rescore}). This might be useful if you're playing
9790 around with your score files behind Gnus' back and want to see the
9791 effect you're having.
9794 @kindex V a (Summary)
9795 @findex gnus-summary-score-entry
9796 Add a new score entry, and allow specifying all elements
9797 (@code{gnus-summary-score-entry}).
9800 @kindex V c (Summary)
9801 @findex gnus-score-change-score-file
9802 Make a different score file the current
9803 (@code{gnus-score-change-score-file}).
9806 @kindex V e (Summary)
9807 @findex gnus-score-edit-current-scores
9808 Edit the current score file (@code{gnus-score-edit-current-scores}).
9809 You will be popped into a @code{gnus-score-mode} buffer (@pxref{Score
9813 @kindex V f (Summary)
9814 @findex gnus-score-edit-file
9815 Edit a score file and make this score file the current one
9816 (@code{gnus-score-edit-file}).
9819 @kindex V F (Summary)
9820 @findex gnus-score-flush-cache
9821 Flush the score cahe (@code{gnus-score-flush-cache}). This is useful
9822 after editing score files.
9825 @kindex V C (Summary)
9826 @findex gnus-score-customize
9827 Customize a score file in a visually pleasing manner
9828 (@code{gnus-score-customize}).
9831 @kindex I C-i (Summary)
9832 @findex gnus-summary-raise-score
9833 Increase the score of the current article
9834 (@code{gnus-summary-raise-score}).
9837 @kindex L C-l (Summary)
9838 @findex gnus-summary-lower-score
9839 Lower the score of the current article
9840 (@code{gnus-summary-lower-score}).
9843 The rest of these commands modify the local score file.
9848 @kindex V m (Summary)
9849 @findex gnus-score-set-mark-below
9850 Prompt for a score, and mark all articles with a score below this as
9851 read (@code{gnus-score-set-mark-below}).
9854 @kindex V x (Summary)
9855 @findex gnus-score-set-expunge-below
9856 Prompt for a score, and add a score rule to the current score file to
9857 expunge all articles below this score
9858 (@code{gnus-score-set-expunge-below}).
9861 The keystrokes for actually making score entries follow a very regular
9862 pattern, so there's no need to list all the commands. (Hundreds of
9867 The first key is either @kbd{I} (upper case i) for increasing the score
9868 or @kbd{L} for lowering the score.
9870 The second key says what header you want to score on. The following
9875 Score on the author name.
9878 Score on the subject line.
9881 Score on the Xref line---i.e., the cross-posting line.
9884 Score on thread---the References line.
9890 Score on the number of lines.
9893 Score on the Message-ID.
9906 The third key is the match type. Which match types are legal depends on
9907 what headers you are scoring on.
9951 Greater than number.
9956 The fourth and final key says whether this is a temporary (i.e., expiring)
9957 score entry, or a permanent (i.e., non-expiring) score entry, or whether
9958 it is to be done immediately, without adding to the score file.
9962 Temporary score entry.
9965 Permanent score entry.
9968 Immediately scoring.
9973 So, let's say you want to increase the score on the current author with
9974 exact matching permanently: @kbd{I a e p}. If you want to lower the
9975 score based on the subject line, using substring matching, and make a
9976 temporary score entry: @kbd{L s s t}. Pretty easy.
9978 To make things a bit more complicated, there are shortcuts. If you use
9979 a capital letter on either the second or third keys, Gnus will use
9980 defaults for the remaining one or two keystrokes. The defaults are
9981 ``substring'' and ``temporary''. So @kbd{I A} is the same as @kbd{I a s
9982 t}, and @kbd{I a R} is the same as @kbd{I a r t}.
9984 @vindex gnus-score-mimic-keymap
9985 The @code{gnus-score-mimic-keymap} says whether these commands will
9986 pretend they are keymaps or not.
9989 @node Group Score Commands
9990 @section Group Score Commands
9991 @cindex group score commands
9993 There aren't many of these as yet, I'm afraid.
9999 @findex gnus-score-flush-cache
10000 Gnus maintains a cache of score alists to avoid having to reload them
10001 all the time. This command will flush the cache
10002 (@code{gnus-score-flush-cache}).
10007 @node Score Variables
10008 @section Score Variables
10009 @cindex score variables
10013 @item gnus-use-scoring
10014 @vindex gnus-use-scoring
10015 If @code{nil}, Gnus will not check for score files, and will not, in
10016 general, do any score-related work. This is @code{t} by default.
10018 @item gnus-kill-killed
10019 @vindex gnus-kill-killed
10020 If this variable is @code{nil}, Gnus will never apply score files to
10021 articles that have already been through the kill process. While this
10022 may save you lots of time, it also means that if you apply a kill file
10023 to a group, and then change the kill file and want to run it over you
10024 group again to kill more articles, it won't work. You have to set this
10025 variable to @code{t} to do that. (It is @code{t} by default.)
10027 @item gnus-kill-files-directory
10028 @vindex gnus-kill-files-directory
10029 All kill and score files will be stored in this directory, which is
10030 initialized from the @code{SAVEDIR} environment variable by default.
10031 This is @file{~/News/} by default.
10033 @item gnus-score-file-suffix
10034 @vindex gnus-score-file-suffix
10035 Suffix to add to the group name to arrive at the score file name
10036 (@samp{SCORE} by default.)
10038 @item gnus-score-uncacheable-files
10039 @vindex gnus-score-uncacheable-files
10040 @cindex score cache
10041 All score files are normally cached to avoid excessive re-loading of
10042 score files. However, if this might make you Emacs grow big and
10043 bloated, so this regexp can be used to weed out score files that are
10044 unlikely to be needed again. It would be a bad idea to deny caching of
10045 @file{all.SCORE}, while it might be a good idea to not cache
10046 @file{comp.infosystems.www.authoring.misc.ADAPT}. In fact, this
10047 variable is @samp{ADAPT$} by default, so no adaptive score files will
10050 @item gnus-save-score
10051 @vindex gnus-save-score
10052 If you have really complicated score files, and do lots of batch
10053 scoring, then you might set this variable to @code{t}. This will make
10054 Gnus save the scores into the @file{.newsrc.eld} file.
10056 @item gnus-score-interactive-default-score
10057 @vindex gnus-score-interactive-default-score
10058 Score used by all the interactive raise/lower commands to raise/lower
10059 score with. Default is 1000, which may seem excessive, but this is to
10060 ensure that the adaptive scoring scheme gets enough room to play with.
10061 We don't want the small changes from the adaptive scoring to overwrite
10062 manually entered data.
10064 @item gnus-summary-default-score
10065 @vindex gnus-summary-default-score
10066 Default score of an article, which is 0 by default.
10068 @item gnus-score-over-mark
10069 @vindex gnus-score-over-mark
10070 Mark (in the third column) used for articles with a score over the
10071 default. Default is @samp{+}.
10073 @item gnus-score-below-mark
10074 @vindex gnus-score-below-mark
10075 Mark (in the third column) used for articles with a score below the
10076 default. Default is @samp{-}.
10078 @item gnus-score-find-score-files-function
10079 @vindex gnus-score-find-score-files-function
10080 Function used to find score files for the current group. This function
10081 is called with the name of the group as the argument.
10083 Predefined functions available are:
10086 @item gnus-score-find-single
10087 @findex gnus-score-find-single
10088 Only apply the group's own score file.
10090 @item gnus-score-find-bnews
10091 @findex gnus-score-find-bnews
10092 Apply all score files that match, using bnews syntax. This is the
10093 default. For instance, if the current group is @samp{gnu.emacs.gnus},
10094 @file{all.emacs.all.SCORE}, @file{not.alt.all.SCORE} and
10095 @file{gnu.all.SCORE} would all apply. In short, the instances of
10096 @samp{all} in the score file names are translated into @samp{.*}, and
10097 then a regexp match is done.
10099 This means that if you have some score entries that you want to apply to
10100 all groups, then you put those entries in the @file{all.SCORE} file.
10102 @item gnus-score-find-hierarchical
10103 @findex gnus-score-find-hierarchical
10104 Apply all score files from all the parent groups. This means that you
10105 can't have score files like @file{all.SCORE} or @file{all.emacs.SCORE},
10106 but you can have @file{SCORE}, @file{comp.SCORE} and
10107 @file{comp.emacs.SCORE}.
10110 This variable can also be a list of functions. In that case, all these
10111 functions will be called, and all the returned lists of score files will
10112 be applied. These functions can also return lists of score alists
10113 directly. In that case, the functions that return these non-file score
10114 alists should probably be placed before the ``real'' score file
10115 functions, to ensure that the last score file returned is the local
10118 @item gnus-score-expiry-days
10119 @vindex gnus-score-expiry-days
10120 This variable says how many days should pass before an unused score file
10121 entry is expired. If this variable is @code{nil}, no score file entries
10122 are expired. It's 7 by default.
10124 @item gnus-update-score-entry-dates
10125 @vindex gnus-update-score-entry-dates
10126 If this variable is non-@code{nil}, matching score entries will have
10127 their dates updated. (This is how Gnus controls expiry---all
10128 non-matching entries will become too old while matching entries will
10129 stay fresh and young.) However, if you set this variable to @code{nil},
10130 even matching entries will grow old and will have to face that oh-so
10133 @item gnus-score-after-write-file-function
10134 @vindex gnus-score-after-write-file-function
10135 Function called with the name of the score file just written.
10140 @node Score File Format
10141 @section Score File Format
10142 @cindex score file format
10144 A score file is an @code{emacs-lisp} file that normally contains just a
10145 single form. Casual users are not expected to edit these files;
10146 everything can be changed from the summary buffer.
10148 Anyway, if you'd like to dig into it yourself, here's an example:
10152 ("Lars Ingebrigtsen" -10000)
10154 ("larsi\\|lmi" -50000 nil R))
10156 ("Ding is Badd" nil 728373))
10158 ("alt.politics" -1000 728372 s))
10163 (mark-and-expunge -10)
10167 (files "/hom/larsi/News/gnu.SCORE")
10168 (exclude-files "all.SCORE")
10169 (local (gnus-newsgroup-auto-expire t)
10170 (gnus-summary-make-false-root 'empty))
10174 This example demonstrates absolutely everything about a score file.
10176 Even though this looks much like lisp code, nothing here is actually
10177 @code{eval}ed. The lisp reader is used to read this form, though, so it
10178 has to be legal syntactically, if not semantically.
10180 Six keys are supported by this alist:
10185 If the key is a string, it is the name of the header to perform the
10186 match on. Scoring can only be performed on these eight headers:
10187 @code{From}, @code{Subject}, @code{References}, @code{Message-ID},
10188 @code{Xref}, @code{Lines}, @code{Chars} and @code{Date}. In addition to
10189 these headers, there are three strings to tell Gnus to fetch the entire
10190 article and do the match on larger parts of the article: @code{Body}
10191 will perform the match on the body of the article, @code{Head} will
10192 perform the match on the head of the article, and @code{All} will
10193 perform the match on the entire article. Note that using any of these
10194 last three keys will slow down group entry @emph{considerably}. The
10195 final ``header'' you can score on is @code{Followup}. These score
10196 entries will result in new score entries being added for all follow-ups
10197 to articles that matches these score entries.
10199 Following this key is a arbitrary number of score entries, where each
10200 score entry has one to four elements.
10204 The first element is the @dfn{match element}. On most headers this will
10205 be a string, but on the Lines and Chars headers, this must be an
10209 If the second element is present, it should be a number---the @dfn{score
10210 element}. This number should be an integer in the neginf to posinf
10211 interval. This number is added to the score of the article if the match
10212 is successful. If this element is not present, the
10213 @code{gnus-score-interactive-default-score} number will be used
10214 instead. This is 1000 by default.
10217 If the third element is present, it should be a number---the @dfn{date
10218 element}. This date says when the last time this score entry matched,
10219 which provides a mechanism for expiring the score entries. It this
10220 element is not present, the score entry is permanent. The date is
10221 represented by the number of days since December 31, 1 ce.
10224 If the fourth element is present, it should be a symbol---the @dfn{type
10225 element}. This element specifies what function should be used to see
10226 whether this score entry matches the article. What match types that can
10227 be used depends on what header you wish to perform the match on.
10230 @item From, Subject, References, Xref, Message-ID
10231 For most header types, there are the @code{r} and @code{R} (regexp), as
10232 well as @code{s} and @code{S} (substring) types, and @code{e} and
10233 @code{E} (exact match), and @code{w} (word match) types. If this
10234 element is not present, Gnus will assume that substring matching should
10235 be used. @code{R}, @code{S}, and @code{E} differ from the others in
10236 that the matches will be done in a case-sensitive manner. All these
10237 one-letter types are really just abbreviations for the @code{regexp},
10238 @code{string}, @code{exact}, and @code{word} types, which you can use
10239 instead, if you feel like.
10242 These two headers use different match types: @code{<}, @code{>},
10243 @code{=}, @code{>=} and @code{<=}.
10246 For the Date header we have three kinda silly match types:
10247 @code{before}, @code{at} and @code{after}. I can't really imagine this
10248 ever being useful, but, like, it would feel kinda silly not to provide
10249 this function. Just in case. You never know. Better safe than sorry.
10250 Once burnt, twice shy. Don't judge a book by its cover. Never not have
10251 sex on a first date. (I have been told that at least one person, and I
10252 quote, ``found this function indispensable'', however.)
10254 A more useful match type is @code{regexp}. With it, you can match the
10255 date string using a regular expression. The date is normalized to
10256 ISO8601 compact format first, which looks like @samp{YYYYMMDDTHHMMSS}.
10257 If you want to match all articles that have been posted on April 1st in
10258 every year, you could use @samp{....0401.........} as a match string,
10259 for instance. (Note that the date is kept in its original time zone, so
10260 this will match articles that were posted when it was April 1st where
10261 the article was posted from. Time zones are such wholesome fun for the
10264 @item Head, Body, All
10265 These three match keys use the same match types as the @code{From} (etc)
10269 This match key will add a score entry on all articles that followup to
10270 some author. Uses the same match types as the @code{From} header uses.
10273 This match key will add a score entry on all articles that are part of
10274 a thread. Uses the same match types as the @code{References} header
10280 The value of this entry should be a number. Any articles with a score
10281 lower than this number will be marked as read.
10284 The value of this entry should be a number. Any articles with a score
10285 lower than this number will be removed from the summary buffer.
10287 @item mark-and-expunge
10288 The value of this entry should be a number. Any articles with a score
10289 lower than this number will be marked as read and removed from the
10292 @item thread-mark-and-expunge
10293 The value of this entry should be a number. All articles that belong to
10294 a thread that has a total score below this number will be marked as read
10295 and removed from the summary buffer. @code{gnus-thread-score-function}
10296 says how to compute the total score for a thread.
10299 The value of this entry should be any number of file names. These files
10300 are assumed to be score files as well, and will be loaded the same way
10303 @item exclude-files
10304 The clue of this entry should be any number of files. This files will
10305 not be loaded, even though they would normally be so, for some reason or
10309 The value of this entry will be @code{eval}el. This element will be
10310 ignored when handling global score files.
10313 Read-only score files will not be updated or saved. Global score files
10314 should feature this atom (@pxref{Global Score Files}).
10317 The value of this entry should be a number. Articles that do not have
10318 parents will get this number added to their scores. Imagine you follow
10319 some high-volume newsgroup, like @samp{comp.lang.c}. Most likely you
10320 will only follow a few of the threads, also want to see any new threads.
10322 You can do this with the following two score file entries:
10326 (mark-and-expunge -100)
10329 When you enter the group the first time, you will only see the new
10330 threads. You then raise the score of the threads that you find
10331 interesting (with @kbd{I T} or @kbd{I S}), and ignore (@kbd{C y}) the
10332 rest. Next time you enter the group, you will see new articles in the
10333 interesting threads, plus any new threads.
10335 I.e.---the orphan score atom is for high-volume groups where there
10336 exist a few interesting threads which can't be found automatically by
10337 ordinary scoring rules.
10340 This entry controls the adaptive scoring. If it is @code{t}, the
10341 default adaptive scoring rules will be used. If it is @code{ignore}, no
10342 adaptive scoring will be performed on this group. If it is a list, this
10343 list will be used as the adaptive scoring rules. If it isn't present,
10344 or is something other than @code{t} or @code{ignore}, the default
10345 adaptive scoring rules will be used. If you want to use adaptive
10346 scoring on most groups, you'd set @code{gnus-use-adaptive-scoring} to
10347 @code{t}, and insert an @code{(adapt ignore)} in the groups where you do
10348 not want adaptive scoring. If you only want adaptive scoring in a few
10349 groups, you'd set @code{gnus-use-adaptive-scoring} to @code{nil}, and
10350 insert @code{(adapt t)} in the score files of the groups where you want
10354 All adaptive score entries will go to the file named by this entry. It
10355 will also be applied when entering the group. This atom might be handy
10356 if you want to adapt on several groups at once, using the same adaptive
10357 file for a number of groups.
10360 @cindex local variables
10361 The value of this entry should be a list of @code{(VAR VALUE)} pairs.
10362 Each @var{var} will be made buffer-local to the current summary buffer,
10363 and set to the value specified. This is a convenient, if somewhat
10364 strange, way of setting variables in some groups if you don't like hooks
10369 @node Score File Editing
10370 @section Score File Editing
10372 You normally enter all scoring commands from the summary buffer, but you
10373 might feel the urge to edit them by hand as well, so we've supplied you
10374 with a mode for that.
10376 It's simply a slightly customized @code{emacs-lisp} mode, with these
10377 additional commands:
10382 @kindex C-c C-c (Score)
10383 @findex gnus-score-edit-done
10384 Save the changes you have made and return to the summary buffer
10385 (@code{gnus-score-edit-done}).
10388 @kindex C-c C-d (Score)
10389 @findex gnus-score-edit-insert-date
10390 Insert the current date in numerical format
10391 (@code{gnus-score-edit-insert-date}). This is really the day number, if
10392 you were wondering.
10395 @kindex C-c C-p (Score)
10396 @findex gnus-score-pretty-print
10397 The adaptive score files are saved in an unformatted fashion. If you
10398 intend to read one of these files, you want to @dfn{pretty print} it
10399 first. This command (@code{gnus-score-pretty-print}) does that for
10404 Type @kbd{M-x gnus-score-mode} to use this mode.
10406 @vindex gnus-score-mode-hook
10407 @code{gnus-score-menu-hook} is run in score mode buffers.
10409 In the summary buffer you can use commands like @kbd{V f} and @kbd{V
10410 e} to begin editing score files.
10413 @node Adaptive Scoring
10414 @section Adaptive Scoring
10415 @cindex adaptive scoring
10417 If all this scoring is getting you down, Gnus has a way of making it all
10418 happen automatically---as if by magic. Or rather, as if by artificial
10419 stupidity, to be precise.
10421 @vindex gnus-use-adaptive-scoring
10422 When you read an article, or mark an article as read, or kill an
10423 article, you leave marks behind. On exit from the group, Gnus can sniff
10424 these marks and add score elements depending on what marks it finds.
10425 You turn on this ability by setting @code{gnus-use-adaptive-scoring} to
10426 @code{t} or @code{(line)}. If you want score adaptively on separate
10427 words appearing in the subjects, you should set this variable to
10428 @code{(word)}. If you want to use both adaptive methods, set this
10429 variable to @code{(word line)}.
10431 @vindex gnus-default-adaptive-score-alist
10432 To give you complete control over the scoring process, you can customize
10433 the @code{gnus-default-adaptive-score-alist} variable. For instance, it
10434 might look something like this:
10437 (defvar gnus-default-adaptive-score-alist
10438 '((gnus-unread-mark)
10439 (gnus-ticked-mark (from 4))
10440 (gnus-dormant-mark (from 5))
10441 (gnus-del-mark (from -4) (subject -1))
10442 (gnus-read-mark (from 4) (subject 2))
10443 (gnus-expirable-mark (from -1) (subject -1))
10444 (gnus-killed-mark (from -1) (subject -3))
10445 (gnus-kill-file-mark)
10446 (gnus-ancient-mark)
10447 (gnus-low-score-mark)
10448 (gnus-catchup-mark (from -1) (subject -1))))
10451 As you see, each element in this alist has a mark as a key (either a
10452 variable name or a ``real'' mark---a character). Following this key is
10453 a arbitrary number of header/score pairs. If there are no header/score
10454 pairs following the key, no adaptive scoring will be done on articles
10455 that have that key as the article mark. For instance, articles with
10456 @code{gnus-unread-mark} in the example above will not get adaptive score
10459 Each article can have only one mark, so just a single of these rules
10460 will be applied to each article.
10462 To take @code{gnus-del-mark} as an example---this alist says that all
10463 articles that have that mark (i.e., are marked with @samp{D}) will have a
10464 score entry added to lower based on the @code{From} header by -4, and
10465 lowered by @code{Subject} by -1. Change this to fit your prejudices.
10467 If you have marked 10 articles with the same subject with
10468 @code{gnus-del-mark}, the rule for that mark will be applied ten times.
10469 That means that that subject will get a score of ten times -1, which
10470 should be, unless I'm much mistaken, -10.
10472 The headers you can score on are @code{from}, @code{subject},
10473 @code{message-id}, @code{references}, @code{xref}, @code{lines},
10474 @code{chars} and @code{date}. In addition, you can score on
10475 @code{followup}, which will create an adaptive score entry that matches
10476 on the @code{References} header using the @code{Message-ID} of the
10477 current article, thereby matching the following thread.
10479 You can also score on @code{thread}, which will try to score all
10480 articles that appear in a thread. @code{thread} matches uses a
10481 @code{Message-ID} to match on the @code{References} header of the
10482 article. If the match is made, the @code{Message-ID} of the article is
10483 added to the @code{thread} rule. (Think about it. I'd recommend two
10484 aspirins afterwards.)
10486 If you use this scheme, you should set the score file atom @code{mark}
10487 to something small---like -300, perhaps, to avoid having small random
10488 changes result in articles getting marked as read.
10490 After using adaptive scoring for a week or so, Gnus should start to
10491 become properly trained and enhance the authors you like best, and kill
10492 the authors you like least, without you having to say so explicitly.
10494 You can control what groups the adaptive scoring is to be performed on
10495 by using the score files (@pxref{Score File Format}). This will also
10496 let you use different rules in different groups.
10498 @vindex gnus-adaptive-file-suffix
10499 The adaptive score entries will be put into a file where the name is the
10500 group name with @code{gnus-adaptive-file-suffix} appended. The default
10503 @vindex gnus-score-exact-adapt-limit
10504 When doing adaptive scoring, substring or fuzzy matching would probably
10505 give you the best results in most cases. However, if the header one
10506 matches is short, the possibility for false positives is great, so if
10507 the length of the match is less than
10508 @code{gnus-score-exact-adapt-limit}, exact matching will be used. If
10509 this variable is @code{nil}, exact matching will always be used to avoid
10512 @vindex gnus-default-adaptive-word-score-alist
10513 As mentioned above, you can adapt either on individual words or entire
10514 headers. If you adapt on words, the
10515 @code{gnus-default-adaptive-word-score-alist} variable says what score
10516 each instance of a word should add given a mark.
10519 (setq gnus-default-adaptive-word-score-alist
10520 `((,gnus-read-mark . 30)
10521 (,gnus-catchup-mark . -10)
10522 (,gnus-killed-mark . -20)
10523 (,gnus-del-mark . -15)))
10526 This is the default value. If you have adaption on words enabled, every
10527 word that appears in subjects of articles that are marked with
10528 @code{gnus-read-mark} will result in a score rule that increase the
10529 score with 30 points.
10531 @vindex gnus-default-ignored-adaptive-words
10532 @vindex gnus-ignored-adaptive-words
10533 Words that appear in the @code{gnus-default-ignored-adaptive-words} list
10534 will be ignored. If you wish to add more words to be ignored, use the
10535 @code{gnus-ignored-adaptive-words} list instead.
10537 @vindex gnus-adaptive-word-syntax-table
10538 When the scoring is done, @code{gnus-adaptive-word-syntax-table} is the
10539 syntax table in effect. It is similar to the standard syntax table, but
10540 it considers numbers to be non-word-consituant characters.
10542 After using this scheme for a while, it might be nice to write a
10543 @code{gnus-psychoanalyze-user} command to go through the rules and see
10544 what words you like and what words you don't like. Or perhaps not.
10547 @node Home Score File
10548 @section Home Score File
10550 The score file where new score file entries will go is called the
10551 @dfn{home score file}. This is normally (and by default) the score file
10552 for the group itself. For instance, the home score file for
10553 @samp{gnu.emacs.gnus} is @file{gnu.emacs.gnus.SCORE}.
10555 However, this may not be what you want. It is often convenient to share
10556 a common home score file among many groups---all @samp{emacs} groups
10557 could perhaps use the same home score file.
10559 @vindex gnus-home-score-file
10560 The variable that controls this is @code{gnus-home-score-file}. It can
10565 A string. Then this file will be used as the home score file for all
10569 A function. The result of this function will be used as the home score
10570 file. The function will be called with the name of the group as the
10574 A list. The elements in this list can be:
10578 @var{(regexp file-name)}. If the @var{regexp} matches the group name,
10579 the @var{file-name} will will be used as the home score file.
10582 A function. If the function returns non-nil, the result will be used as
10583 the home score file.
10586 A string. Use the string as the home score file.
10589 The list will be traversed from the beginning towards the end looking
10594 So, if you want to use just a single score file, you could say:
10597 (setq gnus-home-score-file
10598 "my-total-score-file.SCORE")
10601 If you want to use @file{gnu.SCORE} for all @samp{gnu} groups and
10602 @file{rec.SCORE} for all @samp{rec} groups (and so on), you can say:
10605 (setq gnus-home-score-file
10606 'gnus-hierarchial-home-score-file)
10609 This is a ready-made function provided for your convenience.
10611 If you want to have one score file for the @samp{emacs} groups and
10612 another for the @samp{comp} groups, while letting all other groups use
10613 their own home score files:
10616 (setq gnus-home-score-file
10617 ;; All groups that match the regexp "\\.emacs"
10618 '("\\.emacs" "emacs.SCORE")
10619 ;; All the comp groups in one score file
10620 ("^comp" "comp.SCORE"))
10623 @vindex gnus-home-adapt-file
10624 @code{gnus-home-adapt-file} works exactly the same way as
10625 @code{gnus-home-score-file}, but says what the home adaptive score file
10626 is instead. All new adaptive file entries will go into the file
10627 specified by this variable, and the same syntax is allowed.
10629 In addition to using @code{gnus-home-score-file} and
10630 @code{gnus-home-adapt-file}, you can also use group parameters
10631 (@pxref{Group Parameters}) and topic parameters (@pxref{Topic
10632 Parameters}) to achieve much the same. Group and topic parameters take
10633 presedence over this variable.
10636 @node Followups To Yourself
10637 @section Followups To Yourself
10639 Gnus offers two commands for picking out the @code{Message-ID} header in
10640 the current buffer. Gnus will then add a score rule that scores using
10641 this @code{Message-ID} on the @code{References} header of other
10642 articles. This will, in effect, increase the score of all articles that
10643 respond to the article in the current buffer. Quite useful if you want
10644 to easily note when people answer what you've said.
10648 @item gnus-score-followup-article
10649 @findex gnus-score-followup-article
10650 This will add a score to articles that directly follow up your own
10653 @item gnus-score-followup-thread
10654 @findex gnus-score-followup-thread
10655 This will add a score to all articles that appear in a thread ``below''
10659 @vindex message-sent-hook
10660 These two functions are both primarily meant to be used in hooks like
10661 @code{message-sent-hook}.
10663 If you look closely at your own @code{Message-ID}, you'll notice that
10664 the first two or three characters are always the same. Here's two of
10668 <x6u3u47icf.fsf@@eyesore.no>
10669 <x6sp9o7ibw.fsf@@eyesore.no>
10672 So ``my'' ident on this machine is @samp{x6}. This can be
10673 exploited---the following rule will raise the score on all followups to
10678 "<x6[0-9a-z]+\\.fsf@.*eyesore.no>" 1000 nil r)
10681 Whether it's the first two or first three characters that are ``yours''
10682 is system-dependent.
10686 @section Scoring Tips
10687 @cindex scoring tips
10693 @cindex scoring crossposts
10694 If you want to lower the score of crossposts, the line to match on is
10695 the @code{Xref} header.
10697 ("xref" (" talk.politics.misc:" -1000))
10700 @item Multiple crossposts
10701 If you want to lower the score of articles that have been crossposted to
10702 more than, say, 3 groups:
10704 ("xref" ("[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+" -1000 nil r))
10707 @item Matching on the body
10708 This is generally not a very good idea---it takes a very long time.
10709 Gnus actually has to fetch each individual article from the server. But
10710 you might want to anyway, I guess. Even though there are three match
10711 keys (@code{Head}, @code{Body} and @code{All}), you should choose one
10712 and stick with it in each score file. If you use any two, each article
10713 will be fetched @emph{twice}. If you want to match a bit on the
10714 @code{Head} and a bit on the @code{Body}, just use @code{All} for all
10717 @item Marking as read
10718 You will probably want to mark articles that has a score below a certain
10719 number as read. This is most easily achieved by putting the following
10720 in your @file{all.SCORE} file:
10724 You may also consider doing something similar with @code{expunge}.
10726 @item Negated character classes
10727 If you say stuff like @code{[^abcd]*}, you may get unexpected results.
10728 That will match newlines, which might lead to, well, The Unknown. Say
10729 @code{[^abcd\n]*} instead.
10733 @node Reverse Scoring
10734 @section Reverse Scoring
10735 @cindex reverse scoring
10737 If you want to keep just articles that have @samp{Sex with Emacs} in the
10738 subject header, and expunge all other articles, you could put something
10739 like this in your score file:
10743 ("Sex with Emacs" 2))
10748 So, you raise all articles that match @samp{Sex with Emacs} and mark the
10749 rest as read, and expunge them to boot.
10752 @node Global Score Files
10753 @section Global Score Files
10754 @cindex global score files
10756 Sure, other newsreaders have ``global kill files''. These are usually
10757 nothing more than a single kill file that applies to all groups, stored
10758 in the user's home directory. Bah! Puny, weak newsreaders!
10760 What I'm talking about here are Global Score Files. Score files from
10761 all over the world, from users everywhere, uniting all nations in one
10762 big, happy score file union! Ange-score! New and untested!
10764 @vindex gnus-global-score-files
10765 All you have to do to use other people's score files is to set the
10766 @code{gnus-global-score-files} variable. One entry for each score file,
10767 or each score file directory. Gnus will decide by itself what score
10768 files are applicable to which group.
10770 Say you want to use all score files in the
10771 @file{/ftp@@ftp.some-where:/pub/score} directory and the single score
10772 file @file{/ftp@@ftp.ifi.uio.no:/pub/larsi/ding/score/soc.motss.SCORE}:
10775 (setq gnus-global-score-files
10776 '("/ftp@@ftp.ifi.uio.no:/pub/larsi/ding/score/soc.motss.SCORE"
10777 "/ftp@@ftp.some-where:/pub/score/"))
10780 @findex gnus-score-search-global-directories
10781 Simple, eh? Directory names must end with a @samp{/}. These
10782 directories are typically scanned only once during each Gnus session.
10783 If you feel the need to manually re-scan the remote directories, you can
10784 use the @code{gnus-score-search-global-directories} command.
10786 Note that, at present, using this option will slow down group entry
10787 somewhat. (That is---a lot.)
10789 If you want to start maintaining score files for other people to use,
10790 just put your score file up for anonymous ftp and announce it to the
10791 world. Become a retro-moderator! Participate in the retro-moderator
10792 wars sure to ensue, where retro-moderators battle it out for the
10793 sympathy of the people, luring them to use their score files on false
10794 premises! Yay! The net is saved!
10796 Here are some tips for the would-be retro-moderator, off the top of my
10802 Articles that are heavily crossposted are probably junk.
10804 To lower a single inappropriate article, lower by @code{Message-ID}.
10806 Particularly brilliant authors can be raised on a permanent basis.
10808 Authors that repeatedly post off-charter for the group can safely be
10809 lowered out of existence.
10811 Set the @code{mark} and @code{expunge} atoms to obliterate the nastiest
10812 articles completely.
10815 Use expiring score entries to keep the size of the file down. You
10816 should probably have a long expiry period, though, as some sites keep
10817 old articles for a long time.
10820 ... I wonder whether other newsreaders will support global score files
10821 in the future. @emph{Snicker}. Yup, any day now, newsreaders like Blue
10822 Wave, xrn and 1stReader are bound to implement scoring. Should we start
10823 holding our breath yet?
10827 @section Kill Files
10830 Gnus still supports those pesky old kill files. In fact, the kill file
10831 entries can now be expiring, which is something I wrote before Daniel
10832 Quinlan thought of doing score files, so I've left the code in there.
10834 In short, kill processing is a lot slower (and I do mean @emph{a lot})
10835 than score processing, so it might be a good idea to rewrite your kill
10836 files into score files.
10838 Anyway, a kill file is a normal @code{emacs-lisp} file. You can put any
10839 forms into this file, which means that you can use kill files as some
10840 sort of primitive hook function to be run on group entry, even though
10841 that isn't a very good idea.
10843 XCNormal kill files look like this:
10846 (gnus-kill "From" "Lars Ingebrigtsen")
10847 (gnus-kill "Subject" "ding")
10851 This will mark every article written by me as read, and remove them from
10852 the summary buffer. Very useful, you'll agree.
10854 Other programs use a totally different kill file syntax. If Gnus
10855 encounters what looks like a @code{rn} kill file, it will take a stab at
10858 Two summary functions for editing a GNUS kill file:
10863 @kindex M-k (Summary)
10864 @findex gnus-summary-edit-local-kill
10865 Edit this group's kill file (@code{gnus-summary-edit-local-kill}).
10868 @kindex M-K (Summary)
10869 @findex gnus-summary-edit-global-kill
10870 Edit the general kill file (@code{gnus-summary-edit-global-kill}).
10873 Two group mode functions for editing the kill files:
10878 @kindex M-k (Group)
10879 @findex gnus-group-edit-local-kill
10880 Edit this group's kill file (@code{gnus-group-edit-local-kill}).
10883 @kindex M-K (Group)
10884 @findex gnus-group-edit-global-kill
10885 Edit the general kill file (@code{gnus-group-edit-global-kill}).
10888 Kill file variables:
10891 @item gnus-kill-file-name
10892 @vindex gnus-kill-file-name
10893 A kill file for the group @samp{soc.motss} is normally called
10894 @file{soc.motss.KILL}. The suffix appended to the group name to get
10895 this file name is detailed by the @code{gnus-kill-file-name} variable.
10896 The ``global'' kill file (not in the score file sense of ``global'', of
10897 course) is called just @file{KILL}.
10899 @vindex gnus-kill-save-kill-file
10900 @item gnus-kill-save-kill-file
10901 If this variable is non-@code{nil}, Gnus will save the
10902 kill file after processing, which is necessary if you use expiring
10905 @item gnus-apply-kill-hook
10906 @vindex gnus-apply-kill-hook
10907 @findex gnus-apply-kill-file-unless-scored
10908 @findex gnus-apply-kill-file
10909 A hook called to apply kill files to a group. It is
10910 @code{(gnus-apply-kill-file)} by default. If you want to ignore the
10911 kill file if you have a score file for the same group, you can set this
10912 hook to @code{(gnus-apply-kill-file-unless-scored)}. If you don't want
10913 kill files to be processed, you should set this variable to @code{nil}.
10915 @item gnus-kill-file-mode-hook
10916 @vindex gnus-kill-file-mode-hook
10917 A hook called in kill-file mode buffers.
10926 GroupLens is a collaborative filtering system that helps you work
10927 together with other people to find the quality news articles out of the
10928 huge volume of news articles generated every day.
10930 To accomplish this the GroupLens system combines your opinions about
10931 articles you have already read with the opinions of others who have done
10932 likewise and gives you a personalized prediction for each unread news
10933 article. Think of GroupLens as a matchmaker. GroupLens watches how you
10934 rate articles, and finds other people that rate articles the same way.
10935 Once it has found for you some people you agree with it tells you, in
10936 the form of a prediction, what they thought of the article. You can use
10937 this prediction to help you decide whether or not you want to read the
10941 * Using GroupLens:: How to make Gnus use GroupLens.
10942 * Rating Articles:: Letting GroupLens know how you rate articles.
10943 * Displaying Predictions:: Displaying predictions given by GroupLens.
10944 * GroupLens Variables:: Customizing GroupLens.
10948 @node Using GroupLens
10949 @subsection Using GroupLens
10951 To use GroupLens you must register a pseudonym with your local Better
10952 Bit Bureau (BBB). At the moment the only better bit in town is at
10953 @samp{http://www.cs.umn.edu/Research/GroupLens/bbb.html}.
10955 Once you have registered you'll need to set a couple of variables.
10959 @item gnus-use-grouplens
10960 @vindex gnus-use-grouplens
10961 Setting this variable to a non-@code{nil} value will make Gnus hook into
10962 all the relevant GroupLens functions.
10964 @item grouplens-pseudonym
10965 @vindex grouplens-pseudonym
10966 This variable should be set to the pseudonum you got when registering
10967 with the Better Bit Bureau.
10969 @item grouplens-newsgroups
10970 @vindex grouplens-newsgroups
10971 A list of groups that you want to get GroupLens predictions for.
10975 Thats the minimum of what you need to get up and running with GroupLens.
10976 Once you've registered, GroupLens will start giving you scores for
10977 articles based on the average of what other people think. But, to get
10978 the real benefit of GroupLens you need to start rating articles
10979 yourself. Then the scores GroupLens gives you will be personalized for
10980 you, based on how the people you usually agree with have already rated.
10983 @node Rating Articles
10984 @subsection Rating Articles
10986 In GroupLens, an article is rated on a scale from 1 to 5, inclusive.
10987 Where 1 means something like this article is a waste of bandwidth and 5
10988 means that the article was really good. The basic question to ask
10989 yourself is, "on a scale from 1 to 5 would I like to see more articles
10992 There are four ways to enter a rating for an article in GroupLens.
10997 @kindex r (GroupLens)
10998 @findex bbb-summary-rate-article
10999 This function will prompt you for a rating on a scale of one to five.
11002 @kindex k (GroupLens)
11003 @findex grouplens-score-thread
11004 This function will prompt you for a rating, and rate all the articles in
11005 the thread. This is really useful for some of those long running giant
11006 threads in rec.humor.
11010 The next two commands, @kbd{n} and @kbd{,} take a numerical prefix to be
11011 the score of the article you're reading.
11016 @kindex n (GroupLens)
11017 @findex grouplens-next-unread-article
11018 Rate the article and go to the next unread article.
11021 @kindex , (GroupLens)
11022 @findex grouplens-best-unread-article
11023 Rate the article and go to the next unread article with the highest score.
11027 If you want to give the current article a score of 4 and then go to the
11028 next article, just type @kbd{4 n}.
11031 @node Displaying Predictions
11032 @subsection Displaying Predictions
11034 GroupLens makes a prediction for you about how much you will like a
11035 news article. The predictions from GroupLens are on a scale from 1 to
11036 5, where 1 is the worst and 5 is the best. You can use the predictions
11037 from GroupLens in one of three ways controlled by the variable
11038 @code{gnus-grouplens-override-scoring}.
11040 @vindex gnus-grouplens-override-scoring
11041 There are three ways to display predictions in grouplens. You may
11042 choose to have the GroupLens scores contribute to, or override the
11043 regular gnus scoring mechanism. override is the default; however, some
11044 people prefer to see the Gnus scores plus the grouplens scores. To get
11045 the separate scoring behavior you need to set
11046 @code{gnus-grouplens-override-scoring} to @code{'separate}. To have the
11047 GroupLens predictions combined with the grouplens scores set it to
11048 @code{'override} and to combine the scores set
11049 @code{gnus-grouplens-override-scoring} to @code{'combine}. When you use
11050 the combine option you will also want to set the values for
11051 @code{grouplens-prediction-offset} and
11052 @code{grouplens-score-scale-factor}.
11054 @vindex grouplens-prediction-display
11055 In either case, GroupLens gives you a few choices for how you would like
11056 to see your predictions displayed. The display of predictions is
11057 controlled by the @code{grouplens-prediction-display} variable.
11059 The following are legal values for that variable.
11062 @item prediction-spot
11063 The higher the prediction, the further to the right an @samp{*} is
11066 @item confidence-interval
11067 A numeric confidence interval.
11069 @item prediction-bar
11070 The higher the prediction, the longer the bar.
11072 @item confidence-bar
11073 Numerical confidence.
11075 @item confidence-spot
11076 The spot gets bigger with more confidence.
11078 @item prediction-num
11079 Plain-old numeric value.
11081 @item confidence-plus-minus
11082 Prediction +/i confidence.
11087 @node GroupLens Variables
11088 @subsection GroupLens Variables
11092 @item gnus-summary-grouplens-line-format
11093 The summary line format used in summary buffers that are GroupLens
11094 enhanced. It accepts the same specs as the normal summary line format
11095 (@pxref{Summary Buffer Lines}). The default is
11096 @samp{%U%R%z%l%I%(%[%4L: %-20,20n%]%) %s\n}.
11098 @item grouplens-bbb-host
11099 Host running the bbbd server. The default is
11100 @samp{grouplens.cs.umn.edu}.
11102 @item grouplens-bbb-port
11103 Port of the host running the bbbd server. The default is 9000.
11105 @item grouplens-score-offset
11106 Offset the prediction by this value. In other words, subtract the
11107 prediction value by this number to arrive at the effective score. The
11110 @item grouplens-score-scale-factor
11111 This variable allows the user to magnify the effect of GroupLens scores.
11112 The scale factor is applied after the offset. The default is 1.
11117 @node Advanced Scoring
11118 @section Advanced Scoring
11120 Scoring on Subjects and From headers is nice enough, but what if you're
11121 really interested in what a person has to say only when she's talking
11122 about a particular subject? Or what about if you really don't want to
11123 read what person A has to say when she's following up to person B, but
11124 want to read what she says when she's following up to person C?
11126 By using advanced scoring rules you may create arbitrarily complex
11130 * Advanced Scoring Syntax:: A definition.
11131 * Advanced Scoring Examples:: What they look like.
11132 * Advanced Scoring Tips:: Getting the most out of it.
11136 @node Advanced Scoring Syntax
11137 @subsection Advanced Scoring Syntax
11139 Ordinary scoring rules have a string as the first element in the rule.
11140 Advanced scoring rules have a list as the first element. The second
11141 element is the score to be applied if the first element evaluated to a
11142 non-@code{nil} value.
11144 These lists may consist of three logical operators, one redirection
11145 operator, and various match operators.
11152 This logical operator will evaluate each of its arguments until it finds
11153 one that evaluates to @code{false}, and then it'll stop. If all arguments
11154 evaluate to @code{true} values, then this operator will return
11159 This logical operator will evaluate each of its arguments until it finds
11160 one that evaluates to @code{true}. If no arguments are @code{true},
11161 then this operator will return @code{false}.
11166 This logical operator only takes a single argument. It returns the
11167 inverse of the value of its argument.
11171 There is an @dfn{indirection operator} that will make its arguments
11172 apply to the ancenstors of the current article being scored. For
11173 instance, @code{1-} will make score rules apply to the parent of the
11174 current article. @code{2-} will make score fules apply to the
11175 grandparent of the current article. Alternatively, you can write
11176 @code{^^}, where the number of @code{^}s (carets) say how far back into
11177 the ancestry you want to go.
11179 Finally, we have the match operators. These are the ones that do the
11180 real work. Match operators are header name strings followed by a match
11181 and a match type. A typical match operator looks like @samp{("from"
11182 "Lars Ingebrigtsen" s)}. The header names are the same as when using
11183 simple scoring, and the match types are also the same.
11186 @node Advanced Scoring Examples
11187 @subsection Advanced Scoring Examples
11189 Let's say you want to increase the score of articles written by Lars
11190 when he's talking about Gnus:
11194 ("from" "Lars Ingebrigtsen")
11195 ("subject" "Gnus"))
11201 When he writes long articles, he sometimes has something nice to say:
11205 ("from" "Lars Ingebrigtsen")
11212 However, when he responds to things written by Reig Eigil Logge, you
11213 really don't want to read what he's written:
11217 ("from" "Lars Ingebrigtsen")
11218 (1- ("from" "Reig Eigir Logge")))
11222 Everybody that follows up Redmondo when he writes about disappearing
11223 socks should have their scores raised, but only when they talk about
11224 white socks. However, when Lars talks about socks, it's usually not
11231 ("from" "redmondo@@.*no" r)
11232 ("body" "disappearing.*socks" t)))
11233 (! ("from" "Lars Ingebrigtsen"))
11234 ("body" "white.*socks"))
11238 The possibilities are endless.
11241 @node Advanced Scoring Tips
11242 @subsection Advanced Scoring Tips
11244 The @code{&} and @code{|} logical operators do short-circuit logic.
11245 That is, they stop processing their arguments when it's clear what the
11246 result of the operation will be. For instance, if one of the arguments
11247 of an @code{&} evaluates to @code{false}, there's no point in evaluating
11248 the rest of the arguments. This means that you should put slow matches
11249 (@samp{body}, @code{header}) last and quick matches (@samp{from},
11250 @samp{subject}) first.
11252 The indirection arguments (@code{1-} and so on) will make their
11253 arguments work on previous generations of the thread. If you say
11264 Then that means "score on the from header of the grandparent of the
11265 current article". An indirection is quite fast, but it's better to say:
11271 ("subject" "Gnus")))
11278 (1- ("from" "Lars"))
11279 (1- ("subject" "Gnus")))
11284 @section Score Decays
11285 @cindex score decays
11288 You may find that your scores have a tendency to grow without
11289 bounds, especially if you're using adaptive scoring. If scores get too
11290 big, they lose all meaning---they simply max out and it's difficult to
11291 use them in any sensible way.
11293 @vindex gnus-decay-scores
11294 @findex gnus-decay-score
11295 @vindex gnus-score-decay-function
11296 Gnus provides a mechanism for decaying scores to help with this problem.
11297 When score files are loaded and @code{gnus-decay-scores} is
11298 non-@code{nil}, Gnus will run the score files through the decaying
11299 mechanism thereby lowering the scores of all non-permanent score rules.
11300 The decay itself if performed by the @code{gnus-score-decay-function}
11301 function, which is @code{gnus-decay-score} by default. Here's the
11302 definition of that function:
11305 (defun gnus-decay-score (score)
11308 (* (if (< score 0) 1 -1)
11310 (max gnus-score-decay-constant
11312 gnus-score-decay-scale)))))))
11315 @vindex gnus-score-decay-scale
11316 @vindex gnus-score-decay-constant
11317 @code{gnus-score-decay-constant} is 3 by default and
11318 @code{gnus-score-decay-scale} is 0.05. This should cause the following:
11322 Scores between -3 and 3 will be set to 0 when this function is called.
11325 Scores with magnitudes between 3 and 60 will be shrunk by 3.
11328 Scores with magnutudes greater than 60 will be shrunk by 5% of the
11332 If you don't like this decay function, write your own. It is called
11333 with the score to be decayed as its only parameter, and it should return
11334 the new score, which should be an integer.
11336 Gnus will try to decay scores once a day. If you haven't run Gnus for
11337 four days, Gnus will decay the scores four times, for instance.
11344 * Process/Prefix:: A convention used by many treatment commands.
11345 * Interactive:: Making Gnus ask you many questions.
11346 * Formatting Variables:: You can specify what buffers should look like.
11347 * Windows Configuration:: Configuring the Gnus buffer windows.
11348 * Compilation:: How to speed Gnus up.
11349 * Mode Lines:: Displaying information in the mode lines.
11350 * Highlighting and Menus:: Making buffers look all nice and cozy.
11351 * Buttons:: Get tendonitis in ten easy steps!
11352 * Daemons:: Gnus can do things behind your back.
11353 * NoCeM:: How to avoid spam and other fatty foods.
11354 * Picons:: How to display pictures of what your reading.
11355 * Moderation:: What to do if you're a moderator.
11356 * XEmacs Enhancements:: There are more pictures and stuff under XEmacs.
11357 * Various Various:: Things that are really various.
11361 @node Process/Prefix
11362 @section Process/Prefix
11363 @cindex process/prefix convention
11365 Many functions, among them functions for moving, decoding and saving
11366 articles, use what is known as the @dfn{Process/Prefix convention}.
11368 This is a method for figuring out what articles that the user wants the
11369 command to be performed on.
11373 If the numeric prefix is N, perform the operation on the next N
11374 articles, starting with the current one. If the numeric prefix is
11375 negative, perform the operation on the previous N articles, starting
11376 with the current one.
11378 @vindex transient-mark-mode
11379 If @code{transient-mark-mode} in non-@code{nil} and the region is
11380 active, all articles in the region will be worked upon.
11382 If there is no numeric prefix, but some articles are marked with the
11383 process mark, perform the operation on the articles that are marked with
11386 If there is neither a numeric prefix nor any articles marked with the
11387 process mark, just perform the operation on the current article.
11389 Quite simple, really, but it needs to be made clear so that surprises
11392 Commands that react to the process mark will push the current list of
11393 process marked articles onto a stack and will then clear all process
11394 marked articles. You can restore the previous configuration with the
11395 @kbd{M P y} command (@pxref{Setting Process Marks}).
11397 @vindex gnus-summary-goto-unread
11398 One thing that seems to shock & horrify lots of people is that, for
11399 instance, @kbd{3 d} does exactly the same as @kbd{d} @kbd{d} @kbd{d}.
11400 Since each @kbd{d} (which marks the current article as read) by default
11401 goes to the next unread article after marking, this means that @kbd{3 d}
11402 will mark the next three unread articles as read, no matter what the
11403 summary buffer looks like. Set @code{gnus-summary-goto-unread} to
11404 @code{nil} for a more straightforward action.
11408 @section Interactive
11409 @cindex interaction
11413 @item gnus-novice-user
11414 @vindex gnus-novice-user
11415 If this variable is non-@code{nil}, you are either a newcomer to the
11416 World of Usenet, or you are very cautious, which is a nice thing to be,
11417 really. You will be given questions of the type ``Are you sure you want
11418 to do this?'' before doing anything dangerous. This is @code{t} by
11421 @item gnus-expert-user
11422 @vindex gnus-expert-user
11423 If this variable is non-@code{nil}, you will never ever be asked any
11424 questions by Gnus. It will simply assume you know what you're doing, no
11425 matter how strange.
11427 @item gnus-interactive-catchup
11428 @vindex gnus-interactive-catchup
11429 Require confirmation before catching up a group if non-@code{nil}. It
11430 is @code{t} by default.
11432 @item gnus-interactive-exit
11433 @vindex gnus-interactive-exit
11434 Require confirmation before exiting Gnus. This variable is @code{t} by
11439 @node Formatting Variables
11440 @section Formatting Variables
11441 @cindex formatting variables
11443 Throughout this manual you've probably noticed lots of variables that
11444 are called things like @code{gnus-group-line-format} and
11445 @code{gnus-summary-mode-line-format}. These control how Gnus is to
11446 output lines in the various buffers. There's quite a lot of them.
11447 Fortunately, they all use the same syntax, so there's not that much to
11450 Here's an example format spec (from the group buffer): @samp{%M%S%5y:
11451 %(%g%)\n}. We see that it is indeed extremely ugly, and that there are
11452 lots of percentages everywhere.
11455 * Formatting Basics:: A formatting variable is basically a format string.
11456 * Advanced Formatting:: Modifying output in various ways.
11457 * User-Defined Specs:: Having Gnus call your own functions.
11458 * Formatting Fonts:: Making the formatting look colorful and nice.
11461 Currently Gnus uses the following formatting variables:
11462 @code{gnus-group-line-format}, @code{gnus-summary-line-format},
11463 @code{gnus-server-line-format}, @code{gnus-topic-line-format},
11464 @code{gnus-group-mode-line-format},
11465 @code{gnus-summary-mode-line-format},
11466 @code{gnus-article-mode-line-format},
11467 @code{gnus-server-mode-line-format}, and
11468 @code{gnus-summary-pick-line-format}.
11470 All these format variables can also be arbitrary elisp forms. In that
11471 case, they will be @code{eval}ed to insert the required lines.
11473 @kindex M-x gnus-update-format
11474 @findex gnus-update-format
11475 Gnus includes a command to help you while creating your own format
11476 specs. @kbd{M-x gnus-update-format} will @code{eval} the current form,
11477 update the spec in question and pop you to a buffer where you can
11478 examine the resulting lisp code to be run to generate the line.
11482 @node Formatting Basics
11483 @subsection Formatting Basics
11485 Each @samp{%} element will be replaced by some string or other when the
11486 buffer in question is generated. @samp{%5y} means ``insert the @samp{y}
11487 spec, and pad with spaces to get a 5-character field''.
11489 As with normal C and Emacs Lisp formatting strings, the numerical
11490 modifier between the @samp{%} and the formatting type character will
11491 @dfn{pad} the output so that it is always at least that long.
11492 @samp{%5y} will make the field always (at least) five characters wide by
11493 padding with spaces to the left. If you say @samp{%-5y}, it will pad to
11496 You may also wish to limit the length of the field to protect against
11497 particularly wide values. For that you can say @samp{%4,6y}, which
11498 means that the field will never be more than 6 characters wide and never
11499 less than 4 characters wide.
11502 @node Advanced Formatting
11503 @subsection Advanced Formatting
11505 It is frequently useful to post-process the fields in some way.
11506 Padding, limiting, cutting off parts and suppressing certain values can
11507 be achieved by using @dfn{tilde modifiers}. A typical tilde spec might
11508 look like @samp{%~(cut 3)~(ignore "0")y}.
11510 These are the legal modifiers:
11515 Pad the field to the left with spaces until it reaches the required
11519 Pad the field to the right with spaces until it reaches the required
11524 Cut off characters from the left until it reaches the specified length.
11527 Cut off characters from the right until it reaches the specified
11532 Cut off the specified number of characters from the left.
11535 Cut off the specified number of characters from the right.
11538 Return an empty string if the field is equal to the specified value.
11541 Use the specified form as the field value when the @samp{@@} spec is
11545 Let's take an example. The @samp{%o} spec in the summary mode lines
11546 will return a date in compact ISO8601 format---@samp{19960809T230410}.
11547 This is quite a mouthful, so we want to shave off the century number and
11548 the time, leaving us with a six-character date. That would be
11549 @samp{%~(cut-left 2)~(max-right 6)~(pad 6)o}. (Cutting is done before
11550 maxing, and we need the padding to ensure that the date is never less
11551 than 6 characters to make it look nice in columns.)
11553 Ignoring is done first; then cutting; then maxing; and then as the very
11554 last operation, padding.
11556 If you use lots of these advanced thingies, you'll find that Gnus gets
11557 quite slow. This can be helped enourmously by running @kbd{M-x
11558 gnus-compile} when you are setisfied with the look of your lines.
11559 @xref{Compilation}.
11562 @node User-Defined Specs
11563 @subsection User-Defined Specs
11565 All the specs allow for inserting user defined specifiers---@samp{u}.
11566 The next character in the format string should be a letter. Gnus
11567 will call the function @code{gnus-user-format-function-}@samp{X}, where
11568 @samp{X} is the letter following @samp{%u}. The function will be passed
11569 a single parameter---what the parameter means depends on what buffer
11570 it's being called from. The function should return a string, which will
11571 be inserted into the buffer just like information from any other
11572 specifier. This function may also be called with dummy values, so it
11573 should protect against that.
11575 You can also use tilde modifiers (@pxref{Advanced Formatting} to achieve
11576 much the same without defining new functions. Here's an example:
11577 @samp{%~(form (count-lines (point-min) (point)))@@}. The form
11578 given here will be evaluated to yield the current line number, and then
11582 @node Formatting Fonts
11583 @subsection Formatting Fonts
11585 There are specs for highlighting, and these are shared by all the format
11586 variables. Text inside the @samp{%(} and @samp{%)} specifiers will get
11587 the special @code{mouse-face} property set, which means that it will be
11588 highlighted (with @code{gnus-mouse-face}) when you put the mouse pointer
11591 Text inside the @samp{%[} and @samp{%]} specifiers will have their
11592 normal faces set using @code{gnus-face-0}, which is @code{bold} by
11593 default. If you say @samp{%1[} instead, you'll get @code{gnus-face-1}
11594 instead, and so on. Create as many faces as you wish. The same goes
11595 for the @code{mouse-face} specs---you can say @samp{%3(hello%)} to have
11596 @samp{hello} mouse-highlighted with @code{gnus-mouse-face-3}.
11598 Here's an alternative recipe for the group buffer:
11601 ;; Create three face types.
11602 (setq gnus-face-1 'bold)
11603 (setq gnus-face-3 'italic)
11605 ;; We want the article count to be in
11606 ;; a bold and green face. So we create
11607 ;; a new face called `my-green-bold'.
11608 (copy-face 'bold 'my-green-bold)
11610 (set-face-foreground 'my-green-bold "ForestGreen")
11611 (setq gnus-face-2 'my-green-bold)
11613 ;; Set the new & fancy format.
11614 (setq gnus-group-line-format
11615 "%M%S%3@{%5y%@}%2[:%] %(%1@{%g%@}%)\n")
11618 I'm sure you'll be able to use this scheme to create totally unreadable
11619 and extremely vulgar displays. Have fun!
11621 Note that the @samp{%(} specs (and friends) do not make any sense on the
11622 mode-line variables.
11625 @node Windows Configuration
11626 @section Windows Configuration
11627 @cindex windows configuration
11629 No, there's nothing here about X, so be quiet.
11631 @vindex gnus-use-full-window
11632 If @code{gnus-use-full-window} non-@code{nil}, Gnus will delete all
11633 other windows and occupy the entire Emacs screen by itself. It is
11634 @code{t} by default.
11636 @vindex gnus-buffer-configuration
11637 @code{gnus-buffer-configuration} describes how much space each Gnus
11638 buffer should be given. Here's an excerpt of this variable:
11641 ((group (vertical 1.0 (group 1.0 point)
11642 (if gnus-carpal (group-carpal 4))))
11643 (article (vertical 1.0 (summary 0.25 point)
11647 This is an alist. The @dfn{key} is a symbol that names some action or
11648 other. For instance, when displaying the group buffer, the window
11649 configuration function will use @code{group} as the key. A full list of
11650 possible names is listed below.
11652 The @dfn{value} (i. e., the @dfn{split}) says how much space each buffer
11653 should occupy. To take the @code{article} split as an example -
11656 (article (vertical 1.0 (summary 0.25 point)
11660 This @dfn{split} says that the summary buffer should occupy 25% of upper
11661 half of the screen, and that it is placed over the article buffer. As
11662 you may have noticed, 100% + 25% is actually 125% (yup, I saw y'all
11663 reaching for that calculator there). However, the special number
11664 @code{1.0} is used to signal that this buffer should soak up all the
11665 rest of the space available after the rest of the buffers have taken
11666 whatever they need. There should be only one buffer with the @code{1.0}
11667 size spec per split.
11669 Point will be put in the buffer that has the optional third element
11672 Here's a more complicated example:
11675 (article (vertical 1.0 (group 4)
11676 (summary 0.25 point)
11677 (if gnus-carpal (summary-carpal 4))
11681 If the size spec is an integer instead of a floating point number,
11682 then that number will be used to say how many lines a buffer should
11683 occupy, not a percentage.
11685 If the @dfn{split} looks like something that can be @code{eval}ed (to be
11686 precise---if the @code{car} of the split is a function or a subr), this
11687 split will be @code{eval}ed. If the result is non-@code{nil}, it will
11688 be used as a split. This means that there will be three buffers if
11689 @code{gnus-carpal} is @code{nil}, and four buffers if @code{gnus-carpal}
11692 Not complicated enough for you? Well, try this on for size:
11695 (article (horizontal 1.0
11700 (summary 0.25 point)
11705 Whoops. Two buffers with the mystery 100% tag. And what's that
11706 @code{horizontal} thingie?
11708 If the first element in one of the split is @code{horizontal}, Gnus will
11709 split the window horizontally, giving you two windows side-by-side.
11710 Inside each of these strips you may carry on all you like in the normal
11711 fashion. The number following @code{horizontal} says what percentage of
11712 the screen is to be given to this strip.
11714 For each split, there @emph{must} be one element that has the 100% tag.
11715 The splitting is never accurate, and this buffer will eat any leftover
11716 lines from the splits.
11718 To be slightly more formal, here's a definition of what a legal split
11722 split = frame | horizontal | vertical | buffer | form
11723 frame = "(frame " size *split ")"
11724 horizontal = "(horizontal " size *split ")"
11725 vertical = "(vertical " size *split ")"
11726 buffer = "(" buffer-name " " size *[ "point" ] ")"
11727 size = number | frame-params
11728 buffer-name = group | article | summary ...
11731 The limitations are that the @code{frame} split can only appear as the
11732 top-level split. @var{form} should be an Emacs Lisp form that should
11733 return a valid split. We see that each split is fully recursive, and
11734 may contain any number of @code{vertical} and @code{horizontal} splits.
11736 @vindex gnus-window-min-width
11737 @vindex gnus-window-min-height
11738 @cindex window height
11739 @cindex window width
11740 Finding the right sizes can be a bit complicated. No window may be less
11741 than @code{gnus-window-min-height} (default 1) characters high, and all
11742 windows must be at least @code{gnus-window-min-width} (default 1)
11743 characters wide. Gnus will try to enforce this before applying the
11744 splits. If you want to use the normal Emacs window width/height limit,
11745 you can just set these two variables to @code{nil}.
11747 If you're not familiar with Emacs terminology, @code{horizontal} and
11748 @code{vertical} splits may work the opposite way of what you'd expect.
11749 Windows inside a @code{horizontal} split are shown side-by-side, and
11750 windows within a @code{vertical} split are shown above each other.
11752 @findex gnus-configure-frame
11753 If you want to experiment with window placement, a good tip is to call
11754 @code{gnus-configure-frame} directly with a split. This is the function
11755 that does all the real work when splitting buffers. Below is a pretty
11756 nonsensical configuration with 5 windows; two for the group buffer and
11757 three for the article buffer. (I said it was nonsensical.) If you
11758 @code{eval} the statement below, you can get an idea of how that would
11759 look straight away, without going through the normal Gnus channels.
11760 Play with it until you're satisfied, and then use
11761 @code{gnus-add-configuration} to add your new creation to the buffer
11762 configuration list.
11765 (gnus-configure-frame
11769 (article 0.3 point))
11777 You might want to have several frames as well. No prob---just use the
11778 @code{frame} split:
11781 (gnus-configure-frame
11784 (summary 0.25 point)
11786 (vertical ((height . 5) (width . 15)
11787 (user-position . t)
11788 (left . -1) (top . 1))
11793 This split will result in the familiar summary/article window
11794 configuration in the first (or ``main'') frame, while a small additional
11795 frame will be created where picons will be shown. As you can see,
11796 instead of the normal @code{1.0} top-level spec, each additional split
11797 should have a frame parameter alist as the size spec.
11798 @xref{Frame Parameters, , Frame Parameters, elisp, The GNU Emacs Lisp
11801 Here's a list of all possible keys for
11802 @code{gnus-buffer-configuration}:
11804 @code{group}, @code{summary}, @code{article}, @code{server},
11805 @code{browse}, @code{message}, @code{pick}, @code{info},
11806 @code{summary-faq}, @code{edit-group}, @code{edit-server},
11807 @code{edit-score}, @code{post}, @code{reply}, @code{forward},
11808 @code{reply-yank}, @code{mail-bounce}, @code{draft},
11809 @code{pipe}, @code{bug}, @code{compose-bounce}.
11811 Note that the @code{message} key is used for both
11812 @code{gnus-group-mail} and @code{gnus-summary-mail-other-window}. If
11813 it is desireable to distinguish between the two, something like this
11817 (message (horizontal 1.0
11818 (vertical 1.0 (message 1.0 point))
11820 (if (buffer-live-p gnus-summary-buffer)
11825 @findex gnus-add-configuration
11826 Since the @code{gnus-buffer-configuration} variable is so long and
11827 complicated, there's a function you can use to ease changing the config
11828 of a single setting: @code{gnus-add-configuration}. If, for instance,
11829 you want to change the @code{article} setting, you could say:
11832 (gnus-add-configuration
11833 '(article (vertical 1.0
11835 (summary .25 point)
11839 You'd typically stick these @code{gnus-add-configuration} calls in your
11840 @file{.gnus} file or in some startup hook---they should be run after
11841 Gnus has been loaded.
11845 @section Compilation
11846 @cindex compilation
11847 @cindex byte-compilation
11849 @findex gnus-compile
11851 Remember all those line format specification variables?
11852 @code{gnus-summary-line-format}, @code{gnus-group-line-format}, and so
11853 on. Now, Gnus will of course heed whatever these variables are, but,
11854 unfortunately, changing them will mean a quite significant slow-down.
11855 (The default values of these variables have byte-compiled functions
11856 associated with them, while the user-generated versions do not, of
11859 To help with this, you can run @kbd{M-x gnus-compile} after you've
11860 fiddled around with the variables and feel that you're (kind of)
11861 satisfied. This will result in the new specs being byte-compiled, and
11862 you'll get top speed again. Gnus will save these compiled specs in the
11863 @file{.newsrc.eld} file. (User-defined functions aren't compiled by
11864 this function, though---you should compile them yourself by sticking
11865 them into the @code{.gnus.el} file and byte-compiling that file.)
11869 @section Mode Lines
11872 @vindex gnus-updated-mode-lines
11873 @code{gnus-updated-mode-lines} says what buffers should keep their mode
11874 lines updated. It is a list of symbols. Supported symbols include
11875 @code{group}, @code{article}, @code{summary}, @code{server},
11876 @code{browse}, and @code{tree}. If the corresponding symbol is present,
11877 Gnus will keep that mode line updated with information that may be
11878 pertinent. If this variable is @code{nil}, screen refresh may be
11881 @cindex display-time
11883 @vindex gnus-mode-non-string-length
11884 By default, Gnus displays information on the current article in the mode
11885 lines of the summary and article buffers. The information Gnus wishes
11886 to display (eg. the subject of the article) is often longer than the
11887 mode lines, and therefore have to be cut off at some point. The
11888 @code{gnus-mode-non-string-length} variable says how long the other
11889 elements on the line is (i.e., the non-info part). If you put
11890 additional elements on the mode line (eg. a clock), you should modify
11893 @c Hook written by Francesco Potorti` <pot@cnuce.cnr.it>
11895 (add-hook 'display-time-hook
11896 (lambda () (setq gnus-mode-non-string-length
11898 (if line-number-mode 5 0)
11899 (if column-number-mode 4 0)
11900 (length display-time-string)))))
11903 If this variable is @code{nil} (which is the default), the mode line
11904 strings won't be chopped off, and they won't be padded either.
11907 @node Highlighting and Menus
11908 @section Highlighting and Menus
11910 @cindex highlighting
11913 @vindex gnus-visual
11914 The @code{gnus-visual} variable controls most of the prettifying Gnus
11915 aspects. If @code{nil}, Gnus won't attempt to create menus or use fancy
11916 colors or fonts. This will also inhibit loading the @file{gnus-vis.el}
11919 This variable can be a list of visual properties that are enabled. The
11920 following elements are legal, and are all included by default:
11923 @item group-highlight
11924 Do highlights in the group buffer.
11925 @item summary-highlight
11926 Do highlights in the summary buffer.
11927 @item article-highlight
11928 Do highlights in the article buffer.
11930 Turn on highlighting in all buffers.
11932 Create menus in the group buffer.
11934 Create menus in the summary buffers.
11936 Create menus in the article buffer.
11938 Create menus in the browse buffer.
11940 Create menus in the server buffer.
11942 Create menus in the score buffers.
11944 Create menus in all buffers.
11947 So if you only want highlighting in the article buffer and menus in all
11948 buffers, you could say something like:
11951 (setq gnus-visual '(article-highlight menu))
11954 If you want only highlighting and no menus whatsoever, you'd say:
11957 (setq gnus-visual '(highlight))
11960 If @code{gnus-visual} is @code{t}, highlighting and menus will be used
11961 in all Gnus buffers.
11963 Other general variables that influence the look of all buffers include:
11966 @item gnus-mouse-face
11967 @vindex gnus-mouse-face
11968 This is the face (i.e., font) used for mouse highlighting in Gnus. No
11969 mouse highlights will be done if @code{gnus-visual} is @code{nil}.
11971 @item gnus-display-type
11972 @vindex gnus-display-type
11973 This variable is symbol indicating the display type Emacs is running
11974 under. The symbol should be one of @code{color}, @code{grayscale} or
11975 @code{mono}. If Gnus guesses this display attribute wrongly, either set
11976 this variable in your @file{~/.emacs} or set the resource
11977 @code{Emacs.displayType} in your @file{~/.Xdefaults}.
11979 @item gnus-background-mode
11980 @vindex gnus-background-mode
11981 This is a symbol indicating the Emacs background brightness. The symbol
11982 should be one of @code{light} or @code{dark}. If Gnus guesses this
11983 frame attribute wrongly, either set this variable in your @file{~/.emacs} or
11984 set the resource @code{Emacs.backgroundMode} in your @file{~/.Xdefaults}.
11985 `gnus-display-type'.
11988 There are hooks associated with the creation of all the different menus:
11992 @item gnus-article-menu-hook
11993 @vindex gnus-article-menu-hook
11994 Hook called after creating the article mode menu.
11996 @item gnus-group-menu-hook
11997 @vindex gnus-group-menu-hook
11998 Hook called after creating the group mode menu.
12000 @item gnus-summary-menu-hook
12001 @vindex gnus-summary-menu-hook
12002 Hook called after creating the summary mode menu.
12004 @item gnus-server-menu-hook
12005 @vindex gnus-server-menu-hook
12006 Hook called after creating the server mode menu.
12008 @item gnus-browse-menu-hook
12009 @vindex gnus-browse-menu-hook
12010 Hook called after creating the browse mode menu.
12012 @item gnus-score-menu-hook
12013 @vindex gnus-score-menu-hook
12014 Hook called after creating the score mode menu.
12025 Those new-fangled @dfn{mouse} contraptions is very popular with the
12026 young, hep kids who don't want to learn the proper way to do things
12027 these days. Why, I remember way back in the summer of '89, when I was
12028 using Emacs on a Tops 20 system. Three hundred users on one single
12029 machine, and every user was running Simula compilers. Bah!
12033 @vindex gnus-carpal
12034 Well, you can make Gnus display bufferfuls of buttons you can click to
12035 do anything by setting @code{gnus-carpal} to @code{t}. Pretty simple,
12036 really. Tell the chiropractor I sent you.
12041 @item gnus-carpal-mode-hook
12042 @vindex gnus-carpal-mode-hook
12043 Hook run in all carpal mode buffers.
12045 @item gnus-carpal-button-face
12046 @vindex gnus-carpal-button-face
12047 Face used on buttons.
12049 @item gnus-carpal-header-face
12050 @vindex gnus-carpal-header-face
12051 Face used on carpal buffer headers.
12053 @item gnus-carpal-group-buffer-buttons
12054 @vindex gnus-carpal-group-buffer-buttons
12055 Buttons in the group buffer.
12057 @item gnus-carpal-summary-buffer-buttons
12058 @vindex gnus-carpal-summary-buffer-buttons
12059 Buttons in the summary buffer.
12061 @item gnus-carpal-server-buffer-buttons
12062 @vindex gnus-carpal-server-buffer-buttons
12063 Buttons in the server buffer.
12065 @item gnus-carpal-browse-buffer-buttons
12066 @vindex gnus-carpal-browse-buffer-buttons
12067 Buttons in the browse buffer.
12070 All the @code{buttons} variables are lists. The elements in these list
12071 is either a cons cell where the car contains a text to be displayed and
12072 the cdr contains a function symbol, or a simple string.
12080 Gnus, being larger than any program ever written (allegedly), does lots
12081 of strange stuff that you may wish to have done while you're not
12082 present. For instance, you may want it to check for new mail once in a
12083 while. Or you may want it to close down all connections to all servers
12084 when you leave Emacs idle. And stuff like that.
12086 Gnus will let you do stuff like that by defining various
12087 @dfn{handlers}. Each handler consists of three elements: A
12088 @var{function}, a @var{time}, and an @var{idle} parameter.
12090 Here's an example of a handler that closes connections when Emacs has
12091 been idle for thirty minutes:
12094 (gnus-demon-close-connections nil 30)
12097 Here's a handler that scans for PGP headers every hour when Emacs is
12101 (gnus-demon-scan-pgp 60 t)
12104 This @var{time} parameter and than @var{idle} parameter works together
12105 in a strange, but wonderful fashion. Basically, if @var{idle} is
12106 @code{nil}, then the function will be called every @var{time} minutes.
12108 If @var{idle} is @code{t}, then the function will be called after
12109 @var{time} minutes only if Emacs is idle. So if Emacs is never idle,
12110 the function will never be called. But once Emacs goes idle, the
12111 function will be called every @var{time} minutes.
12113 If @var{idle} is a number and @var{time} is a number, the function will
12114 be called every @var{time} minutes only when Emacs has been idle for
12115 @var{idle} minutes.
12117 If @var{idle} is a number and @var{time} is @code{nil}, the function
12118 will be called once every time Emacs has been idle for @var{idle}
12121 And if @var{time} is a string, it should look like @samp{07:31}, and
12122 the function will then be called once every day somewhere near that
12123 time. Modified by the @var{idle} parameter, of course.
12125 @vindex gnus-demon-timestep
12126 (When I say ``minute'' here, I really mean @code{gnus-demon-timestep}
12127 seconds. This is @code{60} by default. If you change that variable,
12128 all the timings in the handlers will be affected.)
12130 @vindex gnus-use-demon
12131 To set the whole thing in motion, though, you have to set
12132 @code{gnus-use-demon} to @code{t}.
12134 So, if you want to add a handler, you could put something like this in
12135 your @file{.gnus} file:
12137 @findex gnus-demon-add-handler
12139 (gnus-demon-add-handler 'gnus-demon-close-connections nil 30)
12142 @findex gnus-demon-add-nocem
12143 @findex gnus-demon-add-scanmail
12144 @findex gnus-demon-add-rescan
12145 @findex gnus-demon-add-disconnection
12146 Some ready-made functions to do this has been created:
12147 @code{gnus-demon-add-nocem}, @code{gnus-demon-add-disconnection},
12148 @code{gnus-demon-add-rescan}, and @code{gnus-demon-add-scanmail}. Just
12149 put those functions in your @file{.gnus} if you want those abilities.
12151 @findex gnus-demon-init
12152 @findex gnus-demon-cancel
12153 @vindex gnus-demon-handlers
12154 If you add handlers to @code{gnus-demon-handlers} directly, you should
12155 run @code{gnus-demon-init} to make the changes take hold. To cancel all
12156 daemons, you can use the @code{gnus-demon-cancel} function.
12158 Note that adding daemons can be pretty naughty if you overdo it. Adding
12159 functions that scan all news and mail from all servers every two seconds
12160 is a sure-fire way of getting booted off any respectable system. So
12169 @dfn{Spamming} is posting the same article lots and lots of times.
12170 Spamming is bad. Spamming is evil.
12172 Spamming is usually canceled within a day or so by various anti-spamming
12173 agencies. These agencies usually also send out @dfn{NoCeM} messages.
12174 NoCeM is pronounced ``no see-'em'', and means what the name
12175 implies---these are messages that make the offending articles, like, go
12178 What use are these NoCeM messages if the articles are canceled anyway?
12179 Some sites do not honor cancel messages and some sites just honor cancels
12180 from a select few people. Then you may wish to make use of the NoCeM
12181 messages, which are distributed in the @samp{alt.nocem.misc} newsgroup.
12183 Gnus can read and parse the messages in this group automatically, and
12184 this will make spam disappear.
12186 There are some variables to customize, of course:
12189 @item gnus-use-nocem
12190 @vindex gnus-use-nocem
12191 Set this variable to @code{t} to set the ball rolling. It is @code{nil}
12194 @item gnus-nocem-groups
12195 @vindex gnus-nocem-groups
12196 Gnus will look for NoCeM messages in the groups in this list. The
12197 default is @code{("alt.nocem.misc" "news.admin.net-abuse.announce")}.
12199 @item gnus-nocem-issuers
12200 @vindex gnus-nocem-issuers
12201 There are many people issuing NoCeM messages. This list says what
12202 people you want to listen to. The default is @code{("Automoose-1"
12203 "clewis@@ferret.ocunix.on.ca;" "jem@@xpat.com;" "red@@redpoll.mrfs.oh.us
12204 (Richard E. Depew)")}; fine, upstanding citizens all of them.
12206 Known despammers that you can put in this list include:
12209 @item clewis@@ferret.ocunix.on.ca;
12210 @cindex Chris Lewis
12211 Chris Lewis---Major Canadian despammer who has probably canceled more
12212 usenet abuse than anybody else.
12215 @cindex CancelMoose[tm]
12216 The CancelMoose[tm] on autopilot. The CancelMoose[tm] is reputed to be
12217 Norwegian, and was the person(s) who invented NoCeM.
12219 @item jem@@xpat.com;
12221 Jem---Korean despammer who is getting very busy these days.
12223 @item red@@redpoll.mrfs.oh.us (Richard E. Depew)
12224 Richard E. Depew---lone American despammer. He mostly cancels binary
12225 postings to non-binary groups and removes spews (regurgitated articles).
12228 You do not have to heed NoCeM messages from all these people---just the
12229 ones you want to listen to.
12231 @item gnus-nocem-directory
12232 @vindex gnus-nocem-directory
12233 This is where Gnus will store its NoCeM cache files. The default is
12234 @file{~/News/NoCeM/}.
12236 @item gnus-nocem-expiry-wait
12237 @vindex gnus-nocem-expiry-wait
12238 The number of days before removing old NoCeM entries from the cache.
12239 The default is 15. If you make it shorter Gnus will be faster, but you
12240 might then see old spam.
12248 So... You want to slow down your news reader even more! This is a
12249 good way to do so. Its also a great way to impress people staring
12250 over your shoulder as you read news.
12253 * Picon Basics:: What are picons and How do I get them.
12254 * Picon Requirements:: Don't go further if you aren't using XEmacs.
12255 * Easy Picons:: Displaying Picons---the easy way.
12256 * Hard Picons:: The way you should do it. You'll learn something.
12257 * Picon Configuration:: Other variables you can trash/tweak/munge/play with.
12262 @subsection Picon Basics
12264 What are Picons? To quote directly from the Picons Web site
12265 (@samp{http://www.cs.indiana.edu/picons/ftp/index.html}):
12268 @dfn{Picons} is short for ``personal icons''. They're small,
12269 constrained images used to represent users and domains on the net,
12270 organized into databases so that the appropriate image for a given
12271 e-mail address can be found. Besides users and domains, there are picon
12272 databases for Usenet newsgroups and weather forecasts. The picons are
12273 in either monochrome @code{XBM} format or color @code{XPM} and
12274 @code{GIF} formats.
12277 Please see the above mentioned web site for instructions on obtaining
12278 and installing the picons databases, or the following ftp site:
12279 @samp{http://www.cs.indiana.edu/picons/ftp/index.html}.
12281 @vindex gnus-picons-database
12282 Gnus expects picons to be installed into a location pointed to by
12283 @code{gnus-picons-database}.
12286 @node Picon Requirements
12287 @subsection Picon Requirements
12289 To use have Gnus display Picons for you, you must be running XEmacs
12290 19.13 or greater since all other versions of Emacs aren't yet able to
12293 Additionally, you must have @code{xpm} support compiled into XEmacs.
12295 @vindex gnus-picons-convert-x-face
12296 If you want to display faces from @code{X-Face} headers, you must have
12297 the @code{netpbm} utilities installed, or munge the
12298 @code{gnus-picons-convert-x-face} variable to use something else.
12302 @subsection Easy Picons
12304 To enable displaying picons, simply put the following line in your
12305 @file{~/.gnus} file and start Gnus.
12308 (setq gnus-use-picons t)
12309 (add-hook 'gnus-article-display-hook 'gnus-article-display-picons t)
12310 (add-hook 'gnus-summary-prepare-hook 'gnus-group-display-picons t)
12311 (add-hook 'gnus-article-display-hook 'gnus-picons-article-display-x-face)
12316 @subsection Hard Picons
12318 Gnus can display picons for you as you enter and leave groups and
12319 articles. It knows how to interact with three sections of the picons
12320 database. Namely, it can display the picons newsgroup pictures,
12321 author's face picture(s), and the authors domain. To enable this
12322 feature, you need to first decide where to display them.
12326 @item gnus-picons-display-where
12327 @vindex gnus-picons-display-where
12328 Where the picon images should be displayed. It is @code{picons} by
12329 default (which by default maps to the buffer @samp{*Picons*}). Other
12330 valid places could be @code{article}, @code{summary}, or
12331 @samp{"*scratch*"} for all I care. Just make sure that you've made the
12332 buffer visible using the standard Gnus window configuration
12333 routines---@xref{Windows Configuration}.
12337 Note: If you set @code{gnus-use-picons} to @code{t}, it will set up your
12338 window configuration for you to include the @code{picons} buffer.
12340 Now that you've made that decision, you need to add the following
12341 functions to the appropriate hooks so these pictures will get
12342 displayed at the right time.
12344 @vindex gnus-article-display-hook
12345 @vindex gnus-picons-display-where
12347 @item gnus-article-display-picons
12348 @findex gnus-article-display-picons
12349 Looks up and display the picons for the author and the author's domain
12350 in the @code{gnus-picons-display-where} buffer. Should be added to
12351 the @code{gnus-article-display-hook}.
12353 @item gnus-group-display-picons
12354 @findex gnus-article-display-picons
12355 Displays picons representing the current group. This function should
12356 be added to the @code{gnus-summary-prepare-hook} or to the
12357 @code{gnus-article-display-hook} if @code{gnus-picons-display-where}
12358 is set to @code{article}.
12360 @item gnus-picons-article-display-x-face
12361 @findex gnus-article-display-picons
12362 Decodes and displays the X-Face header if present. This function
12363 should be added to @code{gnus-article-display-hook}.
12367 Note: You must append them to the hook, so make sure to specify 't'
12368 to the append flag of @code{add-hook}:
12371 (add-hook 'gnus-article-display-hook 'gnus-article-display-picons t)
12375 @node Picon Configuration
12376 @subsection Picon Configuration
12378 The following variables offer further control over how things are
12379 done, where things are located, and other useless stuff you really
12380 don't need to worry about.
12383 @item gnus-picons-database
12384 @vindex gnus-picons-database
12385 The location of the picons database. Should point to a directory
12386 containing the @file{news}, @file{domains}, @file{users} (and so on)
12387 subdirectories. Defaults to @file{/usr/local/faces}.
12389 @item gnus-picons-news-directory
12390 @vindex gnus-picons-news-directory
12391 Sub-directory of the faces database containing the icons for
12394 @item gnus-picons-user-directories
12395 @vindex gnus-picons-user-directories
12396 List of subdirectories to search in @code{gnus-picons-database} for user
12397 faces. Defaults to @code{("local" "users" "usenix" "misc/MISC")}.
12399 @item gnus-picons-domain-directories
12400 @vindex gnus-picons-domain-directories
12401 List of subdirectories to search in @code{gnus-picons-database} for
12402 domain name faces. Defaults to @code{("domains")}. Some people may
12403 want to add @samp{unknown} to this list.
12405 @item gnus-picons-convert-x-face
12406 @vindex gnus-picons-convert-x-face
12407 The command to use to convert the @code{X-Face} header to an X bitmap
12408 (@code{xbm}). Defaults to @code{(format "@{ echo '/* Width=48,
12409 Height=48 */'; uncompface; @} | icontopbm | pbmtoxbm > %s"
12410 gnus-picons-x-face-file-name)}
12412 @item gnus-picons-x-face-file-name
12413 @vindex gnus-picons-x-face-file-name
12414 Names a temporary file to store the @code{X-Face} bitmap in. Defaults
12415 to @code{(format "/tmp/picon-xface.%s.xbm" (user-login-name))}.
12417 @item gnus-picons-buffer
12418 @vindex gnus-picons-buffer
12419 The name of the buffer that @code{picons} points to. Defaults to
12420 @samp{*Icon Buffer*}.
12426 @section Moderation
12429 If you are a moderator, you can use the @file{gnus-mdrtn.el} package.
12430 It is not included in the standard Gnus package. Write a mail to
12431 @samp{larsi@@ifi.uio.no} and state what group you moderate, and you'll
12434 The moderation package is implemented as a minor mode for summary
12438 (add-hook 'gnus-summary-mode-hook 'gnus-moderate)
12441 in your @file{.gnus.el} file.
12443 If you are the moderation of @samp{rec.zoofle}, this is how it's
12448 You split your incoming mail by matching on
12449 @samp{Newsgroups:.*rec.zoofle}, which will put all the to-be-posted
12450 articles in some mail group---@samp{nnml:rec.zoofle}, for instance.
12453 You enter that group once in a while and post articles using the @kbd{e}
12454 (edit-and-post) or @kbd{s} (just send unedited) commands.
12457 If, while reading the @samp{rec.zoofle} newsgroup, you happen upon some
12458 articles that weren't approved by you, you can cancel them with the
12462 To use moderation mode in these two groups, say:
12465 (setq gnus-moderatated-groups
12466 "^nnml:rec.zoofle$\\|^rec.zoofle$")
12470 @node XEmacs Enhancements
12471 @section XEmacs Enhancements
12474 XEmacs is able to display pictures and stuff, so Gnus has taken
12475 advantage of that. Relevant variables include:
12478 @item gnus-xmas-glyph-directory
12479 @vindex gnus-xmas-glyph-directory
12480 This is where Gnus will look for pictures. Gnus will normally
12481 auto-detect this directory, but you may set it manually if you have an
12482 unusual directory structure.
12484 @item gnus-xmas-logo-color-alist
12485 @vindex gnus-xmas-logo-color-alist
12486 This is an alist where the key is a type symbol and the values are the
12487 foreground and background color of the splash page glyph.
12489 @item gnus-xmas-logo-color-style
12490 @vindex gnus-xmas-logo-color-style
12491 This is the key used to look up the color in the alist described above.
12492 Legal values include @code{flame}, @code{pine}, @code{moss},
12493 @code{irish}, @code{sky}, @code{tin}, @code{velvet}, @code{grape},
12494 @code{labia}, @code{berry}, @code{neutral}, and @code{september}.
12496 @item gnus-use-toolbar
12497 @vindex gnus-use-toolbar
12498 If @code{nil}, don't display toolbars. If non-@code{nil}, it should be
12499 one of @code{default-toolbar}, @code{top-toolbar}, @code{bottom-toolbar},
12500 @code{right-toolbar}, or @code{left-toolbar}.
12502 @item gnus-group-toolbar
12503 @vindex gnus-group-toolbar
12504 The toolbar in the group buffer.
12506 @item gnus-summary-toolbar
12507 @vindex gnus-summary-toolbar
12508 The toolbar in the summary buffer.
12510 @item gnus-summary-mail-toolbar
12511 @vindex gnus-summary-mail-toolbar
12512 The toolbar in the summary buffer of mail groups.
12514 @item gnus-xmas-modeline-glyph
12515 @vindex gnus-xmas-modeline-glyph
12516 A glyph dislayed in all Gnus mode lines. It is a tiny gnu head by
12522 @node Various Various
12523 @section Various Various
12529 @item gnus-directory
12530 @vindex gnus-directory
12531 All Gnus directories will be initialized from this variable, which
12532 defaults to the @samp{SAVEDIR} environment variable, or @file{~/News/}
12533 if that variable isn't set.
12535 @item gnus-default-directory
12536 @vindex gnus-default-directory
12537 Not related to the above variable at all---this variable says what the
12538 default directory of all Gnus buffers should be. If you issue commands
12539 like @kbd{C-x C-f}, the prompt you'll get starts in the current buffer's
12540 default directory. If this variable is @code{nil} (which is the
12541 default), the default directory will be the default directory of the
12542 buffer you were in when you started Gnus.
12545 @vindex gnus-verbose
12546 This variable is an integer between zero and ten. The higher the value,
12547 the more messages will be displayed. If this variable is zero, Gnus
12548 will never flash any messages, if it is seven (which is the default),
12549 most important messages will be shown, and if it is ten, Gnus won't ever
12550 shut up, but will flash so many messages it will make your head swim.
12552 @item gnus-verbose-backends
12553 @vindex gnus-verbose-backends
12554 This variable works the same way as @code{gnus-verbose}, but it applies
12555 to the Gnus backends instead of Gnus proper.
12557 @item nnheader-max-head-length
12558 @vindex nnheader-max-head-length
12559 When the backends read straight heads of articles, they all try to read
12560 as little as possible. This variable (default @code{4096}) specifies
12561 the absolute max length the backends will try to read before giving up
12562 on finding a separator line between the head and the body. If this
12563 variable is @code{nil}, there is no upper read bound. If it is
12564 @code{t}, the backends won't try to read the articles piece by piece,
12565 but read the entire articles. This makes sense with some versions of
12568 @item nnheader-file-name-translation-alist
12569 @vindex nnheader-file-name-translation-alist
12571 @cindex illegal characters in file names
12572 @cindex characters in file names
12573 This is an alist that says how to translate characters in file names.
12574 For instance, if @samp{:} is illegal as a file character in file names
12575 on your system (you OS/2 user you), you could say something like:
12578 (setq nnheader-file-name-translation-alist
12582 In fact, this is the default value for this variable on OS/2 and MS
12583 Windows (phooey) systems.
12585 @item gnus-hidden-properties
12586 @vindex gnus-hidden-properties
12587 This is a list of properties to use to hide ``invisible'' text. It is
12588 @code{(invisible t intangible t)} by default on most systems, which
12589 makes invisible text invisible and intangible.
12591 @item gnus-parse-headers-hook
12592 @vindex gnus-parse-headers-hook
12593 A hook called before parsing headers. It can be used, for instance, to
12594 gather statistics on the headers fetched, or perhaps you'd like to prune
12595 some headers. I don't see why you'd want that, though.
12597 @item gnus-shell-command-separator
12598 @vindex gnus-shell-command-separator
12599 String used to separate to shell commands. The default is @samp{;}.
12608 Well, that's the manual---you can get on with your life now. Keep in
12609 touch. Say hello to your cats from me.
12611 My @strong{ghod}---I just can't stand goodbyes. Sniffle.
12613 Ol' Charles Reznikoff said it pretty well, so I leave the floor to him:
12618 Not because of victories @*
12621 but for the common sunshine,@*
12623 the largess of the spring.
12626 but for the day's work done@*
12627 as well as I was able;@*
12628 not for a seat upon the dais@*
12629 but at the common table.@*
12634 @chapter Appendices
12637 * History:: How Gnus got where it is today.
12638 * Terminology:: We use really difficult, like, words here.
12639 * Customization:: Tailoring Gnus to your needs.
12640 * Troubleshooting:: What you might try if things do not work.
12641 * A Programmers Guide to Gnus:: Rilly, rilly technical stuff.
12642 * Emacs for Heathens:: A short introduction to Emacsian terms.
12643 * Frequently Asked Questions:: A question-and-answer session.
12651 @sc{gnus} was written by Masanobu @sc{Umeda}. When autumn crept up in
12652 '94, Lars Magne Ingebrigtsen grew bored and decided to rewrite Gnus.
12654 If you want to investigate the person responsible for this outrage, you
12655 can point your (feh!) web browser to
12656 @file{http://www.ifi.uio.no/~larsi/}. This is also the primary
12657 distribution point for the new and spiffy versions of Gnus, and is known
12658 as The Site That Destroys Newsrcs And Drives People Mad.
12660 During the first extended alpha period of development, the new Gnus was
12661 called ``(ding) Gnus''. @dfn{(ding)}, is, of course, short for
12662 @dfn{ding is not Gnus}, which is a total and utter lie, but who cares?
12663 (Besides, the ``Gnus'' in this abbreviation should probably be
12664 pronounced ``news'' as @sc{Umeda} intended, which makes it a more
12665 appropriate name, don't you think?)
12667 In any case, after spending all that energy on coming up with a new and
12668 spunky name, we decided that the name was @emph{too} spunky, so we
12669 renamed it back again to ``Gnus''. But in mixed case. ``Gnus'' vs.
12670 ``@sc{gnus}''. New vs. old.
12672 The first ``proper'' release of Gnus 5 was done in November 1995 when it
12673 was included in the Emacs 19.30 distribution.
12675 In May 1996 the next Gnus generation (aka. ``September Gnus'') was
12676 released under the name ``Gnus 5.2''.
12678 On July 28th 1996 work on Red Gnus was begun.
12681 * Why?:: What's the point of Gnus?
12682 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
12683 * Conformity:: Gnus tries to conform to all standards.
12684 * Emacsen:: Gnus can be run on a few modern Emacsen.
12685 * Contributors:: Oodles of people.
12686 * New Features:: Pointers to some of the new stuff in Gnus.
12687 * Newest Features:: Features so new that they haven't been written yet.
12694 What's the point of Gnus?
12696 I want to provide a ``rad'', ``happening'', ``way cool'' and ``hep''
12697 newsreader, that lets you do anything you can think of. That was my
12698 original motivation, but while working on Gnus, it has become clear to
12699 me that this generation of newsreaders really belong in the stone age.
12700 Newsreaders haven't developed much since the infancy of the net. If the
12701 volume continues to rise with the current rate of increase, all current
12702 newsreaders will be pretty much useless. How do you deal with
12703 newsgroups that have thousands of new articles each day? How do you
12704 keep track of millions of people who post?
12706 Gnus offers no real solutions to these questions, but I would very much
12707 like to see Gnus being used as a testing ground for new methods of
12708 reading and fetching news. Expanding on @sc{Umeda}-san's wise decision
12709 to separate the newsreader from the backends, Gnus now offers a simple
12710 interface for anybody who wants to write new backends for fetching mail
12711 and news from different sources. I have added hooks for customizations
12712 everywhere I could imagine useful. By doing so, I'm inviting every one
12713 of you to explore and invent.
12715 May Gnus never be complete. @kbd{C-u 100 M-x hail-emacs}.
12718 @node Compatibility
12719 @subsection Compatibility
12721 @cindex compatibility
12722 Gnus was designed to be fully compatible with @sc{gnus}. Almost all key
12723 bindings have been kept. More key bindings have been added, of course,
12724 but only in one or two obscure cases have old bindings been changed.
12729 @center In a cloud bones of steel.
12733 All commands have kept their names. Some internal functions have changed
12736 The @code{gnus-uu} package has changed drastically. @pxref{Decoding
12739 One major compatibility question is the presence of several summary
12740 buffers. All variables that are relevant while reading a group are
12741 buffer-local to the summary buffer they belong in. Although many
12742 important variables have their values copied into their global
12743 counterparts whenever a command is executed in the summary buffer, this
12744 change might lead to incorrect values being used unless you are careful.
12746 All code that relies on knowledge of @sc{gnus} internals will probably
12747 fail. To take two examples: Sorting @code{gnus-newsrc-alist} (or
12748 changing it in any way, as a matter of fact) is strictly verboten. Gnus
12749 maintains a hash table that points to the entries in this alist (which
12750 speeds up many functions), and changing the alist directly will lead to
12754 @cindex highlighting
12755 Old hilit19 code does not work at all. In fact, you should probably
12756 remove all hilit code from all Gnus hooks
12757 (@code{gnus-group-prepare-hook} and @code{gnus-summary-prepare-hook}).
12758 Gnus provides various integrated functions for highlighting. These are
12759 faster and more accurate. To make life easier for everybody, Gnus will
12760 by default remove all hilit calls from all hilit hooks. Uncleanliness!
12763 Packages like @code{expire-kill} will no longer work. As a matter of
12764 fact, you should probably remove all old @sc{gnus} packages (and other
12765 code) when you start using Gnus. More likely than not, Gnus already
12766 does what you have written code to make @sc{gnus} do. (Snicker.)
12768 Even though old methods of doing things are still supported, only the
12769 new methods are documented in this manual. If you detect a new method of
12770 doing something while reading this manual, that does not mean you have
12771 to stop doing it the old way.
12773 Gnus understands all @sc{gnus} startup files.
12775 @kindex M-x gnus-bug
12777 @cindex reporting bugs
12779 Overall, a casual user who hasn't written much code that depends on
12780 @sc{gnus} internals should suffer no problems. If problems occur,
12781 please let me know by issuing that magic command @kbd{M-x gnus-bug}.
12785 @subsection Conformity
12787 No rebels without a clue here, ma'am. We conform to all standards known
12788 to (wo)man. Except for those standards and/or conventions we disagree
12795 There are no known breaches of this standard.
12799 There are no known breaches of this standard, either.
12801 @item Good Net-Keeping Seal of Approval
12802 @cindex Good Net-Keeping Seal of Approval
12803 Gnus has been through the Seal process and failed. I think it'll pass
12804 the next inspection.
12806 @item Son-of-RFC 1036
12807 @cindex Son-of-RFC 1036
12808 We do have some breaches to this one.
12813 Gnus does no MIME handling, and this standard-to-be seems to think that
12814 MIME is the bees' knees, so we have major breakage here.
12817 This is considered to be a ``vanity header'', while I consider it to be
12818 consumer information. After seeing so many badly formatted articles
12819 coming from @code{tin} and @code{Netscape} I know not to use either of
12820 those for posting articles. I would not have known that if it wasn't
12821 for the @code{X-Newsreader} header.
12824 Gnus does line breaking on this header. I infer from RFC1036 that being
12825 conservative in what you output is not creating 5000-character lines, so
12826 it seems like a good idea to me. However, this standard-to-be says that
12827 whitespace in the @code{References} header is to be preserved, so... It
12828 doesn't matter one way or the other to Gnus, so if somebody tells me
12829 what The Way is, I'll change it. Or not.
12834 If you ever notice Gnus acting non-compliantly with regards to the texts
12835 mentioned above, don't hesitate to drop a note to Gnus Towers and let us
12840 @subsection Emacsen
12846 Gnus should work on :
12851 Emacs 19.30 and up.
12854 XEmacs 19.13 and up.
12857 Mule versions based on Emacs 19.30 and up.
12861 Gnus will absolutely not work on any Emacsen older than that. Not
12862 reliably, at least.
12864 There are some vague differences between Gnus on the various platforms:
12869 The mouse-face on Gnus lines under Emacs and Mule is delimited to
12870 certain parts of the lines while they cover the entire line under
12874 The same with current-article marking---XEmacs puts an underline under
12875 the entire summary line while Emacs and Mule are nicer and kinder.
12878 XEmacs features more graphics---a logo and a toolbar.
12881 Citation highlighting us better under Emacs and Mule than under XEmacs.
12884 Emacs 19.26-19.28 have tangible hidden headers, which can be a bit
12891 @subsection Contributors
12892 @cindex contributors
12894 The new Gnus version couldn't have been done without the help of all the
12895 people on the (ding) mailing list. Every day for over a year I have
12896 gotten billions of nice bug reports from them, filling me with joy,
12897 every single one of them. Smooches. The people on the list have been
12898 tried beyond endurance, what with my ``oh, that's a neat idea <type
12899 type>, yup, I'll release it right away <ship off> no wait, that doesn't
12900 work at all <type type>, yup, I'll ship that one off right away <ship
12901 off> no, wait, that absolutely does not work'' policy for releases.
12902 Micro$oft---bah. Amateurs. I'm @emph{much} worse. (Or is that
12903 ``worser''? ``much worser''? ``worsest''?)
12905 I would like to take this opportunity to thank the Academy for... oops,
12910 @item Masanobu @sc{Umeda}
12911 The writer of the original @sc{gnus}.
12913 @item Per Abrahamsen
12914 Custom, scoring, highlighting and @sc{soup} code (as well as numerous
12917 @item Luis Fernandes
12918 Design and graphics.
12921 @file{gnus-picon.el} and the manual section on @dfn{picons}
12925 @file{gnus-gl.el} and the GroupLens manual section (@pxref{GroupLens}).
12927 @item Sudish Joseph
12928 Innumerable bug fixes.
12931 @file{gnus-topic.el}.
12933 @item Steven L. Baur
12934 Lots and lots of bugs detections and fixes.
12936 @item Vladimir Alexiev
12937 The refcard and reference booklets.
12939 @item Felix Lee & JWZ
12940 I stole some pieces from the XGnus distribution by Felix Lee and JWZ.
12943 @file{nnfolder.el} enhancements & rewrite.
12945 @item Peter Mutsaers
12946 Orphan article scoring code.
12951 @item Hallvard B Furuseth
12952 Various bits and pieces, especially dealing with .newsrc files.
12954 @item Brian Edmonds
12955 @file{gnus-bbdb.el}.
12957 @item Ricardo Nassif and Mark Borges
12960 @item Kevin Davidson
12961 Came up with the name @dfn{ding}, so blame him.
12965 Peter Arius, Stainless Steel Rat, Ulrik Dickow, Jack Vinson, Daniel
12966 Quinlan, Frank D. Cringle, Geoffrey T. Dairiki, Fabrice Popineau and
12967 Andrew Eskilsson have all contributed code and suggestions.
12971 @subsection New Features
12972 @cindex new features
12977 The look of all buffers can be changed by setting format-like variables
12978 (@pxref{Group Buffer Format} and @pxref{Summary Buffer Format}).
12981 Local spool and several @sc{nntp} servers can be used at once
12982 (@pxref{Select Methods}).
12985 You can combine groups into virtual groups (@pxref{Virtual Groups}).
12988 You can read a number of different mail formats (@pxref{Getting Mail}).
12989 All the mail backends implement a convenient mail expiry scheme
12990 (@pxref{Expiring Mail}).
12993 Gnus can use various strategies for gathering threads that have lost
12994 their roots (thereby gathering loose sub-threads into one thread) or it
12995 can go back and retrieve enough headers to build a complete thread
12996 (@pxref{Customizing Threading}).
12999 Killed groups can be displayed in the group buffer, and you can read
13000 them as well (@pxref{Listing Groups}).
13003 Gnus can do partial group updates---you do not have to retrieve the
13004 entire active file just to check for new articles in a few groups
13005 (@pxref{The Active File}).
13008 Gnus implements a sliding scale of subscribedness to groups
13009 (@pxref{Group Levels}).
13012 You can score articles according to any number of criteria
13013 (@pxref{Scoring}). You can even get Gnus to find out how to score
13014 articles for you (@pxref{Adaptive Scoring}).
13017 Gnus maintains a dribble buffer that is auto-saved the normal Emacs
13018 manner, so it should be difficult to lose much data on what you have
13019 read if your machine should go down (@pxref{Auto Save}).
13022 Gnus now has its own startup file (@file{.gnus}) to avoid cluttering up
13023 the @file{.emacs} file.
13026 You can set the process mark on both groups and articles and perform
13027 operations on all the marked items (@pxref{Process/Prefix}).
13030 You can grep through a subset of groups and create a group from the
13031 results (@pxref{Kibozed Groups}).
13034 You can list subsets of groups according to, well, anything
13035 (@pxref{Listing Groups}).
13038 You can browse foreign servers and subscribe to groups from those
13039 servers (@pxref{Browse Foreign Server}).
13042 Gnus can fetch articles asynchronously on a second connection to the
13043 server (@pxref{Asynchronous Fetching}).
13046 You can cache articles locally (@pxref{Article Caching}).
13049 The uudecode functions have been expanded and generalized
13050 (@pxref{Decoding Articles}).
13053 You can still post uuencoded articles, which was a little-known feature
13054 of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
13057 Fetching parents (and other articles) now actually works without
13058 glitches (@pxref{Finding the Parent}).
13061 Gnus can fetch FAQs and group descriptions (@pxref{Group Information}).
13064 Digests (and other files) can be used as the basis for groups
13065 (@pxref{Document Groups}).
13068 Articles can be highlighted and customized (@pxref{Customizing
13072 URLs and other external references can be buttonized (@pxref{Article
13076 You can do lots of strange stuff with the Gnus window & frame
13077 configuration (@pxref{Windows Configuration}).
13080 You can click on buttons instead of using the keyboard
13084 Gnus can use NoCeM files to weed out spam (@pxref{NoCeM}).
13088 This is, of course, just a @emph{short} overview of the @emph{most}
13089 important new features. No, really. There are tons more. Yes, we have
13090 feeping creaturism in full effect, but nothing too gratuitous, I would
13094 @node Newest Features
13095 @subsection Newest Features
13098 Also known as the @dfn{todo list}. Sure to be implemented before the
13101 Be afraid. Be very afraid.
13105 Native @sc{mime} support is something that should be done.
13107 A better and simpler method for specifying mail composing methods.
13109 Allow posting through mail-to-news gateways.
13111 Really do unbinhexing.
13114 And much, much, much more. There is more to come than has already been
13115 implemented. (But that's always true, isn't it?)
13117 @code{<URL:http://www.ifi.uio.no/~larsi/sgnus/todo>} is where the actual
13118 up-to-the-second todo list is located, so if you're really curious, you
13119 could point your Web browser over that-a-way.
13123 @section Terminology
13125 @cindex terminology
13130 This is what you are supposed to use this thing for---reading news.
13131 News is generally fetched from a nearby @sc{nntp} server, and is
13132 generally publicly available to everybody. If you post news, the entire
13133 world is likely to read just what you have written, and they'll all
13134 snigger mischievously. Behind your back.
13138 Everything that's delivered to you personally is mail. Some news/mail
13139 readers (like Gnus) blur the distinction between mail and news, but
13140 there is a difference. Mail is private. News is public. Mailing is
13141 not posting, and replying is not following up.
13145 Send a mail to the person who has written what you are reading.
13149 Post an article to the current newsgroup responding to the article you
13154 Gnus gets fed articles from a number of backends, both news and mail
13155 backends. Gnus does not handle the underlying media, so to speak---this
13156 is all done by the backends.
13160 Gnus will always use one method (and backend) as the @dfn{native}, or
13161 default, way of getting news.
13165 You can also have any number of foreign groups active at the same time.
13166 These are groups that use different backends for getting news.
13170 Secondary backends are somewhere half-way between being native and being
13171 foreign, but they mostly act like they are native.
13175 A nessage that has been posted as news.
13178 @cindex mail message
13179 A message that has been mailed.
13183 A mail message or news article
13187 The top part of a message, where administrative information (etc.) is
13192 The rest of an article. Everything that is not in the head is in the
13197 A line from the head of an article.
13201 A collection of such lines, or a collection of heads. Or even a
13202 collection of @sc{nov} lines.
13206 When Gnus enters a group, it asks the backend for the headers of all
13207 unread articles in the group. Most servers support the News OverView
13208 format, which is more compact and much faster to read and parse than the
13209 normal @sc{head} format.
13213 Each group is subscribed at some @dfn{level} or other (1-9). The ones
13214 that have a lower level are ``more'' subscribed than the groups with a
13215 higher level. In fact, groups on levels 1-5 are considered
13216 @dfn{subscribed}; 6-7 are @dfn{unsubscribed}; 8 are @dfn{zombies}; and 9
13217 are @dfn{killed}. Commands for listing groups and scanning for new
13218 articles will all use the numeric prefix as @dfn{working level}.
13220 @item killed groups
13221 @cindex killed groups
13222 No information on killed groups is stored or updated, which makes killed
13223 groups much easier to handle than subscribed groups.
13225 @item zombie groups
13226 @cindex zombie groups
13227 Just like killed groups, only slightly less dead.
13230 @cindex active file
13231 The news server has to keep track of what articles it carries, and what
13232 groups exist. All this information in stored in the active file, which
13233 is rather large, as you might surmise.
13236 @cindex bogus groups
13237 A group that exists in the @file{.newsrc} file, but isn't known to the
13238 server (i. e., it isn't in the active file), is a @emph{bogus group}.
13239 This means that the group probably doesn't exist (any more).
13243 A machine than one can connect to and get news (or mail) from.
13245 @item select method
13246 @cindex select method
13247 A structure that specifies the backend, the server and the virtual
13250 @item virtual server
13251 @cindex virtual server
13252 A named select method. Since a select methods defines all there is to
13253 know about connecting to a (physical) server, taking the who things as a
13254 whole is a virtual server.
13259 @node Customization
13260 @section Customization
13261 @cindex general customization
13263 All variables are properly documented elsewhere in this manual. This
13264 section is designed to give general pointers on how to customize Gnus
13265 for some quite common situations.
13268 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
13269 * Slow Terminal Connection:: You run a remote Emacs.
13270 * Little Disk Space:: You feel that having large setup files is icky.
13271 * Slow Machine:: You feel like buying a faster machine.
13275 @node Slow/Expensive Connection
13276 @subsection Slow/Expensive @sc{nntp} Connection
13278 If you run Emacs on a machine locally, and get your news from a machine
13279 over some very thin strings, you want to cut down on the amount of data
13280 Gnus has to get from the @sc{nntp} server.
13284 @item gnus-read-active-file
13285 Set this to @code{nil}, which will inhibit Gnus from requesting the
13286 entire active file from the server. This file is often v. large. You
13287 also have to set @code{gnus-check-new-news} and
13288 @code{gnus-check-bogus-newsgroups} to @code{nil} to make sure that Gnus
13289 doesn't suddenly decide to fetch the active file anyway.
13291 @item gnus-nov-is-evil
13292 This one has to be @code{nil}. If not, grabbing article headers from
13293 the @sc{nntp} server will not be very fast. Not all @sc{nntp} servers
13294 support @sc{xover}; Gnus will detect this by itself.
13298 @node Slow Terminal Connection
13299 @subsection Slow Terminal Connection
13301 Let's say you use your home computer for dialing up the system that
13302 runs Emacs and Gnus. If your modem is slow, you want to reduce the
13303 amount of data that is sent over the wires as much as possible.
13307 @item gnus-auto-center-summary
13308 Set this to @code{nil} to inhibit Gnus from re-centering the summary
13309 buffer all the time. If it is @code{vertical}, do only vertical
13310 re-centering. If it is neither @code{nil} nor @code{vertical}, do both
13311 horizontal and vertical recentering.
13313 @item gnus-visible-headers
13314 Cut down on the headers that are included in the articles to the
13315 minimum. You can, in fact, make do without them altogether---most of the
13316 useful data is in the summary buffer, anyway. Set this variable to
13317 @samp{^NEVVVVER} or @samp{From:}, or whatever you feel you need.
13319 @item gnus-article-display-hook
13320 Set this hook to all the available hiding commands:
13322 (setq gnus-article-display-hook
13323 '(gnus-article-hide-headers gnus-article-hide-signature
13324 gnus-article-hide-citation))
13327 @item gnus-use-full-window
13328 By setting this to @code{nil}, you can make all the windows smaller.
13329 While this doesn't really cut down much generally, it means that you
13330 have to see smaller portions of articles before deciding that you didn't
13331 want to read them anyway.
13333 @item gnus-thread-hide-subtree
13334 If this is non-@code{nil}, all threads in the summary buffer will be
13337 @item gnus-updated-mode-lines
13338 If this is @code{nil}, Gnus will not put information in the buffer mode
13339 lines, which might save some time.
13343 @node Little Disk Space
13344 @subsection Little Disk Space
13347 The startup files can get rather large, so you may want to cut their
13348 sizes a bit if you are running out of space.
13352 @item gnus-save-newsrc-file
13353 If this is @code{nil}, Gnus will never save @file{.newsrc}---it will
13354 only save @file{.newsrc.eld}. This means that you will not be able to
13355 use any other newsreaders than Gnus. This variable is @code{t} by
13358 @item gnus-save-killed-list
13359 If this is @code{nil}, Gnus will not save the list of dead groups. You
13360 should also set @code{gnus-check-new-newsgroups} to @code{ask-server}
13361 and @code{gnus-check-bogus-newsgroups} to @code{nil} if you set this
13362 variable to @code{nil}. This variable is @code{t} by default.
13368 @subsection Slow Machine
13369 @cindex slow machine
13371 If you have a slow machine, or are just really impatient, there are a
13372 few things you can do to make Gnus run faster.
13374 Set@code{gnus-check-new-newsgroups} and
13375 @code{gnus-check-bogus-newsgroups} to @code{nil} to make startup faster.
13377 Set @code{gnus-show-threads}, @code{gnus-use-cross-reference} and
13378 @code{gnus-nov-is-evil} to @code{nil} to make entering and exiting the
13379 summary buffer faster.
13381 Set @code{gnus-article-display-hook} to @code{nil} to make article
13382 processing a bit faster.
13385 @node Troubleshooting
13386 @section Troubleshooting
13387 @cindex troubleshooting
13389 Gnus works @emph{so} well straight out of the box---I can't imagine any
13397 Make sure your computer is switched on.
13400 Make sure that you really load the current Gnus version. If you have
13401 been running @sc{gnus}, you need to exit Emacs and start it up again before
13405 Try doing an @kbd{M-x gnus-version}. If you get something that looks
13406 like @samp{Gnus v5.46; nntp 4.0} you have the right files loaded. If,
13407 on the other hand, you get something like @samp{NNTP 3.x} or @samp{nntp
13408 flee}, you have some old @file{.el} files lying around. Delete these.
13411 Read the help group (@kbd{G h} in the group buffer) for a FAQ and a
13415 @vindex max-lisp-eval-depth
13416 Gnus works on many recursive structures, and in some extreme (and very
13417 rare) cases Gnus may recurse down ``too deeply'' and Emacs will beep at
13418 you. If this happens to you, set @code{max-lisp-eval-depth} to 500 or
13419 something like that.
13422 If all else fails, report the problem as a bug.
13425 @cindex reporting bugs
13427 @kindex M-x gnus-bug
13429 If you find a bug in Gnus, you can report it with the @kbd{M-x gnus-bug}
13430 command. @kbd{M-x set-variable RET debug-on-error RET t RET}, and send
13431 me the backtrace. I will fix bugs, but I can only fix them if you send
13432 me a precise description as to how to reproduce the bug.
13434 You really can never be too detailed in a bug report. Always use the
13435 @kbd{M-x gnus-bug} command when you make bug reports, even if it creates
13436 a 10Kb mail each time you use it, and even if you have sent me your
13437 environment 500 times before. I don't care. I want the full info each
13440 It is also important to remember that I have no memory whatsoever. If
13441 you send a bug report, and I send you a reply, and then you send back
13442 just ``No, it's not! Moron!'', I will have no idea what you are
13443 insulting me about. Always over-explain everything. It's much easier
13444 for all of us---if I don't have all the information I need, I will just
13445 mail you and ask for more info, and everything takes more time.
13447 If the problem you're seeing is very visual, and you can't quite explain
13448 it, copy the Emacs window to a file (with @code{xwd}, for instance), put
13449 it somewhere it can be reached, and include the URL of the picture in
13452 If you just need help, you are better off asking on
13453 @samp{gnu.emacs.gnus}. I'm not very helpful.
13455 @cindex gnu.emacs.gnus
13456 @cindex ding mailing list
13457 You can also ask on the ding mailing list---@samp{ding@@ifi.uio.no}.
13458 Write to @samp{ding-request@@ifi.uio.no} to subscribe.
13461 @node A Programmers Guide to Gnus
13462 @section A Programmer's Guide to Gnus
13464 It is my hope that other people will figure out smart stuff that Gnus
13465 can do, and that other people will write those smart things as well. To
13466 facilitate that I thought it would be a good idea to describe the inner
13467 workings of Gnus. And some of the not-so-inner workings, while I'm at
13470 You can never expect the internals of a program not to change, but I
13471 will be defining (in some details) the interface between Gnus and its
13472 backends (this is written in stone), the format of the score files
13473 (ditto), data structures (some are less likely to change than others)
13474 and general method of operations.
13477 * Backend Interface:: How Gnus communicates with the servers.
13478 * Score File Syntax:: A BNF definition of the score file standard.
13479 * Headers:: How Gnus stores headers internally.
13480 * Ranges:: A handy format for storing mucho numbers.
13481 * Group Info:: The group info format.
13482 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
13483 * Various File Formats:: Formats of files that Gnus use.
13487 @node Backend Interface
13488 @subsection Backend Interface
13490 Gnus doesn't know anything about @sc{nntp}, spools, mail or virtual
13491 groups. It only knows how to talk to @dfn{virtual servers}. A virtual
13492 server is a @dfn{backend} and some @dfn{backend variables}. As examples
13493 of the first, we have @code{nntp}, @code{nnspool} and @code{nnmbox}. As
13494 examples of the latter we have @code{nntp-port-number} and
13495 @code{nnmbox-directory}.
13497 When Gnus asks for information from a backend---say @code{nntp}---on
13498 something, it will normally include a virtual server name in the
13499 function parameters. (If not, the backend should use the ``current''
13500 virtual server.) For instance, @code{nntp-request-list} takes a virtual
13501 server as its only (optional) parameter. If this virtual server hasn't
13502 been opened, the function should fail.
13504 Note that a virtual server name has no relation to some physical server
13505 name. Take this example:
13509 (nntp-address "ifi.uio.no")
13510 (nntp-port-number 4324))
13513 Here the virtual server name is @samp{odd-one} while the name of
13514 the physical server is @samp{ifi.uio.no}.
13516 The backends should be able to switch between several virtual servers.
13517 The standard backends implement this by keeping an alist of virtual
13518 server environments that it pulls down/pushes up when needed.
13520 There are two groups of interface functions: @dfn{required functions},
13521 which must be present, and @dfn{optional functions}, which Gnus will
13522 always check whether are present before attempting to call.
13524 All these functions are expected to return data in the buffer
13525 @code{nntp-server-buffer} (@samp{ *nntpd*}), which is somewhat
13526 unfortunately named, but we'll have to live with it. When I talk about
13527 @dfn{resulting data}, I always refer to the data in that buffer. When I
13528 talk about @dfn{return value}, I talk about the function value returned by
13529 the function call. Functions that fail should return @code{nil} as the
13532 Some backends could be said to be @dfn{server-forming} backends, and
13533 some might be said to not be. The latter are backends that generally
13534 only operate on one group at a time, and have no concept of ``server''
13535 -- they have a group, and they deliver info on that group and nothing
13538 In the examples and definitions I will refer to the imaginary backend
13541 @cindex @code{nnchoke}
13544 * Required Backend Functions:: Functions that must be implemented.
13545 * Optional Backend Functions:: Functions that need not be implemented.
13546 * Error Messaging:: How to get messages and report errors.
13547 * Writing New Backends:: Extending old backends.
13548 * Hooking New Backends Into Gnus:: What has to be done on the Gnus end.
13552 @node Required Backend Functions
13553 @subsubsection Required Backend Functions
13557 @item (nnchoke-retrieve-headers ARTICLES &optional GROUP SERVER FETCH-OLD)
13559 @var{articles} is either a range of article numbers or a list of
13560 @code{Message-ID}s. Current backends do not fully support either---only
13561 sequences (lists) of article numbers, and most backends do not support
13562 retrieval of @code{Message-ID}s. But they should try for both.
13564 The result data should either be HEADs or NOV lines, and the result
13565 value should either be @code{headers} or @code{nov} to reflect this.
13566 This might later be expanded to @code{various}, which will be a mixture
13567 of HEADs and NOV lines, but this is currently not supported by Gnus.
13569 If @var{fetch-old} is non-@code{nil} it says to try to fetch "extra
13570 headers, in some meaning of the word. This is generally done by
13571 fetching (at most) @var{fetch-old} extra headers less than the smallest
13572 article number in @code{articles}, and fill in the gaps as well. The
13573 presence of this parameter can be ignored if the backend finds it
13574 cumbersome to follow the request. If this is non-@code{nil} and not a
13575 number, do maximum fetches.
13577 Here's an example HEAD:
13580 221 1056 Article retrieved.
13581 Path: ifi.uio.no!sturles
13582 From: sturles@@ifi.uio.no (Sturle Sunde)
13583 Newsgroups: ifi.discussion
13584 Subject: Re: Something very droll
13585 Date: 27 Oct 1994 14:02:57 +0100
13586 Organization: Dept. of Informatics, University of Oslo, Norway
13588 Message-ID: <38o8e1$a0o@@holmenkollen.ifi.uio.no>
13589 References: <38jdmq$4qu@@visbur.ifi.uio.no>
13590 NNTP-Posting-Host: holmenkollen.ifi.uio.no
13594 So a @code{headers} return value would imply that there's a number of
13595 these in the data buffer.
13597 Here's a BNF definition of such a buffer:
13601 head = error / valid-head
13602 error-message = [ "4" / "5" ] 2number " " <error message> eol
13603 valid-head = valid-message *header "." eol
13604 valid-message = "221 " <number> " Article retrieved." eol
13605 header = <text> eol
13608 If the return value is @code{nov}, the data buffer should contain
13609 @dfn{network overview database} lines. These are basically fields
13613 nov-buffer = *nov-line
13614 nov-line = 8*9 [ field <TAB> ] eol
13615 field = <text except TAB>
13618 For a closer explanation what should be in those fields,
13622 @item (nnchoke-open-server SERVER &optional DEFINITIONS)
13624 @var{server} is here the virtual server name. @var{definitions} is a
13625 list of @code{(VARIABLE VALUE)} pairs that defines this virtual server.
13627 If the server can't be opened, no error should be signaled. The backend
13628 may then choose to refuse further attempts at connecting to this
13629 server. In fact, it should do so.
13631 If the server is opened already, this function should return a
13632 non-@code{nil} value. There should be no data returned.
13635 @item (nnchoke-close-server &optional SERVER)
13637 Close connection to @var{server} and free all resources connected
13638 to it. Return @code{nil} if the server couldn't be closed for some
13641 There should be no data returned.
13644 @item (nnchoke-request-close)
13646 Close connection to all servers and free all resources that the backend
13647 have reserved. All buffers that have been created by that backend
13648 should be killed. (Not the @code{nntp-server-buffer}, though.) This
13649 function is generally only called when Gnus is shutting down.
13651 There should be no data returned.
13654 @item (nnchoke-server-opened &optional SERVER)
13656 If @var{server} is the current virtual server, and the connection to the
13657 physical server is alive, then this function should return a
13658 non-@code{nil} vlue. This function should under no circumstances
13659 attempt to reconnect to a server that is has lost connection to.
13661 There should be no data returned.
13664 @item (nnchoke-status-message &optional SERVER)
13666 This function should return the last error message from @var{server}.
13668 There should be no data returned.
13671 @item (nnchoke-request-article ARTICLE &optional GROUP SERVER TO-BUFFER)
13673 The result data from this function should be the article specified by
13674 @var{article}. This might either be a @code{Message-ID} or a number.
13675 It is optional whether to implement retrieval by @code{Message-ID}, but
13676 it would be nice if that were possible.
13678 If @var{to-buffer} is non-@code{nil}, the result data should be returned
13679 in this buffer instead of the normal data buffer. This is to make it
13680 possible to avoid copying large amounts of data from one buffer to
13681 another, and Gnus mainly request articles to be inserted directly into
13682 its article buffer.
13684 If it is at all possible, this function should return a cons cell where
13685 the car is the group name the article was fetched from, and the cdr is
13686 the article number. This will enable Gnus to find out what the real
13687 group and article numbers are when fetching articles by
13688 @code{Message-ID}. If this isn't possible, @code{t} should be returned
13689 on successful article retrievement.
13692 @item (nnchoke-open-group GROUP &optional SERVER)
13694 Make @var{group} the current group.
13696 There should be no data returned by this function.
13699 @item (nnchoke-request-group GROUP &optional SERVER FAST)
13701 Get data on @var{group}. This function also has the side effect of
13702 making @var{group} the current group.
13704 If @var{FAST}, don't bother to return useful data, just make @var{group}
13707 Here's an example of some result data and a definition of the same:
13710 211 56 1000 1059 ifi.discussion
13713 The first number is the status, which should be @code{211}. Next is the
13714 total number of articles in the group, the lowest article number, the
13715 highest article number, and finally the group name. Note that the total
13716 number of articles may be less than one might think while just
13717 considering the highest and lowest article numbers, but some articles
13718 may have been canceled. Gnus just discards the total-number, so
13719 whether one should take the bother to generate it properly (if that is a
13720 problem) is left as an exercise to the reader.
13723 group-status = [ error / info ] eol
13724 error = [ "4" / "5" ] 2<number> " " <Error message>
13725 info = "211 " 3* [ <number> " " ] <string>
13729 @item (nnchoke-close-group GROUP &optional SERVER)
13731 Close @var{group} and free any resources connected to it. This will be
13732 a no-op on most backends.
13734 There should be no data returned.
13737 @item (nnchoke-request-list &optional SERVER)
13739 Return a list of all groups available on @var{server}. And that means
13742 Here's an example from a server that only carries two groups:
13745 ifi.test 0000002200 0000002000 y
13746 ifi.discussion 3324 3300 n
13749 On each line we have a group name, then the highest article number in
13750 that group, the lowest article number, and finally a flag.
13753 active-file = *active-line
13754 active-line = name " " <number> " " <number> " " flags eol
13756 flags = "n" / "y" / "m" / "x" / "j" / "=" name
13759 The flag says whether the group is read-only (@samp{n}), is moderated
13760 (@samp{m}), is dead (@samp{x}), is aliased to some other group
13761 (@samp{=other-group} or none of the above (@samp{y}).
13764 @item (nnchoke-request-post &optional SERVER)
13766 This function should post the current buffer. It might return whether
13767 the posting was successful or not, but that's not required. If, for
13768 instance, the posting is done asynchronously, it has generally not been
13769 completed by the time this function concludes. In that case, this
13770 function should set up some kind of sentinel to beep the user loud and
13771 clear if the posting could not be completed.
13773 There should be no result data from this function.
13778 @node Optional Backend Functions
13779 @subsubsection Optional Backend Functions
13783 @item (nnchoke-retrieve-groups GROUPS &optional SERVER)
13785 @var{groups} is a list of groups, and this function should request data
13786 on all those groups. How it does it is of no concern to Gnus, but it
13787 should attempt to do this in a speedy fashion.
13789 The return value of this function can be either @code{active} or
13790 @code{group}, which says what the format of the result data is. The
13791 former is in the same format as the data from
13792 @code{nnchoke-request-list}, while the latter is a buffer full of lines
13793 in the same format as @code{nnchoke-request-group} gives.
13796 group-buffer = *active-line / *group-status
13800 @item (nnchoke-request-update-info GROUP INFO &optional SERVER)
13802 A Gnus group info (@pxref{Group Info}) is handed to the backend for
13803 alterations. This comes in handy if the backend really carries all the
13804 information (as is the case with virtual an imap groups). This function
13805 may alter the info in any manner it sees fit, and should return the
13806 (altered) group info. This function may alter the group info
13807 destructively, so no copying is needed before boogeying.
13809 There should be no result data from this function.
13812 @item (nnchoke-request-type GROUP &optional ARTICLE)
13814 When the user issues commands for ``sending news'' (@kbd{F} in the
13815 summary buffer, for instance), Gnus has to know whether the article the
13816 user is following up is news or mail. This function should return
13817 @code{news} if @var{article} in @var{group} is news, @code{mail} if it
13818 is mail and @code{unknown} if the type can't be decided. (The
13819 @var{article} parameter is necessary in @code{nnvirtual} groups which
13820 might very well combine mail groups and news groups.) Both @var{group}
13821 and @var{article} may be @code{nil}.
13823 There should be no result data from this function.
13826 @item (nnchoke-request-update-mark GROUP ARTICLE MARK)
13828 If the user tries to set a mark that the backend doesn't like, this
13829 function may change the mark. Gnus will use whatever this function
13830 returns as the mark for @var{article} instead of the original
13831 @var{mark}. If the backend doesn't care, it must return the original
13832 @var{mark}, and not @code{nil} or any other type of garbage.
13834 The only use for this that I can see is what @code{nnvirtual} does with
13835 it---if a component group is auto-expirable, marking an article as read
13836 in the virtual group should result in the article being marked as
13839 There should be no result data from this function.
13842 @item (nnchoke-request-scan &optional GROUP SERVER)
13844 This function may be called at any time (by Gnus or anything else) to
13845 request that the backend check for incoming articles, in one way or
13846 another. A mail backend will typically read the spool file or query the
13847 POP server when this function is invoked. The @var{group} doesn't have
13848 to be heeded---if the backend decides that it is too much work just
13849 scanning for a single group, it may do a total scan of all groups. It
13850 would be nice, however, to keep things local if that's practical.
13852 There should be no result data from this function.
13855 @item (nnchoke-request-group-description GROUP &optional SERVER)
13857 The result data from this function should be a description of
13861 description-line = name <TAB> description eol
13863 description = <text>
13866 @item (nnchoke-request-list-newsgroups &optional SERVER)
13868 The result data from this function should be the description of all
13869 groups available on the server.
13872 description-buffer = *description-line
13876 @item (nnchoke-request-newgroups DATE &optional SERVER)
13878 The result data from this function should be all groups that were
13879 created after @samp{date}, which is in normal human-readable date
13880 format. The data should be in the active buffer format.
13883 @item (nnchoke-request-create-group GROUP &optional SERVER)
13885 This function should create an empty group with name @var{group}.
13887 There should be no return data.
13890 @item (nnchoke-request-expire-articles ARTICLES &optional GROUP SERVER FORCE)
13892 This function should run the expiry process on all articles in the
13893 @var{articles} range (which is currently a simple list of article
13894 numbers.) It is left up to the backend to decide how old articles
13895 should be before they are removed by this function. If @var{force} is
13896 non-@code{nil}, all @var{articles} should be deleted, no matter how new
13899 This function should return a list of articles that it did not/was not
13902 There should be no result data returned.
13905 @item (nnchoke-request-move-article ARTICLE GROUP SERVER ACCEPT-FORM
13908 This function should move @var{article} (which is a number) from
13909 @var{group} by calling @var{accept-form}.
13911 This function should ready the article in question for moving by
13912 removing any header lines it has added to the article, and generally
13913 should ``tidy up'' the article. Then it should @code{eval}
13914 @var{accept-form} in the buffer where the ``tidy'' article is. This
13915 will do the actual copying. If this @code{eval} returns a
13916 non-@code{nil} value, the article should be removed.
13918 If @var{last} is @code{nil}, that means that there is a high likelihood
13919 that there will be more requests issued shortly, so that allows some
13922 The function should return a cons where the car is the group name and
13923 the cdr is the article number that the article was entered as.
13925 There should be no data returned.
13928 @item (nnchoke-request-accept-article GROUP &optional SERVER LAST)
13930 This function takes the current buffer and inserts it into @var{group}.
13931 If @var{last} in @code{nil}, that means that there will be more calls to
13932 this function in short order.
13934 The function should return a cons where the car is the group name and
13935 the cdr is the article number that the article was entered as.
13937 There should be no data returned.
13940 @item (nnchoke-request-replace-article ARTICLE GROUP BUFFER)
13942 This function should remove @var{article} (which is a number) from
13943 @var{group} and insert @var{buffer} there instead.
13945 There should be no data returned.
13948 @item (nnchoke-request-delete-group GROUP FORCE &optional SERVER)
13950 This function should delete @var{group}. If @var{force}, it should
13951 really delete all the articles in the group, and then delete the group
13952 itself. (If there is such a thing as ``the group itself''.)
13954 There should be no data returned.
13957 @item (nnchoke-request-rename-group GROUP NEW-NAME &optional SERVER)
13959 This function should rename @var{group} into @var{new-name}. All
13960 articles that are in @var{group} should move to @var{new-name}.
13962 There should be no data returned.
13967 @node Error Messaging
13968 @subsubsection Error Messaging
13970 @findex nnheader-report
13971 @findex nnheader-get-report
13972 The backends should use the function @code{nnheader-report} to report
13973 error conditions---they should not raise errors when they aren't able to
13974 perform a request. The first argument to this function is the backend
13975 symbol, and the rest are interpreted as arguments to @code{format} if
13976 there are many of them, or just a string if there is one of them.
13977 This function always returns @code{nil}.
13980 (nnheader-report 'nnchoke "You did something totally bogus")
13982 (nnheader-report 'nnchoke "Could not request group %s" group)
13985 Gnus, in turn, will call @code{nnheader-get-report} when it gets a
13986 @code{nil} back from a server, and this function returns the most
13987 recently reported message for the backend in question. This function
13988 takes one argument---the server symbol.
13990 Internally, these function access @var{backend}@code{-status-string}, so
13991 the @code{nnchoke} backend will have its error message stored in
13992 @code{nnchoke-status-string}.
13995 @node Writing New Backends
13996 @subsubsection Writing New Backends
13998 Many backends are quite similar. @code{nnml} is just like
13999 @code{nnspool}, but it allows you to edit the articles on the server.
14000 @code{nnmh} is just like @code{nnml}, but it doesn't use an active file,
14001 and it doesn't maintain overview databases. @code{nndir} is just like
14002 @code{nnml}, but it has no concept of ``groups'', and it doesn't allow
14005 It would make sense if it were possible to ``inherit'' functions from
14006 backends when writing new backends. And, indeed, you can do that if you
14007 want to. (You don't have to if you don't want to, of course.)
14009 All the backends declare their public variables and functions by using a
14010 package called @code{nnoo}.
14012 To inherit functions from other backends (and allow other backends to
14013 inherit functions from the current backend), you should use the
14020 This macro declares the first parameter to be a child of the subsequent
14021 parameters. For instance:
14024 (nnoo-declare nndir
14028 @code{nndir} has here declared that it intends to inherit functions from
14029 both @code{nnml} and @code{nnmh}.
14032 This macro is equivalent to @code{defvar}, but registers the variable as
14033 a public server variable. Most state-oriented variables should be
14034 declared with @code{defvoo} instead of @code{defvar}.
14036 In addition to the normal @code{defvar} parameters, it takes a list of
14037 variables in the parent backends to map the variable to when executing
14038 a function in those backends.
14041 (defvoo nndir-directory nil
14042 "Where nndir will look for groups."
14043 nnml-current-directory nnmh-current-directory)
14046 This means that @code{nnml-current-directory} will be set to
14047 @code{nndir-directory} when an @code{nnml} function is called on behalf
14048 of @code{nndir}. (The same with @code{nnmh}.)
14050 @item nnoo-define-basics
14051 This macro defines some common functions that almost all backends should
14055 (nnoo-define-basics nndir)
14059 This macro is just like @code{defun} and takes the same parameters. In
14060 addition to doing the normal @code{defun} things, it registers the
14061 function as being public so that other backends can inherit it.
14063 @item nnoo-map-functions
14064 This macro allows mapping of functions from the current backend to
14065 functions from the parent backends.
14068 (nnoo-map-functions nndir
14069 (nnml-retrieve-headers 0 nndir-current-group 0 0)
14070 (nnmh-request-article 0 nndir-current-group 0 0))
14073 This means that when @code{nndir-retrieve-headers} is called, the first,
14074 third, and fourth parameters will be passed on to
14075 @code{nnml-retrieve-headers}, while the second parameter is set to the
14076 value of @code{nndir-current-group}.
14079 This macro allows importing functions from backends. It should be the
14080 last thing in the source file, since it will only define functions that
14081 haven't already been defined.
14087 nnmh-request-newgroups)
14091 This means that calls to @code{nndir-request-list} should just be passed
14092 on to @code{nnmh-request-list}, while all public functions from
14093 @code{nnml} that haven't been defined in @code{nndir} yet should be
14098 Below is a slightly shortened version of the @code{nndir} backend.
14101 ;;; nndir.el --- single directory newsgroup access for Gnus
14102 ;; Copyright (C) 1995,96 Free Software Foundation, Inc.
14106 (require 'nnheader)
14110 (eval-when-compile (require 'cl))
14112 (nnoo-declare nndir
14115 (defvoo nndir-directory nil
14116 "Where nndir will look for groups."
14117 nnml-current-directory nnmh-current-directory)
14119 (defvoo nndir-nov-is-evil nil
14120 "*Non-nil means that nndir will never retrieve NOV headers."
14123 (defvoo nndir-current-group "" nil nnml-current-group nnmh-current-group)
14124 (defvoo nndir-top-directory nil nil nnml-directory nnmh-directory)
14125 (defvoo nndir-get-new-mail nil nil nnml-get-new-mail nnmh-get-new-mail)
14127 (defvoo nndir-status-string "" nil nnmh-status-string)
14128 (defconst nndir-version "nndir 1.0")
14130 ;;; Interface functions.
14132 (nnoo-define-basics nndir)
14134 (deffoo nndir-open-server (server &optional defs)
14135 (setq nndir-directory
14136 (or (cadr (assq 'nndir-directory defs))
14138 (unless (assq 'nndir-directory defs)
14139 (push `(nndir-directory ,server) defs))
14140 (push `(nndir-current-group
14141 ,(file-name-nondirectory (directory-file-name nndir-directory)))
14143 (push `(nndir-top-directory
14144 ,(file-name-directory (directory-file-name nndir-directory)))
14146 (nnoo-change-server 'nndir server defs))
14148 (nnoo-map-functions nndir
14149 (nnml-retrieve-headers 0 nndir-current-group 0 0)
14150 (nnmh-request-article 0 nndir-current-group 0 0)
14151 (nnmh-request-group nndir-current-group 0 0)
14152 (nnmh-close-group nndir-current-group 0))
14156 nnmh-status-message
14158 nnmh-request-newgroups))
14164 @node Hooking New Backends Into Gnus
14165 @subsubsection Hooking New Backends Into Gnus
14167 @vindex gnus-valid-select-methods
14168 Having Gnus start using your new backend is rather easy---you just
14169 declare it with the @code{gnus-declare-backend} functions. This will
14170 enter the backend into the @code{gnus-valid-select-methods} variable.
14172 @code{gnus-declare-backend} takes two parameters---the backend name and
14173 an arbitrary number of @dfn{abilities}.
14178 (gnus-declare-backend "nnchoke" 'mail 'respool 'address)
14181 The abilities can be:
14185 This is a mailish backend---followups should (probably) go via mail.
14187 This is a newsish backend---followups should (probably) go via news.
14189 This backend supports both mail and news.
14191 This is neither a post or mail backend---it's something completely
14194 It supports respooling---or rather, it is able to modify its source
14195 articles and groups.
14197 The name of the server should be in the virtual server name. This is
14198 true for almost all backends.
14199 @item prompt-address
14200 The user should be prompted for an address when doing commands like
14201 @kbd{B} in the group buffer. This is true for backends like
14202 @code{nntp}, but not @code{nnmbox}, for instance.
14207 @node Score File Syntax
14208 @subsection Score File Syntax
14210 Score files are meant to be easily parsable, but yet extremely
14211 mallable. It was decided that something that had the same read syntax
14212 as an Emacs Lisp list would fit that spec.
14214 Here's a typical score file:
14218 ("win95" -10000 nil s)
14225 BNF definition of a score file:
14228 score-file = "" / "(" *element ")"
14229 element = rule / atom
14230 rule = string-rule / number-rule / date-rule
14231 string-rule = "(" quote string-header quote space *string-match ")"
14232 number-rule = "(" quote number-header quote space *number-match ")"
14233 date-rule = "(" quote date-header quote space *date-match ")"
14235 string-header = "subject" / "from" / "references" / "message-id" /
14236 "xref" / "body" / "head" / "all" / "followup"
14237 number-header = "lines" / "chars"
14238 date-header = "date"
14239 string-match = "(" quote <string> quote [ "" / [ space score [ "" /
14240 space date [ "" / [ space string-match-t ] ] ] ] ] ")"
14241 score = "nil" / <integer>
14242 date = "nil" / <natural number>
14243 string-match-t = "nil" / "s" / "substring" / "S" / "Substring" /
14244 "r" / "regex" / "R" / "Regex" /
14245 "e" / "exact" / "E" / "Exact" /
14246 "f" / "fuzzy" / "F" / "Fuzzy"
14247 number-match = "(" <integer> [ "" / [ space score [ "" /
14248 space date [ "" / [ space number-match-t ] ] ] ] ] ")"
14249 number-match-t = "nil" / "=" / "<" / ">" / ">=" / "<="
14250 date-match = "(" quote <string> quote [ "" / [ space score [ "" /
14251 space date [ "" / [ space date-match-t ] ] ] ] ")"
14252 date-match-t = "nil" / "at" / "before" / "after"
14253 atom = "(" [ required-atom / optional-atom ] ")"
14254 required-atom = mark / expunge / mark-and-expunge / files /
14255 exclude-files / read-only / touched
14256 optional-atom = adapt / local / eval
14257 mark = "mark" space nil-or-number
14258 nil-or-number = "nil" / <integer>
14259 expunge = "expunge" space nil-or-number
14260 mark-and-expunge = "mark-and-expunge" space nil-or-number
14261 files = "files" *[ space <string> ]
14262 exclude-files = "exclude-files" *[ space <string> ]
14263 read-only = "read-only" [ space "nil" / space "t" ]
14264 adapt = "adapt" [ space "nil" / space "t" / space adapt-rule ]
14265 adapt-rule = "(" *[ <string> *[ "(" <string> <integer> ")" ] ")"
14266 local = "local" *[ space "(" <string> space <form> ")" ]
14267 eval = "eval" space <form>
14268 space = *[ " " / <TAB> / <NEWLINE> ]
14271 Any unrecognized elements in a score file should be ignored, but not
14274 As you can see, white space is needed, but the type and amount of white
14275 space is irrelevant. This means that formatting of the score file is
14276 left up to the programmer---if it's simpler to just spew it all out on
14277 one looong line, then that's ok.
14279 The meaning of the various atoms are explained elsewhere in this
14284 @subsection Headers
14286 Gnus uses internally a format for storing article headers that
14287 corresponds to the @sc{nov} format in a mysterious fashion. One could
14288 almost suspect that the author looked at the @sc{nov} specification and
14289 just shamelessly @emph{stole} the entire thing, and one would be right.
14291 @dfn{Header} is a severely overloaded term. ``Header'' is used in
14292 RFC1036 to talk about lines in the head of an article (eg.,
14293 @code{From}). It is used by many people as a synonym for
14294 ``head''---``the header and the body''. (That should be avoided, in my
14295 opinion.) And Gnus uses a format internally that it calls ``header'',
14296 which is what I'm talking about here. This is a 9-element vector,
14297 basically, with each header (ouch) having one slot.
14299 These slots are, in order: @code{number}, @code{subject}, @code{from},
14300 @code{date}, @code{id}, @code{references}, @code{chars}, @code{lines},
14301 @code{xref}. There are macros for accessing and setting these
14302 slots---they all have predictable names beginning with
14303 @code{mail-header-} and @code{mail-header-set-}, respectively.
14305 The @code{xref} slot is really a @code{misc} slot. Any extra info will
14312 @sc{gnus} introduced a concept that I found so useful that I've started
14313 using it a lot and have elaborated on it greatly.
14315 The question is simple: If you have a large amount of objects that are
14316 identified by numbers (say, articles, to take a @emph{wild} example)
14317 that you want to callify as being ``included'', a normal sequence isn't
14318 very useful. (A 200,000 length sequence is a bit long-winded.)
14320 The solution is as simple as the question: You just collapse the
14324 (1 2 3 4 5 6 10 11 12)
14327 is transformed into
14330 ((1 . 6) (10 . 12))
14333 To avoid having those nasty @samp{(13 . 13)} elements to denote a
14334 lonesome object, a @samp{13} is a valid element:
14337 ((1 . 6) 7 (10 . 12))
14340 This means that comparing two ranges to find out whether they are equal
14341 is slightly tricky:
14344 ((1 . 5) 7 8 (10 . 12))
14350 ((1 . 5) (7 . 8) (10 . 12))
14353 are equal. In fact, any non-descending list is a range:
14359 is a perfectly valid range, although a pretty long-winded one. This is
14366 and is equal to the previous range.
14368 Here's a BNF definition of ranges. Of course, one must remember the
14369 semantic requirement that the numbers are non-descending. (Any number
14370 of repetition of the same number is allowed, but apt to disappear in
14374 range = simple-range / normal-range
14375 simple-range = "(" number " . " number ")"
14376 normal-range = "(" start-contents ")"
14377 contents = "" / simple-range *[ " " contents ] /
14378 number *[ " " contents ]
14381 Gnus currently uses ranges to keep track of read articles and article
14382 marks. I plan on implementing a number of range operators in C if The
14383 Powers That Be are willing to let me. (I haven't asked yet, because I
14384 need to do some more thinking on what operators I need to make life
14385 totally range-based without ever having to convert back to normal
14390 @subsection Group Info
14392 Gnus stores all permanent info on groups in a @dfn{group info} list.
14393 This list is from three to six elements (or more) long and exhaustively
14394 describes the group.
14396 Here are two example group infos; one is a very simple group while the
14397 second is a more complex one:
14400 ("no.group" 5 (1 . 54324))
14402 ("nnml:my.mail" 3 ((1 . 5) 9 (20 . 55))
14403 ((tick (15 . 19)) (replied 3 6 (19 . 3)))
14405 (auto-expire (to-address "ding@@ifi.uio.no")))
14408 The first element is the group name as Gnus knows the group; the second
14409 is the group level; the third is the read articles in range format; the
14410 fourth is a list of article marks lists; the fifth is the select method;
14411 and the sixth contains the group parameters.
14413 Here's a BNF definition of the group info format:
14416 info = "(" group space level space read
14417 [ "" / [ space marks-list [ "" / [ space method [ "" /
14418 space parameters ] ] ] ] ] ")"
14419 group = quote <string> quote
14420 level = <integer in the range of 1 to inf>
14422 marks-lists = nil / "(" *marks ")"
14423 marks = "(" <string> range ")"
14424 method = "(" <string> *elisp-forms ")"
14425 parameters = "(" *elisp-forms ")"
14428 Actually that @samp{marks} rule is a fib. A @samp{marks} is a
14429 @samp{<string>} consed on to a @samp{range}, but that's a bitch to say
14433 @node Emacs/XEmacs Code
14434 @subsection Emacs/XEmacs Code
14438 While Gnus runs under Emacs, XEmacs and Mule, I decided that one of the
14439 platforms must be the primary one. I chose Emacs. Not because I don't
14440 like XEmacs or Mule, but because it comes first alphabetically.
14442 This means that Gnus will byte-compile under Emacs with nary a warning,
14443 while XEmacs will pump out gigabytes of warnings while byte-compiling.
14444 As I use byte-compilation warnings to help me root out trivial errors in
14445 Gnus, that's very useful.
14447 I've also consistently used Emacs function interfaces, but have used
14448 Gnusey aliases for the functions. To take an example: Emacs defines a
14449 @code{run-at-time} function while XEmacs defines a @code{start-itimer}
14450 function. I then define a function called @code{gnus-run-at-time} that
14451 takes the same parameters as the Emacs @code{run-at-time}. When running
14452 Gnus under Emacs, the former function is just an alias for the latter.
14453 However, when running under XEmacs, the former is an alias for the
14454 following function:
14457 (defun gnus-xmas-run-at-time (time repeat function &rest args)
14461 (,function ,@@args))
14465 This sort of thing has been done for bunches of functions. Gnus does
14466 not redefine any native Emacs functions while running under XEmacs---it
14467 does this @code{defalias} thing with Gnus equivalents instead. Cleaner
14470 Of course, I could have chosen XEmacs as my native platform and done
14471 mapping functions the other way around. But I didn't. The performance
14472 hit these indirections impose on Gnus under XEmacs should be slight.
14475 @node Various File Formats
14476 @subsection Various File Formats
14479 * Active File Format:: Information on articles and groups available.
14480 * Newsgroups File Format:: Group descriptions.
14484 @node Active File Format
14485 @subsubsection Active File Format
14487 The active file lists all groups that are available on the server in
14488 question. It also lists the highest and lowest current article numbers
14491 Here's an excerpt from a typical active file:
14494 soc.motss 296030 293865 y
14495 alt.binaries.pictures.fractals 3922 3913 n
14496 comp.sources.unix 1605 1593 m
14497 comp.binaries.ibm.pc 5097 5089 y
14498 no.general 1000 900 y
14501 Here's a pseudo-BNF definition of this file:
14504 active = *group-line
14505 group-line = group space high-number space low-number space flag <NEWLINE>
14506 group = <non-white-space string>
14508 high-number = <non-negative integer>
14509 low-number = <positive integer>
14510 flag = "y" / "n" / "m" / "j" / "x" / "=" group
14514 @node Newsgroups File Format
14515 @subsubsection Newsgroups File Format
14517 The newsgroups file lists groups along with their descriptions. Not all
14518 groups on the server have to be listed, and not all groups in the file
14519 have to exist on the server. The file is meant purely as information to
14522 The format is quite simple; a group name, a tab, and the description.
14523 Here's the definition:
14527 line = group tab description <NEWLINE>
14528 group = <non-white-space string>
14530 description = <string>
14534 @node Emacs for Heathens
14535 @section Emacs for Heathens
14537 Believe it or not, but some people who use Gnus haven't really used
14538 Emacs much before they embarked on their journey on the Gnus Love Boat.
14539 If you are one of those unfortunates whom ``@kbd{M-C-a}'', ``kill the
14540 region'', and ``set @code{gnus-flargblossen} to an alist where the key
14541 is a regexp that is used for matching on the group name'' are magical
14542 phrases with little or no meaning, then this appendix is for you. If
14543 you are already familiar with Emacs, just ignore this and go fondle your
14547 * Keystrokes:: Entering text and executing commands.
14548 * Emacs Lisp:: The built-in Emacs programming language.
14553 @subsection Keystrokes
14557 Q: What is an experienced Emacs user?
14560 A: A person who wishes that the terminal had pedals.
14563 Yes, when you use Emacs, you are apt to use the control key, the shift
14564 key and the meta key a lot. This is very annoying to some people
14565 (notably @code{vi}le users), and the rest of us just love the hell out
14566 of it. Just give up and submit. Emacs really does stand for
14567 ``Escape-Meta-Alt-Control-Shift'', and not ``Editing Macros'', as you
14568 may have heard from other disreputable sources (like the Emacs author).
14570 The shift key is normally located near your pinky fingers, and are
14571 normally used to get capital letters and stuff. You probably use it all
14572 the time. The control key is normally marked ``CTRL'' or something like
14573 that. The meta key is, funnily enough, never marked as such on any
14574 keyboards. The one I'm currently at has a key that's marked ``Alt'',
14575 which is the meta key on this keyboard. It's usually located somewhere
14576 to the left hand side of the keyboard, usually on the bottom row.
14578 Now, us Emacs people doesn't say ``press the meta-control-m key'',
14579 because that's just too inconvenient. We say ``press the @kbd{M-C-m}
14580 key''. @kbd{M-} is the prefix that means ``meta'' and ``C-'' is the
14581 prefix that means ``control''. So ``press @kbd{C-k}'' means ``press
14582 down the control key, and hold it down while you press @kbd{k}''.
14583 ``Press @kbd{M-C-k}'' means ``press down and hold down the meta key and
14584 the control key and then press @kbd{k}''. Simple, ay?
14586 This is somewhat complicated by the fact that not all keyboards have a
14587 meta key. In that case you can use the ``escape'' key. Then @kbd{M-k}
14588 means ``press escape, release escape, press @kbd{k}''. That's much more
14589 work than if you have a meta key, so if that's the case, I respectfully
14590 suggest you get a real keyboard with a meta key. You can't live without
14596 @subsection Emacs Lisp
14598 Emacs is the King of Editors because it's really a Lisp interpreter.
14599 Each and every key you tap runs some Emacs Lisp code snippet, and since
14600 Emacs Lisp is an interpreted language, that means that you can configure
14601 any key to run any arbitrary code. You just, like, do it.
14603 Gnus is written in Emacs Lisp, and is run as a bunch of interpreted
14604 functions. (These are byte-compiled for speed, but it's still
14605 interpreted.) If you decide that you don't like the way Gnus does
14606 certain things, it's trivial to have it do something a different way.
14607 (Well, at least if you know how to write Lisp code.) However, that's
14608 beyond the scope of this manual, so we are simply going to talk about
14609 some common constructs that you normally use in your @file{.emacs} file
14612 If you want to set the variable @code{gnus-florgbnize} to four (4), you
14613 write the following:
14616 (setq gnus-florgbnize 4)
14619 This function (really ``special form'') @code{setq} is the one that can
14620 set a variable to some value. This is really all you need to know. Now
14621 you can go and fill your @code{.emacs} file with lots of these to change
14624 If you have put that thing in your @code{.emacs} file, it will be read
14625 and @code{eval}ed (which is lisp-ese for ``run'') the next time you
14626 start Emacs. If you want to change the variable right away, simply say
14627 @kbd{C-x C-e} after the closing parenthesis. That will @code{eval} the
14628 previous ``form'', which here is a simple @code{setq} statement.
14630 Go ahead---just try it, if you're located at your Emacs. After you
14631 @kbd{C-x C-e}, you will see @samp{4} appear in the echo area, which
14632 is the return value of the form you @code{eval}ed.
14636 If the manual says ``set @code{gnus-read-active-file} to @code{some}'',
14640 (setq gnus-read-active-file 'some)
14643 On the other hand, if the manual says ``set @code{gnus-nntp-server} to
14644 @samp{nntp.ifi.uio.no}'', that means:
14647 (setq gnus-nntp-server "nntp.ifi.uio.no")
14650 So be careful not to mix up strings (the latter) with symbols (the
14651 former). The manual is unambiguous, but it can be confusing.
14654 @include gnus-faq.texi