1 \input texinfo @c -*-texinfo-*-
4 @settitle September Gnus 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 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 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 September Gnus Manual
235 @author by Lars Magne Ingebrigtsen
238 @vskip 0pt plus 1filll
239 Copyright @copyright{} 1995 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 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 * Message:: Message sending interface.
304 * Composing Messages:: Information on sending mail and news.
305 * Select Methods:: Gnus reads all messages from various select methods.
306 * Scoring:: Assigning values to articles.
307 * Various:: General purpose settings.
308 * The End:: Farewell and goodbye.
309 * Appendices:: Terminology, Emacs intro, FAQ, History, Internals.
310 * Index:: Variable, function and concept index.
311 * 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 Gnusii:: 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 * Startup Variables:: Other variables you might change.
347 @node Finding the News
348 @section Finding the News
350 @vindex gnus-select-method
352 The @code{gnus-select-method} variable says where Gnus should look for
353 news. This variable should be a list where the first element says
354 @dfn{how} and the second element says @dfn{where}. This method is your
355 native method. All groups that are not fetched with this method are
358 For instance, if the @samp{news.somewhere.edu} @sc{nntp} server is where
359 you want to get your daily dosage of news from, you'd say:
362 (setq gnus-select-method '(nntp "news.somewhere.edu"))
365 If you want to read directly from the local spool, say:
368 (setq gnus-select-method '(nnspool ""))
371 If you can use a local spool, you probably should, as it will almost
372 certainly be much faster.
374 @vindex gnus-nntpserver-file
376 @cindex @sc{nntp} server
377 If this variable is not set, Gnus will take a look at the
378 @code{NNTPSERVER} environment variable. If that variable isn't set,
379 Gnus will see whether @code{gnus-nntpserver-file}
380 (@file{/etc/nntpserver} by default) has any opinions on the matter. If
381 that fails as well, Gnus will will try to use the machine that is
382 running Emacs as an @sc{nntp} server. That's a long-shot, though.
384 @vindex gnus-nntp-server
385 If @code{gnus-nntp-server} is set, this variable will override
386 @code{gnus-select-method}. You should therefore set
387 @code{gnus-nntp-server} to @code{nil}, which is what it is by default.
389 @vindex gnus-secondary-servers
390 You can also make Gnus prompt you interactively for the name of an
391 @sc{nntp} server. If you give a non-numerical prefix to @code{gnus}
392 (i.e., @kbd{C-u M-x gnus}), Gnus will let you choose between the servers
393 in the @code{gnus-secondary-servers} list (if any). You can also just
394 type in the name of any server you feel like visiting.
396 @findex gnus-group-browse-foreign-server
398 However, if you use one @sc{nntp} server regularly and are just
399 interested in a couple of groups from a different server, you would be
400 better served by using the @kbd{B} command in the group buffer. It will
401 let you have a look at what groups are available, and you can subscribe
402 to any of the groups you want to. This also makes @file{.newsrc}
403 maintenance much tidier. @xref{Foreign Groups}.
405 @vindex gnus-secondary-select-methods
407 A slightly different approach to foreign groups is to set the
408 @code{gnus-secondary-select-methods} variable. The select methods
409 listed in this variable are in many ways just as native as the
410 @code{gnus-select-method} server. They will also be queried for active
411 files during startup (if that's required), and new newsgroups that
412 appear on these servers will be subscribed (or not) just as native
415 For instance, if you use the @code{nnmbox} backend to read your mail, you
416 would typically set this variable to
419 (setq gnus-secondary-select-methods '((nnmbox "")))
424 @section The First Time
425 @cindex first time usage
427 If no startup files exist, Gnus will try to determine what groups should
428 be subscribed by default.
430 @vindex gnus-default-subscribed-newsgroups
431 If the variable @code{gnus-default-subscribed-newsgroups} is set, Gnus
432 will subscribe you to just those groups in that list, leaving the rest
433 killed. Your system administrator should have set this variable to
436 Since she hasn't, Gnus will just subscribe you to a few arbitrarily
437 picked groups (i.e., @samp{*.newusers}). (@dfn{Arbitrary} is here
438 defined as @dfn{whatever Lars thinks you should read}.)
440 You'll also be subscribed to the Gnus documentation group, which should
441 help you with most common problems.
443 If @code{gnus-default-subscribed-newsgroups} is @code{t}, Gnus will just
444 use the normal functions for handling new groups, and not do anything
448 @node The Server is Down
449 @section The Server is Down
450 @cindex server errors
452 If the default server is down, Gnus will understandably have some
453 problems starting. However, if you have some mail groups in addition to
454 the news groups, you may want to start Gnus anyway.
456 Gnus, being the trusting sort of program, will ask whether to proceed
457 without a native select method if that server can't be contacted. This
458 will happen whether the server doesn't actually exist (i.e., you have
459 given the wrong address) or the server has just momentarily taken ill
460 for some reason or other. If you decide to continue and have no foreign
461 groups, you'll find it difficult to actually do anything in the group
462 buffer. But, hey, that's your problem. Blllrph!
464 @findex gnus-no-server
466 If you know that the server is definitely down, or you just want to read
467 your mail without bothering with the server at all, you can use the
468 @code{gnus-no-server} command to start Gnus. That might come in handy
469 if you're in a hurry as well.
473 @section Slave Gnusiï
476 You might want to run more than one Emacs with more than one Gnus at the
477 same time. If you are using different @file{.newsrc} files (eg., if you
478 are using the two different Gnusiï to read from two different servers),
479 that is no problem whatsoever. You just do it.
481 The problem appears when you want to run two Gnusiï that use the same
484 To work around that problem some, we here at the Think-Tank at the Gnus
485 Towers have come up with a new concept: @dfn{Masters} and
486 @dfn{servants}. (We have applied for a patent on this concept, and have
487 taken out a copyright on those words. If you wish to use those words in
488 conjunction with each other, you have to send $1 per usage instance to
489 me. Usage of the patent (@dfn{Master/Slave Relationships In Computer
490 Applications}) will be much more expensive, of course.)
492 Anyways, you start one Gnus up the normal way with @kbd{M-x gnus} (or
493 however you do it). Each subsequent slave Gnusiï should be started with
494 @kbd{M-x gnus-slave}. These slaves won't save normal @file{.newsrc}
495 files, but instead save @dfn{slave files} that contains information only
496 on what groups have been read in the slave session. When a master Gnus
497 starts, it will read (and delete) these slave files, incorporating all
498 information from them. (The slave files will be read in the sequence
499 they were created, so the latest changes will have precedence.)
501 Information from the slave files has, of course, precedence over the
502 information in the normal (i. e., master) @code{.newsrc} file.
505 @node Fetching a Group
506 @section Fetching a Group
508 @findex gnus-fetch-group
509 It it sometime convenient to be able to just say ``I want to read this
510 group and I don't care whether Gnus has been started or not''. This is
511 perhaps more useful for people who write code than for users, but the
512 command @code{gnus-fetch-group} provides this functionality in any case.
513 It takes the group name as a parameter.
520 @vindex gnus-subscribe-newsgroup-method
521 What Gnus does when it encounters a new group is determined by the
522 @code{gnus-subscribe-newsgroup-method} variable.
524 This variable should contain a function. Some handy pre-fab values
529 @item gnus-subscribe-zombies
530 @vindex gnus-subscribe-zombies
531 Make all new groups zombies. You can browse the zombies later (with
532 @kbd{A z}) and either kill them all off properly, or subscribe to them.
535 @item gnus-subscribe-randomly
536 @vindex gnus-subscribe-randomly
537 Subscribe all new groups randomly.
539 @item gnus-subscribe-alphabetically
540 @vindex gnus-subscribe-alphabetically
541 Subscribe all new groups alphabetically.
543 @item gnus-subscribe-hierarchically
544 @vindex gnus-subscribe-hierarchically
545 Subscribe all new groups hierarchically.
547 @item gnus-subscribe-interactively
548 @vindex gnus-subscribe-interactively
549 Subscribe new groups interactively. This means that Gnus will ask
550 you about @strong{all} new groups.
552 @item gnus-subscribe-killed
553 @vindex gnus-subscribe-killed
558 @vindex gnus-subscribe-hierarchical-interactive
559 A closely related variable is
560 @code{gnus-subscribe-hierarchical-interactive}. (That's quite a
561 mouthful.) If this variable is non-@code{nil}, Gnus will ask you in a
562 hierarchical fashion whether to subscribe to new groups or not. Gnus
563 will ask you for each sub-hierarchy whether you want to descend the
566 One common mistake is to set the variable a few paragraphs above to
567 @code{gnus-subscribe-hierarchical-interactive}. This is an error. This
568 will not work. This is ga-ga. So don't do it.
570 A nice and portable way to control which new newsgroups should be
571 subscribed (or ignored) is to put an @dfn{options} line at the start of
572 the @file{.newsrc} file. Here's an example:
575 options -n !alt.all !rec.all sci.all
578 @vindex gnus-subscribe-options-newsgroup-method
579 This line obviously belongs to a serious-minded intellectual scientific
580 person (or she may just be plain old boring), because it says that all
581 groups that have names beginning with @samp{alt} and @samp{rec} should
582 be ignored, and all groups with names beginning with @samp{sci} should
583 be subscribed. Gnus will not use the normal subscription method for
584 subscribing these groups.
585 @code{gnus-subscribe-options-newsgroup-method} is used instead. This
586 variable defaults to @code{gnus-subscribe-alphabetically}.
588 @vindex gnus-options-not-subscribe
589 @vindex gnus-options-subscribe
590 If you don't want to mess with your @file{.newsrc} file, you can just
591 set the two variables @code{gnus-options-subscribe} and
592 @code{gnus-options-not-subscribe}. These two variables do exactly the
593 same as the @file{.newsrc} @samp{options -n} trick. Both are regexps,
594 and if the the new group matches the former, it will be unconditionally
595 subscribed, and if it matches the latter, it will be ignored.
597 @vindex gnus-auto-subscribed-groups
598 Yet another variable that meddles here is
599 @code{gnus-auto-subscribed-groups}. It works exactly like
600 @code{gnus-options-subscribe}, and is therefore really superfluous, but I
601 thought it would be nice to have two of these. This variable is more
602 meant for setting some ground rules, while the other variable is used
603 more for user fiddling. By default this variable makes all new groups
604 that come from mail backends (@code{nnml}, @code{nnbabyl},
605 @code{nnfolder}, @code{nnmbox}, and @code{nnmh}) subscribed. If you
606 don't like that, just set this variable to @code{nil}.
608 @vindex gnus-check-new-newsgroups
609 If you are satisfied that you really never want to see any new groups,
610 you could set @code{gnus-check-new-newsgroups} to @code{nil}. This will
611 also save you some time at startup. Even if this variable is
612 @code{nil}, you can always subscribe to the new groups just by pressing
613 @kbd{U} in the group buffer (@pxref{Group Maintenance}). This variable
614 is @code{t} by default.
616 Gnus normally determines whether a group is new or not by comparing the
617 list of groups from the active file(s) with the lists of subscribed and
618 dead groups. This isn't a particularly fast method. If
619 @code{gnus-check-new-newsgroups} is @code{ask-server}, Gnus will ask the
620 server for new groups since the last time. This is both faster &
621 cheaper. This also means that you can get rid of the list of killed
622 groups altogether, so you may set @code{gnus-save-killed-list} to
623 @code{nil}, which will save time both at startup, at exit, and all over.
624 Saves disk space, too. Why isn't this the default, then?
625 Unfortunately, not all servers support this command.
627 I bet I know what you're thinking now: How do I find out whether my
628 server supports @code{ask-server}? No? Good, because I don't have a
629 fail-safe answer. I would suggest just setting this variable to
630 @code{ask-server} and see whether any new groups appear within the next
631 few days. If any do, then it works. If any don't, then it doesn't
632 work. I could write a function to make Gnus guess whether the server
633 supports @code{ask-server}, but it would just be a guess. So I won't.
634 You could @code{telnet} to the server and say @code{HELP} and see
635 whether it lists @samp{NEWGROUPS} among the commands it understands. If
636 it does, then it might work. (But there are servers that lists
637 @samp{NEWGROUPS} without supporting the function properly.)
639 This variable can also be a list of select methods. If so, Gnus will
640 issue an @code{ask-server} command to each of the select methods, and
641 subscribe them (or not) using the normal methods. This might be handy
642 if you are monitoring a few servers for new groups. A side effect is
643 that startup will take much longer, so you can meditate while waiting.
644 Use the mantra ``dingnusdingnusdingnus'' to achieve permanent bliss.
648 @section Startup Files
649 @cindex startup files
652 Now, you all know about the @file{.newsrc} file. All subscription
653 information is traditionally stored in this file.
655 Things got a bit more complicated with @sc{gnus}. In addition to
656 keeping the @file{.newsrc} file updated, it also used a file called
657 @file{.newsrc.el} for storing all the information that didn't fit into
658 the @file{.newsrc} file. (Actually, it also duplicated everything in
659 the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
660 files was the most recently saved, which enabled people to swap between
661 @sc{gnus} and other newsreaders.
663 That was kinda silly, so Gnus went one better: In addition to the
664 @file{.newsrc} and @file{.newsrc.el} files, Gnus also has a file called
665 @file{.newsrc.eld}. It will read whichever of these files that are most
666 recent, but it will never write a @file{.newsrc.el} file.
668 @vindex gnus-save-newsrc-file
669 You can turn off writing the @file{.newsrc} file by setting
670 @code{gnus-save-newsrc-file} to @code{nil}, which means you can delete
671 the file and save some space, as well as making exit from Gnus faster.
672 However, this will make it impossible to use other newsreaders than
673 Gnus. But hey, who would want to, right?
675 @vindex gnus-save-killed-list
676 If @code{gnus-save-killed-list} (default @code{t}) is @code{nil}, Gnus
677 will not save the list of killed groups to the startup file. This will
678 save both time (when starting and quitting) and space (on disk). It
679 will also means that Gnus has no record of what groups are new or old,
680 so the automatic new groups subscription methods become meaningless.
681 You should always set @code{gnus-check-new-newsgroups} to @code{nil} or
682 @code{ask-server} if you set this variable to @code{nil} (@pxref{New
685 @vindex gnus-startup-file
686 The @code{gnus-startup-file} variable says where the startup files are.
687 The default value is @file{~/.newsrc}, with the Gnus (El Dingo) startup
688 file being whatever that one is with a @samp{.eld} appended.
690 @vindex gnus-save-newsrc-hook
691 @vindex gnus-save-quick-newsrc-hook
692 @vindex gnus-save-standard-newsrc-hook
693 @code{gnus-save-newsrc-hook} is called before saving any of the newsrc
694 files, while @code{gnus-save-quick-newsrc-hook} is called just before
695 saving the @file{.newsrc.eld} file, and
696 @code{gnus-save-standard-newsrc-hook} is called just before saving the
697 @file{.newsrc} file. The latter two are commonly used to turn version
698 control on or off. Version control is off by default when saving the
707 Whenever you do something that changes the Gnus data (reading articles,
708 catching up, killing/subscribing groups), the change is added to a
709 special @dfn{dribble buffer}. This buffer is auto-saved the normal
710 Emacs way. If your Emacs should crash before you have saved the
711 @file{.newsrc} files, all changes you have made can be recovered from
714 If Gnus detects this file at startup, it will ask the user whether to
715 read it. The auto save file is deleted whenever the real startup file is
718 @vindex gnus-use-dribble-file
719 If @code{gnus-use-dribble-file} is @code{nil}, Gnus won't create and
720 maintain a dribble buffer. The default is @code{t}.
722 @vindex gnus-dribble-directory
723 Gnus will put the dribble file(s) in @code{gnus-dribble-directory}. If
724 this variable is @code{nil}, which it is by default, Gnus will dribble
725 into the directory where the @file{.newsrc} file is located. (This is
726 normally the user's home directory.) The dribble file will get the same
727 file permissions as the @code{.newsrc} file.
730 @node The Active File
731 @section The Active File
733 @cindex ignored groups
735 When Gnus starts, or indeed whenever it tries to determine whether new
736 articles have arrived, it reads the active file. This is a very large
737 file that lists all the active groups and articles on the server.
739 @vindex gnus-ignored-newsgroups
740 Before examining the active file, Gnus deletes all lines that match the
741 regexp @code{gnus-ignored-newsgroups}. This is done primarily to reject
742 any groups with bogus names, but you can use this variable to make Gnus
743 ignore hierarchies you aren't ever interested in. However, this is not
744 recommended. In fact, it's highly discouraged. Instead, @pxref{New
745 Groups} for an overview of other variables that can be used instead.
748 @c @code{nil} by default, and will slow down active file handling somewhat
749 @c if you set it to anything else.
751 @vindex gnus-read-active-file
753 The active file can be rather Huge, so if you have a slow network, you
754 can set @code{gnus-read-active-file} to @code{nil} to prevent Gnus from
755 reading the active file. This variable is @code{t} by default.
757 Gnus will try to make do by getting information just on the groups that
758 you actually subscribe to.
760 Note that if you subscribe to lots and lots of groups, setting this
761 variable to @code{nil} will probably make Gnus slower, not faster. At
762 present, having this variable @code{nil} will slow Gnus down
763 considerably, unless you read news over a 2400 baud modem.
765 This variable can also have the value @code{some}. Gnus will then
766 attempt to read active info only on the subscribed groups. On some
767 servers this is quite fast (on sparkling, brand new INN servers that
768 support the @code{LIST ACTIVE group} command), on others this isn't fast
769 at all. In any case, @code{some} should be faster than @code{nil}, and
770 is certainly faster than @code{t} over slow lines.
772 If this variable is @code{nil}, Gnus will ask for group info in total
773 lock-step, which isn't very fast. If it is @code{some} and you use an
774 @sc{nntp} server, Gnus will pump out commands as fast as it can, and
775 read all the replies in one swoop. This will normally result in better
776 performance, but if the server does not support the aforementioned
777 @code{LIST ACTIVE group} command, this isn't very nice to the server.
779 In any case, if you use @code{some} or @code{nil}, you should definitely
780 kill all groups that you aren't interested in to speed things up.
783 @node Startup Variables
784 @section Startup Variables
789 @vindex gnus-load-hook
790 A hook that is run while Gnus is being loaded. Note that this hook will
791 normally be run just once in each Emacs session, no matter how many
792 times you start Gnus.
794 @item gnus-startup-hook
795 @vindex gnus-startup-hook
796 A hook that is run after starting up Gnus successfully.
798 @item gnus-check-bogus-newsgroups
799 @vindex gnus-check-bogus-newsgroups
800 If non-@code{nil}, Gnus will check for and delete all bogus groups at
801 startup. A @dfn{bogus group} is a group that you have in your
802 @file{.newsrc} file, but doesn't exist on the news server. Checking for
803 bogus groups can take quite a while, so to save time and resources it's
804 best to leave this option off, and do the checking for bogus groups once
805 in a while from the group buffer instead (@pxref{Group Maintenance}).
807 @item gnus-inhibit-startup-message
808 @vindex gnus-inhibit-startup-message
809 If non-@code{nil}, the startup message won't be displayed. That way,
810 your boss might not notice that you are reading news instead of doing
813 @item gnus-no-groups-message
814 @vindex gnus-no-groups-message
815 Message displayed by Gnus when no groups are available.
819 @node The Group Buffer
820 @chapter The Group Buffer
823 The @dfn{group buffer} lists all (or parts) of the available groups. It
824 is the first buffer shown when Gnus starts, and will never be killed as
825 long as Gnus is active.
828 * Group Buffer Format:: Information listed and how you can change it.
829 * Group Maneuvering:: Commands for moving in the group buffer.
830 * Selecting a Group:: Actually reading news.
831 * Subscription Commands:: Unsubscribing, killing, subscribing.
832 * Group Levels:: Levels? What are those, then?
833 * Group Score:: A mechanism for finding out what groups you like.
834 * Marking Groups:: You can mark groups for later processing.
835 * Foreign Groups:: Creating and editing groups.
836 * Group Parameters:: Each group may have different parameters set.
837 * Listing Groups:: Gnus can list various subsets of the groups.
838 * Sorting Groups:: Re-arrange the group order.
839 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
840 * Browse Foreign Server:: You can browse a server. See what it has to offer.
841 * Exiting Gnus:: Stop reading news and get some work done.
842 * Group Topics:: A folding group mode divided into topics.
843 * Misc Group Stuff:: Other stuff that you can to do.
847 @node Group Buffer Format
848 @section Group Buffer Format
849 @cindex group buffer format
852 * Group Line Specification:: Deciding how the group buffer is to look.
853 * Group Modeline Specification:: The group buffer modeline.
854 * Group Highlighting:: Having nice colors in the group buffer.
858 @node Group Line Specification
859 @subsection Group Line Specification
861 The default format of the group buffer is nice and dull, but you can
862 make it as exciting and ugly as you feel like.
864 Here's a couple of example group lines:
867 25: news.announce.newusers
868 * 0: alt.fan.andrea-dworkin
873 You can see that there are 25 unread articles in
874 @samp{news.announce.newusers}. There are no unread articles, but some
875 ticked articles, in @samp{alt.fan.andrea-dworkin} (see that little
876 asterisk at the beginning of the line?)
878 @vindex gnus-group-line-format
879 You can change that format to whatever you want by fiddling with the
880 @code{gnus-group-line-format} variable. This variable works along the
881 lines of a @code{format} specification, which is pretty much the same as
882 a @code{printf} specifications, for those of you who use (feh!) C.
883 @xref{Formatting Variables}.
885 The default value that produced those lines above is
886 @samp{%M%S%5y: %(%g%)\n}.
888 There should always be a colon on the line; the cursor always moves to
889 the colon after performing an operation. Nothing else is required---not
890 even the group name. All displayed text is just window dressing, and is
891 never examined by Gnus. Gnus stores all real information it needs using
894 (Note that if you make a really strange, wonderful, spreadsheet-like
895 layout, everybody will believe you are hard at work with the accounting
896 instead of wasting time reading news.)
898 Here's a list of all available format characters:
903 Only marked articles.
906 Whether the group is subscribed.
909 Level of subscribedness.
912 Number of unread articles.
915 Number of dormant articles.
918 Number of ticked articles.
921 Number of read articles.
924 Total number of articles.
927 Number of unread, unticked, non-dormant articles.
930 Number of ticked and dormant articles.
939 Newsgroup description.
942 @samp{m} if moderated.
945 @samp{(m)} if moderated.
954 A string that looks like @samp{<%s:%n>} if a foreign select method is
958 Indentation based on the level of the topic (@pxref{Group Topics}).
961 @vindex gnus-group-uncollapsed-levels
962 Short (collapsed) group name. The @code{gnus-group-uncollapsed-levels}
963 variable says how many levels to leave at the end of the group name.
964 The default is @code{1}.
967 User defined specifier. The next character in the format string should
968 be a letter. @sc{gnus} will call the function
969 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
970 following @samp{%u}. The function will be passed the current headers as
971 argument. The function should return a string, which will be inserted
972 into the buffer just like information from any other specifier.
976 All the ``number-of'' specs will be filled with an asterisk (@samp{*})
977 if no info is available---for instance, if it is a non-activated foreign
978 group, or a bogus (or semi-bogus) native group.
981 @node Group Modeline Specification
982 @subsection Group Modeline Specification
984 @vindex gnus-group-mode-line-format
985 The mode line can be changed by setting
986 (@code{gnus-group-mode-line-format}). It doesn't understand that many
991 The native news server.
993 The native select method.
997 @node Group Highlighting
998 @subsection Group Highlighting
1000 @vindex gnus-group-highlight
1001 Highlighting in the group buffer is controlled by the
1002 @code{gnus-group-highlight} variable. This is an alist with elements
1003 that look like @var{(form . face)}. If @var{form} evaluates to
1004 something non-@code{nil}, the @var{face} will be used on the line.
1006 Here's an example value for this variable that might look nice if the
1010 (setq gnus-group-highlight
1012 ,(custom-face-lookup "Red" nil nil t nil nil))
1013 ((and (< level 3) (zerop unread)) .
1014 ,(custom-face-lookup "SeaGreen" nil nil t nil nil))
1016 ,(custom-face-lookup "SpringGreen" nil nil t nil nil))
1018 ,(custom-face-lookup "SteelBlue" nil nil t nil nil))
1020 ,(custom-face-lookup "SkyBlue" nil nil t nil nil))
1024 Variables that are dynamically bound when the forms are evaluated
1031 The number of unread articles in the group.
1035 Whether the group is a mail group.
1037 The level of the group.
1039 The score of the group.
1041 The number of ticked articles in the group.
1044 When the forms are @code{eval}ed, point is at the beginning of the line
1045 of the group in question, so you can use many of the normal Gnus
1046 functions for snarfing info on the group.
1048 @vindex gnus-group-update-hook
1049 @findex gnus-group-highlight-line
1050 @code{gnus-group-update-hook} is called when a group line is changed.
1051 It will not be called when @code{gnus-visual} is @code{nil}. This hook
1052 calls @code{gnus-group-highlight-line} by default.
1055 @node Group Maneuvering
1056 @section Group Maneuvering
1057 @cindex group movement
1059 All movement commands understand the numeric prefix and will behave as
1060 expected, hopefully.
1066 @findex gnus-group-next-unread-group
1067 Go to the next group that has unread articles
1068 (@code{gnus-group-next-unread-group}).
1075 @findex gnus-group-prev-unread-group
1076 Go to the previous group group that has unread articles
1077 (@code{gnus-group-prev-unread-group}).
1081 @findex gnus-group-next-group
1082 Go to the next group (@code{gnus-group-next-group}).
1086 @findex gnus-group-prev-group
1087 Go to the previous group (@code{gnus-group-prev-group}).
1091 @findex gnus-group-next-unread-group-same-level
1092 Go to the next unread group on the same level (or lower)
1093 (@code{gnus-group-next-unread-group-same-level}).
1097 @findex gnus-group-prev-unread-group-same-level
1098 Go to the previous unread group on the same level (or lower)
1099 (@code{gnus-group-prev-unread-group-same-level}).
1102 Three commands for jumping to groups:
1108 @findex gnus-group-jump-to-group
1109 Jump to a group (and make it visible if it isn't already)
1110 (@code{gnus-group-jump-to-group}). Killed groups can be jumped to, just
1115 @findex gnus-group-best-unread-group
1116 Jump to the unread group with the lowest level
1117 (@code{gnus-group-best-unread-group}).
1121 @findex gnus-group-first-unread-group
1122 Jump to the first group with unread articles
1123 (@code{gnus-group-first-unread-group}).
1126 @vindex gnus-group-goto-unread
1127 If @code{gnus-group-goto-unread} is @code{nil}, all the movement
1128 commands will move to the next group, not the next unread group. Even
1129 the commands that say they move to the next unread group. The default
1133 @node Selecting a Group
1134 @section Selecting a Group
1135 @cindex group selection
1140 @kindex SPACE (Group)
1141 @findex gnus-group-read-group
1142 Select the current group, switch to the summary buffer and display the
1143 first unread article (@code{gnus-group-read-group}). If there are no
1144 unread articles in the group, or if you give a non-numerical prefix to
1145 this command, Gnus will offer to fetch all the old articles in this
1146 group from the server. If you give a numerical prefix @var{N}, Gnus
1147 will fetch @var{N} number of articles. If @var{N} is positive, fetch
1148 the @var{N} newest articles, if @var{N} is negative, fetch the
1149 @var{abs(N)} oldest articles.
1153 @findex gnus-group-select-group
1154 Select the current group and switch to the summary buffer
1155 (@code{gnus-group-select-group}). Takes the same arguments as
1156 @code{gnus-group-read-group}---the only difference is that this command
1157 does not display the first unread article automatically upon group
1161 @kindex M-RET (Group)
1162 @findex gnus-group-quick-select-group
1163 This does the same as the command above, but tries to do it with the
1164 minimum amount off fuzz (@code{gnus-group-quick-select-group}). No
1165 scoring/killing will be performed, there will be no highlights and no
1166 expunging. This might be useful if you're in a real hurry and have to
1167 enter some humongous group.
1170 @kindex M-RET (Group)
1171 @findex gnus-group-visible-select-group
1172 This is yet one more command that does the same as the one above, but
1173 this one does it without expunging and hiding dormants
1174 (@code{gnus-group-visible-select-group}).
1178 @findex gnus-group-catchup-current
1179 @vindex gnus-group-catchup-group-hook
1180 Mark all unticked articles in this group as read
1181 (@code{gnus-group-catchup-current}).
1182 @code{gnus-group-catchup-group-hook} is when catching up a group from
1187 @findex gnus-group-catchup-current-all
1188 Mark all articles in this group, even the ticked ones, as read
1189 (@code{gnus-group-catchup-current-all}).
1192 @vindex gnus-large-newsgroup
1193 The @code{gnus-large-newsgroup} variable says what Gnus should consider
1194 to be a big group. This is 200 by default. If the group has more
1195 unread articles than this, Gnus will query the user before entering the
1196 group. The user can then specify how many articles should be fetched
1197 from the server. If the user specifies a negative number (@code{-n}),
1198 the @code{n} oldest articles will be fetched. If it is positive, the
1199 @code{n} articles that have arrived most recently will be fetched.
1201 @vindex gnus-select-group-hook
1202 @vindex gnus-auto-select-first
1203 @code{gnus-auto-select-first} control whether any articles are selected
1204 automatically when entering a group.
1209 Don't select any articles when entering the group. Just display the
1210 full summary buffer.
1213 Select the first unread article when entering the group.
1216 Select the most high-scored article in the group when entering the
1220 If you want to prevent automatic selection in some group (say, in a
1221 binary group with Huge articles) you can set this variable to @code{nil}
1222 in @code{gnus-select-group-hook}, which is called when a group is
1225 @findex gnus-thread-sort-by-total-score
1226 @findex gnus-thread-sort-by-date
1227 @findex gnus-thread-sort-by-score
1228 @findex gnus-thread-sort-by-subject
1229 @findex gnus-thread-sort-by-author
1230 @findex gnus-thread-sort-by-number
1231 @vindex gnus-thread-sort-functions
1232 If you are using a threaded summary display, you can sort the threads by
1233 setting @code{gnus-thread-sort-functions}, which is a list of functions.
1234 By default, sorting is done on article numbers. Ready-made sorting
1235 predicate functions include @code{gnus-thread-sort-by-number},
1236 @code{gnus-thread-sort-by-author}, @code{gnus-thread-sort-by-subject},
1237 @code{gnus-thread-sort-by-date}, @code{gnus-thread-sort-by-score}, and
1238 @code{gnus-thread-sort-by-total-score}.
1240 Each function takes two threads and return non-@code{nil} if the first
1241 thread should be sorted before the other. Note that sorting really is
1242 normally done by looking only at the roots of each thread. If you use
1243 more than one function, the primary sort key should be the last function
1244 in the list. You should probably always include
1245 @code{gnus-thread-sort-by-number} in the list of sorting
1246 functions---preferably first. This will ensure that threads that are
1247 equal with respect to the other sort criteria will be displayed in
1248 ascending article order.
1250 If you would like to sort by score, then by subject, and finally by
1251 number, you could do something like:
1254 (setq gnus-thread-sort-functions
1255 '(gnus-thread-sort-by-number
1256 gnus-thread-sort-by-subject
1257 gnus-thread-sort-by-score))
1260 The threads that have highest score will be displayed first in the
1261 summary buffer. When threads have the same score, they will be sorted
1262 alphabetically. The threads that have the same score and the same
1263 subject will be sorted by number, which is (normally) the sequence in
1264 which the articles arrived.
1266 If you want to sort by score and then reverse arrival order, you could
1270 (setq gnus-thread-sort-functions
1272 (not (gnus-thread-sort-by-number t1 t2)))
1273 gnus-thread-sort-by-score))
1276 @vindex gnus-thread-score-function
1277 The function in the @code{gnus-thread-score-function} variable (default
1278 @code{+}) is used for calculating the total score of a thread. Useful
1279 functions might be @code{max}, @code{min}, or squared means, or whatever
1282 @findex gnus-article-sort-functions
1283 @findex gnus-article-sort-by-date
1284 @findex gnus-article-sort-by-score
1285 @findex gnus-article-sort-by-subject
1286 @findex gnus-article-sort-by-author
1287 @findex gnus-article-sort-by-number
1288 If you are using an unthreaded display for some strange reason or other,
1289 you have to fiddle with the @code{gnus-article-sort-functions} variable.
1290 It is very similar to the @code{gnus-thread-sort-functions}, except that
1291 is uses slightly different functions for article comparison. Available
1292 sorting predicate functions are @code{gnus-article-sort-by-number},
1293 @code{gnus-article-sort-by-author}, @code{gnus-article-sort-by-subject},
1294 @code{gnus-article-sort-by-date}, and @code{gnus-article-sort-by-score}.
1296 If you want to sort an unthreaded summary display by subject, you could
1300 (setq gnus-article-sort-functions
1301 '(gnus-article-sort-by-number
1302 gnus-article-sort-by-subject))
1306 @node Subscription Commands
1307 @section Subscription Commands
1316 @findex gnus-group-unsubscribe-current-group
1317 Toggle subscription to the current group
1318 (@code{gnus-group-unsubscribe-current-group}).
1324 @findex gnus-group-unsubscribe-group
1325 Prompt for a group to subscribe, and then subscribe it. If it was
1326 subscribed already, unsubscribe it instead
1327 (@code{gnus-group-unsubscribe-group}).
1333 @findex gnus-group-kill-group
1334 Kill the current group (@code{gnus-group-kill-group}).
1340 @findex gnus-group-yank-group
1341 Yank the last killed group (@code{gnus-group-yank-group}).
1344 @kindex C-x C-t (Group)
1345 @findex gnus-group-transpose-groups
1346 Transpose two groups (@code{gnus-group-transpose-groups}). This isn't
1347 really a subscription command, but you can use it instead of a
1348 kill-and-yank sequence sometimes.
1354 @findex gnus-group-kill-region
1355 Kill all groups in the region (@code{gnus-group-kill-region}).
1359 @findex gnus-group-kill-all-zombies
1360 Kill all zombie groups (@code{gnus-group-kill-all-zombies}).
1363 @kindex S C-k (Group)
1364 @findex gnus-group-kill-level
1365 Kill all groups on a certain level (@code{gnus-group-kill-level}).
1366 These groups can't be yanked back after killing, so this command should
1367 be used with some caution. The only thing where this command comes in
1368 really handy is when you have a @file{.newsrc} with lots of unsubscribed
1369 groups that you want to get rid off. @kbd{S C-k} on level @code{7} will
1370 kill off all unsubscribed groups that do not have message numbers in the
1371 @file{.newsrc} file.
1375 Also @pxref{Group Levels}.
1379 @section Group Levels
1382 All groups have a level of @dfn{subscribedness}. For instance, if a
1383 group is on level 2, it is more subscribed than a group on level 5. You
1384 can ask Gnus to just list groups on a given level or lower
1385 (@pxref{Listing Groups}), or to just check for new articles in groups on
1386 a given level or lower (@pxref{Scanning New Messages}).
1392 @findex gnus-group-set-current-level
1393 Set the level of the current group. If a numeric prefix is given, the
1394 next @var{n} groups will have their levels set. The user will be
1395 prompted for a level.
1398 @vindex gnus-level-killed
1399 @vindex gnus-level-zombie
1400 @vindex gnus-level-unsubscribed
1401 @vindex gnus-level-subscribed
1402 Gnus considers groups on between levels 1 and
1403 @code{gnus-level-subscribed} (inclusive) (default 5) to be subscribed,
1404 @code{gnus-level-subscribed} (exclusive) and
1405 @code{gnus-level-unsubscribed} (inclusive) (default 7) to be
1406 unsubscribed, @code{gnus-level-zombie} to be zombies (walking dead)
1407 (default 8) and @code{gnus-level-killed} to be killed (default 9),
1408 completely dead. Gnus treats subscribed and unsubscribed groups exactly
1409 the same, but zombie and killed groups have no information on what
1410 articles you have read, etc, stored. This distinction between dead and
1411 living groups isn't done because it is nice or clever, it is done purely
1412 for reasons of efficiency.
1414 It is recommended that you keep all your mail groups (if any) on quite
1415 low levels (eg. 1 or 2).
1417 If you want to play with the level variables, you should show some care.
1418 Set them once, and don't touch them ever again. Better yet, don't touch
1419 them at all unless you know exactly what you're doing.
1421 @vindex gnus-level-default-unsubscribed
1422 @vindex gnus-level-default-subscribed
1423 Two closely related variables are @code{gnus-level-default-subscribed}
1424 (default 3) and @code{gnus-level-default-unsubscribed} (default 6),
1425 which are the levels that new groups will be put on if they are
1426 (un)subscribed. These two variables should, of course, be inside the
1427 relevant legal ranges.
1429 @vindex gnus-keep-same-level
1430 If @code{gnus-keep-same-level} is non-@code{nil}, some movement commands
1431 will only move to groups that are of the same level (or lower). In
1432 particular, going from the last article in one group to the next group
1433 will go to the next group of the same level (or lower). This might be
1434 handy if you want to read the most important groups before you read the
1437 @vindex gnus-group-default-list-level
1438 All groups with a level less than or equal to
1439 @code{gnus-group-default-list-level} will be listed in the group buffer
1442 @vindex gnus-group-list-inactive-groups
1443 If @code{gnus-group-list-inactive-groups} is non-@code{nil}, non-active
1444 groups will be listed along with the unread groups. This variable is
1445 @code{t} by default. If it is @code{nil}, inactive groups won't be
1448 @vindex gnus-group-use-permanent-levels
1449 If @code{gnus-group-use-permanent-levels} is non-@code{nil}, once you
1450 give a level prefix to @kbd{g} or @kbd{l}, all subsequent commands will
1451 use this level as the ``work'' level.
1453 @vindex gnus-activate-level
1454 Gnus will normally just activate groups that are on level
1455 @code{gnus-activate-level} or less. If you don't want to activate
1456 unsubscribed groups, for instance, you might set this variable to
1461 @section Group Score
1464 You would normally keep important groups on high levels, but that scheme
1465 is somewhat restrictive. Don't you wish you could have Gnus sort the
1466 group buffer according to how often you read groups, perhaps? Within
1469 This is what @dfn{group score} is for. You can assign a score to each
1470 group. You can then sort the group buffer based on this score.
1471 Alternatively, you can sort on score and then level. (Taken together,
1472 the level and the score is called the @dfn{rank} of the group. A group
1473 that is on level 4 and has a score of 1 has a higher rank than a group
1474 on level 5 that has a score of 300. (The level is the most significant
1475 part and the score is the least significant part.)
1477 @findex gnus-summary-bubble-group
1478 If you want groups you read often to get higher scores than groups you
1479 read seldom you can add the @code{gnus-summary-bubble-group} function to
1480 the @code{gnus-summary-exit-hook} hook. This will result (after
1481 sorting) in a bubbling sort of action. If you want to see that in
1482 action after each summary exit, you can add
1483 @code{gnus-group-sort-groups-by-rank} or
1484 @code{gnus-group-sort-groups-by-score} to the same hook, but that will
1485 slow things down somewhat.
1488 @node Marking Groups
1489 @section Marking Groups
1490 @cindex marking groups
1492 If you want to perform some command on several groups, and they appear
1493 subsequently in the group buffer, you would normally just give a
1494 numerical prefix to the command. Most group commands will then do your
1495 bidding on those groups.
1497 However, if the groups are not in sequential order, you can still
1498 perform a command on several groups. You simply mark the groups first
1499 with the process mark and then execute the command.
1507 @findex gnus-group-mark-group
1508 Set the mark on the current group (@code{gnus-group-mark-group}).
1514 @findex gnus-group-unmark-group
1515 Remove the mark from the current group
1516 (@code{gnus-group-unmark-group}).
1520 @findex gnus-group-unmark-all-groups
1521 Remove the mark from all groups (@code{gnus-group-unmark-all-groups}).
1525 @findex gnus-group-mark-region
1526 Mark all groups between point and mark (@code{gnus-group-mark-region}).
1530 @findex gnus-group-mark-buffer
1531 Mark all groups in the buffer (@code{gnus-group-mark-buffer}).
1535 @findex gnus-group-mark-regexp
1536 Mark all groups that match some regular expression
1537 (@code{gnus-group-mark-regexp}).
1540 Also @pxref{Process/Prefix}.
1542 @findex gnus-group-universal-argument
1543 If you want to execute some command on all groups that have been marked
1544 with the process mark, you can use the @kbd{M-&}
1545 (@code{gnus-group-universal-argument}) command. It will prompt you for
1546 the command to be executed.
1549 @node Foreign Groups
1550 @section Foreign Groups
1552 Here are some group mode commands for making and editing general foreign
1553 groups, as well as commands to ease the creation of a few
1554 special-purpose groups:
1560 @findex gnus-group-make-group
1561 Make a new group (@code{gnus-group-make-group}). Gnus will prompt you
1562 for a name, a method and possibly an @dfn{address}. For an easier way
1563 to subscribe to @sc{nntp} groups, @pxref{Browse Foreign Server}.
1567 @findex gnus-group-rename-group
1568 Rename the current group to something else
1569 (@code{gnus-group-rename-group}). This is legal only on some groups --
1570 mail groups mostly. This command might very well be quite slow on some
1575 @findex gnus-group-edit-group-method
1576 Enter a buffer where you can edit the select method of the current
1577 group (@code{gnus-group-edit-group-method}).
1581 @findex gnus-group-edit-group-parameters
1582 Enter a buffer where you can edit the group parameters
1583 (@code{gnus-group-edit-group-parameters}).
1587 @findex gnus-group-edit-group
1588 Enter a buffer where you can edit the group info
1589 (@code{gnus-group-edit-group}).
1593 @findex gnus-group-make-directory-group
1594 Make a directory group. You will be prompted for a directory name
1595 (@code{gnus-group-make-directory-group}).
1599 @findex gnus-group-make-help-group
1600 Make the Gnus help group (@code{gnus-group-make-help-group}).
1604 @findex gnus-group-make-archive-group
1605 @vindex gnus-group-archive-directory
1606 @vindex gnus-group-recent-archive-directory
1607 Make a Gnus archive group (@code{gnus-group-make-archive-group}). By
1608 default a group pointing to the most recent articles will be created
1609 (@code{gnus-group-recent-archive-directory}), but given a prefix, a full
1610 group will be created from from @code{gnus-group-archive-directory}.
1614 @findex gnus-group-make-kiboze-group
1615 Make a kiboze group. You will be prompted for a name, for a regexp to
1616 match groups to be ``included'' in the kiboze group, and a series of
1617 strings to match on headers (@code{gnus-group-make-kiboze-group}).
1621 @findex gnus-group-enter-directory
1622 Read an arbitrary directory as if with were a newsgroup with the
1623 @code{nneething} backend (@code{gnus-group-enter-directory}).
1627 @findex gnus-group-make-doc-group
1628 @cindex ClariNet Briefs
1629 Make a group based on some file or other
1630 (@code{gnus-group-make-doc-group}). If you give a prefix to this
1631 command, you will be prompted for a file name and a file type.
1632 Currently supported types are @code{babyl}, @code{mbox}, @code{digest},
1633 @code{mmdf}, @code{news}, @code{rnews}, @code{clari-briefs}, and
1634 @code{forward}. If you run this command without a prefix, Gnus will
1635 guess at the file type.
1638 @kindex G DEL (Group)
1639 @findex gnus-group-delete-group
1640 This function will delete the current group
1641 (@code{gnus-group-delete-group}). If given a prefix, this function will
1642 actually delete all the articles in the group, and forcibly remove the
1643 group itself from the face of the Earth. Use a prefix only if you are
1644 absolutely sure of what you are doing.
1648 @findex gnus-group-make-empty-virtual
1649 Make a new, fresh, empty @code{nnvirtual} group
1650 (@code{gnus-group-make-empty-virtual}).
1654 @findex gnus-group-add-to-virtual
1655 Add the current group to an @code{nnvirtual} group
1656 (@code{gnus-group-add-to-virtual}). Uses the process/prefix convention.
1659 @xref{Select Methods} for more information on the various select
1662 @vindex gnus-activate-foreign-newsgroups
1663 If the @code{gnus-activate-foreign-newsgroups} is a positive number,
1664 Gnus will check all foreign groups with this level or lower at startup.
1665 This might take quite a while, especially if you subscribe to lots of
1666 groups from different @sc{nntp} servers.
1669 @node Group Parameters
1670 @section Group Parameters
1671 @cindex group parameters
1673 Gnus stores all information on a group in a list that is usually known
1674 as the @dfn{group info}. This list has from three to six elements.
1675 Here's an example info.
1678 ("nnml:mail.ding" 3 ((1 . 232) 244 (256 . 270)) ((tick 246 249))
1679 (nnml "private") ((to-address . "ding@@ifi.uio.no")))
1682 The first element is the @dfn{group name}, as Gnus knows the group,
1683 anyway. The second element is the @dfn{subscription level}, which
1684 normally is a small integer. The third element is a list of ranges of
1685 read articles. The fourth element is a list of lists of article marks
1686 of various kinds. The fifth element is the select method (or virtual
1687 server, if you like). The sixth element is a list of @dfn{group
1688 parameters}, which is what this section is about.
1690 Any of the last three elements may be missing if they are not required.
1691 In fact, the vast majority of groups will normally only have the first
1692 three elements, which saves quite a lot of cons cells.
1694 The group parameters store information local to a particular group:
1699 If the group parameter list contains an element that looks like
1700 @code{(to-address . "some@@where.com")}, that address will be used by
1701 the backend when doing followups and posts. This is primarily useful in
1702 mail groups that represent closed mailing lists---mailing lists where
1703 it's expected that everybody that writes to the mailing list is
1704 subscribed to it. Since using this parameter ensures that the mail only
1705 goes to the mailing list itself, it means that members won't receive two
1706 copies of your followups.
1708 Using @code{to-address} will actually work whether the group is foreign
1709 or not. Let's say there's a group on the server that is called
1710 @samp{fa.4ad-l}. This is a real newsgroup, but the server has gotten
1711 the articles from a mail-to-news gateway. Posting directly to this
1712 group is therefore impossible---you have to send mail to the mailing
1713 list address instead.
1717 If the group parameter list has an element that looks like
1718 @code{(to-list . "some@@where.com")}, that address will be used when
1719 doing a @kbd{a} in any group. It is totally ignored when doing a
1720 followup---except that if it is present in a news group, you'll get mail
1721 group semantics when doing @kbd{f}.
1723 @item broken-reply-to
1724 @cindex broken-reply-to
1725 Elements like @code{(broken-reply-to . t)} signals that @code{Reply-To}
1726 headers in this group are to be ignored. This can be useful if you're
1727 reading a mailing list group where the listserv has inserted
1728 @code{Reply-To} headers that point back to the listserv itself. This is
1729 broken behavior. So there!
1733 If the group parameter list contains an element like @code{(to-group
1734 . "some.group.name")}, all posts will be sent to that group.
1738 If this symbol is present in the group parameter list, all articles that
1739 are read will be marked as expirable. For an alternative approach,
1740 @pxref{Expiring Mail}.
1743 @cindex total-expire
1744 If this symbol is present, all read articles will be put through the
1745 expiry process, even if they are not marked as expirable. Use with
1750 @vindex nnmail-expiry-wait-function
1751 If the group parameter has an element that looks like @code{(expiry-wait
1752 . 10)}, this value will override any @code{nnmail-expiry-wait} and
1753 @code{nnmail-expiry-wait-function} when expiring expirable messages.
1754 The value can either be a number of days (not necessarily an integer) or
1755 the symbols @code{never} or @code{immediate}.
1758 Elements that look like @code{(score-file . "file")} will make
1759 @samp{file} into the current score file for the group in question. This
1760 means that all score commands you issue will end up in that file.
1763 When unsubscribing to a mailing list you should never send the
1764 unsubscription notice to the mailing list itself. Instead, you'd send
1765 messages to the administrative address. This parameter allows you to
1766 put the admin address somewhere convenient.
1769 This parameter allows you to enter a arbitrary comment on the group.
1771 @item @var{(variable form)}
1772 You can use the group parameters to set variables local to the group you
1773 are entering. Say you want to turn threading off in
1774 @samp{news.answers}. You'd then put @code{(gnus-show-threads nil)} in
1775 the group parameters of that group. @code{gnus-show-threads} will be
1776 made into a local variable in the summary buffer you enter, and the form
1777 @code{nil} will be @code{eval}ed there.
1779 This can also be used as a group-specific hook function, if you'd like.
1780 If you want to hear a beep when you enter the group
1781 @samp{alt.binaries.pictures.furniture}, you could put something like
1782 @code{(dummy-variable (ding))} in the parameters of that group.
1783 @code{dummy-variable} will be set to the result of the @code{(ding)}
1784 form, but who cares?
1788 If you want to change the group info you can use the @kbd{G E} command
1789 to enter a buffer where you can edit it.
1791 You usually don't want to edit the entire group info, so you'd be better
1792 off using the @kbd{G p} command to just edit the group parameters.
1795 @node Listing Groups
1796 @section Listing Groups
1797 @cindex group listing
1799 These commands all list various slices of the groups that are available.
1807 @findex gnus-group-list-groups
1808 List all groups that have unread articles
1809 (@code{gnus-group-list-groups}). If the numeric prefix is used, this
1810 command will list only groups of level ARG and lower. By default, it
1811 only lists groups of level five or lower (i.e., just subscribed groups).
1817 @findex gnus-group-list-all-groups
1818 List all groups, whether they have unread articles or not
1819 (@code{gnus-group-list-all-groups}). If the numeric prefix is used,
1820 this command will list only groups of level ARG and lower. By default,
1821 it lists groups of level seven or lower (i.e., just subscribed and
1822 unsubscribed groups).
1826 @findex gnus-group-list-level
1827 List all unread groups on a specific level
1828 (@code{gnus-group-list-level}). If given a prefix, also list the groups
1829 with no unread articles.
1833 @findex gnus-group-list-killed
1834 List all killed groups (@code{gnus-group-list-killed}). If given a
1835 prefix argument, really list all groups that are available, but aren't
1836 currently (un)subscribed. This could entail reading the active file
1841 @findex gnus-group-list-zombies
1842 List all zombie groups (@code{gnus-group-list-zombies}).
1846 @findex gnus-group-list-matching
1847 List all subscribed groups with unread articles that match a regexp
1848 (@code{gnus-group-list-matching}).
1852 @findex gnus-group-list-all-matching
1853 List groups that match a regexp (@code{gnus-group-list-all-matching}).
1857 @findex gnus-group-list-active
1858 List absolutely all groups that are in the active file(s) of the
1859 server(s) you are connected to (@code{gnus-group-list-active}). This
1860 might very well take quite a while. It might actually be a better idea
1861 to do a @kbd{A m} to list all matching, and just give @samp{.} as the
1866 @findex gnus-group-apropos
1867 List all groups that have names that match a regexp
1868 (@code{gnus-group-apropos}).
1872 @findex gnus-group-description-apropos
1873 List all groups that have names or descriptions that match a regexp
1874 (@code{gnus-group-description-apropos}).
1878 @vindex gnus-permanently-visible-groups
1879 @cindex visible group parameter
1880 Groups that match the @code{gnus-permanently-visible-groups} regexp will
1881 always be shown, whether they have unread articles or not. You can also
1882 add the @code{visible} element to the group parameters in question to
1883 get the same effect.
1885 @vindex gnus-list-groups-with-ticked-articles
1886 Groups that have just ticked articles in it are normally listed in the
1887 group buffer. If @code{gnus-list-groups-with-ticked-articles} is
1888 @code{nil}, these groups will be treated just like totally empty
1889 groups. It is @code{t} by default.
1892 @node Sorting Groups
1893 @section Sorting Groups
1894 @cindex sorting groups
1896 @kindex C-c C-s (Group)
1897 @findex gnus-group-sort-groups
1898 @vindex gnus-group-sort-function
1899 The @kbd{C-c C-s} (@code{gnus-group-sort-groups}) command sorts the
1900 group buffer according to the function(s) given by the
1901 @code{gnus-group-sort-function} variable. Available sorting functions
1906 @item gnus-group-sort-by-alphabet
1907 @findex gnus-group-sort-by-alphabet
1908 Sort the group names alphabetically. This is the default.
1910 @item gnus-group-sort-by-level
1911 @findex gnus-group-sort-by-level
1912 Sort by group level.
1914 @item gnus-group-sort-by-score
1915 @findex gnus-group-sort-by-score
1916 Sort by group score.
1918 @item gnus-group-sort-by-rank
1919 @findex gnus-group-sort-by-rank
1920 Sort by group score and then the group level. The level and the score
1921 are, when taken together, the group's @dfn{rank}.
1923 @item gnus-group-sort-by-unread
1924 @findex gnus-group-sort-by-unread
1925 Sort by number of unread articles.
1927 @item gnus-group-sort-by-method
1928 @findex gnus-group-sort-by-method
1929 Sort by alphabetically on the select method.
1934 @code{gnus-group-sort-function} can also be a list of sorting
1935 functions. In that case, the most significant sort key function must be
1939 There are also a number of commands for sorting directly according to
1940 some sorting criteria:
1944 @kindex G S a (Group)
1945 @findex gnus-group-sort-groups-by-alphabet
1946 Sort the group buffer alphabetically by group name
1947 (@code{gnus-group-sort-groups-by-alphabet}).
1950 @kindex G S u (Group)
1951 @findex gnus-group-sort-groups-by-unread
1952 Sort the group buffer by the number of unread articles
1953 (@code{gnus-group-sort-groups-by-unread}).
1956 @kindex G S l (Group)
1957 @findex gnus-group-sort-groups-by-level
1958 Sort the group buffer by group level
1959 (@code{gnus-group-sort-groups-by-level}).
1962 @kindex G S v (Group)
1963 @findex gnus-group-sort-groups-by-score
1964 Sort the group buffer by group score
1965 (@code{gnus-group-sort-groups-by-score}).
1968 @kindex G S r (Group)
1969 @findex gnus-group-sort-groups-by-rank
1970 Sort the group buffer by group level
1971 (@code{gnus-group-sort-groups-by-rank}).
1974 @kindex G S m (Group)
1975 @findex gnus-group-sort-groups-by-method
1976 Sort the group buffer alphabetically by backend name
1977 (@code{gnus-group-sort-groups-by-method}).
1981 When given a prefix, all these commands will sort in reverse order.
1984 @node Group Maintenance
1985 @section Group Maintenance
1986 @cindex bogus groups
1991 @findex gnus-group-check-bogus-groups
1992 Find bogus groups and delete them
1993 (@code{gnus-group-check-bogus-groups}).
1997 @findex gnus-find-new-newsgroups
1998 Find new groups and process them (@code{gnus-find-new-newsgroups}). If
1999 given a prefix, use the @code{ask-server} method to query the server for
2003 @kindex C-c C-x (Group)
2004 @findex gnus-group-expire-articles
2005 Run all expirable articles in the current group through the expiry
2006 process (if any) (@code{gnus-group-expire-articles}).
2009 @kindex C-c M-C-x (Group)
2010 @findex gnus-group-expire-all-groups
2011 Run all articles in all groups through the expiry process
2012 (@code{gnus-group-expire-all-groups}).
2017 @node Browse Foreign Server
2018 @section Browse Foreign Server
2019 @cindex foreign servers
2020 @cindex browsing servers
2025 @findex gnus-group-browse-foreign-server
2026 You will be queried for a select method and a server name. Gnus will
2027 then attempt to contact this server and let you browse the groups there
2028 (@code{gnus-group-browse-foreign-server}).
2031 @findex gnus-browse-server-mode
2032 A new buffer with a list of available groups will appear. This buffer
2033 will be use the @code{gnus-browse-server-mode}. This buffer looks a bit
2034 (well, a lot) like a normal group buffer, but with one major difference
2035 - you can't enter any of the groups. If you want to read any of the
2036 news available on that server, you have to subscribe to the groups you
2037 think may be interesting, and then you have to exit this buffer. The
2038 new groups will be added to the group buffer, and then you can read them
2039 as you would any other group.
2041 Future versions of Gnus may possibly permit reading groups straight from
2044 Here's a list of keystrokes available in the browse mode:
2049 @findex gnus-group-next-group
2050 Go to the next group (@code{gnus-group-next-group}).
2054 @findex gnus-group-prev-group
2055 Go to the previous group (@code{gnus-group-prev-group}).
2058 @kindex SPACE (Browse)
2059 @findex gnus-browse-read-group
2060 Enter the current group and display the first article
2061 (@code{gnus-browse-read-group}).
2064 @kindex RET (Browse)
2065 @findex gnus-browse-select-group
2066 Enter the current group (@code{gnus-browse-select-group}).
2070 @findex gnus-browse-unsubscribe-current-group
2071 Unsubscribe to the current group, or, as will be the case here,
2072 subscribe to it (@code{gnus-browse-unsubscribe-current-group}).
2078 @findex gnus-browse-exit
2079 Exit browse mode (@code{gnus-browse-exit}).
2083 @findex gnus-browse-describe-briefly
2084 Describe browse mode briefly (well, there's not much to describe, is
2085 there) (@code{gnus-browse-describe-briefly}).
2090 @section Exiting Gnus
2091 @cindex exiting Gnus
2093 Yes, Gnus is ex(c)iting.
2098 @findex gnus-group-suspend
2099 Suspend Gnus (@code{gnus-group-suspend}). This doesn't really exit Gnus,
2100 but it kills all buffers except the Group buffer. I'm not sure why this
2101 is a gain, but then who am I to judge?
2105 @findex gnus-group-exit
2106 Quit Gnus (@code{gnus-group-exit}).
2110 @findex gnus-group-quit
2111 Quit Gnus without saving any startup files (@code{gnus-group-quit}).
2114 @vindex gnus-exit-gnus-hook
2115 @vindex gnus-suspend-gnus-hook
2116 @code{gnus-suspend-gnus-hook} is called when you suspend Gnus and
2117 @code{gnus-exit-gnus-hook} is called when you quit Gnus, while
2118 @code{gnus-after-exiting-gnus-hook} is called as the final item when
2123 If you wish to completely unload Gnus and all its adherents, you can use
2124 the @code{gnus-unload} command. This command is also very handy when
2125 trying to customize meta-variables.
2130 Miss Lisa Cannifax, while sitting in English class, feels her feet go
2131 numbly heavy and herself fall into a hazy trance as the boy sitting
2132 behind her drew repeated lines with his pencil across the back of her
2138 @section Group Topics
2141 If you read lots and lots of groups, it might be convenient to group
2142 them hierarchically according to topics. You put your Emacs groups over
2143 here, your sex groups over there, and the rest (what, two groups or so?)
2144 you put in some misc section that you never bother with anyway. You can
2145 even group the Emacs sex groups as a sub-topic to either the Emacs
2146 groups or the sex groups---or both! Go wild!
2148 @findex gnus-topic-mode
2150 To get this @emph{fab} functionality you simply turn on (ooh!) the
2151 @code{gnus-topic} minor mode---type @kbd{t} in the group buffer. (This
2152 is a toggling command.)
2154 Go ahead, just try it. I'll still be here when you get back. La de
2155 dum... Nice tune, that... la la la... What, you're back? Yes, and now
2156 press @kbd{l}. There. All your groups are now listed under
2157 @samp{misc}. Doesn't that make you feel all warm and fuzzy? Hot and
2160 If you want this permanently enabled, you should add that minor mode to
2161 the hook for the group mode:
2164 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
2168 * Topic Variables:: How to customize the topics the Lisp Way.
2169 * Topic Commands:: Interactive E-Z commands.
2170 * Topic Topology:: A map of the world.
2174 @node Topic Variables
2175 @subsection Topic Variables
2176 @cindex topic variables
2178 @vindex gnus-topic-unique
2179 If @code{gnus-topic-unique} is non-@code{nil}, each group will be member
2180 of (tops) one topic each. If this is @code{nil}, each group might end
2181 up being a member of several topics.
2183 Now, if you select a topic, if will fold/unfold that topic, which is
2184 really neat, I think.
2186 @vindex gnus-topic-line-format
2187 The topic lines themselves are created according to the
2188 @code{gnus-topic-line-format} variable. @xref{Formatting Variables}.
2189 Elements allowed are: