|
0
|
1 \input texinfo @c -*-texinfo-*-
|
|
|
2
|
|
16
|
3 @setfilename gnus
|
|
44
|
4 @settitle Gnus 5.4.37 Manual
|
|
0
|
5 @synindex fn cp
|
|
|
6 @synindex vr cp
|
|
|
7 @synindex pg cp
|
|
|
8 @iftex
|
|
|
9 @finalout
|
|
|
10 @end iftex
|
|
|
11 @setchapternewpage odd
|
|
|
12
|
|
|
13 @iftex
|
|
|
14 @iflatex
|
|
|
15 \documentclass[twoside,a4paper,openright]{book}
|
|
|
16 \usepackage[latin1]{inputenc}
|
|
|
17 \usepackage{pagestyle}
|
|
|
18 \usepackage{epsfig}
|
|
|
19 \fontfamily{bembo}\selectfont
|
|
|
20
|
|
|
21 \makeindex
|
|
|
22 \begin{document}
|
|
|
23
|
|
|
24 \newcommand{\gnuschaptername}{}
|
|
|
25 \newcommand{\gnussectionname}{}
|
|
|
26
|
|
|
27 \newcommand{\gnusbackslash}{/}
|
|
|
28
|
|
|
29 \newcommand{\gnusxref}[1]{See ``#1'' on page \pageref{#1}}
|
|
|
30 \newcommand{\gnuspxref}[1]{see ``#1'' on page \pageref{#1}}
|
|
|
31
|
|
|
32 \newcommand{\gnuskindex}[1]{\index{#1}}
|
|
|
33 \newcommand{\gnusindex}[1]{\index{#1}}
|
|
|
34
|
|
|
35 \newcommand{\gnustt}[1]{{\textbf{\textsf{#1}}}}
|
|
|
36 \newcommand{\gnuscode}[1]{\gnustt{#1}}
|
|
|
37 \newcommand{\gnussamp}[1]{``\gnustt{#1}''}
|
|
|
38 \newcommand{\gnuslisp}[1]{\gnustt{#1}}
|
|
|
39 \newcommand{\gnuskbd}[1]{`\gnustt{#1}'}
|
|
|
40 \newcommand{\gnusfile}[1]{`\gnustt{#1}'}
|
|
|
41 \newcommand{\gnusdfn}[1]{\textit{#1}}
|
|
|
42 \newcommand{\gnusi}[1]{\textit{#1}}
|
|
|
43 \newcommand{\gnusstrong}[1]{\textbf{#1}}
|
|
|
44 \newcommand{\gnusemph}[1]{\textit{#1}}
|
|
|
45 \newcommand{\gnusvar}[1]{\textsl{\textsf{#1}}}
|
|
|
46 \newcommand{\gnussc}[1]{\textsc{#1}}
|
|
|
47 \newcommand{\gnustitle}[1]{{\huge\textbf{#1}}}
|
|
|
48 \newcommand{\gnusauthor}[1]{{\large\textbf{#1}}}
|
|
|
49
|
|
|
50 \newcommand{\gnusbullet}{{${\bullet}$}}
|
|
|
51 \newcommand{\gnusdollar}{\$}
|
|
|
52 \newcommand{\gnusampersand}{\&}
|
|
|
53 \newcommand{\gnuspercent}{\%}
|
|
|
54 \newcommand{\gnushash}{\#}
|
|
|
55 \newcommand{\gnushat}{\symbol{"5E}}
|
|
|
56 \newcommand{\gnusunderline}{\symbol{"5F}}
|
|
16
|
57 \newcommand{\gnusnot}{$\neg$}
|
|
0
|
58 \newcommand{\gnustilde}{\symbol{"7E}}
|
|
|
59 \newcommand{\gnusless}{{$<$}}
|
|
|
60 \newcommand{\gnusgreater}{{$>$}}
|
|
|
61
|
|
|
62 \newcommand{\gnushead}{\raisebox{-1cm}{\epsfig{figure=gnus-head.eps,height=1cm}}}
|
|
|
63 \newcommand{\gnusinteresting}{
|
|
|
64 \marginpar[\hspace{2.5cm}\gnushead]{\gnushead}
|
|
|
65 }
|
|
|
66
|
|
16
|
67 \newcommand{\gnuscleardoublepage}{\ifodd\count0\mbox{}\clearpage\thispagestyle{empty}\mbox{}\clearpage\else\clearpage\fi}
|
|
|
68
|
|
|
69 \newcommand{\gnuspagechapter}[1]{
|
|
|
70 {\mbox{}}
|
|
|
71 }
|
|
|
72
|
|
|
73 \newdimen{\gnusdimen}
|
|
|
74 \gnusdimen 0pt
|
|
|
75
|
|
|
76 \newcommand{\gnuschapter}[2]{
|
|
|
77 \gnuscleardoublepage
|
|
|
78 \ifdim \gnusdimen = 0pt\setcounter{page}{1}\pagestyle{gnus}\pagenumbering{arabic} \gnusdimen 1pt\fi
|
|
|
79 \chapter{#2}
|
|
0
|
80 \renewcommand{\gnussectionname}{}
|
|
16
|
81 \renewcommand{\gnuschaptername}{#2}
|
|
0
|
82 \thispagestyle{empty}
|
|
16
|
83 \hspace*{-2cm}
|
|
|
84 \begin{picture}(500,500)(0,0)
|
|
|
85 \put(0,0){\makebox(480,350)[tr]{#1}}
|
|
|
86 \put(40,300){\makebox(500,50)[bl]{{\Huge\bf{#2}}}}
|
|
|
87 \end{picture}
|
|
0
|
88 \clearpage
|
|
|
89 }
|
|
|
90
|
|
16
|
91 \newcommand{\gnusitemx}[1]{\mbox{}\vspace*{-\itemsep}\vspace*{-\parsep}\item#1}
|
|
0
|
92
|
|
|
93 \newcommand{\gnussection}[1]{
|
|
|
94 \renewcommand{\gnussectionname}{#1}
|
|
|
95 \section{#1}
|
|
|
96 }
|
|
|
97
|
|
|
98 \newenvironment{codelist}%
|
|
|
99 {\begin{list}{}{
|
|
|
100 }
|
|
|
101 }{\end{list}}
|
|
|
102
|
|
|
103 \newenvironment{kbdlist}%
|
|
|
104 {\begin{list}{}{
|
|
|
105 \labelwidth=0cm
|
|
|
106 }
|
|
|
107 }{\end{list}}
|
|
|
108
|
|
|
109 \newenvironment{dfnlist}%
|
|
|
110 {\begin{list}{}{
|
|
|
111 }
|
|
|
112 }{\end{list}}
|
|
|
113
|
|
|
114 \newenvironment{stronglist}%
|
|
|
115 {\begin{list}{}{
|
|
|
116 }
|
|
|
117 }{\end{list}}
|
|
|
118
|
|
|
119 \newenvironment{samplist}%
|
|
|
120 {\begin{list}{}{
|
|
|
121 }
|
|
|
122 }{\end{list}}
|
|
|
123
|
|
|
124 \newenvironment{varlist}%
|
|
|
125 {\begin{list}{}{
|
|
|
126 }
|
|
|
127 }{\end{list}}
|
|
|
128
|
|
|
129 \newenvironment{emphlist}%
|
|
|
130 {\begin{list}{}{
|
|
|
131 }
|
|
|
132 }{\end{list}}
|
|
|
133
|
|
16
|
134 \newlength\gnusheadtextwidth
|
|
|
135 \setlength{\gnusheadtextwidth}{\headtextwidth}
|
|
|
136 \addtolength{\gnusheadtextwidth}{1cm}
|
|
|
137
|
|
|
138 \newpagestyle{gnuspreamble}%
|
|
0
|
139 {
|
|
|
140 {
|
|
|
141 \ifodd\count0
|
|
|
142 {
|
|
16
|
143 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\mbox{}}\textbf{\hfill\roman{page}}}
|
|
0
|
144 }
|
|
|
145 \else
|
|
|
146 {
|
|
16
|
147 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\roman{page}\hfill\mbox{}}}
|
|
|
148 }
|
|
0
|
149 }
|
|
|
150 \fi
|
|
|
151 }
|
|
|
152 }
|
|
|
153 {
|
|
|
154 \ifodd\count0
|
|
|
155 \mbox{} \hfill
|
|
|
156 \raisebox{-0.5cm}{\epsfig{figure=gnus-big-logo.eps,height=1cm}}
|
|
|
157 \else
|
|
|
158 \raisebox{-0.5cm}{\epsfig{figure=gnus-big-logo.eps,height=1cm}}
|
|
|
159 \hfill \mbox{}
|
|
|
160 \fi
|
|
|
161 }
|
|
16
|
162
|
|
|
163 \newpagestyle{gnusindex}%
|
|
|
164 {
|
|
|
165 {
|
|
|
166 \ifodd\count0
|
|
|
167 {
|
|
|
168 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\gnuschaptername\hfill\arabic{page}}}}
|
|
|
169 }
|
|
|
170 \else
|
|
|
171 {
|
|
|
172 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}
|
|
|
173 }
|
|
|
174 \fi
|
|
|
175 }
|
|
|
176 }
|
|
|
177 {
|
|
|
178 \ifodd\count0
|
|
|
179 \mbox{} \hfill
|
|
|
180 \raisebox{-0.5cm}{\epsfig{figure=gnus-big-logo.eps,height=1cm}}
|
|
|
181 \else
|
|
|
182 \raisebox{-0.5cm}{\epsfig{figure=gnus-big-logo.eps,height=1cm}}
|
|
|
183 \hfill \mbox{}
|
|
|
184 \fi
|
|
|
185 }
|
|
|
186
|
|
|
187 \newpagestyle{gnus}%
|
|
|
188 {
|
|
|
189 {
|
|
|
190 \ifodd\count0
|
|
|
191 {
|
|
|
192 \hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{chapter}.\arabic{section}} \textbf{\gnussectionname\hfill\arabic{page}}}}
|
|
|
193 }
|
|
|
194 \else
|
|
|
195 {
|
|
|
196 \hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}
|
|
|
197 }
|
|
|
198 \fi
|
|
|
199 }
|
|
|
200 }
|
|
|
201 {
|
|
|
202 \ifodd\count0
|
|
|
203 \mbox{} \hfill
|
|
|
204 \raisebox{-0.5cm}{\epsfig{figure=gnus-big-logo.eps,height=1cm}}
|
|
|
205 \else
|
|
|
206 \raisebox{-0.5cm}{\epsfig{figure=gnus-big-logo.eps,height=1cm}}
|
|
|
207 \hfill \mbox{}
|
|
|
208 \fi
|
|
|
209 }
|
|
|
210
|
|
|
211 \pagenumbering{roman}
|
|
|
212 \pagestyle{gnuspreamble}
|
|
0
|
213
|
|
|
214 @end iflatex
|
|
|
215 @end iftex
|
|
|
216
|
|
|
217 @iftex
|
|
|
218 @iflatex
|
|
|
219 \begin{titlepage}
|
|
|
220 {
|
|
|
221
|
|
|
222 %\addtolength{\oddsidemargin}{-5cm}
|
|
|
223 %\addtolength{\evensidemargin}{-5cm}
|
|
|
224 \parindent=0cm
|
|
|
225 \addtolength{\textheight}{2cm}
|
|
|
226
|
|
|
227 \gnustitle{\gnustitlename}\\
|
|
|
228 \rule{15cm}{1mm}\\
|
|
|
229 \vfill
|
|
|
230 \hspace*{-1cm}\epsfig{figure=gnus-big-logo.eps,height=15cm}
|
|
|
231 \vfill
|
|
|
232 \rule{15cm}{1mm}\\
|
|
|
233 \gnusauthor{by Lars Magne Ingebrigtsen}
|
|
|
234 \newpage
|
|
|
235 }
|
|
|
236
|
|
|
237 \mbox{}
|
|
|
238 \vfill
|
|
|
239
|
|
|
240 \thispagestyle{empty}
|
|
|
241
|
|
|
242 Copyright \copyright{} 1995,96 Free Software Foundation, Inc.
|
|
|
243
|
|
|
244 Permission is granted to make and distribute verbatim copies of
|
|
|
245 this manual provided the copyright notice and this permission notice
|
|
|
246 are preserved on all copies.
|
|
|
247
|
|
|
248 Permission is granted to copy and distribute modified versions of this
|
|
|
249 manual under the conditions for verbatim copying, provided that the
|
|
|
250 entire resulting derived work is distributed under the terms of a
|
|
|
251 permission notice identical to this one.
|
|
|
252
|
|
|
253 Permission is granted to copy and distribute translations of this manual
|
|
|
254 into another language, under the above conditions for modified versions.
|
|
|
255
|
|
|
256 \newpage
|
|
|
257 \end{titlepage}
|
|
|
258 @end iflatex
|
|
|
259 @end iftex
|
|
|
260
|
|
|
261 @ifinfo
|
|
|
262
|
|
|
263 This file documents Gnus, the GNU Emacs newsreader.
|
|
|
264
|
|
|
265 Copyright (C) 1995,96 Free Software Foundation, Inc.
|
|
|
266
|
|
|
267 Permission is granted to make and distribute verbatim copies of
|
|
|
268 this manual provided the copyright notice and this permission notice
|
|
|
269 are preserved on all copies.
|
|
|
270
|
|
|
271 @ignore
|
|
|
272 Permission is granted to process this file through Tex and print the
|
|
|
273 results, provided the printed document carries copying permission
|
|
|
274 notice identical to this one except for the removal of this paragraph
|
|
|
275 (this paragraph not being relevant to the printed manual).
|
|
|
276
|
|
|
277 @end ignore
|
|
|
278 Permission is granted to copy and distribute modified versions of this
|
|
|
279 manual under the conditions for verbatim copying, provided also that the
|
|
|
280 entire resulting derived work is distributed under the terms of a
|
|
|
281 permission notice identical to this one.
|
|
|
282
|
|
|
283 Permission is granted to copy and distribute translations of this manual
|
|
|
284 into another language, under the above conditions for modified versions.
|
|
|
285 @end ifinfo
|
|
|
286
|
|
|
287 @tex
|
|
|
288
|
|
|
289 @titlepage
|
|
44
|
290 @title Gnus 5.4.37 Manual
|
|
0
|
291
|
|
|
292 @author by Lars Magne Ingebrigtsen
|
|
|
293 @page
|
|
|
294
|
|
|
295 @vskip 0pt plus 1filll
|
|
34
|
296 Copyright @copyright{} 1995,96,97 Free Software Foundation, Inc.
|
|
0
|
297
|
|
|
298 Permission is granted to make and distribute verbatim copies of
|
|
|
299 this manual provided the copyright notice and this permission notice
|
|
|
300 are preserved on all copies.
|
|
|
301
|
|
|
302 Permission is granted to copy and distribute modified versions of this
|
|
|
303 manual under the conditions for verbatim copying, provided that the
|
|
|
304 entire resulting derived work is distributed under the terms of a
|
|
|
305 permission notice identical to this one.
|
|
|
306
|
|
|
307 Permission is granted to copy and distribute translations of this manual
|
|
|
308 into another language, under the above conditions for modified versions.
|
|
|
309
|
|
|
310 @end titlepage
|
|
|
311 @page
|
|
|
312
|
|
|
313 @end tex
|
|
|
314
|
|
|
315
|
|
|
316 @node Top
|
|
|
317 @top The Gnus Newsreader
|
|
|
318
|
|
|
319 @ifinfo
|
|
|
320
|
|
|
321 You can read news (and mail) from within Emacs by using Gnus. The news
|
|
|
322 can be gotten by any nefarious means you can think of---@sc{nntp}, local
|
|
|
323 spool or your mbox file. All at the same time, if you want to push your
|
|
|
324 luck.
|
|
|
325
|
|
44
|
326 This manual corresponds to Gnus 5.4.37.
|
|
16
|
327
|
|
0
|
328 @end ifinfo
|
|
|
329
|
|
|
330 @iftex
|
|
|
331
|
|
|
332 @iflatex
|
|
16
|
333 \tableofcontents
|
|
|
334 \gnuscleardoublepage
|
|
0
|
335 @end iflatex
|
|
|
336
|
|
|
337 Gnus is the advanced, self-documenting, customizable, extensible
|
|
|
338 unreal-time newsreader for GNU Emacs.
|
|
|
339
|
|
|
340 Oops. That sounds oddly familiar, so let's start over again to avoid
|
|
|
341 being accused of plagiarism:
|
|
|
342
|
|
|
343 Gnus is a message-reading laboratory. It will let you look at just
|
|
|
344 about anything as if it were a newsgroup. You can read mail with it,
|
|
|
345 you can browse directories with it, you can @code{ftp} with it---you can
|
|
|
346 even read news with it!
|
|
|
347
|
|
|
348 Gnus tries to empower people who read news the same way Emacs empowers
|
|
|
349 people who edit text. Gnus sets no limits to what the user should be
|
|
|
350 allowed to do. Users are encouraged to extend Gnus to make it behave
|
|
|
351 like they want it to behave. A program should not control people;
|
|
|
352 people should be empowered to do what they want by using (or abusing)
|
|
|
353 the program.
|
|
|
354
|
|
|
355 @end iftex
|
|
|
356
|
|
|
357
|
|
|
358 @menu
|
|
|
359 * Starting Up:: Finding news can be a pain.
|
|
|
360 * The Group Buffer:: Selecting, subscribing and killing groups.
|
|
|
361 * The Summary Buffer:: Reading, saving and posting articles.
|
|
|
362 * The Article Buffer:: Displaying and handling articles.
|
|
|
363 * Composing Messages:: Information on sending mail and news.
|
|
|
364 * Select Methods:: Gnus reads all messages from various select methods.
|
|
|
365 * Scoring:: Assigning values to articles.
|
|
|
366 * Various:: General purpose settings.
|
|
|
367 * The End:: Farewell and goodbye.
|
|
|
368 * Appendices:: Terminology, Emacs intro, FAQ, History, Internals.
|
|
|
369 * Index:: Variable, function and concept index.
|
|
|
370 * Key Index:: Key Index.
|
|
|
371 @end menu
|
|
|
372
|
|
|
373 @node Starting Up
|
|
|
374 @chapter Starting Gnus
|
|
|
375 @cindex starting up
|
|
|
376
|
|
|
377 @kindex M-x gnus
|
|
|
378 @findex gnus
|
|
|
379 If your system administrator has set things up properly, starting Gnus
|
|
|
380 and reading news is extremely easy---you just type @kbd{M-x gnus} in
|
|
|
381 your Emacs.
|
|
|
382
|
|
|
383 @findex gnus-other-frame
|
|
|
384 @kindex M-x gnus-other-frame
|
|
|
385 If you want to start Gnus in a different frame, you can use the command
|
|
|
386 @kbd{M-x gnus-other-frame} instead.
|
|
|
387
|
|
|
388 If things do not go smoothly at startup, you have to twiddle some
|
|
|
389 variables.
|
|
|
390
|
|
|
391 @menu
|
|
|
392 * Finding the News:: Choosing a method for getting news.
|
|
|
393 * The First Time:: What does Gnus do the first time you start it?
|
|
|
394 * The Server is Down:: How can I read my mail then?
|
|
16
|
395 * Slave Gnusae:: You can have more than one Gnus active at a time.
|
|
0
|
396 * Fetching a Group:: Starting Gnus just to read a group.
|
|
|
397 * New Groups:: What is Gnus supposed to do with new groups?
|
|
|
398 * Startup Files:: Those pesky startup files---@file{.newsrc}.
|
|
|
399 * Auto Save:: Recovering from a crash.
|
|
|
400 * The Active File:: Reading the active file over a slow line Takes Time.
|
|
16
|
401 * Changing Servers:: You may want to move from one server to another.
|
|
0
|
402 * Startup Variables:: Other variables you might change.
|
|
|
403 @end menu
|
|
|
404
|
|
|
405
|
|
|
406 @node Finding the News
|
|
|
407 @section Finding the News
|
|
16
|
408 @cindex finding news
|
|
0
|
409
|
|
|
410 @vindex gnus-select-method
|
|
|
411 @c @head
|
|
|
412 The @code{gnus-select-method} variable says where Gnus should look for
|
|
|
413 news. This variable should be a list where the first element says
|
|
|
414 @dfn{how} and the second element says @dfn{where}. This method is your
|
|
|
415 native method. All groups that are not fetched with this method are
|
|
|
416 foreign groups.
|
|
|
417
|
|
|
418 For instance, if the @samp{news.somewhere.edu} @sc{nntp} server is where
|
|
|
419 you want to get your daily dosage of news from, you'd say:
|
|
|
420
|
|
|
421 @lisp
|
|
|
422 (setq gnus-select-method '(nntp "news.somewhere.edu"))
|
|
|
423 @end lisp
|
|
|
424
|
|
|
425 If you want to read directly from the local spool, say:
|
|
|
426
|
|
|
427 @lisp
|
|
|
428 (setq gnus-select-method '(nnspool ""))
|
|
|
429 @end lisp
|
|
|
430
|
|
|
431 If you can use a local spool, you probably should, as it will almost
|
|
|
432 certainly be much faster.
|
|
|
433
|
|
|
434 @vindex gnus-nntpserver-file
|
|
|
435 @cindex NNTPSERVER
|
|
|
436 @cindex @sc{nntp} server
|
|
|
437 If this variable is not set, Gnus will take a look at the
|
|
|
438 @code{NNTPSERVER} environment variable. If that variable isn't set,
|
|
|
439 Gnus will see whether @code{gnus-nntpserver-file}
|
|
|
440 (@file{/etc/nntpserver} by default) has any opinions on the matter. If
|
|
|
441 that fails as well, Gnus will will try to use the machine that is
|
|
16
|
442 running Emacs as an @sc{nntp} server. That's a long shot, though.
|
|
0
|
443
|
|
|
444 @vindex gnus-nntp-server
|
|
|
445 If @code{gnus-nntp-server} is set, this variable will override
|
|
|
446 @code{gnus-select-method}. You should therefore set
|
|
|
447 @code{gnus-nntp-server} to @code{nil}, which is what it is by default.
|
|
|
448
|
|
|
449 @vindex gnus-secondary-servers
|
|
|
450 You can also make Gnus prompt you interactively for the name of an
|
|
|
451 @sc{nntp} server. If you give a non-numerical prefix to @code{gnus}
|
|
|
452 (i.e., @kbd{C-u M-x gnus}), Gnus will let you choose between the servers
|
|
|
453 in the @code{gnus-secondary-servers} list (if any). You can also just
|
|
|
454 type in the name of any server you feel like visiting.
|
|
|
455
|
|
|
456 @findex gnus-group-browse-foreign-server
|
|
|
457 @kindex B (Group)
|
|
|
458 However, if you use one @sc{nntp} server regularly and are just
|
|
|
459 interested in a couple of groups from a different server, you would be
|
|
|
460 better served by using the @kbd{B} command in the group buffer. It will
|
|
|
461 let you have a look at what groups are available, and you can subscribe
|
|
|
462 to any of the groups you want to. This also makes @file{.newsrc}
|
|
|
463 maintenance much tidier. @xref{Foreign Groups}.
|
|
|
464
|
|
|
465 @vindex gnus-secondary-select-methods
|
|
|
466 @c @head
|
|
|
467 A slightly different approach to foreign groups is to set the
|
|
|
468 @code{gnus-secondary-select-methods} variable. The select methods
|
|
|
469 listed in this variable are in many ways just as native as the
|
|
|
470 @code{gnus-select-method} server. They will also be queried for active
|
|
|
471 files during startup (if that's required), and new newsgroups that
|
|
|
472 appear on these servers will be subscribed (or not) just as native
|
|
|
473 groups are.
|
|
|
474
|
|
|
475 For instance, if you use the @code{nnmbox} backend to read your mail, you
|
|
|
476 would typically set this variable to
|
|
|
477
|
|
|
478 @lisp
|
|
|
479 (setq gnus-secondary-select-methods '((nnmbox "")))
|
|
|
480 @end lisp
|
|
|
481
|
|
|
482
|
|
|
483 @node The First Time
|
|
|
484 @section The First Time
|
|
|
485 @cindex first time usage
|
|
|
486
|
|
|
487 If no startup files exist, Gnus will try to determine what groups should
|
|
|
488 be subscribed by default.
|
|
|
489
|
|
|
490 @vindex gnus-default-subscribed-newsgroups
|
|
|
491 If the variable @code{gnus-default-subscribed-newsgroups} is set, Gnus
|
|
|
492 will subscribe you to just those groups in that list, leaving the rest
|
|
|
493 killed. Your system administrator should have set this variable to
|
|
|
494 something useful.
|
|
|
495
|
|
|
496 Since she hasn't, Gnus will just subscribe you to a few arbitrarily
|
|
|
497 picked groups (i.e., @samp{*.newusers}). (@dfn{Arbitrary} is here
|
|
|
498 defined as @dfn{whatever Lars thinks you should read}.)
|
|
|
499
|
|
|
500 You'll also be subscribed to the Gnus documentation group, which should
|
|
|
501 help you with most common problems.
|
|
|
502
|
|
|
503 If @code{gnus-default-subscribed-newsgroups} is @code{t}, Gnus will just
|
|
|
504 use the normal functions for handling new groups, and not do anything
|
|
|
505 special.
|
|
|
506
|
|
|
507
|
|
|
508 @node The Server is Down
|
|
|
509 @section The Server is Down
|
|
|
510 @cindex server errors
|
|
|
511
|
|
|
512 If the default server is down, Gnus will understandably have some
|
|
|
513 problems starting. However, if you have some mail groups in addition to
|
|
|
514 the news groups, you may want to start Gnus anyway.
|
|
|
515
|
|
|
516 Gnus, being the trusting sort of program, will ask whether to proceed
|
|
|
517 without a native select method if that server can't be contacted. This
|
|
|
518 will happen whether the server doesn't actually exist (i.e., you have
|
|
|
519 given the wrong address) or the server has just momentarily taken ill
|
|
|
520 for some reason or other. If you decide to continue and have no foreign
|
|
|
521 groups, you'll find it difficult to actually do anything in the group
|
|
|
522 buffer. But, hey, that's your problem. Blllrph!
|
|
|
523
|
|
|
524 @findex gnus-no-server
|
|
16
|
525 @kindex M-x gnus-no-server
|
|
0
|
526 @c @head
|
|
|
527 If you know that the server is definitely down, or you just want to read
|
|
|
528 your mail without bothering with the server at all, you can use the
|
|
|
529 @code{gnus-no-server} command to start Gnus. That might come in handy
|
|
16
|
530 if you're in a hurry as well. This command will not attempt to contact
|
|
|
531 your primary server---instead, it will just activate all groups on level
|
|
|
532 1 and 2. (You should preferably keep no native groups on those two
|
|
|
533 levels.)
|
|
|
534
|
|
|
535
|
|
|
536 @node Slave Gnusae
|
|
|
537 @section Slave Gnusae
|
|
0
|
538 @cindex slave
|
|
|
539
|
|
|
540 You might want to run more than one Emacs with more than one Gnus at the
|
|
16
|
541 same time. If you are using different @file{.newsrc} files (e.g., if you
|
|
|
542 are using the two different Gnusae to read from two different servers),
|
|
0
|
543 that is no problem whatsoever. You just do it.
|
|
|
544
|
|
16
|
545 The problem appears when you want to run two Gnusae that use the same
|
|
0
|
546 @code{.newsrc} file.
|
|
|
547
|
|
|
548 To work around that problem some, we here at the Think-Tank at the Gnus
|
|
|
549 Towers have come up with a new concept: @dfn{Masters} and
|
|
16
|
550 @dfn{slaves}. (We have applied for a patent on this concept, and have
|
|
0
|
551 taken out a copyright on those words. If you wish to use those words in
|
|
|
552 conjunction with each other, you have to send $1 per usage instance to
|
|
|
553 me. Usage of the patent (@dfn{Master/Slave Relationships In Computer
|
|
|
554 Applications}) will be much more expensive, of course.)
|
|
|
555
|
|
|
556 Anyways, you start one Gnus up the normal way with @kbd{M-x gnus} (or
|
|
16
|
557 however you do it). Each subsequent slave Gnusae should be started with
|
|
0
|
558 @kbd{M-x gnus-slave}. These slaves won't save normal @file{.newsrc}
|
|
16
|
559 files, but instead save @dfn{slave files} that contain information only
|
|
0
|
560 on what groups have been read in the slave session. When a master Gnus
|
|
|
561 starts, it will read (and delete) these slave files, incorporating all
|
|
|
562 information from them. (The slave files will be read in the sequence
|
|
|
563 they were created, so the latest changes will have precedence.)
|
|
|
564
|
|
|
565 Information from the slave files has, of course, precedence over the
|
|
16
|
566 information in the normal (i.e., master) @code{.newsrc} file.
|
|
0
|
567
|
|
|
568
|
|
|
569 @node Fetching a Group
|
|
|
570 @section Fetching a Group
|
|
16
|
571 @cindex fetching a group
|
|
0
|
572
|
|
|
573 @findex gnus-fetch-group
|
|
16
|
574 It it sometimes convenient to be able to just say ``I want to read this
|
|
0
|
575 group and I don't care whether Gnus has been started or not''. This is
|
|
|
576 perhaps more useful for people who write code than for users, but the
|
|
|
577 command @code{gnus-fetch-group} provides this functionality in any case.
|
|
|
578 It takes the group name as a parameter.
|
|
|
579
|
|
|
580
|
|
|
581 @node New Groups
|
|
|
582 @section New Groups
|
|
|
583 @cindex new groups
|
|
16
|
584 @cindex subscription
|
|
|
585
|
|
|
586 @vindex gnus-check-new-newsgroups
|
|
|
587 If you are satisfied that you really never want to see any new groups,
|
|
|
588 you can set @code{gnus-check-new-newsgroups} to @code{nil}. This will
|
|
|
589 also save you some time at startup. Even if this variable is
|
|
|
590 @code{nil}, you can always subscribe to the new groups just by pressing
|
|
|
591 @kbd{U} in the group buffer (@pxref{Group Maintenance}). This variable
|
|
|
592 is @code{t} by default. If you set this variable to @code{always}, then
|
|
|
593 Gnus will query the backends for new groups even when you do the @kbd{g}
|
|
|
594 command (@pxref{Scanning New Messages}).
|
|
|
595
|
|
|
596 @menu
|
|
|
597 * Checking New Groups:: Determining what groups are new.
|
|
|
598 * Subscription Methods:: What Gnus should do with new groups.
|
|
|
599 * Filtering New Groups:: Making Gnus ignore certain new groups.
|
|
|
600 @end menu
|
|
|
601
|
|
|
602
|
|
|
603 @node Checking New Groups
|
|
|
604 @subsection Checking New Groups
|
|
|
605
|
|
|
606 Gnus normally determines whether a group is new or not by comparing the
|
|
|
607 list of groups from the active file(s) with the lists of subscribed and
|
|
|
608 dead groups. This isn't a particularly fast method. If
|
|
|
609 @code{gnus-check-new-newsgroups} is @code{ask-server}, Gnus will ask the
|
|
|
610 server for new groups since the last time. This is both faster and
|
|
|
611 cheaper. This also means that you can get rid of the list of killed
|
|
|
612 groups altogether, so you may set @code{gnus-save-killed-list} to
|
|
|
613 @code{nil}, which will save time both at startup, at exit, and all over.
|
|
|
614 Saves disk space, too. Why isn't this the default, then?
|
|
|
615 Unfortunately, not all servers support this command.
|
|
|
616
|
|
|
617 I bet I know what you're thinking now: How do I find out whether my
|
|
|
618 server supports @code{ask-server}? No? Good, because I don't have a
|
|
|
619 fail-safe answer. I would suggest just setting this variable to
|
|
|
620 @code{ask-server} and see whether any new groups appear within the next
|
|
|
621 few days. If any do, then it works. If none do, then it doesn't
|
|
|
622 work. I could write a function to make Gnus guess whether the server
|
|
|
623 supports @code{ask-server}, but it would just be a guess. So I won't.
|
|
|
624 You could @code{telnet} to the server and say @code{HELP} and see
|
|
|
625 whether it lists @samp{NEWGROUPS} among the commands it understands. If
|
|
|
626 it does, then it might work. (But there are servers that lists
|
|
|
627 @samp{NEWGROUPS} without supporting the function properly.)
|
|
|
628
|
|
|
629 This variable can also be a list of select methods. If so, Gnus will
|
|
|
630 issue an @code{ask-server} command to each of the select methods, and
|
|
|
631 subscribe them (or not) using the normal methods. This might be handy
|
|
|
632 if you are monitoring a few servers for new groups. A side effect is
|
|
|
633 that startup will take much longer, so you can meditate while waiting.
|
|
|
634 Use the mantra ``dingnusdingnusdingnus'' to achieve permanent bliss.
|
|
|
635
|
|
|
636
|
|
|
637 @node Subscription Methods
|
|
|
638 @subsection Subscription Methods
|
|
0
|
639
|
|
|
640 @vindex gnus-subscribe-newsgroup-method
|
|
|
641 What Gnus does when it encounters a new group is determined by the
|
|
|
642 @code{gnus-subscribe-newsgroup-method} variable.
|
|
|
643
|
|
|
644 This variable should contain a function. Some handy pre-fab values
|
|
|
645 are:
|
|
|
646
|
|
|
647 @table @code
|
|
|
648
|
|
|
649 @item gnus-subscribe-zombies
|
|
|
650 @vindex gnus-subscribe-zombies
|
|
16
|
651 Make all new groups zombies. This is the default. You can browse the
|
|
|
652 zombies later (with @kbd{A z}) and either kill them all off properly
|
|
|
653 (with @kbd{S z}), or subscribe to them (with @kbd{u}).
|
|
0
|
654
|
|
|
655 @item gnus-subscribe-randomly
|
|
|
656 @vindex gnus-subscribe-randomly
|
|
|
657 Subscribe all new groups randomly.
|
|
|
658
|
|
|
659 @item gnus-subscribe-alphabetically
|
|
|
660 @vindex gnus-subscribe-alphabetically
|
|
|
661 Subscribe all new groups alphabetically.
|
|
|
662
|
|
16
|
663 @item gnus-subscribe-hierarchically
|
|
|
664 @vindex gnus-subscribe-hierarchically
|
|
2
|
665 Subscribe all new groups hierarchically. The difference between this
|
|
|
666 function and @code{gnus-subscribe-alphabetically} is slight.
|
|
16
|
667 @code{gnus-subscribe-alphabetically} will subscribe new groups in a strictly
|
|
|
668 alphabetical fashion, while this function will enter groups into it's
|
|
|
669 hierarchy. So if you want to have the @samp{rec} hierarchy before the
|
|
|
670 @samp{comp} hierarchy, this function will not mess that configuration
|
|
|
671 up. Or something like that.
|
|
0
|
672
|
|
|
673 @item gnus-subscribe-interactively
|
|
|
674 @vindex gnus-subscribe-interactively
|
|
|
675 Subscribe new groups interactively. This means that Gnus will ask
|
|
|
676 you about @strong{all} new groups.
|
|
|
677
|
|
|
678 @item gnus-subscribe-killed
|
|
|
679 @vindex gnus-subscribe-killed
|
|
|
680 Kill all new groups.
|
|
|
681
|
|
|
682 @end table
|
|
|
683
|
|
|
684 @vindex gnus-subscribe-hierarchical-interactive
|
|
|
685 A closely related variable is
|
|
|
686 @code{gnus-subscribe-hierarchical-interactive}. (That's quite a
|
|
|
687 mouthful.) If this variable is non-@code{nil}, Gnus will ask you in a
|
|
|
688 hierarchical fashion whether to subscribe to new groups or not. Gnus
|
|
|
689 will ask you for each sub-hierarchy whether you want to descend the
|
|
|
690 hierarchy or not.
|
|
|
691
|
|
|
692 One common mistake is to set the variable a few paragraphs above to
|
|
|
693 @code{gnus-subscribe-hierarchical-interactive}. This is an error. This
|
|
|
694 will not work. This is ga-ga. So don't do it.
|
|
|
695
|
|
16
|
696
|
|
|
697 @node Filtering New Groups
|
|
|
698 @subsection Filtering New Groups
|
|
|
699
|
|
0
|
700 A nice and portable way to control which new newsgroups should be
|
|
|
701 subscribed (or ignored) is to put an @dfn{options} line at the start of
|
|
|
702 the @file{.newsrc} file. Here's an example:
|
|
|
703
|
|
|
704 @example
|
|
|
705 options -n !alt.all !rec.all sci.all
|
|
|
706 @end example
|
|
|
707
|
|
|
708 @vindex gnus-subscribe-options-newsgroup-method
|
|
|
709 This line obviously belongs to a serious-minded intellectual scientific
|
|
|
710 person (or she may just be plain old boring), because it says that all
|
|
|
711 groups that have names beginning with @samp{alt} and @samp{rec} should
|
|
|
712 be ignored, and all groups with names beginning with @samp{sci} should
|
|
|
713 be subscribed. Gnus will not use the normal subscription method for
|
|
|
714 subscribing these groups.
|
|
|
715 @code{gnus-subscribe-options-newsgroup-method} is used instead. This
|
|
|
716 variable defaults to @code{gnus-subscribe-alphabetically}.
|
|
|
717
|
|
|
718 @vindex gnus-options-not-subscribe
|
|
|
719 @vindex gnus-options-subscribe
|
|
|
720 If you don't want to mess with your @file{.newsrc} file, you can just
|
|
|
721 set the two variables @code{gnus-options-subscribe} and
|
|
|
722 @code{gnus-options-not-subscribe}. These two variables do exactly the
|
|
|
723 same as the @file{.newsrc} @samp{options -n} trick. Both are regexps,
|
|
|
724 and if the the new group matches the former, it will be unconditionally
|
|
|
725 subscribed, and if it matches the latter, it will be ignored.
|
|
|
726
|
|
|
727 @vindex gnus-auto-subscribed-groups
|
|
|
728 Yet another variable that meddles here is
|
|
|
729 @code{gnus-auto-subscribed-groups}. It works exactly like
|
|
|
730 @code{gnus-options-subscribe}, and is therefore really superfluous, but I
|
|
|
731 thought it would be nice to have two of these. This variable is more
|
|
|
732 meant for setting some ground rules, while the other variable is used
|
|
|
733 more for user fiddling. By default this variable makes all new groups
|
|
|
734 that come from mail backends (@code{nnml}, @code{nnbabyl},
|
|
|
735 @code{nnfolder}, @code{nnmbox}, and @code{nnmh}) subscribed. If you
|
|
|
736 don't like that, just set this variable to @code{nil}.
|
|
|
737
|
|
16
|
738 New groups that match this regexp are subscribed using
|
|
|
739 @code{gnus-subscribe-options-newsgroup-method}.
|
|
|
740
|
|
|
741
|
|
|
742 @node Changing Servers
|
|
|
743 @section Changing Servers
|
|
|
744 @cindex changing servers
|
|
|
745
|
|
|
746 Sometimes it is necessary to move from one @sc{nntp} server to another.
|
|
|
747 This happens very rarely, but perhaps you change jobs, or one server is
|
|
|
748 very flaky and you want to use another.
|
|
|
749
|
|
|
750 Changing the server is pretty easy, right? You just change
|
|
|
751 @code{gnus-select-method} to point to the new server?
|
|
|
752
|
|
|
753 @emph{Wrong!}
|
|
|
754
|
|
|
755 Article numbers are not (in any way) kept synchronized between different
|
|
|
756 @sc{nntp} servers, and the only way Gnus keeps track of what articles
|
|
|
757 you have read is by keeping track of article numbers. So when you
|
|
|
758 change @code{gnus-select-method}, your @file{.newsrc} file becomes
|
|
|
759 worthless.
|
|
|
760
|
|
|
761 Gnus provides a few functions to attempt to translate a @file{.newsrc}
|
|
|
762 file from one server to another. They all have one thing in
|
|
|
763 common---they take a looong time to run. You don't want to use these
|
|
|
764 functions more than absolutely necessary.
|
|
|
765
|
|
|
766 @kindex M-x gnus-change-server
|
|
|
767 @findex gnus-change-server
|
|
|
768 If you have access to both servers, Gnus can request the headers for all
|
|
|
769 the articles you have read and compare @code{Message-ID}s and map the
|
|
|
770 article numbers of the read articles and article marks. The @kbd{M-x
|
|
|
771 gnus-change-server} command will do this for all your native groups. It
|
|
|
772 will prompt for the method you want to move to.
|
|
|
773
|
|
|
774 @kindex M-x gnus-group-move-group-to-server
|
|
|
775 @findex gnus-group-move-group-to-server
|
|
|
776 You can also move individual groups with the @kbd{M-x
|
|
|
777 gnus-group-move-group-to-server} command. This is useful if you want to
|
|
|
778 move a (foreign) group from one server to another.
|
|
|
779
|
|
|
780 @kindex M-x gnus-group-clear-data-on-native-groups
|
|
|
781 @findex gnus-group-clear-data-on-native-groups
|
|
|
782 If you don't have access to both the old and new server, all your marks
|
|
|
783 and read ranges have become worthless. You can use the @kbd{M-x
|
|
|
784 gnus-group-clear-data-on-native-groups} command to clear out all data
|
|
|
785 that you have on your native groups. Use with caution.
|
|
0
|
786
|
|
|
787
|
|
|
788 @node Startup Files
|
|
|
789 @section Startup Files
|
|
|
790 @cindex startup files
|
|
|
791 @cindex .newsrc
|
|
16
|
792 @cindex .newsrc.el
|
|
|
793 @cindex .newsrc.eld
|
|
0
|
794
|
|
|
795 Now, you all know about the @file{.newsrc} file. All subscription
|
|
|
796 information is traditionally stored in this file.
|
|
|
797
|
|
|
798 Things got a bit more complicated with @sc{gnus}. In addition to
|
|
|
799 keeping the @file{.newsrc} file updated, it also used a file called
|
|
|
800 @file{.newsrc.el} for storing all the information that didn't fit into
|
|
|
801 the @file{.newsrc} file. (Actually, it also duplicated everything in
|
|
|
802 the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
|
|
|
803 files was the most recently saved, which enabled people to swap between
|
|
|
804 @sc{gnus} and other newsreaders.
|
|
|
805
|
|
|
806 That was kinda silly, so Gnus went one better: In addition to the
|
|
|
807 @file{.newsrc} and @file{.newsrc.el} files, Gnus also has a file called
|
|
|
808 @file{.newsrc.eld}. It will read whichever of these files that are most
|
|
|
809 recent, but it will never write a @file{.newsrc.el} file.
|
|
|
810
|
|
|
811 @vindex gnus-save-newsrc-file
|
|
|
812 You can turn off writing the @file{.newsrc} file by setting
|
|
|
813 @code{gnus-save-newsrc-file} to @code{nil}, which means you can delete
|
|
|
814 the file and save some space, as well as making exit from Gnus faster.
|
|
|
815 However, this will make it impossible to use other newsreaders than
|
|
|
816 Gnus. But hey, who would want to, right?
|
|
|
817
|
|
|
818 @vindex gnus-save-killed-list
|
|
|
819 If @code{gnus-save-killed-list} (default @code{t}) is @code{nil}, Gnus
|
|
|
820 will not save the list of killed groups to the startup file. This will
|
|
|
821 save both time (when starting and quitting) and space (on disk). It
|
|
16
|
822 will also mean that Gnus has no record of what groups are new or old,
|
|
0
|
823 so the automatic new groups subscription methods become meaningless.
|
|
|
824 You should always set @code{gnus-check-new-newsgroups} to @code{nil} or
|
|
|
825 @code{ask-server} if you set this variable to @code{nil} (@pxref{New
|
|
16
|
826 Groups}). This variable can also be a regular expression. If that's
|
|
|
827 the case, remove all groups that do not match this regexp before
|
|
|
828 saving. This can be useful in certain obscure situations that involve
|
|
|
829 several servers where not all servers support @code{ask-server}.
|
|
0
|
830
|
|
|
831 @vindex gnus-startup-file
|
|
|
832 The @code{gnus-startup-file} variable says where the startup files are.
|
|
|
833 The default value is @file{~/.newsrc}, with the Gnus (El Dingo) startup
|
|
|
834 file being whatever that one is with a @samp{.eld} appended.
|
|
|
835
|
|
|
836 @vindex gnus-save-newsrc-hook
|
|
|
837 @vindex gnus-save-quick-newsrc-hook
|
|
|
838 @vindex gnus-save-standard-newsrc-hook
|
|
|
839 @code{gnus-save-newsrc-hook} is called before saving any of the newsrc
|
|
|
840 files, while @code{gnus-save-quick-newsrc-hook} is called just before
|
|
|
841 saving the @file{.newsrc.eld} file, and
|
|
|
842 @code{gnus-save-standard-newsrc-hook} is called just before saving the
|
|
|
843 @file{.newsrc} file. The latter two are commonly used to turn version
|
|
16
|
844 control on or off. Version control is on by default when saving the
|
|
|
845 startup files. If you want to turn backup creation off, say something like:
|
|
|
846
|
|
|
847 @lisp
|
|
|
848 (defun turn-off-backup ()
|
|
|
849 (set (make-local-variable 'backup-inhibited) t))
|
|
|
850
|
|
|
851 (add-hook 'gnus-save-quick-newsrc-hook 'turn-off-backup)
|
|
|
852 (add-hook 'gnus-save-standard-newsrc-hook 'turn-off-backup)
|
|
|
853 @end lisp
|
|
0
|
854
|
|
2
|
855 @vindex gnus-init-file
|
|
16
|
856 When Gnus starts, it will read the @code{gnus-site-init-file}
|
|
28
|
857 (@file{.../site-lisp/gnus} by default) and @code{gnus-init-file}
|
|
|
858 (@file{~/.gnus} by default) files. These are normal Emacs Lisp files
|
|
|
859 and can be used to avoid cluttering your @file{~/.emacs} and
|
|
|
860 @file{site-init} files with Gnus stuff. Gnus will also check for files
|
|
|
861 with the same names as these, but with @file{.elc} and @file{.el}
|
|
|
862 suffixes. In other words, if you have set @code{gnus-init-file} to
|
|
|
863 @file{~/.gnus}, it will look for @file{~/.gnus.elc}, @file{~/.gnus.el},
|
|
|
864 and finally @file{~/.gnus} (in this order).
|
|
|
865
|
|
2
|
866
|
|
0
|
867
|
|
|
868 @node Auto Save
|
|
|
869 @section Auto Save
|
|
|
870 @cindex dribble file
|
|
|
871 @cindex auto-save
|
|
|
872
|
|
|
873 Whenever you do something that changes the Gnus data (reading articles,
|
|
|
874 catching up, killing/subscribing groups), the change is added to a
|
|
|
875 special @dfn{dribble buffer}. This buffer is auto-saved the normal
|
|
|
876 Emacs way. If your Emacs should crash before you have saved the
|
|
|
877 @file{.newsrc} files, all changes you have made can be recovered from
|
|
|
878 this file.
|
|
|
879
|
|
|
880 If Gnus detects this file at startup, it will ask the user whether to
|
|
|
881 read it. The auto save file is deleted whenever the real startup file is
|
|
|
882 saved.
|
|
|
883
|
|
|
884 @vindex gnus-use-dribble-file
|
|
|
885 If @code{gnus-use-dribble-file} is @code{nil}, Gnus won't create and
|
|
|
886 maintain a dribble buffer. The default is @code{t}.
|
|
|
887
|
|
|
888 @vindex gnus-dribble-directory
|
|
|
889 Gnus will put the dribble file(s) in @code{gnus-dribble-directory}. If
|
|
|
890 this variable is @code{nil}, which it is by default, Gnus will dribble
|
|
|
891 into the directory where the @file{.newsrc} file is located. (This is
|
|
|
892 normally the user's home directory.) The dribble file will get the same
|
|
|
893 file permissions as the @code{.newsrc} file.
|
|
|
894
|
|
|
895
|
|
|
896 @node The Active File
|
|
|
897 @section The Active File
|
|
|
898 @cindex active file
|
|
|
899 @cindex ignored groups
|
|
|
900
|
|
|
901 When Gnus starts, or indeed whenever it tries to determine whether new
|
|
|
902 articles have arrived, it reads the active file. This is a very large
|
|
|
903 file that lists all the active groups and articles on the server.
|
|
|
904
|
|
|
905 @vindex gnus-ignored-newsgroups
|
|
|
906 Before examining the active file, Gnus deletes all lines that match the
|
|
|
907 regexp @code{gnus-ignored-newsgroups}. This is done primarily to reject
|
|
|
908 any groups with bogus names, but you can use this variable to make Gnus
|
|
|
909 ignore hierarchies you aren't ever interested in. However, this is not
|
|
|
910 recommended. In fact, it's highly discouraged. Instead, @pxref{New
|
|
|
911 Groups} for an overview of other variables that can be used instead.
|
|
|
912
|
|
|
913 @c This variable is
|
|
|
914 @c @code{nil} by default, and will slow down active file handling somewhat
|
|
|
915 @c if you set it to anything else.
|
|
|
916
|
|
|
917 @vindex gnus-read-active-file
|
|
|
918 @c @head
|
|
|
919 The active file can be rather Huge, so if you have a slow network, you
|
|
|
920 can set @code{gnus-read-active-file} to @code{nil} to prevent Gnus from
|
|
|
921 reading the active file. This variable is @code{t} by default.
|
|
|
922
|
|
|
923 Gnus will try to make do by getting information just on the groups that
|
|
|
924 you actually subscribe to.
|
|
|
925
|
|
|
926 Note that if you subscribe to lots and lots of groups, setting this
|
|
|
927 variable to @code{nil} will probably make Gnus slower, not faster. At
|
|
|
928 present, having this variable @code{nil} will slow Gnus down
|
|
|
929 considerably, unless you read news over a 2400 baud modem.
|
|
|
930
|
|
|
931 This variable can also have the value @code{some}. Gnus will then
|
|
|
932 attempt to read active info only on the subscribed groups. On some
|
|
|
933 servers this is quite fast (on sparkling, brand new INN servers that
|
|
|
934 support the @code{LIST ACTIVE group} command), on others this isn't fast
|
|
|
935 at all. In any case, @code{some} should be faster than @code{nil}, and
|
|
|
936 is certainly faster than @code{t} over slow lines.
|
|
|
937
|
|
|
938 If this variable is @code{nil}, Gnus will ask for group info in total
|
|
|
939 lock-step, which isn't very fast. If it is @code{some} and you use an
|
|
|
940 @sc{nntp} server, Gnus will pump out commands as fast as it can, and
|
|
|
941 read all the replies in one swoop. This will normally result in better
|
|
|
942 performance, but if the server does not support the aforementioned
|
|
|
943 @code{LIST ACTIVE group} command, this isn't very nice to the server.
|
|
|
944
|
|
|
945 In any case, if you use @code{some} or @code{nil}, you should definitely
|
|
|
946 kill all groups that you aren't interested in to speed things up.
|
|
|
947
|
|
16
|
948 Note that this variable also affects active file retrieval from
|
|
|
949 secondary select methods.
|
|
|
950
|
|
0
|
951
|
|
|
952 @node Startup Variables
|
|
|
953 @section Startup Variables
|
|
|
954
|
|
|
955 @table @code
|
|
|
956
|
|
|
957 @item gnus-load-hook
|
|
|
958 @vindex gnus-load-hook
|
|
|
959 A hook that is run while Gnus is being loaded. Note that this hook will
|
|
|
960 normally be run just once in each Emacs session, no matter how many
|
|
|
961 times you start Gnus.
|
|
|
962
|
|
|
963 @item gnus-startup-hook
|
|
|
964 @vindex gnus-startup-hook
|
|
|
965 A hook that is run after starting up Gnus successfully.
|
|
|
966
|
|
26
|
967 @item gnus-started-hook
|
|
|
968 @vindex gnus-started-hook
|
|
|
969 A hook that is run as the very last thing after starting up Gnus
|
|
|
970 successfully.
|
|
|
971
|
|
0
|
972 @item gnus-check-bogus-newsgroups
|
|
|
973 @vindex gnus-check-bogus-newsgroups
|
|
|
974 If non-@code{nil}, Gnus will check for and delete all bogus groups at
|
|
|
975 startup. A @dfn{bogus group} is a group that you have in your
|
|
|
976 @file{.newsrc} file, but doesn't exist on the news server. Checking for
|
|
|
977 bogus groups can take quite a while, so to save time and resources it's
|
|
|
978 best to leave this option off, and do the checking for bogus groups once
|
|
|
979 in a while from the group buffer instead (@pxref{Group Maintenance}).
|
|
|
980
|
|
|
981 @item gnus-inhibit-startup-message
|
|
|
982 @vindex gnus-inhibit-startup-message
|
|
|
983 If non-@code{nil}, the startup message won't be displayed. That way,
|
|
16
|
984 your boss might not notice as easily that you are reading news instead
|
|
|
985 of doing your job. Note that this variable is used before
|
|
|
986 @file{.gnus.el} is loaded, so it should be set in @code{.emacs} instead.
|
|
0
|
987
|
|
|
988 @item gnus-no-groups-message
|
|
|
989 @vindex gnus-no-groups-message
|
|
|
990 Message displayed by Gnus when no groups are available.
|
|
16
|
991
|
|
|
992 @item gnus-play-startup-jingle
|
|
|
993 @vindex gnus-play-startup-jingle
|
|
|
994 If non-@code{nil}, play the Gnus jingle at startup.
|
|
|
995
|
|
|
996 @item gnus-startup-jingle
|
|
|
997 @vindex gnus-startup-jingle
|
|
|
998 Jingle to be played if the above variable is non-@code{nil}. The
|
|
|
999 default is @samp{Tuxedomoon.Jingle4.au}.
|
|
|
1000
|
|
0
|
1001 @end table
|
|
|
1002
|
|
|
1003
|
|
|
1004 @node The Group Buffer
|
|
|
1005 @chapter The Group Buffer
|
|
|
1006 @cindex group buffer
|
|
|
1007
|
|
|
1008 The @dfn{group buffer} lists all (or parts) of the available groups. It
|
|
|
1009 is the first buffer shown when Gnus starts, and will never be killed as
|
|
|
1010 long as Gnus is active.
|
|
|
1011
|
|
|
1012 @menu
|
|
|
1013 * Group Buffer Format:: Information listed and how you can change it.
|
|
|
1014 * Group Maneuvering:: Commands for moving in the group buffer.
|
|
|
1015 * Selecting a Group:: Actually reading news.
|
|
16
|
1016 * Group Data:: Changing the info for a group.
|
|
0
|
1017 * Subscription Commands:: Unsubscribing, killing, subscribing.
|
|
|
1018 * Group Levels:: Levels? What are those, then?
|
|
|
1019 * Group Score:: A mechanism for finding out what groups you like.
|
|
|
1020 * Marking Groups:: You can mark groups for later processing.
|
|
|
1021 * Foreign Groups:: Creating and editing groups.
|
|
|
1022 * Group Parameters:: Each group may have different parameters set.
|
|
|
1023 * Listing Groups:: Gnus can list various subsets of the groups.
|
|
|
1024 * Sorting Groups:: Re-arrange the group order.
|
|
|
1025 * Group Maintenance:: Maintaining a tidy @file{.newsrc} file.
|
|
|
1026 * Browse Foreign Server:: You can browse a server. See what it has to offer.
|
|
|
1027 * Exiting Gnus:: Stop reading news and get some work done.
|
|
|
1028 * Group Topics:: A folding group mode divided into topics.
|
|
|
1029 * Misc Group Stuff:: Other stuff that you can to do.
|
|
|
1030 @end menu
|
|
|
1031
|
|
|
1032
|
|
|
1033 @node Group Buffer Format
|
|
|
1034 @section Group Buffer Format
|
|
|
1035
|
|
|
1036 @menu
|
|
|
1037 * Group Line Specification:: Deciding how the group buffer is to look.
|
|
|
1038 * Group Modeline Specification:: The group buffer modeline.
|
|
|
1039 * Group Highlighting:: Having nice colors in the group buffer.
|
|
|
1040 @end menu
|
|
|
1041
|
|
|
1042
|
|
|
1043 @node Group Line Specification
|
|
|
1044 @subsection Group Line Specification
|
|
16
|
1045 @cindex group buffer format
|
|
0
|
1046
|
|
|
1047 The default format of the group buffer is nice and dull, but you can
|
|
|
1048 make it as exciting and ugly as you feel like.
|
|
|
1049
|
|
|
1050 Here's a couple of example group lines:
|
|
|
1051
|
|
|
1052 @example
|
|
|
1053 25: news.announce.newusers
|
|
|
1054 * 0: alt.fan.andrea-dworkin
|
|
|
1055 @end example
|
|
|
1056
|
|
|
1057 Quite simple, huh?
|
|
|
1058
|
|
|
1059 You can see that there are 25 unread articles in
|
|
|
1060 @samp{news.announce.newusers}. There are no unread articles, but some
|
|
|
1061 ticked articles, in @samp{alt.fan.andrea-dworkin} (see that little
|
|
|
1062 asterisk at the beginning of the line?)
|
|
|
1063
|
|
|
1064 @vindex gnus-group-line-format
|
|
|
1065 You can change that format to whatever you want by fiddling with the
|
|
|
1066 @code{gnus-group-line-format} variable. This variable works along the
|
|
|
1067 lines of a @code{format} specification, which is pretty much the same as
|
|
|
1068 a @code{printf} specifications, for those of you who use (feh!) C.
|
|
|
1069 @xref{Formatting Variables}.
|
|
|
1070
|
|
16
|
1071 @samp{%M%S%5y: %(%g%)\n} is the value that produced those lines above.
|
|
0
|
1072
|
|
|
1073 There should always be a colon on the line; the cursor always moves to
|
|
|
1074 the colon after performing an operation. Nothing else is required---not
|
|
|
1075 even the group name. All displayed text is just window dressing, and is
|
|
|
1076 never examined by Gnus. Gnus stores all real information it needs using
|
|
|
1077 text properties.
|
|
|
1078
|
|
|
1079 (Note that if you make a really strange, wonderful, spreadsheet-like
|
|
|
1080 layout, everybody will believe you are hard at work with the accounting
|
|
|
1081 instead of wasting time reading news.)
|
|
|
1082
|
|
|
1083 Here's a list of all available format characters:
|
|
|
1084
|
|
|
1085 @table @samp
|
|
|
1086
|
|
|
1087 @item M
|
|
16
|
1088 An asterisk if the group only has marked articles.
|
|
0
|
1089
|
|
|
1090 @item S
|
|
|
1091 Whether the group is subscribed.
|
|
|
1092
|
|
|
1093 @item L
|
|
|
1094 Level of subscribedness.
|
|
|
1095
|
|
|
1096 @item N
|
|
|
1097 Number of unread articles.
|
|
|
1098
|
|
|
1099 @item I
|
|
|
1100 Number of dormant articles.
|
|
|
1101
|
|
|
1102 @item T
|
|
|
1103 Number of ticked articles.
|
|
|
1104
|
|
|
1105 @item R
|
|
|
1106 Number of read articles.
|
|
|
1107
|
|
|
1108 @item t
|
|
16
|
1109 Estimated total number of articles. (This is really @var{max-number}
|
|
|
1110 minus @var{min-number} plus 1.)
|
|
0
|
1111
|
|
|
1112 @item y
|
|
|
1113 Number of unread, unticked, non-dormant articles.
|
|
|
1114
|
|
|
1115 @item i
|
|
|
1116 Number of ticked and dormant articles.
|
|
|
1117
|
|
|
1118 @item g
|
|
|
1119 Full group name.
|
|
|
1120
|
|
|
1121 @item G
|
|
|
1122 Group name.
|
|
|
1123
|
|
|
1124 @item D
|
|
|
1125 Newsgroup description.
|
|
|
1126
|
|
|
1127 @item o
|
|
|
1128 @samp{m} if moderated.
|
|
|
1129
|
|
|
1130 @item O
|
|
|
1131 @samp{(m)} if moderated.
|
|
|
1132
|
|
|
1133 @item s
|
|
|
1134 Select method.
|
|
|
1135
|
|
|
1136 @item n
|
|
|
1137 Select from where.
|
|
|
1138
|
|
|
1139 @item z
|
|
|
1140 A string that looks like @samp{<%s:%n>} if a foreign select method is
|
|
|
1141 used.
|
|
|
1142
|
|
|
1143 @item P
|
|
|
1144 Indentation based on the level of the topic (@pxref{Group Topics}).
|
|
|
1145
|
|
|
1146 @item c
|
|
|
1147 @vindex gnus-group-uncollapsed-levels
|
|
|
1148 Short (collapsed) group name. The @code{gnus-group-uncollapsed-levels}
|
|
|
1149 variable says how many levels to leave at the end of the group name.
|
|
16
|
1150 The default is 1---this will mean that group names like
|
|
|
1151 @samp{gnu.emacs.gnus} will be shortened to @samp{g.emacs.gnus}.
|
|
|
1152
|
|
|
1153 @item m
|
|
|
1154 @vindex gnus-new-mail-mark
|
|
|
1155 @cindex %
|
|
|
1156 @samp{%} (@code{gnus-new-mail-mark}) if there has arrived new mail to
|
|
|
1157 the group lately.
|
|
|
1158
|
|
|
1159 @item d
|
|
|
1160 A string that says when you last read the group (@pxref{Group
|
|
|
1161 Timestamp}).
|
|
0
|
1162
|
|
|
1163 @item u
|
|
|
1164 User defined specifier. The next character in the format string should
|
|
|
1165 be a letter. @sc{gnus} will call the function
|
|
|
1166 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
|
|
16
|
1167 following @samp{%u}. The function will be passed a single dummy
|
|
30
|
1168 parameter as argument. The function should return a string, which will
|
|
16
|
1169 be inserted into the buffer just like information from any other
|
|
|
1170 specifier.
|
|
0
|
1171 @end table
|
|
|
1172
|
|
|
1173 @cindex *
|
|
|
1174 All the ``number-of'' specs will be filled with an asterisk (@samp{*})
|
|
|
1175 if no info is available---for instance, if it is a non-activated foreign
|
|
16
|
1176 group, or a bogus native group.
|
|
0
|
1177
|
|
|
1178
|
|
|
1179 @node Group Modeline Specification
|
|
|
1180 @subsection Group Modeline Specification
|
|
16
|
1181 @cindex group modeline
|
|
0
|
1182
|
|
|
1183 @vindex gnus-group-mode-line-format
|
|
|
1184 The mode line can be changed by setting
|
|
16
|
1185 @code{gnus-group-mode-line-format} (@pxref{Formatting Variables}). It
|
|
|
1186 doesn't understand that many format specifiers:
|
|
0
|
1187
|
|
|
1188 @table @samp
|
|
|
1189 @item S
|
|
|
1190 The native news server.
|
|
|
1191 @item M
|
|
|
1192 The native select method.
|
|
|
1193 @end table
|
|
|
1194
|
|
|
1195
|
|
|
1196 @node Group Highlighting
|
|
|
1197 @subsection Group Highlighting
|
|
16
|
1198 @cindex highlighting
|
|
|
1199 @cindex group highlighting
|
|
0
|
1200
|
|
|
1201 @vindex gnus-group-highlight
|
|
|
1202 Highlighting in the group buffer is controlled by the
|
|
|
1203 @code{gnus-group-highlight} variable. This is an alist with elements
|
|
|
1204 that look like @var{(form . face)}. If @var{form} evaluates to
|
|
|
1205 something non-@code{nil}, the @var{face} will be used on the line.
|
|
|
1206
|
|
|
1207 Here's an example value for this variable that might look nice if the
|
|
|
1208 background is dark:
|
|
|
1209
|
|
|
1210 @lisp
|
|
|
1211 (setq gnus-group-highlight
|
|
16
|
1212 `(((> unread 200) .
|
|
|
1213 ,(custom-face-lookup "Red" nil nil t nil nil))
|
|
|
1214 ((and (< level 3) (zerop unread)) .
|
|
|
1215 ,(custom-face-lookup "SeaGreen" nil nil t nil nil))
|
|
|
1216 ((< level 3) .
|
|
|
1217 ,(custom-face-lookup "SpringGreen" nil nil t nil nil))
|
|
|
1218 ((zerop unread) .
|
|
|
1219 ,(custom-face-lookup "SteelBlue" nil nil t nil nil))
|
|
|
1220 (t .
|
|
|
1221 ,(custom-face-lookup "SkyBlue" nil nil t nil nil))))
|
|
0
|
1222 @end lisp
|
|
|
1223
|
|
|
1224 Variables that are dynamically bound when the forms are evaluated
|
|
|
1225 include:
|
|
|
1226
|
|
|
1227 @table @code
|
|
|
1228 @item group
|
|
|
1229 The group name.
|
|
|
1230 @item unread
|
|
|
1231 The number of unread articles in the group.
|
|
|
1232 @item method
|
|
|
1233 The select method.
|
|
|
1234 @item mailp
|
|
|
1235 Whether the group is a mail group.
|
|
|
1236 @item level
|
|
|
1237 The level of the group.
|
|
|
1238 @item score
|
|
|
1239 The score of the group.
|
|
|
1240 @item ticked
|
|
|
1241 The number of ticked articles in the group.
|
|
16
|
1242 @item total
|
|
|
1243 The total number of articles in the group. Or rather, MAX-NUMBER minus
|
|
|
1244 MIN-NUMBER.
|
|
0
|
1245 @item topic
|
|
|
1246 When using the topic minor mode, this variable is bound to the current
|
|
|
1247 topic being inserted.
|
|
|
1248 @end table
|
|
|
1249
|
|
|
1250 When the forms are @code{eval}ed, point is at the beginning of the line
|
|
|
1251 of the group in question, so you can use many of the normal Gnus
|
|
|
1252 functions for snarfing info on the group.
|
|
|
1253
|
|
|
1254 @vindex gnus-group-update-hook
|
|
|
1255 @findex gnus-group-highlight-line
|
|
|
1256 @code{gnus-group-update-hook} is called when a group line is changed.
|
|
|
1257 It will not be called when @code{gnus-visual} is @code{nil}. This hook
|
|
|
1258 calls @code{gnus-group-highlight-line} by default.
|
|
|
1259
|
|
|
1260
|
|
|
1261 @node Group Maneuvering
|
|
|
1262 @section Group Maneuvering
|
|
|
1263 @cindex group movement
|
|
|
1264
|
|
|
1265 All movement commands understand the numeric prefix and will behave as
|
|
|
1266 expected, hopefully.
|
|
|
1267
|
|
|
1268 @table @kbd
|
|
|
1269
|
|
|
1270 @item n
|
|
|
1271 @kindex n (Group)
|
|
|
1272 @findex gnus-group-next-unread-group
|
|
|
1273 Go to the next group that has unread articles
|
|
|
1274 (@code{gnus-group-next-unread-group}).
|
|
|
1275
|
|
|
1276 @item p
|
|
|
1277 @itemx DEL
|
|
|
1278 @kindex DEL (Group)
|
|
|
1279 @kindex p (Group)
|
|
|
1280 @findex gnus-group-prev-unread-group
|
|
16
|
1281 Go to the previous group that has unread articles
|
|
0
|
1282 (@code{gnus-group-prev-unread-group}).
|
|
|
1283
|
|
|
1284 @item N
|
|
|
1285 @kindex N (Group)
|
|
|
1286 @findex gnus-group-next-group
|
|
|
1287 Go to the next group (@code{gnus-group-next-group}).
|
|
|
1288
|
|
|
1289 @item P
|
|
|
1290 @kindex P (Group)
|
|
|
1291 @findex gnus-group-prev-group
|
|
|
1292 Go to the previous group (@code{gnus-group-prev-group}).
|
|
|
1293
|
|
|
1294 @item M-p
|
|
|
1295 @kindex M-p (Group)
|
|
|
1296 @findex gnus-group-next-unread-group-same-level
|
|
16
|
1297 Go to the next unread group on the same (or lower) level
|
|
0
|
1298 (@code{gnus-group-next-unread-group-same-level}).
|
|
|
1299
|
|
|
1300 @item M-n
|
|
|
1301 @kindex M-n (Group)
|
|
|
1302 @findex gnus-group-prev-unread-group-same-level
|
|
16
|
1303 Go to the previous unread group on the same (or lower) level
|
|
0
|
1304 (@code{gnus-group-prev-unread-group-same-level}).
|
|
|
1305 @end table
|
|
|
1306
|
|
|
1307 Three commands for jumping to groups:
|
|
|
1308
|
|
|
1309 @table @kbd
|
|
|
1310
|
|
|
1311 @item j
|
|
|
1312 @kindex j (Group)
|
|
|
1313 @findex gnus-group-jump-to-group
|
|
|
1314 Jump to a group (and make it visible if it isn't already)
|
|
|
1315 (@code{gnus-group-jump-to-group}). Killed groups can be jumped to, just
|
|
|
1316 like living groups.
|
|
|
1317
|
|
|
1318 @item ,
|
|
|
1319 @kindex , (Group)
|
|
|
1320 @findex gnus-group-best-unread-group
|
|
|
1321 Jump to the unread group with the lowest level
|
|
|
1322 (@code{gnus-group-best-unread-group}).
|
|
|
1323
|
|
|
1324 @item .
|
|
|
1325 @kindex . (Group)
|
|
|
1326 @findex gnus-group-first-unread-group
|
|
|
1327 Jump to the first group with unread articles
|
|
|
1328 (@code{gnus-group-first-unread-group}).
|
|
|
1329 @end table
|
|
|
1330
|
|
|
1331 @vindex gnus-group-goto-unread
|
|
|
1332 If @code{gnus-group-goto-unread} is @code{nil}, all the movement
|
|
|
1333 commands will move to the next group, not the next unread group. Even
|
|
|
1334 the commands that say they move to the next unread group. The default
|
|
|
1335 is @code{t}.
|
|
|
1336
|
|
|
1337
|
|
|
1338 @node Selecting a Group
|
|
|
1339 @section Selecting a Group
|
|
|
1340 @cindex group selection
|
|
|
1341
|
|
|
1342 @table @kbd
|
|
|
1343
|
|
|
1344 @item SPACE
|
|
|
1345 @kindex SPACE (Group)
|
|
|
1346 @findex gnus-group-read-group
|
|
|
1347 Select the current group, switch to the summary buffer and display the
|
|
|
1348 first unread article (@code{gnus-group-read-group}). If there are no
|
|
|
1349 unread articles in the group, or if you give a non-numerical prefix to
|
|
|
1350 this command, Gnus will offer to fetch all the old articles in this
|
|
16
|
1351 group from the server. If you give a numerical prefix @var{N}, @var{N}
|
|
|
1352 determines the number of articles Gnus will fetch. If @var{N} is
|
|
|
1353 positive, Gnus fetches the @var{N} newest articles, if @var{N} is
|
|
|
1354 negative, Gnus fetches the @var{abs(N)} oldest articles.
|
|
0
|
1355
|
|
|
1356 @item RET
|
|
|
1357 @kindex RET (Group)
|
|
|
1358 @findex gnus-group-select-group
|
|
|
1359 Select the current group and switch to the summary buffer
|
|
|
1360 (@code{gnus-group-select-group}). Takes the same arguments as
|
|
|
1361 @code{gnus-group-read-group}---the only difference is that this command
|
|
|
1362 does not display the first unread article automatically upon group
|
|
|
1363 entry.
|
|
|
1364
|
|
|
1365 @item M-RET
|
|
|
1366 @kindex M-RET (Group)
|
|
|
1367 @findex gnus-group-quick-select-group
|
|
|
1368 This does the same as the command above, but tries to do it with the
|
|
16
|
1369 minimum amount of fuzz (@code{gnus-group-quick-select-group}). No
|
|
0
|
1370 scoring/killing will be performed, there will be no highlights and no
|
|
|
1371 expunging. This might be useful if you're in a real hurry and have to
|
|
16
|
1372 enter some humongous group. If you give a 0 prefix to this command
|
|
|
1373 (i.e., @kbd{0 M-RET}), Gnus won't even generate the summary buffer.
|
|
|
1374 This might be useful if you want to toggle threading before entering the
|
|
|
1375 group.
|
|
0
|
1376
|
|
|
1377 @item M-SPACE
|
|
16
|
1378 @kindex M-SPACE (Group)
|
|
0
|
1379 @findex gnus-group-visible-select-group
|
|
16
|
1380 This is yet one more command that does the same as the @kbd{RET}
|
|
|
1381 command, but this one does it without expunging and hiding dormants
|
|
|
1382 (@code{gnus-group-visible-select-group}).
|
|
|
1383
|
|
|
1384 @item M-C-RET
|
|
|
1385 @kindex M-C-RET (Group)
|
|
|
1386 @findex gnus-group-select-group-ephemerally
|
|
|
1387 Finally, this command selects the current group ephemerally without
|
|
|
1388 doing any processing of its contents
|
|
|
1389 (@code{gnus-group-select-group-ephemerally}). Even threading has been
|
|
|
1390 turned off. Everything you do in the group after selecting it in this
|
|
|
1391 manner will have no permanent effects.
|
|
|
1392
|
|
0
|
1393 @end table
|
|
|
1394
|
|
|
1395 @vindex gnus-large-newsgroup
|
|
|
1396 The @code{gnus-large-newsgroup} variable says what Gnus should consider
|
|
|
1397 to be a big group. This is 200 by default. If the group has more
|
|
16
|
1398 (unread and/or ticked) articles than this, Gnus will query the user
|
|
|
1399 before entering the group. The user can then specify how many articles
|
|
|
1400 should be fetched from the server. If the user specifies a negative
|
|
|
1401 number (@code{-n}), the @code{n} oldest articles will be fetched. If it
|
|
|
1402 is positive, the @code{n} articles that have arrived most recently will
|
|
|
1403 be fetched.
|
|
0
|
1404
|
|
|
1405 @vindex gnus-select-group-hook
|
|
|
1406 @vindex gnus-auto-select-first
|
|
|
1407 @code{gnus-auto-select-first} control whether any articles are selected
|
|
16
|
1408 automatically when entering a group with the @kbd{SPACE} command.
|
|
0
|
1409
|
|
|
1410 @table @code
|
|
|
1411
|
|
|
1412 @item nil
|
|
|
1413 Don't select any articles when entering the group. Just display the
|
|
|
1414 full summary buffer.
|
|
|
1415
|
|
|
1416 @item t
|
|
|
1417 Select the first unread article when entering the group.
|
|
|
1418
|
|
|
1419 @item best
|
|
|
1420 Select the most high-scored article in the group when entering the
|
|
|
1421 group.
|
|
|
1422 @end table
|
|
|
1423
|
|
|
1424 If you want to prevent automatic selection in some group (say, in a
|
|
|
1425 binary group with Huge articles) you can set this variable to @code{nil}
|
|
|
1426 in @code{gnus-select-group-hook}, which is called when a group is
|
|
|
1427 selected.
|
|
|
1428
|
|
|
1429
|
|
|
1430 @node Subscription Commands
|
|
|
1431 @section Subscription Commands
|
|
16
|
1432 @cindex subscription
|
|
0
|
1433
|
|
|
1434 @table @kbd
|
|
|
1435
|
|
|
1436 @item S t
|
|
|
1437 @itemx u
|
|
|
1438 @kindex S t (Group)
|
|
|
1439 @kindex u (Group)
|
|
|
1440 @findex gnus-group-unsubscribe-current-group
|
|
|
1441 Toggle subscription to the current group
|
|
|
1442 (@code{gnus-group-unsubscribe-current-group}).
|
|
|
1443
|
|
|
1444 @item S s
|
|
|
1445 @itemx U
|
|
|
1446 @kindex S s (Group)
|
|
|
1447 @kindex U (Group)
|
|
|
1448 @findex gnus-group-unsubscribe-group
|
|
|
1449 Prompt for a group to subscribe, and then subscribe it. If it was
|
|
|
1450 subscribed already, unsubscribe it instead
|
|
|
1451 (@code{gnus-group-unsubscribe-group}).
|
|
|
1452
|
|
|
1453 @item S k
|
|
|
1454 @itemx C-k
|
|
|
1455 @kindex S k (Group)
|
|
|
1456 @kindex C-k (Group)
|
|
|
1457 @findex gnus-group-kill-group
|
|
|
1458 Kill the current group (@code{gnus-group-kill-group}).
|
|
|
1459
|
|
|
1460 @item S y
|
|
|
1461 @itemx C-y
|
|
|
1462 @kindex S y (Group)
|
|
|
1463 @kindex C-y (Group)
|
|
|
1464 @findex gnus-group-yank-group
|
|
|
1465 Yank the last killed group (@code{gnus-group-yank-group}).
|
|
|
1466
|
|
|
1467 @item C-x C-t
|
|
|
1468 @kindex C-x C-t (Group)
|
|
|
1469 @findex gnus-group-transpose-groups
|
|
|
1470 Transpose two groups (@code{gnus-group-transpose-groups}). This isn't
|
|
|
1471 really a subscription command, but you can use it instead of a
|
|
|
1472 kill-and-yank sequence sometimes.
|
|
|
1473
|
|
|
1474 @item S w
|
|
|
1475 @itemx C-w
|
|
|
1476 @kindex S w (Group)
|
|
|
1477 @kindex C-w (Group)
|
|
|
1478 @findex gnus-group-kill-region
|
|
|
1479 Kill all groups in the region (@code{gnus-group-kill-region}).
|
|
|
1480
|
|
|
1481 @item S z
|
|
|
1482 @kindex S z (Group)
|
|
|
1483 @findex gnus-group-kill-all-zombies
|
|
|
1484 Kill all zombie groups (@code{gnus-group-kill-all-zombies}).
|
|
|
1485
|
|
|
1486 @item S C-k
|
|
|
1487 @kindex S C-k (Group)
|
|
|
1488 @findex gnus-group-kill-level
|
|
|
1489 Kill all groups on a certain level (@code{gnus-group-kill-level}).
|
|
|
1490 These groups can't be yanked back after killing, so this command should
|
|
16
|
1491 be used with some caution. The only time where this command comes in
|
|
0
|
1492 really handy is when you have a @file{.newsrc} with lots of unsubscribed
|
|
16
|
1493 groups that you want to get rid off. @kbd{S C-k} on level 7 will
|
|
0
|
1494 kill off all unsubscribed groups that do not have message numbers in the
|
|
|
1495 @file{.newsrc} file.
|
|
|
1496
|
|
|
1497 @end table
|
|
|
1498
|
|
|
1499 Also @pxref{Group Levels}.
|
|
|
1500
|
|
|
1501
|
|
16
|
1502 @node Group Data
|
|
|
1503 @section Group Data
|
|
|
1504
|
|
|
1505 @table @kbd
|
|
|
1506
|
|
|
1507 @item c
|
|
|
1508 @kindex c (Group)
|
|
|
1509 @findex gnus-group-catchup-current
|
|
|
1510 @vindex gnus-group-catchup-group-hook
|
|
|
1511 Mark all unticked articles in this group as read
|
|
|
1512 (@code{gnus-group-catchup-current}).
|
|
|
1513 @code{gnus-group-catchup-group-hook} is called when catching up a group from
|
|
|
1514 the group buffer.
|
|
|
1515
|
|
|
1516 @item C
|
|
|
1517 @kindex C (Group)
|
|
|
1518 @findex gnus-group-catchup-current-all
|
|
|
1519 Mark all articles in this group, even the ticked ones, as read
|
|
|
1520 (@code{gnus-group-catchup-current-all}).
|
|
|
1521
|
|
|
1522 @item M-c
|
|
|
1523 @kindex M-c (Group)
|
|
|
1524 @findex gnus-group-clear-data
|
|
|
1525 Clear the data from the current group---nix out marks and the list of
|
|
|
1526 read articles (@code{gnus-group-clear-data}).
|
|
|
1527
|
|
|
1528 @item M-x gnus-group-clear-data-on-native-groups
|
|
|
1529 @kindex M-x gnus-group-clear-data-on-native-groups
|
|
|
1530 @findex gnus-group-clear-data-on-native-groups
|
|
|
1531 If you have switched from one @sc{nntp} server to another, all your marks
|
|
|
1532 and read ranges have become worthless. You can use this command to
|
|
|
1533 clear out all data that you have on your native groups. Use with
|
|
|
1534 caution.
|
|
|
1535
|
|
|
1536 @end table
|
|
|
1537
|
|
|
1538
|
|
0
|
1539 @node Group Levels
|
|
|
1540 @section Group Levels
|
|
|
1541 @cindex group level
|
|
16
|
1542 @cindex level
|
|
0
|
1543
|
|
|
1544 All groups have a level of @dfn{subscribedness}. For instance, if a
|
|
|
1545 group is on level 2, it is more subscribed than a group on level 5. You
|
|
|
1546 can ask Gnus to just list groups on a given level or lower
|
|
|
1547 (@pxref{Listing Groups}), or to just check for new articles in groups on
|
|
|
1548 a given level or lower (@pxref{Scanning New Messages}).
|
|
|
1549
|
|
|
1550 Remember: The higher the level of the group, the less important it is.
|
|
|
1551
|
|
|
1552 @table @kbd
|
|
|
1553
|
|
|
1554 @item S l
|
|
|
1555 @kindex S l (Group)
|
|
|
1556 @findex gnus-group-set-current-level
|
|
|
1557 Set the level of the current group. If a numeric prefix is given, the
|
|
|
1558 next @var{n} groups will have their levels set. The user will be
|
|
|
1559 prompted for a level.
|
|
|
1560 @end table
|
|
|
1561
|
|
|
1562 @vindex gnus-level-killed
|
|
|
1563 @vindex gnus-level-zombie
|
|
|
1564 @vindex gnus-level-unsubscribed
|
|
|
1565 @vindex gnus-level-subscribed
|
|
|
1566 Gnus considers groups on between levels 1 and
|
|
|
1567 @code{gnus-level-subscribed} (inclusive) (default 5) to be subscribed,
|
|
|
1568 @code{gnus-level-subscribed} (exclusive) and
|
|
|
1569 @code{gnus-level-unsubscribed} (inclusive) (default 7) to be
|
|
|
1570 unsubscribed, @code{gnus-level-zombie} to be zombies (walking dead)
|
|
|
1571 (default 8) and @code{gnus-level-killed} to be killed (default 9),
|
|
|
1572 completely dead. Gnus treats subscribed and unsubscribed groups exactly
|
|
|
1573 the same, but zombie and killed groups have no information on what
|
|
|
1574 articles you have read, etc, stored. This distinction between dead and
|
|
|
1575 living groups isn't done because it is nice or clever, it is done purely
|
|
|
1576 for reasons of efficiency.
|
|
|
1577
|
|
|
1578 It is recommended that you keep all your mail groups (if any) on quite
|
|
16
|
1579 low levels (e.g. 1 or 2).
|
|
0
|
1580
|
|
|
1581 If you want to play with the level variables, you should show some care.
|
|
|
1582 Set them once, and don't touch them ever again. Better yet, don't touch
|
|
|
1583 them at all unless you know exactly what you're doing.
|
|
|
1584
|
|
|
1585 @vindex gnus-level-default-unsubscribed
|
|
|
1586 @vindex gnus-level-default-subscribed
|
|
|
1587 Two closely related variables are @code{gnus-level-default-subscribed}
|
|
|
1588 (default 3) and @code{gnus-level-default-unsubscribed} (default 6),
|
|
|
1589 which are the levels that new groups will be put on if they are
|
|
|
1590 (un)subscribed. These two variables should, of course, be inside the
|
|
|
1591 relevant legal ranges.
|
|
|
1592
|
|
|
1593 @vindex gnus-keep-same-level
|
|
|
1594 If @code{gnus-keep-same-level} is non-@code{nil}, some movement commands
|
|
|
1595 will only move to groups that are of the same level (or lower). In
|
|
|
1596 particular, going from the last article in one group to the next group
|
|
|
1597 will go to the next group of the same level (or lower). This might be
|
|
|
1598 handy if you want to read the most important groups before you read the
|
|
|
1599 rest.
|
|
|
1600
|
|
|
1601 @vindex gnus-group-default-list-level
|
|
|
1602 All groups with a level less than or equal to
|
|
|
1603 @code{gnus-group-default-list-level} will be listed in the group buffer
|
|
|
1604 by default.
|
|
|
1605
|
|
|
1606 @vindex gnus-group-list-inactive-groups
|
|
|
1607 If @code{gnus-group-list-inactive-groups} is non-@code{nil}, non-active
|
|
|
1608 groups will be listed along with the unread groups. This variable is
|
|
|
1609 @code{t} by default. If it is @code{nil}, inactive groups won't be
|
|
|
1610 listed.
|
|
|
1611
|
|
|
1612 @vindex gnus-group-use-permanent-levels
|
|
|
1613 If @code{gnus-group-use-permanent-levels} is non-@code{nil}, once you
|
|
|
1614 give a level prefix to @kbd{g} or @kbd{l}, all subsequent commands will
|
|
|
1615 use this level as the ``work'' level.
|
|
|
1616
|
|
|
1617 @vindex gnus-activate-level
|
|
|
1618 Gnus will normally just activate groups that are on level
|
|
|
1619 @code{gnus-activate-level} or less. If you don't want to activate
|
|
|
1620 unsubscribed groups, for instance, you might set this variable to
|
|
16
|
1621 5. The default is 6.
|
|
0
|
1622
|
|
|
1623
|
|
|
1624 @node Group Score
|
|
|
1625 @section Group Score
|
|
|
1626 @cindex group score
|
|
|
1627
|
|
|
1628 You would normally keep important groups on high levels, but that scheme
|
|
|
1629 is somewhat restrictive. Don't you wish you could have Gnus sort the
|
|
|
1630 group buffer according to how often you read groups, perhaps? Within
|
|
|
1631 reason?
|
|
|
1632
|
|
|
1633 This is what @dfn{group score} is for. You can assign a score to each
|
|
|
1634 group. You can then sort the group buffer based on this score.
|
|
|
1635 Alternatively, you can sort on score and then level. (Taken together,
|
|
|
1636 the level and the score is called the @dfn{rank} of the group. A group
|
|
|
1637 that is on level 4 and has a score of 1 has a higher rank than a group
|
|
|
1638 on level 5 that has a score of 300. (The level is the most significant
|
|
16
|
1639 part and the score is the least significant part.))
|
|
0
|
1640
|
|
|
1641 @findex gnus-summary-bubble-group
|
|
|
1642 If you want groups you read often to get higher scores than groups you
|
|
|
1643 read seldom you can add the @code{gnus-summary-bubble-group} function to
|
|
|
1644 the @code{gnus-summary-exit-hook} hook. This will result (after
|
|
|
1645 sorting) in a bubbling sort of action. If you want to see that in
|
|
|
1646 action after each summary exit, you can add
|
|
|
1647 @code{gnus-group-sort-groups-by-rank} or
|
|
|
1648 @code{gnus-group-sort-groups-by-score} to the same hook, but that will
|
|
|
1649 slow things down somewhat.
|
|
|
1650
|
|
|
1651
|
|
|
1652 @node Marking Groups
|
|
|
1653 @section Marking Groups
|
|
|
1654 @cindex marking groups
|
|
|
1655
|
|
|
1656 If you want to perform some command on several groups, and they appear
|
|
|
1657 subsequently in the group buffer, you would normally just give a
|
|
|
1658 numerical prefix to the command. Most group commands will then do your
|
|
|
1659 bidding on those groups.
|
|
|
1660
|
|
|
1661 However, if the groups are not in sequential order, you can still
|
|
|
1662 perform a command on several groups. You simply mark the groups first
|
|
|
1663 with the process mark and then execute the command.
|
|
|
1664
|
|
|
1665 @table @kbd
|
|
|
1666
|
|
|
1667 @item #
|
|
|
1668 @kindex # (Group)
|
|
|
1669 @itemx M m
|
|
|
1670 @kindex M m (Group)
|
|
|
1671 @findex gnus-group-mark-group
|
|
|
1672 Set the mark on the current group (@code{gnus-group-mark-group}).
|
|
|
1673
|
|
|
1674 @item M-#
|
|
|
1675 @kindex M-# (Group)
|
|
|
1676 @itemx M u
|
|
|
1677 @kindex M u (Group)
|
|
|
1678 @findex gnus-group-unmark-group
|
|
|
1679 Remove the mark from the current group
|
|
|
1680 (@code{gnus-group-unmark-group}).
|
|
|
1681
|
|
|
1682 @item M U
|
|
|
1683 @kindex M U (Group)
|
|
|
1684 @findex gnus-group-unmark-all-groups
|
|
|
1685 Remove the mark from all groups (@code{gnus-group-unmark-all-groups}).
|
|
|
1686
|
|
|
1687 @item M w
|
|
|
1688 @kindex M w (Group)
|
|
|
1689 @findex gnus-group-mark-region
|
|
|
1690 Mark all groups between point and mark (@code{gnus-group-mark-region}).
|
|
|
1691
|
|
|
1692 @item M b
|
|
|
1693 @kindex M b (Group)
|
|
|
1694 @findex gnus-group-mark-buffer
|
|
|
1695 Mark all groups in the buffer (@code{gnus-group-mark-buffer}).
|
|
|
1696
|
|
|
1697 @item M r
|
|
|
1698 @kindex M r (Group)
|
|
|
1699 @findex gnus-group-mark-regexp
|
|
|
1700 Mark all groups that match some regular expression
|
|
|
1701 (@code{gnus-group-mark-regexp}).
|
|
|
1702 @end table
|
|
|
1703
|
|
|
1704 Also @pxref{Process/Prefix}.
|
|
|
1705
|
|
|
1706 @findex gnus-group-universal-argument
|
|
|
1707 If you want to execute some command on all groups that have been marked
|
|
|
1708 with the process mark, you can use the @kbd{M-&}
|
|
|
1709 (@code{gnus-group-universal-argument}) command. It will prompt you for
|
|
|
1710 the command to be executed.
|
|
|
1711
|
|
|
1712
|
|
|
1713 @node Foreign Groups
|
|
|
1714 @section Foreign Groups
|
|
16
|
1715 @cindex foreign groups
|
|
|
1716
|
|
|
1717 Below are some group mode commands for making and editing general foreign
|
|
0
|
1718 groups, as well as commands to ease the creation of a few
|
|
16
|
1719 special-purpose groups. All these commands insert the newly created
|
|
|
1720 groups under point---@code{gnus-subscribe-newsgroup-method} is not
|
|
|
1721 consulted.
|
|
0
|
1722
|
|
|
1723 @table @kbd
|
|
|
1724
|
|
|
1725 @item G m
|
|
|
1726 @kindex G m (Group)
|
|
|
1727 @findex gnus-group-make-group
|
|
16
|
1728 @cindex making groups
|
|
0
|
1729 Make a new group (@code{gnus-group-make-group}). Gnus will prompt you
|
|
|
1730 for a name, a method and possibly an @dfn{address}. For an easier way
|
|
|
1731 to subscribe to @sc{nntp} groups, @pxref{Browse Foreign Server}.
|
|
|
1732
|
|
|
1733 @item G r
|
|
|
1734 @kindex G r (Group)
|
|
|
1735 @findex gnus-group-rename-group
|
|
16
|
1736 @cindex renaming groups
|
|
0
|
1737 Rename the current group to something else
|
|
2
|
1738 (@code{gnus-group-rename-group}). This is legal only on some
|
|
|
1739 groups---mail groups mostly. This command might very well be quite slow
|
|
|
1740 on some backends.
|
|
0
|
1741
|
|
16
|
1742 @item G c
|
|
|
1743 @kindex G c (Group)
|
|
|
1744 @cindex customizing
|
|
|
1745 @findex gnus-group-customize
|
|
|
1746 Customize the group parameters (@code{gnus-group-customize}).
|
|
|
1747
|
|
0
|
1748 @item G e
|
|
|
1749 @kindex G e (Group)
|
|
|
1750 @findex gnus-group-edit-group-method
|
|
16
|
1751 @cindex renaming groups
|
|
0
|
1752 Enter a buffer where you can edit the select method of the current
|
|
|
1753 group (@code{gnus-group-edit-group-method}).
|
|
|
1754
|
|
|
1755 @item G p
|
|
|
1756 @kindex G p (Group)
|
|
|
1757 @findex gnus-group-edit-group-parameters
|
|
|
1758 Enter a buffer where you can edit the group parameters
|
|
|
1759 (@code{gnus-group-edit-group-parameters}).
|
|
|
1760
|
|
|
1761 @item G E
|
|
|
1762 @kindex G E (Group)
|
|
|
1763 @findex gnus-group-edit-group
|
|
|
1764 Enter a buffer where you can edit the group info
|
|
|
1765 (@code{gnus-group-edit-group}).
|
|
|
1766
|
|
|
1767 @item G d
|
|
|
1768 @kindex G d (Group)
|
|
|
1769 @findex gnus-group-make-directory-group
|
|
16
|
1770 @cindex nndir
|
|
|
1771 Make a directory group (@pxref{Directory Groups}). You will be prompted
|
|
|
1772 for a directory name (@code{gnus-group-make-directory-group}).
|
|
0
|
1773
|
|
|
1774 @item G h
|
|
|
1775 @kindex G h (Group)
|
|
16
|
1776 @cindex help group
|
|
0
|
1777 @findex gnus-group-make-help-group
|
|
|
1778 Make the Gnus help group (@code{gnus-group-make-help-group}).
|
|
|
1779
|
|
|
1780 @item G a
|
|
|
1781 @kindex G a (Group)
|
|
16
|
1782 @cindex (ding) archive
|
|
|
1783 @cindex archive group
|
|
0
|
1784 @findex gnus-group-make-archive-group
|
|
|
1785 @vindex gnus-group-archive-directory
|
|
|
1786 @vindex gnus-group-recent-archive-directory
|
|
|
1787 Make a Gnus archive group (@code{gnus-group-make-archive-group}). By
|
|
|
1788 default a group pointing to the most recent articles will be created
|
|
|
1789 (@code{gnus-group-recent-archive-directory}), but given a prefix, a full
|
|
2
|
1790 group will be created from @code{gnus-group-archive-directory}.
|
|
0
|
1791
|
|
|
1792 @item G k
|
|
|
1793 @kindex G k (Group)
|
|
|
1794 @findex gnus-group-make-kiboze-group
|
|
16
|
1795 @cindex nnkiboze
|
|
0
|
1796 Make a kiboze group. You will be prompted for a name, for a regexp to
|
|
|
1797 match groups to be ``included'' in the kiboze group, and a series of
|
|
|
1798 strings to match on headers (@code{gnus-group-make-kiboze-group}).
|
|
16
|
1799 @xref{Kibozed Groups}.
|
|
0
|
1800
|
|
|
1801 @item G D
|
|
|
1802 @kindex G D (Group)
|
|
|
1803 @findex gnus-group-enter-directory
|
|
16
|
1804 @cindex nneething
|
|
0
|
1805 Read an arbitrary directory as if with were a newsgroup with the
|
|
|
1806 @code{nneething} backend (@code{gnus-group-enter-directory}).
|
|
16
|
1807 @xref{Anything Groups}.
|
|
0
|
1808
|
|
|
1809 @item G f
|
|
|
1810 @kindex G f (Group)
|
|
|
1811 @findex gnus-group-make-doc-group
|
|
|
1812 @cindex ClariNet Briefs
|
|
16
|
1813 @cindex nndoc
|
|
0
|
1814 Make a group based on some file or other
|
|
|
1815 (@code{gnus-group-make-doc-group}). If you give a prefix to this
|
|
|
1816 command, you will be prompted for a file name and a file type.
|
|
|
1817 Currently supported types are @code{babyl}, @code{mbox}, @code{digest},
|
|
24
|
1818 @code{mmdf}, @code{news}, @code{rnews}, @code{clari-briefs},
|
|
34
|
1819 @code{rfc934}, @code{rfc822-forward}, and @code{forward}. If you run
|
|
|
1820 this command without a prefix, Gnus will guess at the file type.
|
|
|
1821 @xref{Document Groups}.
|
|
16
|
1822
|
|
|
1823 @item G w
|
|
|
1824 @kindex G w (Group)
|
|
|
1825 @findex gnus-group-make-web-group
|
|
|
1826 @cindex DejaNews
|
|
|
1827 @cindex Alta Vista
|
|
|
1828 @cindex InReference
|
|
|
1829 @cindex nnweb
|
|
|
1830 Make an ephemeral group based on a web search
|
|
|
1831 (@code{gnus-group-make-web-group}). If you give a prefix to this
|
|
|
1832 command, make a solid group instead. You will be prompted for the
|
|
|
1833 search engine type and the search string. Legal search engine types
|
|
|
1834 include @code{dejanews}, @code{altavista} and @code{reference}.
|
|
|
1835 @xref{Web Searches}.
|
|
0
|
1836
|
|
|
1837 @item G DEL
|
|
|
1838 @kindex G DEL (Group)
|
|
|
1839 @findex gnus-group-delete-group
|
|
|
1840 This function will delete the current group
|
|
|
1841 (@code{gnus-group-delete-group}). If given a prefix, this function will
|
|
|
1842 actually delete all the articles in the group, and forcibly remove the
|
|
|
1843 group itself from the face of the Earth. Use a prefix only if you are
|
|
|
1844 absolutely sure of what you are doing.
|
|
|
1845
|
|
|
1846 @item G V
|
|
|
1847 @kindex G V (Group)
|
|
|
1848 @findex gnus-group-make-empty-virtual
|
|
|
1849 Make a new, fresh, empty @code{nnvirtual} group
|
|
16
|
1850 (@code{gnus-group-make-empty-virtual}). @xref{Virtual Groups}.
|
|
0
|
1851
|
|
|
1852 @item G v
|
|
|
1853 @kindex G v (Group)
|
|
|
1854 @findex gnus-group-add-to-virtual
|
|
|
1855 Add the current group to an @code{nnvirtual} group
|
|
|
1856 (@code{gnus-group-add-to-virtual}). Uses the process/prefix convention.
|
|
|
1857 @end table
|
|
|
1858
|
|
|
1859 @xref{Select Methods} for more information on the various select
|
|
|
1860 methods.
|
|
|
1861
|
|
|
1862 @vindex gnus-activate-foreign-newsgroups
|
|
16
|
1863 If @code{gnus-activate-foreign-newsgroups} is a positive number,
|
|
0
|
1864 Gnus will check all foreign groups with this level or lower at startup.
|
|
|
1865 This might take quite a while, especially if you subscribe to lots of
|
|
|
1866 groups from different @sc{nntp} servers.
|
|
|
1867
|
|
|
1868
|
|
|
1869 @node Group Parameters
|
|
|
1870 @section Group Parameters
|
|
|
1871 @cindex group parameters
|
|
|
1872
|
|
|
1873 The group parameters store information local to a particular group:
|
|
|
1874
|
|
|
1875 @table @code
|
|
|
1876 @item to-address
|
|
|
1877 @cindex to-address
|
|
|
1878 If the group parameter list contains an element that looks like
|
|
|
1879 @code{(to-address . "some@@where.com")}, that address will be used by
|
|
|
1880 the backend when doing followups and posts. This is primarily useful in
|
|
|
1881 mail groups that represent closed mailing lists---mailing lists where
|
|
|
1882 it's expected that everybody that writes to the mailing list is
|
|
|
1883 subscribed to it. Since using this parameter ensures that the mail only
|
|
|
1884 goes to the mailing list itself, it means that members won't receive two
|
|
|
1885 copies of your followups.
|
|
|
1886
|
|
|
1887 Using @code{to-address} will actually work whether the group is foreign
|
|
|
1888 or not. Let's say there's a group on the server that is called
|
|
|
1889 @samp{fa.4ad-l}. This is a real newsgroup, but the server has gotten
|
|
|
1890 the articles from a mail-to-news gateway. Posting directly to this
|
|
|
1891 group is therefore impossible---you have to send mail to the mailing
|
|
|
1892 list address instead.
|
|
|
1893
|
|
|
1894 @item to-list
|
|
|
1895 @cindex to-list
|
|
|
1896 If the group parameter list has an element that looks like
|
|
|
1897 @code{(to-list . "some@@where.com")}, that address will be used when
|
|
|
1898 doing a @kbd{a} in any group. It is totally ignored when doing a
|
|
|
1899 followup---except that if it is present in a news group, you'll get mail
|
|
|
1900 group semantics when doing @kbd{f}.
|
|
|
1901
|
|
34
|
1902 If you do an @kbd{a} command in a mail group and you don't have a
|
|
|
1903 @code{to-list} group parameter, one will be added automatically upon
|
|
|
1904 sending the message.
|
|
|
1905
|
|
0
|
1906 @item broken-reply-to
|
|
|
1907 @cindex broken-reply-to
|
|
|
1908 Elements like @code{(broken-reply-to . t)} signals that @code{Reply-To}
|
|
|
1909 headers in this group are to be ignored. This can be useful if you're
|
|
|
1910 reading a mailing list group where the listserv has inserted
|
|
|
1911 @code{Reply-To} headers that point back to the listserv itself. This is
|
|
|
1912 broken behavior. So there!
|
|
|
1913
|
|
|
1914 @item to-group
|
|
|
1915 @cindex to-group
|
|
16
|
1916 Elements like @code{(to-group . "some.group.name")} means that all
|
|
|
1917 posts in that group will be sent to @code{some.group.name}.
|
|
|
1918
|
|
|
1919 @item newsgroup
|
|
|
1920 @cindex newsgroup
|
|
|
1921 If this symbol is present in the group parameter list, Gnus will treat
|
|
|
1922 all responses as if they were responses to news articles. This can be
|
|
|
1923 useful if you have a mail group that's really a mirror of a news group.
|
|
|
1924
|
|
|
1925 @item gcc-self
|
|
|
1926 @cindex gcc-self
|
|
|
1927 If this symbol is present in the group parameter list and set to
|
|
|
1928 @code{t}, new composed messages will be @code{Gcc}'d to the current
|
|
|
1929 group. If it is present and set to @code{none}, no @code{Gcc:} header
|
|
|
1930 will be generated, if it is present and a string, this string will be
|
|
|
1931 inserted literally as a @code{gcc} header (this symbol takes precedence over
|
|
|
1932 any default @code{Gcc} rules as described later).
|
|
0
|
1933
|
|
|
1934 @item auto-expire
|
|
|
1935 @cindex auto-expire
|
|
16
|
1936 If the group parameter has an element that looks like @code{(auto-expire
|
|
|
1937 . t)}, , all articles that are read will be marked as expirable. For an
|
|
|
1938 alternative approach, @pxref{Expiring Mail}.
|
|
0
|
1939
|
|
|
1940 @item total-expire
|
|
|
1941 @cindex total-expire
|
|
16
|
1942 If the group parameter has an element that looks like
|
|
|
1943 @code{(total-expire . t)}, all read articles will be put through the
|
|
0
|
1944 expiry process, even if they are not marked as expirable. Use with
|
|
16
|
1945 caution.
|
|
0
|
1946
|
|
|
1947 @item expiry-wait
|
|
|
1948 @cindex expiry-wait
|
|
|
1949 @vindex nnmail-expiry-wait-function
|
|
|
1950 If the group parameter has an element that looks like @code{(expiry-wait
|
|
|
1951 . 10)}, this value will override any @code{nnmail-expiry-wait} and
|
|
|
1952 @code{nnmail-expiry-wait-function} when expiring expirable messages.
|
|
|
1953 The value can either be a number of days (not necessarily an integer) or
|
|
|
1954 the symbols @code{never} or @code{immediate}.
|
|
|
1955
|
|
|
1956 @item score-file
|
|
16
|
1957 @cindex score file group parameter
|
|
0
|
1958 Elements that look like @code{(score-file . "file")} will make
|
|
16
|
1959 @file{file} into the current score file for the group in question. This
|
|
0
|
1960 means that all score commands you issue will end up in that file.
|
|
|
1961
|
|
16
|
1962 @item adapt-file
|
|
|
1963 @cindex adapt file group parameter
|
|
|
1964 Elements that look like @code{(adapt-file . "file")} will make
|
|
|
1965 @file{file} into the current adaptive file for the group in question.
|
|
|
1966 All adaptive score entries will be put into this file.
|
|
|
1967
|
|
0
|
1968 @item admin-address
|
|
|
1969 When unsubscribing to a mailing list you should never send the
|
|
|
1970 unsubscription notice to the mailing list itself. Instead, you'd send
|
|
|
1971 messages to the administrative address. This parameter allows you to
|
|
|
1972 put the admin address somewhere convenient.
|
|
|
1973
|
|
16
|
1974 @item display
|
|
|
1975 Elements that look like @code{(display . MODE)} says which articles to
|
|
|
1976 display on entering the group. Legal values are:
|
|
|
1977
|
|
|
1978 @table @code
|
|
|
1979 @item all
|
|
|
1980 Display all articles, both read and unread.
|
|
|
1981
|
|
|
1982 @item default
|
|
|
1983 Display the default visible articles, which normally includes unread and
|
|
|
1984 ticked articles.
|
|
|
1985 @end table
|
|
|
1986
|
|
0
|
1987 @item comment
|
|
16
|
1988 Elements that look like @code{(comment . "This is a comment")}
|
|
|
1989 are arbitrary comments on the group. They are currently ignored by
|
|
|
1990 Gnus, but provide a place for you to store information on particular
|
|
|
1991 groups.
|
|
0
|
1992
|
|
|
1993 @item @var{(variable form)}
|
|
|
1994 You can use the group parameters to set variables local to the group you
|
|
16
|
1995 are entering. If you want to turn threading off in @samp{news.answers},
|
|
|
1996 you could put @code{(gnus-show-threads nil)} in the group parameters of
|
|
|
1997 that group. @code{gnus-show-threads} will be made into a local variable
|
|
|
1998 in the summary buffer you enter, and the form @code{nil} will be
|
|
|
1999 @code{eval}ed there.
|
|
0
|
2000
|
|
|
2001 This can also be used as a group-specific hook function, if you'd like.
|
|
16
|
2002 If you want to hear a beep when you enter a group, you could put
|
|
|
2003 something like @code{(dummy-variable (ding))} in the parameters of that
|
|
|
2004 group. @code{dummy-variable} will be set to the result of the
|
|
|
2005 @code{(ding)} form, but who cares?
|
|
|
2006
|
|
|
2007 @end table
|
|
|
2008
|
|
|
2009 Use the @kbd{G p} command to edit group parameters of a group.
|
|
|
2010
|
|
|
2011 Also @pxref{Topic Parameters}.
|
|
0
|
2012
|
|
30
|
2013 Here's an example group parameter list:
|
|
|
2014
|
|
|
2015 @example
|
|
|
2016 ((to-address . "ding@@ifi.uio.no")
|
|
|
2017 (auto-expiry . t))
|
|
|
2018 @end example
|
|
|
2019
|
|
0
|
2020
|
|
|
2021 @node Listing Groups
|
|
|
2022 @section Listing Groups
|
|
|
2023 @cindex group listing
|
|
|
2024
|
|
|
2025 These commands all list various slices of the groups that are available.
|
|
|
2026
|
|
|
2027 @table @kbd
|
|
|
2028
|
|
|
2029 @item l
|
|
|
2030 @itemx A s
|
|
|
2031 @kindex A s (Group)
|
|
|
2032 @kindex l (Group)
|
|
|
2033 @findex gnus-group-list-groups
|
|
|
2034 List all groups that have unread articles
|
|
|
2035 (@code{gnus-group-list-groups}). If the numeric prefix is used, this
|
|
|
2036 command will list only groups of level ARG and lower. By default, it
|
|
16
|
2037 only lists groups of level five (i. e.,
|
|
|
2038 @code{gnus-group-default-list-level}) or lower (i.e., just subscribed
|
|
|
2039 groups).
|
|
0
|
2040
|
|
|
2041 @item L
|
|
|
2042 @itemx A u
|
|
|
2043 @kindex A u (Group)
|
|
|
2044 @kindex L (Group)
|
|
|
2045 @findex gnus-group-list-all-groups
|
|
|
2046 List all groups, whether they have unread articles or not
|
|
|
2047 (@code{gnus-group-list-all-groups}). If the numeric prefix is used,
|
|
|
2048 this command will list only groups of level ARG and lower. By default,
|
|
|
2049 it lists groups of level seven or lower (i.e., just subscribed and
|
|
|
2050 unsubscribed groups).
|
|
|
2051
|
|
|
2052 @item A l
|
|
|
2053 @kindex A l (Group)
|
|
|
2054 @findex gnus-group-list-level
|
|
|
2055 List all unread groups on a specific level
|
|
|
2056 (@code{gnus-group-list-level}). If given a prefix, also list the groups
|
|
|
2057 with no unread articles.
|
|
|
2058
|
|
|
2059 @item A k
|
|
|
2060 @kindex A k (Group)
|
|
|
2061 @findex gnus-group-list-killed
|
|
|
2062 List all killed groups (@code{gnus-group-list-killed}). If given a
|
|
|
2063 prefix argument, really list all groups that are available, but aren't
|
|
|
2064 currently (un)subscribed. This could entail reading the active file
|
|
|
2065 from the server.
|
|
|
2066
|
|
|
2067 @item A z
|
|
|
2068 @kindex A z (Group)
|
|
|
2069 @findex gnus-group-list-zombies
|
|
|
2070 List all zombie groups (@code{gnus-group-list-zombies}).
|
|
|
2071
|
|
|
2072 @item A m
|
|
|
2073 @kindex A m (Group)
|
|
|
2074 @findex gnus-group-list-matching
|
|
2
|
2075 List all unread, subscribed groups with names that match a regexp
|
|
0
|
2076 (@code{gnus-group-list-matching}).
|
|
|
2077
|
|
|
2078 @item A M
|
|
|
2079 @kindex A M (Group)
|
|
|
2080 @findex gnus-group-list-all-matching
|
|
|
2081 List groups that match a regexp (@code{gnus-group-list-all-matching}).
|
|
|
2082
|
|
|
2083 @item A A
|
|
|
2084 @kindex A A (Group)
|
|
|
2085 @findex gnus-group-list-active
|
|
|
2086 List absolutely all groups that are in the active file(s) of the
|
|
|
2087 server(s) you are connected to (@code{gnus-group-list-active}). This
|
|
|
2088 might very well take quite a while. It might actually be a better idea
|
|
16
|
2089 to do a @kbd{A M} to list all matching, and just give @samp{.} as the
|
|
|
2090 thing to match on. Also note that this command may list group that
|
|
|
2091 don't exist (yet)---these will be listed as if they are killed groups.
|
|
|
2092 Take the output with some grains of salt.
|
|
0
|
2093
|
|
|
2094 @item A a
|
|
|
2095 @kindex A a (Group)
|
|
|
2096 @findex gnus-group-apropos
|
|
|
2097 List all groups that have names that match a regexp
|
|
|
2098 (@code{gnus-group-apropos}).
|
|
|
2099
|
|
|
2100 @item A d
|
|
|
2101 @kindex A d (Group)
|
|
|
2102 @findex gnus-group-description-apropos
|
|
|
2103 List all groups that have names or descriptions that match a regexp
|
|
|
2104 (@code{gnus-group-description-apropos}).
|
|
|
2105
|
|
|
2106 @end table
|
|
|
2107
|
|
|
2108 @vindex gnus-permanently-visible-groups
|
|
|
2109 @cindex visible group parameter
|
|
|
2110 Groups that match the @code{gnus-permanently-visible-groups} regexp will
|
|
|
2111 always be shown, whether they have unread articles or not. You can also
|
|
|
2112 add the @code{visible} element to the group parameters in question to
|
|
|
2113 get the same effect.
|
|
|
2114
|
|
|
2115 @vindex gnus-list-groups-with-ticked-articles
|
|
|
2116 Groups that have just ticked articles in it are normally listed in the
|
|
|
2117 group buffer. If @code{gnus-list-groups-with-ticked-articles} is
|
|
|
2118 @code{nil}, these groups will be treated just like totally empty
|
|
|
2119 groups. It is @code{t} by default.
|
|
|
2120
|
|
|
2121
|
|
|
2122 @node Sorting Groups
|
|
|
2123 @section Sorting Groups
|
|
|
2124 @cindex sorting groups
|
|
|
2125
|
|
|
2126 @kindex C-c C-s (Group)
|
|
|
2127 @findex gnus-group-sort-groups
|
|
|
2128 @vindex gnus-group-sort-function
|
|
|
2129 The @kbd{C-c C-s} (@code{gnus-group-sort-groups}) command sorts the
|
|
|
2130 group buffer according to the function(s) given by the
|
|
|
2131 @code{gnus-group-sort-function} variable. Available sorting functions
|
|
|
2132 include:
|
|
|
2133
|
|
|
2134 @table @code
|
|
|
2135
|
|
|
2136 @item gnus-group-sort-by-alphabet
|
|
|
2137 @findex gnus-group-sort-by-alphabet
|
|
|
2138 Sort the group names alphabetically. This is the default.
|
|
|
2139
|
|
16
|
2140 @item gnus-group-sort-by-real-name
|
|
|
2141 @findex gnus-group-sort-by-real-name
|
|
|
2142 Sort the group alphabetically on the real (unprefixed) group names.
|
|
|
2143
|
|
0
|
2144 @item gnus-group-sort-by-level
|
|
|
2145 @findex gnus-group-sort-by-level
|
|
|
2146 Sort by group level.
|
|
|
2147
|
|
|
2148 @item gnus-group-sort-by-score
|
|
|
2149 @findex gnus-group-sort-by-score
|
|
|
2150 Sort by group score.
|
|
|
2151
|
|
|
2152 @item gnus-group-sort-by-rank
|
|
|
2153 @findex gnus-group-sort-by-rank
|
|
|
2154 Sort by group score and then the group level. The level and the score
|
|
|
2155 are, when taken together, the group's @dfn{rank}.
|
|
|
2156
|
|
|
2157 @item gnus-group-sort-by-unread
|
|
|
2158 @findex gnus-group-sort-by-unread
|
|
|
2159 Sort by number of unread articles.
|
|
|
2160
|
|
|
2161 @item gnus-group-sort-by-method
|
|
|
2162 @findex gnus-group-sort-by-method
|
|
16
|
2163 Sort alphabetically on the select method.
|
|
0
|
2164
|
|
|
2165
|
|
|
2166 @end table
|
|
|
2167
|
|
|
2168 @code{gnus-group-sort-function} can also be a list of sorting
|
|
|
2169 functions. In that case, the most significant sort key function must be
|
|
|
2170 the last one.
|
|
|
2171
|
|
|
2172
|
|
|
2173 There are also a number of commands for sorting directly according to
|
|
|
2174 some sorting criteria:
|
|
|
2175
|
|
|
2176 @table @kbd
|
|
|
2177 @item G S a
|
|
|
2178 @kindex G S a (Group)
|
|
|
2179 @findex gnus-group-sort-groups-by-alphabet
|
|
|
2180 Sort the group buffer alphabetically by group name
|
|
|
2181 (@code{gnus-group-sort-groups-by-alphabet}).
|
|
|
2182
|
|
|
2183 @item G S u
|
|
|
2184 @kindex G S u (Group)
|
|
|
2185 @findex gnus-group-sort-groups-by-unread
|
|
|
2186 Sort the group buffer by the number of unread articles
|
|
|
2187 (@code{gnus-group-sort-groups-by-unread}).
|
|
|
2188
|
|
|
2189 @item G S l
|
|
|
2190 @kindex G S l (Group)
|
|
|
2191 @findex gnus-group-sort-groups-by-level
|
|
|
2192 Sort the group buffer by group level
|
|
|
2193 (@code{gnus-group-sort-groups-by-level}).
|
|
|
2194
|
|
|
2195 @item G S v
|
|
|
2196 @kindex G S v (Group)
|
|
|
2197 @findex gnus-group-sort-groups-by-score
|
|
|
2198 Sort the group buffer by group score
|
|
|
2199 (@code{gnus-group-sort-groups-by-score}).
|
|
|
2200
|
|
|
2201 @item G S r
|
|
|
2202 @kindex G S r (Group)
|
|
|
2203 @findex gnus-group-sort-groups-by-rank
|
|
16
|
2204 Sort the group buffer by group rank
|
|
0
|
2205 (@code{gnus-group-sort-groups-by-rank}).
|
|
|
2206
|
|
|
2207 @item G S m
|
|
|
2208 @kindex G S m (Group)
|
|
|
2209 @findex gnus-group-sort-groups-by-method
|
|
|
2210 Sort the group buffer alphabetically by backend name
|
|
|
2211 (@code{gnus-group-sort-groups-by-method}).
|
|
|
2212
|
|
|
2213 @end table
|
|
|
2214
|
|
|
2215 When given a prefix, all these commands will sort in reverse order.
|
|
|
2216
|
|
16
|
2217 You can also sort a subset of the groups:
|
|
|
2218
|
|
|
2219 @table @kbd
|
|
|
2220 @item G P a
|
|
|
2221 @kindex G P a (Group)
|
|
|
2222 @findex gnus-group-sort-selected-groups-by-alphabet
|
|
|
2223 Sort the process/prefixed groups in the group buffer alphabetically by
|
|
|
2224 group name (@code{gnus-group-sort-selected-groups-by-alphabet}).
|
|
|
2225
|
|
|
2226 @item G P u
|
|
|
2227 @kindex G P u (Group)
|
|
|
2228 @findex gnus-group-sort-selected-groups-by-unread
|
|
|
2229 Sort the process/prefixed groups in the group buffer by the number of
|
|
|
2230 unread articles (@code{gnus-group-sort-selected-groups-by-unread}).
|
|
|
2231
|
|
|
2232 @item G P l
|
|
|
2233 @kindex G P l (Group)
|
|
|
2234 @findex gnus-group-sort-selected-groups-by-level
|
|
|
2235 Sort the process/prefixed groups in the group buffer by group level
|
|
|
2236 (@code{gnus-group-sort-selected-groups-by-level}).
|
|
|
2237
|
|
|
2238 @item G P v
|
|
|
2239 @kindex G P v (Group)
|
|
|
2240 @findex gnus-group-sort-selected-groups-by-score
|
|
|
2241 Sort the process/prefixed groups in the group buffer by group score
|
|
|
2242 (@code{gnus-group-sort-selected-groups-by-score}).
|
|
|
2243
|
|
|
2244 @item G P r
|
|
|
2245 @kindex G P r (Group)
|
|
|
2246 @findex gnus-group-sort-selected-groups-by-rank
|
|
|
2247 Sort the process/prefixed groups in the group buffer by group rank
|
|
|
2248 (@code{gnus-group-sort-selected-groups-by-rank}).
|
|
|
2249
|
|
|
2250 @item G P m
|
|
|
2251 @kindex G P m (Group)
|
|
|
2252 @findex gnus-group-sort-selected-groups-by-method
|
|
|
2253 Sort the process/prefixed groups in the group buffer alphabetically by
|
|
|
2254 backend name (@code{gnus-group-sort-selected-groups-by-method}).
|
|
|
2255
|
|
|
2256 @end table
|
|
|
2257
|
|
|
2258
|
|
0
|
2259
|
|
|
2260 @node Group Maintenance
|
|
|
2261 @section Group Maintenance
|
|
|
2262 @cindex bogus groups
|
|
|
2263
|
|
|
2264 @table @kbd
|
|
|
2265 @item b
|
|
|
2266 @kindex b (Group)
|
|
|
2267 @findex gnus-group-check-bogus-groups
|
|
|
2268 Find bogus groups and delete them
|
|
|
2269 (@code{gnus-group-check-bogus-groups}).
|
|
|
2270
|
|
|
2271 @item F
|
|
|
2272 @kindex F (Group)
|
|
|
2273 @findex gnus-find-new-newsgroups
|
|
|
2274 Find new groups and process them (@code{gnus-find-new-newsgroups}). If
|
|
|
2275 given a prefix, use the @code{ask-server} method to query the server for
|
|
|
2276 new groups.
|
|
|
2277
|
|
|
2278 @item C-c C-x
|
|
|
2279 @kindex C-c C-x (Group)
|
|
|
2280 @findex gnus-group-expire-articles
|
|
|
2281 Run all expirable articles in the current group through the expiry
|
|
|
2282 process (if any) (@code{gnus-group-expire-articles}).
|
|
|
2283
|
|
|
2284 @item C-c M-C-x
|
|
|
2285 @kindex C-c M-C-x (Group)
|
|
|
2286 @findex gnus-group-expire-all-groups
|
|
|
2287 Run all articles in all groups through the expiry process
|
|
|
2288 (@code{gnus-group-expire-all-groups}).
|
|
|
2289
|
|
|
2290 @end table
|
|
|
2291
|
|
|
2292
|
|
|
2293 @node Browse Foreign Server
|
|
|
2294 @section Browse Foreign Server
|
|
|
2295 @cindex foreign servers
|
|
|
2296 @cindex browsing servers
|
|
|
2297
|
|
|
2298 @table @kbd
|
|
|
2299 @item B
|
|
|
2300 @kindex B (Group)
|
|
|
2301 @findex gnus-group-browse-foreign-server
|
|
|
2302 You will be queried for a select method and a server name. Gnus will
|
|
|
2303 then attempt to contact this server and let you browse the groups there
|
|
|
2304 (@code{gnus-group-browse-foreign-server}).
|
|
|
2305 @end table
|
|
|
2306
|
|
|
2307 @findex gnus-browse-mode
|
|
|
2308 A new buffer with a list of available groups will appear. This buffer
|
|
16
|
2309 will be use the @code{gnus-browse-mode}. This buffer looks a bit (well,
|
|
|
2310 a lot) like a normal group buffer.
|
|
0
|
2311
|
|
|
2312 Here's a list of keystrokes available in the browse mode:
|
|
|
2313
|
|
|
2314 @table @kbd
|
|
|
2315 @item n
|
|
|
2316 @kindex n (Browse)
|
|
|
2317 @findex gnus-group-next-group
|
|
|
2318 Go to the next group (@code{gnus-group-next-group}).
|
|
|
2319
|
|
|
2320 @item p
|
|
|
2321 @kindex p (Browse)
|
|
|
2322 @findex gnus-group-prev-group
|
|
|
2323 Go to the previous group (@code{gnus-group-prev-group}).
|
|
|
2324
|
|
|
2325 @item SPACE
|
|
|
2326 @kindex SPACE (Browse)
|
|
|
2327 @findex gnus-browse-read-group
|
|
|
2328 Enter the current group and display the first article
|
|
|
2329 (@code{gnus-browse-read-group}).
|
|
|
2330
|
|
|
2331 @item RET
|
|
|
2332 @kindex RET (Browse)
|
|
|
2333 @findex gnus-browse-select-group
|
|
|
2334 Enter the current group (@code{gnus-browse-select-group}).
|
|
|
2335
|
|
|
2336 @item u
|
|
|
2337 @kindex u (Browse)
|
|
|
2338 @findex gnus-browse-unsubscribe-current-group
|
|
|
2339 Unsubscribe to the current group, or, as will be the case here,
|
|
|
2340 subscribe to it (@code{gnus-browse-unsubscribe-current-group}).
|
|
|
2341
|
|
|
2342 @item l
|
|
|
2343 @itemx q
|
|
|
2344 @kindex q (Browse)
|
|
|
2345 @kindex l (Browse)
|
|
|
2346 @findex gnus-browse-exit
|
|
|
2347 Exit browse mode (@code{gnus-browse-exit}).
|
|
|
2348
|
|
|
2349 @item ?
|
|
|
2350 @kindex ? (Browse)
|
|
|
2351 @findex gnus-browse-describe-briefly
|
|
|
2352 Describe browse mode briefly (well, there's not much to describe, is
|
|
|
2353 there) (@code{gnus-browse-describe-briefly}).
|
|
|
2354 @end table
|
|
|
2355
|
|
|
2356
|
|
|
2357 @node Exiting Gnus
|
|
|
2358 @section Exiting Gnus
|
|
|
2359 @cindex exiting Gnus
|
|
|
2360
|
|
|
2361 Yes, Gnus is ex(c)iting.
|
|
|
2362
|
|
|
2363 @table @kbd
|
|
|
2364 @item z
|
|
|
2365 @kindex z (Group)
|
|
|
2366 @findex gnus-group-suspend
|
|
|
2367 Suspend Gnus (@code{gnus-group-suspend}). This doesn't really exit Gnus,
|
|
|
2368 but it kills all buffers except the Group buffer. I'm not sure why this
|
|
|
2369 is a gain, but then who am I to judge?
|
|
|
2370
|
|
|
2371 @item q
|
|
|
2372 @kindex q (Group)
|
|
|
2373 @findex gnus-group-exit
|
|
|
2374 Quit Gnus (@code{gnus-group-exit}).
|
|
|
2375
|
|
|
2376 @item Q
|
|
|
2377 @kindex Q (Group)
|
|
|
2378 @findex gnus-group-quit
|
|
16
|
2379 Quit Gnus without saving the @file{.newsrc} files (@code{gnus-group-quit}).
|
|
|
2380 The dribble file will be saved, though (@pxref{Auto Save}).
|
|
0
|
2381 @end table
|
|
|
2382
|
|
|
2383 @vindex gnus-exit-gnus-hook
|
|
|
2384 @vindex gnus-suspend-gnus-hook
|
|
|
2385 @code{gnus-suspend-gnus-hook} is called when you suspend Gnus and
|
|
|
2386 @code{gnus-exit-gnus-hook} is called when you quit Gnus, while
|
|
|
2387 @code{gnus-after-exiting-gnus-hook} is called as the final item when
|
|
|
2388 exiting Gnus.
|
|
|
2389
|
|
|
2390 @findex gnus-unload
|
|
|
2391 @cindex unloading
|
|
|
2392 If you wish to completely unload Gnus and all its adherents, you can use
|
|
|
2393 the @code{gnus-unload} command. This command is also very handy when
|
|
|
2394 trying to customize meta-variables.
|
|
|
2395
|
|
|
2396 Note:
|
|
|
2397
|
|
|
2398 @quotation
|
|
16
|
2399 Miss Lisa Cannifax, while sitting in English class, felt her feet go
|
|
0
|
2400 numbly heavy and herself fall into a hazy trance as the boy sitting
|
|
|
2401 behind her drew repeated lines with his pencil across the back of her
|
|
|
2402 plastic chair.
|
|
|
2403 @end quotation
|
|
|
2404
|
|
|
2405
|
|
|
2406 @node Group Topics
|
|
|
2407 @section Group Topics
|
|
|
2408 @cindex topics
|
|
|
2409
|
|
|
2410 If you read lots and lots of groups, it might be convenient to group
|
|
|
2411 them hierarchically according to topics. You put your Emacs groups over
|
|
|
2412 here, your sex groups over there, and the rest (what, two groups or so?)
|
|
|
2413 you put in some misc section that you never bother with anyway. You can
|
|
|
2414 even group the Emacs sex groups as a sub-topic to either the Emacs
|
|
|
2415 groups or the sex groups---or both! Go wild!
|
|
|
2416
|
|
16
|
2417 Here's an example:
|
|
|
2418
|
|
|
2419 @example
|
|
|
2420 Gnus
|
|
|
2421 Emacs -- I wuw it!
|
|
|
2422 3: comp.emacs
|
|
|
2423 2: alt.religion.emacs
|
|
|
2424 Naughty Emacs
|
|
|
2425 452: alt.sex.emacs
|
|
|
2426 0: comp.talk.emacs.recovery
|
|
|
2427 Misc
|
|
|
2428 8: comp.binaries.fractals
|
|
|
2429 13: comp.sources.unix
|
|
|
2430 @end example
|
|
|
2431
|
|
0
|
2432 @findex gnus-topic-mode
|
|
|
2433 @kindex t (Group)
|
|
|
2434 To get this @emph{fab} functionality you simply turn on (ooh!) the
|
|
|
2435 @code{gnus-topic} minor mode---type @kbd{t} in the group buffer. (This
|
|
|
2436 is a toggling command.)
|
|
|
2437
|
|
|
2438 Go ahead, just try it. I'll still be here when you get back. La de
|
|
|
2439 dum... Nice tune, that... la la la... What, you're back? Yes, and now
|
|
|
2440 press @kbd{l}. There. All your groups are now listed under
|
|
|
2441 @samp{misc}. Doesn't that make you feel all warm and fuzzy? Hot and
|
|
|
2442 bothered?
|
|
|
2443
|
|
|
2444 If you want this permanently enabled, you should add that minor mode to
|
|
|
2445 the hook for the group mode:
|
|
|
2446
|
|
|
2447 @lisp
|
|
|
2448 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
|
|
|
2449 @end lisp
|
|
|
2450
|
|
|
2451 @menu
|
|
|
2452 * Topic Variables:: How to customize the topics the Lisp Way.
|
|
|
2453 * Topic Commands:: Interactive E-Z commands.
|
|
16
|
2454 * Topic Sorting:: Sorting each topic individually.
|
|
0
|
2455 * Topic Topology:: A map of the world.
|
|
16
|
2456 * Topic Parameters:: Parameters that apply to all groups in a topic.
|
|
0
|
2457 @end menu
|
|
|
2458
|
|
|
2459
|
|
|
2460 @node Topic Variables
|
|
|
2461 @subsection Topic Variables
|
|
|
2462 @cindex topic variables
|
|
|
2463
|
|
|
2464 Now, if you select a topic, if will fold/unfold that topic, which is
|
|
|
2465 really neat, I think.
|
|
|
2466
|
|
|
2467 @vindex gnus-topic-line-format
|
|
|
2468 The topic lines themselves are created according to the
|
|
16
|
2469 @code{gnus-topic-line-format} variable (@pxref{Formatting Variables}).
|
|
|
2470 Legal elements are:
|
|
0
|
2471
|
|
|
2472 @table @samp
|
|
|
2473 @item i
|
|
|
2474 Indentation.
|
|
|
2475 @item n
|
|
|
2476 Topic name.
|
|
|
2477 @item v
|
|
|
2478 Visibility.
|
|
|
2479 @item l
|
|
|
2480 Level.
|
|
|
2481 @item g
|
|
|
2482 Number of groups in the topic.
|
|
|
2483 @item a
|
|
|
2484 Number of unread articles in the topic.
|
|
|
2485 @item A
|
|
|
2486 Number of unread articles in the topic and all its subtopics.
|
|
|
2487 @end table
|
|
|
2488
|
|
|
2489 @vindex gnus-topic-indent-level
|
|
|
2490 Each sub-topic (and the groups in the sub-topics) will be indented with
|
|
|
2491 @code{gnus-topic-indent-level} times the topic level number of spaces.
|
|
16
|
2492 The default is 2.
|
|
0
|
2493
|
|
|
2494 @vindex gnus-topic-mode-hook
|
|
|
2495 @code{gnus-topic-mode-hook} is called in topic minor mode buffers.
|
|
|
2496
|
|
16
|
2497 @vindex gnus-topic-display-empty-topics
|
|
|
2498 The @code{gnus-topic-display-empty-topics} says whether to display even
|
|
|
2499 topics that have no unread articles in them. The default is @code{t}.
|
|
|
2500
|
|
0
|
2501
|
|
|
2502 @node Topic Commands
|
|
|
2503 @subsection Topic Commands
|
|
|
2504 @cindex topic commands
|
|
|
2505
|
|
|
2506 When the topic minor mode is turned on, a new @kbd{T} submap will be
|
|
|
2507 available. In addition, a few of the standard keys change their
|
|
|
2508 definitions slightly.
|
|
|
2509
|
|
|
2510 @table @kbd
|
|
|
2511
|
|
|
2512 @item T n
|
|
16
|
2513 @kindex T n (Topic)
|
|
0
|
2514 @findex gnus-topic-create-topic
|
|
|
2515 Prompt for a new topic name and create it
|
|
|
2516 (@code{gnus-topic-create-topic}).
|
|
|
2517
|
|
|
2518 @item T m
|
|
16
|
2519 @kindex T m (Topic)
|
|
0
|
2520 @findex gnus-topic-move-group
|
|
|
2521 Move the current group to some other topic
|
|
16
|
2522 (@code{gnus-topic-move-group}). This command uses the process/prefix
|
|
|
2523 convention (@pxref{Process/Prefix}).
|
|
0
|
2524
|
|
|
2525 @item T c
|
|
16
|
2526 @kindex T c (Topic)
|
|
0
|
2527 @findex gnus-topic-copy-group
|
|
|
2528 Copy the current group to some other topic
|
|
16
|
2529 (@code{gnus-topic-copy-group}). This command uses the process/prefix
|
|
|
2530 convention (@pxref{Process/Prefix}).
|
|
0
|
2531
|
|
|
2532 @item T D
|
|
16
|
2533 @kindex T D (Topic)
|
|
0
|
2534 @findex gnus-topic-remove-group
|
|
|
2535 Remove a group from the current topic (@code{gnus-topic-remove-group}).
|
|
16
|
2536 This command uses the process/prefix convention
|
|
0
|
2537 (@pxref{Process/Prefix}).
|
|
|
2538
|
|
|
2539 @item T M
|
|
16
|
2540 @kindex T M (Topic)
|
|
0
|
2541 @findex gnus-topic-move-matching
|
|
|
2542 Move all groups that match some regular expression to a topic
|
|
|
2543 (@code{gnus-topic-move-matching}).
|
|
|
2544
|
|
|
2545 @item T C
|
|
16
|
2546 @kindex T C (Topic)
|
|
0
|
2547 @findex gnus-topic-copy-matching
|
|
|
2548 Copy all groups that match some regular expression to a topic
|
|
|
2549 (@code{gnus-topic-copy-matching}).
|
|
|
2550
|
|
|
2551 @item T #
|
|
16
|
2552 @kindex T # (Topic)
|
|
0
|
2553 @findex gnus-topic-mark-topic
|
|
|
2554 Mark all groups in the current topic with the process mark
|
|
|
2555 (@code{gnus-topic-mark-topic}).
|
|
|
2556
|
|
|
2557 @item T M-#
|
|
16
|
2558 @kindex T M-# (Topic)
|
|
0
|
2559 @findex gnus-topic-unmark-topic
|
|
|
2560 Remove the process mark from all groups in the current topic
|
|
|
2561 (@code{gnus-topic-unmark-topic}).
|
|
|
2562
|
|
|
2563 @item RET
|
|
16
|
2564 @kindex RET (Topic)
|
|
0
|
2565 @findex gnus-topic-select-group
|
|
|
2566 @itemx SPACE
|
|
|
2567 Either select a group or fold a topic (@code{gnus-topic-select-group}).
|
|
|
2568 When you perform this command on a group, you'll enter the group, as
|
|
|
2569 usual. When done on a topic line, the topic will be folded (if it was
|
|
|
2570 visible) or unfolded (if it was folded already). So it's basically a
|
|
|
2571 toggling command on topics. In addition, if you give a numerical
|
|
|
2572 prefix, group on that level (and lower) will be displayed.
|
|
|
2573
|
|
|
2574 @item T TAB
|
|
16
|
2575 @kindex T TAB (Topic)
|
|
0
|
2576 @findex gnus-topic-indent
|
|
|
2577 ``Indent'' the current topic so that it becomes a sub-topic of the
|
|
|
2578 previous topic (@code{gnus-topic-indent}). If given a prefix,
|
|
|
2579 ``un-indent'' the topic instead.
|
|
|
2580
|
|
|
2581 @item C-k
|
|
16
|
2582 @kindex C-k (Topic)
|
|
0
|
2583 @findex gnus-topic-kill-group
|
|
16
|
2584 Kill a group or topic (@code{gnus-topic-kill-group}). All groups in the
|
|
|
2585 topic will be removed along with the topic.
|
|
0
|
2586
|
|
|
2587 @item C-y
|
|
16
|
2588 @kindex C-y (Topic)
|
|
0
|
2589 @findex gnus-topic-yank-group
|
|
16
|
2590 Yank the previously killed group or topic
|
|
|
2591 (@code{gnus-topic-yank-group}). Note that all topics will be yanked
|
|
|
2592 before all groups.
|
|
0
|
2593
|
|
|
2594 @item T r
|
|
16
|
2595 @kindex T r (Topic)
|
|
0
|
2596 @findex gnus-topic-rename
|
|
|
2597 Rename a topic (@code{gnus-topic-rename}).
|
|
|
2598
|
|
|
2599 @item T DEL
|
|
16
|
2600 @kindex T DEL (Topic)
|
|
0
|
2601 @findex gnus-topic-delete
|
|
|
2602 Delete an empty topic (@code{gnus-topic-delete}).
|
|
|
2603
|
|
|
2604 @item A T
|
|
16
|
2605 @kindex A T (Topic)
|
|
0
|
2606 @findex gnus-topic-list-active
|
|
|
2607 List all groups that Gnus knows about in a topics-ified way
|
|
|
2608 (@code{gnus-topic-list-active}).
|
|
|
2609
|
|
16
|
2610 @item G p
|
|
|
2611 @kindex G p (Topic)
|
|
|
2612 @findex gnus-topic-edit-parameters
|
|
|
2613 @cindex group parameters
|
|
|
2614 @cindex topic parameters
|
|
|
2615 @cindex parameters
|
|
|
2616 Edit the topic parameters (@code{gnus-topic-edit-parameters}).
|
|
|
2617 @xref{Topic Parameters}.
|
|
|
2618
|
|
|
2619 @end table
|
|
|
2620
|
|
|
2621
|
|
|
2622 @node Topic Sorting
|
|
|
2623 @subsection Topic Sorting
|
|
|
2624 @cindex topic sorting
|
|
|
2625
|
|
|
2626 You can sort the groups in each topic individually with the following
|
|
|
2627 commands:
|
|
|
2628
|
|
|
2629
|
|
|
2630 @table @kbd
|
|
|
2631 @item T S a
|
|
|
2632 @kindex T S a (Topic)
|
|
|
2633 @findex gnus-topic-sort-groups-by-alphabet
|
|
|
2634 Sort the current topic alphabetically by group name
|
|
|
2635 (@code{gnus-topic-sort-groups-by-alphabet}).
|
|
|
2636
|
|
|
2637 @item T S u
|
|
|
2638 @kindex T S u (Topic)
|
|
|
2639 @findex gnus-topic-sort-groups-by-unread
|
|
|
2640 Sort the current topic by the number of unread articles
|
|
|
2641 (@code{gnus-topic-sort-groups-by-unread}).
|
|
|
2642
|
|
|
2643 @item T S l
|
|
|
2644 @kindex T S l (Topic)
|
|
|
2645 @findex gnus-topic-sort-groups-by-level
|
|
|
2646 Sort the current topic by group level
|
|
|
2647 (@code{gnus-topic-sort-groups-by-level}).
|
|
|
2648
|
|
|
2649 @item T S v
|
|
|
2650 @kindex T S v (Topic)
|
|
|
2651 @findex gnus-topic-sort-groups-by-score
|
|
|
2652 Sort the current topic by group score
|
|
|
2653 (@code{gnus-topic-sort-groups-by-score}).
|
|
|
2654
|
|
|
2655 @item T S r
|
|
|
2656 @kindex T S r (Topic)
|
|
|
2657 @findex gnus-topic-sort-groups-by-rank
|
|
|
2658 Sort the current topic by group rank
|
|
|
2659 (@code{gnus-topic-sort-groups-by-rank}).
|
|
|
2660
|
|
|
2661 @item T S m
|
|
|
2662 @kindex T S m (Topic)
|
|
|
2663 @findex gnus-topic-sort-groups-by-method
|
|
|
2664 Sort the current topic alphabetically by backend name
|
|
|
2665 (@code{gnus-topic-sort-groups-by-method}).
|
|
|
2666
|
|
|
2667 @end table
|
|
|
2668
|
|
|
2669 @xref{Sorting Groups} for more information about group sorting.
|
|
0
|
2670
|
|
|
2671
|
|
|
2672 @node Topic Topology
|
|
|
2673 @subsection Topic Topology
|
|
|
2674 @cindex topic topology
|
|
|
2675 @cindex topology
|
|
|
2676
|
|
|
2677 So, let's have a look at an example group buffer:
|
|
|
2678
|
|
|
2679 @example
|
|
|
2680 Gnus
|
|
|
2681 Emacs -- I wuw it!
|
|
16
|
2682 3: comp.emacs
|
|
|
2683 2: alt.religion.emacs
|
|
0
|
2684 Naughty Emacs
|
|
|
2685 452: alt.sex.emacs
|
|
|
2686 0: comp.talk.emacs.recovery
|
|
|
2687 Misc
|
|
16
|
2688 8: comp.binaries.fractals
|
|
|
2689 13: comp.sources.unix
|
|
0
|
2690 @end example
|
|
|
2691
|
|
16
|
2692 So, here we have one top-level topic (@samp{Gnus}), two topics under
|
|
|
2693 that, and one sub-topic under one of the sub-topics. (There is always
|
|
|
2694 just one (1) top-level topic). This topology can be expressed as
|
|
|
2695 follows:
|
|
0
|
2696
|
|
|
2697 @lisp
|
|
|
2698 (("Gnus" visible)
|
|
|
2699 (("Emacs -- I wuw it!" visible)
|
|
|
2700 (("Naughty Emacs" visible)))
|
|
|
2701 (("Misc" visible)))
|
|
|
2702 @end lisp
|
|
|
2703
|
|
|
2704 @vindex gnus-topic-topology
|
|
|
2705 This is in fact how the variable @code{gnus-topic-topology} would look
|
|
|
2706 for the display above. That variable is saved in the @file{.newsrc.eld}
|
|
|
2707 file, and shouldn't be messed with manually---unless you really want
|
|
|
2708 to. Since this variable is read from the @file{.newsrc.eld} file,
|
|
|
2709 setting it in any other startup files will have no effect.
|
|
|
2710
|
|
|
2711 This topology shows what topics are sub-topics of what topics (right),
|
|
|
2712 and which topics are visible. Two settings are currently
|
|
|
2713 allowed---@code{visible} and @code{invisible}.
|
|
|
2714
|
|
|
2715
|
|
16
|
2716 @node Topic Parameters
|
|
|
2717 @subsection Topic Parameters
|
|
|
2718 @cindex topic parameters
|
|
|
2719
|
|
|
2720 All groups in a topic will inherit group parameters from the parent (and
|
|
|
2721 ancestor) topic parameters. All legal group parameters are legal topic
|
|
|
2722 parameters (@pxref{Group Parameters}).
|
|
|
2723
|
|
|
2724 Group parameters (of course) override topic parameters, and topic
|
|
|
2725 parameters in sub-topics override topic parameters in super-topics. You
|
|
|
2726 know. Normal inheritance rules. (@dfn{Rules} is here a noun, not a
|
|
|
2727 verb, although you may feel free to disagree with me here.)
|
|
|
2728
|
|
|
2729 @example
|
|
|
2730 Gnus
|
|
|
2731 Emacs
|
|
|
2732 3: comp.emacs
|
|
|
2733 2: alt.religion.emacs
|
|
|
2734 452: alt.sex.emacs
|
|
|
2735 Relief
|
|
|
2736 452: alt.sex.emacs
|
|
|
2737 0: comp.talk.emacs.recovery
|
|
|
2738 Misc
|
|
|
2739 8: comp.binaries.fractals
|
|
|
2740 13: comp.sources.unix
|
|
|
2741 452: alt.sex.emacs
|
|
|
2742 @end example
|
|
|
2743
|
|
|
2744 The @samp{Emacs} topic has the topic parameter @code{(score-file
|
|
|
2745 . "emacs.SCORE")}; the @samp{Relief} topic has the topic parameter
|
|
|
2746 @code{(score-file . "relief.SCORE")}; and the @samp{Misc} topic has the
|
|
|
2747 topic parameter @code{(score-file . "emacs.SCORE")}. In addition,
|
|
|
2748 @samp{alt.religion.emacs} has the group parameter @code{(score-file
|
|
|
2749 . "religion.SCORE")}.
|
|
|
2750
|
|
|
2751 Now, when you enter @samp{alt.sex.emacs} in the @samp{Relief} topic, you
|
|
|
2752 will get the @file{relief.SCORE} home score file. If you enter the same
|
|
|
2753 group in the @samp{Emacs} topic, you'll get the @file{emacs.SCORE} home
|
|
|
2754 score file. If you enter the group @samp{alt.religion.emacs}, you'll
|
|
|
2755 get the @file{religion.SCORE} home score file.
|
|
|
2756
|
|
|
2757 This seems rather simple and self-evident, doesn't it? Well, yes. But
|
|
|
2758 there are some problems, especially with the @code{total-expiry}
|
|
|
2759 parameter. Say you have a mail group in two topics; one with
|
|
|
2760 @code{total-expiry} and one without. What happens when you do @kbd{M-x
|
|
|
2761 gnus-expire-all-expirable-groups}? Gnus has no way of telling which one
|
|
|
2762 of these topics you mean to expire articles from, so anything may
|
|
|
2763 happen. In fact, I hereby declare that it is @dfn{undefined} what
|
|
|
2764 happens. You just have to be careful if you do stuff like that.
|
|
|
2765
|
|
|
2766
|
|
0
|
2767 @node Misc Group Stuff
|
|
|
2768 @section Misc Group Stuff
|
|
|
2769
|
|
|
2770 @menu
|
|
|
2771 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
|
|
|
2772 * Group Information:: Information and help on groups and Gnus.
|
|
16
|
2773 * Group Timestamp:: Making Gnus keep track of when you last read a group.
|
|
0
|
2774 * File Commands:: Reading and writing the Gnus files.
|
|
|
2775 @end menu
|
|
|
2776
|
|
|
2777 @table @kbd
|
|
|
2778
|
|
|
2779 @item ^
|
|
|
2780 @kindex ^ (Group)
|
|
|
2781 @findex gnus-group-enter-server-mode
|
|
16
|
2782 Enter the server buffer (@code{gnus-group-enter-server-mode}).
|
|
|
2783 @xref{The Server Buffer}.
|
|
0
|
2784
|
|
|
2785 @item a
|
|
|
2786 @kindex a (Group)
|
|
|
2787 @findex gnus-group-post-news
|
|
|
2788 Post an article to a group (@code{gnus-group-post-news}). The current
|
|
|
2789 group name will be used as the default.
|
|
|
2790
|
|
|
2791 @item m
|
|
|
2792 @kindex m (Group)
|
|
|
2793 @findex gnus-group-mail
|
|
|
2794 Mail a message somewhere (@code{gnus-group-mail}).
|
|
|
2795
|
|
|
2796 @end table
|
|
|
2797
|
|
|
2798 Variables for the group buffer:
|
|
|
2799
|
|
|
2800 @table @code
|
|
|
2801
|
|
|
2802 @item gnus-group-mode-hook
|
|
|
2803 @vindex gnus-group-mode-hook
|
|
|
2804 @code{gnus-group-mode-hook} is called after the group buffer has been
|
|
|
2805 created.
|
|
|
2806
|
|
|
2807 @item gnus-group-prepare-hook
|
|
|
2808 @vindex gnus-group-prepare-hook
|
|
|
2809 @code{gnus-group-prepare-hook} is called after the group buffer is
|
|
|
2810 generated. It may be used to modify the buffer in some strange,
|
|
|
2811 unnatural way.
|
|
|
2812
|
|
|
2813 @item gnus-permanently-visible-groups
|
|
|
2814 @vindex gnus-permanently-visible-groups
|
|
|
2815 Groups matching this regexp will always be listed in the group buffer,
|
|
|
2816 whether they are empty or not.
|
|
|
2817
|
|
|
2818 @end table
|
|
|
2819
|
|
|
2820
|
|
|
2821 @node Scanning New Messages
|
|
|
2822 @subsection Scanning New Messages
|
|
|
2823 @cindex new messages
|
|
|
2824 @cindex scanning new news
|
|
|
2825
|
|
|
2826 @table @kbd
|
|
|
2827
|
|
|
2828 @item g
|
|
|
2829 @kindex g (Group)
|
|
|
2830 @findex gnus-group-get-new-news
|
|
|
2831 Check the server(s) for new articles. If the numerical prefix is used,
|
|
|
2832 this command will check only groups of level @var{arg} and lower
|
|
|
2833 (@code{gnus-group-get-new-news}). If given a non-numerical prefix, this
|
|
|
2834 command will force a total rereading of the active file(s) from the
|
|
|
2835 backend(s).
|
|
|
2836
|
|
|
2837 @item M-g
|
|
|
2838 @kindex M-g (Group)
|
|
|
2839 @findex gnus-group-get-new-news-this-group
|
|
|
2840 @vindex gnus-goto-next-group-when-activating
|
|
|
2841 Check whether new articles have arrived in the current group
|
|
16
|
2842 (@code{gnus-group-get-new-news-this-group}).
|
|
|
2843 @code{gnus-goto-next-group-when-activating} says whether this command is
|
|
|
2844 to move point to the next group or not. It is @code{t} by default.
|
|
0
|
2845
|
|
|
2846 @findex gnus-activate-all-groups
|
|
|
2847 @cindex activating groups
|
|
|
2848 @item C-c M-g
|
|
|
2849 @kindex C-c M-g (Group)
|
|
|
2850 Activate absolutely all groups (@code{gnus-activate-all-groups}).
|
|
|
2851
|
|
|
2852 @item R
|
|
|
2853 @kindex R (Group)
|
|
|
2854 @cindex restarting
|
|
|
2855 @findex gnus-group-restart
|
|
16
|
2856 Restart Gnus (@code{gnus-group-restart}). This saves the @file{.newsrc}
|
|
|
2857 file(s), closes the connection to all servers, clears up all run-time
|
|
|
2858 Gnus variables, and then starts Gnus all over again.
|
|
0
|
2859
|
|
|
2860 @end table
|
|
|
2861
|
|
|
2862 @vindex gnus-get-new-news-hook
|
|
|
2863 @code{gnus-get-new-news-hook} is run just before checking for new news.
|
|
|
2864
|
|
|
2865 @vindex gnus-after-getting-new-news-hook
|
|
|
2866 @code{gnus-after-getting-new-news-hook} is run after checking for new
|
|
|
2867 news.
|
|
|
2868
|
|
|
2869
|
|
|
2870 @node Group Information
|
|
|
2871 @subsection Group Information
|
|
|
2872 @cindex group information
|
|
|
2873 @cindex information on groups
|
|
|
2874
|
|
|
2875 @table @kbd
|
|
|
2876
|
|
16
|
2877
|
|
|
2878 @item H f
|
|
|
2879 @kindex H f (Group)
|
|
0
|
2880 @findex gnus-group-fetch-faq
|
|
16
|
2881 @vindex gnus-group-faq-directory
|
|
0
|
2882 @cindex FAQ
|
|
|
2883 @cindex ange-ftp
|
|
|
2884 Try to fetch the FAQ for the current group
|
|
|
2885 (@code{gnus-group-fetch-faq}). Gnus will try to get the FAQ from
|
|
|
2886 @code{gnus-group-faq-directory}, which is usually a directory on a
|
|
16
|
2887 remote machine. This variable can also be a list of directories. In
|
|
|
2888 that case, giving a prefix to this command will allow you to choose
|
|
|
2889 between the various sites. @code{ange-ftp} (or @code{efs}) will be used
|
|
|
2890 for fetching the file.
|
|
|
2891
|
|
|
2892 If fetching from the first site is unsuccessful, Gnus will attempt to go
|
|
|
2893 through @code{gnus-group-faq-directory} and try to open them one by one.
|
|
|
2894
|
|
|
2895 @item H d
|
|
|
2896 @itemx C-c C-d
|
|
|
2897 @kindex H d (Group)
|
|
|
2898 @kindex C-c C-d (Group)
|
|
0
|
2899 @cindex describing groups
|
|
|
2900 @cindex group description
|
|
|
2901 @findex gnus-group-describe-group
|
|
|
2902 Describe the current group (@code{gnus-group-describe-group}). If given
|
|
|
2903 a prefix, force Gnus to re-read the description from the server.
|
|
|
2904
|
|
|
2905 @item M-d
|
|
|
2906 @kindex M-d (Group)
|
|
|
2907 @findex gnus-group-describe-all-groups
|
|
|
2908 Describe all groups (@code{gnus-group-describe-all-groups}). If given a
|
|
|
2909 prefix, force Gnus to re-read the description file from the server.
|
|
|
2910
|
|
|
2911 @item V
|
|
|
2912 @kindex V (Group)
|
|
|
2913 @cindex version
|
|
|
2914 @findex gnus-version
|
|
|
2915 Display current Gnus version numbers (@code{gnus-version}).
|
|
|
2916
|
|
|
2917 @item ?
|
|
|
2918 @kindex ? (Group)
|
|
|
2919 @findex gnus-group-describe-briefly
|
|
|
2920 Give a very short help message (@code{gnus-group-describe-briefly}).
|
|
|
2921
|
|
|
2922 @item C-c C-i
|
|
|
2923 @kindex C-c C-i (Group)
|
|
|
2924 @cindex info
|
|
|
2925 @cindex manual
|
|
|
2926 @findex gnus-info-find-node
|
|
|
2927 Go to the Gnus info node (@code{gnus-info-find-node}).
|
|
|
2928 @end table
|
|
|
2929
|
|
|
2930
|
|
16
|
2931 @node Group Timestamp
|
|
|
2932 @subsection Group Timestamp
|
|
|
2933 @cindex timestamps
|
|
|
2934 @cindex group timestamps
|
|
|
2935
|
|
|
2936 It can be convenient to let Gnus keep track of when you last read a
|
|
|
2937 group. To set the ball rolling, you should add
|
|
|
2938 @code{gnus-group-set-timestamp} to @code{gnus-select-group-hook}:
|
|
|
2939
|
|
|
2940 @lisp
|
|
|
2941 (add-hook 'gnus-select-group-hook 'gnus-group-set-timestamp)
|
|
|
2942 @end lisp
|
|
|
2943
|
|
|
2944 After doing this, each time you enter a group, it'll be recorded.
|
|
|
2945
|
|
|
2946 This information can be displayed in various ways---the easiest is to
|
|
|
2947 use the @samp{%d} spec in the group line format:
|
|
|
2948
|
|
|
2949 @lisp
|
|
|
2950 (setq gnus-group-line-format
|
|
|
2951 "%M\%S\%p\%P\%5y: %(%-40,40g%) %d\n")
|
|
|
2952 @end lisp
|
|
|
2953
|
|
|
2954 This will result in lines looking like:
|
|
|
2955
|
|
|
2956 @example
|
|
|
2957 * 0: mail.ding 19961002T012943
|
|
|
2958 0: custom 19961002T012713
|
|
|
2959 @end example
|
|
|
2960
|
|
|
2961 As you can see, the date is displayed in compact ISO 8601 format. This
|
|
|
2962 may be a bit too much, so to just display the date, you could say
|
|
|
2963 something like:
|
|
|
2964
|
|
|
2965 @lisp
|
|
|
2966 (setq gnus-group-line-format
|
|
|
2967 "%M\%S\%p\%P\%5y: %(%-40,40g%) %6,6~(cut 2)d\n")
|
|
|
2968 @end lisp
|
|
|
2969
|
|
|
2970
|
|
0
|
2971 @node File Commands
|
|
|
2972 @subsection File Commands
|
|
|
2973 @cindex file commands
|
|
|
2974
|
|
|
2975 @table @kbd
|
|
|
2976
|
|
|
2977 @item r
|
|
|
2978 @kindex r (Group)
|
|
|
2979 @findex gnus-group-read-init-file
|
|
|
2980 @vindex gnus-init-file
|
|
|
2981 @cindex reading init file
|
|
16
|
2982 Re-read the init file (@code{gnus-init-file}, which defaults to
|
|
0
|
2983 @file{~/.gnus}) (@code{gnus-group-read-init-file}).
|
|
|
2984
|
|
|
2985 @item s
|
|
|
2986 @kindex s (Group)
|
|
|
2987 @findex gnus-group-save-newsrc
|
|
|
2988 @cindex saving .newsrc
|
|
|
2989 Save the @file{.newsrc.eld} file (and @file{.newsrc} if wanted)
|
|
|
2990 (@code{gnus-group-save-newsrc}). If given a prefix, force saving the
|
|
|
2991 file(s) whether Gnus thinks it is necessary or not.
|
|
|
2992
|
|
2
|
2993 @c @item Z
|
|
|
2994 @c @kindex Z (Group)
|
|
|
2995 @c @findex gnus-group-clear-dribble
|
|
|
2996 @c Clear the dribble buffer (@code{gnus-group-clear-dribble}).
|
|
0
|
2997
|
|
|
2998 @end table
|
|
|
2999
|
|
|
3000
|
|
|
3001 @node The Summary Buffer
|
|
|
3002 @chapter The Summary Buffer
|
|
|
3003 @cindex summary buffer
|
|
|
3004
|
|
|
3005 A line for each article is displayed in the summary buffer. You can
|
|
|
3006 move around, read articles, post articles and reply to articles.
|
|
|
3007
|
|
16
|
3008 The most common way to a summary buffer is to select a group from the
|
|
|
3009 group buffer (@pxref{Selecting a Group}).
|
|
|
3010
|
|
|
3011 You can have as many summary buffers open as you wish.
|
|
|
3012
|
|
0
|
3013 @menu
|
|
|
3014 * Summary Buffer Format:: Deciding how the summary buffer is to look.
|
|
|
3015 * Summary Maneuvering:: Moving around the summary buffer.
|
|
|
3016 * Choosing Articles:: Reading articles.
|
|
|
3017 * Paging the Article:: Scrolling the current article.
|
|
|
3018 * Reply Followup and Post:: Posting articles.
|
|
|
3019 * Canceling and Superseding:: ``Whoops, I shouldn't have called him that.''
|
|
|
3020 * Marking Articles:: Marking articles as read, expirable, etc.
|
|
|
3021 * Limiting:: You can limit the summary buffer.
|
|
|
3022 * Threading:: How threads are made.
|
|
|
3023 * Sorting:: How articles and threads are sorted.
|
|
|
3024 * Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
|
|
|
3025 * Article Caching:: You may store articles in a cache.
|
|
|
3026 * Persistent Articles:: Making articles expiry-resistant.
|
|
|
3027 * Article Backlog:: Having already read articles hang around.
|
|
|
3028 * Saving Articles:: Ways of customizing article saving.
|
|
|
3029 * Decoding Articles:: Gnus can treat series of (uu)encoded articles.
|
|
|
3030 * Article Treatment:: The article buffer can be mangled at will.
|
|
16
|
3031 * Article Commands:: Doing various things with the article buffer.
|
|
0
|
3032 * Summary Sorting:: Sorting the summary buffer in various ways.
|
|
|
3033 * Finding the Parent:: No child support? Get the parent.
|
|
|
3034 * Alternative Approaches:: Reading using non-default summaries.
|
|
|
3035 * Tree Display:: A more visual display of threads.
|
|
|
3036 * Mail Group Commands:: Some commands can only be used in mail groups.
|
|
|
3037 * Various Summary Stuff:: What didn't fit anywhere else.
|
|
|
3038 * Exiting the Summary Buffer:: Returning to the Group buffer.
|
|
16
|
3039 * Crosspost Handling:: How crossposted articles are dealt with.
|
|
|
3040 * Duplicate Suppression:: An alternative when crosspost handling fails.
|
|
0
|
3041 @end menu
|
|
|
3042
|
|
|
3043
|
|
|
3044 @node Summary Buffer Format
|
|
|
3045 @section Summary Buffer Format
|
|
|
3046 @cindex summary buffer format
|
|
|
3047
|
|
|
3048 @menu
|
|
|
3049 * Summary Buffer Lines:: You can specify how summary lines should look.
|
|
|
3050 * Summary Buffer Mode Line:: You can say how the mode line should look.
|
|
|
3051 * Summary Highlighting:: Making the summary buffer all pretty and nice.
|
|
|
3052 @end menu
|
|
|
3053
|
|
|
3054 @findex mail-extract-address-components
|
|
|
3055 @findex gnus-extract-address-components
|
|
|
3056 @vindex gnus-extract-address-components
|
|
|
3057 Gnus will use the value of the @code{gnus-extract-address-components}
|
|
|
3058 variable as a function for getting the name and address parts of a
|
|
|
3059 @code{From} header. Two pre-defined function exist:
|
|
|
3060 @code{gnus-extract-address-components}, which is the default, quite
|
|
|
3061 fast, and too simplistic solution; and
|
|
|
3062 @code{mail-extract-address-components}, which works very nicely, but is
|
|
|
3063 slower. The default function will return the wrong answer in 5% of the
|
|
|
3064 cases. If this is unacceptable to you, use the other function instead.
|
|
|
3065
|
|
|
3066 @vindex gnus-summary-same-subject
|
|
|
3067 @code{gnus-summary-same-subject} is a string indicating that the current
|
|
|
3068 article has the same subject as the previous. This string will be used
|
|
|
3069 with those specs that require it. The default is @samp{}.
|
|
|
3070
|
|
|
3071
|
|
|
3072 @node Summary Buffer Lines
|
|
|
3073 @subsection Summary Buffer Lines
|
|
|
3074
|
|
|
3075 @vindex gnus-summary-line-format
|
|
|
3076 You can change the format of the lines in the summary buffer by changing
|
|
|
3077 the @code{gnus-summary-line-format} variable. It works along the same
|
|
16
|
3078 lines a a normal @code{format} string, with some extensions
|
|
|
3079 (@pxref{Formatting Variables}).
|
|
0
|
3080
|
|
|
3081 The default string is @samp{%U%R%z%I%(%[%4L: %-20,20n%]%) %s\n}.
|
|
|
3082
|
|
|
3083 The following format specification characters are understood:
|
|
|
3084
|
|
|
3085 @table @samp
|
|
|
3086 @item N
|
|
|
3087 Article number.
|
|
|
3088 @item S
|
|
|
3089 Subject string.
|
|
|
3090 @item s
|
|
16
|
3091 Subject if the article is the root or the previous article had a
|
|
|
3092 different subject, @code{gnus-summary-same-subject} otherwise.
|
|
|
3093 (@code{gnus-summary-same-subject} defaults to @samp{}.)
|
|
0
|
3094 @item F
|
|
16
|
3095 Full @code{From} header.
|
|
0
|
3096 @item n
|
|
|
3097 The name (from the @code{From} header).
|
|
|
3098 @item a
|
|
|
3099 The name (from the @code{From} header). This differs from the @code{n}
|
|
16
|
3100 spec in that it uses the function designated by the
|
|
|
3101 @code{gnus-extract-address-components} variable, which is slower, but
|
|
|
3102 may be more thorough.
|
|
0
|
3103 @item A
|
|
|
3104 The address (from the @code{From} header). This works the same way as
|
|
|
3105 the @code{a} spec.
|
|
|
3106 @item L
|
|
|
3107 Number of lines in the article.
|
|
|
3108 @item c
|
|
|
3109 Number of characters in the article.
|
|
|
3110 @item I
|
|
|
3111 Indentation based on thread level (@pxref{Customizing Threading}).
|
|
|
3112 @item T
|
|
|
3113 Nothing if the article is a root and lots of spaces if it isn't (it
|
|
|
3114 pushes everything after it off the screen).
|
|
16
|
3115 @item [
|
|
|
3116 Opening bracket, which is normally @samp{[}, but can also be @samp{<}
|
|
|
3117 for adopted articles (@pxref{Customizing Threading}).
|
|
|
3118 @item ]
|
|
|
3119 Closing bracket, which is normally @samp{]}, but can also be @samp{>}
|
|
0
|
3120 for adopted articles.
|
|
|
3121 @item >
|
|
|
3122 One space for each thread level.
|
|
|
3123 @item <
|
|
|
3124 Twenty minus thread level spaces.
|
|
|
3125 @item U
|
|
|
3126 Unread.
|
|
|
3127 @item R
|
|
|
3128 Replied.
|
|
|
3129 @item i
|
|
|
3130 Score as a number.
|
|
|
3131 @item z
|
|
|
3132 @vindex gnus-summary-zcore-fuzz
|
|
|
3133 Zcore, @samp{+} if above the default level and @samp{-} if below the
|
|
|
3134 default level. If the difference between
|
|
|
3135 @code{gnus-summary-default-level} and the score is less than
|
|
|
3136 @code{gnus-summary-zcore-fuzz}, this spec will not be used.
|
|
|
3137 @item V
|
|
|
3138 Total thread score.
|
|
|
3139 @item x
|
|
|
3140 @code{Xref}.
|
|
|
3141 @item D
|
|
|
3142 @code{Date}.
|
|
16
|
3143 @item d
|
|
|
3144 The @code{Date} in @code{DD-MMM} format.
|
|
|
3145 @item o
|
|
|
3146 The @code{Date} in @code{YYYYMMDDTHHMMSS} format.
|
|
0
|
3147 @item M
|
|
|
3148 @code{Message-ID}.
|
|
|
3149 @item r
|
|
|
3150 @code{References}.
|
|
|
3151 @item t
|
|
|
3152 Number of articles in the current sub-thread. Using this spec will slow
|
|
|
3153 down summary buffer generation somewhat.
|
|
|
3154 @item e
|
|
16
|
3155 An @samp{=} (@code{gnus-not-empty-thread-mark}) will be displayed if the
|
|
|
3156 article has any children.
|
|
|
3157 @item P
|
|
|
3158 The line number.
|
|
0
|
3159 @item u
|
|
|
3160 User defined specifier. The next character in the format string should
|
|
|
3161 be a letter. @sc{gnus} will call the function
|
|
|
3162 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
|
|
|
3163 following @samp{%u}. The function will be passed the current header as
|
|
|
3164 argument. The function should return a string, which will be inserted
|
|
|
3165 into the summary just like information from any other summary specifier.
|
|
|
3166 @end table
|
|
|
3167
|
|
|
3168 The @samp{%U} (status), @samp{%R} (replied) and @samp{%z} (zcore) specs
|
|
|
3169 have to be handled with care. For reasons of efficiency, Gnus will
|
|
|
3170 compute what column these characters will end up in, and ``hard-code''
|
|
|
3171 that. This means that it is illegal to have these specs after a
|
|
|
3172 variable-length spec. Well, you might not be arrested, but your summary
|
|
|
3173 buffer will look strange, which is bad enough.
|
|
|
3174
|
|
|
3175 The smart choice is to have these specs as far to the left as possible.
|
|
|
3176 (Isn't that the case with everything, though? But I digress.)
|
|
|
3177
|
|
|
3178 This restriction may disappear in later versions of Gnus.
|
|
|
3179
|
|
|
3180
|
|
|
3181 @node Summary Buffer Mode Line
|
|
|
3182 @subsection Summary Buffer Mode Line
|
|
|
3183
|
|
|
3184 @vindex gnus-summary-mode-line-format
|
|
|
3185 You can also change the format of the summary mode bar. Set
|
|
16
|
3186 @code{gnus-summary-mode-line-format} to whatever you like. The default
|
|
|
3187 is @samp{Gnus: %%b [%A] %Z}.
|
|
|
3188
|
|
|
3189 Here are the elements you can play with:
|
|
0
|
3190
|
|
|
3191 @table @samp
|
|
|
3192 @item G
|
|
|
3193 Group name.
|
|
|
3194 @item p
|
|
|
3195 Unprefixed group name.
|
|
|
3196 @item A
|
|
|
3197 Current article number.
|
|
|
3198 @item V
|
|
|
3199 Gnus version.
|
|
|
3200 @item U
|
|
|
3201 Number of unread articles in this group.
|
|
|
3202 @item e
|
|
|
3203 Number of unselected articles in this group.
|
|
|
3204 @item Z
|
|
|
3205 A string with the number of unread and unselected articles represented
|
|
16
|
3206 either as @samp{<%U(+%e) more>} if there are both unread and unselected
|
|
0
|
3207 articles, and just as @samp{<%U more>} if there are just unread articles
|
|
|
3208 and no unselected ones.
|
|
|
3209 @item g
|
|
|
3210 Shortish group name. For instance, @samp{rec.arts.anime} will be
|
|
|
3211 shortened to @samp{r.a.anime}.
|
|
|
3212 @item S
|
|
|
3213 Subject of the current article.
|
|
|
3214 @item u
|
|
16
|
3215 User-defined spec.
|
|
0
|
3216 @item s
|
|
|
3217 Name of the current score file.
|
|
|
3218 @item d
|
|
|
3219 Number of dormant articles.
|
|
|
3220 @item t
|
|
|
3221 Number of ticked articles.
|
|
|
3222 @item r
|
|
|
3223 Number of articles that have been marked as read in this session.
|
|
|
3224 @item E
|
|
|
3225 Number of articles expunged by the score files.
|
|
|
3226 @end table
|
|
|
3227
|
|
|
3228
|
|
|
3229 @node Summary Highlighting
|
|
|
3230 @subsection Summary Highlighting
|
|
|
3231
|
|
|
3232 @table @code
|
|
|
3233
|
|
|
3234 @item gnus-visual-mark-article-hook
|
|
|
3235 @vindex gnus-visual-mark-article-hook
|
|
|
3236 This hook is run after selecting an article. It is meant to be used for
|
|
|
3237 highlighting the article in some way. It is not run if
|
|
|
3238 @code{gnus-visual} is @code{nil}.
|
|
|
3239
|
|
|
3240 @item gnus-summary-update-hook
|
|
|
3241 @vindex gnus-summary-update-hook
|
|
|
3242 This hook is called when a summary line is changed. It is not run if
|
|
|
3243 @code{gnus-visual} is @code{nil}.
|
|
|
3244
|
|
|
3245 @item gnus-summary-selected-face
|
|
|
3246 @vindex gnus-summary-selected-face
|
|
|
3247 This is the face (or @dfn{font} as some people call it) that is used to
|
|
|
3248 highlight the current article in the summary buffer.
|
|
|
3249
|
|
|
3250 @item gnus-summary-highlight
|
|
|
3251 @vindex gnus-summary-highlight
|
|
|
3252 Summary lines are highlighted according to this variable, which is a
|
|
16
|
3253 list where the elements are on the format @var{(FORM . FACE)}. If you
|
|
0
|
3254 would, for instance, like ticked articles to be italic and high-scored
|
|
|
3255 articles to be bold, you could set this variable to something like
|
|
|
3256 @lisp
|
|
|
3257 (((eq mark gnus-ticked-mark) . italic)
|
|
|
3258 ((> score default) . bold))
|
|
|
3259 @end lisp
|
|
|
3260 As you may have guessed, if @var{FORM} returns a non-@code{nil} value,
|
|
|
3261 @var{FACE} will be applied to the line.
|
|
|
3262 @end table
|
|
|
3263
|
|
|
3264
|
|
|
3265 @node Summary Maneuvering
|
|
|
3266 @section Summary Maneuvering
|
|
|
3267 @cindex summary movement
|
|
|
3268
|
|
|
3269 All the straight movement commands understand the numeric prefix and
|
|
|
3270 behave pretty much as you'd expect.
|
|
|
3271
|
|
|
3272 None of these commands select articles.
|
|
|
3273
|
|
|
3274 @table @kbd
|
|
|
3275 @item G M-n
|
|
|
3276 @itemx M-n
|
|
|
3277 @kindex M-n (Summary)
|
|
|
3278 @kindex G M-n (Summary)
|
|
|
3279 @findex gnus-summary-next-unread-subject
|
|
|
3280 Go to the next summary line of an unread article
|
|
|
3281 (@code{gnus-summary-next-unread-subject}).
|
|
|
3282
|
|
|
3283 @item G M-p
|
|
|
3284 @itemx M-p
|
|
|
3285 @kindex M-p (Summary)
|
|
|
3286 @kindex G M-p (Summary)
|
|
|
3287 @findex gnus-summary-prev-unread-subject
|
|
|
3288 Go to the previous summary line of an unread article
|
|
|
3289 (@code{gnus-summary-prev-unread-subject}).
|
|
|
3290
|
|
|
3291 @item G j
|
|
|
3292 @itemx j
|
|
|
3293 @kindex j (Summary)
|
|
|
3294 @kindex G j (Summary)
|
|
|
3295 @findex gnus-summary-goto-article
|
|
16
|
3296 Ask for an article number and then go to that article
|
|
0
|
3297 (@code{gnus-summary-goto-article}).
|
|
|
3298
|
|
|
3299 @item G g
|
|
|
3300 @kindex G g (Summary)
|
|
|
3301 @findex gnus-summary-goto-subject
|
|
|
3302 Ask for an article number and then go the summary line of that article
|
|
16
|
3303 without displaying the article (@code{gnus-summary-goto-subject}).
|
|
0
|
3304 @end table
|
|
|
3305
|
|
|
3306 If Gnus asks you to press a key to confirm going to the next group, you
|
|
|
3307 can use the @kbd{C-n} and @kbd{C-p} keys to move around the group
|
|
|
3308 buffer, searching for the next group to read without actually returning
|
|
|
3309 to the group buffer.
|
|
|
3310
|
|
|
3311 Variables related to summary movement:
|
|
|
3312
|
|
|
3313 @table @code
|
|
|
3314
|
|
|
3315 @vindex gnus-auto-select-next
|
|
|
3316 @item gnus-auto-select-next
|
|
16
|
3317 If you issue one of the movement commands (like @kbd{n}) and there are
|
|
|
3318 no more unread articles after the current one, Gnus will offer to go to
|
|
|
3319 the next group. If this variable is @code{t} and the next group is
|
|
|
3320 empty, Gnus will exit summary mode and return to the group buffer. If
|
|
|
3321 this variable is neither @code{t} nor @code{nil}, Gnus will select the
|
|
|
3322 next group, no matter whether it has any unread articles or not. As a
|
|
|
3323 special case, if this variable is @code{quietly}, Gnus will select the
|
|
|
3324 next group without asking for confirmation. If this variable is
|
|
|
3325 @code{almost-quietly}, the same will happen only if you are located on
|
|
|
3326 the last article in the group. Finally, if this variable is
|
|
|
3327 @code{slightly-quietly}, the @kbd{Z n} command will go to the next group
|
|
|
3328 without confirmation. Also @pxref{Group Levels}.
|
|
0
|
3329
|
|
|
3330 @item gnus-auto-select-same
|
|
|
3331 @vindex gnus-auto-select-same
|
|
|
3332 If non-@code{nil}, all the movement commands will try to go to the next
|
|
2
|
3333 article with the same subject as the current. (@dfn{Same} here might
|
|
|
3334 mean @dfn{roughly equal}. See @code{gnus-summary-gather-subject-limit}
|
|
|
3335 for details (@pxref{Customizing Threading}).) This variable is not
|
|
0
|
3336 particularly useful if you use a threaded display.
|
|
|
3337
|
|
|
3338 @item gnus-summary-check-current
|
|
|
3339 @vindex gnus-summary-check-current
|
|
|
3340 If non-@code{nil}, all the ``unread'' movement commands will not proceed
|
|
|
3341 to the next (or previous) article if the current article is unread.
|
|
|
3342 Instead, they will choose the current article.
|
|
|
3343
|
|
|
3344 @item gnus-auto-center-summary
|
|
|
3345 @vindex gnus-auto-center-summary
|
|
|
3346 If non-@code{nil}, Gnus will keep the point in the summary buffer
|
|
|
3347 centered at all times. This makes things quite tidy, but if you have a
|
|
|
3348 slow network connection, or simply do not like this un-Emacsism, you can
|
|
|
3349 set this variable to @code{nil} to get the normal Emacs scrolling
|
|
|
3350 action. This will also inhibit horizontal re-centering of the summary
|
|
|
3351 buffer, which might make it more inconvenient to read extremely long
|
|
|
3352 threads.
|
|
|
3353
|
|
|
3354 @end table
|
|
|
3355
|
|
|
3356
|
|
|
3357 @node Choosing Articles
|
|
|
3358 @section Choosing Articles
|
|
|
3359 @cindex selecting articles
|
|
|
3360
|
|
16
|
3361 @menu
|
|
|
3362 * Choosing Commands:: Commands for choosing articles.
|
|
|
3363 * Choosing Variables:: Variables that influence these commands.
|
|
|
3364 @end menu
|
|
|
3365
|
|
|
3366
|
|
|
3367 @node Choosing Commands
|
|
|
3368 @subsection Choosing Commands
|
|
|
3369
|
|
0
|
3370 None of the following movement commands understand the numeric prefix,
|
|
|
3371 and they all select and display an article.
|
|
|
3372
|
|
|
3373 @table @kbd
|
|
|
3374 @item SPACE
|
|
|
3375 @kindex SPACE (Summary)
|
|
|
3376 @findex gnus-summary-next-page
|
|
|
3377 Select the current article, or, if that one's read already, the next
|
|
|
3378 unread article (@code{gnus-summary-next-page}).
|
|
|
3379
|
|
|
3380 @item G n
|
|
|
3381 @itemx n
|
|
|
3382 @kindex n (Summary)
|
|
|
3383 @kindex G n (Summary)
|
|
|
3384 @findex gnus-summary-next-unread-article
|
|
|
3385 Go to next unread article (@code{gnus-summary-next-unread-article}).
|
|
|
3386
|
|
|
3387 @item G p
|
|
|
3388 @itemx p
|
|
|
3389 @kindex p (Summary)
|
|
|
3390 @findex gnus-summary-prev-unread-article
|
|
|
3391 Go to previous unread article (@code{gnus-summary-prev-unread-article}).
|
|
|
3392
|
|
|
3393 @item G N
|
|
|
3394 @itemx N
|
|
|
3395 @kindex N (Summary)
|
|
|
3396 @kindex G N (Summary)
|
|
|
3397 @findex gnus-summary-next-article
|
|
|
3398 Go to the next article (@code{gnus-summary-next-article}).
|
|
|
3399
|
|
|
3400 @item G P
|
|
|
3401 @itemx P
|
|
|
3402 @kindex P (Summary)
|
|
|
3403 @kindex G P (Summary)
|
|
|
3404 @findex gnus-summary-prev-article
|
|
|
3405 Go to the previous article (@code{gnus-summary-prev-article}).
|
|
|
3406
|
|
|
3407 @item G C-n
|
|
|
3408 @kindex G C-n (Summary)
|
|
|
3409 @findex gnus-summary-next-same-subject
|
|
|
3410 Go to the next article with the same subject
|
|
|
3411 (@code{gnus-summary-next-same-subject}).
|
|
|
3412
|
|
|
3413 @item G C-p
|
|
|
3414 @kindex G C-p (Summary)
|
|
|
3415 @findex gnus-summary-prev-same-subject
|
|
|
3416 Go to the previous article with the same subject
|
|
|
3417 (@code{gnus-summary-prev-same-subject}).
|
|
|
3418
|
|
|
3419 @item G f
|
|
|
3420 @itemx .
|
|
|
3421 @kindex G f (Summary)
|
|
|
3422 @kindex . (Summary)
|
|
|
3423 @findex gnus-summary-first-unread-article
|
|
|
3424 Go to the first unread article
|
|
|
3425 (@code{gnus-summary-first-unread-article}).
|
|
|
3426
|
|
|
3427 @item G b
|
|
|
3428 @itemx ,
|
|
|
3429 @kindex G b (Summary)
|
|
|
3430 @kindex , (Summary)
|
|
|
3431 @findex gnus-summary-best-unread-article
|
|
|
3432 Go to the article with the highest score
|
|
|
3433 (@code{gnus-summary-best-unread-article}).
|
|
|
3434
|
|
|
3435 @item G l
|
|
|
3436 @itemx l
|
|
|
3437 @kindex l (Summary)
|
|
|
3438 @kindex G l (Summary)
|
|
|
3439 @findex gnus-summary-goto-last-article
|
|
|
3440 Go to the previous article read (@code{gnus-summary-goto-last-article}).
|
|
|
3441
|
|
|
3442 @item G p
|
|
|
3443 @kindex G p (Summary)
|
|
|
3444 @findex gnus-summary-pop-article
|
|
|
3445 Pop an article off the summary history and go to this article
|
|
|
3446 (@code{gnus-summary-pop-article}). This command differs from the
|
|
|
3447 command above in that you can pop as many previous articles off the
|
|
|
3448 history as you like.
|
|
|
3449 @end table
|
|
|
3450
|
|
16
|
3451
|
|
|
3452 @node Choosing Variables
|
|
|
3453 @subsection Choosing Variables
|
|
|
3454
|
|
0
|
3455 Some variables that are relevant for moving and selecting articles:
|
|
|
3456
|
|
|
3457 @table @code
|
|
|
3458 @item gnus-auto-extend-newsgroup
|
|
|
3459 @vindex gnus-auto-extend-newsgroup
|
|
|
3460 All the movement commands will try to go to the previous (or next)
|
|
|
3461 article, even if that article isn't displayed in the Summary buffer if
|
|
|
3462 this variable is non-@code{nil}. Gnus will then fetch the article from
|
|
|
3463 the server and display it in the article buffer.
|
|
|
3464
|
|
|
3465 @item gnus-select-article-hook
|
|
|
3466 @vindex gnus-select-article-hook
|
|
|
3467 This hook is called whenever an article is selected. By default it
|
|
|
3468 exposes any threads hidden under the selected article.
|
|
|
3469
|
|
|
3470 @item gnus-mark-article-hook
|
|
|
3471 @vindex gnus-mark-article-hook
|
|
|
3472 @findex gnus-summary-mark-unread-as-read
|
|
|
3473 @findex gnus-summary-mark-read-and-unread-as-read
|
|
|
3474 @findex gnus-unread-mark
|
|
|
3475 This hook is called whenever an article is selected. It is intended to
|
|
|
3476 be used for marking articles as read. The default value is
|
|
|
3477 @code{gnus-summary-mark-read-and-unread-as-read}, and will change the
|
|
|
3478 mark of almost any article you read to @code{gnus-unread-mark}. The
|
|
|
3479 only articles not affected by this function are ticked, dormant, and
|
|
|
3480 expirable articles. If you'd instead like to just have unread articles
|
|
|
3481 marked as read, you can use @code{gnus-summary-mark-unread-as-read}
|
|
|
3482 instead. It will leave marks like @code{gnus-low-score-mark},
|
|
|
3483 @code{gnus-del-mark} (and so on) alone.
|
|
|
3484
|
|
|
3485 @end table
|
|
|
3486
|
|
|
3487
|
|
|
3488 @node Paging the Article
|
|
|
3489 @section Scrolling the Article
|
|
|
3490 @cindex article scrolling
|
|
|
3491
|
|
|
3492 @table @kbd
|
|
|
3493
|
|
|
3494 @item SPACE
|
|
|
3495 @kindex SPACE (Summary)
|
|
|
3496 @findex gnus-summary-next-page
|
|
|
3497 Pressing @kbd{SPACE} will scroll the current article forward one page,
|
|
|
3498 or, if you have come to the end of the current article, will choose the
|
|
|
3499 next article (@code{gnus-summary-next-page}).
|
|
|
3500
|
|
|
3501 @item DEL
|
|
|
3502 @kindex DEL (Summary)
|
|
|
3503 @findex gnus-summary-prev-page
|
|
|
3504 Scroll the current article back one page (@code{gnus-summary-prev-page}).
|
|
|
3505
|
|
|
3506 @item RET
|
|
|
3507 @kindex RET (Summary)
|
|
|
3508 @findex gnus-summary-scroll-up
|
|
|
3509 Scroll the current article one line forward
|
|
|
3510 (@code{gnus-summary-scroll-up}).
|
|
|
3511
|
|
|
3512 @item A g
|
|
|
3513 @itemx g
|
|
|
3514 @kindex A g (Summary)
|
|
|
3515 @kindex g (Summary)
|
|
|
3516 @findex gnus-summary-show-article
|
|
|
3517 (Re)fetch the current article (@code{gnus-summary-show-article}). If
|
|
|
3518 given a prefix, fetch the current article, but don't run any of the
|
|
|
3519 article treatment functions. This will give you a ``raw'' article, just
|
|
|
3520 the way it came from the server.
|
|
|
3521
|
|
|
3522 @item A <
|
|
|
3523 @itemx <
|
|
|
3524 @kindex < (Summary)
|
|
|
3525 @kindex A < (Summary)
|
|
|
3526 @findex gnus-summary-beginning-of-article
|
|
|
3527 Scroll to the beginning of the article
|
|
|
3528 (@code{gnus-summary-beginning-of-article}).
|
|
|
3529
|
|
|
3530 @item A >
|
|
|
3531 @itemx >
|
|
|
3532 @kindex > (Summary)
|
|
|
3533 @kindex A > (Summary)
|
|
|
3534 @findex gnus-summary-end-of-article
|
|
|
3535 Scroll to the end of the article (@code{gnus-summary-end-of-article}).
|
|
|
3536
|
|
|
3537 @item A s
|
|
16
|
3538 @itemx s
|
|
0
|
3539 @kindex A s (Summary)
|
|
16
|
3540 @kindex s (Summary)
|
|
0
|
3541 @findex gnus-summary-isearch-article
|
|
|
3542 Perform an isearch in the article buffer
|
|
|
3543 (@code{gnus-summary-isearch-article}).
|
|
|
3544
|
|
|
3545 @end table
|
|
|
3546
|
|
|
3547
|
|
|
3548 @node Reply Followup and Post
|
|
|
3549 @section Reply, Followup and Post
|
|
|
3550
|
|
|
3551 @menu
|
|
|
3552 * Summary Mail Commands:: Sending mail.
|
|
|
3553 * Summary Post Commands:: Sending news.
|
|
|
3554 @end menu
|
|
|
3555
|
|
|
3556
|
|
|
3557 @node Summary Mail Commands
|
|
|
3558 @subsection Summary Mail Commands
|
|
|
3559 @cindex mail
|
|
|
3560 @cindex composing mail
|
|
|
3561
|
|
|
3562 Commands for composing a mail message:
|
|
|
3563
|
|
|
3564 @table @kbd
|
|
|
3565
|
|
|
3566 @item S r
|
|
|
3567 @itemx r
|
|
|
3568 @kindex S r (Summary)
|
|
|
3569 @kindex r (Summary)
|
|
|
3570 @findex gnus-summary-reply
|
|
|
3571 Mail a reply to the author of the current article
|
|
|
3572 (@code{gnus-summary-reply}).
|
|
|
3573
|
|
|
3574 @item S R
|
|
|
3575 @itemx R
|
|
|
3576 @kindex R (Summary)
|
|
|
3577 @kindex S R (Summary)
|
|
|
3578 @findex gnus-summary-reply-with-original
|
|
|
3579 Mail a reply to the author of the current article and include the
|
|
|
3580 original message (@code{gnus-summary-reply-with-original}). This
|
|
|
3581 command uses the process/prefix convention.
|
|
|
3582
|
|
16
|
3583 @item S w
|
|
|
3584 @kindex S w (Summary)
|
|
|
3585 @findex gnus-summary-wide-reply
|
|
|
3586 Mail a wide reply to the author of the current article
|
|
|
3587 (@code{gnus-summary-wide-reply}).
|
|
|
3588
|
|
|
3589 @item S W
|
|
|
3590 @kindex S W (Summary)
|
|
|
3591 @findex gnus-summary-wide-reply-with-original
|
|
|
3592 Mail a wide reply to the current article and include the original
|
|
|
3593 message (@code{gnus-summary-reply-with-original}). This command uses
|
|
|
3594 the process/prefix convention.
|
|
|
3595
|
|
0
|
3596 @item S o m
|
|
|
3597 @kindex S o m (Summary)
|
|
|
3598 @findex gnus-summary-mail-forward
|
|
|
3599 Forward the current article to some other person
|
|
16
|
3600 (@code{gnus-summary-mail-forward}). If given a prefix, include the full
|
|
|
3601 headers of the forwarded article.
|
|
0
|
3602
|
|
|
3603 @item S m
|
|
|
3604 @itemx m
|
|
|
3605 @kindex m (Summary)
|
|
|
3606 @kindex S m (Summary)
|
|
|
3607 @findex gnus-summary-mail-other-window
|
|
|
3608 Send a mail to some other person
|
|
|
3609 (@code{gnus-summary-mail-other-window}).
|
|
|
3610
|
|
|
3611 @item S D b
|
|
|
3612 @kindex S D b (Summary)
|
|
|
3613 @findex gnus-summary-resend-bounced-mail
|
|
|
3614 @cindex bouncing mail
|
|
|
3615 If you have sent a mail, but the mail was bounced back to you for some
|
|
|
3616 reason (wrong address, transient failure), you can use this command to
|
|
|
3617 resend that bounced mail (@code{gnus-summary-resend-bounced-mail}). You
|
|
|
3618 will be popped into a mail buffer where you can edit the headers before
|
|
|
3619 sending the mail off again. If you give a prefix to this command, and
|
|
|
3620 the bounced mail is a reply to some other mail, Gnus will try to fetch
|
|
|
3621 that mail and display it for easy perusal of its headers. This might
|
|
|
3622 very well fail, though.
|
|
|
3623
|
|
|
3624 @item S D r
|
|
|
3625 @kindex S D r (Summary)
|
|
|
3626 @findex gnus-summary-resend-message
|
|
|
3627 Not to be confused with the previous command,
|
|
|
3628 @code{gnus-summary-resend-message} will prompt you for an address to
|
|
|
3629 send the current message off to, and then send it to that place. The
|
|
|
3630 headers of the message won't be altered---but lots of headers that say
|
|
|
3631 @code{Resent-To}, @code{Resent-From} and so on will be added. This
|
|
|
3632 means that you actually send a mail to someone that has a @code{To}
|
|
|
3633 header that (probably) points to yourself. This will confuse people.
|
|
|
3634 So, natcherly you'll only do that if you're really eVIl.
|
|
|
3635
|
|
|
3636 This command is mainly used if you have several accounts and want to
|
|
|
3637 ship a mail to a different account of yours. (If you're both
|
|
|
3638 @code{root} and @code{postmaster} and get a mail for @code{postmaster}
|
|
|
3639 to the @code{root} account, you may want to resend it to
|
|
16
|
3640 @code{postmaster}. Ordnung muß sein!
|
|
|
3641
|
|
|
3642 This command understands the process/prefix convention
|
|
|
3643 (@pxref{Process/Prefix}).
|
|
0
|
3644
|
|
|
3645 @item S O m
|
|
|
3646 @kindex S O m (Summary)
|
|
|
3647 @findex gnus-uu-digest-mail-forward
|
|
|
3648 Digest the current series and forward the result using mail
|
|
|
3649 (@code{gnus-uu-digest-mail-forward}). This command uses the
|
|
|
3650 process/prefix convention (@pxref{Process/Prefix}).
|
|
|
3651
|
|
16
|
3652 @item S M-c
|
|
|
3653 @kindex S M-c (Summary)
|
|
|
3654 @findex gnus-summary-mail-crosspost-complaint
|
|
|
3655 @cindex crossposting
|
|
|
3656 @cindex excessive crossposting
|
|
|
3657 Send a complaint about excessive crossposting to the author of the
|
|
|
3658 current article (@code{gnus-summary-mail-crosspost-complaint}).
|
|
|
3659
|
|
|
3660 @findex gnus-crosspost-complaint
|
|
|
3661 This command is provided as a way to fight back agains the current
|
|
|
3662 crossposting pandemic that's sweeping Usenet. It will compose a reply
|
|
|
3663 using the @code{gnus-crosspost-complaint} variable as a preamble. This
|
|
|
3664 command understands the process/prefix convention
|
|
|
3665 (@pxref{Process/Prefix}) and will prompt you before sending each mail.
|
|
|
3666
|
|
0
|
3667 @end table
|
|
|
3668
|
|
|
3669
|
|
|
3670 @node Summary Post Commands
|
|
|
3671 @subsection Summary Post Commands
|
|
|
3672 @cindex post
|
|
|
3673 @cindex composing news
|
|
|
3674
|
|
16
|
3675 Commands for posting a news article:
|
|
0
|
3676
|
|
|
3677 @table @kbd
|
|
|
3678 @item S p
|
|
|
3679 @itemx a
|
|
|
3680 @kindex a (Summary)
|
|
|
3681 @kindex S p (Summary)
|
|
|
3682 @findex gnus-summary-post-news
|
|
|
3683 Post an article to the current group
|
|
|
3684 (@code{gnus-summary-post-news}).
|
|
|
3685
|
|
|
3686 @item S f
|
|
|
3687 @itemx f
|
|
|
3688 @kindex f (Summary)
|
|
|
3689 @kindex S f (Summary)
|
|
|
3690 @findex gnus-summary-followup
|
|
|
3691 Post a followup to the current article (@code{gnus-summary-followup}).
|
|
|
3692
|
|
|
3693 @item S F
|
|
|
3694 @itemx F
|
|
|
3695 @kindex S F (Summary)
|
|
|
3696 @kindex F (Summary)
|
|
|
3697 @findex gnus-summary-followup-with-original
|
|
|
3698 Post a followup to the current article and include the original message
|
|
|
3699 (@code{gnus-summary-followup-with-original}). This command uses the
|
|
|
3700 process/prefix convention.
|
|
|
3701
|
|
16
|
3702 @item S n
|
|
|
3703 @kindex S n (Summary)
|
|
|
3704 @findex gnus-summary-followup-to-mail
|
|
|
3705 Post a followup to the current article via news, even if you got the
|
|
|
3706 message through mail (@code{gnus-summary-followup-to-mail}).
|
|
|
3707
|
|
|
3708 @item S n
|
|
|
3709 @kindex S n (Summary)
|
|
|
3710 @findex gnus-summary-followup-to-mail
|
|
|
3711 Post a followup to the current article via news, even if you got the
|
|
|
3712 message through mail and include the original message
|
|
|
3713 (@code{gnus-summary-followup-to-mail-with-original}). This command uses
|
|
|
3714 the process/prefix convention.
|
|
|
3715
|
|
|
3716 @item S o p
|
|
|
3717 @kindex S o p (Summary)
|
|
|
3718 @findex gnus-summary-post-forward
|
|
|
3719 Forward the current article to a newsgroup
|
|
|
3720 (@code{gnus-summary-post-forward}). If given a prefix, include the full
|
|
|
3721 headers of the forwarded article.
|
|
|
3722
|
|
|
3723 @item S O p
|
|
|
3724 @kindex S O p (Summary)
|
|
|
3725 @findex gnus-uu-digest-post-forward
|
|
|
3726 Digest the current series and forward the result to a newsgroup
|
|
|
3727 (@code{gnus-uu-digest-mail-forward}).
|
|
|
3728
|
|
0
|
3729 @item S u
|
|
|
3730 @kindex S u (Summary)
|
|
|
3731 @findex gnus-uu-post-news
|
|
|
3732 Uuencode a file, split it into parts, and post it as a series
|
|
|
3733 (@code{gnus-uu-post-news}). (@pxref{Uuencoding and Posting}).
|
|
|
3734 @end table
|
|
|
3735
|
|
|
3736
|
|
|
3737 @node Canceling and Superseding
|
|
|
3738 @section Canceling Articles
|
|
|
3739 @cindex canceling articles
|
|
|
3740 @cindex superseding articles
|
|
|
3741
|
|
|
3742 Have you ever written something, and then decided that you really,
|
|
|
3743 really, really wish you hadn't posted that?
|
|
|
3744
|
|
|
3745 Well, you can't cancel mail, but you can cancel posts.
|
|
|
3746
|
|
|
3747 @findex gnus-summary-cancel-article
|
|
|
3748 @kindex C (Summary)
|
|
|
3749 Find the article you wish to cancel (you can only cancel your own
|
|
|
3750 articles, so don't try any funny stuff). Then press @kbd{C} or @kbd{S
|
|
|
3751 c} (@code{gnus-summary-cancel-article}). Your article will be
|
|
|
3752 canceled---machines all over the world will be deleting your article.
|
|
|
3753
|
|
|
3754 Be aware, however, that not all sites honor cancels, so your article may
|
|
|
3755 live on here and there, while most sites will delete the article in
|
|
|
3756 question.
|
|
|
3757
|
|
|
3758 If you discover that you have made some mistakes and want to do some
|
|
|
3759 corrections, you can post a @dfn{superseding} article that will replace
|
|
|
3760 your original article.
|
|
|
3761
|
|
|
3762 @findex gnus-summary-supersede-article
|
|
|
3763 @kindex S (Summary)
|
|
|
3764 Go to the original article and press @kbd{S s}
|
|
|
3765 (@code{gnus-summary-supersede-article}). You will be put in a buffer
|
|
|
3766 where you can edit the article all you want before sending it off the
|
|
|
3767 usual way.
|
|
|
3768
|
|
|
3769 The same goes for superseding as for canceling, only more so: Some
|
|
|
3770 sites do not honor superseding. On those sites, it will appear that you
|
|
|
3771 have posted almost the same article twice.
|
|
|
3772
|
|
|
3773 If you have just posted the article, and change your mind right away,
|
|
|
3774 there is a trick you can use to cancel/supersede the article without
|
|
|
3775 waiting for the article to appear on your site first. You simply return
|
|
16
|
3776 to the post buffer (which is called @code{*sent ...*}). There you will
|
|
0
|
3777 find the article you just posted, with all the headers intact. Change
|
|
|
3778 the @code{Message-ID} header to a @code{Cancel} or @code{Supersedes}
|
|
16
|
3779 header by substituting one of those words for the word
|
|
|
3780 @code{Message-ID}. Then just press @kbd{C-c C-c} to send the article as
|
|
|
3781 you would do normally. The previous article will be
|
|
|
3782 canceled/superseded.
|
|
0
|
3783
|
|
|
3784 Just remember, kids: There is no 'c' in 'supersede'.
|
|
|
3785
|
|
|
3786
|
|
|
3787 @node Marking Articles
|
|
|
3788 @section Marking Articles
|
|
|
3789 @cindex article marking
|
|
|
3790 @cindex article ticking
|
|
|
3791 @cindex marks
|
|
|
3792
|
|
|
3793 There are several marks you can set on an article.
|
|
|
3794
|
|
|
3795 You have marks that decide the @dfn{readedness} (whoo, neato-keano
|
|
|
3796 neologism ohoy!) of the article. Alphabetic marks generally mean
|
|
|
3797 @dfn{read}, while non-alphabetic characters generally mean @dfn{unread}.
|
|
|
3798
|
|
|
3799 In addition, you also have marks that do not affect readedness.
|
|
|
3800
|
|
|
3801 @menu
|
|
|
3802 * Unread Articles:: Marks for unread articles.
|
|
|
3803 * Read Articles:: Marks for read articles.
|
|
|
3804 * Other Marks:: Marks that do not affect readedness.
|
|
|
3805 @end menu
|
|
|
3806
|
|
|
3807 @ifinfo
|
|
|
3808 There's a plethora of commands for manipulating these marks:
|
|
|
3809 @end ifinfo
|
|
|
3810
|
|
|
3811 @menu
|
|
|
3812 * Setting Marks:: How to set and remove marks.
|
|
|
3813 * Setting Process Marks:: How to mark articles for later processing.
|
|
|
3814 @end menu
|
|
|
3815
|
|
|
3816
|
|
|
3817 @node Unread Articles
|
|
|
3818 @subsection Unread Articles
|
|
|
3819
|
|
16
|
3820 The following marks mark articles as (kinda) unread, in one form or
|
|
|
3821 other.
|
|
|
3822
|
|
0
|
3823 @table @samp
|
|
|
3824 @item !
|
|
16
|
3825 @vindex gnus-ticked-mark
|
|
|
3826 Marked as ticked (@code{gnus-ticked-mark}).
|
|
|
3827
|
|
0
|
3828 @dfn{Ticked articles} are articles that will remain visible always. If
|
|
|
3829 you see an article that you find interesting, or you want to put off
|
|
|
3830 reading it, or replying to it, until sometime later, you'd typically
|
|
|
3831 tick it. However, articles can be expired, so if you want to keep an
|
|
16
|
3832 article forever, you'll have to make it persistent (@pxref{Persistent
|
|
|
3833 Articles}).
|
|
0
|
3834
|
|
|
3835 @item ?
|
|
|
3836 @vindex gnus-dormant-mark
|
|
16
|
3837 Marked as dormant (@code{gnus-dormant-mark}).
|
|
|
3838
|
|
|
3839 @dfn{Dormant articles} will only appear in the summary buffer if there
|
|
|
3840 are followups to it.
|
|
0
|
3841
|
|
|
3842 @item SPACE
|
|
|
3843 @vindex gnus-unread-mark
|
|
16
|
3844 Markes as unread (@code{gnus-unread-mark}).
|
|
|
3845
|
|
|
3846 @dfn{Unread articles} are articles that haven't been read at all yet.
|
|
0
|
3847 @end table
|
|
|
3848
|
|
|
3849
|
|
|
3850 @node Read Articles
|
|
|
3851 @subsection Read Articles
|
|
|
3852 @cindex expirable mark
|
|
|
3853
|
|
|
3854 All the following marks mark articles as read.
|
|
|
3855
|
|
|
3856 @table @samp
|
|
|
3857
|
|
|
3858 @item r
|
|
|
3859 @vindex gnus-del-mark
|
|
16
|
3860 These are articles that the user has marked as read with the @kbd{d}
|
|
|
3861 command manually, more or less (@code{gnus-del-mark}).
|
|
0
|
3862
|
|
|
3863 @item R
|
|
|
3864 @vindex gnus-read-mark
|
|
16
|
3865 Articles that have actually been read (@code{gnus-read-mark}).
|
|
0
|
3866
|
|
|
3867 @item O
|
|
|
3868 @vindex gnus-ancient-mark
|
|
16
|
3869 Articles that were marked as read in previous sessions and are now
|
|
|
3870 @dfn{old} (@code{gnus-ancient-mark}).
|
|
0
|
3871
|
|
|
3872 @item K
|
|
|
3873 @vindex gnus-killed-mark
|
|
|
3874 Marked as killed (@code{gnus-killed-mark}).
|
|
|
3875
|
|
|
3876 @item X
|
|
|
3877 @vindex gnus-kill-file-mark
|
|
|
3878 Marked as killed by kill files (@code{gnus-kill-file-mark}).
|
|
|
3879
|
|
|
3880 @item Y
|
|
|
3881 @vindex gnus-low-score-mark
|
|
|
3882 Marked as read by having a too low score (@code{gnus-low-score-mark}).
|
|
|
3883
|
|
|
3884 @item C
|
|
|
3885 @vindex gnus-catchup-mark
|
|
|
3886 Marked as read by a catchup (@code{gnus-catchup-mark}).
|
|
|
3887
|
|
|
3888 @item G
|
|
|
3889 @vindex gnus-canceled-mark
|
|
|
3890 Canceled article (@code{gnus-canceled-mark})
|
|
|
3891
|
|
|
3892 @item F
|
|
|
3893 @vindex gnus-souped-mark
|
|
16
|
3894 @sc{SOUP}ed article (@code{gnus-souped-mark}). @xref{SOUP}.
|
|
0
|
3895
|
|
|
3896 @item Q
|
|
|
3897 @vindex gnus-sparse-mark
|
|
16
|
3898 Sparsely reffed article (@code{gnus-sparse-mark}). @xref{Customizing
|
|
|
3899 Threading}.
|
|
|
3900
|
|
|
3901 @item M
|
|
|
3902 @vindex gnus-duplicate-mark
|
|
|
3903 Article marked as read by duplicate suppression
|
|
|
3904 (@code{gnus-duplicated-mark}). @xref{Duplicate Suppression}.
|
|
|
3905
|
|
0
|
3906 @end table
|
|
|
3907
|
|
|
3908 All these marks just mean that the article is marked as read, really.
|
|
16
|
3909 They are interpreted differently when doing adaptive scoring, though.
|
|
0
|
3910
|
|
|
3911 One more special mark, though:
|
|
|
3912
|
|
|
3913 @table @samp
|
|
|
3914 @item E
|
|
|
3915 @vindex gnus-expirable-mark
|
|
16
|
3916 Marked as expirable (@code{gnus-expirable-mark}).
|
|
|
3917
|
|
|
3918 Marking articles as @dfn{expirable} (or have them marked as such
|
|
|
3919 automatically) doesn't make much sense in normal groups---a user doesn't
|
|
|
3920 control the expiring of news articles, but in mail groups, for instance,
|
|
|
3921 articles that are marked as @dfn{expirable} can be deleted by Gnus at
|
|
|
3922 any time.
|
|
0
|
3923 @end table
|
|
|
3924
|
|
|
3925
|
|
|
3926 @node Other Marks
|
|
|
3927 @subsection Other Marks
|
|
|
3928 @cindex process mark
|
|
|
3929 @cindex bookmarks
|
|
|
3930
|
|
|
3931 There are some marks that have nothing to do with whether the article is
|
|
|
3932 read or not.
|
|
|
3933
|
|
|
3934 @itemize @bullet
|
|
|
3935
|
|
|
3936 @item
|
|
|
3937 You can set a bookmark in the current article. Say you are reading a
|
|
|
3938 long thesis on cats' urinary tracts, and have to go home for dinner
|
|
|
3939 before you've finished reading the thesis. You can then set a bookmark
|
|
|
3940 in the article, and Gnus will jump to this bookmark the next time it
|
|
16
|
3941 encounters the article. @xref{Setting Marks}
|
|
0
|
3942
|
|
|
3943 @item
|
|
|
3944 @vindex gnus-replied-mark
|
|
|
3945 All articles that you have replied to or made a followup to (i.e., have
|
|
|
3946 answered) will be marked with an @samp{A} in the second column
|
|
|
3947 (@code{gnus-replied-mark}).
|
|
|
3948
|
|
|
3949 @item
|
|
|
3950 @vindex gnus-cached-mark
|
|
|
3951 Articles that are stored in the article cache will be marked with an
|
|
|
3952 @samp{*} in the second column (@code{gnus-cached-mark}).
|
|
|
3953
|
|
|
3954 @item
|
|
|
3955 @vindex gnus-saved-mark
|
|
|
3956 Articles that are ``saved'' (in some manner or other; not necessarily
|
|
|
3957 religiously) are marked with an @samp{S} in the second column
|
|
|
3958 (@code{gnus-saved-mark}.
|
|
|
3959
|
|
|
3960 @item
|
|
|
3961 @vindex gnus-not-empty-thread-mark
|
|
|
3962 @vindex gnus-empty-thread-mark
|
|
|
3963 It the @samp{%e} spec is used, the presence of threads or not will be
|
|
|
3964 marked with @code{gnus-not-empty-thread-mark} and
|
|
|
3965 @code{gnus-empty-thread-mark} in the third column, respectively.
|
|
|
3966
|
|
|
3967 @item
|
|
|
3968 @vindex gnus-process-mark
|
|
|
3969 Finally we have the @dfn{process mark} (@code{gnus-process-mark}. A
|
|
|
3970 variety of commands react to the presence of the process mark. For
|
|
|
3971 instance, @kbd{X u} (@code{gnus-uu-decode-uu}) will uudecode and view
|
|
|
3972 all articles that have been marked with the process mark. Articles
|
|
|
3973 marked with the process mark have a @samp{#} in the second column.
|
|
|
3974
|
|
|
3975 @end itemize
|
|
|
3976
|
|
|
3977 You might have noticed that most of these ``non-readedness'' marks
|
|
|
3978 appear in the second column by default. So if you have a cached, saved,
|
|
|
3979 replied article that you have process-marked, what will that look like?
|
|
|
3980
|
|
|
3981 Nothing much. The precedence rules go as follows: process -> cache ->
|
|
|
3982 replied -> saved. So if the article is in the cache and is replied,
|
|
|
3983 you'll only see the cache mark and not the replied mark.
|
|
|
3984
|
|
|
3985
|
|
|
3986 @node Setting Marks
|
|
|
3987 @subsection Setting Marks
|
|
|
3988 @cindex setting marks
|
|
|
3989
|
|
|
3990 All the marking commands understand the numeric prefix.
|
|
|
3991
|
|
|
3992 @table @kbd
|
|
|
3993 @item M t
|
|
|
3994 @itemx !
|
|
|
3995 @kindex ! (Summary)
|
|
|
3996 @kindex M t (Summary)
|
|
|
3997 @findex gnus-summary-tick-article-forward
|
|
|
3998 Tick the current article (@code{gnus-summary-tick-article-forward}).
|
|
|
3999
|
|
|
4000 @item M ?
|
|
|
4001 @itemx ?
|
|
|
4002 @kindex ? (Summary)
|
|
|
4003 @kindex M ? (Summary)
|
|
|
4004 @findex gnus-summary-mark-as-dormant
|
|
|
4005 Mark the current article as dormant
|
|
|
4006 (@code{gnus-summary-mark-as-dormant}).
|
|
|
4007
|
|
|
4008 @item M d
|
|
|
4009 @itemx d
|
|
|
4010 @kindex M d (Summary)
|
|
|
4011 @kindex d (Summary)
|
|
|
4012 @findex gnus-summary-mark-as-read-forward
|
|
|
4013 Mark the current article as read
|
|
|
4014 (@code{gnus-summary-mark-as-read-forward}).
|
|
|
4015
|
|
16
|
4016 @item D
|
|
|
4017 @kindex D (Summary)
|
|
|
4018 @findex gnus-summary-mark-as-read-backward
|
|
|
4019 Mark the current article as read and move point to the previous line
|
|
|
4020 (@code{gnus-summary-mark-as-read-backward}).
|
|
|
4021
|
|
0
|
4022 @item M k
|
|
|
4023 @itemx k
|
|
|
4024 @kindex k (Summary)
|
|
|
4025 @kindex M k (Summary)
|
|
|
4026 @findex gnus-summary-kill-same-subject-and-select
|
|
|
4027 Mark all articles that have the same subject as the current one as read,
|
|
|
4028 and then select the next unread article
|
|
|
4029 (@code{gnus-summary-kill-same-subject-and-select}).
|
|
|
4030
|
|
|
4031 @item M K
|
|
|
4032 @itemx C-k
|
|
|
4033 @kindex M K (Summary)
|
|
|
4034 @kindex C-k (Summary)
|
|
|
4035 @findex gnus-summary-kill-same-subject
|
|
|
4036 Mark all articles that have the same subject as the current one as read
|
|
|
4037 (@code{gnus-summary-kill-same-subject}).
|
|
|
4038
|
|
|
4039 @item M C
|
|
|
4040 @kindex M C (Summary)
|
|
|
4041 @findex gnus-summary-catchup
|
|
16
|
4042 Mark all unread articles as read (@code{gnus-summary-catchup}).
|
|
0
|
4043
|
|
|
4044 @item M C-c
|
|
|
4045 @kindex M C-c (Summary)
|
|
|
4046 @findex gnus-summary-catchup-all
|
|
|
4047 Mark all articles in the group as read---even the ticked and dormant
|
|
|
4048 articles (@code{gnus-summary-catchup-all}).
|
|
|
4049
|
|
|
4050 @item M H
|
|
|
4051 @kindex M H (Summary)
|
|
|
4052 @findex gnus-summary-catchup-to-here
|
|
|
4053 Catchup the current group to point
|
|
|
4054 (@code{gnus-summary-catchup-to-here}).
|
|
|
4055
|
|
|
4056 @item C-w
|
|
|
4057 @kindex C-w (Summary)
|
|
|
4058 @findex gnus-summary-mark-region-as-read
|
|
|
4059 Mark all articles between point and mark as read
|
|
|
4060 (@code{gnus-summary-mark-region-as-read}).
|
|
|
4061
|
|
|
4062 @item M V k
|
|
|
4063 @kindex M V k (Summary)
|
|
|
4064 @findex gnus-summary-kill-below
|
|
|
4065 Kill all articles with scores below the default score (or below the
|
|
|
4066 numeric prefix) (@code{gnus-summary-kill-below}).
|
|
|
4067
|
|
|
4068 @item M c
|
|
|
4069 @itemx M-u
|
|
|
4070 @kindex M c (Summary)
|
|
|
4071 @kindex M-u (Summary)
|
|
|
4072 @findex gnus-summary-clear-mark-forward
|
|
|
4073 Clear all readedness-marks from the current article
|
|
|
4074 (@code{gnus-summary-clear-mark-forward}).
|
|
|
4075
|
|
|
4076 @item M e
|
|
|
4077 @itemx E
|
|
|
4078 @kindex M e (Summary)
|
|
|
4079 @kindex E (Summary)
|
|
|
4080 @findex gnus-summary-mark-as-expirable
|
|
|
4081 Mark the current article as expirable
|
|
|
4082 (@code{gnus-summary-mark-as-expirable}).
|
|
|
4083
|
|
|
4084 @item M b
|
|
|
4085 @kindex M b (Summary)
|
|
|
4086 @findex gnus-summary-set-bookmark
|
|
|
4087 Set a bookmark in the current article
|
|
|
4088 (@code{gnus-summary-set-bookmark}).
|
|
|
4089
|
|
|
4090 @item M B
|
|
|
4091 @kindex M B (Summary)
|
|
|
4092 @findex gnus-summary-remove-bookmark
|
|
|
4093 Remove the bookmark from the current article
|
|
|
4094 (@code{gnus-summary-remove-bookmark}).
|
|
|
4095
|
|
|
4096 @item M V c
|
|
|
4097 @kindex M V c (Summary)
|
|
|
4098 @findex gnus-summary-clear-above
|
|
|
4099 Clear all marks from articles with scores over the default score (or
|
|
|
4100 over the numeric prefix) (@code{gnus-summary-clear-above}).
|
|
|
4101
|
|
|
4102 @item M V u
|
|
|
4103 @kindex M V u (Summary)
|
|
|
4104 @findex gnus-summary-tick-above
|
|
|
4105 Tick all articles with scores over the default score (or over the
|
|
|
4106 numeric prefix) (@code{gnus-summary-tick-above}).
|
|
|
4107
|
|
|
4108 @item M V m
|
|
|
4109 @kindex M V m (Summary)
|
|
|
4110 @findex gnus-summary-mark-above
|
|
|
4111 Prompt for a mark, and mark all articles with scores over the default
|
|
|
4112 score (or over the numeric prefix) with this mark
|
|
|
4113 (@code{gnus-summary-clear-above}).
|
|
|
4114 @end table
|
|
|
4115
|
|
|
4116 @vindex gnus-summary-goto-unread
|
|
|
4117 The @code{gnus-summary-goto-unread} variable controls what action should
|
|
|
4118 be taken after setting a mark. If non-@code{nil}, point will move to
|
|
|
4119 the next/previous unread article. If @code{nil}, point will just move
|
|
|
4120 one line up or down. As a special case, if this variable is
|
|
|
4121 @code{never}, all the marking commands as well as other commands (like
|
|
|
4122 @kbd{SPACE}) will move to the next article, whether it is unread or not.
|
|
|
4123 The default is @code{t}.
|
|
|
4124
|
|
|
4125
|
|
|
4126 @node Setting Process Marks
|
|
|
4127 @subsection Setting Process Marks
|
|
|
4128 @cindex setting process marks
|
|
|
4129
|
|
|
4130 @table @kbd
|
|
|
4131
|
|
|
4132 @item M P p
|
|
|
4133 @itemx #
|
|
|
4134 @kindex # (Summary)
|
|
|
4135 @kindex M P p (Summary)
|
|
|
4136 @findex gnus-summary-mark-as-processable
|
|
|
4137 Mark the current article with the process mark
|
|
|
4138 (@code{gnus-summary-mark-as-processable}).
|
|
|
4139 @findex gnus-summary-unmark-as-processable
|
|
|
4140
|
|
|
4141 @item M P u
|
|
|
4142 @itemx M-#
|
|
|
4143 @kindex M P u (Summary)
|
|
|
4144 @kindex M-# (Summary)
|
|
|
4145 Remove the process mark, if any, from the current article
|
|
|
4146 (@code{gnus-summary-unmark-as-processable}).
|
|
|
4147
|
|
|
4148 @item M P U
|
|
|
4149 @kindex M P U (Summary)
|
|
|
4150 @findex gnus-summary-unmark-all-processable
|
|
|
4151 Remove the process mark from all articles
|
|
|
4152 (@code{gnus-summary-unmark-all-processable}).
|
|
|
4153
|
|
16
|
4154 @item M P i
|
|
|
4155 @kindex M P i (Summary)
|
|
|
4156 @findex gnus-uu-invert-processable
|
|
|
4157 Invert the list of process marked articles
|
|
|
4158 (@code{gnus-uu-invert-processable}).
|
|
|
4159
|
|
0
|
4160 @item M P R
|
|
|
4161 @kindex M P R (Summary)
|
|
|
4162 @findex gnus-uu-mark-by-regexp
|
|
|
4163 Mark articles by a regular expression (@code{gnus-uu-mark-by-regexp}).
|
|
|
4164
|
|
|
4165 @item M P r
|
|
|
4166 @kindex M P r (Summary)
|
|
|
4167 @findex gnus-uu-mark-region
|
|
|
4168 Mark articles in region (@code{gnus-uu-mark-region}).
|
|
|
4169
|
|
|
4170 @item M P t
|
|
|
4171 @kindex M P t (Summary)
|
|
|
4172 @findex gnus-uu-mark-thread
|
|
|
4173 Mark all articles in the current (sub)thread
|
|
|
4174 (@code{gnus-uu-mark-thread}).
|
|
|
4175
|
|
|
4176 @item M P T
|
|
|
4177 @kindex M P T (Summary)
|
|
|
4178 @findex gnus-uu-unmark-thread
|
|
|
4179 Unmark all articles in the current (sub)thread
|
|
|
4180 (@code{gnus-uu-unmark-thread}).
|
|
|
4181
|
|
|
4182 @item M P v
|
|
|
4183 @kindex M P v (Summary)
|
|
|
4184 @findex gnus-uu-mark-over
|
|
|
4185 Mark all articles that have a score above the prefix argument
|
|
|
4186 (@code{gnus-uu-mark-over}).
|
|
|
4187
|
|
|
4188 @item M P s
|
|
|
4189 @kindex M P s (Summary)
|
|
|
4190 @findex gnus-uu-mark-series
|
|
|
4191 Mark all articles in the current series (@code{gnus-uu-mark-series}).
|
|
|
4192
|
|
|
4193 @item M P S
|
|
|
4194 @kindex M P S (Summary)
|
|
|
4195 @findex gnus-uu-mark-sparse
|
|
|
4196 Mark all series that have already had some articles marked
|
|
|
4197 (@code{gnus-uu-mark-sparse}).
|
|
|
4198
|
|
|
4199 @item M P a
|
|
|
4200 @kindex M P a (Summary)
|
|
|
4201 @findex gnus-uu-mark-all
|
|
|
4202 Mark all articles in series order (@code{gnus-uu-mark-series}).
|
|
|
4203
|
|
|
4204 @item M P b
|
|
|
4205 @kindex M P b (Summary)
|
|
|
4206 @findex gnus-uu-mark-buffer
|
|
|
4207 Mark all articles in the buffer in the order they appear
|
|
|
4208 (@code{gnus-uu-mark-buffer}).
|
|
16
|
4209
|
|
|
4210 @item M P k
|
|
|
4211 @kindex M P k (Summary)
|
|
|
4212 @findex gnus-summary-kill-process-mark
|
|
|
4213 Push the current process mark set onto the stack and unmark all articles
|
|
|
4214 (@code{gnus-summary-kill-process-mark}).
|
|
|
4215
|
|
|
4216 @item M P y
|
|
|
4217 @kindex M P y (Summary)
|
|
|
4218 @findex gnus-summary-yank-process-mark
|
|
|
4219 Pop the previous process mark set from the stack and restore it
|
|
|
4220 (@code{gnus-summary-yank-process-mark}).
|
|
|
4221
|
|
|
4222 @item M P w
|
|
|
4223 @kindex M P w (Summary)
|
|
|
4224 @findex gnus-summary-save-process-mark
|
|
|
4225 Push the current process mark set onto the stack
|
|
|
4226 (@code{gnus-summary-save-process-mark}).
|
|
|
4227
|
|
0
|
4228 @end table
|
|
|
4229
|
|
|
4230
|
|
|
4231 @node Limiting
|
|
|
4232 @section Limiting
|
|
|
4233 @cindex limiting
|
|
|
4234
|
|
|
4235 It can be convenient to limit the summary buffer to just show some
|
|
|
4236 subset of the articles currently in the group. The effect most limit
|
|
|
4237 commands have is to remove a few (or many) articles from the summary
|
|
|
4238 buffer.
|
|
|
4239
|
|
|
4240 @table @kbd
|
|
|
4241
|
|
|
4242 @item / /
|
|
|
4243 @itemx / s
|
|
|
4244 @kindex / / (Summary)
|
|
|
4245 @findex gnus-summary-limit-to-subject
|
|
|
4246 Limit the summary buffer to articles that match some subject
|
|
|
4247 (@code{gnus-summary-limit-to-subject}).
|
|
|
4248
|
|
|
4249 @item / a
|
|
|
4250 @kindex / a (Summary)
|
|
|
4251 @findex gnus-summary-limit-to-author
|
|
|
4252 Limit the summary buffer to articles that match some author
|
|
|
4253 (@code{gnus-summary-limit-to-author}).
|
|
|
4254
|
|
|
4255 @item / u
|
|
|
4256 @itemx x
|
|
|
4257 @kindex / u (Summary)
|
|
|
4258 @kindex x (Summary)
|
|
|
4259 @findex gnus-summary-limit-to-unread
|
|
|
4260 Limit the summary buffer to articles that are not marked as read
|
|
|
4261 (@code{gnus-summary-limit-to-unread}). If given a prefix, limit the
|
|
|
4262 buffer to articles that are strictly unread. This means that ticked and
|
|
|
4263 dormant articles will also be excluded.
|
|
|
4264
|
|
|
4265 @item / m
|
|
|
4266 @kindex / m (Summary)
|
|
|
4267 @findex gnus-summary-limit-to-marks
|
|
|
4268 Ask for a mark and then limit to all articles that have not been marked
|
|
|
4269 with that mark (@code{gnus-summary-limit-to-marks}).
|
|
|
4270
|
|
16
|
4271 @item / t
|
|
|
4272 @kindex / t (Summary)
|
|
|
4273 @findex gnus-summary-limit-to-age
|
|
|
4274 Ask for a number and then limit the summary buffer to articles that are
|
|
|
4275 older than (or equal to) that number of days
|
|
|
4276 (@code{gnus-summary-limit-to-marks}). If given a prefix, limit to
|
|
|
4277 articles that are younger than that number of days.
|
|
|
4278
|
|
0
|
4279 @item / n
|
|
|
4280 @kindex / n (Summary)
|
|
|
4281 @findex gnus-summary-limit-to-articles
|
|
|
4282 Limit the summary buffer to the current article
|
|
|
4283 (@code{gnus-summary-limit-to-articles}). Uses the process/prefix
|
|
|
4284 convention (@pxref{Process/Prefix}).
|
|
|
4285
|
|
|
4286 @item / w
|
|
|
4287 @kindex / w (Summary)
|
|
|
4288 @findex gnus-summary-pop-limit
|
|
|
4289 Pop the previous limit off the stack and restore it
|
|
|
4290 (@code{gnus-summary-pop-limit}). If given a prefix, pop all limits off
|
|
|
4291 the stack.
|
|
|
4292
|
|
|
4293 @item / v
|
|
|
4294 @kindex / v (Summary)
|
|
|
4295 @findex gnus-summary-limit-to-score
|
|
|
4296 Limit the summary buffer to articles that have a score at or above some
|
|
|
4297 score (@code{gnus-summary-limit-to-score}).
|
|
|
4298
|
|
|
4299 @item / E
|
|
|
4300 @itemx M S
|
|
|
4301 @kindex M S (Summary)
|
|
|
4302 @kindex / E (Summary)
|
|
|
4303 @findex gnus-summary-limit-include-expunged
|
|
|
4304 Display all expunged articles
|
|
|
4305 (@code{gnus-summary-limit-include-expunged}).
|
|
|
4306
|
|
|
4307 @item / D
|
|
|
4308 @kindex / D (Summary)
|
|
|
4309 @findex gnus-summary-limit-include-dormant
|
|
|
4310 Display all dormant articles (@code{gnus-summary-limit-include-dormant}).
|
|
|
4311
|
|
|
4312 @item / d
|
|
|
4313 @kindex / d (Summary)
|
|
|
4314 @findex gnus-summary-limit-exclude-dormant
|
|
|
4315 Hide all dormant articles (@code{gnus-summary-limit-exclude-dormant}).
|
|
|
4316
|
|
|
4317 @item / c
|
|
|
4318 @kindex / c (Summary)
|
|
|
4319 @findex gnus-summary-limit-exclude-childless-dormant
|
|
|
4320 Hide all dormant articles that have no children
|
|
|
4321 (@code{gnus-summary-limit-exclude-childless-dormant}).
|
|
|
4322
|
|
|
4323 @item / C
|
|
|
4324 @kindex / C (Summary)
|
|
|
4325 @findex gnus-summary-limit-mark-excluded-as-read
|
|
|
4326 Mark all excluded unread articles as read
|
|
|
4327 (@code{gnus-summary-limit-mark-excluded-as-read}). If given a prefix,
|
|
|
4328 also mark excluded ticked and dormant articles as read.
|
|
|
4329
|
|
|
4330 @end table
|
|
|
4331
|
|
|
4332
|
|
|
4333 @node Threading
|
|
|
4334 @section Threading
|
|
|
4335 @cindex threading
|
|
|
4336 @cindex article threading
|
|
|
4337
|
|
24
|
4338 Gnus threads articles by default. @dfn{To thread} is to put responses
|
|
|
4339 to articles directly after the articles they respond to---in a
|
|
|
4340 hierarchical fashion.
|
|
0
|
4341
|
|
|
4342 @menu
|
|
|
4343 * Customizing Threading:: Variables you can change to affect the threading.
|
|
|
4344 * Thread Commands:: Thread based commands in the summary buffer.
|
|
|
4345 @end menu
|
|
|
4346
|
|
|
4347
|
|
|
4348 @node Customizing Threading
|
|
|
4349 @subsection Customizing Threading
|
|
|
4350 @cindex customizing threading
|
|
|
4351 @cindex <
|
|
|
4352 @cindex >
|
|
|
4353
|
|
|
4354 @table @code
|
|
|
4355
|
|
|
4356 @item gnus-show-threads
|
|
|
4357 @vindex gnus-show-threads
|
|
|
4358 If this variable is @code{nil}, no threading will be done, and all of
|
|
|
4359 the rest of the variables here will have no effect. Turning threading
|
|
|
4360 off will speed group selection up a bit, but it is sure to make reading
|
|
|
4361 slower and more awkward.
|
|
|
4362
|
|
|
4363 @item gnus-fetch-old-headers
|
|
|
4364 @vindex gnus-fetch-old-headers
|
|
|
4365 If non-@code{nil}, Gnus will attempt to build old threads by fetching
|
|
|
4366 more old headers---headers to articles that are marked as read. If you
|
|
|
4367 would like to display as few summary lines as possible, but still
|
|
|
4368 connect as many loose threads as possible, you should set this variable
|
|
|
4369 to @code{some} or a number. If you set it to a number, no more than
|
|
|
4370 that number of extra old headers will be fetched. In either case,
|
|
|
4371 fetching old headers only works if the backend you are using carries
|
|
|
4372 overview files---this would normally be @code{nntp}, @code{nnspool} and
|
|
|
4373 @code{nnml}. Also remember that if the root of the thread has been
|
|
|
4374 expired by the server, there's not much Gnus can do about that.
|
|
|
4375
|
|
|
4376 @item gnus-build-sparse-threads
|
|
|
4377 @vindex gnus-build-sparse-threads
|
|
|
4378 Fetching old headers can be slow. A low-rent similar effect can be
|
|
|
4379 gotten by setting this variable to @code{some}. Gnus will then look at
|
|
|
4380 the complete @code{References} headers of all articles and try to string
|
|
|
4381 articles that belong in the same thread together. This will leave
|
|
|
4382 @dfn{gaps} in the threading display where Gnus guesses that an article
|
|
|
4383 is missing from the thread. (These gaps appear like normal summary
|
|
|
4384 lines. If you select a gap, Gnus will try to fetch the article in
|
|
|
4385 question.) If this variable is @code{t}, Gnus will display all these
|
|
|
4386 ``gaps'' without regard for whether they are useful for completing the
|
|
|
4387 thread or not. Finally, if this variable is @code{more}, Gnus won't cut
|
|
|
4388 off sparse leaf nodes that don't lead anywhere. This variable is
|
|
|
4389 @code{nil} by default.
|
|
|
4390
|
|
|
4391 @item gnus-summary-gather-subject-limit
|
|
|
4392 @vindex gnus-summary-gather-subject-limit
|
|
|
4393 Loose threads are gathered by comparing subjects of articles. If this
|
|
|
4394 variable is @code{nil}, Gnus requires an exact match between the
|
|
|
4395 subjects of the loose threads before gathering them into one big
|
|
|
4396 super-thread. This might be too strict a requirement, what with the
|
|
|
4397 presence of stupid newsreaders that chop off long subjects lines. If
|
|
|
4398 you think so, set this variable to, say, 20 to require that only the
|
|
|
4399 first 20 characters of the subjects have to match. If you set this
|
|
|
4400 variable to a really low number, you'll find that Gnus will gather
|
|
|
4401 everything in sight into one thread, which isn't very helpful.
|
|
|
4402
|
|
|
4403 @cindex fuzzy article gathering
|
|
|
4404 If you set this variable to the special value @code{fuzzy}, Gnus will
|
|
26
|
4405 use a fuzzy string comparison algorithm on the subjects (@pxref{Fuzzy
|
|
|
4406 Matching}).
|
|
0
|
4407
|
|
|
4408 @item gnus-simplify-subject-fuzzy-regexp
|
|
|
4409 @vindex gnus-simplify-subject-fuzzy-regexp
|
|
|
4410 This can either be a regular expression or list of regular expressions
|
|
|
4411 that match strings that will be removed from subjects if fuzzy subject
|
|
|
4412 simplification is used.
|
|
|
4413
|
|
|
4414 @item gnus-simplify-ignored-prefixes
|
|
|
4415 @vindex gnus-simplify-ignored-prefixes
|
|
|
4416 If you set @code{gnus-summary-gather-subject-limit} to something as low
|
|
|
4417 as 10, you might consider setting this variable to something sensible:
|
|
|
4418
|
|
|
4419 @c Written by Michael Ernst <mernst@cs.rice.edu>
|
|
|
4420 @lisp
|
|
|
4421 (setq gnus-simplify-ignored-prefixes
|
|
|
4422 (concat
|
|
|
4423 "\\`\\[?\\("
|
|
16
|
4424 (mapconcat
|
|
|
4425 'identity
|
|
|
4426 '("looking"
|
|
|
4427 "wanted" "followup" "summary\\( of\\)?"
|
|
|
4428 "help" "query" "problem" "question"
|
|
|
4429 "answer" "reference" "announce"
|
|
|
4430 "How can I" "How to" "Comparison of"
|
|
|
4431 ;; ...
|
|
|
4432 )
|
|
|
4433 "\\|")
|
|
|
4434 "\\)\\s *\\("
|
|
0
|
4435 (mapconcat 'identity
|
|
16
|
4436 '("for" "for reference" "with" "about")
|
|
0
|
4437 "\\|")
|
|
16
|
4438 "\\)?\\]?:?[ \t]*"))
|
|
0
|
4439 @end lisp
|
|
|
4440
|
|
|
4441 All words that match this regexp will be removed before comparing two
|
|
|
4442 subjects.
|
|
|
4443
|
|
|
4444 @item gnus-summary-gather-exclude-subject
|
|
|
4445 @vindex gnus-summary-gather-exclude-subject
|
|
|
4446 Since loose thread gathering is done on subjects only, that might lead
|
|
|
4447 to many false hits, especially with certain common subjects like
|
|
|
4448 @samp{} and @samp{(none)}. To make the situation slightly better,
|
|
|
4449 you can use the regexp @code{gnus-summary-gather-exclude-subject} to say
|
|
|
4450 what subjects should be excluded from the gathering process. The
|
|
|
4451 default is @samp{^ *$\\|^(none)$}.
|
|
|
4452
|
|
|
4453 @item gnus-summary-thread-gathering-function
|
|
|
4454 @vindex gnus-summary-thread-gathering-function
|
|
|
4455 Gnus gathers threads by looking at @code{Subject} headers. This means
|
|
|
4456 that totally unrelated articles may end up in the same ``thread'', which
|
|
|
4457 is confusing. An alternate approach is to look at all the
|
|
|
4458 @code{Message-ID}s in all the @code{References} headers to find matches.
|
|
|
4459 This will ensure that no gathered threads ever includes unrelated
|
|
|
4460 articles, but it's also means that people who have posted with broken
|
|
|
4461 newsreaders won't be gathered properly. The choice is yours---plague or
|
|
|
4462 cholera:
|
|
|
4463
|
|
|
4464 @table @code
|
|
|
4465 @item gnus-gather-threads-by-subject
|
|
|
4466 @findex gnus-gather-threads-by-subject
|
|
|
4467 This function is the default gathering function and looks at
|
|
|
4468 @code{Subject}s exclusively.
|
|
|
4469
|
|
|
4470 @item gnus-gather-threads-by-references
|
|
|
4471 @findex gnus-gather-threads-by-references
|
|
|
4472 This function looks at @code{References} headers exclusively.
|
|
|
4473 @end table
|
|
|
4474
|
|
|
4475 If you want to test gathering by @code{References}, you could say
|
|
|
4476 something like:
|
|
|
4477
|
|
|
4478 @lisp
|
|
|
4479 (setq gnus-summary-thread-gathering-function
|
|
|
4480 'gnus-gather-threads-by-references)
|
|
|
4481 @end lisp
|
|
|
4482
|
|
|
4483 @item gnus-summary-make-false-root
|
|
|
4484 @vindex gnus-summary-make-false-root
|
|
|
4485 If non-@code{nil}, Gnus will gather all loose subtrees into one big tree
|
|
|
4486 and create a dummy root at the top. (Wait a minute. Root at the top?
|
|
|
4487 Yup.) Loose subtrees occur when the real root has expired, or you've
|
|
|
4488 read or killed the root in a previous session.
|
|
|
4489
|
|
|
4490 When there is no real root of a thread, Gnus will have to fudge
|
|
|
4491 something. This variable says what fudging method Gnus should use.
|
|
|
4492 There are four possible values:
|
|
|
4493
|
|
|
4494 @cindex adopting articles
|
|
|
4495
|
|
|
4496 @table @code
|
|
|
4497
|
|
|
4498 @item adopt
|
|
|
4499 Gnus will make the first of the orphaned articles the parent. This
|
|
|
4500 parent will adopt all the other articles. The adopted articles will be
|
|
|
4501 marked as such by pointy brackets (@samp{<>}) instead of the standard
|
|
|
4502 square brackets (@samp{[]}). This is the default method.
|
|
|
4503
|
|
|
4504 @item dummy
|
|
|
4505 @vindex gnus-summary-dummy-line-format
|
|
|
4506 Gnus will create a dummy summary line that will pretend to be the
|
|
|
4507 parent. This dummy line does not correspond to any real article, so
|
|
|
4508 selecting it will just select the first real article after the dummy
|
|
|
4509 article. @code{gnus-summary-dummy-line-format} is used to specify the
|
|
|
4510 format of the dummy roots. It accepts only one format spec: @samp{S},
|
|
|
4511 which is the subject of the article. @xref{Formatting Variables}.
|
|
|
4512
|
|
|
4513 @item empty
|
|
|
4514 Gnus won't actually make any article the parent, but simply leave the
|
|
|
4515 subject field of all orphans except the first empty. (Actually, it will
|
|
|
4516 use @code{gnus-summary-same-subject} as the subject (@pxref{Summary
|
|
|
4517 Buffer Format}).)
|
|
|
4518
|
|
|
4519 @item none
|
|
|
4520 Don't make any article parent at all. Just gather the threads and
|
|
|
4521 display them after one another.
|
|
|
4522
|
|
|
4523 @item nil
|
|
|
4524 Don't gather loose threads.
|
|
|
4525 @end table
|
|
|
4526
|
|
|
4527 @item gnus-thread-hide-subtree
|
|
|
4528 @vindex gnus-thread-hide-subtree
|
|
|
4529 If non-@code{nil}, all threads will be hidden when the summary buffer is
|
|
|
4530 generated.
|
|
|
4531
|
|
16
|
4532 @item gnus-thread-expunge-below
|
|
|
4533 @vindex gnus-thread-expunge-below
|
|
|
4534 All threads that have a total score (as defined by
|
|
|
4535 @code{gnus-thread-score-function}) less than this number will be
|
|
|
4536 expunged. This variable is @code{nil} by default, which means that no
|
|
|
4537 threads are expunged.
|
|
|
4538
|
|
0
|
4539 @item gnus-thread-hide-killed
|
|
|
4540 @vindex gnus-thread-hide-killed
|
|
|
4541 if you kill a thread and this variable is non-@code{nil}, the subtree
|
|
|
4542 will be hidden.
|
|
|
4543
|
|
|
4544 @item gnus-thread-ignore-subject
|
|
|
4545 @vindex gnus-thread-ignore-subject
|
|
|
4546 Sometimes somebody changes the subject in the middle of a thread. If
|
|
|
4547 this variable is non-@code{nil}, the subject change is ignored. If it
|
|
|
4548 is @code{nil}, which is the default, a change in the subject will result
|
|
|
4549 in a new thread.
|
|
|
4550
|
|
|
4551 @item gnus-thread-indent-level
|
|
|
4552 @vindex gnus-thread-indent-level
|
|
|
4553 This is a number that says how much each sub-thread should be indented.
|
|
16
|
4554 The default is 4.
|
|
|
4555
|
|
|
4556 @item gnus-parse-headers-hook
|
|
|
4557 @vindex gnus-parse-headers-hook
|
|
|
4558 Hook run before parsing any headers. The default value is
|
|
|
4559 @code{(gnus-decode-rfc1522)}, which means that QPized headers will be
|
|
|
4560 slightly decoded in a hackish way. This is likely to change in the
|
|
|
4561 future when Gnus becomes @sc{MIME}ified.
|
|
|
4562
|
|
0
|
4563 @end table
|
|
|
4564
|
|
|
4565
|
|
|
4566 @node Thread Commands
|
|
|
4567 @subsection Thread Commands
|
|
|
4568 @cindex thread commands
|
|
|
4569
|
|
|
4570 @table @kbd
|
|
|
4571
|
|
|
4572 @item T k
|
|
|
4573 @itemx M-C-k
|
|
|
4574 @kindex T k (Summary)
|
|
|
4575 @kindex M-C-k (Summary)
|
|
|
4576 @findex gnus-summary-kill-thread
|
|
16
|
4577 Mark all articles in the current (sub-)thread as read
|
|
0
|
4578 (@code{gnus-summary-kill-thread}). If the prefix argument is positive,
|
|
|
4579 remove all marks instead. If the prefix argument is negative, tick
|
|
|
4580 articles instead.
|
|
|
4581
|
|
|
4582 @item T l
|
|
|
4583 @itemx M-C-l
|
|
|
4584 @kindex T l (Summary)
|
|
|
4585 @kindex M-C-l (Summary)
|
|
|
4586 @findex gnus-summary-lower-thread
|
|
16
|
4587 Lower the score of the current (sub-)thread
|
|
0
|
4588 (@code{gnus-summary-lower-thread}).
|
|
|
4589
|
|
|
4590 @item T i
|
|
|
4591 @kindex T i (Summary)
|
|
|
4592 @findex gnus-summary-raise-thread
|
|
16
|
4593 Increase the score of the current (sub-)thread
|
|
0
|
4594 (@code{gnus-summary-raise-thread}).
|
|
|
4595
|
|
|
4596 @item T #
|
|
|
4597 @kindex T # (Summary)
|
|
|
4598 @findex gnus-uu-mark-thread
|
|
16
|
4599 Set the process mark on the current (sub-)thread
|
|
0
|
4600 (@code{gnus-uu-mark-thread}).
|
|
|
4601
|
|
|
4602 @item T M-#
|
|
|
4603 @kindex T M-# (Summary)
|
|
|
4604 @findex gnus-uu-unmark-thread
|
|
16
|
4605 Remove the process mark from the current (sub-)thread
|
|
0
|
4606 (@code{gnus-uu-unmark-thread}).
|
|
|
4607
|
|
|
4608 @item T T
|
|
|
4609 @kindex T T (Summary)
|
|
|
4610 @findex gnus-summary-toggle-threads
|
|
|
4611 Toggle threading (@code{gnus-summary-toggle-threads}).
|
|
|
4612
|
|
|
4613 @item T s
|
|
|
4614 @kindex T s (Summary)
|
|
|
4615 @findex gnus-summary-show-thread
|
|
16
|
4616 Expose the (sub-)thread hidden under the current article, if any
|
|
0
|
4617 (@code{gnus-summary-show-thread}).
|
|
|
4618
|
|
|
4619 @item T h
|
|
|
4620 @kindex T h (Summary)
|
|
|
4621 @findex gnus-summary-hide-thread
|
|
16
|
4622 Hide the current (sub-)thread (@code{gnus-summary-hide-thread}).
|
|
0
|
4623
|
|
|
4624 @item T S
|
|
|
4625 @kindex T S (Summary)
|
|
|
4626 @findex gnus-summary-show-all-threads
|
|
|
4627 Expose all hidden threads (@code{gnus-summary-show-all-threads}).
|
|
|
4628
|
|
|
4629 @item T H
|
|
|
4630 @kindex T H (Summary)
|
|
|
4631 @findex gnus-summary-hide-all-threads
|
|
|
4632 Hide all threads (@code{gnus-summary-hide-all-threads}).
|
|
|
4633
|
|
|
4634 @item T t
|
|
|
4635 @kindex T t (Summary)
|
|
|
4636 @findex gnus-summary-rethread-current
|
|
|
4637 Re-thread the thread the current article is part of
|
|
|
4638 (@code{gnus-summary-rethread-current}). This works even when the
|
|
|
4639 summary buffer is otherwise unthreaded.
|
|
|
4640
|
|
|
4641 @item T ^
|
|
|
4642 @kindex T ^ (Summary)
|
|
|
4643 @findex gnus-summary-reparent-thread
|
|
|
4644 Make the current article the child of the marked (or previous) article
|
|
|
4645 (@code{gnus-summary-reparent-thread}.
|
|
|
4646
|
|
|
4647 @end table
|
|
|
4648
|
|
|
4649 The following commands are thread movement commands. They all
|
|
|
4650 understand the numeric prefix.
|
|
|
4651
|
|
|
4652 @table @kbd
|
|
|
4653
|
|
|
4654 @item T n
|
|
|
4655 @kindex T n (Summary)
|
|
|
4656 @findex gnus-summary-next-thread
|
|
|
4657 Go to the next thread (@code{gnus-summary-next-thread}).
|
|
|
4658
|
|
|
4659 @item T p
|
|
|
4660 @kindex T p (Summary)
|
|
|
4661 @findex gnus-summary-prev-thread
|
|
|
4662 Go to the previous thread (@code{gnus-summary-prev-thread}).
|
|
|
4663
|
|
|
4664 @item T d
|
|
|
4665 @kindex T d (Summary)
|
|
|
4666 @findex gnus-summary-down-thread
|
|
|
4667 Descend the thread (@code{gnus-summary-down-thread}).
|
|
|
4668
|
|
|
4669 @item T u
|
|
|
4670 @kindex T u (Summary)
|
|
|
4671 @findex gnus-summary-up-thread
|
|
|
4672 Ascend the thread (@code{gnus-summary-up-thread}).
|
|
|
4673
|
|
|
4674 @item T o
|
|
|
4675 @kindex T o (Summary)
|
|
|
4676 @findex gnus-summary-top-thread
|
|
|
4677 Go to the top of the thread (@code{gnus-summary-top-thread}).
|
|
|
4678 @end table
|
|
|
4679
|
|
|
4680 @vindex gnus-thread-operation-ignore-subject
|
|
|
4681 If you ignore subject while threading, you'll naturally end up with
|
|
|
4682 threads that have several different subjects in them. If you then issue
|
|
|
4683 a command like `T k' (@code{gnus-summary-kill-thread}) you might not
|
|
|
4684 wish to kill the entire thread, but just those parts of the thread that
|
|
|
4685 have the same subject as the current article. If you like this idea,
|
|
|
4686 you can fiddle with @code{gnus-thread-operation-ignore-subject}. If is
|
|
|
4687 is non-@code{nil} (which it is by default), subjects will be ignored
|
|
|
4688 when doing thread commands. If this variable is @code{nil}, articles in
|
|
|
4689 the same thread with different subjects will not be included in the
|
|
|
4690 operation in question. If this variable is @code{fuzzy}, only articles
|
|
26
|
4691 that have subjects that are fuzzily equal will be included (@pxref{Fuzzy
|
|
|
4692 Matching}).
|
|
0
|
4693
|
|
|
4694
|
|
|
4695 @node Sorting
|
|
|
4696 @section Sorting
|
|
|
4697
|
|
|
4698 @findex gnus-thread-sort-by-total-score
|
|
|
4699 @findex gnus-thread-sort-by-date
|
|
|
4700 @findex gnus-thread-sort-by-score
|
|
|
4701 @findex gnus-thread-sort-by-subject
|
|
|
4702 @findex gnus-thread-sort-by-author
|
|
|
4703 @findex gnus-thread-sort-by-number
|
|
|
4704 @vindex gnus-thread-sort-functions
|
|
|
4705 If you are using a threaded summary display, you can sort the threads by
|
|
|
4706 setting @code{gnus-thread-sort-functions}, which is a list of functions.
|
|
|
4707 By default, sorting is done on article numbers. Ready-made sorting
|
|
|
4708 predicate functions include @code{gnus-thread-sort-by-number},
|
|
|
4709 @code{gnus-thread-sort-by-author}, @code{gnus-thread-sort-by-subject},
|
|
|
4710 @code{gnus-thread-sort-by-date}, @code{gnus-thread-sort-by-score}, and
|
|
|
4711 @code{gnus-thread-sort-by-total-score}.
|
|
|
4712
|
|
|
4713 Each function takes two threads and return non-@code{nil} if the first
|
|
|
4714 thread should be sorted before the other. Note that sorting really is
|
|
|
4715 normally done by looking only at the roots of each thread. If you use
|
|
|
4716 more than one function, the primary sort key should be the last function
|
|
|
4717 in the list. You should probably always include
|
|
|
4718 @code{gnus-thread-sort-by-number} in the list of sorting
|
|
|
4719 functions---preferably first. This will ensure that threads that are
|
|
|
4720 equal with respect to the other sort criteria will be displayed in
|
|
|
4721 ascending article order.
|
|
|
4722
|
|
|
4723 If you would like to sort by score, then by subject, and finally by
|
|
|
4724 number, you could do something like:
|
|
|
4725
|
|
|
4726 @lisp
|
|
|
4727 (setq gnus-thread-sort-functions
|
|
|
4728 '(gnus-thread-sort-by-number
|
|
|
4729 gnus-thread-sort-by-subject
|
|
|
4730 gnus-thread-sort-by-score))
|
|
|
4731 @end lisp
|
|
|
4732
|
|
|
4733 The threads that have highest score will be displayed first in the
|
|
|
4734 summary buffer. When threads have the same score, they will be sorted
|
|
|
4735 alphabetically. The threads that have the same score and the same
|
|
|
4736 subject will be sorted by number, which is (normally) the sequence in
|
|
|
4737 which the articles arrived.
|
|
|
4738
|
|
|
4739 If you want to sort by score and then reverse arrival order, you could
|
|
|
4740 say something like:
|
|
|
4741
|
|
|
4742 @lisp
|
|
|
4743 (setq gnus-thread-sort-functions
|
|
|
4744 '((lambda (t1 t2)
|
|
|
4745 (not (gnus-thread-sort-by-number t1 t2)))
|
|
|
4746 gnus-thread-sort-by-score))
|
|
|
4747 @end lisp
|
|
|
4748
|
|
|
4749 @vindex gnus-thread-score-function
|
|
|
4750 The function in the @code{gnus-thread-score-function} variable (default
|
|
|
4751 @code{+}) is used for calculating the total score of a thread. Useful
|
|
|
4752 functions might be @code{max}, @code{min}, or squared means, or whatever
|
|
|
4753 tickles your fancy.
|
|
|
4754
|
|
|
4755 @findex gnus-article-sort-functions
|
|
|
4756 @findex gnus-article-sort-by-date
|
|
|
4757 @findex gnus-article-sort-by-score
|
|
|
4758 @findex gnus-article-sort-by-subject
|
|
|
4759 @findex gnus-article-sort-by-author
|
|
|
4760 @findex gnus-article-sort-by-number
|
|
|
4761 If you are using an unthreaded display for some strange reason or other,
|
|
|
4762 you have to fiddle with the @code{gnus-article-sort-functions} variable.
|
|
|
4763 It is very similar to the @code{gnus-thread-sort-functions}, except that
|
|
|
4764 is uses slightly different functions for article comparison. Available
|
|
|
4765 sorting predicate functions are @code{gnus-article-sort-by-number},
|
|
|
4766 @code{gnus-article-sort-by-author}, @code{gnus-article-sort-by-subject},
|
|
|
4767 @code{gnus-article-sort-by-date}, and @code{gnus-article-sort-by-score}.
|
|
|
4768
|
|
|
4769 If you want to sort an unthreaded summary display by subject, you could
|
|
|
4770 say something like:
|
|
|
4771
|
|
|
4772 @lisp
|
|
|
4773 (setq gnus-article-sort-functions
|
|
|
4774 '(gnus-article-sort-by-number
|
|
|
4775 gnus-article-sort-by-subject))
|
|
|
4776 @end lisp
|
|
|
4777
|
|
|
4778
|
|
|
4779
|
|
|
4780 @node Asynchronous Fetching
|
|
|
4781 @section Asynchronous Article Fetching
|
|
|
4782 @cindex asynchronous article fetching
|
|
16
|
4783 @cindex article pre-fetch
|
|
|
4784 @cindex pre-fetch
|
|
0
|
4785
|
|
|
4786 If you read your news from an @sc{nntp} server that's far away, the
|
|
|
4787 network latencies may make reading articles a chore. You have to wait
|
|
|
4788 for a while after pressing @kbd{n} to go to the next article before the
|
|
|
4789 article appears. Why can't Gnus just go ahead and fetch the article
|
|
16
|
4790 while you are reading the previous one? Why not, indeed.
|
|
0
|
4791
|
|
|
4792 First, some caveats. There are some pitfalls to using asynchronous
|
|
|
4793 article fetching, especially the way Gnus does it.
|
|
|
4794
|
|
|
4795 Let's say you are reading article 1, which is short, and article 2 is
|
|
|
4796 quite long, and you are not interested in reading that. Gnus does not
|
|
|
4797 know this, so it goes ahead and fetches article 2. You decide to read
|
|
|
4798 article 3, but since Gnus is in the process of fetching article 2, the
|
|
|
4799 connection is blocked.
|
|
|
4800
|
|
|
4801 To avoid these situations, Gnus will open two (count 'em two)
|
|
|
4802 connections to the server. Some people may think this isn't a very nice
|
|
|
4803 thing to do, but I don't see any real alternatives. Setting up that
|
|
|
4804 extra connection takes some time, so Gnus startup will be slower.
|
|
|
4805
|
|
|
4806 Gnus will fetch more articles than you will read. This will mean that
|
|
|
4807 the link between your machine and the @sc{nntp} server will become more
|
|
|
4808 loaded than if you didn't use article pre-fetch. The server itself will
|
|
|
4809 also become more loaded---both with the extra article requests, and the
|
|
|
4810 extra connection.
|
|
|
4811
|
|
|
4812 Ok, so now you know that you shouldn't really use this thing... unless
|
|
|
4813 you really want to.
|
|
|
4814
|
|
|
4815 @vindex gnus-asynchronous
|
|
|
4816 Here's how: Set @code{gnus-asynchronous} to @code{t}. The rest should
|
|
|
4817 happen automatically.
|
|
|
4818
|
|
16
|
4819 @vindex gnus-use-article-prefetch
|
|
0
|
4820 You can control how many articles that are to be pre-fetched by setting
|
|
16
|
4821 @code{gnus-use-article-prefetch}. This is 30 by default, which means
|
|
|
4822 that when you read an article in the group, the backend will pre-fetch
|
|
|
4823 the next 30 articles. If this variable is @code{t}, the backend will
|
|
|
4824 pre-fetch all the articles that it can without bound. If it is
|
|
|
4825 @code{nil}, no pre-fetching will be made.
|
|
|
4826
|
|
|
4827 @vindex gnus-async-prefetch-article-p
|
|
|
4828 @findex gnus-async-read-p
|
|
|
4829 There are probably some articles that you don't want to pre-fetch---read
|
|
|
4830 articles, for instance. Which articles to pre-fetch is controlled by
|
|
|
4831 the @code{gnus-async-prefetch-article-p} variable. This function should
|
|
|
4832 return non-@code{nil} when the article in question is to be
|
|
|
4833 pre-fetched. The default is @code{gnus-async-read-p}, which returns
|
|
|
4834 @code{nil} on read articles. The function is called with an article
|
|
|
4835 data structure as the only parameter.
|
|
|
4836
|
|
|
4837 If, for instance, you wish to pre-fetch only unread articles that are
|
|
|
4838 shorter than 100 lines, you could say something like:
|
|
|
4839
|
|
|
4840 @lisp
|
|
|
4841 (defun my-async-short-unread-p (data)
|
|
|
4842 "Return non-nil for short, unread articles."
|
|
|
4843 (and (gnus-data-unread-p data)
|
|
|
4844 (< (mail-header-lines (gnus-data-header data))
|
|
|
4845 100)))
|
|
|
4846
|
|
|
4847 (setq gnus-async-prefetch-article-p 'my-async-short-unread-p)
|
|
|
4848 @end lisp
|
|
|
4849
|
|
|
4850 These functions will be called many, many times, so they should
|
|
|
4851 preferrably be short and sweet to avoid slowing down Gnus too much.
|
|
|
4852 It's also probably a good idea to byte-compile things like this.
|
|
|
4853
|
|
|
4854 @vindex gnus-prefetched-article-deletion-strategy
|
|
|
4855 Articles have to be removed from the asynch buffer sooner or later. The
|
|
|
4856 @code{gnus-prefetched-article-deletion-strategy} says when to remove
|
|
|
4857 articles. This is a list that may contain the following elements:
|
|
|
4858
|
|
|
4859 @table @code
|
|
|
4860 @item read
|
|
|
4861 Remove articles when they are read.
|
|
|
4862
|
|
|
4863 @item exit
|
|
|
4864 Remove articles when exiting the group.
|
|
|
4865 @end table
|
|
|
4866
|
|
|
4867 The default value is @code{(read exit)}.
|
|
|
4868
|
|
|
4869 @vindex gnus-use-header-prefetch
|
|
|
4870 If @code{gnus-use-header-prefetch} is non-@code{nil}, prefetch articles
|
|
|
4871 from the next group.
|
|
0
|
4872
|
|
|
4873
|
|
|
4874 @node Article Caching
|
|
|
4875 @section Article Caching
|
|
|
4876 @cindex article caching
|
|
|
4877 @cindex caching
|
|
|
4878
|
|
|
4879 If you have an @emph{extremely} slow @sc{nntp} connection, you may
|
|
|
4880 consider turning article caching on. Each article will then be stored
|
|
|
4881 locally under your home directory. As you may surmise, this could
|
|
|
4882 potentially use @emph{huge} amounts of disk space, as well as eat up all
|
|
|
4883 your inodes so fast it will make your head swim. In vodka.
|
|
|
4884
|
|
|
4885 Used carefully, though, it could be just an easier way to save articles.
|
|
|
4886
|
|
|
4887 @vindex gnus-use-long-file-name
|
|
|
4888 @vindex gnus-cache-directory
|
|
|
4889 @vindex gnus-use-cache
|
|
|
4890 To turn caching on, set @code{gnus-use-cache} to @code{t}. By default,
|
|
|
4891 all articles that are ticked or marked as dormant will then be copied
|
|
|
4892 over to your local cache (@code{gnus-cache-directory}). Whether this
|
|
|
4893 cache is flat or hierarchal is controlled by the
|
|
|
4894 @code{gnus-use-long-file-name} variable, as usual.
|
|
|
4895
|
|
|
4896 When re-select a ticked or dormant article, it will be fetched from the
|
|
|
4897 cache instead of from the server. As articles in your cache will never
|
|
|
4898 expire, this might serve as a method of saving articles while still
|
|
|
4899 keeping them where they belong. Just mark all articles you want to save
|
|
|
4900 as dormant, and don't worry.
|
|
|
4901
|
|
|
4902 When an article is marked as read, is it removed from the cache.
|
|
|
4903
|
|
|
4904 @vindex gnus-cache-remove-articles
|
|
|
4905 @vindex gnus-cache-enter-articles
|
|
|
4906 The entering/removal of articles from the cache is controlled by the
|
|
|
4907 @code{gnus-cache-enter-articles} and @code{gnus-cache-remove-articles}
|
|
|
4908 variables. Both are lists of symbols. The first is @code{(ticked
|
|
|
4909 dormant)} by default, meaning that ticked and dormant articles will be
|
|
|
4910 put in the cache. The latter is @code{(read)} by default, meaning that
|
|
|
4911 articles that are marked as read are removed from the cache. Possibly
|
|
|
4912 symbols in these two lists are @code{ticked}, @code{dormant},
|
|
|
4913 @code{unread} and @code{read}.
|
|
|
4914
|
|
|
4915 @findex gnus-jog-cache
|
|
|
4916 So where does the massive article-fetching and storing come into the
|
|
|
4917 picture? The @code{gnus-jog-cache} command will go through all
|
|
|
4918 subscribed newsgroups, request all unread articles, and store them in
|
|
|
4919 the cache. You should only ever, ever ever ever, use this command if 1)
|
|
|
4920 your connection to the @sc{nntp} server is really, really, really slow
|
|
|
4921 and 2) you have a really, really, really huge disk. Seriously.
|
|
|
4922
|
|
|
4923 @vindex gnus-uncacheable-groups
|
|
|
4924 It is likely that you do not want caching on some groups. For instance,
|
|
|
4925 if your @code{nnml} mail is located under your home directory, it makes no
|
|
|
4926 sense to cache it somewhere else under your home directory. Unless you
|
|
|
4927 feel that it's neat to use twice as much space. To limit the caching,
|
|
|
4928 you could set the @code{gnus-uncacheable-groups} regexp to
|
|
|
4929 @samp{^nnml}, for instance. This variable is @code{nil} by
|
|
|
4930 default.
|
|
|
4931
|
|
|
4932 @findex gnus-cache-generate-nov-databases
|
|
|
4933 @findex gnus-cache-generate-active
|
|
|
4934 @vindex gnus-cache-active-file
|
|
|
4935 The cache stores information on what articles it contains in its active
|
|
|
4936 file (@code{gnus-cache-active-file}). If this file (or any other parts
|
|
|
4937 of the cache) becomes all messed up for some reason or other, Gnus
|
|
|
4938 offers two functions that will try to set things right. @kbd{M-x
|
|
|
4939 gnus-cache-generate-nov-databases} will (re)build all the @sc{nov}
|
|
|
4940 files, and @kbd{gnus-cache-generate-active} will (re)generate the active
|
|
|
4941 file.
|
|
|
4942
|
|
|
4943
|
|
|
4944 @node Persistent Articles
|
|
|
4945 @section Persistent Articles
|
|
|
4946 @cindex persistent articles
|
|
|
4947
|
|
|
4948 Closely related to article caching, we have @dfn{persistent articles}.
|
|
|
4949 In fact, it's just a different way of looking at caching, and much more
|
|
|
4950 useful in my opinion.
|
|
|
4951
|
|
|
4952 Say you're reading a newsgroup, and you happen on to some valuable gem
|
|
|
4953 that you want to keep and treasure forever. You'd normally just save it
|
|
|
4954 (using one of the many saving commands) in some file. The problem with
|
|
|
4955 that is that it's just, well, yucky. Ideally you'd prefer just having
|
|
|
4956 the article remain in the group where you found it forever; untouched by
|
|
|
4957 the expiry going on at the news server.
|
|
|
4958
|
|
|
4959 This is what a @dfn{persistent article} is---an article that just won't
|
|
|
4960 be deleted. It's implemented using the normal cache functions, but
|
|
|
4961 you use two explicit commands for managing persistent articles:
|
|
|
4962
|
|
|
4963 @table @kbd
|
|
|
4964
|
|
|
4965 @item *
|
|
|
4966 @kindex * (Summary)
|
|
|
4967 @findex gnus-cache-enter-article
|
|
|
4968 Make the current article persistent (@code{gnus-cache-enter-article}).
|
|
|
4969
|
|
|
4970 @item M-*
|
|
|
4971 @kindex M-* (Summary)
|
|
|
4972 @findex gnus-cache-remove-article
|
|
|
4973 Remove the current article from the persistent articles
|
|
|
4974 (@code{gnus-cache-remove-article}). This will normally delete the
|
|
|
4975 article.
|
|
|
4976 @end table
|
|
|
4977
|
|
|
4978 Both these commands understand the process/prefix convention.
|
|
|
4979
|
|
|
4980 To avoid having all ticked articles (and stuff) entered into the cache,
|
|
|
4981 you should set @code{gnus-use-cache} to @code{passive} if you're just
|
|
|
4982 interested in persistent articles:
|
|
|
4983
|
|
|
4984 @lisp
|
|
|
4985 (setq gnus-use-cache 'passive)
|
|
|
4986 @end lisp
|
|
|
4987
|
|
|
4988
|
|
|
4989 @node Article Backlog
|
|
|
4990 @section Article Backlog
|
|
|
4991 @cindex backlog
|
|
|
4992 @cindex article backlog
|
|
|
4993
|
|
|
4994 If you have a slow connection, but the idea of using caching seems
|
|
|
4995 unappealing to you (and it is, really), you can help the situation some
|
|
|
4996 by switching on the @dfn{backlog}. This is where Gnus will buffer
|
|
|
4997 already read articles so that it doesn't have to re-fetch articles
|
|
|
4998 you've already read. This only helps if you are in the habit of
|
|
|
4999 re-selecting articles you've recently read, of course. If you never do
|
|
|
5000 that, turning the backlog on will slow Gnus down a little bit, and
|
|
|
5001 increase memory usage some.
|
|
|
5002
|
|
|
5003 @vindex gnus-keep-backlog
|
|
|
5004 If you set @code{gnus-keep-backlog} to a number @var{n}, Gnus will store
|
|
|
5005 at most @var{n} old articles in a buffer for later re-fetching. If this
|
|
|
5006 variable is non-@code{nil} and is not a number, Gnus will store
|
|
|
5007 @emph{all} read articles, which means that your Emacs will grow without
|
|
|
5008 bound before exploding and taking your machine down with you. I put
|
|
|
5009 that in there just to keep y'all on your toes.
|
|
|
5010
|
|
|
5011 This variable is @code{nil} by default.
|
|
|
5012
|
|
|
5013
|
|
|
5014 @node Saving Articles
|
|
|
5015 @section Saving Articles
|
|
|
5016 @cindex saving articles
|
|
|
5017
|
|
|
5018 Gnus can save articles in a number of ways. Below is the documentation
|
|
|
5019 for saving articles in a fairly straight-forward fashion (i.e., little
|
|
|
5020 processing of the article is done before it is saved). For a different
|
|
|
5021 approach (uudecoding, unsharing) you should use @code{gnus-uu}
|
|
|
5022 (@pxref{Decoding Articles}).
|
|
|
5023
|
|
|
5024 @vindex gnus-save-all-headers
|
|
|
5025 If @code{gnus-save-all-headers} is non-@code{nil}, Gnus will not delete
|
|
|
5026 unwanted headers before saving the article.
|
|
|
5027
|
|
|
5028 @vindex gnus-saved-headers
|
|
|
5029 If the preceding variable is @code{nil}, all headers that match the
|
|
|
5030 @code{gnus-saved-headers} regexp will be kept, while the rest will be
|
|
|
5031 deleted before saving.
|
|
|
5032
|
|
|
5033 @table @kbd
|
|
|
5034
|
|
|
5035 @item O o
|
|
|
5036 @itemx o
|
|
|
5037 @kindex O o (Summary)
|
|
|
5038 @kindex o (Summary)
|
|
|
5039 @findex gnus-summary-save-article
|
|
|
5040 Save the current article using the default article saver
|
|
|
5041 (@code{gnus-summary-save-article}).
|
|
|
5042
|
|
|
5043 @item O m
|
|
|
5044 @kindex O m (Summary)
|
|
|
5045 @findex gnus-summary-save-article-mail
|
|
|
5046 Save the current article in mail format
|
|
|
5047 (@code{gnus-summary-save-article-mail}).
|
|
|
5048
|
|
|
5049 @item O r
|
|
|
5050 @kindex O r (Summary)
|
|
|
5051 @findex gnus-summary-save-article-rmail
|
|
|
5052 Save the current article in rmail format
|
|
|
5053 (@code{gnus-summary-save-article-rmail}).
|
|
|
5054
|
|
|
5055 @item O f
|
|
|
5056 @kindex O f (Summary)
|
|
|
5057 @findex gnus-summary-save-article-file
|
|
|
5058 Save the current article in plain file format
|
|
|
5059 (@code{gnus-summary-save-article-file}).
|
|
|
5060
|
|
16
|
5061 @item O F
|
|
|
5062 @kindex O F (Summary)
|
|
|
5063 @findex gnus-summary-write-article-file
|
|
|
5064 Write the current article in plain file format, overwriting any previous
|
|
|
5065 file contents (@code{gnus-summary-write-article-file}).
|
|
|
5066
|
|
0
|
5067 @item O b
|
|
|
5068 @kindex O b (Summary)
|
|
|
5069 @findex gnus-summary-save-article-body-file
|
|
|
5070 Save the current article body in plain file format
|
|
|
5071 (@code{gnus-summary-save-article-body-file}).
|
|
|
5072
|
|
|
5073 @item O h
|
|
|
5074 @kindex O h (Summary)
|
|
|
5075 @findex gnus-summary-save-article-folder
|
|
|
5076 Save the current article in mh folder format
|
|
|
5077 (@code{gnus-summary-save-article-folder}).
|
|
|
5078
|
|
|
5079 @item O v
|
|
|
5080 @kindex O v (Summary)
|
|
|
5081 @findex gnus-summary-save-article-vm
|
|
|
5082 Save the current article in a VM folder
|
|
|
5083 (@code{gnus-summary-save-article-vm}).
|
|
|
5084
|
|
|
5085 @item O p
|
|
|
5086 @kindex O p (Summary)
|
|
|
5087 @findex gnus-summary-pipe-output
|
|
|
5088 Save the current article in a pipe. Uhm, like, what I mean is---Pipe
|
|
|
5089 the current article to a process (@code{gnus-summary-pipe-output}).
|
|
|
5090 @end table
|
|
|
5091
|
|
|
5092 @vindex gnus-prompt-before-saving
|
|
|
5093 All these commands use the process/prefix convention
|
|
|
5094 (@pxref{Process/Prefix}). If you save bunches of articles using these
|
|
|
5095 functions, you might get tired of being prompted for files to save each
|
|
|
5096 and every article in. The prompting action is controlled by
|
|
|
5097 the @code{gnus-prompt-before-saving} variable, which is @code{always} by
|
|
|
5098 default, giving you that excessive prompting action you know and
|
|
|
5099 loathe. If you set this variable to @code{t} instead, you'll be prompted
|
|
|
5100 just once for each series of articles you save. If you like to really
|
|
|
5101 have Gnus do all your thinking for you, you can even set this variable
|
|
|
5102 to @code{nil}, which means that you will never be prompted for files to
|
|
|
5103 save articles in. Gnus will simply save all the articles in the default
|
|
|
5104 files.
|
|
|
5105
|
|
|
5106
|
|
|
5107 @vindex gnus-default-article-saver
|
|
|
5108 You can customize the @code{gnus-default-article-saver} variable to make
|
|
|
5109 Gnus do what you want it to. You can use any of the four ready-made
|
|
|
5110 functions below, or you can create your own.
|
|
|
5111
|
|
|
5112 @table @code
|
|
|
5113
|
|
|
5114 @item gnus-summary-save-in-rmail
|
|
|
5115 @findex gnus-summary-save-in-rmail
|
|
|
5116 @vindex gnus-rmail-save-name
|
|
|
5117 @findex gnus-plain-save-name
|
|
|
5118 This is the default format, @dfn{babyl}. Uses the function in the
|
|
|
5119 @code{gnus-rmail-save-name} variable to get a file name to save the
|
|
|
5120 article in. The default is @code{gnus-plain-save-name}.
|
|
|
5121
|
|
|
5122 @item gnus-summary-save-in-mail
|
|
|
5123 @findex gnus-summary-save-in-mail
|
|
|
5124 @vindex gnus-mail-save-name
|
|
|
5125 Save in a Unix mail (mbox) file. Uses the function in the
|
|
|
5126 @code{gnus-mail-save-name} variable to get a file name to save the
|
|
|
5127 article in. The default is @code{gnus-plain-save-name}.
|
|
|
5128
|
|
|
5129 @item gnus-summary-save-in-file
|
|
|
5130 @findex gnus-summary-save-in-file
|
|
|
5131 @vindex gnus-file-save-name
|
|
|
5132 @findex gnus-numeric-save-name
|
|
|
5133 Append the article straight to an ordinary file. Uses the function in
|
|
|
5134 the @code{gnus-file-save-name} variable to get a file name to save the
|
|
|
5135 article in. The default is @code{gnus-numeric-save-name}.
|
|
|
5136
|
|
|
5137 @item gnus-summary-save-body-in-file
|
|
|
5138 @findex gnus-summary-save-body-in-file
|
|
|
5139 Append the article body to an ordinary file. Uses the function in the
|
|
|
5140 @code{gnus-file-save-name} variable to get a file name to save the
|
|
|
5141 article in. The default is @code{gnus-numeric-save-name}.
|
|
|
5142
|
|
|
5143 @item gnus-summary-save-in-folder
|
|
|
5144 @findex gnus-summary-save-in-folder
|
|
|
5145 @findex gnus-folder-save-name
|
|
|
5146 @findex gnus-Folder-save-name
|
|
|
5147 @vindex gnus-folder-save-name
|
|
|
5148 @cindex rcvstore
|
|
|
5149 @cindex MH folders
|
|
|
5150 Save the article to an MH folder using @code{rcvstore} from the MH
|
|
|
5151 library. Uses the function in the @code{gnus-folder-save-name} variable
|
|
|
5152 to get a file name to save the article in. The default is
|
|
|
5153 @code{gnus-folder-save-name}, but you can also use
|
|
|
5154 @code{gnus-Folder-save-name}. The former creates capitalized names, and
|
|
|
5155 the latter does not.
|
|
|
5156
|
|
|
5157 @item gnus-summary-save-in-vm
|
|
|
5158 @findex gnus-summary-save-in-vm
|
|
|
5159 Save the article in a VM folder. You have to have the VM mail
|
|
|
5160 reader to use this setting.
|
|
|
5161 @end table
|
|
|
5162
|
|
|
5163 @vindex gnus-article-save-directory
|
|
|
5164 All of these functions, except for the last one, will save the article
|
|
|
5165 in the @code{gnus-article-save-directory}, which is initialized from the
|
|
|
5166 @code{SAVEDIR} environment variable. This is @file{~/News/} by
|
|
|
5167 default.
|
|
|
5168
|
|
|
5169 As you can see above, the functions use different functions to find a
|
|
|
5170 suitable name of a file to save the article in. Below is a list of
|
|
|
5171 available functions that generate names:
|
|
|
5172
|
|
|
5173 @table @code
|
|
|
5174
|
|
|
5175 @item gnus-Numeric-save-name
|
|
|
5176 @findex gnus-Numeric-save-name
|
|
16
|
5177 File names like @file{~/News/Alt.andrea-dworkin/45}.
|
|
0
|
5178
|
|
|
5179 @item gnus-numeric-save-name
|
|
|
5180 @findex gnus-numeric-save-name
|
|
16
|
5181 File names like @file{~/News/alt.andrea-dworkin/45}.
|
|
0
|
5182
|
|
|
5183 @item gnus-Plain-save-name
|
|
|
5184 @findex gnus-Plain-save-name
|
|
16
|
5185 File names like @file{~/News/Alt.andrea-dworkin}.
|
|
0
|
5186
|
|
|
5187 @item gnus-plain-save-name
|
|
|
5188 @findex gnus-plain-save-name
|
|
16
|
5189 File names like @file{~/News/alt.andrea-dworkin}.
|
|
0
|
5190 @end table
|
|
|
5191
|
|
|
5192 @vindex gnus-split-methods
|
|
|
5193 You can have Gnus suggest where to save articles by plonking a regexp into
|
|
|
5194 the @code{gnus-split-methods} alist. For instance, if you would like to
|
|
|
5195 save articles related to Gnus in the file @file{gnus-stuff}, and articles
|
|
|
5196 related to VM in @code{vm-stuff}, you could set this variable to something
|
|
|
5197 like:
|
|
|
5198
|
|
|
5199 @lisp
|
|
|
5200 (("^Subject:.*gnus\\|^Newsgroups:.*gnus" "gnus-stuff")
|
|
|
5201 ("^Subject:.*vm\\|^Xref:.*vm" "vm-stuff")
|
|
|
5202 (my-choosing-function "../other-dir/my-stuff")
|
|
|
5203 ((equal gnus-newsgroup-name "mail.misc") "mail-stuff"))
|
|
|
5204 @end lisp
|
|
|
5205
|
|
|
5206 We see that this is a list where each element is a list that has two
|
|
|
5207 elements---the @dfn{match} and the @dfn{file}. The match can either be
|
|
|
5208 a string (in which case it is used as a regexp to match on the article
|
|
|
5209 head); it can be a symbol (which will be called as a function with the
|
|
|
5210 group name as a parameter); or it can be a list (which will be
|
|
|
5211 @code{eval}ed). If any of these actions have a non-@code{nil} result,
|
|
|
5212 the @dfn{file} will be used as a default prompt. In addition, the
|
|
|
5213 result of the operation itself will be used if the function or form
|
|
|
5214 called returns a string or a list of strings.
|
|
|
5215
|
|
|
5216 You basically end up with a list of file names that might be used when
|
|
|
5217 saving the current article. (All ``matches'' will be used.) You will
|
|
|
5218 then be prompted for what you really want to use as a name, with file
|
|
|
5219 name completion over the results from applying this variable.
|
|
|
5220
|
|
|
5221 This variable is @code{((gnus-article-archive-name))} by default, which
|
|
|
5222 means that Gnus will look at the articles it saves for an
|
|
|
5223 @code{Archive-name} line and use that as a suggestion for the file
|
|
|
5224 name.
|
|
|
5225
|
|
|
5226 @vindex gnus-use-long-file-name
|
|
|
5227 Finally, you have the @code{gnus-use-long-file-name} variable. If it is
|
|
|
5228 @code{nil}, all the preceding functions will replace all periods
|
|
|
5229 (@samp{.}) in the group names with slashes (@samp{/})---which means that
|
|
|
5230 the functions will generate hierarchies of directories instead of having
|
|
|
5231 all the files in the toplevel directory
|
|
|
5232 (@file{~/News/alt/andrea-dworkin} instead of
|
|
|
5233 @file{~/News/alt.andrea-dworkin}.) This variable is @code{t} by default
|
|
|
5234 on most systems. However, for historical reasons, this is @code{nil} on
|
|
|
5235 Xenix and usg-unix-v machines by default.
|
|
|
5236
|
|
|
5237 This function also affects kill and score file names. If this variable
|
|
|
5238 is a list, and the list contains the element @code{not-score}, long file
|
|
|
5239 names will not be used for score files, if it contains the element
|
|
|
5240 @code{not-save}, long file names will not be used for saving, and if it
|
|
|
5241 contains the element @code{not-kill}, long file names will not be used
|
|
|
5242 for kill files.
|
|
|
5243
|
|
|
5244 If you'd like to save articles in a hierarchy that looks something like
|
|
|
5245 a spool, you could
|
|
|
5246
|
|
|
5247 @lisp
|
|
|
5248 (setq gnus-use-long-file-name '(not-save)) ; to get a hierarchy
|
|
|
5249 (setq gnus-default-article-save 'gnus-summary-save-in-file) ; no encoding
|
|
|
5250 @end lisp
|
|
|
5251
|
|
|
5252 Then just save with @kbd{o}. You'd then read this hierarchy with
|
|
|
5253 ephemeral @code{nneething} groups---@kbd{G D} in the group buffer, and
|
|
|
5254 the toplevel directory as the argument (@file{~/News/}). Then just walk
|
|
|
5255 around to the groups/directories with @code{nneething}.
|
|
|
5256
|
|
|
5257
|
|
|
5258 @node Decoding Articles
|
|
|
5259 @section Decoding Articles
|
|
|
5260 @cindex decoding articles
|
|
|
5261
|
|
|
5262 Sometime users post articles (or series of articles) that have been
|
|
|
5263 encoded in some way or other. Gnus can decode them for you.
|
|
|
5264
|
|
|
5265 @menu
|
|
|
5266 * Uuencoded Articles:: Uudecode articles.
|
|
|
5267 * Shared Articles:: Unshar articles.
|
|
|
5268 * PostScript Files:: Split PostScript.
|
|
|
5269 * Decoding Variables:: Variables for a happy decoding.
|
|
|
5270 * Viewing Files:: You want to look at the result of the decoding?
|
|
|
5271 @end menu
|
|
|
5272
|
|
|
5273 All these functions use the process/prefix convention
|
|
|
5274 (@pxref{Process/Prefix}) for finding out what articles to work on, with
|
|
|
5275 the extension that a ``single article'' means ``a single series''. Gnus
|
|
|
5276 can find out by itself what articles belong to a series, decode all the
|
|
|
5277 articles and unpack/view/save the resulting file(s).
|
|
|
5278
|
|
|
5279 Gnus guesses what articles are in the series according to the following
|
|
|
5280 simplish rule: The subjects must be (nearly) identical, except for the
|
|
|
5281 last two numbers of the line. (Spaces are largely ignored, however.)
|
|
|
5282
|
|
|
5283 For example: If you choose a subject called @samp{cat.gif (2/3)}, Gnus
|
|
|
5284 will find all the articles that match the regexp @samp{^cat.gif
|
|
|
5285 ([0-9]+/[0-9]+).*$}.
|
|
|
5286
|
|
|
5287 Subjects that are nonstandard, like @samp{cat.gif (2/3) Part 6 of a
|
|
|
5288 series}, will not be properly recognized by any of the automatic viewing
|
|
|
5289 commands, and you have to mark the articles manually with @kbd{#}.
|
|
|
5290
|
|
|
5291
|
|
|
5292 @node Uuencoded Articles
|
|
|
5293 @subsection Uuencoded Articles
|
|
|
5294 @cindex uudecode
|
|
|
5295 @cindex uuencoded articles
|
|
|
5296
|
|
|
5297 @table @kbd
|
|
|
5298
|
|
|
5299 @item X u
|
|
|
5300 @kindex X u (Summary)
|
|
|
5301 @findex gnus-uu-decode-uu
|
|
|
5302 Uudecodes the current series (@code{gnus-uu-decode-uu}).
|
|
|
5303
|
|
|
5304 @item X U
|
|
|
5305 @kindex X U (Summary)
|
|
|
5306 @findex gnus-uu-decode-uu-and-save
|
|
|
5307 Uudecodes and saves the current series
|
|
|
5308 (@code{gnus-uu-decode-uu-and-save}).
|
|
|
5309
|
|
|
5310 @item X v u
|
|
|
5311 @kindex X v u (Summary)
|
|
|
5312 @findex gnus-uu-decode-uu-view
|
|
|
5313 Uudecodes and views the current series (@code{gnus-uu-decode-uu-view}).
|
|
|
5314
|
|
|
5315 @item X v U
|
|
|
5316 @kindex X v U (Summary)
|
|
|
5317 @findex gnus-uu-decode-uu-and-save-view
|
|
|
5318 Uudecodes, views and saves the current series
|
|
|
5319 (@code{gnus-uu-decode-uu-and-save-view}).
|
|
|
5320 @end table
|
|
|
5321
|
|
|
5322 Remember that these all react to the presence of articles marked with
|
|
|
5323 the process mark. If, for instance, you'd like to decode and save an
|
|
|
5324 entire newsgroup, you'd typically do @kbd{M P a}
|
|
|
5325 (@code{gnus-uu-mark-all}) and then @kbd{X U}
|
|
|
5326 (@code{gnus-uu-decode-uu-and-save}).
|
|
|
5327
|
|
|
5328 All this is very much different from how @code{gnus-uu} worked with
|
|
|
5329 @sc{gnus 4.1}, where you had explicit keystrokes for everything under
|
|
|
5330 the sun. This version of @code{gnus-uu} generally assumes that you mark
|
|
|
5331 articles in some way (@pxref{Setting Process Marks}) and then press
|
|
|
5332 @kbd{X u}.
|
|
|
5333
|
|
|
5334 @vindex gnus-uu-notify-files
|
|
|
5335 Note: When trying to decode articles that have names matching
|
|
|
5336 @code{gnus-uu-notify-files}, which is hard-coded to
|
|
|
5337 @samp{[Cc][Ii][Nn][Dd][Yy][0-9]+.\\(gif\\|jpg\\)}, @code{gnus-uu} will
|
|
|
5338 automatically post an article on @samp{comp.unix.wizards} saying that
|
|
|
5339 you have just viewed the file in question. This feature can't be turned
|
|
|
5340 off.
|
|
|
5341
|
|
|
5342
|
|
|
5343 @node Shared Articles
|
|
|
5344 @subsection Shared Articles
|
|
|
5345 @cindex unshar
|
|
|
5346 @cindex shared articles
|
|
|
5347
|
|
|
5348 @table @kbd
|
|
|
5349
|
|
|
5350 @item X s
|
|
|
5351 @kindex X s (Summary)
|
|
|
5352 @findex gnus-uu-decode-unshar
|
|
|
5353 Unshars the current series (@code{gnus-uu-decode-unshar}).
|
|
|
5354
|
|
|
5355 @item X S
|
|
|
5356 @kindex X S (Summary)
|
|
|
5357 @findex gnus-uu-decode-unshar-and-save
|
|
|
5358 Unshars and saves the current series (@code{gnus-uu-decode-unshar-and-save}).
|
|
|
5359
|
|
|
5360 @item X v s
|
|
|
5361 @kindex X v s (Summary)
|
|
|
5362 @findex gnus-uu-decode-unshar-view
|
|
|
5363 Unshars and views the current series (@code{gnus-uu-decode-unshar-view}).
|
|
|
5364
|
|
|
5365 @item X v S
|
|
|
5366 @kindex X v S (Summary)
|
|
|
5367 @findex gnus-uu-decode-unshar-and-save-view
|
|
|
5368 Unshars, views and saves the current series
|
|
|
5369 (@code{gnus-uu-decode-unshar-and-save-view}).
|
|
|
5370 @end table
|
|
|
5371
|
|
|
5372
|
|
|
5373 @node PostScript Files
|
|
|
5374 @subsection PostScript Files
|
|
|
5375 @cindex PostScript
|
|
|
5376
|
|
|
5377 @table @kbd
|
|
|
5378
|
|
|
5379 @item X p
|
|
|
5380 @kindex X p (Summary)
|
|
|
5381 @findex gnus-uu-decode-postscript
|
|
|
5382 Unpack the current PostScript series (@code{gnus-uu-decode-postscript}).
|
|
|
5383
|
|
|
5384 @item X P
|
|
|
5385 @kindex X P (Summary)
|
|
|
5386 @findex gnus-uu-decode-postscript-and-save
|
|
|
5387 Unpack and save the current PostScript series
|
|
|
5388 (@code{gnus-uu-decode-postscript-and-save}).
|
|
|
5389
|
|
|
5390 @item X v p
|
|
|
5391 @kindex X v p (Summary)
|
|
|
5392 @findex gnus-uu-decode-postscript-view
|
|
|
5393 View the current PostScript series
|
|
|
5394 (@code{gnus-uu-decode-postscript-view}).
|
|
|
5395
|
|
|
5396 @item X v P
|
|
|
5397 @kindex X v P (Summary)
|
|
|
5398 @findex gnus-uu-decode-postscript-and-save-view
|
|
|
5399 View and save the current PostScript series
|
|
|
5400 (@code{gnus-uu-decode-postscript-and-save-view}).
|
|
|
5401 @end table
|
|
|
5402
|
|
|
5403
|
|
|
5404 @node Decoding Variables
|
|
|
5405 @subsection Decoding Variables
|
|
|
5406
|
|
|
5407 Adjective, not verb.
|
|
|
5408
|
|
|
5409 @menu
|
|
|
5410 * Rule Variables:: Variables that say how a file is to be viewed.
|
|
|
5411 * Other Decode Variables:: Other decode variables.
|
|
|
5412 * Uuencoding and Posting:: Variables for customizing uuencoding.
|
|
|
5413 @end menu
|
|
|
5414
|
|
|
5415
|
|
|
5416 @node Rule Variables
|
|
|
5417 @subsubsection Rule Variables
|
|
|
5418 @cindex rule variables
|
|
|
5419
|
|
|
5420 Gnus uses @dfn{rule variables} to decide how to view a file. All these
|
|
|
5421 variables are on the form
|
|
|
5422
|
|
|
5423 @lisp
|
|
|
5424 (list '(regexp1 command2)
|
|
|
5425 '(regexp2 command2)
|
|
|
5426 ...)
|
|
|
5427 @end lisp
|
|
|
5428
|
|
|
5429 @table @code
|
|
|
5430
|
|
|
5431 @item gnus-uu-user-view-rules
|
|
|
5432 @vindex gnus-uu-user-view-rules
|
|
|
5433 @cindex sox
|
|
|
5434 This variable is consulted first when viewing files. If you wish to use,
|
|
|
5435 for instance, @code{sox} to convert an @samp{.au} sound file, you could
|
|
|
5436 say something like:
|
|
|
5437 @lisp
|
|
16
|
5438 (setq gnus-uu-user-view-rules
|
|
|
5439 (list '(\"\\\\.au$\" \"sox %s -t .aiff > /dev/audio\")))
|
|
0
|
5440 @end lisp
|
|
|
5441
|
|
|
5442 @item gnus-uu-user-view-rules-end
|
|
|
5443 @vindex gnus-uu-user-view-rules-end
|
|
|
5444 This variable is consulted if Gnus couldn't make any matches from the
|
|
|
5445 user and default view rules.
|
|
|
5446
|
|
|
5447 @item gnus-uu-user-archive-rules
|
|
|
5448 @vindex gnus-uu-user-archive-rules
|
|
|
5449 This variable can be used to say what commands should be used to unpack
|
|
|
5450 archives.
|
|
|
5451 @end table
|
|
|
5452
|
|
|
5453
|
|
|
5454 @node Other Decode Variables
|
|
|
5455 @subsubsection Other Decode Variables
|
|
|
5456
|
|
|
5457 @table @code
|
|
|
5458 @vindex gnus-uu-grabbed-file-functions
|
|
|
5459
|
|
|
5460 @item gnus-uu-grabbed-file-functions
|
|
|
5461 All functions in this list will be called right each file has been
|
|
|
5462 successfully decoded---so that you can move or view files right away,
|
|
|
5463 and don't have to wait for all files to be decoded before you can do
|
|
|
5464 anything. Ready-made functions you can put in this list are:
|
|
|
5465
|
|
|
5466 @table @code
|
|
|
5467
|
|
|
5468 @item gnus-uu-grab-view
|
|
|
5469 @findex gnus-uu-grab-view
|
|
|
5470 View the file.
|
|
|
5471
|
|
|
5472 @item gnus-uu-grab-move
|
|
|
5473 @findex gnus-uu-grab-move
|
|
|
5474 Move the file (if you're using a saving function.)
|
|
|
5475 @end table
|
|
|
5476
|
|
16
|
5477 @item gnus-uu-be-dangerous
|
|
|
5478 @vindex gnus-uu-be-dangerous
|
|
|
5479 Specifies what to do if unusual situations arise during decoding. If
|
|
|
5480 @code{nil}, be as conservative as possible. If @code{t}, ignore things
|
|
|
5481 that didn't work, and overwrite existing files. Otherwise, ask each
|
|
|
5482 time.
|
|
|
5483
|
|
0
|
5484 @item gnus-uu-ignore-files-by-name
|
|
|
5485 @vindex gnus-uu-ignore-files-by-name
|
|
|
5486 Files with name matching this regular expression won't be viewed.
|
|
|
5487
|
|
|
5488 @item gnus-uu-ignore-files-by-type
|
|
|
5489 @vindex gnus-uu-ignore-files-by-type
|
|
|
5490 Files with a @sc{mime} type matching this variable won't be viewed.
|
|
|
5491 Note that Gnus tries to guess what type the file is based on the name.
|
|
|
5492 @code{gnus-uu} is not a @sc{mime} package (yet), so this is slightly
|
|
|
5493 kludgey.
|
|
|
5494
|
|
|
5495 @item gnus-uu-tmp-dir
|
|
|
5496 @vindex gnus-uu-tmp-dir
|
|
|
5497 Where @code{gnus-uu} does its work.
|
|
|
5498
|
|
|
5499 @item gnus-uu-do-not-unpack-archives
|
|
|
5500 @vindex gnus-uu-do-not-unpack-archives
|
|
|
5501 Non-@code{nil} means that @code{gnus-uu} won't peek inside archives
|
|
|
5502 looking for files to display.
|
|
|
5503
|
|
|
5504 @item gnus-uu-view-and-save
|
|
|
5505 @vindex gnus-uu-view-and-save
|
|
|
5506 Non-@code{nil} means that the user will always be asked to save a file
|
|
|
5507 after viewing it.
|
|
|
5508
|
|
|
5509 @item gnus-uu-ignore-default-view-rules
|
|
|
5510 @vindex gnus-uu-ignore-default-view-rules
|
|
|
5511 Non-@code{nil} means that @code{gnus-uu} will ignore the default viewing
|
|
|
5512 rules.
|
|
|
5513
|
|
|
5514 @item gnus-uu-ignore-default-archive-rules
|
|
|
5515 @vindex gnus-uu-ignore-default-archive-rules
|
|
|
5516 Non-@code{nil} means that @code{gnus-uu} will ignore the default archive
|
|
|
5517 unpacking commands.
|
|
|
5518
|
|
|
5519 @item gnus-uu-kill-carriage-return
|
|
|
5520 @vindex gnus-uu-kill-carriage-return
|
|
|
5521 Non-@code{nil} means that @code{gnus-uu} will strip all carriage returns
|
|
|
5522 from articles.
|
|
|
5523
|
|
|
5524 @item gnus-uu-unmark-articles-not-decoded
|
|
|
5525 @vindex gnus-uu-unmark-articles-not-decoded
|
|
|
5526 Non-@code{nil} means that @code{gnus-uu} will mark articles that were
|
|
|
5527 unsuccessfully decoded as unread.
|
|
|
5528
|
|
|
5529 @item gnus-uu-correct-stripped-uucode
|
|
|
5530 @vindex gnus-uu-correct-stripped-uucode
|
|
|
5531 Non-@code{nil} means that @code{gnus-uu} will @emph{try} to fix
|
|
|
5532 uuencoded files that have had trailing spaces deleted.
|
|
|
5533
|
|
|
5534 @item gnus-uu-view-with-metamail
|
|
|
5535 @vindex gnus-uu-view-with-metamail
|
|
|
5536 @cindex metamail
|
|
|
5537 Non-@code{nil} means that @code{gnus-uu} will ignore the viewing
|
|
|
5538 commands defined by the rule variables and just fudge a @sc{mime}
|
|
|
5539 content type based on the file name. The result will be fed to
|
|
|
5540 @code{metamail} for viewing.
|
|
|
5541
|
|
|
5542 @item gnus-uu-save-in-digest
|
|
|
5543 @vindex gnus-uu-save-in-digest
|
|
|
5544 Non-@code{nil} means that @code{gnus-uu}, when asked to save without
|
|
|
5545 decoding, will save in digests. If this variable is @code{nil},
|
|
|
5546 @code{gnus-uu} will just save everything in a file without any
|
|
|
5547 embellishments. The digesting almost conforms to RFC1153---no easy way
|
|
|
5548 to specify any meaningful volume and issue numbers were found, so I
|
|
|
5549 simply dropped them.
|
|
|
5550
|
|
|
5551 @end table
|
|
|
5552
|
|
|
5553
|
|
|
5554 @node Uuencoding and Posting
|
|
|
5555 @subsubsection Uuencoding and Posting
|
|
|
5556
|
|
|
5557 @table @code
|
|
|
5558
|
|
|
5559 @item gnus-uu-post-include-before-composing
|
|
|
5560 @vindex gnus-uu-post-include-before-composing
|
|
|
5561 Non-@code{nil} means that @code{gnus-uu} will ask for a file to encode
|
|
|
5562 before you compose the article. If this variable is @code{t}, you can
|
|
|
5563 either include an encoded file with @kbd{C-c C-i} or have one included
|
|
|
5564 for you when you post the article.
|
|
|
5565
|
|
|
5566 @item gnus-uu-post-length
|
|
|
5567 @vindex gnus-uu-post-length
|
|
|
5568 Maximum length of an article. The encoded file will be split into how
|
|
|
5569 many articles it takes to post the entire file.
|
|
|
5570
|
|
|
5571 @item gnus-uu-post-threaded
|
|
|
5572 @vindex gnus-uu-post-threaded
|
|
|
5573 Non-@code{nil} means that @code{gnus-uu} will post the encoded file in a
|
|
|
5574 thread. This may not be smart, as no other decoder I have seen are able
|
|
|
5575 to follow threads when collecting uuencoded articles. (Well, I have
|
|
|
5576 seen one package that does that---@code{gnus-uu}, but somehow, I don't
|
|
|
5577 think that counts...) Default is @code{nil}.
|
|
|
5578
|
|
|
5579 @item gnus-uu-post-separate-description
|
|
|
5580 @vindex gnus-uu-post-separate-description
|
|
|
5581 Non-@code{nil} means that the description will be posted in a separate
|
|
|
5582 article. The first article will typically be numbered (0/x). If this
|
|
|
5583 variable is @code{nil}, the description the user enters will be included
|
|
|
5584 at the beginning of the first article, which will be numbered (1/x).
|
|
|
5585 Default is @code{t}.
|
|
|
5586
|
|
|
5587 @end table
|
|
|
5588
|
|
|
5589
|
|
|
5590 @node Viewing Files
|
|
|
5591 @subsection Viewing Files
|
|
|
5592 @cindex viewing files
|
|
|
5593 @cindex pseudo-articles
|
|
|
5594
|
|
|
5595 After decoding, if the file is some sort of archive, Gnus will attempt
|
|
|
5596 to unpack the archive and see if any of the files in the archive can be
|
|
|
5597 viewed. For instance, if you have a gzipped tar file @file{pics.tar.gz}
|
|
|
5598 containing the files @file{pic1.jpg} and @file{pic2.gif}, Gnus will
|
|
|
5599 uncompress and de-tar the main file, and then view the two pictures.
|
|
|
5600 This unpacking process is recursive, so if the archive contains archives
|
|
|
5601 of archives, it'll all be unpacked.
|
|
|
5602
|
|
|
5603 Finally, Gnus will normally insert a @dfn{pseudo-article} for each
|
|
|
5604 extracted file into the summary buffer. If you go to these
|
|
|
5605 ``articles'', you will be prompted for a command to run (usually Gnus
|
|
|
5606 will make a suggestion), and then the command will be run.
|
|
|
5607
|
|
|
5608 @vindex gnus-view-pseudo-asynchronously
|
|
|
5609 If @code{gnus-view-pseudo-asynchronously} is @code{nil}, Emacs will wait
|
|
|
5610 until the viewing is done before proceeding.
|
|
|
5611
|
|
|
5612 @vindex gnus-view-pseudos
|
|
|
5613 If @code{gnus-view-pseudos} is @code{automatic}, Gnus will not insert
|
|
|
5614 the pseudo-articles into the summary buffer, but view them
|
|
|
5615 immediately. If this variable is @code{not-confirm}, the user won't even
|
|
|
5616 be asked for a confirmation before viewing is done.
|
|
|
5617
|
|
|
5618 @vindex gnus-view-pseudos-separately
|
|
|
5619 If @code{gnus-view-pseudos-separately} is non-@code{nil}, one
|
|
|
5620 pseudo-article will be created for each file to be viewed. If
|
|
|
5621 @code{nil}, all files that use the same viewing command will be given as
|
|
|
5622 a list of parameters to that command.
|
|
|
5623
|
|
|
5624 @vindex gnus-insert-pseudo-articles
|
|
|
5625 If @code{gnus-insert-pseudo-articles} is non-@code{nil}, insert
|
|
|
5626 pseudo-articles when decoding. It is @code{t} by default.
|
|
|
5627
|
|
|
5628 So; there you are, reading your @emph{pseudo-articles} in your
|
|
|
5629 @emph{virtual newsgroup} from the @emph{virtual server}; and you think:
|
|
|
5630 Why isn't anything real anymore? How did we get here?
|
|
|
5631
|
|
|
5632
|
|
|
5633 @node Article Treatment
|
|
|
5634 @section Article Treatment
|
|
|
5635
|
|
|
5636 Reading through this huge manual, you may have quite forgotten that the
|
|
|
5637 object of newsreaders are to actually, like, read what people have
|
|
|
5638 written. Reading articles. Unfortunately, people are quite bad at
|
|
|
5639 writing, so there are tons of functions and variables to make reading
|
|
|
5640 these articles easier.
|
|
|
5641
|
|
|
5642 @menu
|
|
|
5643 * Article Highlighting:: You want to make the article look like fruit salad.
|
|
16
|
5644 * Article Fontisizing:: Making emphasized text look niced.
|
|
0
|
5645 * Article Hiding:: You also want to make certain info go away.
|
|
|
5646 * Article Washing:: Lots of way-neat functions to make life better.
|
|
|
5647 * Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
|
|
|
5648 * Article Date:: Grumble, UT!
|
|
16
|
5649 * Article Signature:: What is a signature?
|
|
0
|
5650 @end menu
|
|
|
5651
|
|
|
5652
|
|
|
5653 @node Article Highlighting
|
|
|
5654 @subsection Article Highlighting
|
|
|
5655 @cindex highlight
|
|
|
5656
|
|
|
5657 Not only do you want your article buffer to look like fruit salad, but
|
|
|
5658 you want it to look like technicolor fruit salad.
|
|
|
5659
|
|
|
5660 @table @kbd
|
|
|
5661
|
|
|
5662 @item W H a
|
|
|
5663 @kindex W H a (Summary)
|
|
|
5664 @findex gnus-article-highlight
|
|
|
5665 Highlight the current article (@code{gnus-article-highlight}).
|
|
|
5666
|
|
|
5667 @item W H h
|
|
|
5668 @kindex W H h (Summary)
|
|
|
5669 @findex gnus-article-highlight-headers
|
|
|
5670 @vindex gnus-header-face-alist
|
|
|
5671 Highlight the headers (@code{gnus-article-highlight-headers}). The
|
|
|
5672 highlighting will be done according to the @code{gnus-header-face-alist}
|
|
|
5673 variable, which is a list where each element has the form @var{(regexp
|
|
|
5674 name content)}. @var{regexp} is a regular expression for matching the
|
|
|
5675 header, @var{name} is the face used for highlighting the header name and
|
|
|
5676 @var{content} is the face for highlighting the header value. The first
|
|
|
5677 match made will be used. Note that @var{regexp} shouldn't have @samp{^}
|
|
|
5678 prepended---Gnus will add one.
|
|
|
5679
|
|
|
5680 @item W H c
|
|
|
5681 @kindex W H c (Summary)
|
|
|
5682 @findex gnus-article-highlight-citation
|
|
|
5683 Highlight cited text (@code{gnus-article-highlight-citation}).
|
|
|
5684
|
|
|
5685 Some variables to customize the citation highlights:
|
|
|
5686
|
|
|
5687 @table @code
|
|
|
5688 @vindex gnus-cite-parse-max-size
|
|
|
5689
|
|
|
5690 @item gnus-cite-parse-max-size
|
|
|
5691 If the article size if bigger than this variable (which is 25000 by
|
|
|
5692 default), no citation highlighting will be performed.
|
|
|
5693
|
|
|
5694 @item gnus-cite-prefix-regexp
|
|
|
5695 @vindex gnus-cite-prefix-regexp
|
|
|
5696 Regexp matching the longest possible citation prefix on a line.
|
|
|
5697
|
|
|
5698 @item gnus-cite-max-prefix
|
|
|
5699 @vindex gnus-cite-max-prefix
|
|
|
5700 Maximum possible length for a citation prefix (default 20).
|
|
|
5701
|
|
|
5702 @item gnus-cite-face-list
|
|
|
5703 @vindex gnus-cite-face-list
|
|
|
5704 List of faces used for highlighting citations. When there are citations
|
|
|
5705 from multiple articles in the same message, Gnus will try to give each
|
|
|
5706 citation from each article its own face. This should make it easier to
|
|
|
5707 see who wrote what.
|
|
|
5708
|
|
|
5709 @item gnus-supercite-regexp
|
|
|
5710 @vindex gnus-supercite-regexp
|
|
|
5711 Regexp matching normal Supercite attribution lines.
|
|
|
5712
|
|
|
5713 @item gnus-supercite-secondary-regexp
|
|
|
5714 @vindex gnus-supercite-secondary-regexp
|
|
|
5715 Regexp matching mangled Supercite attribution lines.
|
|
|
5716
|
|
|
5717 @item gnus-cite-minimum-match-count
|
|
|
5718 @vindex gnus-cite-minimum-match-count
|
|
|
5719 Minimum number of identical prefixes we have to see before we believe
|
|
|
5720 that it's a citation.
|
|
|
5721
|
|
|
5722 @item gnus-cite-attribution-prefix
|
|
|
5723 @vindex gnus-cite-attribution-prefix
|
|
|
5724 Regexp matching the beginning of an attribution line.
|
|
|
5725
|
|
|
5726 @item gnus-cite-attribution-suffix
|
|
|
5727 @vindex gnus-cite-attribution-suffix
|
|
|
5728 Regexp matching the end of an attribution line.
|
|
|
5729
|
|
|
5730 @item gnus-cite-attribution-face
|
|
|
5731 @vindex gnus-cite-attribution-face
|
|
|
5732 Face used for attribution lines. It is merged with the face for the
|
|
|
5733 cited text belonging to the attribution.
|
|
|
5734
|
|
|
5735 @end table
|
|
|
5736
|
|
|
5737
|
|
|
5738 @item W H s
|
|
|
5739 @kindex W H s (Summary)
|
|
|
5740 @vindex gnus-signature-separator
|
|
|
5741 @vindex gnus-signature-face
|
|
|
5742 @findex gnus-article-highlight-signature
|
|
|
5743 Highlight the signature (@code{gnus-article-highlight-signature}).
|
|
16
|
5744 Everything after @code{gnus-signature-separator} (@pxref{Article
|
|
|
5745 Signature}) in an article will be considered a signature and will be
|
|
|
5746 highlighted with @code{gnus-signature-face}, which is @code{italic} by
|
|
|
5747 default.
|
|
|
5748
|
|
|
5749 @end table
|
|
|
5750
|
|
|
5751
|
|
|
5752 @node Article Fontisizing
|
|
|
5753 @subsection Article Fontisizing
|
|
|
5754 @cindex emphasis
|
|
|
5755 @cindex article emphasis
|
|
|
5756
|
|
|
5757 @findex gnus-article-emphasize
|
|
|
5758 @kindex W e (Summary)
|
|
|
5759 People commonly add emphasis to words in news articles by writing things
|
|
|
5760 like @samp{_this_} or @samp{*this*}. Gnus can make this look nicer by
|
|
|
5761 running the article through the @kbd{W e}
|
|
|
5762 (@code{gnus-article-emphasize}) command.
|
|
|
5763
|
|
|
5764 @vindex gnus-article-emphasis
|
|
|
5765 How the emphasis is computed is controlled by the
|
|
|
5766 @code{gnus-article-emphasis} variable. This is an alist where the first
|
|
|
5767 element is a regular expression to be matched. The second is a number
|
|
|
5768 that says what regular expression grouping used to find the entire
|
|
|
5769 emphasized word. The third is a number that says what regexp grouping
|
|
|
5770 should be displayed and highlighted. (The text between these two
|
|
|
5771 groupings will be hidden.) The fourth is the face used for
|
|
|
5772 highlighting.
|
|
|
5773
|
|
|
5774 @lisp
|
|
|
5775 (setq gnus-article-emphasis
|
|
|
5776 '(("_\\(\\w+\\)_" 0 1 gnus-emphasis-underline)
|
|
|
5777 ("\\*\\(\\w+\\)\\*" 0 1 gnus-emphasis-bold)))
|
|
|
5778 @end lisp
|
|
|
5779
|
|
|
5780 @vindex gnus-emphasis-underline
|
|
|
5781 @vindex gnus-emphasis-bold
|
|
|
5782 @vindex gnus-emphasis-italic
|
|
|
5783 @vindex gnus-emphasis-underline-bold
|
|
|
5784 @vindex gnus-emphasis-underline-italic
|
|
|
5785 @vindex gnus-emphasis-bold-italic
|
|
|
5786 @vindex gnus-emphasis-underline-bold-italic
|
|
|
5787 By default, there are seven rules, and they use the following faces:
|
|
|
5788 @code{gnus-emphasis-bold}, @code{gnus-emphasis-italic},
|
|
|
5789 @code{gnus-emphasis-underline}, @code{gnus-emphasis-bold-italic},
|
|
|
5790 @code{gnus-emphasis-underline-italic},
|
|
|
5791 @code{gnus-emphasis-undeline-bold}, and
|
|
|
5792 @code{gnus-emphasis-underline-bold-italic}.
|
|
|
5793
|
|
|
5794 If you want to change these faces, you can either use @kbd{M-x
|
|
|
5795 customize}, or you can use @code{copy-face}. For instance, if you want
|
|
|
5796 to make @code{gnus-emphasis-italic} use a red face instead, you could
|
|
|
5797 say something like:
|
|
|
5798
|
|
|
5799 @lisp
|
|
|
5800 (copy-face 'red 'gnus-emphasis-italic)
|
|
|
5801 @end lisp
|
|
0
|
5802
|
|
|
5803
|
|
|
5804 @node Article Hiding
|
|
|
5805 @subsection Article Hiding
|
|
|
5806 @cindex article hiding
|
|
|
5807
|
|
|
5808 Or rather, hiding certain things in each article. There usually is much
|
|
|
5809 too much cruft in most articles.
|
|
|
5810
|
|
|
5811 @table @kbd
|
|
|
5812
|
|
|
5813 @item W W a
|
|
|
5814 @kindex W W a (Summary)
|
|
|
5815 @findex gnus-article-hide
|
|
|
5816 Do maximum hiding on the summary buffer (@kbd{gnus-article-hide}).
|
|
|
5817
|
|
|
5818 @item W W h
|
|
|
5819 @kindex W W h (Summary)
|
|
|
5820 @findex gnus-article-hide-headers
|
|
|
5821 Hide headers (@code{gnus-article-hide-headers}). @xref{Hiding
|
|
|
5822 Headers}.
|
|
|
5823
|
|
|
5824 @item W W b
|
|
|
5825 @kindex W W b (Summary)
|
|
|
5826 @findex gnus-article-hide-boring-headers
|
|
|
5827 Hide headers that aren't particularly interesting
|
|
|
5828 (@code{gnus-article-hide-boring-headers}). @xref{Hiding Headers}.
|
|
|
5829
|
|
|
5830 @item W W s
|
|
|
5831 @kindex W W s (Summary)
|
|
|
5832 @findex gnus-article-hide-signature
|
|
16
|
5833 Hide signature (@code{gnus-article-hide-signature}). @xref{Article
|
|
|
5834 Signature}.
|
|
0
|
5835
|
|
|
5836 @item W W p
|
|
|
5837 @kindex W W p (Summary)
|
|
|
5838 @findex gnus-article-hide-pgp
|
|
|
5839 Hide @sc{pgp} signatures (@code{gnus-article-hide-pgp}).
|
|
|
5840
|
|
2
|
5841 @item W W P
|
|
|
5842 @kindex W W P (Summary)
|
|
|
5843 @findex gnus-article-hide-pem
|
|
16
|
5844 Hide @sc{pem} (privacy enhanced messages) gruft
|
|
2
|
5845 (@code{gnus-article-hide-pem}).
|
|
|
5846
|
|
0
|
5847 @item W W c
|
|
|
5848 @kindex W W c (Summary)
|
|
|
5849 @findex gnus-article-hide-citation
|
|
|
5850 Hide citation (@code{gnus-article-hide-citation}). Some variables for
|
|
|
5851 customizing the hiding:
|
|
|
5852
|
|
|
5853 @table @code
|
|
|
5854
|
|
|
5855 @item gnus-cite-hide-percentage
|
|
|
5856 @vindex gnus-cite-hide-percentage
|
|
|
5857 If the cited text is of a bigger percentage than this variable (default
|
|
|
5858 50), hide the cited text.
|
|
|
5859
|
|
|
5860 @item gnus-cite-hide-absolute
|
|
|
5861 @vindex gnus-cite-hide-absolute
|
|
|
5862 The cited text must be have at least this length (default 10) before it
|
|
|
5863 is hidden.
|
|
|
5864
|
|
|
5865 @item gnus-cited-text-button-line-format
|
|
|
5866 @vindex gnus-cited-text-button-line-format
|
|
|
5867 Gnus adds buttons show where the cited text has been hidden, and to
|
|
|
5868 allow toggle hiding the text. The format of the variable is specified
|
|
16
|
5869 by this format-like variable (@pxref{Formatting Variables}). These
|
|
|
5870 specs are legal:
|
|
0
|
5871
|
|
|
5872 @table @samp
|
|
|
5873 @item b
|
|
|
5874 Start point of the hidden text.
|
|
|
5875 @item e
|
|
|
5876 End point of the hidden text.
|
|
|
5877 @item l
|
|
|
5878 Length of the hidden text.
|
|
|
5879 @end table
|
|
|
5880
|
|
|
5881 @item gnus-cited-lines-visible
|
|
|
5882 @vindex gnus-cited-lines-visible
|
|
|
5883 The number of lines at the beginning of the cited text to leave shown.
|
|
|
5884
|
|
|
5885 @end table
|
|
|
5886
|
|
|
5887 @item W W C
|
|
|
5888 @kindex W W C (Summary)
|
|
|
5889 @findex gnus-article-hide-citation-in-followups
|
|
|
5890 Hide cited text in articles that aren't roots
|
|
|
5891 (@code{gnus-article-hide-citation-in-followups}). This isn't very
|
|
|
5892 useful as an interactive command, but might be a handy function to stick
|
|
|
5893 in @code{gnus-article-display-hook} (@pxref{Customizing Articles}).
|
|
|
5894
|
|
|
5895 @end table
|
|
|
5896
|
|
|
5897 All these ``hiding'' commands are toggles, but if you give a negative
|
|
|
5898 prefix to these commands, they will show what they have previously
|
|
|
5899 hidden. If you give a positive prefix, they will always hide.
|
|
|
5900
|
|
|
5901 Also @pxref{Article Highlighting} for further variables for
|
|
|
5902 citation customization.
|
|
|
5903
|
|
|
5904
|
|
|
5905 @node Article Washing
|
|
|
5906 @subsection Article Washing
|
|
|
5907 @cindex washing
|
|
|
5908 @cindex article washing
|
|
|
5909
|
|
|
5910 We call this ``article washing'' for a really good reason. Namely, the
|
|
|
5911 @kbd{A} key was taken, so we had to use the @kbd{W} key instead.
|
|
|
5912
|
|
|
5913 @dfn{Washing} is defined by us as ``changing something from something to
|
|
|
5914 something else'', but normally results in something looking better.
|
|
|
5915 Cleaner, perhaps.
|
|
|
5916
|
|
|
5917 @table @kbd
|
|
|
5918
|
|
|
5919 @item W l
|
|
|
5920 @kindex W l (Summary)
|
|
|
5921 @findex gnus-summary-stop-page-breaking
|
|
|
5922 Remove page breaks from the current article
|
|
|
5923 (@code{gnus-summary-stop-page-breaking}).
|
|
|
5924
|
|
|
5925 @item W r
|
|
|
5926 @kindex W r (Summary)
|
|
|
5927 @findex gnus-summary-caesar-message
|
|
|
5928 Do a Caesar rotate (rot13) on the article buffer
|
|
|
5929 (@code{gnus-summary-caesar-message}).
|
|
|
5930
|
|
|
5931 @item W t
|
|
|
5932 @kindex W t (Summary)
|
|
|
5933 @findex gnus-summary-toggle-header
|
|
|
5934 Toggle whether to display all headers in the article buffer
|
|
|
5935 (@code{gnus-summary-toggle-header}).
|
|
|
5936
|
|
|
5937 @item W v
|
|
|
5938 @kindex W v (Summary)
|
|
|
5939 @findex gnus-summary-verbose-header
|
|
|
5940 Toggle whether to display all headers in the article buffer permanently
|
|
|
5941 (@code{gnus-summary-verbose-header}).
|
|
|
5942
|
|
|
5943 @item W m
|
|
|
5944 @kindex W m (Summary)
|
|
|
5945 @findex gnus-summary-toggle-mime
|
|
|
5946 Toggle whether to run the article through @sc{mime} before displaying
|
|
|
5947 (@code{gnus-summary-toggle-mime}).
|
|
|
5948
|
|
|
5949 @item W o
|
|
|
5950 @kindex W o (Summary)
|
|
|
5951 @findex gnus-article-treat-overstrike
|
|
|
5952 Treat overstrike (@code{gnus-article-treat-overstrike}).
|
|
|
5953
|
|
|
5954 @item W w
|
|
|
5955 @kindex W w (Summary)
|
|
|
5956 @findex gnus-article-fill-cited-article
|
|
2
|
5957 Do word wrap (@code{gnus-article-fill-cited-article}). If you use this
|
|
|
5958 function in @code{gnus-article-display-hook}, it should be run fairly
|
|
|
5959 late and certainly after any highlighting.
|
|
0
|
5960
|
|
16
|
5961 You can give the command a numerical prefix to specify the width to use
|
|
|
5962 when filling.
|
|
|
5963
|
|
0
|
5964 @item W c
|
|
|
5965 @kindex W c (Summary)
|
|
|
5966 @findex gnus-article-remove-cr
|
|
|
5967 Remove CR (@code{gnus-article-remove-cr}).
|
|
|
5968
|
|
|
5969 @item W q
|
|
|
5970 @kindex W q (Summary)
|
|
|
5971 @findex gnus-article-de-quoted-unreadable
|
|
|
5972 Treat quoted-printable (@code{gnus-article-de-quoted-unreadable}).
|
|
|
5973
|
|
|
5974 @item W f
|
|
|
5975 @kindex W f (Summary)
|
|
|
5976 @cindex x-face
|
|
|
5977 @findex gnus-article-display-x-face
|
|
|
5978 @findex gnus-article-x-face-command
|
|
|
5979 @vindex gnus-article-x-face-command
|
|
|
5980 @vindex gnus-article-x-face-too-ugly
|
|
|
5981 Look for and display any X-Face headers
|
|
|
5982 (@code{gnus-article-display-x-face}). The command executed by this
|
|
2
|
5983 function is given by the @code{gnus-article-x-face-command} variable.
|
|
|
5984 If this variable is a string, this string will be executed in a
|
|
|
5985 sub-shell. If it is a function, this function will be called with the
|
|
|
5986 face as the argument. If the @code{gnus-article-x-face-too-ugly} (which
|
|
|
5987 is a regexp) matches the @code{From} header, the face will not be shown.
|
|
|
5988 The default action under Emacs is to fork off an @code{xv} to view the
|
|
|
5989 face; under XEmacs the default action is to display the face before the
|
|
|
5990 @code{From} header. (It's nicer if XEmacs has been compiled with X-Face
|
|
|
5991 support---that will make display somewhat faster. If there's no native
|
|
|
5992 X-Face support, Gnus will try to convert the @code{X-Face} header using
|
|
0
|
5993 external programs from the @code{pbmplus} package and friends.) If you
|
|
|
5994 want to have this function in the display hook, it should probably come
|
|
2
|
5995 last.
|
|
0
|
5996
|
|
|
5997 @item W b
|
|
|
5998 @kindex W b (Summary)
|
|
|
5999 @findex gnus-article-add-buttons
|
|
|
6000 Add clickable buttons to the article (@code{gnus-article-add-buttons}).
|
|
|
6001
|
|
|
6002 @item W B
|
|
|
6003 @kindex W B (Summary)
|
|
|
6004 @findex gnus-article-add-buttons-to-head
|
|
|
6005 Add clickable buttons to the article headers
|
|
|
6006 (@code{gnus-article-add-buttons-to-head}).
|
|
|
6007
|
|
16
|
6008 @item W E l
|
|
|
6009 @kindex W E l (Summary)
|
|
|
6010 @findex gnus-article-strip-leading-blank-lines
|
|
|
6011 Remove all blank lines from the beginning of the article
|
|
|
6012 (@code{gnus-article-strip-leading-blank-lines}).
|
|
|
6013
|
|
|
6014 @item W E m
|
|
|
6015 @kindex W E m (Summary)
|
|
|
6016 @findex gnus-article-strip-multiple-blank-lines
|
|
|
6017 Replace all blank lines with empty lines and then all multiple empty
|
|
|
6018 lines with a single empty line.
|
|
|
6019 (@code{gnus-article-strip-multiple-blank-lines}).
|
|
|
6020
|
|
|
6021 @item W E t
|
|
|
6022 @kindex W E t (Summary)
|
|
|
6023 @findex gnus-article-remove-trailing-blank-lines
|
|
|
6024 Remove all blank lines at the end of the article
|
|
|
6025 (@code{gnus-article-remove-trailing-blank-lines}).
|
|
|
6026
|
|
|
6027 @item W E a
|
|
|
6028 @kindex W E a (Summary)
|
|
|
6029 @findex gnus-article-strip-blank-lines
|
|
|
6030 Do all the three commands above
|
|
|
6031 (@code{gnus-article-strip-blank-lines}).
|
|
|
6032
|
|
36
|
6033 @item W E s
|
|
|
6034 @kindex W E s (Summary)
|
|
|
6035 @findex gnus-article-strip-leading-space
|
|
|
6036 Remove all white space from the beginning of all lines of the article
|
|
|
6037 body (@code{gnus-article-strip-leading-space}).
|
|
|
6038
|
|
0
|
6039 @end table
|
|
|
6040
|
|
|
6041
|
|
|
6042 @node Article Buttons
|
|
|
6043 @subsection Article Buttons
|
|
|
6044 @cindex buttons
|
|
|
6045
|
|
|
6046 People often include references to other stuff in articles, and it would
|
|
|
6047 be nice if Gnus could just fetch whatever it is that people talk about
|
|
|
6048 with the minimum of fuzz.
|
|
|
6049
|
|
|
6050 Gnus adds @dfn{buttons} to certain standard references by default:
|
|
|
6051 Well-formed URLs, mail addresses and Message-IDs. This is controlled by
|
|
|
6052 two variables, one that handles article bodies and one that handles
|
|
|
6053 article heads:
|
|
|
6054
|
|
|
6055 @table @code
|
|
|
6056
|
|
|
6057 @item gnus-button-alist
|
|
|
6058 @vindex gnus-button-alist
|
|
|
6059 This is an alist where each entry has this form:
|
|
|
6060
|
|
|
6061 @lisp
|
|
|
6062 (REGEXP BUTTON-PAR USE-P FUNCTION DATA-PAR)
|
|
|
6063 @end lisp
|
|
|
6064
|
|
|
6065 @table @var
|
|
|
6066
|
|
|
6067 @item regexp
|
|
|
6068 All text that match this regular expression will be considered an
|
|
|
6069 external reference. Here's a typical regexp that match embedded URLs:
|
|
|
6070 @samp{<URL:\\([^\n\r>]*\\)>}.
|
|
|
6071
|
|
|
6072 @item button-par
|
|
|
6073 Gnus has to know which parts of the match is to be highlighted. This is
|
|
|
6074 a number that says what sub-expression of the regexp that is to be
|
|
16
|
6075 highlighted. If you want it all highlighted, you use 0 here.
|
|
0
|
6076
|
|
|
6077 @item use-p
|
|
|
6078 This form will be @code{eval}ed, and if the result is non-@code{nil},
|
|
|
6079 this is considered a match. This is useful if you want extra sifting to
|
|
|
6080 avoid false matches.
|
|
|
6081
|
|
|
6082 @item function
|
|
|
6083 This function will be called when you click on this button.
|
|
|
6084
|
|
|
6085 @item data-par
|
|
|
6086 As with @var{button-par}, this is a sub-expression number, but this one
|
|
|
6087 says which part of the match is to be sent as data to @var{function}.
|
|
|
6088
|
|
|
6089 @end table
|
|
|
6090
|
|
|
6091 So the full entry for buttonizing URLs is then
|
|
|
6092
|
|
|
6093 @lisp
|
|
|
6094 ("<URL:\\([^\n\r>]*\\)>" 0 t gnus-button-url 1)
|
|
|
6095 @end lisp
|
|
|
6096
|
|
|
6097 @item gnus-header-button-alist
|
|
|
6098 @vindex gnus-header-button-alist
|
|
|
6099 This is just like the other alist, except that it is applied to the
|
|
|
6100 article head only, and that each entry has an additional element that is
|
|
|
6101 used to say what headers to apply the buttonize coding to:
|
|
|
6102
|
|
|
6103 @lisp
|
|
|
6104 (HEADER REGEXP BUTTON-PAR USE-P FUNCTION DATA-PAR)
|
|
|
6105 @end lisp
|
|
|
6106
|
|
|
6107 @var{header} is a regular expression.
|
|
|
6108
|
|
|
6109 @item gnus-button-url-regexp
|
|
|
6110 @vindex gnus-button-url-regexp
|
|
|
6111 A regular expression that matches embedded URLs. It is used in the
|
|
|
6112 default values of the variables above.
|
|
|
6113
|
|
|
6114 @item gnus-article-button-face
|
|
|
6115 @vindex gnus-article-button-face
|
|
16
|
6116 Face used on buttons.
|
|
0
|
6117
|
|
|
6118 @item gnus-article-mouse-face
|
|
|
6119 @vindex gnus-article-mouse-face
|
|
|
6120 Face is used when the mouse cursor is over a button.
|
|
|
6121
|
|
|
6122 @end table
|
|
|
6123
|
|
|
6124
|
|
|
6125 @node Article Date
|
|
|
6126 @subsection Article Date
|
|
|
6127
|
|
|
6128 The date is most likely generated in some obscure timezone you've never
|
|
|
6129 heard of, so it's quite nice to be able to find out what the time was
|
|
|
6130 when the article was sent.
|
|
|
6131
|
|
|
6132 @table @kbd
|
|
|
6133
|
|
|
6134 @item W T u
|
|
|
6135 @kindex W T u (Summary)
|
|
|
6136 @findex gnus-article-date-ut
|
|
|
6137 Display the date in UT (aka. GMT, aka ZULU)
|
|
|
6138 (@code{gnus-article-date-ut}).
|
|
|
6139
|
|
|
6140 @item W T l
|
|
|
6141 @kindex W T l (Summary)
|
|
|
6142 @findex gnus-article-date-local
|
|
|
6143 Display the date in the local timezone (@code{gnus-article-date-local}).
|
|
|
6144
|
|
16
|
6145 @item W T s
|
|
|
6146 @kindex W T s (Summary)
|
|
|
6147 @vindex gnus-article-time-format
|
|
|
6148 @findex gnus-article-date-user
|
|
|
6149 @findex format-time-string
|
|
|
6150 Display the date using a user-defined format
|
|
|
6151 (@code{gnus-article-date-user}). The format is specified by the
|
|
|
6152 @code{gnus-article-time-format} variable, and is a string that's passed
|
|
|
6153 to @code{format-time-string}. See the documentation of that variable
|
|
|
6154 for a list possible format specs.
|
|
|
6155
|
|
0
|
6156 @item W T e
|
|
|
6157 @kindex W T e (Summary)
|
|
|
6158 @findex gnus-article-date-lapsed
|
|
|
6159 Say how much time has (e)lapsed between the article was posted and now
|
|
|
6160 (@code{gnus-article-date-lapsed}).
|
|
|
6161
|
|
|
6162 @item W T o
|
|
|
6163 @kindex W T o (Summary)
|
|
|
6164 @findex gnus-article-date-original
|
|
|
6165 Display the original date (@code{gnus-article-date-original}). This can
|
|
|
6166 be useful if you normally use some other conversion function and is
|
|
|
6167 worried that it might be doing something totally wrong. Say, claiming
|
|
|
6168 that the article was posted in 1854. Although something like that is
|
|
|
6169 @emph{totally} impossible. Don't you trust me? *titter*
|
|
|
6170
|
|
|
6171 @end table
|
|
|
6172
|
|
|
6173
|
|
16
|
6174 @node Article Signature
|
|
|
6175 @subsection Article Signature
|
|
|
6176 @cindex signatures
|
|
|
6177 @cindex article signature
|
|
|
6178
|
|
|
6179 @vindex gnus-signature-separator
|
|
|
6180 Each article is divided into two parts---the head and the body. The
|
|
|
6181 body can be divided into a signature part and a text part. The variable
|
|
|
6182 that says what is to be considered a signature is
|
|
|
6183 @code{gnus-signature-separator}. This is normally the standard
|
|
|
6184 @samp{^-- $} as mandated by son-of-RFC 1036. However, many people use
|
|
|
6185 non-standard signature separators, so this variable can also be a list
|
|
|
6186 of regular expressions to be tested, one by one. (Searches are done
|
|
|
6187 from the end of the body towards the beginning.) One likely value is:
|
|
|
6188
|
|
|
6189 @lisp
|
|
|
6190 (setq gnus-signature-separator
|
|
|
6191 '("^-- $" ; The standard
|
|
|
6192 "^-- *$" ; A common mangling
|
|
|
6193 "^-------*$" ; Many people just use a looong
|
|
|
6194 ; line of dashes. Shame!
|
|
|
6195 "^ *--------*$" ; Double-shame!
|
|
|
6196 "^________*$" ; Underscores are also popular
|
|
|
6197 "^========*$")) ; Pervert!
|
|
|
6198 @end lisp
|
|
|
6199
|
|
|
6200 The more permissive you are, the more likely it is that you'll get false
|
|
|
6201 positives.
|
|
|
6202
|
|
|
6203 @vindex gnus-signature-limit
|
|
|
6204 @code{gnus-signature-limit} provides a limit to what is considered a
|
|
|
6205 signature.
|
|
|
6206
|
|
|
6207 @enumerate
|
|
|
6208 @item
|
|
|
6209 If it is an integer, no signature may be longer (in characters) than
|
|
|
6210 that integer.
|
|
|
6211 @item
|
|
|
6212 If it is a floating point number, no signature may be longer (in lines)
|
|
|
6213 than that number.
|
|
|
6214 @item
|
|
|
6215 If it is a function, the function will be called without any parameters,
|
|
|
6216 and if it returns @code{nil}, there is no signature in the buffer.
|
|
|
6217 @item
|
|
|
6218 If it is a string, it will be used as a regexp. If it matches, the text
|
|
|
6219 in question is not a signature.
|
|
|
6220 @end enumerate
|
|
|
6221
|
|
|
6222 This variable can also be a list where the elements may be of the types
|
|
|
6223 listed above.
|
|
|
6224
|
|
|
6225
|
|
|
6226 @node Article Commands
|
|
|
6227 @section Article Commands
|
|
|
6228
|
|
|
6229 @table @kbd
|
|
|
6230
|
|
|
6231 @item A P
|
|
|
6232 @cindex PostScript
|
|
|
6233 @cindex printing
|
|
|
6234 @kindex A P (Summary)
|
|
22
|
6235 @vindex gnus-ps-print-hook
|
|
16
|
6236 @findex gnus-summary-print-article
|
|
|
6237 Generate and print a PostScript image of the article buffer
|
|
22
|
6238 (@code{gnus-summary-print-article}). @code{gnus-ps-print-hook} will be
|
|
|
6239 run just before printing the buffer.
|
|
16
|
6240
|
|
|
6241 @end table
|
|
|
6242
|
|
|
6243
|
|
0
|
6244 @node Summary Sorting
|
|
|
6245 @section Summary Sorting
|
|
|
6246 @cindex summary sorting
|
|
|
6247
|
|
|
6248 You can have the summary buffer sorted in various ways, even though I
|
|
|
6249 can't really see why you'd want that.
|
|
|
6250
|
|
|
6251 @table @kbd
|
|
|
6252
|
|
|
6253 @item C-c C-s C-n
|
|
|
6254 @kindex C-c C-s C-n (Summary)
|
|
|
6255 @findex gnus-summary-sort-by-number
|
|
|
6256 Sort by article number (@code{gnus-summary-sort-by-number}).
|
|
|
6257
|
|
|
6258 @item C-c C-s C-a
|
|
|
6259 @kindex C-c C-s C-a (Summary)
|
|
|
6260 @findex gnus-summary-sort-by-author
|
|
|
6261 Sort by author (@code{gnus-summary-sort-by-author}).
|
|
|
6262
|
|
|
6263 @item C-c C-s C-s
|
|
|
6264 @kindex C-c C-s C-s (Summary)
|
|
|
6265 @findex gnus-summary-sort-by-subject
|
|
|
6266 Sort by subject (@code{gnus-summary-sort-by-subject}).
|
|
|
6267
|
|
|
6268 @item C-c C-s C-d
|
|
|
6269 @kindex C-c C-s C-d (Summary)
|
|
|
6270 @findex gnus-summary-sort-by-date
|
|
|
6271 Sort by date (@code{gnus-summary-sort-by-date}).
|
|
|
6272
|
|
16
|
6273 @item C-c C-s C-l
|
|
|
6274 @kindex C-c C-s C-l (Summary)
|
|
|
6275 @findex gnus-summary-sort-by-lines
|
|
|
6276 Sort by lines (@code{gnus-summary-sort-by-lines}).
|
|
|
6277
|
|
0
|
6278 @item C-c C-s C-i
|
|
|
6279 @kindex C-c C-s C-i (Summary)
|
|
|
6280 @findex gnus-summary-sort-by-score
|
|
|
6281 Sort by score (@code{gnus-summary-sort-by-score}).
|
|
|
6282 @end table
|
|
|
6283
|
|
|
6284 These functions will work both when you use threading and when you don't
|
|
|
6285 use threading. In the latter case, all summary lines will be sorted,
|
|
|
6286 line by line. In the former case, sorting will be done on a
|
|
|
6287 root-by-root basis, which might not be what you were looking for. To
|
|
|
6288 toggle whether to use threading, type @kbd{T T} (@pxref{Thread
|
|
|
6289 Commands}).
|
|
|
6290
|
|
|
6291
|
|
|
6292 @node Finding the Parent
|
|
|
6293 @section Finding the Parent
|
|
|
6294 @cindex parent articles
|
|
|
6295 @cindex referring articles
|
|
|
6296
|
|
|
6297 @findex gnus-summary-refer-parent-article
|
|
|
6298 @kindex ^ (Summary)
|
|
|
6299 If you'd like to read the parent of the current article, and it is not
|
|
|
6300 displayed in the summary buffer, you might still be able to. That is,
|
|
|
6301 if the current group is fetched by @sc{nntp}, the parent hasn't expired
|
|
|
6302 and the @code{References} in the current article are not mangled, you
|
|
|
6303 can just press @kbd{^} or @kbd{A r}
|
|
|
6304 (@code{gnus-summary-refer-parent-article}). If everything goes well,
|
|
|
6305 you'll get the parent. If the parent is already displayed in the
|
|
|
6306 summary buffer, point will just move to this article.
|
|
|
6307
|
|
16
|
6308 If given a positive numerical prefix, fetch that many articles back into
|
|
|
6309 the ancestry. If given a negative numerical prefix, fetch just that
|
|
|
6310 ancestor. So if you say @kbd{3 ^}, Gnus will fetch the parent, the
|
|
|
6311 grandparent and the grandgrandparent of the current article. If you say
|
|
|
6312 @kbd{-3 ^}, Gnus will only fetch the grandgrandparent of the current
|
|
|
6313 article.
|
|
|
6314
|
|
0
|
6315 @findex gnus-summary-refer-references
|
|
|
6316 @kindex A R (Summary)
|
|
|
6317 You can have Gnus fetch all articles mentioned in the @code{References}
|
|
|
6318 header of the article by pushing @kbd{A R}
|
|
|
6319 (@code{gnus-summary-refer-references}).
|
|
|
6320
|
|
|
6321 @findex gnus-summary-refer-article
|
|
|
6322 @kindex M-^ (Summary)
|
|
16
|
6323 @cindex Message-ID
|
|
|
6324 @cindex fetching by Message-ID
|
|
0
|
6325 You can also ask the @sc{nntp} server for an arbitrary article, no
|
|
|
6326 matter what group it belongs to. @kbd{M-^}
|
|
|
6327 (@code{gnus-summary-refer-article}) will ask you for a
|
|
16
|
6328 @code{Message-ID}, which is one of those long, hard-to-read thingies
|
|
|
6329 that look something like @samp{<38o6up$6f2@@hymir.ifi.uio.no>}. You
|
|
|
6330 have to get it all exactly right. No fuzzy searches, I'm afraid.
|
|
0
|
6331
|
|
|
6332 @vindex gnus-refer-article-method
|
|
|
6333 If the group you are reading is located on a backend that does not
|
|
|
6334 support fetching by @code{Message-ID} very well (like @code{nnspool}),
|
|
|
6335 you can set @code{gnus-refer-article-method} to an @sc{nntp} method. It
|
|
|
6336 would, perhaps, be best if the @sc{nntp} server you consult is the same
|
|
|
6337 as the one that keeps the spool you are reading from updated, but that's
|
|
|
6338 not really necessary.
|
|
|
6339
|
|
|
6340 Most of the mail backends support fetching by @code{Message-ID}, but do
|
|
|
6341 not do a particularly excellent job of it. That is, @code{nnmbox} and
|
|
|
6342 @code{nnbabyl} are able to locate articles from any groups, while
|
|
|
6343 @code{nnml} and @code{nnfolder} are only able to locate articles that
|
|
|
6344 have been posted to the current group. (Anything else would be too time
|
|
|
6345 consuming.) @code{nnmh} does not support this at all.
|
|
|
6346
|
|
|
6347
|
|
|
6348 @node Alternative Approaches
|
|
|
6349 @section Alternative Approaches
|
|
|
6350
|
|
|
6351 Different people like to read news using different methods. This being
|
|
|
6352 Gnus, we offer a small selection of minor modes for the summary buffers.
|
|
|
6353
|
|
|
6354 @menu
|
|
|
6355 * Pick and Read:: First mark articles and then read them.
|
|
|
6356 * Binary Groups:: Auto-decode all articles.
|
|
|
6357 @end menu
|
|
|
6358
|
|
|
6359
|
|
|
6360 @node Pick and Read
|
|
|
6361 @subsection Pick and Read
|
|
|
6362 @cindex pick and read
|
|
|
6363
|
|
|
6364 Some newsreaders (like @code{nn} and, uhm, @code{nn}) use a two-phased
|
|
|
6365 reading interface. The user first marks the articles she wants to read
|
|
|
6366 from a summary buffer. Then she starts reading the articles with just
|
|
|
6367 an article buffer displayed.
|
|
|
6368
|
|
|
6369 @findex gnus-pick-mode
|
|
|
6370 @kindex M-x gnus-pick-mode
|
|
|
6371 Gnus provides a summary buffer minor mode that allows
|
|
|
6372 this---@code{gnus-pick-mode}. This basically means that a few process
|
|
|
6373 mark commands become one-keystroke commands to allow easy marking, and
|
|
|
6374 it makes one additional command for switching to the summary buffer
|
|
|
6375 available.
|
|
|
6376
|
|
|
6377 Here are the available keystrokes when using pick mode:
|
|
|
6378
|
|
|
6379 @table @kbd
|
|
16
|
6380 @item .
|
|
|
6381 @kindex . (Pick)
|
|
|
6382 @findex gnus-summary-mark-as-processable
|
|
|
6383 Pick the article on the current line
|
|
|
6384 (@code{gnus-summary-mark-as-processable}). If given a numerical prefix,
|
|
|
6385 go to the article on that line and pick that article. (The line number
|
|
|
6386 is normally displayed on the beginning of the summary pick lines.)
|
|
|
6387
|
|
0
|
6388 @item SPACE
|
|
|
6389 @kindex SPACE (Pick)
|
|
16
|
6390 @findex gnus-pick-next-page
|
|
|
6391 Scroll the summary buffer up one page (@code{gnus-pick-next-page}). If
|
|
|
6392 at the end of the buffer, start reading the picked articles.
|
|
0
|
6393
|
|
|
6394 @item u
|
|
|
6395 @kindex u (Pick)
|
|
|
6396 @findex gnus-summary-unmark-as-processable
|
|
|
6397 Unpick the article (@code{gnus-summary-unmark-as-processable}).
|
|
|
6398
|
|
|
6399 @item U
|
|
|
6400 @kindex U (Pick)
|
|
|
6401 @findex gnus-summary-unmark-all-processable
|
|
|
6402 Unpick all articles (@code{gnus-summary-unmark-all-processable}).
|
|
|
6403
|
|
|
6404 @item t
|
|
|
6405 @kindex t (Pick)
|
|
|
6406 @findex gnus-uu-mark-thread
|
|
|
6407 Pick the thread (@code{gnus-uu-mark-thread}).
|
|
|
6408
|
|
|
6409 @item T
|
|
|
6410 @kindex T (Pick)
|
|
|
6411 @findex gnus-uu-unmark-thread
|
|
|
6412 Unpick the thread (@code{gnus-uu-unmark-thread}).
|
|
|
6413
|
|
|
6414 @item r
|
|
|
6415 @kindex r (Pick)
|
|
|
6416 @findex gnus-uu-mark-region
|
|
|
6417 Pick the region (@code{gnus-uu-mark-region}).
|
|
|
6418
|
|
|
6419 @item R
|
|
|
6420 @kindex R (Pick)
|
|
|
6421 @findex gnus-uu-unmark-region
|
|
|
6422 Unpick the region (@code{gnus-uu-unmark-region}).
|
|
|
6423
|
|
|
6424 @item e
|
|
|
6425 @kindex e (Pick)
|
|
|
6426 @findex gnus-uu-mark-by-regexp
|
|
|
6427 Pick articles that match a regexp (@code{gnus-uu-mark-by-regexp}).
|
|
|
6428
|
|
|
6429 @item E
|
|
|
6430 @kindex E (Pick)
|
|
|
6431 @findex gnus-uu-unmark-by-regexp
|
|
|
6432 Unpick articles that match a regexp (@code{gnus-uu-unmark-by-regexp}).
|
|
|
6433
|
|
|
6434 @item b
|
|
|
6435 @kindex b (Pick)
|
|
|
6436 @findex gnus-uu-mark-buffer
|
|
|
6437 Pick the buffer (@code{gnus-uu-mark-buffer}).
|
|
|
6438
|
|
|
6439 @item B
|
|
|
6440 @kindex B (Pick)
|
|
|
6441 @findex gnus-uu-unmark-buffer
|
|
|
6442 Unpick the buffer (@code{gnus-uu-unmark-buffer}).
|
|
|
6443
|
|
|
6444 @item RET
|
|
|
6445 @kindex RET (Pick)
|
|
|
6446 @findex gnus-pick-start-reading
|
|
|
6447 @vindex gnus-pick-display-summary
|
|
|
6448 Start reading the picked articles (@code{gnus-pick-start-reading}). If
|
|
|
6449 given a prefix, mark all unpicked articles as read first. If
|
|
|
6450 @code{gnus-pick-display-summary} is non-@code{nil}, the summary buffer
|
|
|
6451 will still be visible when you are reading.
|
|
|
6452
|
|
|
6453 @end table
|
|
|
6454
|
|
|
6455 If this sounds like a good idea to you, you could say:
|
|
|
6456
|
|
|
6457 @lisp
|
|
|
6458 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
|
|
|
6459 @end lisp
|
|
|
6460
|
|
|
6461 @vindex gnus-pick-mode-hook
|
|
|
6462 @code{gnus-pick-mode-hook} is run in pick minor mode buffers.
|
|
|
6463
|
|
16
|
6464 @vindex gnus-mark-unpicked-articles-as-read
|
|
|
6465 If @code{gnus-mark-unpicked-articles-as-read} is non-@code{nil}, mark
|
|
|
6466 all unpicked articles as read. The default is @code{nil}.
|
|
|
6467
|
|
|
6468 @vindex gnus-summary-pick-line-format
|
|
|
6469 The summary line format in pick mode is slightly different than the
|
|
|
6470 standard format. At the beginning of each line the line number is
|
|
|
6471 displayed. The pick mode line format is controlled by the
|
|
|
6472 @code{gnus-summary-pick-line-format} variable (@pxref{Formatting
|
|
|
6473 Variables}). It accepts the same format specs that
|
|
|
6474 @code{gnus-summary-line-format} does (@pxref{Summary Buffer Lines}).
|
|
|
6475
|
|
0
|
6476
|
|
|
6477 @node Binary Groups
|
|
|
6478 @subsection Binary Groups
|
|
|
6479 @cindex binary groups
|
|
|
6480
|
|
|
6481 @findex gnus-binary-mode
|
|
|
6482 @kindex M-x gnus-binary-mode
|
|
|
6483 If you spend much time in binary groups, you may grow tired of hitting
|
|
|
6484 @kbd{X u}, @kbd{n}, @kbd{RET} all the time. @kbd{M-x gnus-binary-mode}
|
|
|
6485 is a minor mode for summary buffers that makes all ordinary Gnus article
|
|
|
6486 selection functions uudecode series of articles and display the result
|
|
|
6487 instead of just displaying the articles the normal way.
|
|
|
6488
|
|
|
6489 @kindex g (Binary)
|
|
|
6490 @findex gnus-binary-show-article
|
|
|
6491 In fact, the only way to see the actual articles if you have turned this
|
|
|
6492 mode on is the @kbd{g} command (@code{gnus-binary-show-article}).
|
|
|
6493
|
|
|
6494 @vindex gnus-binary-mode-hook
|
|
|
6495 @code{gnus-binary-mode-hook} is called in binary minor mode buffers.
|
|
|
6496
|
|
|
6497
|
|
|
6498 @node Tree Display
|
|
|
6499 @section Tree Display
|
|
|
6500 @cindex trees
|
|
|
6501
|
|
|
6502 @vindex gnus-use-trees
|
|
|
6503 If you don't like the normal Gnus summary display, you might try setting
|
|
|
6504 @code{gnus-use-trees} to @code{t}. This will create (by default) an
|
|
|
6505 additional @dfn{tree buffer}. You can execute all summary mode commands
|
|
|
6506 in the tree buffer.
|
|
|
6507
|
|
|
6508 There are a few variables to customize the tree display, of course:
|
|
|
6509
|
|
|
6510 @table @code
|
|
|
6511 @item gnus-tree-mode-hook
|
|
|
6512 @vindex gnus-tree-mode-hook
|
|
|
6513 A hook called in all tree mode buffers.
|
|
|
6514
|
|
|
6515 @item gnus-tree-mode-line-format
|
|
|
6516 @vindex gnus-tree-mode-line-format
|
|
|
6517 A format string for the mode bar in the tree mode buffers. The default
|
|
|
6518 is @samp{Gnus: %%b [%A] %Z}. For a list of legal specs, @pxref{Summary
|
|
|
6519 Buffer Mode Line}.
|
|
|
6520
|
|
|
6521 @item gnus-selected-tree-face
|
|
|
6522 @vindex gnus-selected-tree-face
|
|
|
6523 Face used for highlighting the selected article in the tree buffer. The
|
|
|
6524 default is @code{modeline}.
|
|
|
6525
|
|
|
6526 @item gnus-tree-line-format
|
|
|
6527 @vindex gnus-tree-line-format
|
|
|
6528 A format string for the tree nodes. The name is a bit of a misnomer,
|
|
|
6529 though---it doesn't define a line, but just the node. The default value
|
|
|
6530 is @samp{%(%[%3,3n%]%)}, which displays the first three characters of
|
|
|
6531 the name of the poster. It is vital that all nodes are of the same
|
|
|
6532 length, so you @emph{must} use @samp{%4,4n}-like specifiers.
|
|
|
6533
|
|
|
6534 Legal specs are:
|
|
|
6535
|
|
|
6536 @table @samp
|
|
|
6537 @item n
|
|
|
6538 The name of the poster.
|
|
|
6539 @item f
|
|
|
6540 The @code{From} header.
|
|
|
6541 @item N
|
|
|
6542 The number of the article.
|
|
|
6543 @item [
|
|
|
6544 The opening bracket.
|
|
|
6545 @item ]
|
|
|
6546 The closing bracket.
|
|
|
6547 @item s
|
|
|
6548 The subject.
|
|
|
6549 @end table
|
|
|
6550
|
|
|
6551 @xref{Formatting Variables}.
|
|
|
6552
|
|
|
6553 Variables related to the display are:
|
|
|
6554
|
|
|
6555 @table @code
|
|
|
6556 @item gnus-tree-brackets
|
|
|
6557 @vindex gnus-tree-brackets
|
|
|
6558 This is used for differentiating between ``real'' articles and
|
|
|
6559 ``sparse'' articles. The format is @var{((real-open . real-close)
|
|
|
6560 (sparse-open . sparse-close) (dummy-open . dummy-close))}, and the
|
|
|
6561 default is @code{((?[ . ?]) (?( . ?)) (?@{ . ?@}))}.
|
|
|
6562
|
|
|
6563 @item gnus-tree-parent-child-edges
|
|
|
6564 @vindex gnus-tree-parent-child-edges
|
|
|
6565 This is a list that contains the characters used for connecting parent
|
|
|
6566 nodes to their children. The default is @code{(?- ?\\ ?|)}.
|
|
|
6567
|
|
|
6568 @end table
|
|
|
6569
|
|
|
6570 @item gnus-tree-minimize-window
|
|
|
6571 @vindex gnus-tree-minimize-window
|
|
|
6572 If this variable is non-@code{nil}, Gnus will try to keep the tree
|
|
|
6573 buffer as small as possible to allow more room for the other Gnus
|
|
|
6574 windows. If this variable is a number, the tree buffer will never be
|
|
|
6575 higher than that number. The default is @code{t}.
|
|
|
6576
|
|
|
6577 @item gnus-generate-tree-function
|
|
|
6578 @vindex gnus-generate-tree-function
|
|
|
6579 @findex gnus-generate-horizontal-tree
|
|
|
6580 @findex gnus-generate-vertical-tree
|
|
|
6581 The function that actually generates the thread tree. Two predefined
|
|
|
6582 functions are available: @code{gnus-generate-horizontal-tree} and
|
|
|
6583 @code{gnus-generate-vertical-tree} (which is the default).
|
|
|
6584
|
|
|
6585 @end table
|
|
|
6586
|
|
|
6587 Here's and example from a horizontal tree buffer:
|
|
|
6588
|
|
|
6589 @example
|
|
|
6590 @{***@}-(***)-[odd]-[Gun]
|
|
16
|
6591 | \[Jan]
|
|
|
6592 | \[odd]-[Eri]
|
|
|
6593 | \(***)-[Eri]
|
|
|
6594 | \[odd]-[Paa]
|
|
0
|
6595 \[Bjo]
|
|
|
6596 \[Gun]
|
|
|
6597 \[Gun]-[Jor]
|
|
|
6598 @end example
|
|
|
6599
|
|
|
6600 Here's the same thread displayed in a vertical tree buffer:
|
|
|
6601
|
|
|
6602 @example
|
|
|
6603 @{***@}
|
|
|
6604 |--------------------------\-----\-----\
|
|
|
6605 (***) [Bjo] [Gun] [Gun]
|
|
|
6606 |--\-----\-----\ |
|
|
|
6607 [odd] [Jan] [odd] (***) [Jor]
|
|
|
6608 | | |--\
|
|
|
6609 [Gun] [Eri] [Eri] [odd]
|
|
|
6610 |
|
|
|
6611 [Paa]
|
|
|
6612 @end example
|
|
|
6613
|
|
|
6614
|
|
|
6615 @node Mail Group Commands
|
|
|
6616 @section Mail Group Commands
|
|
|
6617 @cindex mail group commands
|
|
|
6618
|
|
|
6619 Some commands only make sense in mail groups. If these commands are
|
|
|
6620 illegal in the current group, they will raise a hell and let you know.
|
|
|
6621
|
|
|
6622 All these commands (except the expiry and edit commands) use the
|
|
|
6623 process/prefix convention (@pxref{Process/Prefix}).
|
|
|
6624
|
|
|
6625 @table @kbd
|
|
|
6626
|
|
|
6627 @item B e
|
|
|
6628 @kindex B e (Summary)
|
|
|
6629 @findex gnus-summary-expire-articles
|
|
|
6630 Expire all expirable articles in the group
|
|
|
6631 (@code{gnus-summary-expire-articles}).
|
|
|
6632
|
|
|
6633 @item B M-C-e
|
|
|
6634 @kindex B M-C-e (Summary)
|
|
|
6635 @findex gnus-summary-expire-articles-now
|
|
16
|
6636 Delete all the expirable articles in the group
|
|
0
|
6637 (@code{gnus-summary-expire-articles-now}). This means that @strong{all}
|
|
|
6638 articles that are eligible for expiry in the current group will
|
|
|
6639 disappear forever into that big @file{/dev/null} in the sky.
|
|
|
6640
|
|
|
6641 @item B DEL
|
|
|
6642 @kindex B DEL (Summary)
|
|
|
6643 @findex gnus-summary-delete-article
|
|
|
6644 Delete the mail article. This is ``delete'' as in ``delete it from your
|
|
|
6645 disk forever and ever, never to return again.'' Use with caution.
|
|
|
6646 (@code{gnus-summary-delete-article}).
|
|
|
6647
|
|
|
6648 @item B m
|
|
|
6649 @kindex B m (Summary)
|
|
|
6650 @cindex move mail
|
|
|
6651 @findex gnus-summary-move-article
|
|
|
6652 Move the article from one mail group to another
|
|
|
6653 (@code{gnus-summary-move-article}).
|
|
|
6654
|
|
|
6655 @item B c
|
|
|
6656 @kindex B c (Summary)
|
|
|
6657 @cindex copy mail
|
|
|
6658 @findex gnus-summary-copy-article
|
|
|
6659 Copy the article from one group (mail group or not) to a mail group
|
|
|
6660 (@code{gnus-summary-copy-article}).
|
|
|
6661
|
|
|
6662 @item B C
|
|
|
6663 @kindex B C (Summary)
|
|
|
6664 @cindex crosspost mail
|
|
|
6665 @findex gnus-summary-crosspost-article
|
|
|
6666 Crosspost the current article to some other group
|
|
|
6667 (@code{gnus-summary-crosspost-article}). This will create a new copy of
|
|
|
6668 the article in the other group, and the Xref headers of the article will
|
|
|
6669 be properly updated.
|
|
|
6670
|
|
|
6671 @item B i
|
|
|
6672 @kindex B i (Summary)
|
|
|
6673 @findex gnus-summary-import-article
|
|
|
6674 Import an arbitrary file into the current mail newsgroup
|
|
|
6675 (@code{gnus-summary-import-article}). You will be prompted for a file
|
|
|
6676 name, a @code{From} header and a @code{Subject} header.
|
|
|
6677
|
|
|
6678 @item B r
|
|
|
6679 @kindex B r (Summary)
|
|
|
6680 @findex gnus-summary-respool-article
|
|
|
6681 Respool the mail article (@code{gnus-summary-move-article}).
|
|
16
|
6682 @code{gnus-summary-respool-default-method} will be used as the default
|
|
|
6683 select method when respooling. This variable is @code{nil} by default,
|
|
|
6684 which means that the current group select method will be used instead.
|
|
0
|
6685
|
|
|
6686 @item B w
|
|
|
6687 @itemx e
|
|
|
6688 @kindex B w (Summary)
|
|
|
6689 @kindex e (Summary)
|
|
|
6690 @findex gnus-summary-edit-article
|
|
|
6691 @kindex C-c C-c (Article)
|
|
|
6692 Edit the current article (@code{gnus-summary-edit-article}). To finish
|
|
|
6693 editing and make the changes permanent, type @kbd{C-c C-c}
|
|
|
6694 (@kbd{gnus-summary-edit-article-done}).
|
|
|
6695
|
|
|
6696 @item B q
|
|
|
6697 @kindex B q (Summary)
|
|
|
6698 @findex gnus-summary-respool-query
|
|
|
6699 If you want to re-spool an article, you might be curious as to what group
|
|
|
6700 the article will end up in before you do the re-spooling. This command
|
|
|
6701 will tell you (@code{gnus-summary-respool-query}).
|
|
16
|
6702
|
|
|
6703 @item B p
|
|
|
6704 @kindex B p (Summary)
|
|
|
6705 @findex gnus-summary-article-posted-p
|
|
|
6706 Some people have a tendency to send you "courtesy" copies when they
|
|
|
6707 follow up to articles you have posted. These usually have a
|
|
|
6708 @code{Newsgroups} header in them, but not always. This command
|
|
|
6709 (@code{gnus-summary-article-posted-p}) will try to fetch the current
|
|
|
6710 article from your news server (or rather, from
|
|
|
6711 @code{gnus-refer-article-method} or @code{gnus-select-method}) and will
|
|
|
6712 report back whether it found the article or not. Even if it says that
|
|
|
6713 it didn't find the article, it may have been posted anyway---mail
|
|
|
6714 propagation is much faster than news propagation, and the news copy may
|
|
|
6715 just not have arrived yet.
|
|
|
6716
|
|
0
|
6717 @end table
|
|
|
6718
|
|
|
6719 @vindex gnus-move-split-methods
|
|
|
6720 @cindex moving articles
|
|
|
6721 If you move (or copy) articles regularly, you might wish to have Gnus
|
|
|
6722 suggest where to put the articles. @code{gnus-move-split-methods} is a
|
|
|
6723 variable that uses the same syntax as @code{gnus-split-methods}
|
|
|
6724 (@pxref{Saving Articles}). You may customize that variable to create
|
|
|
6725 suggestions you find reasonable.
|
|
|
6726
|
|
16
|
6727 @lisp
|
|
|
6728 (setq gnus-move-split-methods
|
|
|
6729 '(("^From:.*Lars Magne" "nnml:junk")
|
|
|
6730 ("^Subject:.*gnus" "nnfolder:important")
|
|
|
6731 (".*" "nnml:misc")))
|
|
|
6732 @end lisp
|
|
|
6733
|
|
0
|
6734
|
|
|
6735 @node Various Summary Stuff
|
|
|
6736 @section Various Summary Stuff
|
|
|
6737
|
|
|
6738 @menu
|
|
|
6739 * Summary Group Information:: Information oriented commands.
|
|
|
6740 * Searching for Articles:: Multiple article commands.
|
|
16
|
6741 * Summary Generation Commands:: (Re)generating the summary buffer.
|
|
0
|
6742 * Really Various Summary Commands:: Those pesky non-conformant commands.
|
|
|
6743 @end menu
|
|
|
6744
|
|
|
6745 @table @code
|
|
|
6746 @vindex gnus-summary-mode-hook
|
|
|
6747 @item gnus-summary-mode-hook
|
|
|
6748 This hook is called when creating a summary mode buffer.
|
|
|
6749
|
|
|
6750 @vindex gnus-summary-generate-hook
|
|
|
6751 @item gnus-summary-generate-hook
|
|
|
6752 This is called as the last thing before doing the threading and the
|
|
|
6753 generation of the summary buffer. It's quite convenient for customizing
|
|
|
6754 the threading variables based on what data the newsgroup has. This hook
|
|
|
6755 is called from the summary buffer after most summary buffer variables
|
|
|
6756 has been set.
|
|
|
6757
|
|
|
6758 @vindex gnus-summary-prepare-hook
|
|
|
6759 @item gnus-summary-prepare-hook
|
|
|
6760 Is is called after the summary buffer has been generated. You might use
|
|
|
6761 it to, for instance, highlight lines or modify the look of the buffer in
|
|
|
6762 some other ungodly manner. I don't care.
|
|
|
6763
|
|
38
|
6764 @vindex gnus-summary-ignore-duplicates
|
|
|
6765 @item gnus-summary-ignore-duplicates
|
|
|
6766 When Gnus discovers two articles that have the same @code{Message-ID},
|
|
|
6767 it has to do something drastic. No articles are allowed to have the
|
|
|
6768 same @code{Message-ID}, but this may happen when reading mail from some
|
|
|
6769 sources. Gnus allows you to customize what happens with this variable.
|
|
|
6770 If it is @code{nil} (which is the default), Gnus will rename the
|
|
|
6771 @code{Message-ID} (for display purposes only) and display the article as
|
|
|
6772 any other article. If this variable is @code{t}, it won't display the
|
|
|
6773 article---it'll be as if it never existed.
|
|
|
6774
|
|
0
|
6775 @end table
|
|
|
6776
|
|
|
6777
|
|
|
6778 @node Summary Group Information
|
|
|
6779 @subsection Summary Group Information
|
|
|
6780
|
|
|
6781 @table @kbd
|
|
|
6782
|
|
|
6783 @item H f
|
|
|
6784 @kindex H f (Summary)
|
|
|
6785 @findex gnus-summary-fetch-faq
|
|
|
6786 @vindex gnus-group-faq-directory
|
|
|
6787 Try to fetch the FAQ (list of frequently asked questions) for the
|
|
|
6788 current group (@code{gnus-summary-fetch-faq}). Gnus will try to get the
|
|
|
6789 FAQ from @code{gnus-group-faq-directory}, which is usually a directory
|
|
|
6790 on a remote machine. This variable can also be a list of directories.
|
|
|
6791 In that case, giving a prefix to this command will allow you to choose
|
|
|
6792 between the various sites. @code{ange-ftp} probably will be used for
|
|
|
6793 fetching the file.
|
|
|
6794
|
|
|
6795 @item H d
|
|
|
6796 @kindex H d (Summary)
|
|
|
6797 @findex gnus-summary-describe-group
|
|
|
6798 Give a brief description of the current group
|
|
|
6799 (@code{gnus-summary-describe-group}). If given a prefix, force
|
|
|
6800 rereading the description from the server.
|
|
|
6801
|
|
|
6802 @item H h
|
|
|
6803 @kindex H h (Summary)
|
|
|
6804 @findex gnus-summary-describe-briefly
|
|
16
|
6805 Give an extremely brief description of the most important summary
|
|
|
6806 keystrokes (@code{gnus-summary-describe-briefly}).
|
|
0
|
6807
|
|
|
6808 @item H i
|
|
|
6809 @kindex H i (Summary)
|
|
|
6810 @findex gnus-info-find-node
|
|
|
6811 Go to the Gnus info node (@code{gnus-info-find-node}).
|
|
|
6812 @end table
|
|
|
6813
|
|
|
6814
|
|
|
6815 @node Searching for Articles
|
|
|
6816 @subsection Searching for Articles
|
|
|
6817
|
|
|
6818 @table @kbd
|
|
|
6819
|
|
|
6820 @item M-s
|
|
|
6821 @kindex M-s (Summary)
|
|
|
6822 @findex gnus-summary-search-article-forward
|
|
|
6823 Search through all subsequent articles for a regexp
|
|
|
6824 (@code{gnus-summary-search-article-forward}).
|
|
|
6825
|
|
|
6826 @item M-r
|
|
|
6827 @kindex M-r (Summary)
|
|
|
6828 @findex gnus-summary-search-article-backward
|
|
|
6829 Search through all previous articles for a regexp
|
|
|
6830 (@code{gnus-summary-search-article-backward}).
|
|
|
6831
|
|
|
6832 @item &
|
|
|
6833 @kindex & (Summary)
|
|
|
6834 @findex gnus-summary-execute-command
|
|
|
6835 This command will prompt you for a header field, a regular expression to
|
|
|
6836 match on this field, and a command to be executed if the match is made
|
|
|
6837 (@code{gnus-summary-execute-command}).
|
|
|
6838
|
|
|
6839 @item M-&
|
|
|
6840 @kindex M-& (Summary)
|
|
|
6841 @findex gnus-summary-universal-argument
|
|
|
6842 Perform any operation on all articles that have been marked with
|
|
|
6843 the process mark (@code{gnus-summary-universal-argument}).
|
|
|
6844 @end table
|
|
|
6845
|
|
16
|
6846 @node Summary Generation Commands
|
|
|
6847 @subsection Summary Generation Commands
|
|
|
6848
|
|
|
6849 @table @kbd
|
|
|
6850
|
|
|
6851 @item Y g
|
|
|
6852 @kindex Y g (Summary)
|
|
|
6853 @findex gnus-summary-prepare
|
|
|
6854 Regenerate the current summary buffer (@code{gnus-summary-prepare}).
|
|
|
6855
|
|
|
6856 @item Y c
|
|
|
6857 @kindex Y c (Summary)
|
|
|
6858 @findex gnus-summary-insert-cached-articles
|
|
|
6859 Pull all cached articles (for the current group) into the summary buffer
|
|
|
6860 (@code{gnus-summary-insert-cached-articles}).
|
|
|
6861
|
|
|
6862 @end table
|
|
|
6863
|
|
0
|
6864
|
|
|
6865 @node Really Various Summary Commands
|
|
|
6866 @subsection Really Various Summary Commands
|
|
|
6867
|
|
|
6868 @table @kbd
|
|
|
6869
|
|
16
|
6870 @item C-d
|
|
|
6871 @kindex C-d (Summary)
|
|
0
|
6872 @findex gnus-summary-enter-digest-group
|
|
|
6873 If the current article is a collection of other articles (for instance,
|
|
|
6874 a digest), you might use this command to enter a group based on the that
|
|
|
6875 article (@code{gnus-summary-enter-digest-group}). Gnus will try to
|
|
|
6876 guess what article type is currently displayed unless you give a prefix
|
|
|
6877 to this command, which forces a ``digest'' interpretation. Basically,
|
|
|
6878 whenever you see a message that is a collection of other messages on
|
|
16
|
6879 some format, you @kbd{C-d} and read these messages in a more convenient
|
|
0
|
6880 fashion.
|
|
|
6881
|
|
16
|
6882 @item M-C-d
|
|
|
6883 @kindex M-C-d (Summary)
|
|
|
6884 @findex gnus-summary-read-document
|
|
|
6885 This command is very similar to the one above, but lets you gather
|
|
|
6886 several documents into one biiig group
|
|
|
6887 (@code{gnus-summary-read-document}). It does this by opening several
|
|
|
6888 @code{nndoc} groups for each document, and then opening an
|
|
|
6889 @code{nnvirtual} group on top of these @code{nndoc} groups. This
|
|
|
6890 command understands the process/prefix convention
|
|
|
6891 (@pxref{Process/Prefix}).
|
|
|
6892
|
|
0
|
6893 @item C-t
|
|
|
6894 @kindex C-t (Summary)
|
|
|
6895 @findex gnus-summary-toggle-truncation
|
|
16
|
6896 Toggle truncation of summary lines
|
|
|
6897 (@code{gnus-summary-toggle-truncation}). This will probably confuse the
|
|
|
6898 line centering function in the summary buffer, so it's not a good idea
|
|
|
6899 to have truncation switched off while reading articles.
|
|
0
|
6900
|
|
|
6901 @item =
|
|
|
6902 @kindex = (Summary)
|
|
|
6903 @findex gnus-summary-expand-window
|
|
|
6904 Expand the summary buffer window (@code{gnus-summary-expand-window}).
|
|
|
6905 If given a prefix, force an @code{article} window configuration.
|
|
16
|
6906
|
|
0
|
6907 @end table
|
|
|
6908
|
|
|
6909
|
|
|
6910 @node Exiting the Summary Buffer
|
|
|
6911 @section Exiting the Summary Buffer
|
|
|
6912 @cindex summary exit
|
|
|
6913 @cindex exiting groups
|
|
|
6914
|
|
|
6915 Exiting from the summary buffer will normally update all info on the
|
|
|
6916 group and return you to the group buffer.
|
|
|
6917
|
|
|
6918 @table @kbd
|
|
|
6919
|
|
|
6920 @item Z Z
|
|
|
6921 @itemx q
|
|
|
6922 @kindex Z Z (Summary)
|
|
|
6923 @kindex q (Summary)
|
|
|
6924 @findex gnus-summary-exit
|
|
|
6925 @vindex gnus-summary-exit-hook
|
|
|
6926 @vindex gnus-summary-prepare-exit-hook
|
|
|
6927 Exit the current group and update all information on the group
|
|
|
6928 (@code{gnus-summary-exit}). @code{gnus-summary-prepare-exit-hook} is
|
|
|
6929 called before doing much of the exiting, and calls
|
|
|
6930 @code{gnus-summary-expire-articles} by default.
|
|
|
6931 @code{gnus-summary-exit-hook} is called after finishing the exiting
|
|
16
|
6932 process. @code{gnus-group-no-more-groups-hook} is run when returning to
|
|
|
6933 group mode having no more (unread) groups.
|
|
0
|
6934
|
|
|
6935 @item Z E
|
|
|
6936 @itemx Q
|
|
|
6937 @kindex Z E (Summary)
|
|
|
6938 @kindex Q (Summary)
|
|
|
6939 @findex gnus-summary-exit-no-update
|
|
|
6940 Exit the current group without updating any information on the group
|
|
|
6941 (@code{gnus-summary-exit-no-update}).
|
|
|
6942
|
|
|
6943 @item Z c
|
|
|
6944 @itemx c
|
|
|
6945 @kindex Z c (Summary)
|
|
|
6946 @kindex c (Summary)
|
|
|
6947 @findex gnus-summary-catchup-and-exit
|
|
|
6948 Mark all unticked articles in the group as read and then exit
|
|
|
6949 (@code{gnus-summary-catchup-and-exit}).
|
|
|
6950
|
|
|
6951 @item Z C
|
|
|
6952 @kindex Z C (Summary)
|
|
|
6953 @findex gnus-summary-catchup-all-and-exit
|
|
|
6954 Mark all articles, even the ticked ones, as read and then exit
|
|
|
6955 (@code{gnus-summary-catchup-all-and-exit}).
|
|
|
6956
|
|
|
6957 @item Z n
|
|
|
6958 @kindex Z n (Summary)
|
|
|
6959 @findex gnus-summary-catchup-and-goto-next-group
|
|
|
6960 Mark all articles as read and go to the next group
|
|
|
6961 (@code{gnus-summary-catchup-and-goto-next-group}).
|
|
|
6962
|
|
|
6963 @item Z R
|
|
|
6964 @kindex Z R (Summary)
|
|
|
6965 @findex gnus-summary-reselect-current-group
|
|
|
6966 Exit this group, and then enter it again
|
|
|
6967 (@code{gnus-summary-reselect-current-group}). If given a prefix, select
|
|
|
6968 all articles, both read and unread.
|
|
|
6969
|
|
|
6970 @item Z G
|
|
|
6971 @itemx M-g
|
|
|
6972 @kindex Z G (Summary)
|
|
|
6973 @kindex M-g (Summary)
|
|
|
6974 @findex gnus-summary-rescan-group
|
|
|
6975 Exit the group, check for new articles in the group, and select the
|
|
|
6976 group (@code{gnus-summary-rescan-group}). If given a prefix, select all
|
|
|
6977 articles, both read and unread.
|
|
|
6978
|
|
|
6979 @item Z N
|
|
|
6980 @kindex Z N (Summary)
|
|
|
6981 @findex gnus-summary-next-group
|
|
|
6982 Exit the group and go to the next group
|
|
|
6983 (@code{gnus-summary-next-group}).
|
|
|
6984
|
|
|
6985 @item Z P
|
|
|
6986 @kindex Z P (Summary)
|
|
|
6987 @findex gnus-summary-prev-group
|
|
|
6988 Exit the group and go to the previous group
|
|
|
6989 (@code{gnus-summary-prev-group}).
|
|
16
|
6990
|
|
|
6991 @item Z s
|
|
|
6992 @kindex Z s (Summary)
|
|
|
6993 @findex gnus-summary-save-newsrc
|
|
|
6994 Save the current number of read/marked articles in the dribble buffer
|
|
|
6995 and then save the dribble buffer (@code{gnus-summary-save-newsrc}). If
|
|
|
6996 given a prefix, also save the @file{.newsrc} file(s). Using this
|
|
|
6997 command will make exit without updating (the @kbd{Q} command) worthless.
|
|
0
|
6998 @end table
|
|
|
6999
|
|
|
7000 @vindex gnus-exit-group-hook
|
|
|
7001 @code{gnus-exit-group-hook} is called when you exit the current
|
|
|
7002 group.
|
|
|
7003
|
|
|
7004 @findex gnus-summary-wake-up-the-dead
|
|
|
7005 @findex gnus-dead-summary-mode
|
|
|
7006 @vindex gnus-kill-summary-on-exit
|
|
|
7007 If you're in the habit of exiting groups, and then changing your mind
|
|
|
7008 about it, you might set @code{gnus-kill-summary-on-exit} to @code{nil}.
|
|
|
7009 If you do that, Gnus won't kill the summary buffer when you exit it.
|
|
|
7010 (Quelle surprise!) Instead it will change the name of the buffer to
|
|
|
7011 something like @samp{*Dead Summary ... *} and install a minor mode
|
|
|
7012 called @code{gnus-dead-summary-mode}. Now, if you switch back to this
|
|
|
7013 buffer, you'll find that all keys are mapped to a function called
|
|
|
7014 @code{gnus-summary-wake-up-the-dead}. So tapping any keys in a dead
|
|
|
7015 summary buffer will result in a live, normal summary buffer.
|
|
|
7016
|
|
|
7017 There will never be more than one dead summary buffer at any one time.
|
|
|
7018
|
|
|
7019 @vindex gnus-use-cross-reference
|
|
|
7020 The data on the current group will be updated (which articles you have
|
|
|
7021 read, which articles you have replied to, etc.) when you exit the
|
|
|
7022 summary buffer. If the @code{gnus-use-cross-reference} variable is
|
|
|
7023 @code{t} (which is the default), articles that are cross-referenced to
|
|
|
7024 this group and are marked as read, will also be marked as read in the
|
|
|
7025 other subscribed groups they were cross-posted to. If this variable is
|
|
|
7026 neither @code{nil} nor @code{t}, the article will be marked as read in
|
|
16
|
7027 both subscribed and unsubscribed groups (@pxref{Crosspost Handling}).
|
|
|
7028
|
|
|
7029
|
|
|
7030 @node Crosspost Handling
|
|
|
7031 @section Crosspost Handling
|
|
0
|
7032
|
|
|
7033 @cindex velveeta
|
|
|
7034 @cindex spamming
|
|
|
7035 Marking cross-posted articles as read ensures that you'll never have to
|
|
|
7036 read the same article more than once. Unless, of course, somebody has
|
|
|
7037 posted it to several groups separately. Posting the same article to
|
|
|
7038 several groups (not cross-posting) is called @dfn{spamming}, and you are
|
|
|
7039 by law required to send nasty-grams to anyone who perpetrates such a
|
|
16
|
7040 heinous crime. You may want to try NoCeM handling to filter out spam
|
|
|
7041 (@pxref{NoCeM}).
|
|
0
|
7042
|
|
|
7043 Remember: Cross-posting is kinda ok, but posting the same article
|
|
|
7044 separately to several groups is not. Massive cross-posting (aka.
|
|
16
|
7045 @dfn{velveeta}) is to be avoided at all costs, and you can even use the
|
|
|
7046 @code{gnus-summary-mail-crosspost-complaint} command to complain about
|
|
|
7047 excessive crossposting (@pxref{Summary Mail Commands}).
|
|
0
|
7048
|
|
|
7049 @cindex cross-posting
|
|
|
7050 @cindex Xref
|
|
|
7051 @cindex @sc{nov}
|
|
|
7052 One thing that may cause Gnus to not do the cross-posting thing
|
|
|
7053 correctly is if you use an @sc{nntp} server that supports @sc{xover}
|
|
|
7054 (which is very nice, because it speeds things up considerably) which
|
|
|
7055 does not include the @code{Xref} header in its @sc{nov} lines. This is
|
|
|
7056 Evil, but all too common, alas, alack. Gnus tries to Do The Right Thing
|
|
|
7057 even with @sc{xover} by registering the @code{Xref} lines of all
|
|
|
7058 articles you actually read, but if you kill the articles, or just mark
|
|
|
7059 them as read without reading them, Gnus will not get a chance to snoop
|
|
|
7060 the @code{Xref} lines out of these articles, and will be unable to use
|
|
|
7061 the cross reference mechanism.
|
|
|
7062
|
|
|
7063 @cindex LIST overview.fmt
|
|
|
7064 @cindex overview.fmt
|
|
|
7065 To check whether your @sc{nntp} server includes the @code{Xref} header
|
|
|
7066 in its overview files, try @samp{telnet your.nntp.server nntp},
|
|
|
7067 @samp{MODE READER} on @code{inn} servers, and then say @samp{LIST
|
|
|
7068 overview.fmt}. This may not work, but if it does, and the last line you
|
|
|
7069 get does not read @samp{Xref:full}, then you should shout and whine at
|
|
|
7070 your news admin until she includes the @code{Xref} header in the
|
|
|
7071 overview files.
|
|
|
7072
|
|
|
7073 @vindex gnus-nov-is-evil
|
|
|
7074 If you want Gnus to get the @code{Xref}s right all the time, you have to
|
|
|
7075 set @code{gnus-nov-is-evil} to @code{t}, which slows things down
|
|
|
7076 considerably.
|
|
|
7077
|
|
|
7078 C'est la vie.
|
|
|
7079
|
|
16
|
7080 For an alternative approach, @pxref{Duplicate Suppression}.
|
|
|
7081
|
|
|
7082
|
|
|
7083 @node Duplicate Suppression
|
|
|
7084 @section Duplicate Suppression
|
|
|
7085
|
|
|
7086 By default, Gnus tries to make sure that you don't have to read the same
|
|
|
7087 article more than once by utilizing the crossposting mechanism
|
|
|
7088 (@pxref{Crosspost Handling}). However, that simple and efficient
|
|
|
7089 approach may not work satisfactorily for some users for various
|
|
|
7090 reasons.
|
|
|
7091
|
|
|
7092 @enumerate
|
|
|
7093 @item
|
|
|
7094 The @sc{nntp} server may fail to generate the @code{Xref} header. This
|
|
|
7095 is evil and not very common.
|
|
|
7096
|
|
|
7097 @item
|
|
|
7098 The @sc{nntp} server may fail to include the @code{Xref} header in the
|
|
|
7099 @file{.overview} data bases. This is evil and all too common, alas.
|
|
|
7100
|
|
|
7101 @item
|
|
|
7102 You may be reading the same group (or several related groups) from
|
|
|
7103 different @sc{nntp} servers.
|
|
|
7104
|
|
|
7105 @item
|
|
|
7106 You may be getting mail that duplicates articles posted to groups.
|
|
|
7107 @end enumerate
|
|
|
7108
|
|
|
7109 I'm sure there are other situations that @code{Xref} handling fails as
|
|
|
7110 well, but these four are the most common situations.
|
|
|
7111
|
|
|
7112 If, and only if, @code{Xref} handling fails for you, then you may
|
|
|
7113 consider switching on @dfn{duplicate suppression}. If you do so, Gnus
|
|
|
7114 will remember the @code{Message-ID}s of all articles you have read or
|
|
|
7115 otherwise marked as read, and then, as if by magic, mark them as read
|
|
|
7116 all subsequent times you see them---in @emph{all} groups. Using this
|
|
|
7117 mechanism is quite likely to be somewhat inefficient, but not overly
|
|
|
7118 so. It's certainly preferable to reading the same articles more than
|
|
|
7119 once.
|
|
|
7120
|
|
|
7121 Duplicate suppression is not a very subtle instrument. It's more like a
|
|
|
7122 sledge hammer than anything else. It works in a very simple
|
|
|
7123 fashion---if you have marked an article as read, it adds this Message-ID
|
|
|
7124 to a cache. The next time it sees this Message-ID, it will mark the
|
|
|
7125 article as read the the @samp{M} mark. It doesn't care what group it
|
|
|
7126 saw the article in.
|
|
|
7127
|
|
|
7128 @table @code
|
|
|
7129 @item gnus-suppress-duplicates
|
|
|
7130 @vindex gnus-suppress-duplicates
|
|
|
7131 If non-@code{nil}, suppress duplicates.
|
|
|
7132
|
|
|
7133 @item gnus-save-duplicate-list
|
|
|
7134 @vindex gnus-save-duplicate-list
|
|
|
7135 If non-@code{nil}, save the list of duplicates to a file. This will
|
|
|
7136 make startup and shutdown take longer, so the default is @code{nil}.
|
|
|
7137 However, this means that only duplicate articles that is read in a
|
|
|
7138 single Gnus session are suppressed.
|
|
|
7139
|
|
|
7140 @item gnus-duplicate-list-length
|
|
|
7141 @vindex gnus-duplicate-list-length
|
|
|
7142 This variables says how many @code{Message-ID}s to keep in the duplicate
|
|
|
7143 suppression list. The default is 10000.
|
|
|
7144
|
|
|
7145 @item gnus-duplicate-file
|
|
|
7146 @vindex gnus-duplicate-file
|
|
|
7147 The name of the file to store the duplicate suppression list. The
|
|
|
7148 default is @file{~/News/suppression}.
|
|
|
7149 @end table
|
|
|
7150
|
|
|
7151 If you have a tendency to stop and start Gnus often, setting
|
|
|
7152 @code{gnus-save-duplicate-list} to @code{t} is probably a good idea. If
|
|
|
7153 you leave Gnus running for weeks on end, you may have it @code{nil}. On
|
|
|
7154 the other hand, saving the list makes startup and shutdown much slower,
|
|
|
7155 so that means that if you stop and start Gnus often, you should set
|
|
|
7156 @code{gnus-save-duplicate-list} to @code{nil}. Uhm. I'll leave this up
|
|
|
7157 to you to figure out, I think.
|
|
|
7158
|
|
0
|
7159
|
|
|
7160 @node The Article Buffer
|
|
|
7161 @chapter The Article Buffer
|
|
|
7162 @cindex article buffer
|
|
|
7163
|
|
|
7164 The articles are displayed in the article buffer, of which there is only
|
|
|
7165 one. All the summary buffers share the same article buffer unless you
|
|
|
7166 tell Gnus otherwise.
|
|
|
7167
|
|
|
7168 @menu
|
|
|
7169 * Hiding Headers:: Deciding what headers should be displayed.
|
|
|
7170 * Using MIME:: Pushing articles through @sc{mime} before reading them.
|
|
|
7171 * Customizing Articles:: Tailoring the look of the articles.
|
|
16
|
7172 * Article Keymap:: Keystrokes available in the article buffer.
|
|
0
|
7173 * Misc Article:: Other stuff.
|
|
|
7174 @end menu
|
|
|
7175
|
|
|
7176
|
|
|
7177 @node Hiding Headers
|
|
|
7178 @section Hiding Headers
|
|
|
7179 @cindex hiding headers
|
|
|
7180 @cindex deleting headers
|
|
|
7181
|
|
|
7182 The top section of each article is the @dfn{head}. (The rest is the
|
|
|
7183 @dfn{body}, but you may have guessed that already.)
|
|
|
7184
|
|
|
7185 @vindex gnus-show-all-headers
|
|
|
7186 There is a lot of useful information in the head: the name of the person
|
|
|
7187 who wrote the article, the date it was written and the subject of the
|
|
|
7188 article. That's well and nice, but there's also lots of information
|
|
|
7189 most people do not want to see---what systems the article has passed
|
|
|
7190 through before reaching you, the @code{Message-ID}, the
|
|
|
7191 @code{References}, etc. ad nauseum---and you'll probably want to get rid
|
|
|
7192 of some of those lines. If you want to keep all those lines in the
|
|
|
7193 article buffer, you can set @code{gnus-show-all-headers} to @code{t}.
|
|
|
7194
|
|
|
7195 Gnus provides you with two variables for sifting headers:
|
|
|
7196
|
|
|
7197 @table @code
|
|
|
7198
|
|
|
7199 @item gnus-visible-headers
|
|
|
7200 @vindex gnus-visible-headers
|
|
|
7201 If this variable is non-@code{nil}, it should be a regular expression
|
|
|
7202 that says what headers you wish to keep in the article buffer. All
|
|
|
7203 headers that do not match this variable will be hidden.
|
|
|
7204
|
|
|
7205 For instance, if you only want to see the name of the person who wrote
|
|
|
7206 the article and the subject, you'd say:
|
|
|
7207
|
|
|
7208 @lisp
|
|
|
7209 (setq gnus-visible-headers "^From:\\|^Subject:")
|
|
|
7210 @end lisp
|
|
|
7211
|
|
|
7212 This variable can also be a list of regexps to match headers that are to
|
|
|
7213 remain visible.
|
|
|
7214
|
|
|
7215 @item gnus-ignored-headers
|
|
|
7216 @vindex gnus-ignored-headers
|
|
|
7217 This variable is the reverse of @code{gnus-visible-headers}. If this
|
|
|
7218 variable is set (and @code{gnus-visible-headers} is @code{nil}), it
|
|
|
7219 should be a regular expression that matches all lines that you want to
|
|
|
7220 hide. All lines that do not match this variable will remain visible.
|
|
|
7221
|
|
|
7222 For instance, if you just want to get rid of the @code{References} line
|
|
|
7223 and the @code{Xref} line, you might say:
|
|
|
7224
|
|
|
7225 @lisp
|
|
|
7226 (setq gnus-ignored-headers "^References:\\|^Xref:")
|
|
|
7227 @end lisp
|
|
|
7228
|
|
|
7229 This variable can also be a list of regexps to match headers that are to
|
|
|
7230 be removed.
|
|
|
7231
|
|
|
7232 Note that if @code{gnus-visible-headers} is non-@code{nil}, this
|
|
|
7233 variable will have no effect.
|
|
|
7234
|
|
|
7235 @end table
|
|
|
7236
|
|
|
7237 @vindex gnus-sorted-header-list
|
|
|
7238 Gnus can also sort the headers for you. (It does this by default.) You
|
|
|
7239 can control the sorting by setting the @code{gnus-sorted-header-list}
|
|
|
7240 variable. It is a list of regular expressions that says in what order
|
|
|
7241 the headers are to be displayed.
|
|
|
7242
|
|
|
7243 For instance, if you want the name of the author of the article first,
|
|
|
7244 and then the subject, you might say something like:
|
|
|
7245
|
|
|
7246 @lisp
|
|
|
7247 (setq gnus-sorted-header-list '("^From:" "^Subject:"))
|
|
|
7248 @end lisp
|
|
|
7249
|
|
|
7250 Any headers that are to remain visible, but are not listed in this
|
|
|
7251 variable, will be displayed in random order after all the headers that
|
|
|
7252 are listed in this variable.
|
|
|
7253
|
|
|
7254 @findex gnus-article-hide-boring-headers
|
|
|
7255 @vindex gnus-article-display-hook
|
|
|
7256 @vindex gnus-boring-article-headers
|
|
|
7257 You can hide further boring headers by entering
|
|
|
7258 @code{gnus-article-hide-boring-headers} into
|
|
|
7259 @code{gnus-article-display-hook}. What this function does depends on
|
|
|
7260 the @code{gnus-boring-article-headers} variable. It's a list, but this
|
|
|
7261 list doesn't actually contain header names. Instead is lists various
|
|
|
7262 @dfn{boring conditions} that Gnus can check and remove from sight.
|
|
|
7263
|
|
|
7264 These conditions are:
|
|
|
7265 @table @code
|
|
|
7266 @item empty
|
|
|
7267 Remove all empty headers.
|
|
|
7268 @item newsgroups
|
|
|
7269 Remove the @code{Newsgroups} header if it only contains the current group
|
|
|
7270 name.
|
|
|
7271 @item followup-to
|
|
|
7272 Remove the @code{Followup-To} header if it is identical to the
|
|
|
7273 @code{Newsgroups} header.
|
|
|
7274 @item reply-to
|
|
|
7275 Remove the @code{Reply-To} header if it lists the same address as the
|
|
|
7276 @code{From} header.
|
|
|
7277 @item date
|
|
|
7278 Remove the @code{Date} header if the article is less than three days
|
|
|
7279 old.
|
|
|
7280 @end table
|
|
|
7281
|
|
|
7282 To include the four first elements, you could say something like;
|
|
|
7283
|
|
|
7284 @lisp
|
|
|
7285 (setq gnus-boring-article-headers
|
|
|
7286 '(empty newsgroups followup-to reply-to))
|
|
|
7287 @end lisp
|
|
|
7288
|
|
|
7289 This is also the default value for this variable.
|
|
|
7290
|
|
|
7291
|
|
|
7292 @node Using MIME
|
|
|
7293 @section Using @sc{mime}
|
|
|
7294 @cindex @sc{mime}
|
|
|
7295
|
|
|
7296 Mime is a standard for waving your hands through the air, aimlessly,
|
|
|
7297 while people stand around yawning.
|
|
|
7298
|
|
|
7299 @sc{mime}, however, is a standard for encoding your articles, aimlessly,
|
|
|
7300 while all newsreaders die of fear.
|
|
|
7301
|
|
|
7302 @sc{mime} may specify what character set the article uses, the encoding
|
|
|
7303 of the characters, and it also makes it possible to embed pictures and
|
|
|
7304 other naughty stuff in innocent-looking articles.
|
|
|
7305
|
|
|
7306 @vindex gnus-show-mime
|
|
|
7307 @vindex gnus-show-mime-method
|
|
|
7308 @vindex gnus-strict-mime
|
|
|
7309 @findex metamail-buffer
|
|
16
|
7310 Gnus handles @sc{mime} by pushing the articles through
|
|
0
|
7311 @code{gnus-show-mime-method}, which is @code{metamail-buffer} by
|
|
|
7312 default. Set @code{gnus-show-mime} to @code{t} if you want to use
|
|
|
7313 @sc{mime} all the time. However, if @code{gnus-strict-mime} is
|
|
|
7314 non-@code{nil}, the @sc{mime} method will only be used if there are
|
|
16
|
7315 @sc{mime} headers in the article. If you have @code{gnus-show-mime}
|
|
|
7316 set, then you'll see some unfortunate display glitches in the article
|
|
|
7317 buffer. These can't be avoided.
|
|
0
|
7318
|
|
|
7319 It might be best to just use the toggling functions from the summary
|
|
|
7320 buffer to avoid getting nasty surprises. (For instance, you enter the
|
|
|
7321 group @samp{alt.sing-a-long} and, before you know it, @sc{mime} has
|
|
|
7322 decoded the sound file in the article and some horrible sing-a-long song
|
|
|
7323 comes streaming out out your speakers, and you can't find the volume
|
|
|
7324 button, because there isn't one, and people are starting to look at you,
|
|
|
7325 and you try to stop the program, but you can't, and you can't find the
|
|
|
7326 program to control the volume, and everybody else in the room suddenly
|
|
|
7327 decides to look at you disdainfully, and you'll feel rather stupid.)
|
|
|
7328
|
|
|
7329 Any similarity to real events and people is purely coincidental. Ahem.
|
|
|
7330
|
|
|
7331
|
|
|
7332 @node Customizing Articles
|
|
|
7333 @section Customizing Articles
|
|
|
7334 @cindex article customization
|
|
|
7335
|
|
|
7336 @vindex gnus-article-display-hook
|
|
|
7337 The @code{gnus-article-display-hook} is called after the article has
|
|
|
7338 been inserted into the article buffer. It is meant to handle all
|
|
|
7339 treatment of the article before it is displayed.
|
|
|
7340
|
|
|
7341 @findex gnus-article-maybe-highlight
|
|
16
|
7342 By default this hook just contains @code{gnus-article-hide-headers},
|
|
0
|
7343 @code{gnus-article-treat-overstrike}, and
|
|
|
7344 @code{gnus-article-maybe-highlight}, but there are thousands, nay
|
|
|
7345 millions, of functions you can put in this hook. For an overview of
|
|
|
7346 functions @pxref{Article Highlighting}, @pxref{Article Hiding},
|
|
|
7347 @pxref{Article Washing}, @pxref{Article Buttons} and @pxref{Article
|
|
16
|
7348 Date}. Note that the order of functions in this hook might affect
|
|
|
7349 things, so you may have to fiddle a bit to get the desired results.
|
|
0
|
7350
|
|
|
7351 You can, of course, write your own functions. The functions are called
|
|
|
7352 from the article buffer, and you can do anything you like, pretty much.
|
|
|
7353 There is no information that you have to keep in the buffer---you can
|
|
|
7354 change everything. However, you shouldn't delete any headers. Instead
|
|
|
7355 make them invisible if you want to make them go away.
|
|
|
7356
|
|
|
7357
|
|
|
7358 @node Article Keymap
|
|
|
7359 @section Article Keymap
|
|
|
7360
|
|
|
7361 Most of the keystrokes in the summary buffer can also be used in the
|
|
|
7362 article buffer. They should behave as if you typed them in the summary
|
|
|
7363 buffer, which means that you don't actually have to have a summary
|
|
|
7364 buffer displayed while reading. You can do it all from the article
|
|
|
7365 buffer.
|
|
|
7366
|
|
|
7367 A few additional keystrokes are available:
|
|
|
7368
|
|
|
7369 @table @kbd
|
|
|
7370
|
|
|
7371 @item SPACE
|
|
|
7372 @kindex SPACE (Article)
|
|
|
7373 @findex gnus-article-next-page
|
|
|
7374 Scroll forwards one page (@code{gnus-article-next-page}).
|
|
|
7375
|
|
|
7376 @item DEL
|
|
|
7377 @kindex DEL (Article)
|
|
|
7378 @findex gnus-article-prev-page
|
|
|
7379 Scroll backwards one page (@code{gnus-article-prev-page}).
|
|
|
7380
|
|
|
7381 @item C-c ^
|
|
|
7382 @kindex C-c ^ (Article)
|
|
|
7383 @findex gnus-article-refer-article
|
|
|
7384 If point is in the neighborhood of a @code{Message-ID} and you press
|
|
|
7385 @kbd{r}, Gnus will try to get that article from the server
|
|
|
7386 (@code{gnus-article-refer-article}).
|
|
|
7387
|
|
|
7388 @item C-c C-m
|
|
|
7389 @kindex C-c C-m (Article)
|
|
|
7390 @findex gnus-article-mail
|
|
|
7391 Send a reply to the address near point (@code{gnus-article-mail}). If
|
|
|
7392 given a prefix, include the mail.
|
|
|
7393
|
|
|
7394 @item s
|
|
|
7395 @kindex s (Article)
|
|
|
7396 @findex gnus-article-show-summary
|
|
|
7397 Reconfigure the buffers so that the summary buffer becomes visible
|
|
|
7398 (@code{gnus-article-show-summary}).
|
|
|
7399
|
|
|
7400 @item ?
|
|
|
7401 @kindex ? (Article)
|
|
|
7402 @findex gnus-article-describe-briefly
|
|
|
7403 Give a very brief description of the available keystrokes
|
|
|
7404 (@code{gnus-article-describe-briefly}).
|
|
|
7405
|
|
|
7406 @item TAB
|
|
|
7407 @kindex TAB (Article)
|
|
|
7408 @findex gnus-article-next-button
|
|
|
7409 Go to the next button, if any (@code{gnus-article-next-button}. This
|
|
|
7410 only makes sense if you have buttonizing turned on.
|
|
|
7411
|
|
|
7412 @item M-TAB
|
|
|
7413 @kindex M-TAB (Article)
|
|
|
7414 @findex gnus-article-prev-button
|
|
|
7415 Go to the previous button, if any (@code{gnus-article-prev-button}.
|
|
|
7416
|
|
|
7417 @end table
|
|
|
7418
|
|
|
7419
|
|
|
7420 @node Misc Article
|
|
|
7421 @section Misc Article
|
|
|
7422
|
|
|
7423 @table @code
|
|
|
7424
|
|
|
7425 @item gnus-single-article-buffer
|
|
|
7426 @vindex gnus-single-article-buffer
|
|
|
7427 If non-@code{nil}, use the same article buffer for all the groups.
|
|
|
7428 (This is the default.) If @code{nil}, each group will have its own
|
|
|
7429 article buffer.
|
|
|
7430
|
|
|
7431 @vindex gnus-article-prepare-hook
|
|
|
7432 @item gnus-article-prepare-hook
|
|
|
7433 This hook is called right after the article has been inserted into the
|
|
|
7434 article buffer. It is mainly intended for functions that do something
|
|
|
7435 depending on the contents; it should probably not be used for changing
|
|
|
7436 the contents of the article buffer.
|
|
|
7437
|
|
|
7438 @vindex gnus-article-display-hook
|
|
|
7439 @item gnus-article-display-hook
|
|
|
7440 This hook is called as the last thing when displaying an article, and is
|
|
|
7441 intended for modifying the contents of the buffer, doing highlights,
|
|
|
7442 hiding headers, and the like.
|
|
|
7443
|
|
|
7444 @item gnus-article-mode-hook
|
|
|
7445 @vindex gnus-article-mode-hook
|
|
|
7446 Hook called in article mode buffers.
|
|
|
7447
|
|
16
|
7448 @item gnus-article-mode-syntax-table
|
|
|
7449 @vindex gnus-article-mode-syntax-table
|
|
|
7450 Syntax table used in article buffers. It is initialized from
|
|
|
7451 @code{text-mode-syntax-table}.
|
|
|
7452
|
|
0
|
7453 @vindex gnus-article-mode-line-format
|
|
|
7454 @item gnus-article-mode-line-format
|
|
|
7455 This variable is a format string along the same lines as
|
|
16
|
7456 @code{gnus-summary-mode-line-format}. It accepts the same
|
|
|
7457 format specifications as that variable, with one extension:
|
|
|
7458
|
|
|
7459 @table @samp
|
|
|
7460 @item w
|
|
|
7461 The @dfn{wash status} of the article. This is a short string with one
|
|
|
7462 character for each possible article wash operation that may have been
|
|
|
7463 performed.
|
|
|
7464 @end table
|
|
|
7465
|
|
0
|
7466 @vindex gnus-break-pages
|
|
|
7467
|
|
|
7468 @item gnus-break-pages
|
|
|
7469 Controls whether @dfn{page breaking} is to take place. If this variable
|
|
|
7470 is non-@code{nil}, the articles will be divided into pages whenever a
|
|
|
7471 page delimiter appears in the article. If this variable is @code{nil},
|
|
|
7472 paging will not be done.
|
|
|
7473
|
|
|
7474 @item gnus-page-delimiter
|
|
|
7475 @vindex gnus-page-delimiter
|
|
|
7476 This is the delimiter mentioned above. By default, it is @samp{^L}
|
|
|
7477 (form linefeed).
|
|
|
7478 @end table
|
|
|
7479
|
|
|
7480
|
|
|
7481 @node Composing Messages
|
|
|
7482 @chapter Composing Messages
|
|
|
7483 @cindex reply
|
|
|
7484 @cindex followup
|
|
|
7485 @cindex post
|
|
|
7486
|
|
|
7487 @kindex C-c C-c (Post)
|
|
|
7488 All commands for posting and mailing will put you in a message buffer
|
|
|
7489 where you can edit the article all you like, before you send the article
|
|
|
7490 by pressing @kbd{C-c C-c}. @xref{Top, , Top, message, The Message
|
|
|
7491 Manual}. If you are in a foreign news group, and you wish to post the
|
|
|
7492 article using the foreign server, you can give a prefix to @kbd{C-c C-c}
|
|
|
7493 to make Gnus try to post using the foreign server.
|
|
|
7494
|
|
|
7495 @menu
|
|
|
7496 * Mail:: Mailing and replying.
|
|
|
7497 * Post:: Posting and following up.
|
|
|
7498 * Posting Server:: What server should you post via?
|
|
|
7499 * Mail and Post:: Mailing and posting at the same time.
|
|
|
7500 * Archived Messages:: Where Gnus stores the messages you've sent.
|
|
|
7501 @c * Posting Styles:: An easier way to configure some key elements.
|
|
|
7502 @c * Drafts:: Postponing messages and rejected messages.
|
|
|
7503 @c * Rejected Articles:: What happens if the server doesn't like your article?
|
|
|
7504 @end menu
|
|
|
7505
|
|
|
7506 Also see @pxref{Canceling and Superseding} for information on how to
|
|
|
7507 remove articles you shouldn't have posted.
|
|
|
7508
|
|
|
7509
|
|
|
7510 @node Mail
|
|
|
7511 @section Mail
|
|
|
7512
|
|
|
7513 Variables for customizing outgoing mail:
|
|
|
7514
|
|
|
7515 @table @code
|
|
|
7516 @item gnus-uu-digest-headers
|
|
|
7517 @vindex gnus-uu-digest-headers
|
|
|
7518 List of regexps to match headers included in digested messages. The
|
|
|
7519 headers will be included in the sequence they are matched.
|
|
|
7520
|
|
|
7521 @end table
|
|
|
7522
|
|
|
7523
|
|
|
7524 @node Post
|
|
|
7525 @section Post
|
|
|
7526
|
|
|
7527 Variables for composing news articles:
|
|
|
7528
|
|
|
7529 @table @code
|
|
|
7530 @item gnus-sent-message-ids-file
|
|
|
7531 @vindex gnus-sent-message-ids-file
|
|
|
7532 Gnus will keep a @code{Message-ID} history file of all the mails it has
|
|
|
7533 sent. If it discovers that it has already sent a mail, it will ask the
|
|
|
7534 user whether to re-send the mail. (This is primarily useful when
|
|
|
7535 dealing with @sc{soup} packets and the like where one is apt to sent the
|
|
|
7536 same packet multiple times.) This variable says what the name of this
|
|
|
7537 history file is. It is @file{~/News/Sent-Message-IDs} by default. Set
|
|
|
7538 this variable to @code{nil} if you don't want Gnus to keep a history
|
|
|
7539 file.
|
|
|
7540
|
|
|
7541 @item gnus-sent-message-ids-length
|
|
|
7542 @vindex gnus-sent-message-ids-length
|
|
|
7543 This variable says how many @code{Message-ID}s to keep in the history
|
|
|
7544 file. It is 1000 by default.
|
|
|
7545
|
|
|
7546 @end table
|
|
|
7547
|
|
|
7548
|
|
|
7549 @node Posting Server
|
|
|
7550 @section Posting Server
|
|
|
7551
|
|
|
7552 When you press those magical @kbd{C-c C-c} keys to ship off your latest
|
|
|
7553 (extremely intelligent, of course) article, where does it go?
|
|
|
7554
|
|
|
7555 Thank you for asking. I hate you.
|
|
|
7556
|
|
|
7557 @vindex gnus-post-method
|
|
|
7558
|
|
|
7559 It can be quite complicated. Normally, Gnus will use the same native
|
|
|
7560 server. However. If your native server doesn't allow posting, just
|
|
|
7561 reading, you probably want to use some other server to post your
|
|
|
7562 (extremely intelligent and fabulously interesting) articles. You can
|
|
|
7563 then set the @code{gnus-post-method} to some other method:
|
|
|
7564
|
|
|
7565 @lisp
|
|
|
7566 (setq gnus-post-method '(nnspool ""))
|
|
|
7567 @end lisp
|
|
|
7568
|
|
|
7569 Now, if you've done this, and then this server rejects your article, or
|
|
|
7570 this server is down, what do you do then? To override this variable you
|
|
|
7571 can use a non-zero prefix to the @kbd{C-c C-c} command to force using
|
|
|
7572 the ``current'' server for posting.
|
|
|
7573
|
|
16
|
7574 If you give a zero prefix (i.e., @kbd{C-u 0 C-c C-c}) to that command,
|
|
0
|
7575 Gnus will prompt you for what method to use for posting.
|
|
|
7576
|
|
|
7577 You can also set @code{gnus-post-method} to a list of select methods.
|
|
|
7578 If that's the case, Gnus will always prompt you for what method to use
|
|
|
7579 for posting.
|
|
|
7580
|
|
|
7581
|
|
|
7582 @node Mail and Post
|
|
|
7583 @section Mail and Post
|
|
|
7584
|
|
|
7585 Here's a list of variables that are relevant to both mailing and
|
|
|
7586 posting:
|
|
|
7587
|
|
|
7588 @table @code
|
|
|
7589 @item gnus-mailing-list-groups
|
|
|
7590 @findex gnus-mailing-list-groups
|
|
|
7591 @cindex mailing lists
|
|
|
7592
|
|
|
7593 If your news server offers groups that are really mailing lists that are
|
|
|
7594 gatewayed to the @sc{nntp} server, you can read those groups without
|
|
|
7595 problems, but you can't post/followup to them without some difficulty.
|
|
|
7596 One solution is to add a @code{to-address} to the group parameters
|
|
|
7597 (@pxref{Group Parameters}). An easier thing to do is set the
|
|
|
7598 @code{gnus-mailing-list-groups} to a regexp that match the groups that
|
|
|
7599 really are mailing lists. Then, at least, followups to the mailing
|
|
|
7600 lists will work most of the time. Posting to these groups (@kbd{a}) is
|
|
|
7601 still a pain, though.
|
|
|
7602
|
|
|
7603 @end table
|
|
|
7604
|
|
|
7605 You may want to do spell-checking on messages that you send out. Or, if
|
|
|
7606 you don't want to spell-check by hand, you could add automatic
|
|
|
7607 spell-checking via the @code{ispell} package:
|
|
|
7608
|
|
|
7609 @cindex ispell
|
|
|
7610 @findex ispell-message
|
|
|
7611 @lisp
|
|
|
7612 (add-hook 'message-send-hook 'ispell-message)
|
|
|
7613 @end lisp
|
|
|
7614
|
|
|
7615
|
|
|
7616 @node Archived Messages
|
|
|
7617 @section Archived Messages
|
|
|
7618 @cindex archived messages
|
|
|
7619 @cindex sent messages
|
|
|
7620
|
|
26
|
7621 Gnus provides a few different methods for storing the mail and news you
|
|
|
7622 send. The default method is to use the @dfn{archive virtual server} to
|
|
|
7623 store the messages. If you want to disable this completely, the
|
|
22
|
7624 @code{gnus-message-archive-group} variable should be @code{nil}, which
|
|
|
7625 is the default.
|
|
0
|
7626
|
|
|
7627 @vindex gnus-message-archive-method
|
|
|
7628 @code{gnus-message-archive-method} says what virtual server Gnus is to
|
|
16
|
7629 use to store sent messages. The default is:
|
|
|
7630
|
|
|
7631 @lisp
|
|
|
7632 (nnfolder "archive"
|
|
|
7633 (nnfolder-directory "~/Mail/archive/"))
|
|
|
7634 @end lisp
|
|
|
7635
|
|
|
7636 You can, however, use any mail select method (@code{nnml},
|
|
|
7637 @code{nnmbox}, etc.). @code{nnfolder} is a quite likeable select method
|
|
|
7638 for doing this sort of thing, though. If you don't like the default
|
|
|
7639 directory chosen, you could say something like:
|
|
0
|
7640
|
|
|
7641 @lisp
|
|
|
7642 (setq gnus-message-archive-method
|
|
|
7643 '(nnfolder "archive"
|
|
|
7644 (nnfolder-inhibit-expiry t)
|
|
|
7645 (nnfolder-active-file "~/News/sent-mail/active")
|
|
|
7646 (nnfolder-directory "~/News/sent-mail/")))
|
|
|
7647 @end lisp
|
|
|
7648
|
|
|
7649 @vindex gnus-message-archive-group
|
|
|
7650 @cindex Gcc
|
|
|
7651 Gnus will insert @code{Gcc} headers in all outgoing messages that point
|
|
|
7652 to one or more group(s) on that server. Which group to use is
|
|
|
7653 determined by the @code{gnus-message-archive-group} variable.
|
|
|
7654
|
|
|
7655 This variable can be:
|
|
|
7656
|
|
|
7657 @itemize @bullet
|
|
|
7658 @item a string
|
|
|
7659 Messages will be saved in that group.
|
|
|
7660 @item a list of strings
|
|
|
7661 Messages will be saved in all those groups.
|
|
|
7662 @item an alist of regexps, functions and forms
|
|
|
7663 When a key ``matches'', the result is used.
|
|
2
|
7664 @item @code{nil}
|
|
|
7665 No message archiving will take place. This is the default.
|
|
0
|
7666 @end itemize
|
|
|
7667
|
|
|
7668 Let's illustrate:
|
|
|
7669
|
|
|
7670 Just saving to a single group called @samp{MisK}:
|
|
|
7671 @lisp
|
|
|
7672 (setq gnus-message-archive-group "MisK")
|
|
|
7673 @end lisp
|
|
|
7674
|
|
|
7675 Saving to two groups, @samp{MisK} and @samp{safe}:
|
|
|
7676 @lisp
|
|
|
7677 (setq gnus-message-archive-group '("MisK" "safe"))
|
|
|
7678 @end lisp
|
|
|
7679
|
|
|
7680 Save to different groups based on what group you are in:
|
|
|
7681 @lisp
|
|
|
7682 (setq gnus-message-archive-group
|
|
|
7683 '(("^alt" "sent-to-alt")
|
|
|
7684 ("mail" "sent-to-mail")
|
|
|
7685 (".*" "sent-to-misc")))
|
|
|
7686 @end lisp
|
|
|
7687
|
|
|
7688 More complex stuff:
|
|
|
7689 @lisp
|
|
|
7690 (setq gnus-message-archive-group
|
|
|
7691 '((if (message-news-p)
|
|
|
7692 "misc-news"
|
|
|
7693 "misc-mail")))
|
|
|
7694 @end lisp
|
|
|
7695
|
|
|
7696 How about storing all news messages in one file, but storing all mail
|
|
|
7697 messages in one file per month:
|
|
|
7698
|
|
|
7699 @lisp
|
|
|
7700 (setq gnus-message-archive-group
|
|
|
7701 '((if (message-news-p)
|
|
|
7702 "misc-news"
|
|
|
7703 (concat "mail." (format-time-string
|
|
|
7704 "%Y-%m" (current-time))))))
|
|
|
7705 @end lisp
|
|
|
7706
|
|
|
7707 Now, when you send a message off, it will be stored in the appropriate
|
|
|
7708 group. (If you want to disable storing for just one particular message,
|
|
|
7709 you can just remove the @code{Gcc} header that has been inserted.) The
|
|
|
7710 archive group will appear in the group buffer the next time you start
|
|
|
7711 Gnus, or the next time you press @kbd{F} in the group buffer. You can
|
|
|
7712 enter it and read the articles in it just like you'd read any other
|
|
|
7713 group. If the group gets really big and annoying, you can simply rename
|
|
2
|
7714 if (using @kbd{G r} in the group buffer) to something
|
|
|
7715 nice---@samp{misc-mail-september-1995}, or whatever. New messages will
|
|
0
|
7716 continue to be stored in the old (now empty) group.
|
|
|
7717
|
|
26
|
7718 That's the default method of archiving sent messages. Gnus also a
|
|
|
7719 different way for the people who don't like the default method. In that
|
|
|
7720 case you should set @code{gnus-message-archive-group} to @code{nil};
|
|
|
7721 this will disable archiving.
|
|
0
|
7722
|
|
|
7723 XEmacs 19.13 doesn't have @code{format-time-string}, so you'll have to
|
|
|
7724 use a different value for @code{gnus-message-archive-group} there.
|
|
|
7725
|
|
|
7726 @table @code
|
|
|
7727 @item gnus-outgoing-message-group
|
|
|
7728 @vindex gnus-outgoing-message-group
|
|
|
7729 All outgoing messages will be put in this group. If you want to store
|
|
|
7730 all your outgoing mail and articles in the group @samp{nnml:archive},
|
|
|
7731 you set this variable to that value. This variable can also be a list of
|
|
|
7732 group names.
|
|
|
7733
|
|
|
7734 If you want to have greater control over what group to put each
|
|
|
7735 message in, you can set this variable to a function that checks the
|
|
|
7736 current newsgroup name and then returns a suitable group name (or list
|
|
|
7737 of names).
|
|
26
|
7738
|
|
|
7739 This variable can be used instead of @code{gnus-message-archive-group},
|
|
|
7740 but the latter is the preferred method.
|
|
0
|
7741 @end table
|
|
|
7742
|
|
|
7743
|
|
|
7744 @c @node Posting Styles
|
|
|
7745 @c @section Posting Styles
|
|
|
7746 @c @cindex posting styles
|
|
|
7747 @c @cindex styles
|
|
|
7748 @c
|
|
|
7749 @c All them variables, they make my head swim.
|
|
|
7750 @c
|
|
|
7751 @c So what if you want a different @code{Organization} and signature based
|
|
|
7752 @c on what groups you post to? And you post both from your home machine
|
|
|
7753 @c and your work machine, and you want different @code{From} lines, and so
|
|
|
7754 @c on?
|
|
|
7755 @c
|
|
|
7756 @c @vindex gnus-posting-styles
|
|
|
7757 @c One way to do stuff like that is to write clever hooks that change the
|
|
|
7758 @c variables you need to have changed. That's a bit boring, so somebody
|
|
|
7759 @c came up with the bright idea of letting the user specify these things in
|
|
|
7760 @c a handy alist. Here's an example of a @code{gnus-posting-styles}
|
|
|
7761 @c variable:
|
|
|
7762 @c
|
|
|
7763 @c @lisp
|
|
|
7764 @c ((".*"
|
|
|
7765 @c (signature . "Peace and happiness")
|
|
|
7766 @c (organization . "What me?"))
|
|
|
7767 @c ("^comp"
|
|
|
7768 @c (signature . "Death to everybody"))
|
|
|
7769 @c ("comp.emacs.i-love-it"
|
|
|
7770 @c (organization . "Emacs is it")))
|
|
|
7771 @c @end lisp
|
|
|
7772 @c
|
|
|
7773 @c As you might surmise from this example, this alist consists of several
|
|
|
7774 @c @dfn{styles}. Each style will be applicable if the first element
|
|
|
7775 @c ``matches'', in some form or other. The entire alist will be iterated
|
|
|
7776 @c over, from the beginning towards the end, and each match will be
|
|
|
7777 @c applied, which means that attributes in later styles that match override
|
|
|
7778 @c the same attributes in earlier matching styles. So
|
|
|
7779 @c @samp{comp.programming.literate} will have the @samp{Death to everybody}
|
|
|
7780 @c signature and the @samp{What me?} @code{Organization} header.
|
|
|
7781 @c
|
|
|
7782 @c The first element in each style is called the @code{match}. If it's a
|
|
|
7783 @c string, then Gnus will try to regexp match it against the group name.
|
|
|
7784 @c If it's a function symbol, that function will be called with no
|
|
|
7785 @c arguments. If it's a variable symbol, then the variable will be
|
|
|
7786 @c referenced. If it's a list, then that list will be @code{eval}ed. In
|
|
|
7787 @c any case, if this returns a non-@code{nil} value, then the style is said
|
|
|
7788 @c to @dfn{match}.
|
|
|
7789 @c
|
|
|
7790 @c Each style may contain a arbitrary amount of @dfn{attributes}. Each
|
|
|
7791 @c attribute consists of a @var{(name . value)} pair. The attribute name
|
|
|
7792 @c can be one of @code{signature}, @code{organization} or @code{from}. The
|
|
|
7793 @c attribute name can also be a string. In that case, this will be used as
|
|
|
7794 @c a header name, and the value will be inserted in the headers of the
|
|
|
7795 @c article.
|
|
|
7796 @c
|
|
|
7797 @c The attribute value can be a string (used verbatim), a function (the
|
|
|
7798 @c return value will be used), a variable (its value will be used) or a
|
|
|
7799 @c list (it will be @code{eval}ed and the return value will be used).
|
|
|
7800 @c
|
|
|
7801 @c So here's a new example:
|
|
|
7802 @c
|
|
|
7803 @c @lisp
|
|
|
7804 @c (setq gnus-posting-styles
|
|
|
7805 @c '((".*"
|
|
|
7806 @c (signature . "~/.signature")
|
|
|
7807 @c (from . "user@@foo (user)")
|
|
|
7808 @c ("X-Home-Page" . (getenv "WWW_HOME"))
|
|
|
7809 @c (organization . "People's Front Against MWM"))
|
|
|
7810 @c ("^rec.humor"
|
|
|
7811 @c (signature . my-funny-signature-randomizer))
|
|
|
7812 @c ((equal (system-name) "gnarly")
|
|
|
7813 @c (signature . my-quote-randomizer))
|
|
|
7814 @c (posting-from-work-p
|
|
|
7815 @c (signature . "~/.work-signature")
|
|
|
7816 @c (from . "user@@bar.foo (user)")
|
|
|
7817 @c (organization . "Important Work, Inc"))
|
|
|
7818 @c ("^nn.+:"
|
|
|
7819 @c (signature . "~/.mail-signature"))))
|
|
|
7820 @c @end lisp
|
|
|
7821
|
|
|
7822 @c @node Drafts
|
|
|
7823 @c @section Drafts
|
|
|
7824 @c @cindex drafts
|
|
|
7825 @c
|
|
|
7826 @c If you are writing a message (mail or news) and suddenly remember that
|
|
|
7827 @c you have a steak in the oven (or some pesto in the food processor, you
|
|
|
7828 @c craazy vegetarians), you'll probably wish there was a method to save the
|
|
|
7829 @c message you are writing so that you can continue editing it some other
|
|
|
7830 @c day, and send it when you feel its finished.
|
|
|
7831 @c
|
|
|
7832 @c Well, don't worry about it. Whenever you start composing a message of
|
|
|
7833 @c some sort using the Gnus mail and post commands, the buffer you get will
|
|
|
7834 @c automatically associate to an article in a special @dfn{draft} group.
|
|
|
7835 @c If you save the buffer the normal way (@kbd{C-x C-s}, for instance), the
|
|
|
7836 @c article will be saved there. (Auto-save files also go to the draft
|
|
|
7837 @c group.)
|
|
|
7838 @c
|
|
|
7839 @c @cindex nndraft
|
|
|
7840 @c @vindex gnus-draft-group-directory
|
|
|
7841 @c The draft group is a special group (which is implemented as an
|
|
|
7842 @c @code{nndraft} group, if you absolutely have to know) called
|
|
|
7843 @c @samp{nndraft:drafts}. The variable @code{gnus-draft-group-directory}
|
|
|
7844 @c controls both the name of the group and the location---the leaf element
|
|
|
7845 @c in the path will be used as the name of the group. What makes this
|
|
|
7846 @c group special is that you can't tick any articles in it or mark any
|
|
|
7847 @c articles as read---all articles in the group are permanently unread.
|
|
|
7848 @c
|
|
|
7849 @c If the group doesn't exist, it will be created and you'll be subscribed
|
|
|
7850 @c to it.
|
|
|
7851 @c
|
|
|
7852 @c @findex gnus-dissociate-buffer-from-draft
|
|
|
7853 @c @kindex C-c M-d (Mail)
|
|
|
7854 @c @kindex C-c M-d (Post)
|
|
|
7855 @c @findex gnus-associate-buffer-with-draft
|
|
|
7856 @c @kindex C-c C-d (Mail)
|
|
|
7857 @c @kindex C-c C-d (Post)
|
|
|
7858 @c If you're writing some super-secret message that you later want to
|
|
|
7859 @c encode with PGP before sending, you may wish to turn the auto-saving
|
|
|
7860 @c (and association with the draft group) off. You never know who might be
|
|
|
7861 @c interested in reading all your extremely valuable and terribly horrible
|
|
|
7862 @c and interesting secrets. The @kbd{C-c M-d}
|
|
|
7863 @c (@code{gnus-dissociate-buffer-from-draft}) command does that for you.
|
|
|
7864 @c If you change your mind and want to turn the auto-saving back on again,
|
|
|
7865 @c @kbd{C-c C-d} (@code{gnus-associate-buffer-with-draft} does that.
|
|
|
7866 @c
|
|
|
7867 @c @vindex gnus-use-draft
|
|
|
7868 @c To leave association with the draft group off by default, set
|
|
|
7869 @c @code{gnus-use-draft} to @code{nil}. It is @code{t} by default.
|
|
|
7870 @c
|
|
|
7871 @c @findex gnus-summary-send-draft
|
|
|
7872 @c @kindex S D c (Summary)
|
|
|
7873 @c When you want to continue editing the article, you simply enter the
|
|
|
7874 @c draft group and push @kbd{S D c} (@code{gnus-summary-send-draft}) to do
|
|
|
7875 @c that. You will be placed in a buffer where you left off.
|
|
|
7876 @c
|
|
|
7877 @c Rejected articles will also be put in this draft group (@pxref{Rejected
|
|
|
7878 @c Articles}).
|
|
|
7879 @c
|
|
|
7880 @c @findex gnus-summary-send-all-drafts
|
|
|
7881 @c If you have lots of rejected messages you want to post (or mail) without
|
|
|
7882 @c doing further editing, you can use the @kbd{S D a} command
|
|
|
7883 @c (@code{gnus-summary-send-all-drafts}). This command understands the
|
|
|
7884 @c process/prefix convention (@pxref{Process/Prefix}).
|
|
|
7885 @c
|
|
|
7886 @c
|
|
|
7887 @c @node Rejected Articles
|
|
|
7888 @c @section Rejected Articles
|
|
|
7889 @c @cindex rejected articles
|
|
|
7890 @c
|
|
|
7891 @c Sometimes a news server will reject an article. Perhaps the server
|
|
|
7892 @c doesn't like your face. Perhaps it just feels miserable. Perhaps
|
|
|
7893 @c @emph{there be demons}. Perhaps you have included too much cited text.
|
|
|
7894 @c Perhaps the disk is full. Perhaps the server is down.
|
|
|
7895 @c
|
|
|
7896 @c These situations are, of course, totally beyond the control of Gnus.
|
|
|
7897 @c (Gnus, of course, loves the way you look, always feels great, has angels
|
|
|
7898 @c fluttering around inside of it, doesn't care about how much cited text
|
|
|
7899 @c you include, never runs full and never goes down.) So Gnus saves these
|
|
|
7900 @c articles until some later time when the server feels better.
|
|
|
7901 @c
|
|
|
7902 @c The rejected articles will automatically be put in a special draft group
|
|
|
7903 @c (@pxref{Drafts}). When the server comes back up again, you'd then
|
|
|
7904 @c typically enter that group and send all the articles off.
|
|
|
7905 @c
|
|
|
7906
|
|
|
7907 @node Select Methods
|
|
|
7908 @chapter Select Methods
|
|
|
7909 @cindex foreign groups
|
|
|
7910 @cindex select methods
|
|
|
7911
|
|
|
7912 A @dfn{foreign group} is a group that is not read by the usual (or
|
|
|
7913 default) means. It could be, for instance, a group from a different
|
|
|
7914 @sc{nntp} server, it could be a virtual group, or it could be your own
|
|
|
7915 personal mail group.
|
|
|
7916
|
|
|
7917 A foreign group (or any group, really) is specified by a @dfn{name} and
|
|
|
7918 a @dfn{select method}. To take the latter first, a select method is a
|
|
16
|
7919 list where the first element says what backend to use (e.g. @code{nntp},
|
|
0
|
7920 @code{nnspool}, @code{nnml}) and the second element is the @dfn{server
|
|
|
7921 name}. There may be additional elements in the select method, where the
|
|
|
7922 value may have special meaning for the backend in question.
|
|
|
7923
|
|
|
7924 One could say that a select method defines a @dfn{virtual server}---so
|
|
|
7925 we do just that (@pxref{The Server Buffer}).
|
|
|
7926
|
|
|
7927 The @dfn{name} of the group is the name the backend will recognize the
|
|
|
7928 group as.
|
|
|
7929
|
|
|
7930 For instance, the group @samp{soc.motss} on the @sc{nntp} server
|
|
|
7931 @samp{some.where.edu} will have the name @samp{soc.motss} and select
|
|
16
|
7932 method @code{(nntp "some.where.edu")}. Gnus will call this group
|
|
|
7933 @samp{nntp+some.where.edu:soc.motss}, even though the @code{nntp}
|
|
|
7934 backend just knows this group as @samp{soc.motss}.
|
|
0
|
7935
|
|
|
7936 The different methods all have their peculiarities, of course.
|
|
|
7937
|
|
|
7938 @menu
|
|
|
7939 * The Server Buffer:: Making and editing virtual servers.
|
|
|
7940 * Getting News:: Reading USENET news with Gnus.
|
|
|
7941 * Getting Mail:: Reading your personal mail with Gnus.
|
|
|
7942 * Other Sources:: Reading directories, files, SOUP packets.
|
|
|
7943 * Combined Groups:: Combining groups into one group.
|
|
|
7944 @end menu
|
|
|
7945
|
|
|
7946
|
|
|
7947 @node The Server Buffer
|
|
|
7948 @section The Server Buffer
|
|
|
7949
|
|
|
7950 Traditionally, a @dfn{server} is a machine or a piece of software that
|
|
|
7951 one connects to, and then requests information from. Gnus does not
|
|
|
7952 connect directly to any real servers, but does all transactions through
|
|
|
7953 one backend or other. But that's just putting one layer more between
|
|
|
7954 the actual media and Gnus, so we might just as well say that each
|
|
|
7955 backend represents a virtual server.
|
|
|
7956
|
|
|
7957 For instance, the @code{nntp} backend may be used to connect to several
|
|
|
7958 different actual @sc{nntp} servers, or, perhaps, to many different ports
|
|
|
7959 on the same actual @sc{nntp} server. You tell Gnus which backend to
|
|
|
7960 use, and what parameters to set by specifying a @dfn{select method}.
|
|
|
7961
|
|
|
7962 These select methods specifications can sometimes become quite
|
|
|
7963 complicated---say, for instance, that you want to read from the
|
|
16
|
7964 @sc{nntp} server @samp{news.funet.fi} on port number 13, which
|
|
0
|
7965 hangs if queried for @sc{nov} headers and has a buggy select. Ahem.
|
|
|
7966 Anyways, if you had to specify that for each group that used this
|
|
|
7967 server, that would be too much work, so Gnus offers a way of naming
|
|
|
7968 select methods, which is what you do in the server buffer.
|
|
|
7969
|
|
|
7970 To enter the server buffer, user the @kbd{^}
|
|
|
7971 (@code{gnus-group-enter-server-mode}) command in the group buffer.
|
|
|
7972
|
|
|
7973 @menu
|
|
|
7974 * Server Buffer Format:: You can customize the look of this buffer.
|
|
|
7975 * Server Commands:: Commands to manipulate servers.
|
|
|
7976 * Example Methods:: Examples server specifications.
|
|
|
7977 * Creating a Virtual Server:: An example session.
|
|
24
|
7978 * Server Variables:: Which variables to set.
|
|
0
|
7979 * Servers and Methods:: You can use server names as select methods.
|
|
|
7980 * Unavailable Servers:: Some servers you try to contact may be down.
|
|
|
7981 @end menu
|
|
|
7982
|
|
|
7983 @vindex gnus-server-mode-hook
|
|
|
7984 @code{gnus-server-mode-hook} is run when creating the server buffer.
|
|
|
7985
|
|
|
7986
|
|
|
7987 @node Server Buffer Format
|
|
|
7988 @subsection Server Buffer Format
|
|
|
7989 @cindex server buffer format
|
|
|
7990
|
|
|
7991 @vindex gnus-server-line-format
|
|
|
7992 You can change the look of the server buffer lines by changing the
|
|
|
7993 @code{gnus-server-line-format} variable. This is a @code{format}-like
|
|
|
7994 variable, with some simple extensions:
|
|
|
7995
|
|
|
7996 @table @samp
|
|
|
7997
|
|
|
7998 @item h
|
|
|
7999 How the news is fetched---the backend name.
|
|
|
8000
|
|
|
8001 @item n
|
|
|
8002 The name of this server.
|
|
|
8003
|
|
|
8004 @item w
|
|
|
8005 Where the news is to be fetched from---the address.
|
|
|
8006
|
|
|
8007 @item s
|
|
|
8008 The opened/closed/denied status of the server.
|
|
|
8009 @end table
|
|
|
8010
|
|
|
8011 @vindex gnus-server-mode-line-format
|
|
|
8012 The mode line can also be customized by using the
|
|
|
8013 @code{gnus-server-mode-line-format} variable. The following specs are
|
|
|
8014 understood:
|
|
|
8015
|
|
|
8016 @table @samp
|
|
|
8017 @item S
|
|
|
8018 Server name.
|
|
|
8019
|
|
|
8020 @item M
|
|
|
8021 Server method.
|
|
|
8022 @end table
|
|
|
8023
|
|
|
8024 Also @pxref{Formatting Variables}.
|
|
|
8025
|
|
|
8026
|
|
|
8027 @node Server Commands
|
|
|
8028 @subsection Server Commands
|
|
|
8029 @cindex server commands
|
|
|
8030
|
|
|
8031 @table @kbd
|
|
|
8032
|
|
|
8033 @item a
|
|
|
8034 @kindex a (Server)
|
|
|
8035 @findex gnus-server-add-server
|
|
|
8036 Add a new server (@code{gnus-server-add-server}).
|
|
|
8037
|
|
|
8038 @item e
|
|
|
8039 @kindex e (Server)
|
|
|
8040 @findex gnus-server-edit-server
|
|
|
8041 Edit a server (@code{gnus-server-edit-server}).
|
|
|
8042
|
|
|
8043 @item SPACE
|
|
|
8044 @kindex SPACE (Server)
|
|
|
8045 @findex gnus-server-read-server
|
|
|
8046 Browse the current server (@code{gnus-server-read-server}).
|
|
|
8047
|
|
|
8048 @item q
|
|
|
8049 @kindex q (Server)
|
|
|
8050 @findex gnus-server-exit
|
|
|
8051 Return to the group buffer (@code{gnus-server-exit}).
|
|
|
8052
|
|
|
8053 @item k
|
|
|
8054 @kindex k (Server)
|
|
|
8055 @findex gnus-server-kill-server
|
|
|
8056 Kill the current server (@code{gnus-server-kill-server}).
|
|
|
8057
|
|
|
8058 @item y
|
|
|
8059 @kindex y (Server)
|
|
|
8060 @findex gnus-server-yank-server
|
|
|
8061 Yank the previously killed server (@code{gnus-server-yank-server}).
|
|
|
8062
|
|
|
8063 @item c
|
|
|
8064 @kindex c (Server)
|
|
|
8065 @findex gnus-server-copy-server
|
|
|
8066 Copy the current server (@code{gnus-server-copy-server}).
|
|
|
8067
|
|
|
8068 @item l
|
|
|
8069 @kindex l (Server)
|
|
|
8070 @findex gnus-server-list-servers
|
|
|
8071 List all servers (@code{gnus-server-list-servers}).
|
|
|
8072
|
|
16
|
8073 @item s
|
|
|
8074 @kindex s (Server)
|
|
|
8075 @findex gnus-server-scan-server
|
|
|
8076 Request that the server scan its sources for new articles
|
|
|
8077 (@code{gnus-server-scan-server}). This is mainly sensible with mail
|
|
|
8078 servers.
|
|
|
8079
|
|
|
8080 @item g
|
|
|
8081 @kindex g (Server)
|
|
|
8082 @findex gnus-server-regenerate-server
|
|
|
8083 Request that the server regenerate all its data structures
|
|
|
8084 (@code{gnus-server-regenerate-server}). This can be useful if you have
|
|
|
8085 a mail backend that has gotten out of synch.
|
|
|
8086
|
|
0
|
8087 @end table
|
|
|
8088
|
|
|
8089
|
|
|
8090 @node Example Methods
|
|
|
8091 @subsection Example Methods
|
|
|
8092
|
|
|
8093 Most select methods are pretty simple and self-explanatory:
|
|
|
8094
|
|
|
8095 @lisp
|
|
|
8096 (nntp "news.funet.fi")
|
|
|
8097 @end lisp
|
|
|
8098
|
|
|
8099 Reading directly from the spool is even simpler:
|
|
|
8100
|
|
|
8101 @lisp
|
|
|
8102 (nnspool "")
|
|
|
8103 @end lisp
|
|
|
8104
|
|
|
8105 As you can see, the first element in a select method is the name of the
|
|
|
8106 backend, and the second is the @dfn{address}, or @dfn{name}, if you
|
|
|
8107 will.
|
|
|
8108
|
|
|
8109 After these two elements, there may be a arbitrary number of
|
|
|
8110 @var{(variable form)} pairs.
|
|
|
8111
|
|
|
8112 To go back to the first example---imagine that you want to read from
|
|
16
|
8113 port 15 from that machine. This is what the select method should
|
|
0
|
8114 look like then:
|
|
|
8115
|
|
|
8116 @lisp
|
|
|
8117 (nntp "news.funet.fi" (nntp-port-number 15))
|
|
|
8118 @end lisp
|
|
|
8119
|
|
|
8120 You should read the documentation to each backend to find out what
|
|
|
8121 variables are relevant, but here's an @code{nnmh} example.
|
|
|
8122
|
|
|
8123 @code{nnmh} is a mail backend that reads a spool-like structure. Say
|
|
|
8124 you have two structures that you wish to access: One is your private
|
|
|
8125 mail spool, and the other is a public one. Here's the possible spec for
|
|
|
8126 you private mail:
|
|
|
8127
|
|
|
8128 @lisp
|
|
|
8129 (nnmh "private" (nnmh-directory "~/private/mail/"))
|
|
|
8130 @end lisp
|
|
|
8131
|
|
|
8132 (This server is then called @samp{private}, but you may have guessed
|
|
|
8133 that.)
|
|
|
8134
|
|
|
8135 Here's the method for a public spool:
|
|
|
8136
|
|
|
8137 @lisp
|
|
|
8138 (nnmh "public"
|
|
|
8139 (nnmh-directory "/usr/information/spool/")
|
|
|
8140 (nnmh-get-new-mail nil))
|
|
|
8141 @end lisp
|
|
|
8142
|
|
16
|
8143 If you are behind a firewall and only have access to the @sc{nntp}
|
|
|
8144 server from the firewall machine, you can instruct Gnus to @code{rlogin}
|
|
|
8145 on the firewall machine and telnet from there to the @sc{nntp} server.
|
|
|
8146 Doing this can be rather fiddly, but your virtual server definition
|
|
|
8147 should probably look something like this:
|
|
|
8148
|
|
|
8149 @lisp
|
|
|
8150 (nntp "firewall"
|
|
|
8151 (nntp-address "the.firewall.machine")
|
|
|
8152 (nntp-open-connection-function nntp-open-rlogin)
|
|
|
8153 (nntp-end-of-line "\n")
|
|
|
8154 (nntp-rlogin-parameters
|
|
|
8155 ("telnet" "the.real.nntp.host" "nntp")))
|
|
|
8156 @end lisp
|
|
|
8157
|
|
|
8158
|
|
0
|
8159
|
|
|
8160 @node Creating a Virtual Server
|
|
|
8161 @subsection Creating a Virtual Server
|
|
|
8162
|
|
|
8163 If you're saving lots of articles in the cache by using persistent
|
|
|
8164 articles, you may want to create a virtual server to read the cache.
|
|
|
8165
|
|
|
8166 First you need to add a new server. The @kbd{a} command does that. It
|
|
|
8167 would probably be best to use @code{nnspool} to read the cache. You
|
|
|
8168 could also use @code{nnml} or @code{nnmh}, though.
|
|
|
8169
|
|
|
8170 Type @kbd{a nnspool RET cache RET}.
|
|
|
8171
|
|
|
8172 You should now have a brand new @code{nnspool} virtual server called
|
|
|
8173 @samp{cache}. You now need to edit it to have the right definitions.
|
|
|
8174 Type @kbd{e} to edit the server. You'll be entered into a buffer that
|
|
|
8175 will contain the following:
|
|
|
8176
|
|
|
8177 @lisp
|
|
|
8178 (nnspool "cache")
|
|
|
8179 @end lisp
|
|
|
8180
|
|
|
8181 Change that to:
|
|
|
8182
|
|
|
8183 @lisp
|
|
|
8184 (nnspool "cache"
|
|
16
|
8185 (nnspool-spool-directory "~/News/cache/")
|
|
|
8186 (nnspool-nov-directory "~/News/cache/")
|
|
|
8187 (nnspool-active-file "~/News/cache/active"))
|
|
0
|
8188 @end lisp
|
|
|
8189
|
|
|
8190 Type @kbd{C-c C-c} to return to the server buffer. If you now press
|
|
|
8191 @kbd{RET} over this virtual server, you should be entered into a browse
|
|
|
8192 buffer, and you should be able to enter any of the groups displayed.
|
|
|
8193
|
|
|
8194
|
|
24
|
8195 @node Server Variables
|
|
|
8196 @subsection Server Variables
|
|
|
8197
|
|
|
8198 One sticky point when defining variables (both on backends and in Emacs
|
|
|
8199 in general) is that some variables are typically initialized from other
|
|
|
8200 variables when the definition of the variables is being loaded. If you
|
|
|
8201 change the "base" variable after the variables have been loaded, you
|
|
|
8202 won't change the "derived" variables.
|
|
|
8203
|
|
|
8204 This typically affects directory and file variables. For instance,
|
|
|
8205 @code{nnml-directory} is @file{~/Mail/} by default, and all @code{nnml}
|
|
|
8206 directory variables are initialized from that variable, so
|
|
|
8207 @code{nnml-active-file} will be @file{~/Mail/active}. If you define a
|
|
|
8208 new virtual @code{nnml} server, it will @emph{not} suffice to set just
|
|
|
8209 @code{nnml-directory}---you have to explicitly set all the file
|
|
|
8210 variables to be what you want them to be. For a complete list of
|
|
|
8211 variables for each backend, see each backend's section later in this
|
|
|
8212 manual, but here's an example @code{nnml} definition:
|
|
|
8213
|
|
|
8214 @lisp
|
|
|
8215 (nnml "public"
|
|
|
8216 (nnml-directory "~/my-mail/")
|
|
|
8217 (nnml-active-file "~/my-mail/active")
|
|
|
8218 (nnml-newsgroups-file "~/my-mail/newsgroups"))
|
|
|
8219 @end lisp
|
|
|
8220
|
|
|
8221
|
|
0
|
8222 @node Servers and Methods
|
|
|
8223 @subsection Servers and Methods
|
|
|
8224
|
|
|
8225 Wherever you would normally use a select method
|
|
16
|
8226 (e.g. @code{gnus-secondary-select-method}, in the group select method,
|
|
0
|
8227 when browsing a foreign server) you can use a virtual server name
|
|
|
8228 instead. This could potentially save lots of typing. And it's nice all
|
|
|
8229 over.
|
|
|
8230
|
|
|
8231
|
|
|
8232 @node Unavailable Servers
|
|
|
8233 @subsection Unavailable Servers
|
|
|
8234
|
|
|
8235 If a server seems to be unreachable, Gnus will mark that server as
|
|
|
8236 @code{denied}. That means that any subsequent attempt to make contact
|
|
|
8237 with that server will just be ignored. ``It can't be opened,'' Gnus
|
|
|
8238 will tell you, without making the least effort to see whether that is
|
|
|
8239 actually the case or not.
|
|
|
8240
|
|
|
8241 That might seem quite naughty, but it does make sense most of the time.
|
|
|
8242 Let's say you have 10 groups subscribed to the server
|
|
42
|
8243 @samp{nephelococcygia.com}. This server is located somewhere quite far
|
|
|
8244 away from you and the machine is quite slow, so it takes 1 minute just
|
|
|
8245 to find out that it refuses connection from you today. If Gnus were to
|
|
|
8246 attempt to do that 10 times, you'd be quite annoyed, so Gnus won't
|
|
|
8247 attempt to do that. Once it has gotten a single ``connection refused'',
|
|
|
8248 it will regard that server as ``down''.
|
|
0
|
8249
|
|
|
8250 So, what happens if the machine was only feeling unwell temporarily?
|
|
|
8251 How do you test to see whether the machine has come up again?
|
|
|
8252
|
|
|
8253 You jump to the server buffer (@pxref{The Server Buffer}) and poke it
|
|
|
8254 with the following commands:
|
|
|
8255
|
|
|
8256 @table @kbd
|
|
|
8257
|
|
|
8258 @item O
|
|
|
8259 @kindex O (Server)
|
|
|
8260 @findex gnus-server-open-server
|
|
|
8261 Try to establish connection to the server on the current line
|
|
|
8262 (@code{gnus-server-open-server}).
|
|
|
8263
|
|
|
8264 @item C
|
|
|
8265 @kindex C (Server)
|
|
|
8266 @findex gnus-server-close-server
|
|
|
8267 Close the connection (if any) to the server
|
|
|
8268 (@code{gnus-server-close-server}).
|
|
|
8269
|
|
|
8270 @item D
|
|
|
8271 @kindex D (Server)
|
|
|
8272 @findex gnus-server-deny-server
|
|
|
8273 Mark the current server as unreachable
|
|
|
8274 (@code{gnus-server-deny-server}).
|
|
|
8275
|
|
16
|
8276 @item M-o
|
|
|
8277 @kindex M-o (Server)
|
|
|
8278 @findex gnus-server-open-all-servers
|
|
|
8279 Open the connections to all servers in the buffer
|
|
|
8280 (@code{gnus-server-open-all-servers}).
|
|
|
8281
|
|
|
8282 @item M-c
|
|
|
8283 @kindex M-c (Server)
|
|
|
8284 @findex gnus-server-close-all-servers
|
|
|
8285 Close the connections to all servers in the buffer
|
|
|
8286 (@code{gnus-server-close-all-servers}).
|
|
|
8287
|
|
0
|
8288 @item R
|
|
|
8289 @kindex R (Server)
|
|
|
8290 @findex gnus-server-remove-denials
|
|
|
8291 Remove all marks to whether Gnus was denied connection from all servers
|
|
|
8292 (@code{gnus-server-remove-denials}).
|
|
|
8293
|
|
|
8294 @end table
|
|
|
8295
|
|
|
8296
|
|
|
8297 @node Getting News
|
|
|
8298 @section Getting News
|
|
|
8299 @cindex reading news
|
|
|
8300 @cindex news backends
|
|
|
8301
|
|
|
8302 A newsreader is normally used for reading news. Gnus currently provides
|
|
2
|
8303 only two methods of getting news---it can read from an @sc{nntp} server,
|
|
|
8304 or it can read from a local spool.
|
|
0
|
8305
|
|
|
8306 @menu
|
|
|
8307 * NNTP:: Reading news from an @sc{nntp} server.
|
|
|
8308 * News Spool:: Reading news from the local spool.
|
|
|
8309 @end menu
|
|
|
8310
|
|
|
8311
|
|
|
8312 @node NNTP
|
|
|
8313 @subsection @sc{nntp}
|
|
|
8314 @cindex nntp
|
|
|
8315
|
|
|
8316 Subscribing to a foreign group from an @sc{nntp} server is rather easy.
|
|
|
8317 You just specify @code{nntp} as method and the address of the @sc{nntp}
|
|
|
8318 server as the, uhm, address.
|
|
|
8319
|
|
|
8320 If the @sc{nntp} server is located at a non-standard port, setting the
|
|
|
8321 third element of the select method to this port number should allow you
|
|
|
8322 to connect to the right port. You'll have to edit the group info for
|
|
|
8323 that (@pxref{Foreign Groups}).
|
|
|
8324
|
|
|
8325 The name of the foreign group can be the same as a native group. In
|
|
|
8326 fact, you can subscribe to the same group from as many different servers
|
|
|
8327 you feel like. There will be no name collisions.
|
|
|
8328
|
|
|
8329 The following variables can be used to create a virtual @code{nntp}
|
|
|
8330 server:
|
|
|
8331
|
|
|
8332 @table @code
|
|
|
8333
|
|
|
8334 @item nntp-server-opened-hook
|
|
|
8335 @vindex nntp-server-opened-hook
|
|
|
8336 @cindex @sc{mode reader}
|
|
|
8337 @cindex authinfo
|
|
|
8338 @cindex authentification
|
|
|
8339 @cindex nntp authentification
|
|
|
8340 @findex nntp-send-authinfo
|
|
|
8341 @findex nntp-send-mode-reader
|
|
|
8342 @code{nntp-server-opened-hook} is run after a connection has been made.
|
|
|
8343 It can be used to send commands to the @sc{nntp} server after it has
|
|
|
8344 been contacted. By default is sends the command @code{MODE READER} to
|
|
16
|
8345 the server with the @code{nntp-send-mode-reader} function.
|
|
|
8346
|
|
|
8347 @item nntp-authinfo-function
|
|
|
8348 @vindex nntp-authinfo-function
|
|
|
8349 This function will be used to send @samp{AUTHINFO} to the @sc{nntp}
|
|
|
8350 server. Available functions include:
|
|
|
8351
|
|
|
8352 @table @code
|
|
|
8353 @item nntp-send-authinfo
|
|
|
8354 @findex nntp-send-authinfo
|
|
|
8355 This function will used you current login name as the user name and will
|
|
|
8356 prompt you for the password. This is the default.
|
|
|
8357
|
|
|
8358 @item nntp-send-nosy-authinfo
|
|
|
8359 @findex nntp-send-nosy-authinfo
|
|
|
8360 This function will prompt you for both user name and password.
|
|
|
8361
|
|
|
8362 @item nntp-send-authinfo-from-file
|
|
|
8363 @findex nntp-send-authinfo-from-file
|
|
|
8364 This function will use your current login name as the user name and will
|
|
|
8365 read the @sc{nntp} password from @file{~/.nntp-authinfo}.
|
|
|
8366 @end table
|
|
0
|
8367
|
|
|
8368 @item nntp-server-action-alist
|
|
|
8369 @vindex nntp-server-action-alist
|
|
|
8370 This is an list of regexps to match on server types and actions to be
|
|
|
8371 taken when matches are made. For instance, if you want Gnus to beep
|
|
|
8372 every time you connect to innd, you could say something like:
|
|
|
8373
|
|
|
8374 @lisp
|
|
|
8375 (setq nntp-server-action-alist
|
|
|
8376 '(("innd" (ding))))
|
|
|
8377 @end lisp
|
|
|
8378
|
|
|
8379 You probably don't want to do that, though.
|
|
|
8380
|
|
|
8381 The default value is
|
|
|
8382
|
|
|
8383 @lisp
|
|
|
8384 '(("nntpd 1\\.5\\.11t"
|
|
|
8385 (remove-hook 'nntp-server-opened-hook nntp-send-mode-reader)))
|
|
|
8386 @end lisp
|
|
|
8387
|
|
|
8388 This ensures that Gnus doesn't send the @code{MODE READER} command to
|
|
|
8389 nntpd 1.5.11t, since that command chokes that server, I've been told.
|
|
|
8390
|
|
|
8391 @item nntp-maximum-request
|
|
|
8392 @vindex nntp-maximum-request
|
|
|
8393 If the @sc{nntp} server doesn't support @sc{nov} headers, this backend
|
|
|
8394 will collect headers by sending a series of @code{head} commands. To
|
|
|
8395 speed things up, the backend sends lots of these commands without
|
|
|
8396 waiting for reply, and then reads all the replies. This is controlled
|
|
|
8397 by the @code{nntp-maximum-request} variable, and is 400 by default. If
|
|
|
8398 your network is buggy, you should set this to 1.
|
|
|
8399
|
|
|
8400 @item nntp-connection-timeout
|
|
|
8401 @vindex nntp-connection-timeout
|
|
|
8402 If you have lots of foreign @code{nntp} groups that you connect to
|
|
|
8403 regularly, you're sure to have problems with @sc{nntp} servers not
|
|
|
8404 responding properly, or being too loaded to reply within reasonable
|
|
|
8405 time. This is can lead to awkward problems, which can be helped
|
|
|
8406 somewhat by setting @code{nntp-connection-timeout}. This is an integer
|
|
|
8407 that says how many seconds the @code{nntp} backend should wait for a
|
|
|
8408 connection before giving up. If it is @code{nil}, which is the default,
|
|
|
8409 no timeouts are done.
|
|
|
8410
|
|
|
8411 @item nntp-command-timeout
|
|
|
8412 @vindex nntp-command-timeout
|
|
|
8413 @cindex PPP connections
|
|
|
8414 @cindex dynamic IP addresses
|
|
|
8415 If you're running Gnus on a machine that has a dynamically assigned
|
|
|
8416 address, Gnus may become confused. If the address of your machine
|
|
|
8417 changes after connecting to the @sc{nntp} server, Gnus will simply sit
|
|
|
8418 waiting forever for replies from the server. To help with this
|
|
|
8419 unfortunate problem, you can set this command to a number. Gnus will
|
|
|
8420 then, if it sits waiting longer than that number of seconds for a reply
|
|
|
8421 from the server, shut down the connection, start a new one, and resend
|
|
|
8422 the command. This should hopefully be transparent to the user. A
|
|
|
8423 likely number is 30 seconds.
|
|
|
8424
|
|
|
8425 @item nntp-retry-on-break
|
|
|
8426 @vindex nntp-retry-on-break
|
|
|
8427 If this variable is non-@code{nil}, you can also @kbd{C-g} if Gnus
|
|
|
8428 hangs. This will have much the same effect as the command timeout
|
|
|
8429 described above.
|
|
|
8430
|
|
|
8431 @item nntp-server-hook
|
|
|
8432 @vindex nntp-server-hook
|
|
|
8433 This hook is run as the last step when connecting to an @sc{nntp}
|
|
|
8434 server.
|
|
|
8435
|
|
|
8436 @findex nntp-open-rlogin
|
|
|
8437 @findex nntp-open-network-stream
|
|
16
|
8438 @item nntp-open-connection-function
|
|
|
8439 @vindex nntp-open-connection-function
|
|
0
|
8440 This function is used to connect to the remote system. Two pre-made
|
|
|
8441 functions are @code{nntp-open-network-stream}, which is the default, and
|
|
|
8442 simply connects to some port or other on the remote system. The other
|
|
|
8443 is @code{nntp-open-rlogin}, which does an rlogin on the remote system,
|
|
|
8444 and then does a telnet to the @sc{nntp} server available there.
|
|
|
8445
|
|
|
8446 @item nntp-rlogin-parameters
|
|
|
8447 @vindex nntp-rlogin-parameters
|
|
|
8448 If you use @code{nntp-open-rlogin} as the
|
|
16
|
8449 @code{nntp-open-connection-function}, this list will be used as the
|
|
0
|
8450 parameter list given to @code{rsh}.
|
|
|
8451
|
|
|
8452 @item nntp-end-of-line
|
|
|
8453 @vindex nntp-end-of-line
|
|
|
8454 String to use as end-of-line markers when talking to the @sc{nntp}
|
|
|
8455 server. This is @samp{\r\n} by default, but should be @samp{\n} when
|
|
|
8456 using @code{rlogin} to talk to the server.
|
|
|
8457
|
|
|
8458 @item nntp-rlogin-user-name
|
|
|
8459 @vindex nntp-rlogin-user-name
|
|
|
8460 User name on the remote system when using the @code{rlogin} connect
|
|
|
8461 function.
|
|
|
8462
|
|
|
8463 @item nntp-address
|
|
|
8464 @vindex nntp-address
|
|
|
8465 The address of the remote system running the @sc{nntp} server.
|
|
|
8466
|
|
|
8467 @item nntp-port-number
|
|
|
8468 @vindex nntp-port-number
|
|
|
8469 Port number to connect to when using the @code{nntp-open-network-stream}
|
|
|
8470 connect function.
|
|
|
8471
|
|
|
8472 @item nntp-buggy-select
|
|
|
8473 @vindex nntp-buggy-select
|
|
|
8474 Set this to non-@code{nil} if your select routine is buggy.
|
|
|
8475
|
|
|
8476 @item nntp-nov-is-evil
|
|
|
8477 @vindex nntp-nov-is-evil
|
|
|
8478 If the @sc{nntp} server does not support @sc{nov}, you could set this
|
|
|
8479 variable to @code{t}, but @code{nntp} usually checks whether @sc{nov}
|
|
|
8480 can be used automatically.
|
|
|
8481
|
|
|
8482 @item nntp-xover-commands
|
|
|
8483 @vindex nntp-xover-commands
|
|
|
8484 @cindex nov
|
|
|
8485 @cindex XOVER
|
|
|
8486 List of strings that are used as commands to fetch @sc{nov} lines from a
|
|
|
8487 server. The default value of this variable is @code{("XOVER"
|
|
|
8488 "XOVERVIEW")}.
|
|
|
8489
|
|
|
8490 @item nntp-nov-gap
|
|
|
8491 @vindex nntp-nov-gap
|
|
|
8492 @code{nntp} normally sends just one big request for @sc{nov} lines to
|
|
|
8493 the server. The server responds with one huge list of lines. However,
|
|
|
8494 if you have read articles 2-5000 in the group, and only want to read
|
|
|
8495 article 1 and 5001, that means that @code{nntp} will fetch 4999 @sc{nov}
|
|
|
8496 lines that you do not want, and will not use. This variable says how
|
|
|
8497 big a gap between two consecutive articles is allowed to be before the
|
|
|
8498 @code{XOVER} request is split into several request. Note that if your
|
|
|
8499 network is fast, setting this variable to a really small number means
|
|
|
8500 that fetching will probably be slower. If this variable is @code{nil},
|
|
|
8501 @code{nntp} will never split requests.
|
|
|
8502
|
|
|
8503 @item nntp-prepare-server-hook
|
|
|
8504 @vindex nntp-prepare-server-hook
|
|
|
8505 A hook run before attempting to connect to an @sc{nntp} server.
|
|
|
8506
|
|
|
8507 @item nntp-warn-about-losing-connection
|
|
|
8508 @vindex nntp-warn-about-losing-connection
|
|
|
8509 If this variable is non-@code{nil}, some noise will be made when a
|
|
|
8510 server closes connection.
|
|
|
8511
|
|
|
8512 @end table
|
|
|
8513
|
|
|
8514
|
|
|
8515 @node News Spool
|
|
|
8516 @subsection News Spool
|
|
|
8517 @cindex nnspool
|
|
|
8518 @cindex news spool
|
|
|
8519
|
|
|
8520 Subscribing to a foreign group from the local spool is extremely easy,
|
|
16
|
8521 and might be useful, for instance, to speed up reading groups that
|
|
|
8522 contain very big articles---@samp{alt.binaries.pictures.furniture}, for
|
|
|
8523 instance.
|
|
0
|
8524
|
|
|
8525 Anyways, you just specify @code{nnspool} as the method and @samp{} (or
|
|
|
8526 anything else) as the address.
|
|
|
8527
|
|
|
8528 If you have access to a local spool, you should probably use that as the
|
|
|
8529 native select method (@pxref{Finding the News}). It is normally faster
|
|
|
8530 than using an @code{nntp} select method, but might not be. It depends.
|
|
|
8531 You just have to try to find out what's best at your site.
|
|
|
8532
|
|
|
8533 @table @code
|
|
|
8534
|
|
|
8535 @item nnspool-inews-program
|
|
|
8536 @vindex nnspool-inews-program
|
|
|
8537 Program used to post an article.
|
|
|
8538
|
|
|
8539 @item nnspool-inews-switches
|
|
|
8540 @vindex nnspool-inews-switches
|
|
|
8541 Parameters given to the inews program when posting an article.
|
|
|
8542
|
|
|
8543 @item nnspool-spool-directory
|
|
|
8544 @vindex nnspool-spool-directory
|
|
|
8545 Where @code{nnspool} looks for the articles. This is normally
|
|
|
8546 @file{/usr/spool/news/}.
|
|
|
8547
|
|
|
8548 @item nnspool-nov-directory
|
|
|
8549 @vindex nnspool-nov-directory
|
|
|
8550 Where @code{nnspool} will look for @sc{nov} files. This is normally
|
|
|
8551 @file{/usr/spool/news/over.view/}.
|
|
|
8552
|
|
|
8553 @item nnspool-lib-dir
|
|
|
8554 @vindex nnspool-lib-dir
|
|
|
8555 Where the news lib dir is (@file{/usr/lib/news/} by default).
|
|
|
8556
|
|
|
8557 @item nnspool-active-file
|
|
|
8558 @vindex nnspool-active-file
|
|
|
8559 The path of the active file.
|
|
|
8560
|
|
|
8561 @item nnspool-newsgroups-file
|
|
|
8562 @vindex nnspool-newsgroups-file
|
|
|
8563 The path of the group descriptions file.
|
|
|
8564
|
|
|
8565 @item nnspool-history-file
|
|
|
8566 @vindex nnspool-history-file
|
|
|
8567 The path of the news history file.
|
|
|
8568
|
|
|
8569 @item nnspool-active-times-file
|
|
|
8570 @vindex nnspool-active-times-file
|
|
|
8571 The path of the active date file.
|
|
|
8572
|
|
|
8573 @item nnspool-nov-is-evil
|
|
|
8574 @vindex nnspool-nov-is-evil
|
|
|
8575 If non-@code{nil}, @code{nnspool} won't try to use any @sc{nov} files
|
|
|
8576 that it finds.
|
|
|
8577
|
|
|
8578 @item nnspool-sift-nov-with-sed
|
|
|
8579 @vindex nnspool-sift-nov-with-sed
|
|
|
8580 @cindex sed
|
|
|
8581 If non-@code{nil}, which is the default, use @code{sed} to get the
|
|
|
8582 relevant portion from the overview file. If nil, @code{nnspool} will
|
|
|
8583 load the entire file into a buffer and process it there.
|
|
|
8584
|
|
|
8585 @end table
|
|
|
8586
|
|
|
8587
|
|
|
8588 @node Getting Mail
|
|
|
8589 @section Getting Mail
|
|
|
8590 @cindex reading mail
|
|
|
8591 @cindex mail
|
|
|
8592
|
|
|
8593 Reading mail with a newsreader---isn't that just plain WeIrD? But of
|
|
|
8594 course.
|
|
|
8595
|
|
|
8596 @menu
|
|
|
8597 * Getting Started Reading Mail:: A simple cookbook example.
|
|
|
8598 * Splitting Mail:: How to create mail groups.
|
|
|
8599 * Mail Backend Variables:: Variables for customizing mail handling.
|
|
|
8600 * Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
|
|
|
8601 * Mail and Procmail:: Reading mail groups that procmail create.
|
|
|
8602 * Incorporating Old Mail:: What about the old mail you have?
|
|
|
8603 * Expiring Mail:: Getting rid of unwanted mail.
|
|
16
|
8604 * Washing Mail:: Removing gruft from the mail you get.
|
|
0
|
8605 * Duplicates:: Dealing with duplicated mail.
|
|
|
8606 * Not Reading Mail:: Using mail backends for reading other files.
|
|
|
8607 * Choosing a Mail Backend:: Gnus can read a variety of mail formats.
|
|
|
8608 @end menu
|
|
|
8609
|
|
|
8610
|
|
|
8611 @node Getting Started Reading Mail
|
|
|
8612 @subsection Getting Started Reading Mail
|
|
|
8613
|
|
|
8614 It's quite easy to use Gnus to read your new mail. You just plonk the
|
|
|
8615 mail backend of your choice into @code{gnus-secondary-select-methods},
|
|
|
8616 and things will happen automatically.
|
|
|
8617
|
|
|
8618 For instance, if you want to use @code{nnml} (which is a one file per
|
|
|
8619 mail backend), you could put the following in your @file{.gnus} file:
|
|
|
8620
|
|
|
8621 @lisp
|
|
|
8622 (setq gnus-secondary-select-methods
|
|
|
8623 '((nnml "private")))
|
|
|
8624 @end lisp
|
|
|
8625
|
|
|
8626 Now, the next time you start Gnus, this backend will be queried for new
|
|
|
8627 articles, and it will move all the messages in your spool file to its
|
|
|
8628 directory, which is @code{~/Mail/} by default. The new group that will
|
|
|
8629 be created (@samp{mail.misc}) will be subscribed, and you can read it
|
|
|
8630 like any other group.
|
|
|
8631
|
|
|
8632 You will probably want to split the mail into several groups, though:
|
|
|
8633
|
|
|
8634 @lisp
|
|
|
8635 (setq nnmail-split-methods
|
|
16
|
8636 '(("junk" "^From:.*Lars Ingebrigtsen")
|
|
|
8637 ("crazy" "^Subject:.*die\\|^Organization:.*flabby")
|
|
|
8638 ("other" "")))
|
|
|
8639 @end lisp
|
|
|
8640
|
|
|
8641 This will result in three new @code{nnml} mail groups being created:
|
|
0
|
8642 @samp{nnml:junk}, @samp{nnml:crazy}, and @samp{nnml:other}. All the
|
|
|
8643 mail that doesn't fit into the first two groups will be placed in the
|
|
|
8644 latter group.
|
|
|
8645
|
|
|
8646 This should be sufficient for reading mail with Gnus. You might want to
|
|
|
8647 give the other sections in this part of the manual a perusal, though,
|
|
|
8648 especially @pxref{Choosing a Mail Backend} and @pxref{Expiring Mail}.
|
|
|
8649
|
|
|
8650
|
|
|
8651 @node Splitting Mail
|
|
|
8652 @subsection Splitting Mail
|
|
|
8653 @cindex splitting mail
|
|
|
8654 @cindex mail splitting
|
|
|
8655
|
|
|
8656 @vindex nnmail-split-methods
|
|
|
8657 The @code{nnmail-split-methods} variable says how the incoming mail is
|
|
|
8658 to be split into groups.
|
|
|
8659
|
|
|
8660 @lisp
|
|
|
8661 (setq nnmail-split-methods
|
|
|
8662 '(("mail.junk" "^From:.*Lars Ingebrigtsen")
|
|
|
8663 ("mail.crazy" "^Subject:.*die\\|^Organization:.*flabby")
|
|
|
8664 ("mail.other" "")))
|
|
|
8665 @end lisp
|
|
|
8666
|
|
|
8667 This variable is a list of lists, where the first element of each of
|
|
|
8668 these lists is the name of the mail group (they do not have to be called
|
|
|
8669 something beginning with @samp{mail}, by the way), and the second
|
|
|
8670 element is a regular expression used on the header of each mail to
|
|
|
8671 determine if it belongs in this mail group.
|
|
|
8672
|
|
16
|
8673 If the first element is the special symbol @code{junk}, then messages
|
|
|
8674 that match the regexp will disappear into the aether. Use with
|
|
|
8675 extreme caution.
|
|
|
8676
|
|
0
|
8677 The second element can also be a function. In that case, it will be
|
|
|
8678 called narrowed to the headers with the first element of the rule as the
|
|
|
8679 argument. It should return a non-@code{nil} value if it thinks that the
|
|
|
8680 mail belongs in that group.
|
|
|
8681
|
|
|
8682 The last of these groups should always be a general one, and the regular
|
|
18
|
8683 expression should @emph{always} be @samp{} so that it matches any mails
|
|
|
8684 that haven't been matched by any of the other regexps. (These rules are
|
|
|
8685 processed from the beginning of the alist toward the end. The first
|
|
|
8686 rule to make a match will "win", unless you have crossposting enabled.
|
|
|
8687 In that case, all matching rules will "win".)
|
|
0
|
8688
|
|
|
8689 If you like to tinker with this yourself, you can set this variable to a
|
|
|
8690 function of your choice. This function will be called without any
|
|
|
8691 arguments in a buffer narrowed to the headers of an incoming mail
|
|
|
8692 message. The function should return a list of groups names that it
|
|
|
8693 thinks should carry this mail message.
|
|
|
8694
|
|
|
8695 Note that the mail backends are free to maul the poor, innocent
|
|
|
8696 incoming headers all they want to. They all add @code{Lines} headers;
|
|
|
8697 some add @code{X-Gnus-Group} headers; most rename the Unix mbox
|
|
|
8698 @code{From<SPACE>} line to something else.
|
|
|
8699
|
|
|
8700 @vindex nnmail-crosspost
|
|
|
8701 The mail backends all support cross-posting. If several regexps match,
|
|
|
8702 the mail will be ``cross-posted'' to all those groups.
|
|
|
8703 @code{nnmail-crosspost} says whether to use this mechanism or not. Note
|
|
|
8704 that no articles are crossposted to the general (@samp{}) group.
|
|
|
8705
|
|
|
8706 @vindex nnmail-crosspost-link-function
|
|
|
8707 @cindex crosspost
|
|
|
8708 @cindex links
|
|
|
8709 @code{nnmh} and @code{nnml} makes crossposts by creating hard links to
|
|
|
8710 the crossposted articles. However, not all files systems support hard
|
|
|
8711 links. If that's the case for you, set
|
|
|
8712 @code{nnmail-crosspost-link-function} to @code{copy-file}. (This
|
|
|
8713 variable is @code{add-name-to-file} by default.)
|
|
|
8714
|
|
16
|
8715 @kindex M-x nnmail-split-history
|
|
|
8716 @kindex nnmail-split-history
|
|
|
8717 If you wish to see where the previous mail split put the messages, you
|
|
|
8718 can use the @kbd{M-x nnmail-split-history} command.
|
|
|
8719
|
|
0
|
8720 Gnus gives you all the opportunity you could possibly want for shooting
|
|
|
8721 yourself in the foot. Let's say you create a group that will contain
|
|
|
8722 all the mail you get from your boss. And then you accidentally
|
|
|
8723 unsubscribe from the group. Gnus will still put all the mail from your
|
|
|
8724 boss in the unsubscribed group, and so, when your boss mails you ``Have
|
|
|
8725 that report ready by Monday or you're fired!'', you'll never see it and,
|
|
|
8726 come Tuesday, you'll still believe that you're gainfully employed while
|
|
|
8727 you really should be out collecting empty bottles to save up for next
|
|
|
8728 month's rent money.
|
|
|
8729
|
|
|
8730
|
|
|
8731 @node Mail Backend Variables
|
|
|
8732 @subsection Mail Backend Variables
|
|
|
8733
|
|
|
8734 These variables are (for the most part) pertinent to all the various
|
|
|
8735 mail backends.
|
|
|
8736
|
|
|
8737 @table @code
|
|
|
8738 @vindex nnmail-read-incoming-hook
|
|
|
8739 @item nnmail-read-incoming-hook
|
|
|
8740 The mail backends all call this hook after reading new mail. You can
|
|
|
8741 use this hook to notify any mail watch programs, if you want to.
|
|
|
8742
|
|
|
8743 @vindex nnmail-spool-file
|
|
|
8744 @item nnmail-spool-file
|
|
|
8745 @cindex POP mail
|
|
|
8746 @cindex MAILHOST
|
|
|
8747 @cindex movemail
|
|
|
8748 @vindex nnmail-pop-password
|
|
|
8749 @vindex nnmail-pop-password-required
|
|
|
8750 The backends will look for new mail in this file. If this variable is
|
|
|
8751 @code{nil}, the mail backends will never attempt to fetch mail by
|
|
|
8752 themselves. If you are using a POP mail server and your name is
|
|
|
8753 @samp{larsi}, you should set this variable to @samp{po:larsi}. If
|
|
|
8754 your name is not @samp{larsi}, you should probably modify that
|
|
|
8755 slightly, but you may have guessed that already, you smart & handsome
|
|
|
8756 devil! You can also set this variable to @code{pop}, and Gnus will try
|
|
|
8757 to figure out the POP mail string by itself. In any case, Gnus will
|
|
|
8758 call @code{movemail} which will contact the POP server named in the
|
|
|
8759 @code{MAILHOST} environment variable. If the POP server needs a
|
|
|
8760 password, you can either set @code{nnmail-pop-password-required} to
|
|
|
8761 @code{t} and be prompted for the password, or set
|
|
|
8762 @code{nnmail-pop-password} to the password itself.
|
|
|
8763
|
|
22
|
8764 @code{nnmail-spool-file} can also be a list of mailboxes.
|
|
|
8765
|
|
16
|
8766 Your Emacs has to have been configured with @samp{--with-pop} before
|
|
|
8767 compilation. This is the default, but some installations have it
|
|
|
8768 switched off.
|
|
|
8769
|
|
0
|
8770 When you use a mail backend, Gnus will slurp all your mail from your
|
|
|
8771 inbox and plonk it down in your home directory. Gnus doesn't move any
|
|
|
8772 mail if you're not using a mail backend---you have to do a lot of magic
|
|
|
8773 invocations first. At the time when you have finished drawing the
|
|
|
8774 pentagram, lightened the candles, and sacrificed the goat, you really
|
|
|
8775 shouldn't be too surprised when Gnus moves your mail.
|
|
|
8776
|
|
|
8777 @vindex nnmail-use-procmail
|
|
|
8778 @vindex nnmail-procmail-suffix
|
|
|
8779 @item nnmail-use-procmail
|
|
|
8780 If non-@code{nil}, the mail backends will look in
|
|
|
8781 @code{nnmail-procmail-directory} for incoming mail. All the files in
|
|
|
8782 that directory that have names ending in @code{nnmail-procmail-suffix}
|
|
|
8783 will be considered incoming mailboxes, and will be searched for new
|
|
|
8784 mail.
|
|
|
8785
|
|
|
8786 @vindex nnmail-crash-box
|
|
|
8787 @item nnmail-crash-box
|
|
|
8788 When the mail backends read a spool file, it is first moved to this
|
|
|
8789 file, which is @file{~/.gnus-crash-box} by default. If this file
|
|
|
8790 already exists, it will always be read (and incorporated) before any
|
|
|
8791 other spool files.
|
|
|
8792
|
|
|
8793 @vindex nnmail-prepare-incoming-hook
|
|
|
8794 @item nnmail-prepare-incoming-hook
|
|
|
8795 This is run in a buffer that holds all the new incoming mail, and can be
|
|
|
8796 used for, well, anything, really.
|
|
|
8797
|
|
16
|
8798 @vindex nnmail-split-hook
|
|
|
8799 @item nnmail-split-hook
|
|
|
8800 @findex article-decode-rfc1522
|
|
|
8801 @findex RFC1522 decoding
|
|
|
8802 Hook run in the buffer where the mail headers of each message is kept
|
|
|
8803 just before the splitting based on these headers is done. The hook is
|
|
|
8804 free to modify the buffer contents in any way it sees fit---the buffer
|
|
|
8805 is discarded after the splitting has been done, and no changes performed
|
|
|
8806 in the buffer will show up in any files. @code{gnus-article-decode-rfc1522}
|
|
|
8807 is one likely function to add to this hook.
|
|
|
8808
|
|
0
|
8809 @vindex nnmail-pre-get-new-mail-hook
|
|
|
8810 @vindex nnmail-post-get-new-mail-hook
|
|
|
8811 @item nnmail-pre-get-new-mail-hook
|
|
|
8812 @itemx nnmail-post-get-new-mail-hook
|
|
|
8813 These are two useful hooks executed when treating new incoming
|
|
|
8814 mail---@code{nnmail-pre-get-new-mail-hook} (is called just before
|
|
|
8815 starting to handle the new mail) and
|
|
|
8816 @code{nnmail-post-get-new-mail-hook} (is called when the mail handling
|
|
|
8817 is done). Here's and example of using these two hooks to change the
|
|
|
8818 default file modes the new mail files get:
|
|
|
8819
|
|
|
8820 @lisp
|
|
|
8821 (add-hook 'gnus-pre-get-new-mail-hook
|
|
|
8822 (lambda () (set-default-file-modes 511)))
|
|
|
8823
|
|
|
8824 (add-hook 'gnus-post-get-new-mail-hook
|
|
|
8825 (lambda () (set-default-file-modes 551)))
|
|
|
8826 @end lisp
|
|
|
8827
|
|
|
8828 @item nnmail-tmp-directory
|
|
|
8829 @vindex nnmail-tmp-directory
|
|
|
8830 This variable says where to move the incoming mail to while processing
|
|
|
8831 it. This is usually done in the same directory that the mail backend
|
|
|
8832 inhabits (i.e., @file{~/Mail/}), but if this variable is non-@code{nil},
|
|
|
8833 it will be used instead.
|
|
|
8834
|
|
|
8835 @item nnmail-movemail-program
|
|
|
8836 @vindex nnmail-movemail-program
|
|
|
8837 This program is executed to move mail from the user's inbox to her home
|
|
|
8838 directory. The default is @samp{movemail}.
|
|
|
8839
|
|
16
|
8840 This can also be a function. In that case, the function will be called
|
|
|
8841 with two parameters -- the name of the inbox, and the file to be moved
|
|
|
8842 to.
|
|
|
8843
|
|
0
|
8844 @item nnmail-delete-incoming
|
|
|
8845 @vindex nnmail-delete-incoming
|
|
|
8846 @cindex incoming mail files
|
|
|
8847 @cindex deleting incoming files
|
|
|
8848 If non-@code{nil}, the mail backends will delete the temporary incoming
|
|
24
|
8849 file after splitting mail into the proper groups. This is @code{t} by
|
|
|
8850 default.
|
|
|
8851
|
|
|
8852 @c This is @code{nil} by
|
|
|
8853 @c default for reasons of security.
|
|
0
|
8854
|
|
16
|
8855 @c Since Red Gnus is an alpha release, it is to be expected to lose mail.
|
|
|
8856 (No Gnus release since (ding) Gnus 0.10 (or something like that) have
|
|
|
8857 lost mail, I think, but that's not the point. (Except certain versions
|
|
|
8858 of Red Gnus.)) By not deleting the Incoming* files, one can be sure to
|
|
|
8859 not lose mail -- if Gnus totally whacks out, one can always recover what
|
|
|
8860 was lost.
|
|
|
8861
|
|
|
8862 Delete the @file{Incoming*} files at will.
|
|
|
8863
|
|
0
|
8864 @item nnmail-use-long-file-names
|
|
|
8865 @vindex nnmail-use-long-file-names
|
|
|
8866 If non-@code{nil}, the mail backends will use long file and directory
|
|
|
8867 names. Groups like @samp{mail.misc} will end up in directories like
|
|
|
8868 @file{mail.misc/}. If it is @code{nil}, the same group will end up in
|
|
|
8869 @file{mail/misc/}.
|
|
|
8870
|
|
|
8871 @item nnmail-delete-file-function
|
|
|
8872 @vindex nnmail-delete-file-function
|
|
|
8873 @findex delete-file
|
|
|
8874 Function called to delete files. It is @code{delete-file} by default.
|
|
|
8875
|
|
38
|
8876 @item nnmail-cache-accepted-message-ids
|
|
|
8877 @vindex nnmail-cache-accepted-message-ids
|
|
|
8878 If non-@code{nil}, put the @code{Message-ID}s of articles imported into
|
|
|
8879 the backend (via @code{Gcc}, for instance) into the mail duplication
|
|
|
8880 discovery cache. The default is @code{nil}.
|
|
|
8881
|
|
0
|
8882 @end table
|
|
|
8883
|
|
|
8884
|
|
|
8885 @node Fancy Mail Splitting
|
|
|
8886 @subsection Fancy Mail Splitting
|
|
|
8887 @cindex mail splitting
|
|
|
8888 @cindex fancy mail splitting
|
|
|
8889
|
|
|
8890 @vindex nnmail-split-fancy
|
|
|
8891 @findex nnmail-split-fancy
|
|
|
8892 If the rather simple, standard method for specifying how to split mail
|
|
|
8893 doesn't allow you to do what you want, you can set
|
|
|
8894 @code{nnmail-split-methods} to @code{nnmail-split-fancy}. Then you can
|
|
16
|
8895 play with the @code{nnmail-split-fancy} variable.
|
|
0
|
8896
|
|
|
8897 Let's look at an example value of this variable first:
|
|
|
8898
|
|
|
8899 @lisp
|
|
|
8900 ;; Messages from the mailer daemon are not crossposted to any of
|
|
|
8901 ;; the ordinary groups. Warnings are put in a separate group
|
|
|
8902 ;; from real errors.
|
|
|
8903 (| ("from" mail (| ("subject" "warn.*" "mail.warning")
|
|
|
8904 "mail.misc"))
|
|
|
8905 ;; Non-error messages are crossposted to all relevant
|
|
|
8906 ;; groups, but we don't crosspost between the group for the
|
|
|
8907 ;; (ding) list and the group for other (ding) related mail.
|
|
|
8908 (& (| (any "ding@@ifi\\.uio\\.no" "ding.list")
|
|
|
8909 ("subject" "ding" "ding.misc"))
|
|
|
8910 ;; Other mailing lists...
|
|
|
8911 (any "procmail@@informatik\\.rwth-aachen\\.de" "procmail.list")
|
|
|
8912 (any "SmartList@@informatik\\.rwth-aachen\\.de" "SmartList.list")
|
|
|
8913 ;; People...
|
|
42
|
8914 (any "larsi@@ifi\\.uio\\.no" "people.Lars_Magne_Ingebrigtsen"))
|
|
0
|
8915 ;; Unmatched mail goes to the catch all group.
|
|
16
|
8916 "misc.misc")
|
|
0
|
8917 @end lisp
|
|
|
8918
|
|
|
8919 This variable has the format of a @dfn{split}. A split is a (possibly)
|
|
|
8920 recursive structure where each split may contain other splits. Here are
|
|
16
|
8921 the five possible split syntaxes:
|
|
|
8922
|
|
|
8923 @enumerate
|
|
|
8924
|
|
|
8925 @item
|
|
|
8926 @samp{group}: If the split is a string, that will be taken as a group name.
|
|
|
8927
|
|
|
8928 @item
|
|
|
8929 @var{(FIELD VALUE SPLIT)}: If the split is a list, and the first
|
|
|
8930 element is a string, then that means that if header FIELD (a regexp)
|
|
|
8931 contains VALUE (also a regexp), then store the message as specified by
|
|
|
8932 SPLIT.
|
|
|
8933
|
|
|
8934 @item
|
|
|
8935 @var{(| SPLIT...)}: If the split is a list, and the first element is
|
|
|
8936 @code{|} (vertical bar), then process each SPLIT until one of them
|
|
|
8937 matches. A SPLIT is said to match if it will cause the mail message to
|
|
|
8938 be stored in one or more groups.
|
|
|
8939
|
|
|
8940 @item
|
|
|
8941 @var{(& SPLIT...)}: If the split is a list, and the first element is
|
|
|
8942 @code{&}, then process all SPLITs in the list.
|
|
|
8943
|
|
|
8944 @item
|
|
|
8945 @code{junk}: If the split is the symbol @code{junk}, then don't save
|
|
|
8946 this message anywhere.
|
|
|
8947
|
|
|
8948 @item
|
|
|
8949 @var{(: function arg1 arg2 ...)}: If the split is a list, and the first
|
|
|
8950 element is @code{:}, then the second element will be called as a
|
|
|
8951 function with @var{args} given as arguments. The function should return
|
|
|
8952 a SPLIT.
|
|
|
8953
|
|
|
8954 @end enumerate
|
|
|
8955
|
|
|
8956 In these splits, @var{FIELD} must match a complete field name.
|
|
|
8957 @var{VALUE} must match a complete word according to the fundamental mode
|
|
|
8958 syntax table. You can use @code{.*} in the regexps to match partial
|
|
|
8959 field names or words. In other words, all @var{VALUE}'s are wrapped in
|
|
|
8960 @samp{\<} and @samp{\>} pairs.
|
|
0
|
8961
|
|
|
8962 @vindex nnmail-split-abbrev-alist
|
|
16
|
8963 @var{FIELD} and @var{VALUE} can also be lisp symbols, in that case they
|
|
|
8964 are expanded as specified by the variable
|
|
|
8965 @code{nnmail-split-abbrev-alist}. This is an alist of cons cells, where
|
|
|
8966 the car of the cells contains the key, and the cdr contains a string.
|
|
0
|
8967
|
|
|
8968 @vindex nnmail-split-fancy-syntax-table
|
|
|
8969 @code{nnmail-split-fancy-syntax-table} is the syntax table in effect
|
|
|
8970 when all this splitting is performed.
|
|
|
8971
|
|
16
|
8972 If you want to have Gnus create groups dynamically based on some
|
|
|
8973 information in the headers, you can say things like:
|
|
|
8974
|
|
|
8975 @example
|
|
|
8976 (any "debian-\(\\w*\\)@@lists.debian.org" "mail.debian.\\1")
|
|
|
8977 @end example
|
|
|
8978
|
|
|
8979 That is, do @code{replace-match}-like substitions in the group names.
|
|
|
8980
|
|
0
|
8981
|
|
|
8982 @node Mail and Procmail
|
|
|
8983 @subsection Mail and Procmail
|
|
|
8984 @cindex procmail
|
|
|
8985
|
|
|
8986 @cindex slocal
|
|
|
8987 @cindex elm
|
|
|
8988 Many people use @code{procmail} (or some other mail filter program or
|
|
|
8989 external delivery agent---@code{slocal}, @code{elm}, etc) to split
|
|
|
8990 incoming mail into groups. If you do that, you should set
|
|
|
8991 @code{nnmail-spool-file} to @code{procmail} to ensure that the mail
|
|
|
8992 backends never ever try to fetch mail by themselves.
|
|
|
8993
|
|
|
8994 This also means that you probably don't want to set
|
|
|
8995 @code{nnmail-split-methods} either, which has some, perhaps, unexpected
|
|
|
8996 side effects.
|
|
|
8997
|
|
|
8998 When a mail backend is queried for what groups it carries, it replies
|
|
|
8999 with the contents of that variable, along with any groups it has figured
|
|
|
9000 out that it carries by other means. None of the backends (except
|
|
|
9001 @code{nnmh}) actually go out to the disk and check what groups actually
|
|
|
9002 exist. (It's not trivial to distinguish between what the user thinks is
|
|
|
9003 a basis for a newsgroup and what is just a plain old file or directory.)
|
|
|
9004
|
|
|
9005 This means that you have to tell Gnus (and the backends) what groups
|
|
|
9006 exist by hand.
|
|
|
9007
|
|
|
9008 Let's take the @code{nnmh} backend as an example.
|
|
|
9009
|
|
|
9010 The folders are located in @code{nnmh-directory}, say, @file{~/Mail/}.
|
|
|
9011 There are three folders, @file{foo}, @file{bar} and @file{mail.baz}.
|
|
|
9012
|
|
|
9013 Go to the group buffer and type @kbd{G m}. When prompted, answer
|
|
|
9014 @samp{foo} for the name and @samp{nnmh} for the method. Repeat
|
|
|
9015 twice for the two other groups, @samp{bar} and @samp{mail.baz}. Be sure
|
|
|
9016 to include all your mail groups.
|
|
|
9017
|
|
|
9018 That's it. You are now set to read your mail. An active file for this
|
|
|
9019 method will be created automatically.
|
|
|
9020
|
|
|
9021 @vindex nnmail-procmail-suffix
|
|
|
9022 @vindex nnmail-procmail-directory
|
|
|
9023 If you use @code{nnfolder} or any other backend that store more than a
|
|
|
9024 single article in each file, you should never have procmail add mails to
|
|
|
9025 the file that Gnus sees. Instead, procmail should put all incoming mail
|
|
|
9026 in @code{nnmail-procmail-directory}. To arrive at the file name to put
|
|
|
9027 the incoming mail in, append @code{nnmail-procmail-suffix} to the group
|
|
|
9028 name. The mail backends will read the mail from these files.
|
|
|
9029
|
|
|
9030 @vindex nnmail-resplit-incoming
|
|
|
9031 When Gnus reads a file called @file{mail.misc.spool}, this mail will be
|
|
|
9032 put in the @code{mail.misc}, as one would expect. However, if you want
|
|
|
9033 Gnus to split the mail the normal way, you could set
|
|
|
9034 @code{nnmail-resplit-incoming} to @code{t}.
|
|
|
9035
|
|
|
9036 @vindex nnmail-keep-last-article
|
|
|
9037 If you use @code{procmail} to split things directory into an @code{nnmh}
|
|
|
9038 directory (which you shouldn't do), you should set
|
|
|
9039 @code{nnmail-keep-last-article} to non-@code{nil} to prevent Gnus from
|
|
30
|
9040 ever expiring the final article (i. e., the article with the highest
|
|
|
9041 article number) in a mail newsgroup. This is quite, quite important.
|
|
0
|
9042
|
|
16
|
9043 Here's an example setup: The incoming spools are located in
|
|
|
9044 @file{~/incoming/} and have @samp{""} as suffixes (i. e., the incoming
|
|
|
9045 spool files have the same names as the equivalent groups). The
|
|
|
9046 @code{nnfolder} backend is to be used as the mail interface, and the
|
|
|
9047 @code{nnfolder} directory is @file{~/fMail/}.
|
|
|
9048
|
|
|
9049 @lisp
|
|
|
9050 (setq nnfolder-directory "~/fMail/")
|
|
|
9051 (setq nnmail-spool-file 'procmail)
|
|
|
9052 (setq nnmail-procmail-directory "~/incoming/")
|
|
|
9053 (setq gnus-secondary-select-methods '((nnfolder "")))
|
|
|
9054 (setq nnmail-procmail-suffix "")
|
|
|
9055 @end lisp
|
|
|
9056
|
|
0
|
9057
|
|
|
9058 @node Incorporating Old Mail
|
|
|
9059 @subsection Incorporating Old Mail
|
|
|
9060
|
|
|
9061 Most people have lots of old mail stored in various file formats. If
|
|
|
9062 you have set up Gnus to read mail using one of the spiffy Gnus mail
|
|
|
9063 backends, you'll probably wish to have that old mail incorporated into
|
|
|
9064 your mail groups.
|
|
|
9065
|
|
|
9066 Doing so can be quite easy.
|
|
|
9067
|
|
|
9068 To take an example: You're reading mail using @code{nnml}
|
|
|
9069 (@pxref{Mail Spool}), and have set @code{nnmail-split-methods} to a
|
|
|
9070 satisfactory value (@pxref{Splitting Mail}). You have an old Unix mbox
|
|
|
9071 file filled with important, but old, mail. You want to move it into
|
|
|
9072 your @code{nnml} groups.
|
|
|
9073
|
|
|
9074 Here's how:
|
|
|
9075
|
|
|
9076 @enumerate
|
|
|
9077 @item
|
|
|
9078 Go to the group buffer.
|
|
|
9079
|
|
|
9080 @item
|
|
|
9081 Type `G f' and give the path of the mbox file when prompted to create an
|
|
|
9082 @code{nndoc} group from the mbox file (@pxref{Foreign Groups}).
|
|
|
9083
|
|
|
9084 @item
|
|
|
9085 Type `SPACE' to enter the newly created group.
|
|
|
9086
|
|
|
9087 @item
|
|
|
9088 Type `M P b' to process-mark all articles in this group (@pxref{Setting
|
|
|
9089 Process Marks}).
|
|
|
9090
|
|
|
9091 @item
|
|
|
9092 Type `B r' to respool all the process-marked articles, and answer
|
|
|
9093 @samp{nnml} when prompted (@pxref{Mail Group Commands}).
|
|
|
9094 @end enumerate
|
|
|
9095
|
|
|
9096 All the mail messages in the mbox file will now also be spread out over
|
|
|
9097 all your @code{nnml} groups. Try entering them and check whether things
|
|
|
9098 have gone without a glitch. If things look ok, you may consider
|
|
|
9099 deleting the mbox file, but I wouldn't do that unless I was absolutely
|
|
|
9100 sure that all the mail has ended up where it should be.
|
|
|
9101
|
|
|
9102 Respooling is also a handy thing to do if you're switching from one mail
|
|
|
9103 backend to another. Just respool all the mail in the old mail groups
|
|
|
9104 using the new mail backend.
|
|
|
9105
|
|
|
9106
|
|
|
9107 @node Expiring Mail
|
|
|
9108 @subsection Expiring Mail
|
|
|
9109 @cindex article expiry
|
|
|
9110
|
|
|
9111 Traditional mail readers have a tendency to remove mail articles when
|
|
|
9112 you mark them as read, in some way. Gnus takes a fundamentally
|
|
|
9113 different approach to mail reading.
|
|
|
9114
|
|
|
9115 Gnus basically considers mail just to be news that has been received in
|
|
|
9116 a rather peculiar manner. It does not think that it has the power to
|
|
|
9117 actually change the mail, or delete any mail messages. If you enter a
|
|
|
9118 mail group, and mark articles as ``read'', or kill them in some other
|
|
|
9119 fashion, the mail articles will still exist on the system. I repeat:
|
|
|
9120 Gnus will not delete your old, read mail. Unless you ask it to, of
|
|
|
9121 course.
|
|
|
9122
|
|
|
9123 To make Gnus get rid of your unwanted mail, you have to mark the
|
|
|
9124 articles as @dfn{expirable}. This does not mean that the articles will
|
|
|
9125 disappear right away, however. In general, a mail article will be
|
|
|
9126 deleted from your system if, 1) it is marked as expirable, AND 2) it is
|
|
|
9127 more than one week old. If you do not mark an article as expirable, it
|
|
|
9128 will remain on your system until hell freezes over. This bears
|
|
|
9129 repeating one more time, with some spurious capitalizations: IF you do
|
|
|
9130 NOT mark articles as EXPIRABLE, Gnus will NEVER delete those ARTICLES.
|
|
|
9131
|
|
|
9132 @vindex gnus-auto-expirable-newsgroups
|
|
|
9133 You do not have to mark articles as expirable by hand. Groups that
|
|
|
9134 match the regular expression @code{gnus-auto-expirable-newsgroups} will
|
|
|
9135 have all articles that you read marked as expirable automatically. All
|
|
|
9136 articles that are marked as expirable have an @samp{E} in the first
|
|
|
9137 column in the summary buffer.
|
|
|
9138
|
|
16
|
9139 Note that making a group auto-expirable don't mean that all read
|
|
|
9140 articles are expired---only the articles that are marked as expirable
|
|
|
9141 will be expired. Also note the using the @kbd{d} command won't make
|
|
|
9142 groups expirable---only semi-automatic marking of articles as read will
|
|
|
9143 mark the articles as expirable in auto-expirable groups.
|
|
|
9144
|
|
0
|
9145 Let's say you subscribe to a couple of mailing lists, and you want the
|
|
|
9146 articles you have read to disappear after a while:
|
|
|
9147
|
|
|
9148 @lisp
|
|
|
9149 (setq gnus-auto-expirable-newsgroups
|
|
|
9150 "mail.nonsense-list\\|mail.nice-list")
|
|
|
9151 @end lisp
|
|
|
9152
|
|
|
9153 Another way to have auto-expiry happen is to have the element
|
|
|
9154 @code{auto-expire} in the group parameters of the group.
|
|
|
9155
|
|
16
|
9156 If you use adaptive scoring (@pxref{Adaptive Scoring}) and
|
|
|
9157 auto-expiring, you'll have problems. Auto-expiring and adaptive scoring
|
|
|
9158 doesn't really mix very well.
|
|
|
9159
|
|
0
|
9160 @vindex nnmail-expiry-wait
|
|
|
9161 The @code{nnmail-expiry-wait} variable supplies the default time an
|
|
34
|
9162 expirable article has to live. Gnus starts counting days from when the
|
|
|
9163 message @emph{arrived}, not from when it was sent. The default is seven
|
|
|
9164 days.
|
|
0
|
9165
|
|
|
9166 Gnus also supplies a function that lets you fine-tune how long articles
|
|
|
9167 are to live, based on what group they are in. Let's say you want to
|
|
|
9168 have one month expiry period in the @samp{mail.private} group, a one day
|
|
|
9169 expiry period in the @samp{mail.junk} group, and a six day expiry period
|
|
|
9170 everywhere else:
|
|
|
9171
|
|
|
9172 @vindex nnmail-expiry-wait-function
|
|
|
9173 @lisp
|
|
|
9174 (setq nnmail-expiry-wait-function
|
|
|
9175 (lambda (group)
|
|
|
9176 (cond ((string= group "mail.private")
|
|
|
9177 31)
|
|
|
9178 ((string= group "mail.junk")
|
|
|
9179 1)
|
|
|
9180 ((string= group "important")
|
|
|
9181 'never)
|
|
|
9182 (t
|
|
|
9183 6))))
|
|
|
9184 @end lisp
|
|
|
9185
|
|
|
9186 The group names that this function is fed are ``unadorned'' group
|
|
|
9187 names---no @samp{nnml:} prefixes and the like.
|
|
|
9188
|
|
|
9189 The @code{nnmail-expiry-wait} variable and
|
|
|
9190 @code{nnmail-expiry-wait-function} function can be either a number (not
|
|
|
9191 necessarily an integer) or the symbols @code{immediate} or
|
|
|
9192 @code{never}.
|
|
|
9193
|
|
|
9194 You can also use the @code{expiry-wait} group parameter to selectively
|
|
|
9195 change the expiry period (@pxref{Group Parameters}).
|
|
|
9196
|
|
|
9197 @vindex nnmail-keep-last-article
|
|
|
9198 If @code{nnmail-keep-last-article} is non-@code{nil}, Gnus will never
|
|
|
9199 expire the final article in a mail newsgroup. This is to make life
|
|
|
9200 easier for procmail users.
|
|
|
9201
|
|
|
9202 @vindex gnus-total-expirable-newsgroups
|
|
|
9203 By the way, that line up there about Gnus never expiring non-expirable
|
|
|
9204 articles is a lie. If you put @code{total-expire} in the group
|
|
|
9205 parameters, articles will not be marked as expirable, but all read
|
|
|
9206 articles will be put through the expiry process. Use with extreme
|
|
|
9207 caution. Even more dangerous is the
|
|
|
9208 @code{gnus-total-expirable-newsgroups} variable. All groups that match
|
|
|
9209 this regexp will have all read articles put through the expiry process,
|
|
|
9210 which means that @emph{all} old mail articles in the groups in question
|
|
|
9211 will be deleted after a while. Use with extreme caution, and don't come
|
|
|
9212 crying to me when you discover that the regexp you used matched the
|
|
|
9213 wrong group and all your important mail has disappeared. Be a
|
|
|
9214 @emph{man}! Or a @emph{woman}! Whatever you feel more comfortable
|
|
|
9215 with! So there!
|
|
|
9216
|
|
16
|
9217 Most people make most of their mail groups total-expirable, though.
|
|
|
9218
|
|
|
9219
|
|
|
9220 @node Washing Mail
|
|
|
9221 @subsection Washing Mail
|
|
|
9222 @cindex mail washing
|
|
|
9223 @cindex list server brain damage
|
|
|
9224 @cindex incoming mail treatment
|
|
|
9225
|
|
|
9226 Mailers and list servers are notorious for doing all sorts of really,
|
|
|
9227 really stupid things with mail. ``Hey, RFC822 doesn't explicitly
|
|
|
9228 prohibit us from adding the string @code{wE aRe ElItE!!!!!1!!} to the
|
|
|
9229 end of all lines passing through our server, so let's do that!!!!1!''
|
|
|
9230 Yes, but RFC822 wasn't designed to be read by morons. Things that were
|
|
|
9231 considered to be self-evident were not discussed. So. Here we are.
|
|
|
9232
|
|
|
9233 Case in point: The German version of Microsoft Exchange adds @samp{AW:
|
|
|
9234 } to the subjects of replies instead of @samp{Re: }. I could pretend to
|
|
|
9235 be shocked and dismayed by this, but I haven't got the energy. It is to
|
|
|
9236 laugh.
|
|
|
9237
|
|
|
9238 Gnus provides a plethora of functions for washing articles while
|
|
|
9239 displaying them, but it might be nicer to do the filtering before
|
|
|
9240 storing the mail to disc. For that purpose, we have three hooks and
|
|
|
9241 various functions that can be put in these hooks.
|
|
|
9242
|
|
|
9243 @table @code
|
|
|
9244 @item nnmail-prepare-incoming-hook
|
|
|
9245 @vindex nnmail-prepare-incoming-hook
|
|
|
9246 This hook is called before doing anything with the mail and is meant for
|
|
|
9247 grand, sweeping gestures. Functions to be used include:
|
|
|
9248
|
|
|
9249 @table @code
|
|
|
9250 @item nnheader-ms-strip-cr
|
|
|
9251 @findex nnheader-ms-strip-cr
|
|
|
9252 Remove trailing carriage returns from each line. This is default on
|
|
|
9253 Emacs running on MS machines.
|
|
|
9254
|
|
|
9255 @end table
|
|
|
9256
|
|
|
9257 @item nnmail-prepare-incoming-header-hook
|
|
|
9258 @vindex nnmail-prepare-incoming-header-hook
|
|
|
9259 This hook is called narrowed to each header. It can be used when
|
|
|
9260 cleaning up the headers. Functions that can be used include:
|
|
|
9261
|
|
|
9262 @table @code
|
|
|
9263 @item nnmail-remove-leading-whitespace
|
|
|
9264 @findex nnmail-remove-leading-whitespace
|
|
|
9265 Clear leading white space that ``helpful'' listservs have added to the
|
|
|
9266 headers too make them look nice. Aaah.
|
|
|
9267
|
|
|
9268 @item nnmail-remove-list-identifiers
|
|
|
9269 @findex nnmail-remove-list-identifiers
|
|
|
9270 Some list servers add an identifier---for example, @samp{(idm)}---to the
|
|
|
9271 beginning of all @code{Subject} headers. I'm sure that's nice for
|
|
|
9272 people who use stone age mail readers. This function will remove
|
|
|
9273 strings that match the @code{nnmail-list-identifiers} regexp, which can
|
|
|
9274 also be a list of regexp.
|
|
|
9275
|
|
|
9276 For instance, if you want to remove the @samp{(idm)} and the
|
|
|
9277 @samp{nagnagnag} identifiers:
|
|
|
9278
|
|
|
9279 @lisp
|
|
|
9280 (setq nnmail-list-identifiers
|
|
|
9281 '("(idm)" "nagnagnag"))
|
|
|
9282 @end lisp
|
|
|
9283
|
|
|
9284 @item nnmail-remove-tabs
|
|
|
9285 @findex nnmail-remove-tabs
|
|
|
9286 Translate all @samp{TAB} characters into @samp{SPACE} characters.
|
|
|
9287
|
|
|
9288 @end table
|
|
|
9289
|
|
|
9290 @item nnmail-prepare-incoming-message-hook
|
|
|
9291 @vindex nnmail-prepare-incoming-message-hook
|
|
|
9292 This hook is called narrowed to each message. Functions to be used
|
|
|
9293 include:
|
|
|
9294
|
|
|
9295 @table @code
|
|
|
9296 @item article-de-quoted-unreadable
|
|
|
9297 @findex article-de-quoted-unreadable
|
|
|
9298 Decode Quoted Readable encoding.
|
|
|
9299
|
|
|
9300 @end table
|
|
|
9301 @end table
|
|
|
9302
|
|
0
|
9303
|
|
|
9304 @node Duplicates
|
|
|
9305 @subsection Duplicates
|
|
|
9306
|
|
|
9307 @vindex nnmail-treat-duplicates
|
|
|
9308 @vindex nnmail-message-id-cache-length
|
|
|
9309 @vindex nnmail-message-id-cache-file
|
|
|
9310 @cindex duplicate mails
|
|
|
9311 If you are a member of a couple of mailing list, you will sometime
|
|
|
9312 receive two copies of the same mail. This can be quite annoying, so
|
|
|
9313 @code{nnmail} checks for and treats any duplicates it might find. To do
|
|
16
|
9314 this, it keeps a cache of old @code{Message-ID}s---
|
|
0
|
9315 @code{nnmail-message-id-cache-file}, which is @file{~/.nnmail-cache} by
|
|
|
9316 default. The approximate maximum number of @code{Message-ID}s stored
|
|
|
9317 there is controlled by the @code{nnmail-message-id-cache-length}
|
|
|
9318 variable, which is 1000 by default. (So 1000 @code{Message-ID}s will be
|
|
|
9319 stored.) If all this sounds scary to you, you can set
|
|
|
9320 @code{nnmail-treat-duplicates} to @code{warn} (which is what it is by
|
|
|
9321 default), and @code{nnmail} won't delete duplicate mails. Instead it
|
|
30
|
9322 will insert a warning into the head of the mail saying that it thinks
|
|
|
9323 that this is a duplicate of a different message.
|
|
0
|
9324
|
|
|
9325 This variable can also be a function. If that's the case, the function
|
|
|
9326 will be called from a buffer narrowed to the message in question with
|
|
|
9327 the @code{Message-ID} as a parameter. The function must return either
|
|
|
9328 @code{nil}, @code{warn}, or @code{delete}.
|
|
|
9329
|
|
|
9330 You can turn this feature off completely by setting the variable to
|
|
|
9331 @code{nil}.
|
|
|
9332
|
|
|
9333 If you want all the duplicate mails to be put into a special
|
|
|
9334 @dfn{duplicates} group, you could do that using the normal mail split
|
|
|
9335 methods:
|
|
|
9336
|
|
|
9337 @lisp
|
|
|
9338 (setq nnmail-split-fancy
|
|
|
9339 '(| ;; Messages duplicates go to a separate group.
|
|
|
9340 ("gnus-warning" "duplication of message" "duplicate")
|
|
|
9341 ;; Message from daemons, postmaster, and the like to another.
|
|
|
9342 (any mail "mail.misc")
|
|
|
9343 ;; Other rules.
|
|
|
9344 [ ... ] ))
|
|
|
9345 @end lisp
|
|
|
9346
|
|
|
9347 Or something like:
|
|
|
9348 @lisp
|
|
|
9349 (setq nnmail-split-methods
|
|
|
9350 '(("duplicates" "^Gnus-Warning:")
|
|
|
9351 ;; Other rules.
|
|
|
9352 [...]))
|
|
|
9353 @end lisp
|
|
|
9354
|
|
|
9355 Here's a neat feature: If you know that the recipient reads her mail
|
|
|
9356 with Gnus, and that she has @code{nnmail-treat-duplicates} set to
|
|
|
9357 @code{delete}, you can send her as many insults as you like, just by
|
|
|
9358 using a @code{Message-ID} of a mail that you know that she's already
|
|
|
9359 received. Think of all the fun! She'll never see any of it! Whee!
|
|
|
9360
|
|
|
9361
|
|
|
9362 @node Not Reading Mail
|
|
|
9363 @subsection Not Reading Mail
|
|
|
9364
|
|
|
9365 If you start using any of the mail backends, they have the annoying
|
|
|
9366 habit of assuming that you want to read mail with them. This might not
|
|
|
9367 be unreasonable, but it might not be what you want.
|
|
|
9368
|
|
|
9369 If you set @code{nnmail-spool-file} to @code{nil}, none of the backends
|
|
|
9370 will ever attempt to read incoming mail, which should help.
|
|
|
9371
|
|
|
9372 @vindex nnbabyl-get-new-mail
|
|
|
9373 @vindex nnmbox-get-new-mail
|
|
|
9374 @vindex nnml-get-new-mail
|
|
|
9375 @vindex nnmh-get-new-mail
|
|
|
9376 @vindex nnfolder-get-new-mail
|
|
|
9377 This might be too much, if, for instance, you are reading mail quite
|
|
|
9378 happily with @code{nnml} and just want to peek at some old @sc{rmail}
|
|
|
9379 file you have stashed away with @code{nnbabyl}. All backends have
|
|
|
9380 variables called backend-@code{get-new-mail}. If you want to disable
|
|
|
9381 the @code{nnbabyl} mail reading, you edit the virtual server for the
|
|
|
9382 group to have a setting where @code{nnbabyl-get-new-mail} to @code{nil}.
|
|
|
9383
|
|
|
9384 All the mail backends will call @code{nn}*@code{-prepare-save-mail-hook}
|
|
|
9385 narrowed to the article to be saved before saving it when reading
|
|
|
9386 incoming mail.
|
|
|
9387
|
|
|
9388
|
|
|
9389 @node Choosing a Mail Backend
|
|
|
9390 @subsection Choosing a Mail Backend
|
|
|
9391
|
|
|
9392 Gnus will read the mail spool when you activate a mail group. The mail
|
|
|
9393 file is first copied to your home directory. What happens after that
|
|
|
9394 depends on what format you want to store your mail in.
|
|
|
9395
|
|
|
9396 @menu
|
|
|
9397 * Unix Mail Box:: Using the (quite) standard Un*x mbox.
|
|
|
9398 * Rmail Babyl:: Emacs programs use the rmail babyl format.
|
|
|
9399 * Mail Spool:: Store your mail in a private spool?
|
|
|
9400 * MH Spool:: An mhspool-like backend.
|
|
|
9401 * Mail Folders:: Having one file for each group.
|
|
|
9402 @end menu
|
|
|
9403
|
|
|
9404
|
|
|
9405 @node Unix Mail Box
|
|
|
9406 @subsubsection Unix Mail Box
|
|
|
9407 @cindex nnmbox
|
|
|
9408 @cindex unix mail box
|
|
|
9409
|
|
|
9410 @vindex nnmbox-active-file
|
|
|
9411 @vindex nnmbox-mbox-file
|
|
|
9412 The @dfn{nnmbox} backend will use the standard Un*x mbox file to store
|
|
|
9413 mail. @code{nnmbox} will add extra headers to each mail article to say
|
|
|
9414 which group it belongs in.
|
|
|
9415
|
|
|
9416 Virtual server settings:
|
|
|
9417
|
|
|
9418 @table @code
|
|
|
9419 @item nnmbox-mbox-file
|
|
|
9420 @vindex nnmbox-mbox-file
|
|
|
9421 The name of the mail box in the user's home directory.
|
|
|
9422
|
|
|
9423 @item nnmbox-active-file
|
|
|
9424 @vindex nnmbox-active-file
|
|
|
9425 The name of the active file for the mail box.
|
|
|
9426
|
|
|
9427 @item nnmbox-get-new-mail
|
|
|
9428 @vindex nnmbox-get-new-mail
|
|
|
9429 If non-@code{nil}, @code{nnmbox} will read incoming mail and split it
|
|
|
9430 into groups.
|
|
|
9431 @end table
|
|
|
9432
|
|
|
9433
|
|
|
9434 @node Rmail Babyl
|
|
|
9435 @subsubsection Rmail Babyl
|
|
|
9436 @cindex nnbabyl
|
|
|
9437 @cindex rmail mbox
|
|
|
9438
|
|
|
9439 @vindex nnbabyl-active-file
|
|
|
9440 @vindex nnbabyl-mbox-file
|
|
|
9441 The @dfn{nnbabyl} backend will use a babyl mail box (aka. @dfn{rmail
|
|
|
9442 mbox}) to store mail. @code{nnbabyl} will add extra headers to each mail
|
|
|
9443 article to say which group it belongs in.
|
|
|
9444
|
|
|
9445 Virtual server settings:
|
|
|
9446
|
|
|
9447 @table @code
|
|
|
9448 @item nnbabyl-mbox-file
|
|
|
9449 @vindex nnbabyl-mbox-file
|
|
|
9450 The name of the rmail mbox file.
|
|
|
9451
|
|
|
9452 @item nnbabyl-active-file
|
|
|
9453 @vindex nnbabyl-active-file
|
|
|
9454 The name of the active file for the rmail box.
|
|
|
9455
|
|
|
9456 @item nnbabyl-get-new-mail
|
|
|
9457 @vindex nnbabyl-get-new-mail
|
|
|
9458 If non-@code{nil}, @code{nnbabyl} will read incoming mail.
|
|
|
9459 @end table
|
|
|
9460
|
|
|
9461
|
|
|
9462 @node Mail Spool
|
|
|
9463 @subsubsection Mail Spool
|
|
|
9464 @cindex nnml
|
|
|
9465 @cindex mail @sc{nov} spool
|
|
|
9466
|
|
|
9467 The @dfn{nnml} spool mail format isn't compatible with any other known
|
|
|
9468 format. It should be used with some caution.
|
|
|
9469
|
|
|
9470 @vindex nnml-directory
|
|
|
9471 If you use this backend, Gnus will split all incoming mail into files;
|
|
|
9472 one file for each mail, and put the articles into the correct
|
|
|
9473 directories under the directory specified by the @code{nnml-directory}
|
|
|
9474 variable. The default value is @file{~/Mail/}.
|
|
|
9475
|
|
|
9476 You do not have to create any directories beforehand; Gnus will take
|
|
|
9477 care of all that.
|
|
|
9478
|
|
|
9479 If you have a strict limit as to how many files you are allowed to store
|
|
|
9480 in your account, you should not use this backend. As each mail gets its
|
|
|
9481 own file, you might very well occupy thousands of inodes within a few
|
|
|
9482 weeks. If this is no problem for you, and it isn't a problem for you
|
|
|
9483 having your friendly systems administrator walking around, madly,
|
|
|
9484 shouting ``Who is eating all my inodes?! Who? Who!?!'', then you should
|
|
|
9485 know that this is probably the fastest format to use. You do not have
|
|
|
9486 to trudge through a big mbox file just to read your new mail.
|
|
|
9487
|
|
|
9488 @code{nnml} is probably the slowest backend when it comes to article
|
|
|
9489 splitting. It has to create lots of files, and it also generates
|
|
|
9490 @sc{nov} databases for the incoming mails. This makes is the fastest
|
|
|
9491 backend when it comes to reading mail.
|
|
|
9492
|
|
|
9493 Virtual server settings:
|
|
|
9494
|
|
|
9495 @table @code
|
|
|
9496 @item nnml-directory
|
|
|
9497 @vindex nnml-directory
|
|
|
9498 All @code{nnml} directories will be placed under this directory.
|
|
|
9499
|
|
|
9500 @item nnml-active-file
|
|
|
9501 @vindex nnml-active-file
|
|
|
9502 The active file for the @code{nnml} server.
|
|
|
9503
|
|
|
9504 @item nnml-newsgroups-file
|
|
|
9505 @vindex nnml-newsgroups-file
|
|
|
9506 The @code{nnml} group descriptions file. @xref{Newsgroups File
|
|
|
9507 Format}.
|
|
|
9508
|
|
|
9509 @item nnml-get-new-mail
|
|
|
9510 @vindex nnml-get-new-mail
|
|
|
9511 If non-@code{nil}, @code{nnml} will read incoming mail.
|
|
|
9512
|
|
|
9513 @item nnml-nov-is-evil
|
|
|
9514 @vindex nnml-nov-is-evil
|
|
|
9515 If non-@code{nil}, this backend will ignore any @sc{nov} files.
|
|
|
9516
|
|
|
9517 @item nnml-nov-file-name
|
|
|
9518 @vindex nnml-nov-file-name
|
|
|
9519 The name of the @sc{nov} files. The default is @file{.overview}.
|
|
|
9520
|
|
|
9521 @item nnml-prepare-save-mail-hook
|
|
|
9522 @vindex nnml-prepare-save-mail-hook
|
|
|
9523 Hook run narrowed to an article before saving.
|
|
|
9524
|
|
|
9525 @end table
|
|
|
9526
|
|
|
9527 @findex nnml-generate-nov-databases
|
|
|
9528 If your @code{nnml} groups and @sc{nov} files get totally out of whack,
|
|
|
9529 you can do a complete update by typing @kbd{M-x
|
|
|
9530 nnml-generate-nov-databases}. This command will trawl through the
|
|
|
9531 entire @code{nnml} hierarchy, looking at each and every article, so it
|
|
16
|
9532 might take a while to complete. A better interface to this
|
|
|
9533 functionality can be found in the server buffer (@pxref{Server
|
|
|
9534 Commands}).
|
|
0
|
9535
|
|
|
9536
|
|
|
9537 @node MH Spool
|
|
|
9538 @subsubsection MH Spool
|
|
|
9539 @cindex nnmh
|
|
|
9540 @cindex mh-e mail spool
|
|
|
9541
|
|
|
9542 @code{nnmh} is just like @code{nnml}, except that is doesn't generate
|
|
|
9543 @sc{nov} databases and it doesn't keep an active file. This makes
|
|
|
9544 @code{nnmh} a @emph{much} slower backend than @code{nnml}, but it also
|
|
|
9545 makes it easier to write procmail scripts for.
|
|
|
9546
|
|
|
9547 Virtual server settings:
|
|
|
9548
|
|
|
9549 @table @code
|
|
|
9550 @item nnmh-directory
|
|
|
9551 @vindex nnmh-directory
|
|
|
9552 All @code{nnmh} directories will be located under this directory.
|
|
|
9553
|
|
|
9554 @item nnmh-get-new-mail
|
|
|
9555 @vindex nnmh-get-new-mail
|
|
|
9556 If non-@code{nil}, @code{nnmh} will read incoming mail.
|
|
|
9557
|
|
|
9558 @item nnmh-be-safe
|
|
|
9559 @vindex nnmh-be-safe
|
|
|
9560 If non-@code{nil}, @code{nnmh} will go to ridiculous lengths to make
|
|
|
9561 sure that the articles in the folder are actually what Gnus thinks they
|
|
|
9562 are. It will check date stamps and stat everything in sight, so
|
|
|
9563 setting this to @code{t} will mean a serious slow-down. If you never
|
|
|
9564 use anything but Gnus to read the @code{nnmh} articles, you do not have
|
|
|
9565 to set this variable to @code{t}.
|
|
|
9566 @end table
|
|
|
9567
|
|
|
9568
|
|
|
9569 @node Mail Folders
|
|
|
9570 @subsubsection Mail Folders
|
|
|
9571 @cindex nnfolder
|
|
|
9572 @cindex mbox folders
|
|
|
9573 @cindex mail folders
|
|
|
9574
|
|
|
9575 @code{nnfolder} is a backend for storing each mail group in a separate
|
|
|
9576 file. Each file is in the standard Un*x mbox format. @code{nnfolder}
|
|
|
9577 will add extra headers to keep track of article numbers and arrival
|
|
|
9578 dates.
|
|
|
9579
|
|
|
9580 Virtual server settings:
|
|
|
9581
|
|
|
9582 @table @code
|
|
|
9583 @item nnfolder-directory
|
|
|
9584 @vindex nnfolder-directory
|
|
|
9585 All the @code{nnfolder} mail boxes will be stored under this directory.
|
|
|
9586
|
|
|
9587 @item nnfolder-active-file
|
|
|
9588 @vindex nnfolder-active-file
|
|
|
9589 The name of the active file.
|
|
|
9590
|
|
|
9591 @item nnfolder-newsgroups-file
|
|
|
9592 @vindex nnfolder-newsgroups-file
|
|
|
9593 The name of the group descriptions file. @xref{Newsgroups File Format}.
|
|
|
9594
|
|
|
9595 @item nnfolder-get-new-mail
|
|
|
9596 @vindex nnfolder-get-new-mail
|
|
|
9597 If non-@code{nil}, @code{nnfolder} will read incoming mail.
|
|
|
9598 @end table
|
|
|
9599
|
|
|
9600 @findex nnfolder-generate-active-file
|
|
|
9601 @kindex M-x nnfolder-generate-active-file
|
|
|
9602 If you have lots of @code{nnfolder}-like files you'd like to read with
|
|
|
9603 @code{nnfolder}, you can use the @kbd{M-x nnfolder-generate-active-file}
|
|
|
9604 command to make @code{nnfolder} aware of all likely files in
|
|
|
9605 @code{nnfolder-directory}.
|
|
|
9606
|
|
|
9607
|
|
|
9608 @node Other Sources
|
|
|
9609 @section Other Sources
|
|
|
9610
|
|
|
9611 Gnus can do more than just read news or mail. The methods described
|
|
|
9612 below allow Gnus to view directories and files as if they were
|
|
|
9613 newsgroups.
|
|
|
9614
|
|
|
9615 @menu
|
|
16
|
9616 * Directory Groups:: You can read a directory as if it was a newsgroup.
|
|
|
9617 * Anything Groups:: Dired? Who needs dired?
|
|
|
9618 * Document Groups:: Single files can be the basis of a group.
|
|
|
9619 * SOUP:: Reading @sc{SOUP} packets ``offline''.
|
|
|
9620 * Web Searches:: Creating groups from articles that match a string.
|
|
|
9621 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
|
|
0
|
9622 @end menu
|
|
|
9623
|
|
|
9624
|
|
|
9625 @node Directory Groups
|
|
|
9626 @subsection Directory Groups
|
|
|
9627 @cindex nndir
|
|
|
9628 @cindex directory groups
|
|
|
9629
|
|
|
9630 If you have a directory that has lots of articles in separate files in
|
|
|
9631 it, you might treat it as a newsgroup. The files have to have numerical
|
|
|
9632 names, of course.
|
|
|
9633
|
|
|
9634 This might be an opportune moment to mention @code{ange-ftp}, that most
|
|
|
9635 wonderful of all wonderful Emacs packages. When I wrote @code{nndir}, I
|
|
|
9636 didn't think much about it---a backend to read directories. Big deal.
|
|
|
9637
|
|
|
9638 @code{ange-ftp} changes that picture dramatically. For instance, if you
|
|
16
|
9639 enter the @code{ange-ftp} file name
|
|
|
9640 @file{/ftp.hpc.uh.edu:/pub/emacs/ding-list/} as the the directory name,
|
|
|
9641 @code{ange-ftp} will actually allow you to read this directory over at
|
|
|
9642 @samp{sina} as a newsgroup. Distributed news ahoy!
|
|
0
|
9643
|
|
|
9644 @code{nndir} will use @sc{nov} files if they are present.
|
|
|
9645
|
|
|
9646 @code{nndir} is a ``read-only'' backend---you can't delete or expire
|
|
|
9647 articles with this method. You can use @code{nnmh} or @code{nnml} for
|
|
|
9648 whatever you use @code{nndir} for, so you could switch to any of those
|
|
|
9649 methods if you feel the need to have a non-read-only @code{nndir}.
|
|
|
9650
|
|
|
9651
|
|
|
9652 @node Anything Groups
|
|
|
9653 @subsection Anything Groups
|
|
|
9654 @cindex nneething
|
|
|
9655
|
|
|
9656 From the @code{nndir} backend (which reads a single spool-like
|
|
|
9657 directory), it's just a hop and a skip to @code{nneething}, which
|
|
|
9658 pretends that any arbitrary directory is a newsgroup. Strange, but
|
|
|
9659 true.
|
|
|
9660
|
|
|
9661 When @code{nneething} is presented with a directory, it will scan this
|
|
|
9662 directory and assign article numbers to each file. When you enter such
|
|
|
9663 a group, @code{nneething} must create ``headers'' that Gnus can use.
|
|
|
9664 After all, Gnus is a newsreader, in case you're
|
|
|
9665 forgetting. @code{nneething} does this in a two-step process. First, it
|
|
|
9666 snoops each file in question. If the file looks like an article (i.e.,
|
|
|
9667 the first few lines look like headers), it will use this as the head.
|
|
16
|
9668 If this is just some arbitrary file without a head (e.g. a C source
|
|
0
|
9669 file), @code{nneething} will cobble up a header out of thin air. It
|
|
|
9670 will use file ownership, name and date and do whatever it can with these
|
|
|
9671 elements.
|
|
|
9672
|
|
|
9673 All this should happen automatically for you, and you will be presented
|
|
|
9674 with something that looks very much like a newsgroup. Totally like a
|
|
|
9675 newsgroup, to be precise. If you select an article, it will be displayed
|
|
|
9676 in the article buffer, just as usual.
|
|
|
9677
|
|
|
9678 If you select a line that represents a directory, Gnus will pop you into
|
|
|
9679 a new summary buffer for this @code{nneething} group. And so on. You can
|
|
|
9680 traverse the entire disk this way, if you feel like, but remember that
|
|
|
9681 Gnus is not dired, really, and does not intend to be, either.
|
|
|
9682
|
|
|
9683 There are two overall modes to this action---ephemeral or solid. When
|
|
|
9684 doing the ephemeral thing (i.e., @kbd{G D} from the group buffer), Gnus
|
|
|
9685 will not store information on what files you have read, and what files
|
|
|
9686 are new, and so on. If you create a solid @code{nneething} group the
|
|
|
9687 normal way with @kbd{G m}, Gnus will store a mapping table between
|
|
|
9688 article numbers and file names, and you can treat this group like any
|
|
|
9689 other groups. When you activate a solid @code{nneething} group, you will
|
|
|
9690 be told how many unread articles it contains, etc., etc.
|
|
|
9691
|
|
|
9692 Some variables:
|
|
|
9693
|
|
|
9694 @table @code
|
|
|
9695 @item nneething-map-file-directory
|
|
|
9696 @vindex nneething-map-file-directory
|
|
|
9697 All the mapping files for solid @code{nneething} groups will be stored
|
|
|
9698 in this directory, which defaults to @file{~/.nneething/}.
|
|
|
9699
|
|
|
9700 @item nneething-exclude-files
|
|
|
9701 @vindex nneething-exclude-files
|
|
|
9702 All files that match this regexp will be ignored. Nice to use to exclude
|
|
|
9703 auto-save files and the like, which is what it does by default.
|
|
|
9704
|
|
|
9705 @item nneething-map-file
|
|
|
9706 @vindex nneething-map-file
|
|
|
9707 Name of the map files.
|
|
|
9708 @end table
|
|
|
9709
|
|
|
9710
|
|
|
9711 @node Document Groups
|
|
|
9712 @subsection Document Groups
|
|
|
9713 @cindex nndoc
|
|
|
9714 @cindex documentation group
|
|
|
9715 @cindex help group
|
|
|
9716
|
|
|
9717 @code{nndoc} is a cute little thing that will let you read a single file
|
|
|
9718 as a newsgroup. Several files types are supported:
|
|
|
9719
|
|
|
9720 @table @code
|
|
|
9721 @cindex babyl
|
|
|
9722 @cindex rmail mbox
|
|
|
9723
|
|
|
9724 @item babyl
|
|
|
9725 The babyl (rmail) mail box.
|
|
|
9726 @cindex mbox
|
|
|
9727 @cindex Unix mbox
|
|
|
9728
|
|
|
9729 @item mbox
|
|
|
9730 The standard Unix mbox file.
|
|
|
9731
|
|
|
9732 @cindex MMDF mail box
|
|
|
9733 @item mmdf
|
|
|
9734 The MMDF mail box format.
|
|
|
9735
|
|
|
9736 @item news
|
|
|
9737 Several news articles appended into a file.
|
|
|
9738
|
|
|
9739 @item rnews
|
|
|
9740 @cindex rnews batch files
|
|
|
9741 The rnews batch transport format.
|
|
|
9742 @cindex forwarded messages
|
|
|
9743
|
|
|
9744 @item forward
|
|
|
9745 Forwarded articles.
|
|
|
9746
|
|
|
9747 @item mime-digest
|
|
|
9748 @cindex digest
|
|
|
9749 @cindex MIME digest
|
|
|
9750 @cindex 1153 digest
|
|
|
9751 @cindex RFC 1153 digest
|
|
|
9752 @cindex RFC 341 digest
|
|
|
9753 MIME (RFC 1341) digest format.
|
|
|
9754
|
|
|
9755 @item standard-digest
|
|
|
9756 The standard (RFC 1153) digest format.
|
|
|
9757
|
|
|
9758 @item slack-digest
|
|
|
9759 Non-standard digest format---matches most things, but does it badly.
|
|
|
9760 @end table
|
|
|
9761
|
|
|
9762 You can also use the special ``file type'' @code{guess}, which means
|
|
|
9763 that @code{nndoc} will try to guess what file type it is looking at.
|
|
|
9764 @code{digest} means that @code{nndoc} should guess what digest type the
|
|
|
9765 file is.
|
|
|
9766
|
|
|
9767 @code{nndoc} will not try to change the file or insert any extra headers into
|
|
|
9768 it---it will simply, like, let you use the file as the basis for a
|
|
|
9769 group. And that's it.
|
|
|
9770
|
|
|
9771 If you have some old archived articles that you want to insert into your
|
|
|
9772 new & spiffy Gnus mail backend, @code{nndoc} can probably help you with
|
|
|
9773 that. Say you have an old @file{RMAIL} file with mail that you now want
|
|
|
9774 to split into your new @code{nnml} groups. You look at that file using
|
|
16
|
9775 @code{nndoc} (using the @kbd{G f} command in the group buffer
|
|
|
9776 (@pxref{Foreign Groups})), set the process mark on all the articles in
|
|
|
9777 the buffer (@kbd{M P b}, for instance), and then re-spool (@kbd{B r})
|
|
|
9778 using @code{nnml}. If all goes well, all the mail in the @file{RMAIL}
|
|
|
9779 file is now also stored in lots of @code{nnml} directories, and you can
|
|
|
9780 delete that pesky @file{RMAIL} file. If you have the guts!
|
|
0
|
9781
|
|
|
9782 Virtual server variables:
|
|
|
9783
|
|
|
9784 @table @code
|
|
|
9785 @item nndoc-article-type
|
|
|
9786 @vindex nndoc-article-type
|
|
|
9787 This should be one of @code{mbox}, @code{babyl}, @code{digest},
|
|
34
|
9788 @code{mmdf}, @code{forward}, @code{rfc934}, @code{rfc822-forward},
|
|
|
9789 @code{news}, @code{rnews}, @code{mime-digest}, @code{clari-briefs}, or
|
|
|
9790 @code{guess}.
|
|
0
|
9791
|
|
|
9792 @item nndoc-post-type
|
|
|
9793 @vindex nndoc-post-type
|
|
|
9794 This variable says whether Gnus is to consider the group a news group or
|
|
|
9795 a mail group. There are two legal values: @code{mail} (the default)
|
|
|
9796 and @code{news}.
|
|
|
9797 @end table
|
|
|
9798
|
|
16
|
9799 @menu
|
|
|
9800 * Document Server Internals:: How to add your own document types.
|
|
|
9801 @end menu
|
|
|
9802
|
|
|
9803
|
|
|
9804 @node Document Server Internals
|
|
|
9805 @subsubsection Document Server Internals
|
|
|
9806
|
|
|
9807 Adding new document types to be recognized by @code{nndoc} isn't
|
|
|
9808 difficult. You just have to whip up a definition of what the document
|
|
|
9809 looks like, write a predicate function to recognize that document type,
|
|
|
9810 and then hook into @code{nndoc}.
|
|
|
9811
|
|
|
9812 First, here's an example document type definition:
|
|
|
9813
|
|
|
9814 @example
|
|
|
9815 (mmdf
|
|
|
9816 (article-begin . "^\^A\^A\^A\^A\n")
|
|
|
9817 (body-end . "^\^A\^A\^A\^A\n"))
|
|
|
9818 @end example
|
|
|
9819
|
|
|
9820 The definition is simply a unique @dfn{name} followed by a series of
|
|
|
9821 regexp pseudo-variable settings. Below are the possible
|
|
|
9822 variables---don't be daunted by the number of variables; most document
|
|
|
9823 types can be defined with very few settings:
|
|
|
9824
|
|
|
9825 @table @code
|
|
|
9826 @item first-article
|
|
|
9827 If present, @code{nndoc} will skip past all text until it finds
|
|
|
9828 something that match this regexp. All text before this will be
|
|
|
9829 totally ignored.
|
|
|
9830
|
|
|
9831 @item article-begin
|
|
|
9832 This setting has to be present in all document type definitions. It
|
|
|
9833 says what the beginning of each article looks like.
|
|
|
9834
|
|
|
9835 @item head-begin-function
|
|
|
9836 If present, this should be a function that moves point to the head of
|
|
|
9837 the article.
|
|
|
9838
|
|
|
9839 @item nndoc-head-begin
|
|
|
9840 If present, this should be a regexp that matches the head of the
|
|
|
9841 article.
|
|
|
9842
|
|
|
9843 @item nndoc-head-end
|
|
|
9844 This should match the end of the head of the article. It defaults to
|
|
|
9845 @samp{^$}---the empty line.
|
|
|
9846
|
|
|
9847 @item body-begin-function
|
|
|
9848 If present, this function should move point to the beginning of the body
|
|
|
9849 of the article.
|
|
|
9850
|
|
|
9851 @item body-begin
|
|
|
9852 This should match the beginning of the body of the article. It defaults
|
|
|
9853 to @samp{^\n}.
|
|
|
9854
|
|
|
9855 @item body-end-function
|
|
|
9856 If present, this function should move point to the end of the body of
|
|
|
9857 the article.
|
|
|
9858
|
|
|
9859 @item body-end
|
|
|
9860 If present, this should match the end of the body of the article.
|
|
|
9861
|
|
|
9862 @item nndoc-file-end
|
|
|
9863 If present, this should match the end of the file. All text after this
|
|
|
9864 regexp will be totally ignored.
|
|
|
9865
|
|
|
9866 @end table
|
|
|
9867
|
|
|
9868 So, using these variables @code{nndoc} is able to dissect a document
|
|
|
9869 file into a series of articles, each with a head and a body. However, a
|
|
|
9870 few more variables are needed since not all document types are all that
|
|
|
9871 news-like---variables needed to transform the head or the body into
|
|
|
9872 something that's palatable for Gnus:
|
|
|
9873
|
|
|
9874 @table @code
|
|
|
9875 @item prepare-body-function
|
|
|
9876 If present, this function will be called when requesting an article. It
|
|
|
9877 will be called with point at the start of the body, and is useful if the
|
|
|
9878 document has encoded some parts of its contents.
|
|
|
9879
|
|
|
9880 @item article-transform-function
|
|
|
9881 If present, this function is called when requesting an article. It's
|
|
|
9882 meant to be used how more wide-ranging transformation of both head and
|
|
|
9883 body of the article.
|
|
|
9884
|
|
|
9885 @item generate-head-function
|
|
|
9886 If present, this function is called to generate a head that Gnus can
|
|
|
9887 understand. It is called with the article number as a parameter, and is
|
|
|
9888 expected to generate a nice head for the article in question. It is
|
|
|
9889 called when requesting the headers of all articles.
|
|
|
9890
|
|
|
9891 @end table
|
|
|
9892
|
|
|
9893 Let's look at the most complicated example I can come up with---standard
|
|
|
9894 digests:
|
|
|
9895
|
|
|
9896 @example
|
|
|
9897 (standard-digest
|
|
|
9898 (first-article . ,(concat "^" (make-string 70 ?-) "\n\n+"))
|
|
|
9899 (article-begin . ,(concat "\n\n" (make-string 30 ?-) "\n\n+"))
|
|
|
9900 (prepare-body-function . nndoc-unquote-dashes)
|
|
|
9901 (body-end-function . nndoc-digest-body-end)
|
|
|
9902 (head-end . "^ ?$")
|
|
|
9903 (body-begin . "^ ?\n")
|
|
|
9904 (file-end . "^End of .*digest.*[0-9].*\n\\*\\*\\|^End of.*Digest *$")
|
|
|
9905 (subtype digest guess))
|
|
|
9906 @end example
|
|
|
9907
|
|
|
9908 We see that all text before a 70-width line of dashes is ignored; all
|
|
|
9909 text after a line that starts with that @samp{^End of} is also ignored;
|
|
|
9910 each article begins with a 30-width line of dashes; the line separating
|
|
|
9911 the head from the body may contain a single space; and that the body is
|
|
|
9912 run through @code{nndoc-unquote-dashes} before being delivered.
|
|
|
9913
|
|
|
9914 To hook your own document definition into @code{nndoc}, use the
|
|
|
9915 @code{nndoc-add-type} function. It takes two parameters---the first is
|
|
|
9916 the definition itself and the second (optional) parameter says where in
|
|
|
9917 the document type definition alist to put this definition. The alist is
|
|
|
9918 traversed sequentially, and @code{nndoc-TYPE-type-p} is called for each
|
|
|
9919 type. So @code{nndoc-mmdf-type-p} is called to see whether a document
|
|
|
9920 is of @code{mmdf} type, and so on. These type predicates should return
|
|
|
9921 @code{nil} if the document is not of the correct type; @code{t} if it is
|
|
|
9922 of the correct type; and a number if the document might be of the
|
|
|
9923 correct type. A high number means high probability; a low number means
|
|
|
9924 low probability with @samp{0} being the lowest legal number.
|
|
|
9925
|
|
0
|
9926
|
|
|
9927 @node SOUP
|
|
|
9928 @subsection SOUP
|
|
|
9929 @cindex SOUP
|
|
|
9930 @cindex offline
|
|
|
9931
|
|
|
9932 In the PC world people often talk about ``offline'' newsreaders. These
|
|
|
9933 are thingies that are combined reader/news transport monstrosities.
|
|
|
9934 With built-in modem programs. Yecchh!
|
|
|
9935
|
|
|
9936 Of course, us Unix Weenie types of human beans use things like
|
|
|
9937 @code{uucp} and, like, @code{nntpd} and set up proper news and mail
|
|
|
9938 transport things like Ghod intended. And then we just use normal
|
|
|
9939 newsreaders.
|
|
|
9940
|
|
|
9941 However, it can sometimes be convenient to do something a that's a bit
|
|
|
9942 easier on the brain if you have a very slow modem, and you're not really
|
|
|
9943 that interested in doing things properly.
|
|
|
9944
|
|
|
9945 A file format called @sc{soup} has been developed for transporting news
|
|
|
9946 and mail from servers to home machines and back again. It can be a bit
|
|
|
9947 fiddly.
|
|
|
9948
|
|
16
|
9949 First some terminology:
|
|
|
9950
|
|
|
9951 @table @dfn
|
|
|
9952
|
|
|
9953 @item server
|
|
|
9954 This is the machine that is connected to the outside world and where you
|
|
|
9955 get news and/or mail from.
|
|
|
9956
|
|
|
9957 @item home machine
|
|
|
9958 This is the machine that you want to do the actual reading and responding
|
|
|
9959 on. It is typically not connected to the rest of the world in any way.
|
|
|
9960
|
|
|
9961 @item packet
|
|
|
9962 Something that contains messages and/or commands. There are two kinds
|
|
|
9963 of packets:
|
|
|
9964
|
|
|
9965 @table @dfn
|
|
|
9966 @item message packets
|
|
|
9967 These are packets made at the server, and typically contains lots of
|
|
|
9968 messages for you to read. These are called @file{SoupoutX.tgz} by
|
|
|
9969 default, where @var{X} is a number.
|
|
|
9970
|
|
|
9971 @item response packets
|
|
|
9972 These are packets made at the home machine, and typically contains
|
|
|
9973 replies that you've written. These are called @file{SoupinX.tgz} by
|
|
|
9974 default, where @var{X} is a number.
|
|
|
9975
|
|
|
9976 @end table
|
|
|
9977
|
|
|
9978 @end table
|
|
|
9979
|
|
|
9980
|
|
0
|
9981 @enumerate
|
|
|
9982
|
|
|
9983 @item
|
|
|
9984 You log in on the server and create a @sc{soup} packet. You can either
|
|
16
|
9985 use a dedicated @sc{soup} thingie (like the @code{awk} program), or you
|
|
|
9986 can use Gnus to create the packet with its @sc{soup} commands (@kbd{O
|
|
|
9987 s} and/or @kbd{G s b}; and then @kbd{G s p}) (@pxref{SOUP Commands}).
|
|
0
|
9988
|
|
|
9989 @item
|
|
|
9990 You transfer the packet home. Rail, boat, car or modem will do fine.
|
|
|
9991
|
|
|
9992 @item
|
|
|
9993 You put the packet in your home directory.
|
|
|
9994
|
|
|
9995 @item
|
|
16
|
9996 You fire up Gnus on your home machine using the @code{nnsoup} backend as
|
|
|
9997 the native or secondary server.
|
|
0
|
9998
|
|
|
9999 @item
|
|
|
10000 You read articles and mail and answer and followup to the things you
|
|
16
|
10001 want (@pxref{SOUP Replies}).
|
|
0
|
10002
|
|
|
10003 @item
|
|
|
10004 You do the @kbd{G s r} command to pack these replies into a @sc{soup}
|
|
|
10005 packet.
|
|
|
10006
|
|
|
10007 @item
|
|
|
10008 You transfer this packet to the server.
|
|
|
10009
|
|
|
10010 @item
|
|
|
10011 You use Gnus to mail this packet out with the @kbd{G s s} command.
|
|
|
10012
|
|
|
10013 @item
|
|
|
10014 You then repeat until you die.
|
|
|
10015
|
|
|
10016 @end enumerate
|
|
|
10017
|
|
|
10018 So you basically have a bipartite system---you use @code{nnsoup} for
|
|
|
10019 reading and Gnus for packing/sending these @sc{soup} packets.
|
|
|
10020
|
|
|
10021 @menu
|
|
|
10022 * SOUP Commands:: Commands for creating and sending @sc{soup} packets
|
|
|
10023 * SOUP Groups:: A backend for reading @sc{soup} packets.
|
|
|
10024 * SOUP Replies:: How to enable @code{nnsoup} to take over mail and news.
|
|
|
10025 @end menu
|
|
|
10026
|
|
|
10027
|
|
|
10028 @node SOUP Commands
|
|
|
10029 @subsubsection SOUP Commands
|
|
|
10030
|
|
16
|
10031 These are commands for creating and manipulating @sc{soup} packets.
|
|
|
10032
|
|
0
|
10033 @table @kbd
|
|
|
10034 @item G s b
|
|
|
10035 @kindex G s b (Group)
|
|
|
10036 @findex gnus-group-brew-soup
|
|
|
10037 Pack all unread articles in the current group
|
|
|
10038 (@code{gnus-group-brew-soup}). This command understands the
|
|
|
10039 process/prefix convention.
|
|
|
10040
|
|
|
10041 @item G s w
|
|
|
10042 @kindex G s w (Group)
|
|
|
10043 @findex gnus-soup-save-areas
|
|
16
|
10044 Save all @sc{soup} data files (@code{gnus-soup-save-areas}).
|
|
0
|
10045
|
|
|
10046 @item G s s
|
|
|
10047 @kindex G s s (Group)
|
|
|
10048 @findex gnus-soup-send-replies
|
|
|
10049 Send all replies from the replies packet
|
|
|
10050 (@code{gnus-soup-send-replies}).
|
|
|
10051
|
|
|
10052 @item G s p
|
|
|
10053 @kindex G s p (Group)
|
|
|
10054 @findex gnus-soup-pack-packet
|
|
|
10055 Pack all files into a @sc{soup} packet (@code{gnus-soup-pack-packet}).
|
|
|
10056
|
|
|
10057 @item G s r
|
|
|
10058 @kindex G s r (Group)
|
|
|
10059 @findex nnsoup-pack-replies
|
|
|
10060 Pack all replies into a replies packet (@code{nnsoup-pack-replies}).
|
|
|
10061
|
|
|
10062 @item O s
|
|
|
10063 @kindex O s (Summary)
|
|
|
10064 @findex gnus-soup-add-article
|
|
|
10065 This summary-mode command adds the current article to a @sc{soup} packet
|
|
|
10066 (@code{gnus-soup-add-article}). It understands the process/prefix
|
|
16
|
10067 convention (@pxref{Process/Prefix}).
|
|
0
|
10068
|
|
|
10069 @end table
|
|
|
10070
|
|
|
10071
|
|
|
10072 There are a few variables to customize where Gnus will put all these
|
|
|
10073 thingies:
|
|
|
10074
|
|
|
10075 @table @code
|
|
|
10076
|
|
|
10077 @item gnus-soup-directory
|
|
|
10078 @vindex gnus-soup-directory
|
|
|
10079 Directory where Gnus will save intermediate files while composing
|
|
|
10080 @sc{soup} packets. The default is @file{~/SoupBrew/}.
|
|
|
10081
|
|
|
10082 @item gnus-soup-replies-directory
|
|
|
10083 @vindex gnus-soup-replies-directory
|
|
|
10084 This is what Gnus will use as a temporary directory while sending our
|
|
16
|
10085 reply packets. @file{~/SoupBrew/SoupReplies/} is the default.
|
|
0
|
10086
|
|
|
10087 @item gnus-soup-prefix-file
|
|
|
10088 @vindex gnus-soup-prefix-file
|
|
|
10089 Name of the file where Gnus stores the last used prefix. The default is
|
|
|
10090 @samp{gnus-prefix}.
|
|
|
10091
|
|
|
10092 @item gnus-soup-packer
|
|
|
10093 @vindex gnus-soup-packer
|
|
|
10094 A format string command for packing a @sc{soup} packet. The default is
|
|
|
10095 @samp{tar cf - %s | gzip > $HOME/Soupout%d.tgz}.
|
|
|
10096
|
|
|
10097 @item gnus-soup-unpacker
|
|
|
10098 @vindex gnus-soup-unpacker
|
|
|
10099 Format string command for unpacking a @sc{soup} packet. The default is
|
|
|
10100 @samp{gunzip -c %s | tar xvf -}.
|
|
|
10101
|
|
|
10102 @item gnus-soup-packet-directory
|
|
|
10103 @vindex gnus-soup-packet-directory
|
|
|
10104 Where Gnus will look for reply packets. The default is @file{~/}.
|
|
|
10105
|
|
|
10106 @item gnus-soup-packet-regexp
|
|
|
10107 @vindex gnus-soup-packet-regexp
|
|
|
10108 Regular expression matching @sc{soup} reply packets in
|
|
|
10109 @code{gnus-soup-packet-directory}.
|
|
|
10110
|
|
|
10111 @end table
|
|
|
10112
|
|
|
10113
|
|
|
10114 @node SOUP Groups
|
|
|
10115 @subsubsection @sc{soup} Groups
|
|
|
10116 @cindex nnsoup
|
|
|
10117
|
|
|
10118 @code{nnsoup} is the backend for reading @sc{soup} packets. It will
|
|
|
10119 read incoming packets, unpack them, and put them in a directory where
|
|
|
10120 you can read them at leisure.
|
|
|
10121
|
|
|
10122 These are the variables you can use to customize its behavior:
|
|
|
10123
|
|
|
10124 @table @code
|
|
|
10125
|
|
|
10126 @item nnsoup-tmp-directory
|
|
|
10127 @vindex nnsoup-tmp-directory
|
|
|
10128 When @code{nnsoup} unpacks a @sc{soup} packet, it does it in this
|
|
|
10129 directory. (@file{/tmp/} by default.)
|
|
|
10130
|
|
|
10131 @item nnsoup-directory
|
|
|
10132 @vindex nnsoup-directory
|
|
|
10133 @code{nnsoup} then moves each message and index file to this directory.
|
|
|
10134 The default is @file{~/SOUP/}.
|
|
|
10135
|
|
|
10136 @item nnsoup-replies-directory
|
|
|
10137 @vindex nnsoup-replies-directory
|
|
|
10138 All replies will stored in this directory before being packed into a
|
|
|
10139 reply packet. The default is @file{~/SOUP/replies/"}.
|
|
|
10140
|
|
|
10141 @item nnsoup-replies-format-type
|
|
|
10142 @vindex nnsoup-replies-format-type
|
|
|
10143 The @sc{soup} format of the replies packets. The default is @samp{?n}
|
|
|
10144 (rnews), and I don't think you should touch that variable. I probably
|
|
|
10145 shouldn't even have documented it. Drats! Too late!
|
|
|
10146
|
|
|
10147 @item nnsoup-replies-index-type
|
|
|
10148 @vindex nnsoup-replies-index-type
|
|
|
10149 The index type of the replies packet. The is @samp{?n}, which means
|
|
|
10150 ``none''. Don't fiddle with this one either!
|
|
|
10151
|
|
|
10152 @item nnsoup-active-file
|
|
|
10153 @vindex nnsoup-active-file
|
|
|
10154 Where @code{nnsoup} stores lots of information. This is not an ``active
|
|
|
10155 file'' in the @code{nntp} sense; it's an Emacs Lisp file. If you lose
|
|
|
10156 this file or mess it up in any way, you're dead. The default is
|
|
|
10157 @file{~/SOUP/active}.
|
|
|
10158
|
|
|
10159 @item nnsoup-packer
|
|
|
10160 @vindex nnsoup-packer
|
|
|
10161 Format string command for packing a reply @sc{soup} packet. The default
|
|
|
10162 is @samp{tar cf - %s | gzip > $HOME/Soupin%d.tgz}.
|
|
|
10163
|
|
|
10164 @item nnsoup-unpacker
|
|
|
10165 @vindex nnsoup-unpacker
|
|
|
10166 Format string command for unpacking incoming @sc{soup} packets. The
|
|
|
10167 default is @samp{gunzip -c %s | tar xvf -}.
|
|
|
10168
|
|
|
10169 @item nnsoup-packet-directory
|
|
|
10170 @vindex nnsoup-packet-directory
|
|
|
10171 Where @code{nnsoup} will look for incoming packets. The default is
|
|
|
10172 @file{~/}.
|
|
|
10173
|
|
|
10174 @item nnsoup-packet-regexp
|
|
|
10175 @vindex nnsoup-packet-regexp
|
|
|
10176 Regular expression matching incoming @sc{soup} packets. The default is
|
|
|
10177 @samp{Soupout}.
|
|
|
10178
|
|
|
10179 @end table
|
|
|
10180
|
|
|
10181
|
|
|
10182 @node SOUP Replies
|
|
|
10183 @subsubsection SOUP Replies
|
|
|
10184
|
|
|
10185 Just using @code{nnsoup} won't mean that your postings and mailings end
|
|
|
10186 up in @sc{soup} reply packets automagically. You have to work a bit
|
|
|
10187 more for that to happen.
|
|
|
10188
|
|
|
10189 @findex nnsoup-set-variables
|
|
|
10190 The @code{nnsoup-set-variables} command will set the appropriate
|
|
|
10191 variables to ensure that all your followups and replies end up in the
|
|
|
10192 @sc{soup} system.
|
|
|
10193
|
|
|
10194 In specific, this is what it does:
|
|
|
10195
|
|
|
10196 @lisp
|
|
16
|
10197 (setq message-send-news-function 'nnsoup-request-post)
|
|
|
10198 (setq message-send-mail-function 'nnsoup-request-mail)
|
|
0
|
10199 @end lisp
|
|
|
10200
|
|
|
10201 And that's it, really. If you only want news to go into the @sc{soup}
|
|
|
10202 system you just use the first line. If you only want mail to be
|
|
|
10203 @sc{soup}ed you use the second.
|
|
|
10204
|
|
|
10205
|
|
16
|
10206 @node Web Searches
|
|
|
10207 @subsection Web Searches
|
|
|
10208 @cindex nnweb
|
|
|
10209 @cindex DejaNews
|
|
|
10210 @cindex Alta Vista
|
|
|
10211 @cindex InReference
|
|
|
10212 @cindex Usenet searches
|
|
|
10213 @cindex searching the Usenet
|
|
|
10214
|
|
|
10215 It's, like, too neat to search the Usenet for articles that match a
|
|
|
10216 string, but it, like, totally @emph{sucks}, like, totally, to use one of
|
|
|
10217 those, like, Web browsers, and you, like, have to, rilly, like, look at
|
|
|
10218 the commercials, so, like, with Gnus you can do @emph{rad}, rilly,
|
|
|
10219 searches without having to use a browser.
|
|
|
10220
|
|
|
10221 The @code{nnweb} backend allows an easy interface to the mighty search
|
|
|
10222 engine. You create an @code{nnweb} group, enter a search pattern, and
|
|
|
10223 then enter the group and read the articles like you would any normal
|
|
|
10224 group. The @kbd{G w} command in the group buffer (@pxref{Foreign
|
|
|
10225 Groups}) will do this in an easy-to-use fashion.
|
|
|
10226
|
|
|
10227 @code{nnweb} groups don't really lend themselves to being solid
|
|
|
10228 groups---they have a very fleeting idea of article numbers. In fact,
|
|
|
10229 each time you enter an @code{nnweb} group (not even changing the search
|
|
|
10230 pattern), you are likely to get the articles ordered in a different
|
|
|
10231 manner. Not even using duplicate suppression (@code{Duplicate
|
|
|
10232 Suppression}) will help, since @code{nnweb} doesn't even know the
|
|
|
10233 @code{Message-ID} of the articles before reading them using some search
|
|
|
10234 engines (DejaNews, for instance). The only possible way to keep track
|
|
|
10235 of which articles you've read is by scoring on the @code{Date}
|
|
|
10236 header---mark all articles that were posted before the last date you
|
|
|
10237 read the group as read.
|
|
|
10238
|
|
|
10239 If the search engine changes its output substantially, @code{nnweb}
|
|
|
10240 won't be able to parse it and will fail. One could hardly fault the Web
|
|
|
10241 providers if they were to do this---their @emph{raison d'être} is to
|
|
|
10242 make money off of advertisements, not to provide services to the
|
|
|
10243 community. Since @code{nnweb} washes the ads off all the articles, one
|
|
|
10244 might think that the providers might be somewhat miffed. We'll see.
|
|
|
10245
|
|
|
10246 You must have the @code{url} and @code{w3} package installed to be able
|
|
|
10247 to use @code{nnweb}.
|
|
|
10248
|
|
|
10249 Virtual server variables:
|
|
|
10250
|
|
|
10251 @table @code
|
|
|
10252 @item nnweb-type
|
|
|
10253 @vindex nnweb-type
|
|
|
10254 What search engine type is being used. The currently supported types
|
|
|
10255 are @code{dejanews}, @code{altavista} and @code{reference}.
|
|
|
10256
|
|
|
10257 @item nnweb-search
|
|
|
10258 @vindex nnweb-search
|
|
|
10259 The search string to feed to the search engine.
|
|
|
10260
|
|
|
10261 @item nnweb-max-hits
|
|
|
10262 @vindex nnweb-max-hits
|
|
|
10263 Advisory maximum number of hits per search to display. The default is
|
|
|
10264 100.
|
|
|
10265
|
|
|
10266 @item nnweb-type-definition
|
|
|
10267 @vindex nnweb-type-definition
|
|
|
10268 Type-to-definition alist. This alist says what @code{nnweb} should do
|
|
|
10269 with the various search engine types. The following elements must be
|
|
|
10270 present:
|
|
|
10271
|
|
|
10272 @table @code
|
|
|
10273 @item article
|
|
|
10274 Function to decode the article and provide something that Gnus
|
|
|
10275 understands.
|
|
|
10276
|
|
|
10277 @item map
|
|
|
10278 Function to create an article number to message header and URL alist.
|
|
|
10279
|
|
|
10280 @item search
|
|
|
10281 Function to send the search string to the search engine.
|
|
|
10282
|
|
|
10283 @item address
|
|
|
10284 The address the aforementioned function should send the search string
|
|
|
10285 to.
|
|
|
10286
|
|
|
10287 @item id
|
|
|
10288 Format string URL to fetch an article by @code{Message-ID}.
|
|
|
10289 @end table
|
|
|
10290
|
|
|
10291 @end table
|
|
|
10292
|
|
|
10293
|
|
|
10294
|
|
|
10295 @node Mail-To-News Gateways
|
|
|
10296 @subsection Mail-To-News Gateways
|
|
|
10297 @cindex mail-to-news gateways
|
|
|
10298 @cindex gateways
|
|
|
10299
|
|
|
10300 If your local @code{nntp} server doesn't allow posting, for some reason
|
|
|
10301 or other, you can post using one of the numerous mail-to-news gateways.
|
|
|
10302 The @code{nngateway} backend provides the interface.
|
|
|
10303
|
|
|
10304 Note that you can't read anything from this backend---it can only be
|
|
|
10305 used to post with.
|
|
|
10306
|
|
|
10307 Server variables:
|
|
|
10308
|
|
|
10309 @table @code
|
|
|
10310 @item nngateway-address
|
|
|
10311 @vindex nngateway-address
|
|
|
10312 This is the address of the mail-to-news gateway.
|
|
|
10313
|
|
|
10314 @item nngateway-header-transformation
|
|
|
10315 @vindex nngateway-header-transformation
|
|
|
10316 News headers have often have to be transformed in some odd way or other
|
|
|
10317 for the mail-to-news gateway to accept it. This variable says what
|
|
|
10318 transformation should be called, and defaults to
|
|
|
10319 @code{nngateway-simple-header-transformation}. The function is called
|
|
|
10320 narrowed to the headers to be transformed and with one parameter---the
|
|
|
10321 gateway address.
|
|
|
10322
|
|
|
10323 This default function just inserts a new @code{To} header based on the
|
|
|
10324 @code{Newsgroups} header and the gateway address---an article with this
|
|
|
10325 @code{Newsgroups} header:
|
|
|
10326
|
|
|
10327 @example
|
|
|
10328 Newsgroups: alt.religion.emacs
|
|
|
10329 @end example
|
|
|
10330
|
|
|
10331 will get this @code{From} header inserted:
|
|
|
10332
|
|
|
10333 @example
|
|
|
10334 To: alt-religion-emacs@@GATEWAY
|
|
|
10335 @end example
|
|
|
10336
|
|
|
10337 @end table
|
|
|
10338
|
|
|
10339 So, to use this, simply say something like:
|
|
|
10340
|
|
|
10341 @lisp
|
|
|
10342 (setq gnus-post-method '(nngateway "GATEWAY.ADDRESS"))
|
|
|
10343 @end lisp
|
|
|
10344
|
|
|
10345
|
|
0
|
10346 @node Combined Groups
|
|
|
10347 @section Combined Groups
|
|
|
10348
|
|
|
10349 Gnus allows combining a mixture of all the other group types into bigger
|
|
|
10350 groups.
|
|
|
10351
|
|
|
10352 @menu
|
|
|
10353 * Virtual Groups:: Combining articles from many groups.
|
|
|
10354 * Kibozed Groups:: Looking through parts of the newsfeed for articles.
|
|
|
10355 @end menu
|
|
|
10356
|
|
|
10357
|
|
|
10358 @node Virtual Groups
|
|
|
10359 @subsection Virtual Groups
|
|
|
10360 @cindex nnvirtual
|
|
|
10361 @cindex virtual groups
|
|
|
10362
|
|
|
10363 An @dfn{nnvirtual group} is really nothing more than a collection of
|
|
|
10364 other groups.
|
|
|
10365
|
|
|
10366 For instance, if you are tired of reading many small group, you can
|
|
|
10367 put them all in one big group, and then grow tired of reading one
|
|
|
10368 big, unwieldy group. The joys of computing!
|
|
|
10369
|
|
|
10370 You specify @code{nnvirtual} as the method. The address should be a
|
|
|
10371 regexp to match component groups.
|
|
|
10372
|
|
|
10373 All marks in the virtual group will stick to the articles in the
|
|
|
10374 component groups. So if you tick an article in a virtual group, the
|
|
|
10375 article will also be ticked in the component group from whence it came.
|
|
|
10376 (And vice versa---marks from the component groups will also be shown in
|
|
|
10377 the virtual group.)
|
|
|
10378
|
|
|
10379 Here's an example @code{nnvirtual} method that collects all Andrea Dworkin
|
|
|
10380 newsgroups into one, big, happy newsgroup:
|
|
|
10381
|
|
|
10382 @lisp
|
|
|
10383 (nnvirtual "^alt\\.fan\\.andrea-dworkin$\\|^rec\\.dworkin.*")
|
|
|
10384 @end lisp
|
|
|
10385
|
|
|
10386 The component groups can be native or foreign; everything should work
|
|
|
10387 smoothly, but if your computer explodes, it was probably my fault.
|
|
|
10388
|
|
|
10389 Collecting the same group from several servers might actually be a good
|
|
|
10390 idea if users have set the Distribution header to limit distribution.
|
|
|
10391 If you would like to read @samp{soc.motss} both from a server in Japan
|
|
|
10392 and a server in Norway, you could use the following as the group regexp:
|
|
|
10393
|
|
|
10394 @example
|
|
|
10395 "^nntp+some.server.jp:soc.motss$\\|^nntp+some.server.no:soc.motss$"
|
|
|
10396 @end example
|
|
|
10397
|
|
|
10398 This should work kinda smoothly---all articles from both groups should
|
|
|
10399 end up in this one, and there should be no duplicates. Threading (and
|
|
|
10400 the rest) will still work as usual, but there might be problems with the
|
|
|
10401 sequence of articles. Sorting on date might be an option here
|
|
|
10402 (@pxref{Selecting a Group}.
|
|
|
10403
|
|
|
10404 One limitation, however---all groups that are included in a virtual
|
|
|
10405 group has to be alive (i.e., subscribed or unsubscribed). Killed or
|
|
|
10406 zombie groups can't be component groups for @code{nnvirtual} groups.
|
|
|
10407
|
|
|
10408 @vindex nnvirtual-always-rescan
|
|
|
10409 If the @code{nnvirtual-always-rescan} is non-@code{nil},
|
|
|
10410 @code{nnvirtual} will always scan groups for unread articles when
|
|
|
10411 entering a virtual group. If this variable is @code{nil} (which is the
|
|
|
10412 default) and you read articles in a component group after the virtual
|
|
|
10413 group has been activated, the read articles from the component group
|
|
|
10414 will show up when you enter the virtual group. You'll also see this
|
|
|
10415 effect if you have two virtual groups that contain the same component
|
|
|
10416 group. If that's the case, you should set this variable to @code{t}.
|
|
|
10417 Or you can just tap @code{M-g} on the virtual group every time before
|
|
|
10418 you enter it---it'll have much the same effect.
|
|
|
10419
|
|
|
10420
|
|
|
10421 @node Kibozed Groups
|
|
|
10422 @subsection Kibozed Groups
|
|
|
10423 @cindex nnkiboze
|
|
|
10424 @cindex kibozing
|
|
|
10425
|
|
|
10426 @dfn{Kibozing} is defined by @sc{oed} as ``grepping through (parts of)
|
|
|
10427 the news feed''. @code{nnkiboze} is a backend that will do this for
|
|
|
10428 you. Oh joy! Now you can grind any @sc{nntp} server down to a halt
|
|
|
10429 with useless requests! Oh happiness!
|
|
|
10430
|
|
2
|
10431 @kindex G k (Group)
|
|
|
10432 To create a kibozed group, use the @kbd{G k} command in the group
|
|
|
10433 buffer.
|
|
|
10434
|
|
0
|
10435 The address field of the @code{nnkiboze} method is, as with
|
|
|
10436 @code{nnvirtual}, a regexp to match groups to be ``included'' in the
|
|
|
10437 @code{nnkiboze} group. There most similarities between @code{nnkiboze}
|
|
|
10438 and @code{nnvirtual} ends.
|
|
|
10439
|
|
|
10440 In addition to this regexp detailing component groups, an @code{nnkiboze} group
|
|
|
10441 must have a score file to say what articles that are to be included in
|
|
|
10442 the group (@pxref{Scoring}).
|
|
|
10443
|
|
|
10444 @kindex M-x nnkiboze-generate-groups
|
|
|
10445 @findex nnkiboze-generate-groups
|
|
|
10446 You must run @kbd{M-x nnkiboze-generate-groups} after creating the
|
|
|
10447 @code{nnkiboze} groups you want to have. This command will take time. Lots of
|
|
|
10448 time. Oodles and oodles of time. Gnus has to fetch the headers from
|
|
|
10449 all the articles in all the components groups and run them through the
|
|
|
10450 scoring process to determine if there are any articles in the groups
|
|
|
10451 that are to be part of the @code{nnkiboze} groups.
|
|
|
10452
|
|
|
10453 Please limit the number of component groups by using restrictive
|
|
|
10454 regexps. Otherwise your sysadmin may become annoyed with you, and the
|
|
|
10455 @sc{nntp} site may throw you off and never let you back in again.
|
|
|
10456 Stranger things have happened.
|
|
|
10457
|
|
|
10458 @code{nnkiboze} component groups do not have to be alive---they can be dead,
|
|
|
10459 and they can be foreign. No restrictions.
|
|
|
10460
|
|
|
10461 @vindex nnkiboze-directory
|
|
|
10462 The generation of an @code{nnkiboze} group means writing two files in
|
|
|
10463 @code{nnkiboze-directory}, which is @file{~/News/} by default. One
|
|
|
10464 contains the @sc{nov} header lines for all the articles in the group,
|
|
|
10465 and the other is an additional @file{.newsrc} file to store information
|
|
|
10466 on what groups that have been searched through to find component
|
|
|
10467 articles.
|
|
|
10468
|
|
|
10469 Articles that are marked as read in the @code{nnkiboze} group will have their
|
|
|
10470 @sc{nov} lines removed from the @sc{nov} file.
|
|
|
10471
|
|
|
10472
|
|
|
10473 @node Scoring
|
|
|
10474 @chapter Scoring
|
|
|
10475 @cindex scoring
|
|
|
10476
|
|
|
10477 Other people use @dfn{kill files}, but we here at Gnus Towers like
|
|
|
10478 scoring better than killing, so we'd rather switch than fight. They do
|
|
|
10479 something completely different as well, so sit up straight and pay
|
|
|
10480 attention!
|
|
|
10481
|
|
|
10482 @vindex gnus-summary-mark-below
|
|
|
10483 All articles have a default score (@code{gnus-summary-default-score}),
|
|
|
10484 which is 0 by default. This score may be raised or lowered either
|
|
|
10485 interactively or by score files. Articles that have a score lower than
|
|
|
10486 @code{gnus-summary-mark-below} are marked as read.
|
|
|
10487
|
|
|
10488 Gnus will read any @dfn{score files} that apply to the current group
|
|
|
10489 before generating the summary buffer.
|
|
|
10490
|
|
|
10491 There are several commands in the summary buffer that insert score
|
|
|
10492 entries based on the current article. You can, for instance, ask Gnus to
|
|
|
10493 lower or increase the score of all articles with a certain subject.
|
|
|
10494
|
|
|
10495 There are two sorts of scoring entries: Permanent and temporary.
|
|
|
10496 Temporary score entries are self-expiring entries. Any entries that are
|
|
|
10497 temporary and have not been used for, say, a week, will be removed
|
|
|
10498 silently to help keep the sizes of the score files down.
|
|
|
10499
|
|
|
10500 @menu
|
|
|
10501 * Summary Score Commands:: Adding score entries for the current group.
|
|
|
10502 * Group Score Commands:: General score commands.
|
|
|
10503 * Score Variables:: Customize your scoring. (My, what terminology).
|
|
|
10504 * Score File Format:: What a score file may contain.
|
|
|
10505 * Score File Editing:: You can edit score files by hand as well.
|
|
16
|
10506 * Adaptive Scoring:: Big Sister Gnus knows what you read.
|
|
|
10507 * Home Score File:: How to say where new score entries are to go.
|
|
0
|
10508 * Followups To Yourself:: Having Gnus notice when people answer you.
|
|
|
10509 * Scoring Tips:: How to score effectively.
|
|
|
10510 * Reverse Scoring:: That problem child of old is not problem.
|
|
|
10511 * Global Score Files:: Earth-spanning, ear-splitting score files.
|
|
|
10512 * Kill Files:: They are still here, but they can be ignored.
|
|
16
|
10513 * Converting Kill Files:: Translating kill files to score files.
|
|
0
|
10514 * GroupLens:: Getting predictions on what you like to read.
|
|
16
|
10515 * Advanced Scoring:: Using logical expressions to build score rules.
|
|
|
10516 * Score Decays:: It can be useful to let scores wither away.
|
|
0
|
10517 @end menu
|
|
|
10518
|
|
|
10519
|
|
|
10520 @node Summary Score Commands
|
|
|
10521 @section Summary Score Commands
|
|
|
10522 @cindex score commands
|
|
|
10523
|
|
|
10524 The score commands that alter score entries do not actually modify real
|
|
|
10525 score files. That would be too inefficient. Gnus maintains a cache of
|
|
|
10526 previously loaded score files, one of which is considered the
|
|
|
10527 @dfn{current score file alist}. The score commands simply insert
|
|
|
10528 entries into this list, and upon group exit, this list is saved.
|
|
|
10529
|
|
|
10530 The current score file is by default the group's local score file, even
|
|
|
10531 if no such score file actually exists. To insert score commands into
|
|
16
|
10532 some other score file (e.g. @file{all.SCORE}), you must first make this
|
|
0
|
10533 score file the current one.
|
|
|
10534
|
|
|
10535 General score commands that don't actually change the score file:
|
|
|
10536
|
|
|
10537 @table @kbd
|
|
|
10538
|
|
|
10539 @item V s
|
|
|
10540 @kindex V s (Summary)
|
|
|
10541 @findex gnus-summary-set-score
|
|
|
10542 Set the score of the current article (@code{gnus-summary-set-score}).
|
|
|
10543
|
|
|
10544 @item V S
|
|
|
10545 @kindex V S (Summary)
|
|
|
10546 @findex gnus-summary-current-score
|
|
|
10547 Display the score of the current article
|
|
|
10548 (@code{gnus-summary-current-score}).
|
|
|
10549
|
|
|
10550 @item V t
|
|
|
10551 @kindex V t (Summary)
|
|
|
10552 @findex gnus-score-find-trace
|
|
|
10553 Display all score rules that have been used on the current article
|
|
|
10554 (@code{gnus-score-find-trace}).
|
|
|
10555
|
|
|
10556 @item V R
|
|
16
|
10557 @kindex V R (Summary)
|
|
0
|
10558 @findex gnus-summary-rescore
|
|
|
10559 Run the current summary through the scoring process
|
|
|
10560 (@code{gnus-summary-rescore}). This might be useful if you're playing
|
|
|
10561 around with your score files behind Gnus' back and want to see the
|
|
|
10562 effect you're having.
|
|
|
10563
|
|
|
10564 @item V a
|
|
|
10565 @kindex V a (Summary)
|
|
|
10566 @findex gnus-summary-score-entry
|
|
|
10567 Add a new score entry, and allow specifying all elements
|
|
|
10568 (@code{gnus-summary-score-entry}).
|
|
|
10569
|
|
|
10570 @item V c
|
|
|
10571 @kindex V c (Summary)
|
|
|
10572 @findex gnus-score-change-score-file
|
|
|
10573 Make a different score file the current
|
|
|
10574 (@code{gnus-score-change-score-file}).
|
|
|
10575
|
|
|
10576 @item V e
|
|
|
10577 @kindex V e (Summary)
|
|
|
10578 @findex gnus-score-edit-current-scores
|
|
|
10579 Edit the current score file (@code{gnus-score-edit-current-scores}).
|
|
|
10580 You will be popped into a @code{gnus-score-mode} buffer (@pxref{Score
|
|
|
10581 File Editing}).
|
|
|
10582
|
|
|
10583 @item V f
|
|
|
10584 @kindex V f (Summary)
|
|
|
10585 @findex gnus-score-edit-file
|
|
|
10586 Edit a score file and make this score file the current one
|
|
|
10587 (@code{gnus-score-edit-file}).
|
|
|
10588
|
|
|
10589 @item V F
|
|
|
10590 @kindex V F (Summary)
|
|
|
10591 @findex gnus-score-flush-cache
|
|
16
|
10592 Flush the score cache (@code{gnus-score-flush-cache}). This is useful
|
|
0
|
10593 after editing score files.
|
|
|
10594
|
|
|
10595 @item V C
|
|
|
10596 @kindex V C (Summary)
|
|
|
10597 @findex gnus-score-customize
|
|
|
10598 Customize a score file in a visually pleasing manner
|
|
|
10599 (@code{gnus-score-customize}).
|
|
|
10600
|
|
|
10601 @item I C-i
|
|
|
10602 @kindex I C-i (Summary)
|
|
|
10603 @findex gnus-summary-raise-score
|
|
|
10604 Increase the score of the current article
|
|
|
10605 (@code{gnus-summary-raise-score}).
|
|
|
10606
|
|
|
10607 @item L C-l
|
|
|
10608 @kindex L C-l (Summary)
|
|
|
10609 @findex gnus-summary-lower-score
|
|
|
10610 Lower the score of the current article
|
|
|
10611 (@code{gnus-summary-lower-score}).
|
|
|
10612 @end table
|
|
|
10613
|
|
|
10614 The rest of these commands modify the local score file.
|
|
|
10615
|
|
|
10616 @table @kbd
|
|
|
10617
|
|
|
10618 @item V m
|
|
|
10619 @kindex V m (Summary)
|
|
|
10620 @findex gnus-score-set-mark-below
|
|
|
10621 Prompt for a score, and mark all articles with a score below this as
|
|
|
10622 read (@code{gnus-score-set-mark-below}).
|
|
|
10623
|
|
2
|
10624 @item V x
|
|
|
10625 @kindex V x (Summary)
|
|
0
|
10626 @findex gnus-score-set-expunge-below
|
|
2
|
10627 Prompt for a score, and add a score rule to the current score file to
|
|
|
10628 expunge all articles below this score
|
|
|
10629 (@code{gnus-score-set-expunge-below}).
|
|
0
|
10630 @end table
|
|
|
10631
|
|
|
10632 The keystrokes for actually making score entries follow a very regular
|
|
|
10633 pattern, so there's no need to list all the commands. (Hundreds of
|
|
|
10634 them.)
|
|
|
10635
|
|
|
10636 @enumerate
|
|
|
10637 @item
|
|
|
10638 The first key is either @kbd{I} (upper case i) for increasing the score
|
|
|
10639 or @kbd{L} for lowering the score.
|
|
|
10640 @item
|
|
|
10641 The second key says what header you want to score on. The following
|
|
|
10642 keys are available:
|
|
|
10643 @table @kbd
|
|
|
10644
|
|
|
10645 @item a
|
|
|
10646 Score on the author name.
|
|
|
10647
|
|
|
10648 @item s
|
|
|
10649 Score on the subject line.
|
|
|
10650
|
|
|
10651 @item x
|
|
|
10652 Score on the Xref line---i.e., the cross-posting line.
|
|
|
10653
|
|
|
10654 @item t
|
|
|
10655 Score on thread---the References line.
|
|
|
10656
|
|
|
10657 @item d
|
|
|
10658 Score on the date.
|
|
|
10659
|
|
|
10660 @item l
|
|
|
10661 Score on the number of lines.
|
|
|
10662
|
|
|
10663 @item i
|
|
|
10664 Score on the Message-ID.
|
|
|
10665
|
|
|
10666 @item f
|
|
|
10667 Score on followups.
|
|
|
10668
|
|
|
10669 @item b
|
|
|
10670 Score on the body.
|
|
|
10671
|
|
|
10672 @item h
|
|
|
10673 Score on the head.
|
|
|
10674 @end table
|
|
|
10675
|
|
|
10676 @item
|
|
|
10677 The third key is the match type. Which match types are legal depends on
|
|
|
10678 what headers you are scoring on.
|
|
|
10679
|
|
|
10680 @table @code
|
|
|
10681
|
|
|
10682 @item strings
|
|
|
10683
|
|
|
10684 @table @kbd
|
|
|
10685
|
|
|
10686 @item e
|
|
|
10687 Exact matching.
|
|
|
10688
|
|
|
10689 @item s
|
|
|
10690 Substring matching.
|
|
|
10691
|
|
|
10692 @item f
|
|
26
|
10693 Fuzzy matching (@pxref{Fuzzy Matching}).
|
|
0
|
10694
|
|
|
10695 @item r
|
|
|
10696 Regexp matching
|
|
|
10697 @end table
|
|
|
10698
|
|
|
10699 @item date
|
|
|
10700 @table @kbd
|
|
|
10701
|
|
|
10702 @item b
|
|
|
10703 Before date.
|
|
|
10704
|
|
|
10705 @item a
|
|
|
10706 At date.
|
|
|
10707
|
|
|
10708 @item n
|
|
|
10709 This date.
|
|
|
10710 @end table
|
|
|
10711
|
|
|
10712 @item number
|
|
|
10713 @table @kbd
|
|
|
10714
|
|
|
10715 @item <
|
|
|
10716 Less than number.
|
|
|
10717
|
|
|
10718 @item =
|
|
|
10719 Equal to number.
|
|
|
10720
|
|
|
10721 @item >
|
|
|
10722 Greater than number.
|
|
|
10723 @end table
|
|
|
10724 @end table
|
|
|
10725
|
|
|
10726 @item
|
|
|
10727 The fourth and final key says whether this is a temporary (i.e., expiring)
|
|
|
10728 score entry, or a permanent (i.e., non-expiring) score entry, or whether
|
|
|
10729 it is to be done immediately, without adding to the score file.
|
|
|
10730 @table @kbd
|
|
|
10731
|
|
|
10732 @item t
|
|
|
10733 Temporary score entry.
|
|
|
10734
|
|
|
10735 @item p
|
|
|
10736 Permanent score entry.
|
|
|
10737
|
|
|
10738 @item i
|
|
|
10739 Immediately scoring.
|
|
|
10740 @end table
|
|
|
10741
|
|
|
10742 @end enumerate
|
|
|
10743
|
|
|
10744 So, let's say you want to increase the score on the current author with
|
|
|
10745 exact matching permanently: @kbd{I a e p}. If you want to lower the
|
|
|
10746 score based on the subject line, using substring matching, and make a
|
|
|
10747 temporary score entry: @kbd{L s s t}. Pretty easy.
|
|
|
10748
|
|
|
10749 To make things a bit more complicated, there are shortcuts. If you use
|
|
|
10750 a capital letter on either the second or third keys, Gnus will use
|
|
|
10751 defaults for the remaining one or two keystrokes. The defaults are
|
|
|
10752 ``substring'' and ``temporary''. So @kbd{I A} is the same as @kbd{I a s
|
|
|
10753 t}, and @kbd{I a R} is the same as @kbd{I a r t}.
|
|
|
10754
|
|
|
10755 @vindex gnus-score-mimic-keymap
|
|
|
10756 The @code{gnus-score-mimic-keymap} says whether these commands will
|
|
|
10757 pretend they are keymaps or not.
|
|
|
10758
|
|
|
10759
|
|
|
10760 @node Group Score Commands
|
|
|
10761 @section Group Score Commands
|
|
|
10762 @cindex group score commands
|
|
|
10763
|
|
|
10764 There aren't many of these as yet, I'm afraid.
|
|
|
10765
|
|
|
10766 @table @kbd
|
|
|
10767
|
|
|
10768 @item W f
|
|
|
10769 @kindex W f (Group)
|
|
|
10770 @findex gnus-score-flush-cache
|
|
|
10771 Gnus maintains a cache of score alists to avoid having to reload them
|
|
|
10772 all the time. This command will flush the cache
|
|
|
10773 (@code{gnus-score-flush-cache}).
|
|
|
10774
|
|
|
10775 @end table
|
|
|
10776
|
|
|
10777
|
|
|
10778 @node Score Variables
|
|
|
10779 @section Score Variables
|
|
|
10780 @cindex score variables
|
|
|
10781
|
|
|
10782 @table @code
|
|
|
10783
|
|
|
10784 @item gnus-use-scoring
|
|
|
10785 @vindex gnus-use-scoring
|
|
|
10786 If @code{nil}, Gnus will not check for score files, and will not, in
|
|
|
10787 general, do any score-related work. This is @code{t} by default.
|
|
|
10788
|
|
|
10789 @item gnus-kill-killed
|
|
|
10790 @vindex gnus-kill-killed
|
|
|
10791 If this variable is @code{nil}, Gnus will never apply score files to
|
|
|
10792 articles that have already been through the kill process. While this
|
|
|
10793 may save you lots of time, it also means that if you apply a kill file
|
|
|
10794 to a group, and then change the kill file and want to run it over you
|
|
|
10795 group again to kill more articles, it won't work. You have to set this
|
|
|
10796 variable to @code{t} to do that. (It is @code{t} by default.)
|
|
|
10797
|
|
|
10798 @item gnus-kill-files-directory
|
|
|
10799 @vindex gnus-kill-files-directory
|
|
|
10800 All kill and score files will be stored in this directory, which is
|
|
|
10801 initialized from the @code{SAVEDIR} environment variable by default.
|
|
|
10802 This is @file{~/News/} by default.
|
|
|
10803
|
|
|
10804 @item gnus-score-file-suffix
|
|
|
10805 @vindex gnus-score-file-suffix
|
|
|
10806 Suffix to add to the group name to arrive at the score file name
|
|
|
10807 (@samp{SCORE} by default.)
|
|
|
10808
|
|
|
10809 @item gnus-score-uncacheable-files
|
|
|
10810 @vindex gnus-score-uncacheable-files
|
|
|
10811 @cindex score cache
|
|
|
10812 All score files are normally cached to avoid excessive re-loading of
|
|
|
10813 score files. However, if this might make you Emacs grow big and
|
|
|
10814 bloated, so this regexp can be used to weed out score files that are
|
|
|
10815 unlikely to be needed again. It would be a bad idea to deny caching of
|
|
|
10816 @file{all.SCORE}, while it might be a good idea to not cache
|
|
|
10817 @file{comp.infosystems.www.authoring.misc.ADAPT}. In fact, this
|
|
|
10818 variable is @samp{ADAPT$} by default, so no adaptive score files will
|
|
|
10819 be cached.
|
|
|
10820
|
|
|
10821 @item gnus-save-score
|
|
|
10822 @vindex gnus-save-score
|
|
|
10823 If you have really complicated score files, and do lots of batch
|
|
|
10824 scoring, then you might set this variable to @code{t}. This will make
|
|
|
10825 Gnus save the scores into the @file{.newsrc.eld} file.
|
|
|
10826
|
|
|
10827 @item gnus-score-interactive-default-score
|
|
|
10828 @vindex gnus-score-interactive-default-score
|
|
|
10829 Score used by all the interactive raise/lower commands to raise/lower
|
|
|
10830 score with. Default is 1000, which may seem excessive, but this is to
|
|
|
10831 ensure that the adaptive scoring scheme gets enough room to play with.
|
|
|
10832 We don't want the small changes from the adaptive scoring to overwrite
|
|
|
10833 manually entered data.
|
|
|
10834
|
|
|
10835 @item gnus-summary-default-score
|
|
|
10836 @vindex gnus-summary-default-score
|
|
|
10837 Default score of an article, which is 0 by default.
|
|
|
10838
|
|
16
|
10839 @item gnus-summary-expunge-below
|
|
|
10840 @vindex gnus-summary-expunge-below
|
|
|
10841 Don't display the summary lines of articles that have scores lower than
|
|
|
10842 this variable. This is @code{nil} by default, which means that no
|
|
|
10843 articles will be hidden.
|
|
|
10844
|
|
0
|
10845 @item gnus-score-over-mark
|
|
|
10846 @vindex gnus-score-over-mark
|
|
|
10847 Mark (in the third column) used for articles with a score over the
|
|
|
10848 default. Default is @samp{+}.
|
|
|
10849
|
|
|
10850 @item gnus-score-below-mark
|
|
|
10851 @vindex gnus-score-below-mark
|
|
|
10852 Mark (in the third column) used for articles with a score below the
|
|
|
10853 default. Default is @samp{-}.
|
|
|
10854
|
|
|
10855 @item gnus-score-find-score-files-function
|
|
|
10856 @vindex gnus-score-find-score-files-function
|
|
|
10857 Function used to find score files for the current group. This function
|
|
|
10858 is called with the name of the group as the argument.
|
|
|
10859
|
|
|
10860 Predefined functions available are:
|
|
|
10861 @table @code
|
|
|
10862
|
|
|
10863 @item gnus-score-find-single
|
|
|
10864 @findex gnus-score-find-single
|
|
|
10865 Only apply the group's own score file.
|
|
|
10866
|
|
|
10867 @item gnus-score-find-bnews
|
|
|
10868 @findex gnus-score-find-bnews
|
|
|
10869 Apply all score files that match, using bnews syntax. This is the
|
|
16
|
10870 default. If the current group is @samp{gnu.emacs.gnus}, for instance,
|
|
0
|
10871 @file{all.emacs.all.SCORE}, @file{not.alt.all.SCORE} and
|
|
|
10872 @file{gnu.all.SCORE} would all apply. In short, the instances of
|
|
|
10873 @samp{all} in the score file names are translated into @samp{.*}, and
|
|
|
10874 then a regexp match is done.
|
|
|
10875
|
|
|
10876 This means that if you have some score entries that you want to apply to
|
|
|
10877 all groups, then you put those entries in the @file{all.SCORE} file.
|
|
|
10878
|
|
16
|
10879 The score files are applied in a semi-random order, although Gnus will
|
|
|
10880 try to apply the more general score files before the more specific score
|
|
|
10881 files. It does this by looking at the number of elements in the score
|
|
|
10882 file names---discarding the @samp{all} elements.
|
|
|
10883
|
|
0
|
10884 @item gnus-score-find-hierarchical
|
|
|
10885 @findex gnus-score-find-hierarchical
|
|
|
10886 Apply all score files from all the parent groups. This means that you
|
|
16
|
10887 can't have score files like @file{all.SCORE}, but you can have
|
|
|
10888 @file{SCORE}, @file{comp.SCORE} and @file{comp.emacs.SCORE}.
|
|
0
|
10889
|
|
|
10890 @end table
|
|
|
10891 This variable can also be a list of functions. In that case, all these
|
|
|
10892 functions will be called, and all the returned lists of score files will
|
|
|
10893 be applied. These functions can also return lists of score alists
|
|
|
10894 directly. In that case, the functions that return these non-file score
|
|
|
10895 alists should probably be placed before the ``real'' score file
|
|
|
10896 functions, to ensure that the last score file returned is the local
|
|
|
10897 score file. Phu.
|
|
|
10898
|
|
|
10899 @item gnus-score-expiry-days
|
|
|
10900 @vindex gnus-score-expiry-days
|
|
|
10901 This variable says how many days should pass before an unused score file
|
|
|
10902 entry is expired. If this variable is @code{nil}, no score file entries
|
|
|
10903 are expired. It's 7 by default.
|
|
|
10904
|
|
|
10905 @item gnus-update-score-entry-dates
|
|
|
10906 @vindex gnus-update-score-entry-dates
|
|
|
10907 If this variable is non-@code{nil}, matching score entries will have
|
|
|
10908 their dates updated. (This is how Gnus controls expiry---all
|
|
|
10909 non-matching entries will become too old while matching entries will
|
|
|
10910 stay fresh and young.) However, if you set this variable to @code{nil},
|
|
|
10911 even matching entries will grow old and will have to face that oh-so
|
|
|
10912 grim reaper.
|
|
|
10913
|
|
|
10914 @item gnus-score-after-write-file-function
|
|
|
10915 @vindex gnus-score-after-write-file-function
|
|
|
10916 Function called with the name of the score file just written.
|
|
|
10917
|
|
|
10918 @end table
|
|
|
10919
|
|
|
10920
|
|
|
10921 @node Score File Format
|
|
|
10922 @section Score File Format
|
|
|
10923 @cindex score file format
|
|
|
10924
|
|
|
10925 A score file is an @code{emacs-lisp} file that normally contains just a
|
|
|
10926 single form. Casual users are not expected to edit these files;
|
|
|
10927 everything can be changed from the summary buffer.
|
|
|
10928
|
|
|
10929 Anyway, if you'd like to dig into it yourself, here's an example:
|
|
|
10930
|
|
|
10931 @lisp
|
|
|
10932 (("from"
|
|
|
10933 ("Lars Ingebrigtsen" -10000)
|
|
|
10934 ("Per Abrahamsen")
|
|
|
10935 ("larsi\\|lmi" -50000 nil R))
|
|
|
10936 ("subject"
|
|
|
10937 ("Ding is Badd" nil 728373))
|
|
|
10938 ("xref"
|
|
|
10939 ("alt.politics" -1000 728372 s))
|
|
|
10940 ("lines"
|
|
|
10941 (2 -100 nil <))
|
|
|
10942 (mark 0)
|
|
|
10943 (expunge -1000)
|
|
|
10944 (mark-and-expunge -10)
|
|
|
10945 (read-only nil)
|
|
|
10946 (orphan -10)
|
|
|
10947 (adapt t)
|
|
|
10948 (files "/hom/larsi/News/gnu.SCORE")
|
|
|
10949 (exclude-files "all.SCORE")
|
|
|
10950 (local (gnus-newsgroup-auto-expire t)
|
|
|
10951 (gnus-summary-make-false-root 'empty))
|
|
|
10952 (eval (ding)))
|
|
|
10953 @end lisp
|
|
|
10954
|
|
|
10955 This example demonstrates absolutely everything about a score file.
|
|
|
10956
|
|
|
10957 Even though this looks much like lisp code, nothing here is actually
|
|
|
10958 @code{eval}ed. The lisp reader is used to read this form, though, so it
|
|
|
10959 has to be legal syntactically, if not semantically.
|
|
|
10960
|
|
|
10961 Six keys are supported by this alist:
|
|
|
10962
|
|
|
10963 @table @code
|
|
|
10964
|
|
|
10965 @item STRING
|
|
|
10966 If the key is a string, it is the name of the header to perform the
|
|
|
10967 match on. Scoring can only be performed on these eight headers:
|
|
|
10968 @code{From}, @code{Subject}, @code{References}, @code{Message-ID},
|
|
|
10969 @code{Xref}, @code{Lines}, @code{Chars} and @code{Date}. In addition to
|
|
|
10970 these headers, there are three strings to tell Gnus to fetch the entire
|
|
|
10971 article and do the match on larger parts of the article: @code{Body}
|
|
|
10972 will perform the match on the body of the article, @code{Head} will
|
|
|
10973 perform the match on the head of the article, and @code{All} will
|
|
|
10974 perform the match on the entire article. Note that using any of these
|
|
|
10975 last three keys will slow down group entry @emph{considerably}. The
|
|
|
10976 final ``header'' you can score on is @code{Followup}. These score
|
|
|
10977 entries will result in new score entries being added for all follow-ups
|
|
|
10978 to articles that matches these score entries.
|
|
|
10979
|
|
|
10980 Following this key is a arbitrary number of score entries, where each
|
|
|
10981 score entry has one to four elements.
|
|
|
10982 @enumerate
|
|
|
10983
|
|
|
10984 @item
|
|
|
10985 The first element is the @dfn{match element}. On most headers this will
|
|
|
10986 be a string, but on the Lines and Chars headers, this must be an
|
|
|
10987 integer.
|
|
|
10988
|
|
|
10989 @item
|
|
|
10990 If the second element is present, it should be a number---the @dfn{score
|
|
|
10991 element}. This number should be an integer in the neginf to posinf
|
|
|
10992 interval. This number is added to the score of the article if the match
|
|
|
10993 is successful. If this element is not present, the
|
|
|
10994 @code{gnus-score-interactive-default-score} number will be used
|
|
|
10995 instead. This is 1000 by default.
|
|
|
10996
|
|
|
10997 @item
|
|
|
10998 If the third element is present, it should be a number---the @dfn{date
|
|
|
10999 element}. This date says when the last time this score entry matched,
|
|
|
11000 which provides a mechanism for expiring the score entries. It this
|
|
|
11001 element is not present, the score entry is permanent. The date is
|
|
28
|
11002 represented by the number of days since December 31, 1 BCE.
|
|
0
|
11003
|
|
|
11004 @item
|
|
|
11005 If the fourth element is present, it should be a symbol---the @dfn{type
|
|
|
11006 element}. This element specifies what function should be used to see
|
|
|
11007 whether this score entry matches the article. What match types that can
|
|
|
11008 be used depends on what header you wish to perform the match on.
|
|
|
11009 @table @dfn
|
|
|
11010
|
|
|
11011 @item From, Subject, References, Xref, Message-ID
|
|
16
|
11012 For most header types, there are the @code{r} and @code{R} (regexp), as
|
|
|
11013 well as @code{s} and @code{S} (substring) types, and @code{e} and
|
|
|
11014 @code{E} (exact match), and @code{w} (word match) types. If this
|
|
|
11015 element is not present, Gnus will assume that substring matching should
|
|
|
11016 be used. @code{R}, @code{S}, and @code{E} differ from the others in
|
|
|
11017 that the matches will be done in a case-sensitive manner. All these
|
|
|
11018 one-letter types are really just abbreviations for the @code{regexp},
|
|
|
11019 @code{string}, @code{exact}, and @code{word} types, which you can use
|
|
|
11020 instead, if you feel like.
|
|
0
|
11021
|
|
|
11022 @item Lines, Chars
|
|
|
11023 These two headers use different match types: @code{<}, @code{>},
|
|
16
|
11024 @code{=}, @code{>=} and @code{<=}. When matching on @code{Lines}, be
|
|
|
11025 careful because some backends (like @code{nndir}) do not generate
|
|
|
11026 @code{Lines} header, so every article ends up being marked as having 0
|
|
|
11027 lines. This can lead to strange results if you happen to lower score of
|
|
|
11028 the articles with few lines.
|
|
0
|
11029
|
|
|
11030 @item Date
|
|
16
|
11031 For the Date header we have three kinda silly match types:
|
|
|
11032 @code{before}, @code{at} and @code{after}. I can't really imagine this
|
|
|
11033 ever being useful, but, like, it would feel kinda silly not to provide
|
|
|
11034 this function. Just in case. You never know. Better safe than sorry.
|
|
|
11035 Once burnt, twice shy. Don't judge a book by its cover. Never not have
|
|
|
11036 sex on a first date. (I have been told that at least one person, and I
|
|
|
11037 quote, ``found this function indispensable'', however.)
|
|
|
11038
|
|
|
11039 @cindex ISO8601
|
|
|
11040 @cindex date
|
|
|
11041 A more useful match type is @code{regexp}. With it, you can match the
|
|
|
11042 date string using a regular expression. The date is normalized to
|
|
|
11043 ISO8601 compact format first---@samp{YYYYMMDDTHHMMSS}. If you want to
|
|
|
11044 match all articles that have been posted on April 1st in every year, you
|
|
|
11045 could use @samp{....0401.........} as a match string, for instance.
|
|
|
11046 (Note that the date is kept in its original time zone, so this will
|
|
|
11047 match articles that were posted when it was April 1st where the article
|
|
|
11048 was posted from. Time zones are such wholesome fun for the whole
|
|
|
11049 family, eh?)
|
|
0
|
11050
|
|
|
11051 @item Head, Body, All
|
|
|
11052 These three match keys use the same match types as the @code{From} (etc)
|
|
|
11053 header uses.
|
|
|
11054
|
|
|
11055 @item Followup
|
|
16
|
11056 This match key is somewhat special, in that it will match the
|
|
|
11057 @code{From} header, and affect the score of not only the matching
|
|
|
11058 articles, but also all followups to the matching articles. This allows
|
|
|
11059 you e.g. increase the score of followups to your own articles, or
|
|
|
11060 decrease the score of followups to the articles of some known
|
|
|
11061 trouble-maker. Uses the same match types as the @code{From} header
|
|
|
11062 uses.
|
|
0
|
11063
|
|
|
11064 @item Thread
|
|
16
|
11065 This match key works along the same lines as the @code{Followup} match
|
|
|
11066 key. If you say that you want to score on a (sub-)thread that is
|
|
|
11067 started by an article with a @code{Message-ID} @var{X}, then you add a
|
|
|
11068 @samp{thread} match. This will add a new @samp{thread} match for each
|
|
|
11069 article that has @var{X} in its @code{References} header. (These new
|
|
|
11070 @samp{thread} matches will use the @code{Message-ID}s of these matching
|
|
|
11071 articles.) This will ensure that you can raise/lower the score of an
|
|
|
11072 entire thread, even though some articles in the thread may not have
|
|
|
11073 complete @code{References} headers. Note that using this may lead to
|
|
|
11074 undeterministic scores of the articles in the thread.
|
|
0
|
11075 @end table
|
|
|
11076 @end enumerate
|
|
|
11077
|
|
|
11078 @item mark
|
|
|
11079 The value of this entry should be a number. Any articles with a score
|
|
|
11080 lower than this number will be marked as read.
|
|
|
11081
|
|
|
11082 @item expunge
|
|
|
11083 The value of this entry should be a number. Any articles with a score
|
|
|
11084 lower than this number will be removed from the summary buffer.
|
|
|
11085
|
|
|
11086 @item mark-and-expunge
|
|
|
11087 The value of this entry should be a number. Any articles with a score
|
|
|
11088 lower than this number will be marked as read and removed from the
|
|
|
11089 summary buffer.
|
|
|
11090
|
|
|
11091 @item thread-mark-and-expunge
|
|
|
11092 The value of this entry should be a number. All articles that belong to
|
|
|
11093 a thread that has a total score below this number will be marked as read
|
|
|
11094 and removed from the summary buffer. @code{gnus-thread-score-function}
|
|
|
11095 says how to compute the total score for a thread.
|
|
|
11096
|
|
|
11097 @item files
|
|
|
11098 The value of this entry should be any number of file names. These files
|
|
|
11099 are assumed to be score files as well, and will be loaded the same way
|
|
|
11100 this one was.
|
|
|
11101
|
|
|
11102 @item exclude-files
|
|
16
|
11103 The clue of this entry should be any number of files. These files will
|
|
0
|
11104 not be loaded, even though they would normally be so, for some reason or
|
|
|
11105 other.
|
|
|
11106
|
|
|
11107 @item eval
|
|
|
11108 The value of this entry will be @code{eval}el. This element will be
|
|
|
11109 ignored when handling global score files.
|
|
|
11110
|
|
|
11111 @item read-only
|
|
|
11112 Read-only score files will not be updated or saved. Global score files
|
|
|
11113 should feature this atom (@pxref{Global Score Files}).
|
|
|
11114
|
|
|
11115 @item orphan
|
|
|
11116 The value of this entry should be a number. Articles that do not have
|
|
|
11117 parents will get this number added to their scores. Imagine you follow
|
|
|
11118 some high-volume newsgroup, like @samp{comp.lang.c}. Most likely you
|
|
|
11119 will only follow a few of the threads, also want to see any new threads.
|
|
|
11120
|
|
|
11121 You can do this with the following two score file entries:
|
|
|
11122
|
|
|
11123 @example
|
|
16
|
11124 (orphan -500)
|
|
|
11125 (mark-and-expunge -100)
|
|
0
|
11126 @end example
|
|
|
11127
|
|
|
11128 When you enter the group the first time, you will only see the new
|
|
|
11129 threads. You then raise the score of the threads that you find
|
|
|
11130 interesting (with @kbd{I T} or @kbd{I S}), and ignore (@kbd{C y}) the
|
|
|
11131 rest. Next time you enter the group, you will see new articles in the
|
|
|
11132 interesting threads, plus any new threads.
|
|
|
11133
|
|
2
|
11134 I.e.---the orphan score atom is for high-volume groups where there
|
|
0
|
11135 exist a few interesting threads which can't be found automatically by
|
|
|
11136 ordinary scoring rules.
|
|
|
11137
|
|
|
11138 @item adapt
|
|
|
11139 This entry controls the adaptive scoring. If it is @code{t}, the
|
|
|
11140 default adaptive scoring rules will be used. If it is @code{ignore}, no
|
|
|
11141 adaptive scoring will be performed on this group. If it is a list, this
|
|
|
11142 list will be used as the adaptive scoring rules. If it isn't present,
|
|
|
11143 or is something other than @code{t} or @code{ignore}, the default
|
|
|
11144 adaptive scoring rules will be used. If you want to use adaptive
|
|
|
11145 scoring on most groups, you'd set @code{gnus-use-adaptive-scoring} to
|
|
|
11146 @code{t}, and insert an @code{(adapt ignore)} in the groups where you do
|
|
|
11147 not want adaptive scoring. If you only want adaptive scoring in a few
|
|
|
11148 groups, you'd set @code{gnus-use-adaptive-scoring} to @code{nil}, and
|
|
|
11149 insert @code{(adapt t)} in the score files of the groups where you want
|
|
|
11150 it.
|
|
|
11151
|
|
|
11152 @item adapt-file
|
|
|
11153 All adaptive score entries will go to the file named by this entry. It
|
|
|
11154 will also be applied when entering the group. This atom might be handy
|
|
|
11155 if you want to adapt on several groups at once, using the same adaptive
|
|
|
11156 file for a number of groups.
|
|
|
11157
|
|
|
11158 @item local
|
|
|
11159 @cindex local variables
|
|
|
11160 The value of this entry should be a list of @code{(VAR VALUE)} pairs.
|
|
|
11161 Each @var{var} will be made buffer-local to the current summary buffer,
|
|
|
11162 and set to the value specified. This is a convenient, if somewhat
|
|
|
11163 strange, way of setting variables in some groups if you don't like hooks
|
|
|
11164 much.
|
|
|
11165 @end table
|
|
|
11166
|
|
|
11167
|
|
|
11168 @node Score File Editing
|
|
|
11169 @section Score File Editing
|
|
|
11170
|
|
|
11171 You normally enter all scoring commands from the summary buffer, but you
|
|
|
11172 might feel the urge to edit them by hand as well, so we've supplied you
|
|
|
11173 with a mode for that.
|
|
|
11174
|
|
|
11175 It's simply a slightly customized @code{emacs-lisp} mode, with these
|
|
|
11176 additional commands:
|
|
|
11177
|
|
|
11178 @table @kbd
|
|
|
11179
|
|
|
11180 @item C-c C-c
|
|
|
11181 @kindex C-c C-c (Score)
|
|
|
11182 @findex gnus-score-edit-done
|
|
|
11183 Save the changes you have made and return to the summary buffer
|
|
|
11184 (@code{gnus-score-edit-done}).
|
|
|
11185
|
|
|
11186 @item C-c C-d
|
|
|
11187 @kindex C-c C-d (Score)
|
|
|
11188 @findex gnus-score-edit-insert-date
|
|
|
11189 Insert the current date in numerical format
|
|
|
11190 (@code{gnus-score-edit-insert-date}). This is really the day number, if
|
|
|
11191 you were wondering.
|
|
|
11192
|
|
|
11193 @item C-c C-p
|
|
|
11194 @kindex C-c C-p (Score)
|
|
|
11195 @findex gnus-score-pretty-print
|
|
|
11196 The adaptive score files are saved in an unformatted fashion. If you
|
|
|
11197 intend to read one of these files, you want to @dfn{pretty print} it
|
|
|
11198 first. This command (@code{gnus-score-pretty-print}) does that for
|
|
|
11199 you.
|
|
|
11200
|
|
|
11201 @end table
|
|
|
11202
|
|
|
11203 Type @kbd{M-x gnus-score-mode} to use this mode.
|
|
|
11204
|
|
|
11205 @vindex gnus-score-mode-hook
|
|
|
11206 @code{gnus-score-menu-hook} is run in score mode buffers.
|
|
|
11207
|
|
|
11208 In the summary buffer you can use commands like @kbd{V f} and @kbd{V
|
|
|
11209 e} to begin editing score files.
|
|
|
11210
|
|
|
11211
|
|
|
11212 @node Adaptive Scoring
|
|
|
11213 @section Adaptive Scoring
|
|
|
11214 @cindex adaptive scoring
|
|
|
11215
|
|
|
11216 If all this scoring is getting you down, Gnus has a way of making it all
|
|
|
11217 happen automatically---as if by magic. Or rather, as if by artificial
|
|
|
11218 stupidity, to be precise.
|
|
|
11219
|
|
|
11220 @vindex gnus-use-adaptive-scoring
|
|
|
11221 When you read an article, or mark an article as read, or kill an
|
|
|
11222 article, you leave marks behind. On exit from the group, Gnus can sniff
|
|
|
11223 these marks and add score elements depending on what marks it finds.
|
|
|
11224 You turn on this ability by setting @code{gnus-use-adaptive-scoring} to
|
|
16
|
11225 @code{t} or @code{(line)}. If you want score adaptively on separate
|
|
|
11226 words appearing in the subjects, you should set this variable to
|
|
|
11227 @code{(word)}. If you want to use both adaptive methods, set this
|
|
|
11228 variable to @code{(word line)}.
|
|
0
|
11229
|
|
|
11230 @vindex gnus-default-adaptive-score-alist
|
|
|
11231 To give you complete control over the scoring process, you can customize
|
|
|
11232 the @code{gnus-default-adaptive-score-alist} variable. For instance, it
|
|
|
11233 might look something like this:
|
|
|
11234
|
|
|
11235 @lisp
|
|
|
11236 (defvar gnus-default-adaptive-score-alist
|
|
|
11237 '((gnus-unread-mark)
|
|
|
11238 (gnus-ticked-mark (from 4))
|
|
|
11239 (gnus-dormant-mark (from 5))
|
|
|
11240 (gnus-del-mark (from -4) (subject -1))
|
|
|
11241 (gnus-read-mark (from 4) (subject 2))
|
|
|
11242 (gnus-expirable-mark (from -1) (subject -1))
|
|
|
11243 (gnus-killed-mark (from -1) (subject -3))
|
|
|
11244 (gnus-kill-file-mark)
|
|
|
11245 (gnus-ancient-mark)
|
|
|
11246 (gnus-low-score-mark)
|
|
|
11247 (gnus-catchup-mark (from -1) (subject -1))))
|
|
|
11248 @end lisp
|
|
|
11249
|
|
|
11250 As you see, each element in this alist has a mark as a key (either a
|
|
|
11251 variable name or a ``real'' mark---a character). Following this key is
|
|
|
11252 a arbitrary number of header/score pairs. If there are no header/score
|
|
|
11253 pairs following the key, no adaptive scoring will be done on articles
|
|
|
11254 that have that key as the article mark. For instance, articles with
|
|
|
11255 @code{gnus-unread-mark} in the example above will not get adaptive score
|
|
|
11256 entries.
|
|
|
11257
|
|
|
11258 Each article can have only one mark, so just a single of these rules
|
|
|
11259 will be applied to each article.
|
|
|
11260
|
|
|
11261 To take @code{gnus-del-mark} as an example---this alist says that all
|
|
|
11262 articles that have that mark (i.e., are marked with @samp{D}) will have a
|
|
|
11263 score entry added to lower based on the @code{From} header by -4, and
|
|
|
11264 lowered by @code{Subject} by -1. Change this to fit your prejudices.
|
|
|
11265
|
|
|
11266 If you have marked 10 articles with the same subject with
|
|
|
11267 @code{gnus-del-mark}, the rule for that mark will be applied ten times.
|
|
|
11268 That means that that subject will get a score of ten times -1, which
|
|
|
11269 should be, unless I'm much mistaken, -10.
|
|
|
11270
|
|
16
|
11271 If you have auto-expirable (mail) groups (@pxref{Expiring Mail}), all
|
|
|
11272 the read articles will be marked with the @samp{E} mark. This'll
|
|
|
11273 probably make adaptive scoring slightly impossible, so auto-expiring and
|
|
|
11274 adaptive scoring doesn't really mix very well.
|
|
|
11275
|
|
0
|
11276 The headers you can score on are @code{from}, @code{subject},
|
|
|
11277 @code{message-id}, @code{references}, @code{xref}, @code{lines},
|
|
|
11278 @code{chars} and @code{date}. In addition, you can score on
|
|
|
11279 @code{followup}, which will create an adaptive score entry that matches
|
|
|
11280 on the @code{References} header using the @code{Message-ID} of the
|
|
|
11281 current article, thereby matching the following thread.
|
|
|
11282
|
|
|
11283 You can also score on @code{thread}, which will try to score all
|
|
|
11284 articles that appear in a thread. @code{thread} matches uses a
|
|
|
11285 @code{Message-ID} to match on the @code{References} header of the
|
|
|
11286 article. If the match is made, the @code{Message-ID} of the article is
|
|
|
11287 added to the @code{thread} rule. (Think about it. I'd recommend two
|
|
|
11288 aspirins afterwards.)
|
|
|
11289
|
|
|
11290 If you use this scheme, you should set the score file atom @code{mark}
|
|
|
11291 to something small---like -300, perhaps, to avoid having small random
|
|
|
11292 changes result in articles getting marked as read.
|
|
|
11293
|
|
|
11294 After using adaptive scoring for a week or so, Gnus should start to
|
|
|
11295 become properly trained and enhance the authors you like best, and kill
|
|
|
11296 the authors you like least, without you having to say so explicitly.
|
|
|
11297
|
|
|
11298 You can control what groups the adaptive scoring is to be performed on
|
|
|
11299 by using the score files (@pxref{Score File Format}). This will also
|
|
|
11300 let you use different rules in different groups.
|
|
|
11301
|
|
|
11302 @vindex gnus-adaptive-file-suffix
|
|
|
11303 The adaptive score entries will be put into a file where the name is the
|
|
|
11304 group name with @code{gnus-adaptive-file-suffix} appended. The default
|
|
|
11305 is @samp{ADAPT}.
|
|
|
11306
|
|
|
11307 @vindex gnus-score-exact-adapt-limit
|
|
|
11308 When doing adaptive scoring, substring or fuzzy matching would probably
|
|
|
11309 give you the best results in most cases. However, if the header one
|
|
|
11310 matches is short, the possibility for false positives is great, so if
|
|
|
11311 the length of the match is less than
|
|
|
11312 @code{gnus-score-exact-adapt-limit}, exact matching will be used. If
|
|
|
11313 this variable is @code{nil}, exact matching will always be used to avoid
|
|
|
11314 this problem.
|
|
|
11315
|
|
16
|
11316 @vindex gnus-default-adaptive-word-score-alist
|
|
|
11317 As mentioned above, you can adapt either on individual words or entire
|
|
|
11318 headers. If you adapt on words, the
|
|
|
11319 @code{gnus-default-adaptive-word-score-alist} variable says what score
|
|
|
11320 each instance of a word should add given a mark.
|
|
|
11321
|
|
|
11322 @lisp
|
|
|
11323 (setq gnus-default-adaptive-word-score-alist
|
|
|
11324 `((,gnus-read-mark . 30)
|
|
|
11325 (,gnus-catchup-mark . -10)
|
|
|
11326 (,gnus-killed-mark . -20)
|
|
|
11327 (,gnus-del-mark . -15)))
|
|
|
11328 @end lisp
|
|
|
11329
|
|
|
11330 This is the default value. If you have adaption on words enabled, every
|
|
|
11331 word that appears in subjects of articles that are marked with
|
|
|
11332 @code{gnus-read-mark} will result in a score rule that increase the
|
|
|
11333 score with 30 points.
|
|
|
11334
|
|
|
11335 @vindex gnus-default-ignored-adaptive-words
|
|
|
11336 @vindex gnus-ignored-adaptive-words
|
|
|
11337 Words that appear in the @code{gnus-default-ignored-adaptive-words} list
|
|
|
11338 will be ignored. If you wish to add more words to be ignored, use the
|
|
|
11339 @code{gnus-ignored-adaptive-words} list instead.
|
|
|
11340
|
|
|
11341 @vindex gnus-adaptive-word-syntax-table
|
|
|
11342 When the scoring is done, @code{gnus-adaptive-word-syntax-table} is the
|
|
|
11343 syntax table in effect. It is similar to the standard syntax table, but
|
|
|
11344 it considers numbers to be non-word-constituent characters.
|
|
|
11345
|
|
|
11346 After using this scheme for a while, it might be nice to write a
|
|
|
11347 @code{gnus-psychoanalyze-user} command to go through the rules and see
|
|
|
11348 what words you like and what words you don't like. Or perhaps not.
|
|
|
11349
|
|
|
11350 Note that the adaptive word scoring thing is highly experimental and is
|
|
|
11351 likely to change in the future. Initial impressions seem to indicate
|
|
|
11352 that it's totally useless as it stands. Some more work (involving more
|
|
|
11353 rigorous statistical methods) will have to be done to make this useful.
|
|
|
11354
|
|
|
11355
|
|
|
11356 @node Home Score File
|
|
|
11357 @section Home Score File
|
|
|
11358
|
|
|
11359 The score file where new score file entries will go is called the
|
|
|
11360 @dfn{home score file}. This is normally (and by default) the score file
|
|
|
11361 for the group itself. For instance, the home score file for
|
|
|
11362 @samp{gnu.emacs.gnus} is @file{gnu.emacs.gnus.SCORE}.
|
|
|
11363
|
|
|
11364 However, this may not be what you want. It is often convenient to share
|
|
|
11365 a common home score file among many groups---all @samp{emacs} groups
|
|
|
11366 could perhaps use the same home score file.
|
|
|
11367
|
|
|
11368 @vindex gnus-home-score-file
|
|
|
11369 The variable that controls this is @code{gnus-home-score-file}. It can
|
|
|
11370 be:
|
|
|
11371
|
|
|
11372 @enumerate
|
|
|
11373 @item
|
|
|
11374 A string. Then this file will be used as the home score file for all
|
|
|
11375 groups.
|
|
|
11376
|
|
|
11377 @item
|
|
|
11378 A function. The result of this function will be used as the home score
|
|
|
11379 file. The function will be called with the name of the group as the
|
|
|
11380 parameter.
|
|
|
11381
|
|
|
11382 @item
|
|
|
11383 A list. The elements in this list can be:
|
|
|
11384
|
|
|
11385 @enumerate
|
|
|
11386 @item
|
|
|
11387 @var{(regexp file-name)}. If the @var{regexp} matches the group name,
|
|
|
11388 the @var{file-name} will will be used as the home score file.
|
|
|
11389
|
|
|
11390 @item
|
|
|
11391 A function. If the function returns non-nil, the result will be used as
|
|
|
11392 the home score file.
|
|
|
11393
|
|
|
11394 @item
|
|
|
11395 A string. Use the string as the home score file.
|
|
|
11396 @end enumerate
|
|
|
11397
|
|
|
11398 The list will be traversed from the beginning towards the end looking
|
|
|
11399 for matches.
|
|
|
11400
|
|
|
11401 @end enumerate
|
|
|
11402
|
|
|
11403 So, if you want to use just a single score file, you could say:
|
|
|
11404
|
|
|
11405 @lisp
|
|
|
11406 (setq gnus-home-score-file
|
|
|
11407 "my-total-score-file.SCORE")
|
|
|
11408 @end lisp
|
|
|
11409
|
|
|
11410 If you want to use @file{gnu.SCORE} for all @samp{gnu} groups and
|
|
|
11411 @file{rec.SCORE} for all @samp{rec} groups (and so on), you can say:
|
|
|
11412
|
|
|
11413 @lisp
|
|
|
11414 (setq gnus-home-score-file
|
|
|
11415 'gnus-hierarchial-home-score-file)
|
|
|
11416 @end lisp
|
|
|
11417
|
|
|
11418 This is a ready-made function provided for your convenience.
|
|
|
11419
|
|
|
11420 If you want to have one score file for the @samp{emacs} groups and
|
|
|
11421 another for the @samp{comp} groups, while letting all other groups use
|
|
|
11422 their own home score files:
|
|
|
11423
|
|
|
11424 @lisp
|
|
|
11425 (setq gnus-home-score-file
|
|
|
11426 ;; All groups that match the regexp "\\.emacs"
|
|
|
11427 '("\\.emacs" "emacs.SCORE")
|
|
|
11428 ;; All the comp groups in one score file
|
|
|
11429 ("^comp" "comp.SCORE"))
|
|
|
11430 @end lisp
|
|
|
11431
|
|
|
11432 @vindex gnus-home-adapt-file
|
|
|
11433 @code{gnus-home-adapt-file} works exactly the same way as
|
|
|
11434 @code{gnus-home-score-file}, but says what the home adaptive score file
|
|
|
11435 is instead. All new adaptive file entries will go into the file
|
|
|
11436 specified by this variable, and the same syntax is allowed.
|
|
|
11437
|
|
|
11438 In addition to using @code{gnus-home-score-file} and
|
|
|
11439 @code{gnus-home-adapt-file}, you can also use group parameters
|
|
|
11440 (@pxref{Group Parameters}) and topic parameters (@pxref{Topic
|
|
|
11441 Parameters}) to achieve much the same. Group and topic parameters take
|
|
|
11442 precedence over this variable.
|
|
|
11443
|
|
0
|
11444
|
|
|
11445 @node Followups To Yourself
|
|
|
11446 @section Followups To Yourself
|
|
|
11447
|
|
|
11448 Gnus offers two commands for picking out the @code{Message-ID} header in
|
|
|
11449 the current buffer. Gnus will then add a score rule that scores using
|
|
|
11450 this @code{Message-ID} on the @code{References} header of other
|
|
|
11451 articles. This will, in effect, increase the score of all articles that
|
|
|
11452 respond to the article in the current buffer. Quite useful if you want
|
|
|
11453 to easily note when people answer what you've said.
|
|
|
11454
|
|
|
11455 @table @code
|
|
|
11456
|
|
|
11457 @item gnus-score-followup-article
|
|
|
11458 @findex gnus-score-followup-article
|
|
|
11459 This will add a score to articles that directly follow up your own
|
|
|
11460 article.
|
|
|
11461
|
|
|
11462 @item gnus-score-followup-thread
|
|
|
11463 @findex gnus-score-followup-thread
|
|
|
11464 This will add a score to all articles that appear in a thread ``below''
|
|
|
11465 your own article.
|
|
|
11466 @end table
|
|
|
11467
|
|
16
|
11468 @vindex message-sent-hook
|
|
0
|
11469 These two functions are both primarily meant to be used in hooks like
|
|
16
|
11470 @code{message-sent-hook}.
|
|
|
11471
|
|
|
11472 If you look closely at your own @code{Message-ID}, you'll notice that
|
|
|
11473 the first two or three characters are always the same. Here's two of
|
|
|
11474 mine:
|
|
|
11475
|
|
|
11476 @example
|
|
|
11477 <x6u3u47icf.fsf@@eyesore.no>
|
|
|
11478 <x6sp9o7ibw.fsf@@eyesore.no>
|
|
|
11479 @end example
|
|
|
11480
|
|
|
11481 So ``my'' ident on this machine is @samp{x6}. This can be
|
|
|
11482 exploited---the following rule will raise the score on all followups to
|
|
|
11483 myself:
|
|
|
11484
|
|
|
11485 @lisp
|
|
|
11486 ("references"
|
|
26
|
11487 ("<x6[0-9a-z]+\\.fsf@@.*eyesore.no>" 1000 nil r))
|
|
16
|
11488 @end lisp
|
|
|
11489
|
|
|
11490 Whether it's the first two or first three characters that are ``yours''
|
|
|
11491 is system-dependent.
|
|
|
11492
|
|
0
|
11493
|
|
|
11494 @node Scoring Tips
|
|
|
11495 @section Scoring Tips
|
|
|
11496 @cindex scoring tips
|
|
|
11497
|
|
|
11498 @table @dfn
|
|
|
11499
|
|
|
11500 @item Crossposts
|
|
|
11501 @cindex crossposts
|
|
|
11502 @cindex scoring crossposts
|
|
|
11503 If you want to lower the score of crossposts, the line to match on is
|
|
|
11504 the @code{Xref} header.
|
|
|
11505 @lisp
|
|
|
11506 ("xref" (" talk.politics.misc:" -1000))
|
|
|
11507 @end lisp
|
|
|
11508
|
|
|
11509 @item Multiple crossposts
|
|
|
11510 If you want to lower the score of articles that have been crossposted to
|
|
|
11511 more than, say, 3 groups:
|
|
|
11512 @lisp
|
|
|
11513 ("xref" ("[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+" -1000 nil r))
|
|
|
11514 @end lisp
|
|
|
11515
|
|
|
11516 @item Matching on the body
|
|
|
11517 This is generally not a very good idea---it takes a very long time.
|
|
|
11518 Gnus actually has to fetch each individual article from the server. But
|
|
|
11519 you might want to anyway, I guess. Even though there are three match
|
|
|
11520 keys (@code{Head}, @code{Body} and @code{All}), you should choose one
|
|
|
11521 and stick with it in each score file. If you use any two, each article
|
|
|
11522 will be fetched @emph{twice}. If you want to match a bit on the
|
|
|
11523 @code{Head} and a bit on the @code{Body}, just use @code{All} for all
|
|
|
11524 the matches.
|
|
|
11525
|
|
|
11526 @item Marking as read
|
|
|
11527 You will probably want to mark articles that has a score below a certain
|
|
|
11528 number as read. This is most easily achieved by putting the following
|
|
|
11529 in your @file{all.SCORE} file:
|
|
|
11530 @lisp
|
|
|
11531 ((mark -100))
|
|
|
11532 @end lisp
|
|
|
11533 You may also consider doing something similar with @code{expunge}.
|
|
|
11534
|
|
|
11535 @item Negated character classes
|
|
|
11536 If you say stuff like @code{[^abcd]*}, you may get unexpected results.
|
|
|
11537 That will match newlines, which might lead to, well, The Unknown. Say
|
|
|
11538 @code{[^abcd\n]*} instead.
|
|
|
11539 @end table
|
|
|
11540
|
|
|
11541
|
|
|
11542 @node Reverse Scoring
|
|
|
11543 @section Reverse Scoring
|
|
|
11544 @cindex reverse scoring
|
|
|
11545
|
|
|
11546 If you want to keep just articles that have @samp{Sex with Emacs} in the
|
|
|
11547 subject header, and expunge all other articles, you could put something
|
|
|
11548 like this in your score file:
|
|
|
11549
|
|
|
11550 @lisp
|
|
|
11551 (("subject"
|
|
|
11552 ("Sex with Emacs" 2))
|
|
|
11553 (mark 1)
|
|
|
11554 (expunge 1))
|
|
|
11555 @end lisp
|
|
|
11556
|
|
|
11557 So, you raise all articles that match @samp{Sex with Emacs} and mark the
|
|
|
11558 rest as read, and expunge them to boot.
|
|
|
11559
|
|
|
11560
|
|
|
11561 @node Global Score Files
|
|
|
11562 @section Global Score Files
|
|
|
11563 @cindex global score files
|
|
|
11564
|
|
|
11565 Sure, other newsreaders have ``global kill files''. These are usually
|
|
|
11566 nothing more than a single kill file that applies to all groups, stored
|
|
|
11567 in the user's home directory. Bah! Puny, weak newsreaders!
|
|
|
11568
|
|
|
11569 What I'm talking about here are Global Score Files. Score files from
|
|
|
11570 all over the world, from users everywhere, uniting all nations in one
|
|
|
11571 big, happy score file union! Ange-score! New and untested!
|
|
|
11572
|
|
|
11573 @vindex gnus-global-score-files
|
|
|
11574 All you have to do to use other people's score files is to set the
|
|
|
11575 @code{gnus-global-score-files} variable. One entry for each score file,
|
|
|
11576 or each score file directory. Gnus will decide by itself what score
|
|
|
11577 files are applicable to which group.
|
|
|
11578
|
|
16
|
11579 Say you want to use the score file
|
|
|
11580 @file{/ftp@@ftp.ifi.uio.no:/pub/larsi/ding/score/soc.motss.SCORE} and
|
|
|
11581 all score files in the @file{/ftp@@ftp.some-where:/pub/score} directory:
|
|
0
|
11582
|
|
|
11583 @lisp
|
|
|
11584 (setq gnus-global-score-files
|
|
|
11585 '("/ftp@@ftp.ifi.uio.no:/pub/larsi/ding/score/soc.motss.SCORE"
|
|
|
11586 "/ftp@@ftp.some-where:/pub/score/"))
|
|
|
11587 @end lisp
|
|
|
11588
|
|
|
11589 @findex gnus-score-search-global-directories
|
|
|
11590 Simple, eh? Directory names must end with a @samp{/}. These
|
|
|
11591 directories are typically scanned only once during each Gnus session.
|
|
|
11592 If you feel the need to manually re-scan the remote directories, you can
|
|
|
11593 use the @code{gnus-score-search-global-directories} command.
|
|
|
11594
|
|
|
11595 Note that, at present, using this option will slow down group entry
|
|
|
11596 somewhat. (That is---a lot.)
|
|
|
11597
|
|
|
11598 If you want to start maintaining score files for other people to use,
|
|
|
11599 just put your score file up for anonymous ftp and announce it to the
|
|
|
11600 world. Become a retro-moderator! Participate in the retro-moderator
|
|
|
11601 wars sure to ensue, where retro-moderators battle it out for the
|
|
|
11602 sympathy of the people, luring them to use their score files on false
|
|
|
11603 premises! Yay! The net is saved!
|
|
|
11604
|
|
|
11605 Here are some tips for the would-be retro-moderator, off the top of my
|
|
|
11606 head:
|
|
|
11607
|
|
|
11608 @itemize @bullet
|
|
|
11609
|
|
|
11610 @item
|
|
|
11611 Articles that are heavily crossposted are probably junk.
|
|
|
11612 @item
|
|
|
11613 To lower a single inappropriate article, lower by @code{Message-ID}.
|
|
|
11614 @item
|
|
|
11615 Particularly brilliant authors can be raised on a permanent basis.
|
|
|
11616 @item
|
|
|
11617 Authors that repeatedly post off-charter for the group can safely be
|
|
|
11618 lowered out of existence.
|
|
|
11619 @item
|
|
|
11620 Set the @code{mark} and @code{expunge} atoms to obliterate the nastiest
|
|
|
11621 articles completely.
|
|
|
11622
|
|
|
11623 @item
|
|
|
11624 Use expiring score entries to keep the size of the file down. You
|
|
|
11625 should probably have a long expiry period, though, as some sites keep
|
|
|
11626 old articles for a long time.
|
|
|
11627 @end itemize
|
|
|
11628
|
|
|
11629 ... I wonder whether other newsreaders will support global score files
|
|
|
11630 in the future. @emph{Snicker}. Yup, any day now, newsreaders like Blue
|
|
|
11631 Wave, xrn and 1stReader are bound to implement scoring. Should we start
|
|
|
11632 holding our breath yet?
|
|
|
11633
|
|
|
11634
|
|
|
11635 @node Kill Files
|
|
|
11636 @section Kill Files
|
|
|
11637 @cindex kill files
|
|
|
11638
|
|
|
11639 Gnus still supports those pesky old kill files. In fact, the kill file
|
|
|
11640 entries can now be expiring, which is something I wrote before Daniel
|
|
|
11641 Quinlan thought of doing score files, so I've left the code in there.
|
|
|
11642
|
|
|
11643 In short, kill processing is a lot slower (and I do mean @emph{a lot})
|
|
|
11644 than score processing, so it might be a good idea to rewrite your kill
|
|
|
11645 files into score files.
|
|
|
11646
|
|
|
11647 Anyway, a kill file is a normal @code{emacs-lisp} file. You can put any
|
|
|
11648 forms into this file, which means that you can use kill files as some
|
|
|
11649 sort of primitive hook function to be run on group entry, even though
|
|
|
11650 that isn't a very good idea.
|
|
|
11651
|
|
16
|
11652 Normal kill files look like this:
|
|
0
|
11653
|
|
|
11654 @lisp
|
|
|
11655 (gnus-kill "From" "Lars Ingebrigtsen")
|
|
|
11656 (gnus-kill "Subject" "ding")
|
|
|
11657 (gnus-expunge "X")
|
|
|
11658 @end lisp
|
|
|
11659
|
|
|
11660 This will mark every article written by me as read, and remove them from
|
|
|
11661 the summary buffer. Very useful, you'll agree.
|
|
|
11662
|
|
|
11663 Other programs use a totally different kill file syntax. If Gnus
|
|
|
11664 encounters what looks like a @code{rn} kill file, it will take a stab at
|
|
|
11665 interpreting it.
|
|
|
11666
|
|
|
11667 Two summary functions for editing a GNUS kill file:
|
|
|
11668
|
|
|
11669 @table @kbd
|
|
|
11670
|
|
|
11671 @item M-k
|
|
|
11672 @kindex M-k (Summary)
|
|
|
11673 @findex gnus-summary-edit-local-kill
|
|
|
11674 Edit this group's kill file (@code{gnus-summary-edit-local-kill}).
|
|
|
11675
|
|
|
11676 @item M-K
|
|
|
11677 @kindex M-K (Summary)
|
|
|
11678 @findex gnus-summary-edit-global-kill
|
|
|
11679 Edit the general kill file (@code{gnus-summary-edit-global-kill}).
|
|
|
11680 @end table
|
|
|
11681
|
|
|
11682 Two group mode functions for editing the kill files:
|
|
|
11683
|
|
|
11684 @table @kbd
|
|
|
11685
|
|
|
11686 @item M-k
|
|
|
11687 @kindex M-k (Group)
|
|
|
11688 @findex gnus-group-edit-local-kill
|
|
|
11689 Edit this group's kill file (@code{gnus-group-edit-local-kill}).
|
|
|
11690
|
|
|
11691 @item M-K
|
|
|
11692 @kindex M-K (Group)
|
|
|
11693 @findex gnus-group-edit-global-kill
|
|
|
11694 Edit the general kill file (@code{gnus-group-edit-global-kill}).
|
|
|
11695 @end table
|
|
|
11696
|
|
|
11697 Kill file variables:
|
|
|
11698
|
|
|
11699 @table @code
|
|
|
11700 @item gnus-kill-file-name
|
|
|
11701 @vindex gnus-kill-file-name
|
|
|
11702 A kill file for the group @samp{soc.motss} is normally called
|
|
|
11703 @file{soc.motss.KILL}. The suffix appended to the group name to get
|
|
|
11704 this file name is detailed by the @code{gnus-kill-file-name} variable.
|
|
|
11705 The ``global'' kill file (not in the score file sense of ``global'', of
|
|
|
11706 course) is called just @file{KILL}.
|
|
|
11707
|
|
|
11708 @vindex gnus-kill-save-kill-file
|
|
|
11709 @item gnus-kill-save-kill-file
|
|
|
11710 If this variable is non-@code{nil}, Gnus will save the
|
|
|
11711 kill file after processing, which is necessary if you use expiring
|
|
|
11712 kills.
|
|
|
11713
|
|
|
11714 @item gnus-apply-kill-hook
|
|
|
11715 @vindex gnus-apply-kill-hook
|
|
|
11716 @findex gnus-apply-kill-file-unless-scored
|
|
|
11717 @findex gnus-apply-kill-file
|
|
|
11718 A hook called to apply kill files to a group. It is
|
|
|
11719 @code{(gnus-apply-kill-file)} by default. If you want to ignore the
|
|
|
11720 kill file if you have a score file for the same group, you can set this
|
|
|
11721 hook to @code{(gnus-apply-kill-file-unless-scored)}. If you don't want
|
|
|
11722 kill files to be processed, you should set this variable to @code{nil}.
|
|
|
11723
|
|
|
11724 @item gnus-kill-file-mode-hook
|
|
|
11725 @vindex gnus-kill-file-mode-hook
|
|
|
11726 A hook called in kill-file mode buffers.
|
|
|
11727
|
|
|
11728 @end table
|
|
|
11729
|
|
|
11730
|
|
16
|
11731 @node Converting Kill Files
|
|
|
11732 @section Converting Kill Files
|
|
|
11733 @cindex kill files
|
|
|
11734 @cindex converting kill files
|
|
|
11735
|
|
|
11736 If you have loads of old kill files, you may want to convert them into
|
|
|
11737 score files. If they are ``regular'', you can use
|
|
|
11738 the @file{gnus-kill-to-score.el} package; if not, you'll have to do it
|
|
|
11739 by hand.
|
|
|
11740
|
|
|
11741 The kill to score conversion package isn't included in Gnus by default.
|
|
|
11742 You can fetch it from
|
|
|
11743 @file{http://www.ifi.uio.no/~larsi/ding-other/gnus-kill-to-score}.
|
|
|
11744
|
|
|
11745 If your old kill files are very complex---if they contain more
|
|
|
11746 non-@code{gnus-kill} forms than not, you'll have to convert them by
|
|
|
11747 hand. Or just let them be as they are. Gnus will still use them as
|
|
|
11748 before.
|
|
|
11749
|
|
|
11750
|
|
0
|
11751 @node GroupLens
|
|
|
11752 @section GroupLens
|
|
|
11753 @cindex GroupLens
|
|
|
11754
|
|
|
11755 GroupLens is a collaborative filtering system that helps you work
|
|
|
11756 together with other people to find the quality news articles out of the
|
|
|
11757 huge volume of news articles generated every day.
|
|
|
11758
|
|
|
11759 To accomplish this the GroupLens system combines your opinions about
|
|
|
11760 articles you have already read with the opinions of others who have done
|
|
|
11761 likewise and gives you a personalized prediction for each unread news
|
|
|
11762 article. Think of GroupLens as a matchmaker. GroupLens watches how you
|
|
|
11763 rate articles, and finds other people that rate articles the same way.
|
|
|
11764 Once it has found for you some people you agree with it tells you, in
|
|
|
11765 the form of a prediction, what they thought of the article. You can use
|
|
|
11766 this prediction to help you decide whether or not you want to read the
|
|
|
11767 article.
|
|
|
11768
|
|
|
11769 @menu
|
|
|
11770 * Using GroupLens:: How to make Gnus use GroupLens.
|
|
|
11771 * Rating Articles:: Letting GroupLens know how you rate articles.
|
|
|
11772 * Displaying Predictions:: Displaying predictions given by GroupLens.
|
|
|
11773 * GroupLens Variables:: Customizing GroupLens.
|
|
|
11774 @end menu
|
|
|
11775
|
|
|
11776
|
|
|
11777 @node Using GroupLens
|
|
|
11778 @subsection Using GroupLens
|
|
|
11779
|
|
|
11780 To use GroupLens you must register a pseudonym with your local Better
|
|
16
|
11781 Bit Bureau (BBB).
|
|
|
11782 @samp{http://www.cs.umn.edu/Research/GroupLens/bbb.html} is the only
|
|
|
11783 better bit in town is at the moment.
|
|
0
|
11784
|
|
|
11785 Once you have registered you'll need to set a couple of variables.
|
|
|
11786
|
|
|
11787 @table @code
|
|
|
11788
|
|
|
11789 @item gnus-use-grouplens
|
|
|
11790 @vindex gnus-use-grouplens
|
|
|
11791 Setting this variable to a non-@code{nil} value will make Gnus hook into
|
|
|
11792 all the relevant GroupLens functions.
|
|
|
11793
|
|
|
11794 @item grouplens-pseudonym
|
|
|
11795 @vindex grouplens-pseudonym
|
|
16
|
11796 This variable should be set to the pseudonym you got when registering
|
|
0
|
11797 with the Better Bit Bureau.
|
|
|
11798
|
|
|
11799 @item grouplens-newsgroups
|
|
|
11800 @vindex grouplens-newsgroups
|
|
|
11801 A list of groups that you want to get GroupLens predictions for.
|
|
|
11802
|
|
|
11803 @end table
|
|
|
11804
|
|
|
11805 Thats the minimum of what you need to get up and running with GroupLens.
|
|
|
11806 Once you've registered, GroupLens will start giving you scores for
|
|
|
11807 articles based on the average of what other people think. But, to get
|
|
|
11808 the real benefit of GroupLens you need to start rating articles
|
|
|
11809 yourself. Then the scores GroupLens gives you will be personalized for
|
|
|
11810 you, based on how the people you usually agree with have already rated.
|
|
|
11811
|
|
|
11812
|
|
|
11813 @node Rating Articles
|
|
|
11814 @subsection Rating Articles
|
|
|
11815
|
|
|
11816 In GroupLens, an article is rated on a scale from 1 to 5, inclusive.
|
|
|
11817 Where 1 means something like this article is a waste of bandwidth and 5
|
|
|
11818 means that the article was really good. The basic question to ask
|
|
|
11819 yourself is, "on a scale from 1 to 5 would I like to see more articles
|
|
|
11820 like this one?"
|
|
|
11821
|
|
|
11822 There are four ways to enter a rating for an article in GroupLens.
|
|
|
11823
|
|
|
11824 @table @kbd
|
|
|
11825
|
|
|
11826 @item r
|
|
|
11827 @kindex r (GroupLens)
|
|
|
11828 @findex bbb-summary-rate-article
|
|
|
11829 This function will prompt you for a rating on a scale of one to five.
|
|
|
11830
|
|
|
11831 @item k
|
|
|
11832 @kindex k (GroupLens)
|
|
|
11833 @findex grouplens-score-thread
|
|
|
11834 This function will prompt you for a rating, and rate all the articles in
|
|
|
11835 the thread. This is really useful for some of those long running giant
|
|
|
11836 threads in rec.humor.
|
|
|
11837
|
|
|
11838 @end table
|
|
|
11839
|
|
|
11840 The next two commands, @kbd{n} and @kbd{,} take a numerical prefix to be
|
|
|
11841 the score of the article you're reading.
|
|
|
11842
|
|
|
11843 @table @kbd
|
|
|
11844
|
|
|
11845 @item 1-5 n
|
|
|
11846 @kindex n (GroupLens)
|
|
|
11847 @findex grouplens-next-unread-article
|
|
|
11848 Rate the article and go to the next unread article.
|
|
|
11849
|
|
|
11850 @item 1-5 ,
|
|
|
11851 @kindex , (GroupLens)
|
|
|
11852 @findex grouplens-best-unread-article
|
|
|
11853 Rate the article and go to the next unread article with the highest score.
|
|
|
11854
|
|
|
11855 @end table
|
|
|
11856
|
|
|
11857 If you want to give the current article a score of 4 and then go to the
|
|
|
11858 next article, just type @kbd{4 n}.
|
|
|
11859
|
|
|
11860
|
|
|
11861 @node Displaying Predictions
|
|
|
11862 @subsection Displaying Predictions
|
|
|
11863
|
|
|
11864 GroupLens makes a prediction for you about how much you will like a
|
|
|
11865 news article. The predictions from GroupLens are on a scale from 1 to
|
|
|
11866 5, where 1 is the worst and 5 is the best. You can use the predictions
|
|
|
11867 from GroupLens in one of three ways controlled by the variable
|
|
|
11868 @code{gnus-grouplens-override-scoring}.
|
|
|
11869
|
|
|
11870 @vindex gnus-grouplens-override-scoring
|
|
|
11871 There are three ways to display predictions in grouplens. You may
|
|
|
11872 choose to have the GroupLens scores contribute to, or override the
|
|
|
11873 regular gnus scoring mechanism. override is the default; however, some
|
|
|
11874 people prefer to see the Gnus scores plus the grouplens scores. To get
|
|
|
11875 the separate scoring behavior you need to set
|
|
|
11876 @code{gnus-grouplens-override-scoring} to @code{'separate}. To have the
|
|
|
11877 GroupLens predictions combined with the grouplens scores set it to
|
|
|
11878 @code{'override} and to combine the scores set
|
|
|
11879 @code{gnus-grouplens-override-scoring} to @code{'combine}. When you use
|
|
|
11880 the combine option you will also want to set the values for
|
|
|
11881 @code{grouplens-prediction-offset} and
|
|
|
11882 @code{grouplens-score-scale-factor}.
|
|
|
11883
|
|
|
11884 @vindex grouplens-prediction-display
|
|
|
11885 In either case, GroupLens gives you a few choices for how you would like
|
|
|
11886 to see your predictions displayed. The display of predictions is
|
|
|
11887 controlled by the @code{grouplens-prediction-display} variable.
|
|
|
11888
|
|
|
11889 The following are legal values for that variable.
|
|
|
11890
|
|
|
11891 @table @code
|
|
|
11892 @item prediction-spot
|
|
|
11893 The higher the prediction, the further to the right an @samp{*} is
|
|
|
11894 displayed.
|
|
|
11895
|
|
|
11896 @item confidence-interval
|
|
|
11897 A numeric confidence interval.
|
|
|
11898
|
|
|
11899 @item prediction-bar
|
|
|
11900 The higher the prediction, the longer the bar.
|
|
|
11901
|
|
|
11902 @item confidence-bar
|
|
|
11903 Numerical confidence.
|
|
|
11904
|
|
|
11905 @item confidence-spot
|
|
|
11906 The spot gets bigger with more confidence.
|
|
|
11907
|
|
|
11908 @item prediction-num
|
|
|
11909 Plain-old numeric value.
|
|
|
11910
|
|
|
11911 @item confidence-plus-minus
|
|
|
11912 Prediction +/i confidence.
|
|
|
11913
|
|
|
11914 @end table
|
|
|
11915
|
|
|
11916
|
|
|
11917 @node GroupLens Variables
|
|
|
11918 @subsection GroupLens Variables
|
|
|
11919
|
|
|
11920 @table @code
|
|
|
11921
|
|
|
11922 @item gnus-summary-grouplens-line-format
|
|
|
11923 The summary line format used in summary buffers that are GroupLens
|
|
|
11924 enhanced. It accepts the same specs as the normal summary line format
|
|
|
11925 (@pxref{Summary Buffer Lines}). The default is
|
|
|
11926 @samp{%U%R%z%l%I%(%[%4L: %-20,20n%]%) %s\n}.
|
|
|
11927
|
|
|
11928 @item grouplens-bbb-host
|
|
16
|
11929 Host running the bbbd server. @samp{grouplens.cs.umn.edu} is the
|
|
|
11930 default.
|
|
0
|
11931
|
|
|
11932 @item grouplens-bbb-port
|
|
|
11933 Port of the host running the bbbd server. The default is 9000.
|
|
|
11934
|
|
|
11935 @item grouplens-score-offset
|
|
|
11936 Offset the prediction by this value. In other words, subtract the
|
|
|
11937 prediction value by this number to arrive at the effective score. The
|
|
|
11938 default is 0.
|
|
|
11939
|
|
|
11940 @item grouplens-score-scale-factor
|
|
|
11941 This variable allows the user to magnify the effect of GroupLens scores.
|
|
|
11942 The scale factor is applied after the offset. The default is 1.
|
|
|
11943
|
|
|
11944 @end table
|
|
|
11945
|
|
|
11946
|
|
16
|
11947 @node Advanced Scoring
|
|
|
11948 @section Advanced Scoring
|
|
|
11949
|
|
|
11950 Scoring on Subjects and From headers is nice enough, but what if you're
|
|
|
11951 really interested in what a person has to say only when she's talking
|
|
|
11952 about a particular subject? Or what about if you really don't want to
|
|
|
11953 read what person A has to say when she's following up to person B, but
|
|
|
11954 want to read what she says when she's following up to person C?
|
|
|
11955
|
|
|
11956 By using advanced scoring rules you may create arbitrarily complex
|
|
|
11957 scoring patterns.
|
|
|
11958
|
|
|
11959 @menu
|
|
|
11960 * Advanced Scoring Syntax:: A definition.
|
|
|
11961 * Advanced Scoring Examples:: What they look like.
|
|
|
11962 * Advanced Scoring Tips:: Getting the most out of it.
|
|
|
11963 @end menu
|
|
|
11964
|
|
|
11965
|
|
|
11966 @node Advanced Scoring Syntax
|
|
|
11967 @subsection Advanced Scoring Syntax
|
|
|
11968
|
|
|
11969 Ordinary scoring rules have a string as the first element in the rule.
|
|
|
11970 Advanced scoring rules have a list as the first element. The second
|
|
|
11971 element is the score to be applied if the first element evaluated to a
|
|
|
11972 non-@code{nil} value.
|
|
|
11973
|
|
|
11974 These lists may consist of three logical operators, one redirection
|
|
|
11975 operator, and various match operators.
|
|
|
11976
|
|
|
11977 Logical operators:
|
|
|
11978
|
|
|
11979 @table @code
|
|
|
11980 @item &
|
|
|
11981 @itemx and
|
|
|
11982 This logical operator will evaluate each of its arguments until it finds
|
|
|
11983 one that evaluates to @code{false}, and then it'll stop. If all arguments
|
|
|
11984 evaluate to @code{true} values, then this operator will return
|
|
|
11985 @code{true}.
|
|
|
11986
|
|
|
11987 @item |
|
|
|
11988 @itemx or
|
|
|
11989 This logical operator will evaluate each of its arguments until it finds
|
|
|
11990 one that evaluates to @code{true}. If no arguments are @code{true},
|
|
|
11991 then this operator will return @code{false}.
|
|
|
11992
|
|
|
11993 @item !
|
|
|
11994 @itemx not
|
|
|
11995 @itemx ¬
|
|
|
11996 This logical operator only takes a single argument. It returns the
|
|
|
11997 inverse of the value of its argument.
|
|
|
11998
|
|
|
11999 @end table
|
|
|
12000
|
|
|
12001 There is an @dfn{indirection operator} that will make its arguments
|
|
|
12002 apply to the ancestors of the current article being scored. For
|
|
|
12003 instance, @code{1-} will make score rules apply to the parent of the
|
|
|
12004 current article. @code{2-} will make score fules apply to the
|
|
|
12005 grandparent of the current article. Alternatively, you can write
|
|
|
12006 @code{^^}, where the number of @code{^}s (carets) say how far back into
|
|
|
12007 the ancestry you want to go.
|
|
|
12008
|
|
|
12009 Finally, we have the match operators. These are the ones that do the
|
|
|
12010 real work. Match operators are header name strings followed by a match
|
|
|
12011 and a match type. A typical match operator looks like @samp{("from"
|
|
|
12012 "Lars Ingebrigtsen" s)}. The header names are the same as when using
|
|
|
12013 simple scoring, and the match types are also the same.
|
|
|
12014
|
|
|
12015
|
|
|
12016 @node Advanced Scoring Examples
|
|
|
12017 @subsection Advanced Scoring Examples
|
|
|
12018
|
|
|
12019 Let's say you want to increase the score of articles written by Lars
|
|
|
12020 when he's talking about Gnus:
|
|
|
12021
|
|
|
12022 @example
|
|
|
12023 ((&
|
|
|
12024 ("from" "Lars Ingebrigtsen")
|
|
|
12025 ("subject" "Gnus"))
|
|
|
12026 1000)
|
|
|
12027 @end example
|
|
|
12028
|
|
|
12029 Quite simple, huh?
|
|
|
12030
|
|
|
12031 When he writes long articles, he sometimes has something nice to say:
|
|
|
12032
|
|
|
12033 @example
|
|
|
12034 ((&
|
|
|
12035 ("from" "Lars Ingebrigtsen")
|
|
|
12036 (|
|
|
|
12037 ("subject" "Gnus")
|
|
|
12038 ("lines" 100 >)))
|
|
|
12039 1000)
|
|
|
12040 @end example
|
|
|
12041
|
|
|
12042 However, when he responds to things written by Reig Eigil Logge, you
|
|
|
12043 really don't want to read what he's written:
|
|
|
12044
|
|
|
12045 @example
|
|
|
12046 ((&
|
|
|
12047 ("from" "Lars Ingebrigtsen")
|
|
|
12048 (1- ("from" "Reig Eigir Logge")))
|
|
|
12049 -100000)
|
|
|
12050 @end example
|
|
|
12051
|
|
|
12052 Everybody that follows up Redmondo when he writes about disappearing
|
|
|
12053 socks should have their scores raised, but only when they talk about
|
|
|
12054 white socks. However, when Lars talks about socks, it's usually not
|
|
|
12055 very interesting:
|
|
|
12056
|
|
|
12057 @example
|
|
|
12058 ((&
|
|
|
12059 (1-
|
|
|
12060 (&
|
|
|
12061 ("from" "redmondo@@.*no" r)
|
|
|
12062 ("body" "disappearing.*socks" t)))
|
|
|
12063 (! ("from" "Lars Ingebrigtsen"))
|
|
|
12064 ("body" "white.*socks"))
|
|
|
12065 1000)
|
|
|
12066 @end example
|
|
|
12067
|
|
|
12068 The possibilities are endless.
|
|
|
12069
|
|
|
12070
|
|
|
12071 @node Advanced Scoring Tips
|
|
|
12072 @subsection Advanced Scoring Tips
|
|
|
12073
|
|
|
12074 The @code{&} and @code{|} logical operators do short-circuit logic.
|
|
|
12075 That is, they stop processing their arguments when it's clear what the
|
|
|
12076 result of the operation will be. For instance, if one of the arguments
|
|
|
12077 of an @code{&} evaluates to @code{false}, there's no point in evaluating
|
|
|
12078 the rest of the arguments. This means that you should put slow matches
|
|
|
12079 (@samp{body}, @code{header}) last and quick matches (@samp{from},
|
|
|
12080 @samp{subject}) first.
|
|
|
12081
|
|
|
12082 The indirection arguments (@code{1-} and so on) will make their
|
|
|
12083 arguments work on previous generations of the thread. If you say
|
|
|
12084 something like:
|
|
|
12085
|
|
|
12086 @example
|
|
|
12087 ...
|
|
|
12088 (1-
|
|
|
12089 (1-
|
|
|
12090 ("from" "lars")))
|
|
|
12091 ...
|
|
|
12092 @end example
|
|
|
12093
|
|
|
12094 Then that means "score on the from header of the grandparent of the
|
|
|
12095 current article". An indirection is quite fast, but it's better to say:
|
|
|
12096
|
|
|
12097 @example
|
|
|
12098 (1-
|
|
|
12099 (&
|
|
|
12100 ("from" "Lars")
|
|
|
12101 ("subject" "Gnus")))
|
|
|
12102 @end example
|
|
|
12103
|
|
|
12104 than it is to say:
|
|
|
12105
|
|
|
12106 @example
|
|
|
12107 (&
|
|
|
12108 (1- ("from" "Lars"))
|
|
|
12109 (1- ("subject" "Gnus")))
|
|
|
12110 @end example
|
|
|
12111
|
|
|
12112
|
|
|
12113 @node Score Decays
|
|
|
12114 @section Score Decays
|
|
|
12115 @cindex score decays
|
|
|
12116 @cindex decays
|
|
|
12117
|
|
|
12118 You may find that your scores have a tendency to grow without
|
|
|
12119 bounds, especially if you're using adaptive scoring. If scores get too
|
|
|
12120 big, they lose all meaning---they simply max out and it's difficult to
|
|
|
12121 use them in any sensible way.
|
|
|
12122
|
|
|
12123 @vindex gnus-decay-scores
|
|
|
12124 @findex gnus-decay-score
|
|
|
12125 @vindex gnus-score-decay-function
|
|
|
12126 Gnus provides a mechanism for decaying scores to help with this problem.
|
|
|
12127 When score files are loaded and @code{gnus-decay-scores} is
|
|
|
12128 non-@code{nil}, Gnus will run the score files through the decaying
|
|
|
12129 mechanism thereby lowering the scores of all non-permanent score rules.
|
|
|
12130 The decay itself if performed by the @code{gnus-score-decay-function}
|
|
|
12131 function, which is @code{gnus-decay-score} by default. Here's the
|
|
|
12132 definition of that function:
|
|
|
12133
|
|
|
12134 @lisp
|
|
|
12135 (defun gnus-decay-score (score)
|
|
|
12136 (floor
|
|
|
12137 (- score
|
|
|
12138 (* (if (< score 0) 1 -1)
|
|
|
12139 (min score
|
|
|
12140 (max gnus-score-decay-constant
|
|
|
12141 (* (abs score)
|
|
|
12142 gnus-score-decay-scale)))))))
|
|
|
12143 @end lisp
|
|
|
12144
|
|
|
12145 @vindex gnus-score-decay-scale
|
|
|
12146 @vindex gnus-score-decay-constant
|
|
|
12147 @code{gnus-score-decay-constant} is 3 by default and
|
|
|
12148 @code{gnus-score-decay-scale} is 0.05. This should cause the following:
|
|
|
12149
|
|
|
12150 @enumerate
|
|
|
12151 @item
|
|
|
12152 Scores between -3 and 3 will be set to 0 when this function is called.
|
|
|
12153
|
|
|
12154 @item
|
|
|
12155 Scores with magnitudes between 3 and 60 will be shrunk by 3.
|
|
|
12156
|
|
|
12157 @item
|
|
|
12158 Scores with magnitudes greater than 60 will be shrunk by 5% of the
|
|
|
12159 score.
|
|
|
12160 @end enumerate
|
|
|
12161
|
|
|
12162 If you don't like this decay function, write your own. It is called
|
|
|
12163 with the score to be decayed as its only parameter, and it should return
|
|
|
12164 the new score, which should be an integer.
|
|
|
12165
|
|
|
12166 Gnus will try to decay scores once a day. If you haven't run Gnus for
|
|
|
12167 four days, Gnus will decay the scores four times, for instance.
|
|
|
12168
|
|
0
|
12169
|
|
|
12170 @node Various
|
|
|
12171 @chapter Various
|
|
|
12172
|
|
|
12173 @menu
|
|
|
12174 * Process/Prefix:: A convention used by many treatment commands.
|
|
|
12175 * Interactive:: Making Gnus ask you many questions.
|
|
|
12176 * Formatting Variables:: You can specify what buffers should look like.
|
|
|
12177 * Windows Configuration:: Configuring the Gnus buffer windows.
|
|
|
12178 * Compilation:: How to speed Gnus up.
|
|
|
12179 * Mode Lines:: Displaying information in the mode lines.
|
|
|
12180 * Highlighting and Menus:: Making buffers look all nice and cozy.
|
|
|
12181 * Buttons:: Get tendonitis in ten easy steps!
|
|
|
12182 * Daemons:: Gnus can do things behind your back.
|
|
|
12183 * NoCeM:: How to avoid spam and other fatty foods.
|
|
|
12184 * Picons:: How to display pictures of what your reading.
|
|
16
|
12185 * Undo:: Some actions can be undone.
|
|
|
12186 * Moderation:: What to do if you're a moderator.
|
|
|
12187 * XEmacs Enhancements:: There are more pictures and stuff under XEmacs.
|
|
26
|
12188 * Fuzzy Matching:: What's the big fuzz?
|
|
42
|
12189 * Thwarting Email Spam:: A how-to on avoiding unsolited commercial email.
|
|
0
|
12190 * Various Various:: Things that are really various.
|
|
|
12191 @end menu
|
|
|
12192
|
|
|
12193
|
|
|
12194 @node Process/Prefix
|
|
|
12195 @section Process/Prefix
|
|
|
12196 @cindex process/prefix convention
|
|
|
12197
|
|
|
12198 Many functions, among them functions for moving, decoding and saving
|
|
|
12199 articles, use what is known as the @dfn{Process/Prefix convention}.
|
|
|
12200
|
|
|
12201 This is a method for figuring out what articles that the user wants the
|
|
|
12202 command to be performed on.
|
|
|
12203
|
|
|
12204 It goes like this:
|
|
|
12205
|
|
|
12206 If the numeric prefix is N, perform the operation on the next N
|
|
|
12207 articles, starting with the current one. If the numeric prefix is
|
|
|
12208 negative, perform the operation on the previous N articles, starting
|
|
|
12209 with the current one.
|
|
|
12210
|
|
|
12211 @vindex transient-mark-mode
|
|
|
12212 If @code{transient-mark-mode} in non-@code{nil} and the region is
|
|
|
12213 active, all articles in the region will be worked upon.
|
|
|
12214
|
|
|
12215 If there is no numeric prefix, but some articles are marked with the
|
|
|
12216 process mark, perform the operation on the articles that are marked with
|
|
|
12217 the process mark.
|
|
|
12218
|
|
|
12219 If there is neither a numeric prefix nor any articles marked with the
|
|
|
12220 process mark, just perform the operation on the current article.
|
|
|
12221
|
|
|
12222 Quite simple, really, but it needs to be made clear so that surprises
|
|
|
12223 are avoided.
|
|
|
12224
|
|
16
|
12225 Commands that react to the process mark will push the current list of
|
|
|
12226 process marked articles onto a stack and will then clear all process
|
|
|
12227 marked articles. You can restore the previous configuration with the
|
|
|
12228 @kbd{M P y} command (@pxref{Setting Process Marks}).
|
|
|
12229
|
|
0
|
12230 @vindex gnus-summary-goto-unread
|
|
|
12231 One thing that seems to shock & horrify lots of people is that, for
|
|
|
12232 instance, @kbd{3 d} does exactly the same as @kbd{d} @kbd{d} @kbd{d}.
|
|
|
12233 Since each @kbd{d} (which marks the current article as read) by default
|
|
|
12234 goes to the next unread article after marking, this means that @kbd{3 d}
|
|
|
12235 will mark the next three unread articles as read, no matter what the
|
|
|
12236 summary buffer looks like. Set @code{gnus-summary-goto-unread} to
|
|
|
12237 @code{nil} for a more straightforward action.
|
|
|
12238
|
|
|
12239
|
|
|
12240 @node Interactive
|
|
|
12241 @section Interactive
|
|
|
12242 @cindex interaction
|
|
|
12243
|
|
|
12244 @table @code
|
|
|
12245
|
|
|
12246 @item gnus-novice-user
|
|
|
12247 @vindex gnus-novice-user
|
|
|
12248 If this variable is non-@code{nil}, you are either a newcomer to the
|
|
|
12249 World of Usenet, or you are very cautious, which is a nice thing to be,
|
|
|
12250 really. You will be given questions of the type ``Are you sure you want
|
|
|
12251 to do this?'' before doing anything dangerous. This is @code{t} by
|
|
|
12252 default.
|
|
|
12253
|
|
|
12254 @item gnus-expert-user
|
|
|
12255 @vindex gnus-expert-user
|
|
|
12256 If this variable is non-@code{nil}, you will never ever be asked any
|
|
|
12257 questions by Gnus. It will simply assume you know what you're doing, no
|
|
|
12258 matter how strange.
|
|
|
12259
|
|
|
12260 @item gnus-interactive-catchup
|
|
|
12261 @vindex gnus-interactive-catchup
|
|
|
12262 Require confirmation before catching up a group if non-@code{nil}. It
|
|
|
12263 is @code{t} by default.
|
|
|
12264
|
|
|
12265 @item gnus-interactive-exit
|
|
|
12266 @vindex gnus-interactive-exit
|
|
|
12267 Require confirmation before exiting Gnus. This variable is @code{t} by
|
|
|
12268 default.
|
|
|
12269 @end table
|
|
|
12270
|
|
|
12271
|
|
|
12272 @node Formatting Variables
|
|
|
12273 @section Formatting Variables
|
|
|
12274 @cindex formatting variables
|
|
|
12275
|
|
|
12276 Throughout this manual you've probably noticed lots of variables that
|
|
|
12277 are called things like @code{gnus-group-line-format} and
|
|
|
12278 @code{gnus-summary-mode-line-format}. These control how Gnus is to
|
|
|
12279 output lines in the various buffers. There's quite a lot of them.
|
|
|
12280 Fortunately, they all use the same syntax, so there's not that much to
|
|
|
12281 be annoyed by.
|
|
|
12282
|
|
|
12283 Here's an example format spec (from the group buffer): @samp{%M%S%5y:
|
|
|
12284 %(%g%)\n}. We see that it is indeed extremely ugly, and that there are
|
|
|
12285 lots of percentages everywhere.
|
|
|
12286
|
|
16
|
12287 @menu
|
|
|
12288 * Formatting Basics:: A formatting variable is basically a format string.
|
|
|
12289 * Advanced Formatting:: Modifying output in various ways.
|
|
|
12290 * User-Defined Specs:: Having Gnus call your own functions.
|
|
|
12291 * Formatting Fonts:: Making the formatting look colorful and nice.
|
|
|
12292 @end menu
|
|
|
12293
|
|
|
12294 Currently Gnus uses the following formatting variables:
|
|
|
12295 @code{gnus-group-line-format}, @code{gnus-summary-line-format},
|
|
|
12296 @code{gnus-server-line-format}, @code{gnus-topic-line-format},
|
|
|
12297 @code{gnus-group-mode-line-format},
|
|
|
12298 @code{gnus-summary-mode-line-format},
|
|
|
12299 @code{gnus-article-mode-line-format},
|
|
|
12300 @code{gnus-server-mode-line-format}, and
|
|
|
12301 @code{gnus-summary-pick-line-format}.
|
|
|
12302
|
|
|
12303 All these format variables can also be arbitrary elisp forms. In that
|
|
|
12304 case, they will be @code{eval}ed to insert the required lines.
|
|
|
12305
|
|
|
12306 @kindex M-x gnus-update-format
|
|
|
12307 @findex gnus-update-format
|
|
|
12308 Gnus includes a command to help you while creating your own format
|
|
|
12309 specs. @kbd{M-x gnus-update-format} will @code{eval} the current form,
|
|
|
12310 update the spec in question and pop you to a buffer where you can
|
|
|
12311 examine the resulting lisp code to be run to generate the line.
|
|
|
12312
|
|
|
12313
|
|
|
12314
|
|
|
12315 @node Formatting Basics
|
|
|
12316 @subsection Formatting Basics
|
|
|
12317
|
|
0
|
12318 Each @samp{%} element will be replaced by some string or other when the
|
|
|
12319 buffer in question is generated. @samp{%5y} means ``insert the @samp{y}
|
|
16
|
12320 spec, and pad with spaces to get a 5-character field''.
|
|
|
12321
|
|
|
12322 As with normal C and Emacs Lisp formatting strings, the numerical
|
|
|
12323 modifier between the @samp{%} and the formatting type character will
|
|
|
12324 @dfn{pad} the output so that it is always at least that long.
|
|
|
12325 @samp{%5y} will make the field always (at least) five characters wide by
|
|
|
12326 padding with spaces to the left. If you say @samp{%-5y}, it will pad to
|
|
|
12327 the right instead.
|
|
|
12328
|
|
|
12329 You may also wish to limit the length of the field to protect against
|
|
|
12330 particularly wide values. For that you can say @samp{%4,6y}, which
|
|
|
12331 means that the field will never be more than 6 characters wide and never
|
|
|
12332 less than 4 characters wide.
|
|
|
12333
|
|
|
12334
|
|
|
12335 @node Advanced Formatting
|
|
|
12336 @subsection Advanced Formatting
|
|
|
12337
|
|
|
12338 It is frequently useful to post-process the fields in some way.
|
|
|
12339 Padding, limiting, cutting off parts and suppressing certain values can
|
|
|
12340 be achieved by using @dfn{tilde modifiers}. A typical tilde spec might
|
|
|
12341 look like @samp{%~(cut 3)~(ignore "0")y}.
|
|
|
12342
|
|
|
12343 These are the legal modifiers:
|
|
|
12344
|
|
|
12345 @table @code
|
|
|
12346 @item pad
|
|
|
12347 @itemx pad-left
|
|
|
12348 Pad the field to the left with spaces until it reaches the required
|
|
|
12349 length.
|
|
|
12350
|
|
|
12351 @item pad-right
|
|
|
12352 Pad the field to the right with spaces until it reaches the required
|
|
|
12353 length.
|
|
|
12354
|
|
|
12355 @item max
|
|
|
12356 @itemx max-left
|
|
|
12357 Cut off characters from the left until it reaches the specified length.
|
|
|
12358
|
|
|
12359 @item max-right
|
|
|
12360 Cut off characters from the right until it reaches the specified
|
|
|
12361 length.
|
|
|
12362
|
|
|
12363 @item cut
|
|
|
12364 @itemx cut-left
|
|
|
12365 Cut off the specified number of characters from the left.
|
|
|
12366
|
|
|
12367 @item cut-right
|
|
|
12368 Cut off the specified number of characters from the right.
|
|
|
12369
|
|
|
12370 @item ignore
|
|
|
12371 Return an empty string if the field is equal to the specified value.
|
|
|
12372
|
|
|
12373 @item form
|
|
|
12374 Use the specified form as the field value when the @samp{@@} spec is
|
|
|
12375 used.
|
|
|
12376 @end table
|
|
|
12377
|
|
|
12378 Let's take an example. The @samp{%o} spec in the summary mode lines
|
|
|
12379 will return a date in compact ISO8601 format---@samp{19960809T230410}.
|
|
|
12380 This is quite a mouthful, so we want to shave off the century number and
|
|
|
12381 the time, leaving us with a six-character date. That would be
|
|
|
12382 @samp{%~(cut-left 2)~(max-right 6)~(pad 6)o}. (Cutting is done before
|
|
|
12383 maxing, and we need the padding to ensure that the date is never less
|
|
|
12384 than 6 characters to make it look nice in columns.)
|
|
|
12385
|
|
|
12386 Ignoring is done first; then cutting; then maxing; and then as the very
|
|
|
12387 last operation, padding.
|
|
|
12388
|
|
|
12389 If you use lots of these advanced thingies, you'll find that Gnus gets
|
|
|
12390 quite slow. This can be helped enormously by running @kbd{M-x
|
|
|
12391 gnus-compile} when you are satisfied with the look of your lines.
|
|
|
12392 @xref{Compilation}.
|
|
|
12393
|
|
|
12394
|
|
|
12395 @node User-Defined Specs
|
|
|
12396 @subsection User-Defined Specs
|
|
|
12397
|
|
|
12398 All the specs allow for inserting user defined specifiers---@samp{u}.
|
|
|
12399 The next character in the format string should be a letter. Gnus
|
|
|
12400 will call the function @code{gnus-user-format-function-}@samp{X}, where
|
|
|
12401 @samp{X} is the letter following @samp{%u}. The function will be passed
|
|
|
12402 a single parameter---what the parameter means depends on what buffer
|
|
|
12403 it's being called from. The function should return a string, which will
|
|
|
12404 be inserted into the buffer just like information from any other
|
|
|
12405 specifier. This function may also be called with dummy values, so it
|
|
|
12406 should protect against that.
|
|
|
12407
|
|
|
12408 You can also use tilde modifiers (@pxref{Advanced Formatting} to achieve
|
|
|
12409 much the same without defining new functions. Here's an example:
|
|
|
12410 @samp{%~(form (count-lines (point-min) (point)))@@}. The form
|
|
|
12411 given here will be evaluated to yield the current line number, and then
|
|
|
12412 inserted.
|
|
|
12413
|
|
|
12414
|
|
|
12415 @node Formatting Fonts
|
|
|
12416 @subsection Formatting Fonts
|
|
|
12417
|
|
|
12418 There are specs for highlighting, and these are shared by all the format
|
|
|
12419 variables. Text inside the @samp{%(} and @samp{%)} specifiers will get
|
|
|
12420 the special @code{mouse-face} property set, which means that it will be
|
|
|
12421 highlighted (with @code{gnus-mouse-face}) when you put the mouse pointer
|
|
|
12422 over it.
|
|
0
|
12423
|
|
|
12424 Text inside the @samp{%[} and @samp{%]} specifiers will have their
|
|
|
12425 normal faces set using @code{gnus-face-0}, which is @code{bold} by
|
|
|
12426 default. If you say @samp{%1[} instead, you'll get @code{gnus-face-1}
|
|
|
12427 instead, and so on. Create as many faces as you wish. The same goes
|
|
|
12428 for the @code{mouse-face} specs---you can say @samp{%3(hello%)} to have
|
|
|
12429 @samp{hello} mouse-highlighted with @code{gnus-mouse-face-3}.
|
|
|
12430
|
|
|
12431 Here's an alternative recipe for the group buffer:
|
|
|
12432
|
|
|
12433 @lisp
|
|
|
12434 ;; Create three face types.
|
|
|
12435 (setq gnus-face-1 'bold)
|
|
|
12436 (setq gnus-face-3 'italic)
|
|
|
12437
|
|
|
12438 ;; We want the article count to be in
|
|
|
12439 ;; a bold and green face. So we create
|
|
|
12440 ;; a new face called `my-green-bold'.
|
|
|
12441 (copy-face 'bold 'my-green-bold)
|
|
|
12442 ;; Set the color.
|
|
|
12443 (set-face-foreground 'my-green-bold "ForestGreen")
|
|
|
12444 (setq gnus-face-2 'my-green-bold)
|
|
|
12445
|
|
|
12446 ;; Set the new & fancy format.
|
|
|
12447 (setq gnus-group-line-format
|
|
|
12448 "%M%S%3@{%5y%@}%2[:%] %(%1@{%g%@}%)\n")
|
|
|
12449 @end lisp
|
|
|
12450
|
|
|
12451 I'm sure you'll be able to use this scheme to create totally unreadable
|
|
|
12452 and extremely vulgar displays. Have fun!
|
|
|
12453
|
|
|
12454 Note that the @samp{%(} specs (and friends) do not make any sense on the
|
|
|
12455 mode-line variables.
|
|
|
12456
|
|
|
12457
|
|
|
12458 @node Windows Configuration
|
|
|
12459 @section Windows Configuration
|
|
|
12460 @cindex windows configuration
|
|
|
12461
|
|
|
12462 No, there's nothing here about X, so be quiet.
|
|
|
12463
|
|
|
12464 @vindex gnus-use-full-window
|
|
|
12465 If @code{gnus-use-full-window} non-@code{nil}, Gnus will delete all
|
|
|
12466 other windows and occupy the entire Emacs screen by itself. It is
|
|
|
12467 @code{t} by default.
|
|
|
12468
|
|
|
12469 @vindex gnus-buffer-configuration
|
|
|
12470 @code{gnus-buffer-configuration} describes how much space each Gnus
|
|
|
12471 buffer should be given. Here's an excerpt of this variable:
|
|
|
12472
|
|
|
12473 @lisp
|
|
|
12474 ((group (vertical 1.0 (group 1.0 point)
|
|
|
12475 (if gnus-carpal (group-carpal 4))))
|
|
|
12476 (article (vertical 1.0 (summary 0.25 point)
|
|
|
12477 (article 1.0))))
|
|
|
12478 @end lisp
|
|
|
12479
|
|
|
12480 This is an alist. The @dfn{key} is a symbol that names some action or
|
|
|
12481 other. For instance, when displaying the group buffer, the window
|
|
|
12482 configuration function will use @code{group} as the key. A full list of
|
|
|
12483 possible names is listed below.
|
|
|
12484
|
|
16
|
12485 The @dfn{value} (i.e., the @dfn{split}) says how much space each buffer
|
|
0
|
12486 should occupy. To take the @code{article} split as an example -
|
|
|
12487
|
|
|
12488 @lisp
|
|
|
12489 (article (vertical 1.0 (summary 0.25 point)
|
|
|
12490 (article 1.0)))
|
|
|
12491 @end lisp
|
|
|
12492
|
|
|
12493 This @dfn{split} says that the summary buffer should occupy 25% of upper
|
|
|
12494 half of the screen, and that it is placed over the article buffer. As
|
|
|
12495 you may have noticed, 100% + 25% is actually 125% (yup, I saw y'all
|
|
|
12496 reaching for that calculator there). However, the special number
|
|
|
12497 @code{1.0} is used to signal that this buffer should soak up all the
|
|
|
12498 rest of the space available after the rest of the buffers have taken
|
|
|
12499 whatever they need. There should be only one buffer with the @code{1.0}
|
|
|
12500 size spec per split.
|
|
|
12501
|
|
|
12502 Point will be put in the buffer that has the optional third element
|
|
|
12503 @code{point}.
|
|
|
12504
|
|
|
12505 Here's a more complicated example:
|
|
|
12506
|
|
|
12507 @lisp
|
|
|
12508 (article (vertical 1.0 (group 4)
|
|
|
12509 (summary 0.25 point)
|
|
|
12510 (if gnus-carpal (summary-carpal 4))
|
|
|
12511 (article 1.0)))
|
|
|
12512 @end lisp
|
|
|
12513
|
|
|
12514 If the size spec is an integer instead of a floating point number,
|
|
|
12515 then that number will be used to say how many lines a buffer should
|
|
|
12516 occupy, not a percentage.
|
|
|
12517
|
|
|
12518 If the @dfn{split} looks like something that can be @code{eval}ed (to be
|
|
|
12519 precise---if the @code{car} of the split is a function or a subr), this
|
|
|
12520 split will be @code{eval}ed. If the result is non-@code{nil}, it will
|
|
|
12521 be used as a split. This means that there will be three buffers if
|
|
|
12522 @code{gnus-carpal} is @code{nil}, and four buffers if @code{gnus-carpal}
|
|
|
12523 is non-@code{nil}.
|
|
|
12524
|
|
|
12525 Not complicated enough for you? Well, try this on for size:
|
|
|
12526
|
|
|
12527 @lisp
|
|
|
12528 (article (horizontal 1.0
|
|
|
12529 (vertical 0.5
|
|
|
12530 (group 1.0)
|
|
|
12531 (gnus-carpal 4))
|
|
|
12532 (vertical 1.0
|
|
|
12533 (summary 0.25 point)
|
|
|
12534 (summary-carpal 4)
|
|
|
12535 (article 1.0))))
|
|
|
12536 @end lisp
|
|
|
12537
|
|
|
12538 Whoops. Two buffers with the mystery 100% tag. And what's that
|
|
|
12539 @code{horizontal} thingie?
|
|
|
12540
|
|
|
12541 If the first element in one of the split is @code{horizontal}, Gnus will
|
|
|
12542 split the window horizontally, giving you two windows side-by-side.
|
|
|
12543 Inside each of these strips you may carry on all you like in the normal
|
|
|
12544 fashion. The number following @code{horizontal} says what percentage of
|
|
|
12545 the screen is to be given to this strip.
|
|
|
12546
|
|
|
12547 For each split, there @emph{must} be one element that has the 100% tag.
|
|
|
12548 The splitting is never accurate, and this buffer will eat any leftover
|
|
|
12549 lines from the splits.
|
|
|
12550
|
|
|
12551 To be slightly more formal, here's a definition of what a legal split
|
|
|
12552 may look like:
|
|
|
12553
|
|
|
12554 @example
|
|
|
12555 split = frame | horizontal | vertical | buffer | form
|
|
|
12556 frame = "(frame " size *split ")"
|
|
|
12557 horizontal = "(horizontal " size *split ")"
|
|
|
12558 vertical = "(vertical " size *split ")"
|
|
|
12559 buffer = "(" buffer-name " " size *[ "point" ] ")"
|
|
|
12560 size = number | frame-params
|
|
|
12561 buffer-name = group | article | summary ...
|
|
|
12562 @end example
|
|
|
12563
|
|
|
12564 The limitations are that the @code{frame} split can only appear as the
|
|
|
12565 top-level split. @var{form} should be an Emacs Lisp form that should
|
|
|
12566 return a valid split. We see that each split is fully recursive, and
|
|
|
12567 may contain any number of @code{vertical} and @code{horizontal} splits.
|
|
|
12568
|
|
|
12569 @vindex gnus-window-min-width
|
|
|
12570 @vindex gnus-window-min-height
|
|
|
12571 @cindex window height
|
|
|
12572 @cindex window width
|
|
|
12573 Finding the right sizes can be a bit complicated. No window may be less
|
|
2
|
12574 than @code{gnus-window-min-height} (default 1) characters high, and all
|
|
0
|
12575 windows must be at least @code{gnus-window-min-width} (default 1)
|
|
|
12576 characters wide. Gnus will try to enforce this before applying the
|
|
|
12577 splits. If you want to use the normal Emacs window width/height limit,
|
|
|
12578 you can just set these two variables to @code{nil}.
|
|
|
12579
|
|
|
12580 If you're not familiar with Emacs terminology, @code{horizontal} and
|
|
|
12581 @code{vertical} splits may work the opposite way of what you'd expect.
|
|
|
12582 Windows inside a @code{horizontal} split are shown side-by-side, and
|
|
|
12583 windows within a @code{vertical} split are shown above each other.
|
|
|
12584
|
|
|
12585 @findex gnus-configure-frame
|
|
|
12586 If you want to experiment with window placement, a good tip is to call
|
|
|
12587 @code{gnus-configure-frame} directly with a split. This is the function
|
|
|
12588 that does all the real work when splitting buffers. Below is a pretty
|
|
|
12589 nonsensical configuration with 5 windows; two for the group buffer and
|
|
|
12590 three for the article buffer. (I said it was nonsensical.) If you
|
|
|
12591 @code{eval} the statement below, you can get an idea of how that would
|
|
|
12592 look straight away, without going through the normal Gnus channels.
|
|
|
12593 Play with it until you're satisfied, and then use
|
|
|
12594 @code{gnus-add-configuration} to add your new creation to the buffer
|
|
|
12595 configuration list.
|
|
|
12596
|
|
|
12597 @lisp
|
|
|
12598 (gnus-configure-frame
|
|
|
12599 '(horizontal 1.0
|
|
|
12600 (vertical 10
|
|
|
12601 (group 1.0)
|
|
|
12602 (article 0.3 point))
|
|
|
12603 (vertical 1.0
|
|
|
12604 (article 1.0)
|
|
|
12605 (horizontal 4
|
|
|
12606 (group 1.0)
|
|
|
12607 (article 10)))))
|
|
|
12608 @end lisp
|
|
|
12609
|
|
|
12610 You might want to have several frames as well. No prob---just use the
|
|
|
12611 @code{frame} split:
|
|
|
12612
|
|
|
12613 @lisp
|
|
|
12614 (gnus-configure-frame
|
|
|
12615 '(frame 1.0
|
|
|
12616 (vertical 1.0
|
|
|
12617 (summary 0.25 point)
|
|
|
12618 (article 1.0))
|
|
|
12619 (vertical ((height . 5) (width . 15)
|
|
|
12620 (user-position . t)
|
|
|
12621 (left . -1) (top . 1))
|
|
|
12622 (picon 1.0))))
|
|
|
12623
|
|
|
12624 @end lisp
|
|
|
12625
|
|
|
12626 This split will result in the familiar summary/article window
|
|
|
12627 configuration in the first (or ``main'') frame, while a small additional
|
|
|
12628 frame will be created where picons will be shown. As you can see,
|
|
|
12629 instead of the normal @code{1.0} top-level spec, each additional split
|
|
|
12630 should have a frame parameter alist as the size spec.
|
|
|
12631 @xref{Frame Parameters, , Frame Parameters, elisp, The GNU Emacs Lisp
|
|
|
12632 Reference Manual}.
|
|
|
12633
|
|
|
12634 Here's a list of all possible keys for
|
|
|
12635 @code{gnus-buffer-configuration}:
|
|
|
12636
|
|
|
12637 @code{group}, @code{summary}, @code{article}, @code{server},
|
|
2
|
12638 @code{browse}, @code{message}, @code{pick}, @code{info},
|
|
|
12639 @code{summary-faq}, @code{edit-group}, @code{edit-server},
|
|
|
12640 @code{edit-score}, @code{post}, @code{reply}, @code{forward},
|
|
24
|
12641 @code{reply-yank}, @code{mail-bounce}, @code{draft}, @code{pipe},
|
|
|
12642 @code{bug}, @code{compose-bounce}.
|
|
2
|
12643
|
|
|
12644 Note that the @code{message} key is used for both
|
|
|
12645 @code{gnus-group-mail} and @code{gnus-summary-mail-other-window}. If
|
|
16
|
12646 it is desirable to distinguish between the two, something like this
|
|
2
|
12647 might be used:
|
|
|
12648
|
|
|
12649 @lisp
|
|
|
12650 (message (horizontal 1.0
|
|
16
|
12651 (vertical 1.0 (message 1.0 point))
|
|
|
12652 (vertical 0.24
|
|
|
12653 (if (buffer-live-p gnus-summary-buffer)
|
|
|
12654 '(summary 0.5))
|
|
|
12655 (group 1.0)))))
|
|
2
|
12656 @end lisp
|
|
0
|
12657
|
|
|
12658 @findex gnus-add-configuration
|
|
|
12659 Since the @code{gnus-buffer-configuration} variable is so long and
|
|
|
12660 complicated, there's a function you can use to ease changing the config
|
|
|
12661 of a single setting: @code{gnus-add-configuration}. If, for instance,
|
|
|
12662 you want to change the @code{article} setting, you could say:
|
|
|
12663
|
|
|
12664 @lisp
|
|
|
12665 (gnus-add-configuration
|
|
|
12666 '(article (vertical 1.0
|
|
|
12667 (group 4)
|
|
|
12668 (summary .25 point)
|
|
|
12669 (article 1.0))))
|
|
|
12670 @end lisp
|
|
|
12671
|
|
|
12672 You'd typically stick these @code{gnus-add-configuration} calls in your
|
|
16
|
12673 @file{.gnus.el} file or in some startup hook---they should be run after
|
|
0
|
12674 Gnus has been loaded.
|
|
|
12675
|
|
16
|
12676 @vindex gnus-always-force-window-configuration
|
|
|
12677 If all windows mentioned in the configuration are already visible, Gnus
|
|
|
12678 won't change the window configuration. If you always want to force the
|
|
|
12679 ``right'' window configuration, you can set
|
|
|
12680 @code{gnus-always-force-window-configuration} to non-@code{nil}.
|
|
|
12681
|
|
|
12682
|
|
|
12683 @node Compilation
|
|
|
12684 @section Compilation
|
|
0
|
12685 @cindex compilation
|
|
|
12686 @cindex byte-compilation
|
|
|
12687
|
|
|
12688 @findex gnus-compile
|
|
|
12689
|
|
|
12690 Remember all those line format specification variables?
|
|
|
12691 @code{gnus-summary-line-format}, @code{gnus-group-line-format}, and so
|
|
|
12692 on. Now, Gnus will of course heed whatever these variables are, but,
|
|
|
12693 unfortunately, changing them will mean a quite significant slow-down.
|
|
|
12694 (The default values of these variables have byte-compiled functions
|
|
|
12695 associated with them, while the user-generated versions do not, of
|
|
|
12696 course.)
|
|
|
12697
|
|
|
12698 To help with this, you can run @kbd{M-x gnus-compile} after you've
|
|
|
12699 fiddled around with the variables and feel that you're (kind of)
|
|
|
12700 satisfied. This will result in the new specs being byte-compiled, and
|
|
16
|
12701 you'll get top speed again. Gnus will save these compiled specs in the
|
|
|
12702 @file{.newsrc.eld} file. (User-defined functions aren't compiled by
|
|
|
12703 this function, though---you should compile them yourself by sticking
|
|
|
12704 them into the @code{.gnus.el} file and byte-compiling that file.)
|
|
0
|
12705
|
|
|
12706
|
|
|
12707 @node Mode Lines
|
|
|
12708 @section Mode Lines
|
|
|
12709 @cindex mode lines
|
|
|
12710
|
|
|
12711 @vindex gnus-updated-mode-lines
|
|
|
12712 @code{gnus-updated-mode-lines} says what buffers should keep their mode
|
|
|
12713 lines updated. It is a list of symbols. Supported symbols include
|
|
|
12714 @code{group}, @code{article}, @code{summary}, @code{server},
|
|
|
12715 @code{browse}, and @code{tree}. If the corresponding symbol is present,
|
|
|
12716 Gnus will keep that mode line updated with information that may be
|
|
|
12717 pertinent. If this variable is @code{nil}, screen refresh may be
|
|
|
12718 quicker.
|
|
|
12719
|
|
|
12720 @cindex display-time
|
|
|
12721
|
|
|
12722 @vindex gnus-mode-non-string-length
|
|
|
12723 By default, Gnus displays information on the current article in the mode
|
|
|
12724 lines of the summary and article buffers. The information Gnus wishes
|
|
16
|
12725 to display (e.g. the subject of the article) is often longer than the
|
|
0
|
12726 mode lines, and therefore have to be cut off at some point. The
|
|
|
12727 @code{gnus-mode-non-string-length} variable says how long the other
|
|
|
12728 elements on the line is (i.e., the non-info part). If you put
|
|
16
|
12729 additional elements on the mode line (e.g. a clock), you should modify
|
|
0
|
12730 this variable:
|
|
|
12731
|
|
|
12732 @c Hook written by Francesco Potorti` <pot@cnuce.cnr.it>
|
|
|
12733 @lisp
|
|
|
12734 (add-hook 'display-time-hook
|
|
|
12735 (lambda () (setq gnus-mode-non-string-length
|
|
|
12736 (+ 21
|
|
|
12737 (if line-number-mode 5 0)
|
|
|
12738 (if column-number-mode 4 0)
|
|
|
12739 (length display-time-string)))))
|
|
|
12740 @end lisp
|
|
|
12741
|
|
|
12742 If this variable is @code{nil} (which is the default), the mode line
|
|
|
12743 strings won't be chopped off, and they won't be padded either.
|
|
18
|
12744 Note that the default is unlikely to be desirable, as even the
|
|
|
12745 percentage complete in the buffer may be crowded off the mode line;
|
|
|
12746 the user should configure this variable appropriately for their
|
|
|
12747 configuration.
|
|
0
|
12748
|
|
|
12749
|
|
|
12750 @node Highlighting and Menus
|
|
|
12751 @section Highlighting and Menus
|
|
|
12752 @cindex visual
|
|
|
12753 @cindex highlighting
|
|
|
12754 @cindex menus
|
|
|
12755
|
|
|
12756 @vindex gnus-visual
|
|
|
12757 The @code{gnus-visual} variable controls most of the prettifying Gnus
|
|
|
12758 aspects. If @code{nil}, Gnus won't attempt to create menus or use fancy
|
|
|
12759 colors or fonts. This will also inhibit loading the @file{gnus-vis.el}
|
|
|
12760 file.
|
|
|
12761
|
|
|
12762 This variable can be a list of visual properties that are enabled. The
|
|
|
12763 following elements are legal, and are all included by default:
|
|
|
12764
|
|
|
12765 @table @code
|
|
|
12766 @item group-highlight
|
|
|
12767 Do highlights in the group buffer.
|
|
|
12768 @item summary-highlight
|
|
|
12769 Do highlights in the summary buffer.
|
|
|
12770 @item article-highlight
|
|
|
12771 Do highlights in the article buffer.
|
|
|
12772 @item highlight
|
|
|
12773 Turn on highlighting in all buffers.
|
|
|
12774 @item group-menu
|
|
|
12775 Create menus in the group buffer.
|
|
|
12776 @item summary-menu
|
|
|
12777 Create menus in the summary buffers.
|
|
|
12778 @item article-menu
|
|
|
12779 Create menus in the article buffer.
|
|
|
12780 @item browse-menu
|
|
|
12781 Create menus in the browse buffer.
|
|
|
12782 @item server-menu
|
|
|
12783 Create menus in the server buffer.
|
|
|
12784 @item score-menu
|
|
|
12785 Create menus in the score buffers.
|
|
|
12786 @item menu
|
|
|
12787 Create menus in all buffers.
|
|
|
12788 @end table
|
|
|
12789
|
|
|
12790 So if you only want highlighting in the article buffer and menus in all
|
|
|
12791 buffers, you could say something like:
|
|
|
12792
|
|
|
12793 @lisp
|
|
|
12794 (setq gnus-visual '(article-highlight menu))
|
|
|
12795 @end lisp
|
|
|
12796
|
|
|
12797 If you want only highlighting and no menus whatsoever, you'd say:
|
|
|
12798
|
|
|
12799 @lisp
|
|
|
12800 (setq gnus-visual '(highlight))
|
|
|
12801 @end lisp
|
|
|
12802
|
|
|
12803 If @code{gnus-visual} is @code{t}, highlighting and menus will be used
|
|
|
12804 in all Gnus buffers.
|
|
|
12805
|
|
|
12806 Other general variables that influence the look of all buffers include:
|
|
|
12807
|
|
|
12808 @table @code
|
|
|
12809 @item gnus-mouse-face
|
|
|
12810 @vindex gnus-mouse-face
|
|
|
12811 This is the face (i.e., font) used for mouse highlighting in Gnus. No
|
|
|
12812 mouse highlights will be done if @code{gnus-visual} is @code{nil}.
|
|
|
12813
|
|
|
12814 @end table
|
|
|
12815
|
|
|
12816 There are hooks associated with the creation of all the different menus:
|
|
|
12817
|
|
|
12818 @table @code
|
|
|
12819
|
|
|
12820 @item gnus-article-menu-hook
|
|
|
12821 @vindex gnus-article-menu-hook
|
|
|
12822 Hook called after creating the article mode menu.
|
|
|
12823
|
|
|
12824 @item gnus-group-menu-hook
|
|
|
12825 @vindex gnus-group-menu-hook
|
|
|
12826 Hook called after creating the group mode menu.
|
|
|
12827
|
|
|
12828 @item gnus-summary-menu-hook
|
|
|
12829 @vindex gnus-summary-menu-hook
|
|
|
12830 Hook called after creating the summary mode menu.
|
|
|
12831
|
|
|
12832 @item gnus-server-menu-hook
|
|
|
12833 @vindex gnus-server-menu-hook
|
|
|
12834 Hook called after creating the server mode menu.
|
|
|
12835
|
|
|
12836 @item gnus-browse-menu-hook
|
|
|
12837 @vindex gnus-browse-menu-hook
|
|
|
12838 Hook called after creating the browse mode menu.
|
|
|
12839
|
|
|
12840 @item gnus-score-menu-hook
|
|
|
12841 @vindex gnus-score-menu-hook
|
|
|
12842 Hook called after creating the score mode menu.
|
|
|
12843
|
|
|
12844 @end table
|
|
|
12845
|
|
|
12846
|
|
|
12847 @node Buttons
|
|
|
12848 @section Buttons
|
|
|
12849 @cindex buttons
|
|
|
12850 @cindex mouse
|
|
|
12851 @cindex click
|
|
|
12852
|
|
|
12853 Those new-fangled @dfn{mouse} contraptions is very popular with the
|
|
|
12854 young, hep kids who don't want to learn the proper way to do things
|
|
|
12855 these days. Why, I remember way back in the summer of '89, when I was
|
|
|
12856 using Emacs on a Tops 20 system. Three hundred users on one single
|
|
|
12857 machine, and every user was running Simula compilers. Bah!
|
|
|
12858
|
|
|
12859 Right.
|
|
|
12860
|
|
|
12861 @vindex gnus-carpal
|
|
|
12862 Well, you can make Gnus display bufferfuls of buttons you can click to
|
|
|
12863 do anything by setting @code{gnus-carpal} to @code{t}. Pretty simple,
|
|
|
12864 really. Tell the chiropractor I sent you.
|
|
|
12865
|
|
|
12866
|
|
|
12867 @table @code
|
|
|
12868
|
|
|
12869 @item gnus-carpal-mode-hook
|
|
|
12870 @vindex gnus-carpal-mode-hook
|
|
|
12871 Hook run in all carpal mode buffers.
|
|
|
12872
|
|
|
12873 @item gnus-carpal-button-face
|
|
|
12874 @vindex gnus-carpal-button-face
|
|
|
12875 Face used on buttons.
|
|
|
12876
|
|
|
12877 @item gnus-carpal-header-face
|
|
|
12878 @vindex gnus-carpal-header-face
|
|
|
12879 Face used on carpal buffer headers.
|
|
|
12880
|
|
|
12881 @item gnus-carpal-group-buffer-buttons
|
|
|
12882 @vindex gnus-carpal-group-buffer-buttons
|
|
|
12883 Buttons in the group buffer.
|
|
|
12884
|
|
|
12885 @item gnus-carpal-summary-buffer-buttons
|
|
|
12886 @vindex gnus-carpal-summary-buffer-buttons
|
|
|
12887 Buttons in the summary buffer.
|
|
|
12888
|
|
|
12889 @item gnus-carpal-server-buffer-buttons
|
|
|
12890 @vindex gnus-carpal-server-buffer-buttons
|
|
|
12891 Buttons in the server buffer.
|
|
|
12892
|
|
|
12893 @item gnus-carpal-browse-buffer-buttons
|
|
|
12894 @vindex gnus-carpal-browse-buffer-buttons
|
|
|
12895 Buttons in the browse buffer.
|
|
|
12896 @end table
|
|
|
12897
|
|
|
12898 All the @code{buttons} variables are lists. The elements in these list
|
|
|
12899 is either a cons cell where the car contains a text to be displayed and
|
|
|
12900 the cdr contains a function symbol, or a simple string.
|
|
|
12901
|
|
|
12902
|
|
|
12903 @node Daemons
|
|
|
12904 @section Daemons
|
|
|
12905 @cindex demons
|
|
|
12906 @cindex daemons
|
|
|
12907
|
|
|
12908 Gnus, being larger than any program ever written (allegedly), does lots
|
|
|
12909 of strange stuff that you may wish to have done while you're not
|
|
|
12910 present. For instance, you may want it to check for new mail once in a
|
|
|
12911 while. Or you may want it to close down all connections to all servers
|
|
|
12912 when you leave Emacs idle. And stuff like that.
|
|
|
12913
|
|
|
12914 Gnus will let you do stuff like that by defining various
|
|
|
12915 @dfn{handlers}. Each handler consists of three elements: A
|
|
|
12916 @var{function}, a @var{time}, and an @var{idle} parameter.
|
|
|
12917
|
|
|
12918 Here's an example of a handler that closes connections when Emacs has
|
|
|
12919 been idle for thirty minutes:
|
|
|
12920
|
|
|
12921 @lisp
|
|
|
12922 (gnus-demon-close-connections nil 30)
|
|
|
12923 @end lisp
|
|
|
12924
|
|
|
12925 Here's a handler that scans for PGP headers every hour when Emacs is
|
|
|
12926 idle:
|
|
|
12927
|
|
|
12928 @lisp
|
|
|
12929 (gnus-demon-scan-pgp 60 t)
|
|
|
12930 @end lisp
|
|
|
12931
|
|
|
12932 This @var{time} parameter and than @var{idle} parameter works together
|
|
|
12933 in a strange, but wonderful fashion. Basically, if @var{idle} is
|
|
|
12934 @code{nil}, then the function will be called every @var{time} minutes.
|
|
|
12935
|
|
|
12936 If @var{idle} is @code{t}, then the function will be called after
|
|
|
12937 @var{time} minutes only if Emacs is idle. So if Emacs is never idle,
|
|
|
12938 the function will never be called. But once Emacs goes idle, the
|
|
|
12939 function will be called every @var{time} minutes.
|
|
|
12940
|
|
|
12941 If @var{idle} is a number and @var{time} is a number, the function will
|
|
|
12942 be called every @var{time} minutes only when Emacs has been idle for
|
|
|
12943 @var{idle} minutes.
|
|
|
12944
|
|
|
12945 If @var{idle} is a number and @var{time} is @code{nil}, the function
|
|
|
12946 will be called once every time Emacs has been idle for @var{idle}
|
|
|
12947 minutes.
|
|
|
12948
|
|
|
12949 And if @var{time} is a string, it should look like @samp{07:31}, and
|
|
|
12950 the function will then be called once every day somewhere near that
|
|
|
12951 time. Modified by the @var{idle} parameter, of course.
|
|
|
12952
|
|
|
12953 @vindex gnus-demon-timestep
|
|
|
12954 (When I say ``minute'' here, I really mean @code{gnus-demon-timestep}
|
|
16
|
12955 seconds. This is 60 by default. If you change that variable,
|
|
0
|
12956 all the timings in the handlers will be affected.)
|
|
|
12957
|
|
|
12958 @vindex gnus-use-demon
|
|
|
12959 To set the whole thing in motion, though, you have to set
|
|
|
12960 @code{gnus-use-demon} to @code{t}.
|
|
|
12961
|
|
|
12962 So, if you want to add a handler, you could put something like this in
|
|
|
12963 your @file{.gnus} file:
|
|
|
12964
|
|
|
12965 @findex gnus-demon-add-handler
|
|
|
12966 @lisp
|
|
|
12967 (gnus-demon-add-handler 'gnus-demon-close-connections nil 30)
|
|
|
12968 @end lisp
|
|
|
12969
|
|
|
12970 @findex gnus-demon-add-nocem
|
|
|
12971 @findex gnus-demon-add-scanmail
|
|
16
|
12972 @findex gnus-demon-add-rescan
|
|
0
|
12973 @findex gnus-demon-add-disconnection
|
|
|
12974 Some ready-made functions to do this has been created:
|
|
16
|
12975 @code{gnus-demon-add-nocem}, @code{gnus-demon-add-disconnection},
|
|
|
12976 @code{gnus-demon-add-rescan}, and @code{gnus-demon-add-scanmail}. Just
|
|
|
12977 put those functions in your @file{.gnus} if you want those abilities.
|
|
0
|
12978
|
|
|
12979 @findex gnus-demon-init
|
|
|
12980 @findex gnus-demon-cancel
|
|
|
12981 @vindex gnus-demon-handlers
|
|
|
12982 If you add handlers to @code{gnus-demon-handlers} directly, you should
|
|
|
12983 run @code{gnus-demon-init} to make the changes take hold. To cancel all
|
|
|
12984 daemons, you can use the @code{gnus-demon-cancel} function.
|
|
|
12985
|
|
|
12986 Note that adding daemons can be pretty naughty if you overdo it. Adding
|
|
|
12987 functions that scan all news and mail from all servers every two seconds
|
|
|
12988 is a sure-fire way of getting booted off any respectable system. So
|
|
42
|
12989 behave.
|
|
0
|
12990
|
|
|
12991
|
|
|
12992 @node NoCeM
|
|
|
12993 @section NoCeM
|
|
|
12994 @cindex nocem
|
|
|
12995 @cindex spam
|
|
|
12996
|
|
|
12997 @dfn{Spamming} is posting the same article lots and lots of times.
|
|
|
12998 Spamming is bad. Spamming is evil.
|
|
|
12999
|
|
|
13000 Spamming is usually canceled within a day or so by various anti-spamming
|
|
|
13001 agencies. These agencies usually also send out @dfn{NoCeM} messages.
|
|
|
13002 NoCeM is pronounced ``no see-'em'', and means what the name
|
|
|
13003 implies---these are messages that make the offending articles, like, go
|
|
|
13004 away.
|
|
|
13005
|
|
|
13006 What use are these NoCeM messages if the articles are canceled anyway?
|
|
|
13007 Some sites do not honor cancel messages and some sites just honor cancels
|
|
|
13008 from a select few people. Then you may wish to make use of the NoCeM
|
|
|
13009 messages, which are distributed in the @samp{alt.nocem.misc} newsgroup.
|
|
|
13010
|
|
|
13011 Gnus can read and parse the messages in this group automatically, and
|
|
|
13012 this will make spam disappear.
|
|
|
13013
|
|
|
13014 There are some variables to customize, of course:
|
|
|
13015
|
|
|
13016 @table @code
|
|
|
13017 @item gnus-use-nocem
|
|
|
13018 @vindex gnus-use-nocem
|
|
|
13019 Set this variable to @code{t} to set the ball rolling. It is @code{nil}
|
|
|
13020 by default.
|
|
|
13021
|
|
|
13022 @item gnus-nocem-groups
|
|
|
13023 @vindex gnus-nocem-groups
|
|
|
13024 Gnus will look for NoCeM messages in the groups in this list. The
|
|
16
|
13025 default is @code{("news.lists.filters" "news.admin.net-abuse.bulletins"
|
|
|
13026 "alt.nocem.misc" "news.admin.net-abuse.announce")}.
|
|
0
|
13027
|
|
|
13028 @item gnus-nocem-issuers
|
|
|
13029 @vindex gnus-nocem-issuers
|
|
|
13030 There are many people issuing NoCeM messages. This list says what
|
|
|
13031 people you want to listen to. The default is @code{("Automoose-1"
|
|
|
13032 "clewis@@ferret.ocunix.on.ca;" "jem@@xpat.com;" "red@@redpoll.mrfs.oh.us
|
|
|
13033 (Richard E. Depew)")}; fine, upstanding citizens all of them.
|
|
|
13034
|
|
|
13035 Known despammers that you can put in this list include:
|
|
|
13036
|
|
|
13037 @table @samp
|
|
|
13038 @item clewis@@ferret.ocunix.on.ca;
|
|
|
13039 @cindex Chris Lewis
|
|
|
13040 Chris Lewis---Major Canadian despammer who has probably canceled more
|
|
|
13041 usenet abuse than anybody else.
|
|
|
13042
|
|
|
13043 @item Automoose-1
|
|
|
13044 @cindex CancelMoose[tm]
|
|
|
13045 The CancelMoose[tm] on autopilot. The CancelMoose[tm] is reputed to be
|
|
|
13046 Norwegian, and was the person(s) who invented NoCeM.
|
|
|
13047
|
|
|
13048 @item jem@@xpat.com;
|
|
|
13049 @cindex Jem
|
|
16
|
13050 John Milburn---despammer located in Korea who is getting very busy these
|
|
|
13051 days.
|
|
0
|
13052
|
|
|
13053 @item red@@redpoll.mrfs.oh.us (Richard E. Depew)
|
|
|
13054 Richard E. Depew---lone American despammer. He mostly cancels binary
|
|
|
13055 postings to non-binary groups and removes spews (regurgitated articles).
|
|
|
13056 @end table
|
|
|
13057
|
|
|
13058 You do not have to heed NoCeM messages from all these people---just the
|
|
|
13059 ones you want to listen to.
|
|
|
13060
|
|
16
|
13061 @item gnus-nocem-verifyer
|
|
|
13062 @vindex gnus-nocem-verifyer
|
|
|
13063 @findex mc-verify
|
|
|
13064 This should be a function for verifying that the NoCeM issuer is who she
|
|
|
13065 says she is. The default is @code{mc-verify}, which is a Mailcrypt
|
|
|
13066 function. If this is too slow and you don't care for verification
|
|
|
13067 (which may be dangerous), you can set this variable to @code{nil}.
|
|
|
13068
|
|
0
|
13069 @item gnus-nocem-directory
|
|
|
13070 @vindex gnus-nocem-directory
|
|
|
13071 This is where Gnus will store its NoCeM cache files. The default is
|
|
|
13072 @file{~/News/NoCeM/}.
|
|
|
13073
|
|
|
13074 @item gnus-nocem-expiry-wait
|
|
|
13075 @vindex gnus-nocem-expiry-wait
|
|
|
13076 The number of days before removing old NoCeM entries from the cache.
|
|
|
13077 The default is 15. If you make it shorter Gnus will be faster, but you
|
|
|
13078 might then see old spam.
|
|
|
13079
|
|
|
13080 @end table
|
|
|
13081
|
|
|
13082
|
|
|
13083 @node Picons
|
|
|
13084 @section Picons
|
|
|
13085
|
|
|
13086 So... You want to slow down your news reader even more! This is a
|
|
|
13087 good way to do so. Its also a great way to impress people staring
|
|
|
13088 over your shoulder as you read news.
|
|
|
13089
|
|
|
13090 @menu
|
|
|
13091 * Picon Basics:: What are picons and How do I get them.
|
|
|
13092 * Picon Requirements:: Don't go further if you aren't using XEmacs.
|
|
2
|
13093 * Easy Picons:: Displaying Picons---the easy way.
|
|
0
|
13094 * Hard Picons:: The way you should do it. You'll learn something.
|
|
|
13095 * Picon Configuration:: Other variables you can trash/tweak/munge/play with.
|
|
|
13096 @end menu
|
|
|
13097
|
|
|
13098
|
|
|
13099 @node Picon Basics
|
|
|
13100 @subsection Picon Basics
|
|
|
13101
|
|
16
|
13102 What are Picons? To quote directly from the Picons Web site:
|
|
0
|
13103
|
|
|
13104 @quotation
|
|
|
13105 @dfn{Picons} is short for ``personal icons''. They're small,
|
|
|
13106 constrained images used to represent users and domains on the net,
|
|
|
13107 organized into databases so that the appropriate image for a given
|
|
|
13108 e-mail address can be found. Besides users and domains, there are picon
|
|
|
13109 databases for Usenet newsgroups and weather forecasts. The picons are
|
|
|
13110 in either monochrome @code{XBM} format or color @code{XPM} and
|
|
|
13111 @code{GIF} formats.
|
|
|
13112 @end quotation
|
|
|
13113
|
|
16
|
13114 For instructions on obtaining and installing the picons databases, point
|
|
|
13115 your Web browser at
|
|
|
13116 @file{http://www.cs.indiana.edu/picons/ftp/index.html}.
|
|
0
|
13117
|
|
|
13118 @vindex gnus-picons-database
|
|
|
13119 Gnus expects picons to be installed into a location pointed to by
|
|
|
13120 @code{gnus-picons-database}.
|
|
|
13121
|
|
|
13122
|
|
|
13123 @node Picon Requirements
|
|
|
13124 @subsection Picon Requirements
|
|
|
13125
|
|
|
13126 To use have Gnus display Picons for you, you must be running XEmacs
|
|
|
13127 19.13 or greater since all other versions of Emacs aren't yet able to
|
|
|
13128 display images.
|
|
|
13129
|
|
|
13130 Additionally, you must have @code{xpm} support compiled into XEmacs.
|
|
|
13131
|
|
|
13132 @vindex gnus-picons-convert-x-face
|
|
|
13133 If you want to display faces from @code{X-Face} headers, you must have
|
|
|
13134 the @code{netpbm} utilities installed, or munge the
|
|
|
13135 @code{gnus-picons-convert-x-face} variable to use something else.
|
|
|
13136
|
|
|
13137
|
|
|
13138 @node Easy Picons
|
|
|
13139 @subsection Easy Picons
|
|
|
13140
|
|
|
13141 To enable displaying picons, simply put the following line in your
|
|
|
13142 @file{~/.gnus} file and start Gnus.
|
|
|
13143
|
|
|
13144 @lisp
|
|
|
13145 (setq gnus-use-picons t)
|
|
|
13146 (add-hook 'gnus-article-display-hook 'gnus-article-display-picons t)
|
|
|
13147 (add-hook 'gnus-summary-prepare-hook 'gnus-group-display-picons t)
|
|
|
13148 (add-hook 'gnus-article-display-hook 'gnus-picons-article-display-x-face)
|
|
|
13149 @end lisp
|
|
|
13150
|
|
|
13151
|
|
|
13152 @node Hard Picons
|
|
|
13153 @subsection Hard Picons
|
|
|
13154
|
|
|
13155 Gnus can display picons for you as you enter and leave groups and
|
|
|
13156 articles. It knows how to interact with three sections of the picons
|
|
|
13157 database. Namely, it can display the picons newsgroup pictures,
|
|
|
13158 author's face picture(s), and the authors domain. To enable this
|
|
|
13159 feature, you need to first decide where to display them.
|
|
|
13160
|
|
|
13161 @table @code
|
|
|
13162
|
|
|
13163 @item gnus-picons-display-where
|
|
|
13164 @vindex gnus-picons-display-where
|
|
|
13165 Where the picon images should be displayed. It is @code{picons} by
|
|
|
13166 default (which by default maps to the buffer @samp{*Picons*}). Other
|
|
|
13167 valid places could be @code{article}, @code{summary}, or
|
|
16
|
13168 @samp{*scratch*} for all I care. Just make sure that you've made the
|
|
2
|
13169 buffer visible using the standard Gnus window configuration
|
|
16
|
13170 routines---@pxref{Windows Configuration}.
|
|
0
|
13171
|
|
|
13172 @end table
|
|
|
13173
|
|
|
13174 Note: If you set @code{gnus-use-picons} to @code{t}, it will set up your
|
|
|
13175 window configuration for you to include the @code{picons} buffer.
|
|
|
13176
|
|
|
13177 Now that you've made that decision, you need to add the following
|
|
|
13178 functions to the appropriate hooks so these pictures will get
|
|
|
13179 displayed at the right time.
|
|
|
13180
|
|
|
13181 @vindex gnus-article-display-hook
|
|
|
13182 @vindex gnus-picons-display-where
|
|
|
13183 @table @code
|
|
|
13184 @item gnus-article-display-picons
|
|
|
13185 @findex gnus-article-display-picons
|
|
|
13186 Looks up and display the picons for the author and the author's domain
|
|
|
13187 in the @code{gnus-picons-display-where} buffer. Should be added to
|
|
|
13188 the @code{gnus-article-display-hook}.
|
|
|
13189
|
|
|
13190 @item gnus-group-display-picons
|
|
|
13191 @findex gnus-article-display-picons
|
|
|
13192 Displays picons representing the current group. This function should
|
|
|
13193 be added to the @code{gnus-summary-prepare-hook} or to the
|
|
|
13194 @code{gnus-article-display-hook} if @code{gnus-picons-display-where}
|
|
|
13195 is set to @code{article}.
|
|
|
13196
|
|
|
13197 @item gnus-picons-article-display-x-face
|
|
|
13198 @findex gnus-article-display-picons
|
|
|
13199 Decodes and displays the X-Face header if present. This function
|
|
|
13200 should be added to @code{gnus-article-display-hook}.
|
|
|
13201
|
|
|
13202 @end table
|
|
|
13203
|
|
|
13204 Note: You must append them to the hook, so make sure to specify 't'
|
|
|
13205 to the append flag of @code{add-hook}:
|
|
|
13206
|
|
|
13207 @lisp
|
|
|
13208 (add-hook 'gnus-article-display-hook 'gnus-article-display-picons t)
|
|
|
13209 @end lisp
|
|
|
13210
|
|
|
13211
|
|
|
13212 @node Picon Configuration
|
|
|
13213 @subsection Picon Configuration
|
|
|
13214
|
|
|
13215 The following variables offer further control over how things are
|
|
|
13216 done, where things are located, and other useless stuff you really
|
|
|
13217 don't need to worry about.
|
|
|
13218
|
|
|
13219 @table @code
|
|
|
13220 @item gnus-picons-database
|
|
|
13221 @vindex gnus-picons-database
|
|
|
13222 The location of the picons database. Should point to a directory
|
|
|
13223 containing the @file{news}, @file{domains}, @file{users} (and so on)
|
|
|
13224 subdirectories. Defaults to @file{/usr/local/faces}.
|
|
|
13225
|
|
|
13226 @item gnus-picons-news-directory
|
|
|
13227 @vindex gnus-picons-news-directory
|
|
|
13228 Sub-directory of the faces database containing the icons for
|
|
|
13229 newsgroups.
|
|
|
13230
|
|
|
13231 @item gnus-picons-user-directories
|
|
|
13232 @vindex gnus-picons-user-directories
|
|
|
13233 List of subdirectories to search in @code{gnus-picons-database} for user
|
|
16
|
13234 faces. @code{("local" "users" "usenix" "misc/MISC")} is the default.
|
|
0
|
13235
|
|
|
13236 @item gnus-picons-domain-directories
|
|
|
13237 @vindex gnus-picons-domain-directories
|
|
|
13238 List of subdirectories to search in @code{gnus-picons-database} for
|
|
|
13239 domain name faces. Defaults to @code{("domains")}. Some people may
|
|
|
13240 want to add @samp{unknown} to this list.
|
|
|
13241
|
|
|
13242 @item gnus-picons-convert-x-face
|
|
|
13243 @vindex gnus-picons-convert-x-face
|
|
|
13244 The command to use to convert the @code{X-Face} header to an X bitmap
|
|
|
13245 (@code{xbm}). Defaults to @code{(format "@{ echo '/* Width=48,
|
|
|
13246 Height=48 */'; uncompface; @} | icontopbm | pbmtoxbm > %s"
|
|
|
13247 gnus-picons-x-face-file-name)}
|
|
|
13248
|
|
|
13249 @item gnus-picons-x-face-file-name
|
|
|
13250 @vindex gnus-picons-x-face-file-name
|
|
|
13251 Names a temporary file to store the @code{X-Face} bitmap in. Defaults
|
|
|
13252 to @code{(format "/tmp/picon-xface.%s.xbm" (user-login-name))}.
|
|
|
13253
|
|
|
13254 @item gnus-picons-buffer
|
|
|
13255 @vindex gnus-picons-buffer
|
|
|
13256 The name of the buffer that @code{picons} points to. Defaults to
|
|
|
13257 @samp{*Icon Buffer*}.
|
|
|
13258
|
|
|
13259 @end table
|
|
|
13260
|
|
|
13261
|
|
16
|
13262 @node Undo
|
|
|
13263 @section Undo
|
|
|
13264 @cindex undo
|
|
|
13265
|
|
|
13266 It is very useful to be able to undo actions one has done. In normal
|
|
|
13267 Emacs buffers, it's easy enough---you just push the @code{undo} button.
|
|
|
13268 In Gnus buffers, however, it isn't that simple.
|
|
|
13269
|
|
|
13270 The things Gnus displays in its buffer is of no value whatsoever to
|
|
|
13271 Gnus---it's all just data that is designed to look nice to the user.
|
|
|
13272 Killing a group in the group buffer with @kbd{C-k} makes the line
|
|
|
13273 disappear, but that's just a side-effect of the real action---the
|
|
|
13274 removal of the group in question from the internal Gnus structures.
|
|
|
13275 Undoing something like that can't be done by the normal Emacs
|
|
|
13276 @code{undo} function.
|
|
|
13277
|
|
|
13278 Gnus tries to remedy this somewhat by keeping track of what the user
|
|
|
13279 does and coming up with actions that would reverse the actions the user
|
|
|
13280 takes. When the user then presses the @code{undo} key, Gnus will run
|
|
|
13281 the code to reverse the previous action, or the previous actions.
|
|
|
13282 However, not all actions are easily reversible, so Gnus currently offers
|
|
|
13283 a few key functions to be undoable. These include killing groups,
|
|
|
13284 yanking groups, and changing the list of read articles of groups.
|
|
|
13285 That's it, really. More functions may be added in the future, but each
|
|
|
13286 added function means an increase in data to be stored, so Gnus will
|
|
|
13287 never be totally undoable.
|
|
|
13288
|
|
|
13289 @findex gnus-undo-mode
|
|
|
13290 @vindex gnus-use-undo
|
|
|
13291 @findex gnus-undo
|
|
|
13292 The undoability is provided by the @code{gnus-undo-mode} minor mode. It
|
|
|
13293 is used if @code{gnus-use-undo} is non-@code{nil}, which is the
|
|
|
13294 default. The @kbd{M-C-_} key performs the @code{gnus-undo} command
|
|
|
13295 command, which should feel kinda like the normal Emacs @code{undo}
|
|
|
13296 command.
|
|
|
13297
|
|
|
13298
|
|
|
13299 @node Moderation
|
|
|
13300 @section Moderation
|
|
|
13301 @cindex moderation
|
|
|
13302
|
|
|
13303 If you are a moderator, you can use the @file{gnus-mdrtn.el} package.
|
|
|
13304 It is not included in the standard Gnus package. Write a mail to
|
|
|
13305 @samp{larsi@@ifi.uio.no} and state what group you moderate, and you'll
|
|
|
13306 get a copy.
|
|
|
13307
|
|
|
13308 The moderation package is implemented as a minor mode for summary
|
|
|
13309 buffers. Put
|
|
|
13310
|
|
|
13311 @lisp
|
|
|
13312 (add-hook 'gnus-summary-mode-hook 'gnus-moderate)
|
|
|
13313 @end lisp
|
|
|
13314
|
|
|
13315 in your @file{.gnus.el} file.
|
|
|
13316
|
|
|
13317 If you are the moderation of @samp{rec.zoofle}, this is how it's
|
|
|
13318 supposed to work:
|
|
|
13319
|
|
|
13320 @enumerate
|
|
|
13321 @item
|
|
|
13322 You split your incoming mail by matching on
|
|
|
13323 @samp{Newsgroups:.*rec.zoofle}, which will put all the to-be-posted
|
|
|
13324 articles in some mail group---for instance, @samp{nnml:rec.zoofle}.
|
|
|
13325
|
|
|
13326 @item
|
|
|
13327 You enter that group once in a while and post articles using the @kbd{e}
|
|
|
13328 (edit-and-post) or @kbd{s} (just send unedited) commands.
|
|
|
13329
|
|
|
13330 @item
|
|
|
13331 If, while reading the @samp{rec.zoofle} newsgroup, you happen upon some
|
|
|
13332 articles that weren't approved by you, you can cancel them with the
|
|
|
13333 @kbd{c} command.
|
|
|
13334 @end enumerate
|
|
|
13335
|
|
|
13336 To use moderation mode in these two groups, say:
|
|
|
13337
|
|
|
13338 @lisp
|
|
|
13339 (setq gnus-moderated-list
|
|
|
13340 "^nnml:rec.zoofle$\\|^rec.zoofle$")
|
|
|
13341 @end lisp
|
|
|
13342
|
|
|
13343
|
|
|
13344 @node XEmacs Enhancements
|
|
|
13345 @section XEmacs Enhancements
|
|
|
13346 @cindex XEmacs
|
|
|
13347
|
|
|
13348 XEmacs is able to display pictures and stuff, so Gnus has taken
|
|
|
13349 advantage of that. Relevant variables include:
|
|
|
13350
|
|
|
13351 @table @code
|
|
|
13352 @item gnus-xmas-glyph-directory
|
|
|
13353 @vindex gnus-xmas-glyph-directory
|
|
|
13354 This is where Gnus will look for pictures. Gnus will normally
|
|
|
13355 auto-detect this directory, but you may set it manually if you have an
|
|
|
13356 unusual directory structure.
|
|
|
13357
|
|
|
13358 @item gnus-xmas-logo-color-alist
|
|
|
13359 @vindex gnus-xmas-logo-color-alist
|
|
|
13360 This is an alist where the key is a type symbol and the values are the
|
|
|
13361 foreground and background color of the splash page glyph.
|
|
|
13362
|
|
|
13363 @item gnus-xmas-logo-color-style
|
|
|
13364 @vindex gnus-xmas-logo-color-style
|
|
|
13365 This is the key used to look up the color in the alist described above.
|
|
|
13366 Legal values include @code{flame}, @code{pine}, @code{moss},
|
|
|
13367 @code{irish}, @code{sky}, @code{tin}, @code{velvet}, @code{grape},
|
|
|
13368 @code{labia}, @code{berry}, @code{neutral}, and @code{september}.
|
|
|
13369
|
|
|
13370 @item gnus-use-toolbar
|
|
|
13371 @vindex gnus-use-toolbar
|
|
|
13372 If @code{nil}, don't display toolbars. If non-@code{nil}, it should be
|
|
|
13373 one of @code{default-toolbar}, @code{top-toolbar}, @code{bottom-toolbar},
|
|
|
13374 @code{right-toolbar}, or @code{left-toolbar}.
|
|
|
13375
|
|
|
13376 @item gnus-group-toolbar
|
|
|
13377 @vindex gnus-group-toolbar
|
|
|
13378 The toolbar in the group buffer.
|
|
|
13379
|
|
|
13380 @item gnus-summary-toolbar
|
|
|
13381 @vindex gnus-summary-toolbar
|
|
|
13382 The toolbar in the summary buffer.
|
|
|
13383
|
|
|
13384 @item gnus-summary-mail-toolbar
|
|
|
13385 @vindex gnus-summary-mail-toolbar
|
|
|
13386 The toolbar in the summary buffer of mail groups.
|
|
|
13387
|
|
|
13388 @item gnus-xmas-modeline-glyph
|
|
|
13389 @vindex gnus-xmas-modeline-glyph
|
|
|
13390 A glyph displayed in all Gnus mode lines. It is a tiny gnu head by
|
|
|
13391 default.
|
|
|
13392
|
|
|
13393 @end table
|
|
|
13394
|
|
|
13395
|
|
26
|
13396 @node Fuzzy Matching
|
|
|
13397 @section Fuzzy Matching
|
|
|
13398 @cindex fuzzy matching
|
|
|
13399
|
|
|
13400 Gnus provides @dfn{fuzzy matching} of @code{Subject} lines when doing
|
|
|
13401 things like scoring, thread gathering and thread comparison.
|
|
|
13402
|
|
|
13403 As opposed to regular expression matching, fuzzy matching is very fuzzy.
|
|
|
13404 It's so fuzzy that there's not even a definition of what @dfn{fuzziness}
|
|
|
13405 means, and the implementation has changed over time.
|
|
|
13406
|
|
|
13407 Basically, it tries to remove all noise from lines before comparing.
|
|
|
13408 @samp{Re: }, parenthetical remarks, white space, and so on, are filtered
|
|
|
13409 out of the strings before comparing the results. This often leads to
|
|
|
13410 adequate results---even when faced with strings generated by text
|
|
|
13411 manglers masquerading as newsreaders.
|
|
|
13412
|
|
|
13413
|
|
42
|
13414 @node Thwarting Email Spam
|
|
|
13415 @section Thwarting Email Spam
|
|
|
13416 @cindex email spam
|
|
|
13417 @cindex spam
|
|
|
13418 @cindex UCE
|
|
|
13419 @cindex unsolicited commercial email
|
|
|
13420
|
|
|
13421 In these last days of the Usenet, commercial vultures are hanging about
|
|
|
13422 and grepping through news like crazy to find email addresses they can
|
|
|
13423 foist off their scams and products to. As a reaction to this, many
|
|
|
13424 people have started putting nonsense addresses into their @code{From}
|
|
|
13425 lines. I think this is counterproductive---it makes it difficult for
|
|
|
13426 people to send you legitimate mail in response to things you write, as
|
|
|
13427 well as making it difficult to see who wrote what. This rewriting may
|
|
|
13428 perhaps be a bigger menace than the unsolicited commercial email itself
|
|
|
13429 in the end.
|
|
|
13430
|
|
|
13431 The biggest problem I have with email spam is that it comes in under
|
|
|
13432 false pretenses. I press @kbd{g} and Gnus merrily informs me that I
|
|
|
13433 have 10 new emails. I say ``Golly gee! Happy is me!'' and selects the
|
|
|
13434 mail group, only to find two pyramid schemes, seven advertisements
|
|
|
13435 ``New! Miracle tonic for growing full, lustrouos hair on your toes!''
|
|
|
13436 and one mail asking me to repent and find some god.
|
|
|
13437
|
|
|
13438 This is annoying.
|
|
|
13439
|
|
|
13440 The way to deal with this is having Gnus split out all spam into a
|
|
|
13441 @samp{spam} mail group (@pxref{Splitting Mail}).
|
|
|
13442
|
|
|
13443 First, pick one (1) legal mail address that you can be reached at, and
|
|
|
13444 put it in your @code{From} header of all your news articles. (I've
|
|
|
13445 chosen @samp{larsi@@trym.ifi.uio.no}.)
|
|
|
13446
|
|
|
13447 @lisp
|
|
|
13448 (setq message-default-news-headers
|
|
|
13449 "From: Lars Magne Ingebrigtsen <larsi@@trym.ifi.uio.no>\n")
|
|
|
13450 @end lisp
|
|
|
13451
|
|
|
13452 Then put the following split rule in @code{nnmail-split-fancy}
|
|
|
13453 (@pxref{Fancy Mail Splitting}):
|
|
|
13454
|
|
|
13455 @lisp
|
|
|
13456 (
|
|
|
13457 ...
|
|
|
13458 (to "larsi@@trym.ifi.uio.no"
|
|
|
13459 (| ("subject" "re:.*" "misc")
|
|
|
13460 ("references" ".*@@.*" "misc")
|
|
|
13461 "spam"))
|
|
|
13462 ...
|
|
|
13463 )
|
|
|
13464 @end lisp
|
|
|
13465
|
|
|
13466 This says that all mail to this address is suspect, but if it has a
|
|
|
13467 @code{Subject} that starts with a @samp{Re:} or has a @code{References}
|
|
|
13468 header, it's probably ok. All the rest goes to the @samp{spam} group.
|
|
|
13469 (This idea probably comes from Tim Pierce.)
|
|
|
13470
|
|
|
13471 In my experience, this will sort virtually everything into the right
|
|
|
13472 group. You still have to check the @samp{spam} group from time to time to
|
|
|
13473 check for legitimate mail, though. If you feel like being a good net
|
|
|
13474 citizen, you can even send off complaints to the proper authorities on
|
|
|
13475 each unsolicited commercial email---at your leisure.
|
|
|
13476
|
|
|
13477 This works for me. It allows people an easy way to contact me (they can
|
|
|
13478 just press @kbd{r} in the usual way), and I'm not bothered at all with
|
|
|
13479 spam. It's a win-win situation. Forging @code{From} headers to point
|
|
|
13480 to non-existant domains is yucky, in my opinion.
|
|
|
13481
|
|
|
13482
|
|
0
|
13483 @node Various Various
|
|
|
13484 @section Various Various
|
|
|
13485 @cindex mode lines
|
|
|
13486 @cindex highlights
|
|
|
13487
|
|
|
13488 @table @code
|
|
|
13489
|
|
32
|
13490 @item gnus-home-directory
|
|
|
13491 All Gnus path variables will be initialized from this variable, which
|
|
|
13492 defaults to @file{~/}.
|
|
|
13493
|
|
16
|
13494 @item gnus-directory
|
|
|
13495 @vindex gnus-directory
|
|
32
|
13496 Most Gnus storage path variables will be initialized from this variable,
|
|
|
13497 which defaults to the @samp{SAVEDIR} environment variable, or
|
|
|
13498 @file{~/News/} if that variable isn't set.
|
|
16
|
13499
|
|
|
13500 @item gnus-default-directory
|
|
|
13501 @vindex gnus-default-directory
|
|
|
13502 Not related to the above variable at all---this variable says what the
|
|
|
13503 default directory of all Gnus buffers should be. If you issue commands
|
|
|
13504 like @kbd{C-x C-f}, the prompt you'll get starts in the current buffer's
|
|
|
13505 default directory. If this variable is @code{nil} (which is the
|
|
|
13506 default), the default directory will be the default directory of the
|
|
|
13507 buffer you were in when you started Gnus.
|
|
|
13508
|
|
0
|
13509 @item gnus-verbose
|
|
|
13510 @vindex gnus-verbose
|
|
|
13511 This variable is an integer between zero and ten. The higher the value,
|
|
|
13512 the more messages will be displayed. If this variable is zero, Gnus
|
|
|
13513 will never flash any messages, if it is seven (which is the default),
|
|
|
13514 most important messages will be shown, and if it is ten, Gnus won't ever
|
|
|
13515 shut up, but will flash so many messages it will make your head swim.
|
|
|
13516
|
|
|
13517 @item gnus-verbose-backends
|
|
|
13518 @vindex gnus-verbose-backends
|
|
|
13519 This variable works the same way as @code{gnus-verbose}, but it applies
|
|
|
13520 to the Gnus backends instead of Gnus proper.
|
|
|
13521
|
|
|
13522 @item nnheader-max-head-length
|
|
|
13523 @vindex nnheader-max-head-length
|
|
|
13524 When the backends read straight heads of articles, they all try to read
|
|
16
|
13525 as little as possible. This variable (default 4096) specifies
|
|
0
|
13526 the absolute max length the backends will try to read before giving up
|
|
|
13527 on finding a separator line between the head and the body. If this
|
|
|
13528 variable is @code{nil}, there is no upper read bound. If it is
|
|
|
13529 @code{t}, the backends won't try to read the articles piece by piece,
|
|
|
13530 but read the entire articles. This makes sense with some versions of
|
|
|
13531 @code{ange-ftp}.
|
|
|
13532
|
|
16
|
13533 @item nnheader-head-chop-length
|
|
|
13534 @vindex nnheader-head-chop-length
|
|
|
13535 This variable says how big a piece of each article to read when doing
|
|
|
13536 the operation described above.
|
|
|
13537
|
|
0
|
13538 @item nnheader-file-name-translation-alist
|
|
|
13539 @vindex nnheader-file-name-translation-alist
|
|
|
13540 @cindex file names
|
|
|
13541 @cindex illegal characters in file names
|
|
|
13542 @cindex characters in file names
|
|
|
13543 This is an alist that says how to translate characters in file names.
|
|
|
13544 For instance, if @samp{:} is illegal as a file character in file names
|
|
|
13545 on your system (you OS/2 user you), you could say something like:
|
|
|
13546
|
|
|
13547 @lisp
|
|
|
13548 (setq nnheader-file-name-translation-alist
|
|
|
13549 '((?: . ?_)))
|
|
|
13550 @end lisp
|
|
|
13551
|
|
|
13552 In fact, this is the default value for this variable on OS/2 and MS
|
|
|
13553 Windows (phooey) systems.
|
|
|
13554
|
|
|
13555 @item gnus-hidden-properties
|
|
|
13556 @vindex gnus-hidden-properties
|
|
|
13557 This is a list of properties to use to hide ``invisible'' text. It is
|
|
|
13558 @code{(invisible t intangible t)} by default on most systems, which
|
|
|
13559 makes invisible text invisible and intangible.
|
|
|
13560
|
|
|
13561 @item gnus-parse-headers-hook
|
|
|
13562 @vindex gnus-parse-headers-hook
|
|
|
13563 A hook called before parsing headers. It can be used, for instance, to
|
|
|
13564 gather statistics on the headers fetched, or perhaps you'd like to prune
|
|
|
13565 some headers. I don't see why you'd want that, though.
|
|
|
13566
|
|
2
|
13567 @item gnus-shell-command-separator
|
|
|
13568 @vindex gnus-shell-command-separator
|
|
|
13569 String used to separate to shell commands. The default is @samp{;}.
|
|
|
13570
|
|
|
13571
|
|
0
|
13572 @end table
|
|
|
13573
|
|
|
13574
|
|
|
13575 @node The End
|
|
|
13576 @chapter The End
|
|
|
13577
|
|
|
13578 Well, that's the manual---you can get on with your life now. Keep in
|
|
|
13579 touch. Say hello to your cats from me.
|
|
|
13580
|
|
|
13581 My @strong{ghod}---I just can't stand goodbyes. Sniffle.
|
|
|
13582
|
|
|
13583 Ol' Charles Reznikoff said it pretty well, so I leave the floor to him:
|
|
|
13584
|
|
|
13585 @quotation
|
|
|
13586 @strong{Te Deum}
|
|
16
|
13587
|
|
0
|
13588 @sp 1
|
|
|
13589 Not because of victories @*
|
|
|
13590 I sing,@*
|
|
|
13591 having none,@*
|
|
|
13592 but for the common sunshine,@*
|
|
|
13593 the breeze,@*
|
|
|
13594 the largess of the spring.
|
|
16
|
13595
|
|
0
|
13596 @sp 1
|
|
|
13597 Not for victory@*
|
|
|
13598 but for the day's work done@*
|
|
|
13599 as well as I was able;@*
|
|
|
13600 not for a seat upon the dais@*
|
|
|
13601 but at the common table.@*
|
|
|
13602 @end quotation
|
|
|
13603
|
|
|
13604
|
|
|
13605 @node Appendices
|
|
|
13606 @chapter Appendices
|
|
|
13607
|
|
|
13608 @menu
|
|
|
13609 * History:: How Gnus got where it is today.
|
|
|
13610 * Terminology:: We use really difficult, like, words here.
|
|
|
13611 * Customization:: Tailoring Gnus to your needs.
|
|
|
13612 * Troubleshooting:: What you might try if things do not work.
|
|
|
13613 * A Programmers Guide to Gnus:: Rilly, rilly technical stuff.
|
|
|
13614 * Emacs for Heathens:: A short introduction to Emacsian terms.
|
|
|
13615 * Frequently Asked Questions:: A question-and-answer session.
|
|
|
13616 @end menu
|
|
|
13617
|
|
|
13618
|
|
|
13619 @node History
|
|
|
13620 @section History
|
|
|
13621
|
|
|
13622 @cindex history
|
|
|
13623 @sc{gnus} was written by Masanobu @sc{Umeda}. When autumn crept up in
|
|
|
13624 '94, Lars Magne Ingebrigtsen grew bored and decided to rewrite Gnus.
|
|
|
13625
|
|
|
13626 If you want to investigate the person responsible for this outrage, you
|
|
|
13627 can point your (feh!) web browser to
|
|
|
13628 @file{http://www.ifi.uio.no/~larsi/}. This is also the primary
|
|
|
13629 distribution point for the new and spiffy versions of Gnus, and is known
|
|
|
13630 as The Site That Destroys Newsrcs And Drives People Mad.
|
|
|
13631
|
|
|
13632 During the first extended alpha period of development, the new Gnus was
|
|
16
|
13633 called ``(ding) Gnus''. @dfn{(ding)} is, of course, short for
|
|
0
|
13634 @dfn{ding is not Gnus}, which is a total and utter lie, but who cares?
|
|
|
13635 (Besides, the ``Gnus'' in this abbreviation should probably be
|
|
|
13636 pronounced ``news'' as @sc{Umeda} intended, which makes it a more
|
|
|
13637 appropriate name, don't you think?)
|
|
|
13638
|
|
|
13639 In any case, after spending all that energy on coming up with a new and
|
|
|
13640 spunky name, we decided that the name was @emph{too} spunky, so we
|
|
|
13641 renamed it back again to ``Gnus''. But in mixed case. ``Gnus'' vs.
|
|
|
13642 ``@sc{gnus}''. New vs. old.
|
|
|
13643
|
|
|
13644 The first ``proper'' release of Gnus 5 was done in November 1995 when it
|
|
16
|
13645 was included in the Emacs 19.30 distribution (132 (ding) Gnus releases
|
|
|
13646 plus 15 Gnus 5.0 releases).
|
|
|
13647
|
|
|
13648 In May 1996 the next Gnus generation (aka. ``September Gnus'' (after 99
|
|
|
13649 releases)) was released under the name ``Gnus 5.2'' (40 releases).
|
|
|
13650
|
|
|
13651 On July 28th 1996 work on Red Gnus was begun, and it was released on
|
|
|
13652 January 25th 1997 (after 84 releases) as ``Gnus 5.4''.
|
|
|
13653
|
|
|
13654 If you happen upon a version of Gnus that has a name that is prefixed --
|
|
|
13655 ``(ding) Gnus'', ``September Gnus'', ``Red Gnus'', ``Quassia Gnus'' --
|
|
|
13656 don't panic. Don't let it know that you're frightened. Back away.
|
|
|
13657 Slowly. Whatever you do, don't run. Walk away, calmly, until you're
|
|
|
13658 out of its reach. Find a proper released version of Gnus and snuggle up
|
|
|
13659 to that instead.
|
|
0
|
13660
|
|
|
13661 @menu
|
|
|
13662 * Why?:: What's the point of Gnus?
|
|
|
13663 * Compatibility:: Just how compatible is Gnus with @sc{gnus}?
|
|
|
13664 * Conformity:: Gnus tries to conform to all standards.
|
|
|
13665 * Emacsen:: Gnus can be run on a few modern Emacsen.
|
|
|
13666 * Contributors:: Oodles of people.
|
|
|
13667 * New Features:: Pointers to some of the new stuff in Gnus.
|
|
|
13668 * Newest Features:: Features so new that they haven't been written yet.
|
|
|
13669 @end menu
|
|
|
13670
|
|
|
13671
|
|
|
13672 @node Why?
|
|
|
13673 @subsection Why?
|
|
|
13674
|
|
|
13675 What's the point of Gnus?
|
|
|
13676
|
|
|
13677 I want to provide a ``rad'', ``happening'', ``way cool'' and ``hep''
|
|
|
13678 newsreader, that lets you do anything you can think of. That was my
|
|
|
13679 original motivation, but while working on Gnus, it has become clear to
|
|
|
13680 me that this generation of newsreaders really belong in the stone age.
|
|
|
13681 Newsreaders haven't developed much since the infancy of the net. If the
|
|
|
13682 volume continues to rise with the current rate of increase, all current
|
|
|
13683 newsreaders will be pretty much useless. How do you deal with
|
|
|
13684 newsgroups that have thousands of new articles each day? How do you
|
|
|
13685 keep track of millions of people who post?
|
|
|
13686
|
|
|
13687 Gnus offers no real solutions to these questions, but I would very much
|
|
|
13688 like to see Gnus being used as a testing ground for new methods of
|
|
|
13689 reading and fetching news. Expanding on @sc{Umeda}-san's wise decision
|
|
|
13690 to separate the newsreader from the backends, Gnus now offers a simple
|
|
|
13691 interface for anybody who wants to write new backends for fetching mail
|
|
|
13692 and news from different sources. I have added hooks for customizations
|
|
|
13693 everywhere I could imagine useful. By doing so, I'm inviting every one
|
|
|
13694 of you to explore and invent.
|
|
|
13695
|
|
|
13696 May Gnus never be complete. @kbd{C-u 100 M-x hail-emacs}.
|
|
|
13697
|
|
|
13698
|
|
|
13699 @node Compatibility
|
|
|
13700 @subsection Compatibility
|
|
|
13701
|
|
|
13702 @cindex compatibility
|
|
|
13703 Gnus was designed to be fully compatible with @sc{gnus}. Almost all key
|
|
|
13704 bindings have been kept. More key bindings have been added, of course,
|
|
|
13705 but only in one or two obscure cases have old bindings been changed.
|
|
|
13706
|
|
|
13707 Our motto is:
|
|
|
13708 @quotation
|
|
|
13709 @cartouche
|
|
|
13710 @center In a cloud bones of steel.
|
|
|
13711 @end cartouche
|
|
|
13712 @end quotation
|
|
|
13713
|
|
|
13714 All commands have kept their names. Some internal functions have changed
|
|
|
13715 their names.
|
|
|
13716
|
|
|
13717 The @code{gnus-uu} package has changed drastically. @pxref{Decoding
|
|
|
13718 Articles}.
|
|
|
13719
|
|
|
13720 One major compatibility question is the presence of several summary
|
|
|
13721 buffers. All variables that are relevant while reading a group are
|
|
|
13722 buffer-local to the summary buffer they belong in. Although many
|
|
|
13723 important variables have their values copied into their global
|
|
|
13724 counterparts whenever a command is executed in the summary buffer, this
|
|
|
13725 change might lead to incorrect values being used unless you are careful.
|
|
|
13726
|
|
|
13727 All code that relies on knowledge of @sc{gnus} internals will probably
|
|
|
13728 fail. To take two examples: Sorting @code{gnus-newsrc-alist} (or
|
|
|
13729 changing it in any way, as a matter of fact) is strictly verboten. Gnus
|
|
|
13730 maintains a hash table that points to the entries in this alist (which
|
|
|
13731 speeds up many functions), and changing the alist directly will lead to
|
|
|
13732 peculiar results.
|
|
|
13733
|
|
|
13734 @cindex hilit19
|
|
|
13735 @cindex highlighting
|
|
|
13736 Old hilit19 code does not work at all. In fact, you should probably
|
|
|
13737 remove all hilit code from all Gnus hooks
|
|
|
13738 (@code{gnus-group-prepare-hook} and @code{gnus-summary-prepare-hook}).
|
|
|
13739 Gnus provides various integrated functions for highlighting. These are
|
|
|
13740 faster and more accurate. To make life easier for everybody, Gnus will
|
|
|
13741 by default remove all hilit calls from all hilit hooks. Uncleanliness!
|
|
|
13742 Away!
|
|
|
13743
|
|
|
13744 Packages like @code{expire-kill} will no longer work. As a matter of
|
|
|
13745 fact, you should probably remove all old @sc{gnus} packages (and other
|
|
|
13746 code) when you start using Gnus. More likely than not, Gnus already
|
|
|
13747 does what you have written code to make @sc{gnus} do. (Snicker.)
|
|
|
13748
|
|
|
13749 Even though old methods of doing things are still supported, only the
|
|
|
13750 new methods are documented in this manual. If you detect a new method of
|
|
|
13751 doing something while reading this manual, that does not mean you have
|
|
|
13752 to stop doing it the old way.
|
|
|
13753
|
|
|
13754 Gnus understands all @sc{gnus} startup files.
|
|
|
13755
|
|
|
13756 @kindex M-x gnus-bug
|
|
|
13757 @findex gnus-bug
|
|
|
13758 @cindex reporting bugs
|
|
|
13759 @cindex bugs
|
|
|
13760 Overall, a casual user who hasn't written much code that depends on
|
|
|
13761 @sc{gnus} internals should suffer no problems. If problems occur,
|
|
|
13762 please let me know by issuing that magic command @kbd{M-x gnus-bug}.
|
|
|
13763
|
|
|
13764
|
|
|
13765 @node Conformity
|
|
|
13766 @subsection Conformity
|
|
|
13767
|
|
|
13768 No rebels without a clue here, ma'am. We conform to all standards known
|
|
|
13769 to (wo)man. Except for those standards and/or conventions we disagree
|
|
|
13770 with, of course.
|
|
|
13771
|
|
|
13772 @table @strong
|
|
|
13773
|
|
|
13774 @item RFC 822
|
|
|
13775 @cindex RFC 822
|
|
|
13776 There are no known breaches of this standard.
|
|
|
13777
|
|
|
13778 @item RFC 1036
|
|
|
13779 @cindex RFC 1036
|
|
|
13780 There are no known breaches of this standard, either.
|
|
|
13781
|
|
2
|
13782 @item Good Net-Keeping Seal of Approval
|
|
|
13783 @cindex Good Net-Keeping Seal of Approval
|
|
|
13784 Gnus has been through the Seal process and failed. I think it'll pass
|
|
|
13785 the next inspection.
|
|
0
|
13786
|
|
|
13787 @item Son-of-RFC 1036
|
|
|
13788 @cindex Son-of-RFC 1036
|
|
|
13789 We do have some breaches to this one.
|
|
|
13790
|
|
|
13791 @table @emph
|
|
|
13792
|
|
|
13793 @item MIME
|
|
|
13794 Gnus does no MIME handling, and this standard-to-be seems to think that
|
|
|
13795 MIME is the bees' knees, so we have major breakage here.
|
|
|
13796
|
|
|
13797 @item X-Newsreader
|
|
|
13798 This is considered to be a ``vanity header'', while I consider it to be
|
|
|
13799 consumer information. After seeing so many badly formatted articles
|
|
|
13800 coming from @code{tin} and @code{Netscape} I know not to use either of
|
|
|
13801 those for posting articles. I would not have known that if it wasn't
|
|
|
13802 for the @code{X-Newsreader} header.
|
|
|
13803 @end table
|
|
|
13804
|
|
|
13805 @end table
|
|
|
13806
|
|
|
13807 If you ever notice Gnus acting non-compliantly with regards to the texts
|
|
|
13808 mentioned above, don't hesitate to drop a note to Gnus Towers and let us
|
|
|
13809 know.
|
|
|
13810
|
|
|
13811
|
|
|
13812 @node Emacsen
|
|
|
13813 @subsection Emacsen
|
|
|
13814 @cindex Emacsen
|
|
|
13815 @cindex XEmacs
|
|
|
13816 @cindex Mule
|
|
|
13817 @cindex Emacs
|
|
|
13818
|
|
|
13819 Gnus should work on :
|
|
|
13820
|
|
|
13821 @itemize @bullet
|
|
|
13822
|
|
|
13823 @item
|
|
16
|
13824 Emacs 19.32 and up.
|
|
|
13825
|
|
|
13826 @item
|
|
|
13827 XEmacs 19.14 and up.
|
|
|
13828
|
|
|
13829 @item
|
|
|
13830 Mule versions based on Emacs 19.32 and up.
|
|
0
|
13831
|
|
|
13832 @end itemize
|
|
|
13833
|
|
|
13834 Gnus will absolutely not work on any Emacsen older than that. Not
|
|
|
13835 reliably, at least.
|
|
|
13836
|
|
16
|
13837 There are some vague differences between Gnus on the various
|
|
|
13838 platforms---XEmacs features more graphics (a logo and a toolbar)---but
|
|
|
13839 other than that, things should look pretty much the same under all
|
|
|
13840 Emacsen.
|
|
0
|
13841
|
|
|
13842
|
|
|
13843 @node Contributors
|
|
|
13844 @subsection Contributors
|
|
|
13845 @cindex contributors
|
|
|
13846
|
|
|
13847 The new Gnus version couldn't have been done without the help of all the
|
|
|
13848 people on the (ding) mailing list. Every day for over a year I have
|
|
|
13849 gotten billions of nice bug reports from them, filling me with joy,
|
|
|
13850 every single one of them. Smooches. The people on the list have been
|
|
|
13851 tried beyond endurance, what with my ``oh, that's a neat idea <type
|
|
|
13852 type>, yup, I'll release it right away <ship off> no wait, that doesn't
|
|
|
13853 work at all <type type>, yup, I'll ship that one off right away <ship
|
|
|
13854 off> no, wait, that absolutely does not work'' policy for releases.
|
|
|
13855 Micro$oft---bah. Amateurs. I'm @emph{much} worse. (Or is that
|
|
|
13856 ``worser''? ``much worser''? ``worsest''?)
|
|
|
13857
|
|
|
13858 I would like to take this opportunity to thank the Academy for... oops,
|
|
|
13859 wrong show.
|
|
|
13860
|
|
|
13861 @itemize @bullet
|
|
|
13862
|
|
16
|
13863 @item
|
|
|
13864 Masanobu @sc{Umeda}---the writer of the original @sc{gnus}.
|
|
|
13865
|
|
|
13866 @item
|
|
|
13867 Per Abrahamsen---custom, scoring, highlighting and @sc{soup} code (as
|
|
|
13868 well as numerous other things).
|
|
|
13869
|
|
|
13870 @item
|
|
|
13871 Luis Fernandes---design and graphics.
|
|
|
13872
|
|
|
13873 @item
|
|
|
13874 Erik Naggum---help, ideas, support, code and stuff.
|
|
|
13875
|
|
|
13876 @item
|
|
|
13877 Wes Hardaker---@file{gnus-picon.el} and the manual section on
|
|
|
13878 @dfn{picons} (@pxref{Picons}).
|
|
|
13879
|
|
|
13880 @item
|
|
|
13881 Brad Miller---@file{gnus-gl.el} and the GroupLens manual section
|
|
|
13882 (@pxref{GroupLens}).
|
|
|
13883
|
|
|
13884 @item
|
|
|
13885 Sudish Joseph---innumerable bug fixes.
|
|
|
13886
|
|
|
13887 @item
|
|
|
13888 Ilja Weis---@file{gnus-topic.el}.
|
|
|
13889
|
|
|
13890 @item
|
|
|
13891 Steven L. Baur---lots and lots and lots of bugs detections and fixes.
|
|
|
13892
|
|
|
13893 @item
|
|
|
13894 Vladimir Alexiev---the refcard and reference booklets.
|
|
|
13895
|
|
|
13896 @item
|
|
|
13897 Felix Lee & Jamie Zawinsky---I stole some pieces from the XGnus
|
|
|
13898 distribution by Felix Lee and JWZ.
|
|
|
13899
|
|
|
13900 @item
|
|
|
13901 Scott Byer---@file{nnfolder.el} enhancements & rewrite.
|
|
|
13902
|
|
|
13903 @item
|
|
|
13904 Peter Mutsaers---orphan article scoring code.
|
|
|
13905
|
|
|
13906 @item
|
|
|
13907 Ken Raeburn---POP mail support.
|
|
|
13908
|
|
|
13909 @item
|
|
|
13910 Hallvard B Furuseth---various bits and pieces, especially dealing with
|
|
|
13911 .newsrc files.
|
|
|
13912
|
|
|
13913 @item
|
|
|
13914 Brian Edmonds---@file{gnus-bbdb.el}.
|
|
|
13915
|
|
|
13916 @item
|
|
|
13917 David Moore---rewrite of @file{nnvirtual.el} and many other things.
|
|
|
13918
|
|
|
13919 @item
|
|
|
13920 Ricardo Nassif, Mark Borges, and Jost Krieger---proof-reading.
|
|
|
13921
|
|
|
13922 @item
|
|
|
13923 Kevin Davidson---came up with the name @dfn{ding}, so blame him.
|
|
|
13924
|
|
|
13925 @item
|
|
|
13926 François Pinard---many, many interesting and thorough bug reports.
|
|
0
|
13927
|
|
|
13928 @end itemize
|
|
|
13929
|
|
16
|
13930 The following people have contributed many patches and suggestions:
|
|
|
13931
|
|
|
13932 Christopher Davis,
|
|
|
13933 Andrew Eskilsson,
|
|
|
13934 Kai Grossjohann,
|
|
|
13935 David Kågedal,
|
|
|
13936 Richard Pieri,
|
|
|
13937 Fabrice Popineau,
|
|
|
13938 Daniel Quinlan,
|
|
|
13939 Jason L. Tibbitts, III,
|
|
|
13940 and
|
|
|
13941 Jack Vinson.
|
|
|
13942
|
|
|
13943 Also thanks to the following for patches and stuff:
|
|
|
13944
|
|
30
|
13945 Adrian Aichner,
|
|
16
|
13946 Peter Arius,
|
|
34
|
13947 Matt Armstrong,
|
|
16
|
13948 Marc Auslander,
|
|
|
13949 Chris Bone,
|
|
|
13950 Mark Borges,
|
|
|
13951 Lance A. Brown,
|
|
|
13952 Kees de Bruin,
|
|
|
13953 Martin Buchholz,
|
|
|
13954 Kevin Buhr,
|
|
|
13955 Alastair Burt,
|
|
|
13956 Joao Cachopo,
|
|
30
|
13957 Zlatko Calusic,
|
|
16
|
13958 Massimo Campostrini,
|
|
|
13959 Michael R. Cook,
|
|
|
13960 Glenn Coombs,
|
|
|
13961 Frank D. Cringle,
|
|
|
13962 Geoffrey T. Dairiki,
|
|
|
13963 Andre Deparade,
|
|
|
13964 Ulrik Dickow,
|
|
|
13965 Dave Disser,
|
|
|
13966 Joev Dubach,
|
|
|
13967 Paul Eggert,
|
|
|
13968 Michael Ernst,
|
|
|
13969 Luc Van Eycken,
|
|
|
13970 Sam Falkner,
|
|
|
13971 Paul Franklin,
|
|
|
13972 David S. Goldberg,
|
|
|
13973 D. Hall,
|
|
|
13974 Magnus Hammerin,
|
|
|
13975 Raja R. Harinath,
|
|
22
|
13976 Hisashige Kenji, @c Hisashige
|
|
16
|
13977 Marc Horowitz,
|
|
22
|
13978 François Felix Ingrand,
|
|
16
|
13979 Ishikawa Ichiro, @c Ishikawa
|
|
|
13980 Lee Iverson,
|
|
|
13981 Rajappa Iyer,
|
|
|
13982 Randell Jesup,
|
|
|
13983 Fred Johansen,
|
|
|
13984 Greg Klanderman,
|
|
30
|
13985 Karl Kleinpaste,
|
|
16
|
13986 Peter Skov Knudsen,
|
|
|
13987 Shuhei Kobayashi, @c Kobayashi
|
|
|
13988 Thor Kristoffersen,
|
|
|
13989 Jens Lautenbacher,
|
|
|
13990 Carsten Leonhardt,
|
|
30
|
13991 James LewisMoss,
|
|
16
|
13992 Christian Limpach,
|
|
|
13993 Markus Linnala,
|
|
|
13994 Dave Love,
|
|
|
13995 Tonny Madsen,
|
|
|
13996 Shlomo Mahlab,
|
|
|
13997 Nat Makarevitch,
|
|
30
|
13998 David Martin,
|
|
34
|
13999 Gordon Matzigkeit,
|
|
16
|
14000 Timo Metzemakers,
|
|
|
14001 Richard Mlynarik,
|
|
|
14002 Lantz Moore,
|
|
|
14003 Morioka Tomohiko, @c Morioka
|
|
|
14004 Erik Toubro Nielsen,
|
|
|
14005 Hrvoje Niksic,
|
|
|
14006 Andy Norman,
|
|
|
14007 C. R. Oldham,
|
|
|
14008 Alexandre Oliva,
|
|
|
14009 Ken Olstad,
|
|
|
14010 Masaharu Onishi, @c Onishi
|
|
|
14011 Hideki Ono, @c Ono
|
|
|
14012 William Perry,
|
|
|
14013 Stephen Peters,
|
|
|
14014 Ulrich Pfeifer,
|
|
|
14015 John McClary Prevost,
|
|
|
14016 Colin Rafferty,
|
|
|
14017 Bart Robinson,
|
|
|
14018 Jason Rumney,
|
|
|
14019 Loren Schall,
|
|
|
14020 Dan Schmidt,
|
|
|
14021 Ralph Schleicher,
|
|
34
|
14022 Philippe Schnoebelen,
|
|
16
|
14023 Randal L. Schwartz,
|
|
|
14024 Danny Siu,
|
|
|
14025 Paul D. Smith,
|
|
|
14026 Jeff Sparkes,
|
|
|
14027 Michael Sperber,
|
|
|
14028 Richard Stallman,
|
|
|
14029 Greg Stark,
|
|
|
14030 Paul Stodghill,
|
|
|
14031 Kurt Swanson,
|
|
|
14032 Samuel Tardieu,
|
|
|
14033 Teddy,
|
|
|
14034 Chuck Thompson,
|
|
|
14035 Philippe Troin,
|
|
|
14036 Jan Vroonhof,
|
|
|
14037 Barry A. Warsaw,
|
|
|
14038 Christoph Wedler,
|
|
|
14039 Joe Wells,
|
|
|
14040 and
|
|
|
14041 Katsumi Yamaoka. @c Yamaoka
|
|
|
14042
|
|
|
14043 For a full overview of what each person has done, the ChangeLogs
|
|
|
14044 included in the Gnus alpha distributions should give ample reading
|
|
|
14045 (550kB and counting).
|
|
|
14046
|
|
|
14047 Apologies to everybody that I've forgotten, of which there are many, I'm
|
|
|
14048 sure.
|
|
|
14049
|
|
|
14050 Gee, that's quite a list of people. I guess that must mean that there
|
|
|
14051 actually are people who are using Gnus. Who'd'a thunk it!
|
|
0
|
14052
|
|
|
14053
|
|
|
14054 @node New Features
|
|
|
14055 @subsection New Features
|
|
|
14056 @cindex new features
|
|
|
14057
|
|
16
|
14058 @menu
|
|
|
14059 * ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
|
|
|
14060 * September Gnus:: The Thing Formally Known As Gnus 5.3/5.3.
|
|
|
14061 * Red Gnus:: Third time best---Gnus 5.4/5.5.
|
|
|
14062 @end menu
|
|
|
14063
|
|
|
14064 These lists are, of course, just @emph{short} overviews of the
|
|
|
14065 @emph{most} important new features. No, really. There are tons more.
|
|
|
14066 Yes, we have feeping creaturism in full effect.
|
|
|
14067
|
|
|
14068
|
|
|
14069 @node ding Gnus
|
|
|
14070 @subsubsection (ding) Gnus
|
|
|
14071
|
|
|
14072 New features in Gnus 5.0/5.1:
|
|
|
14073
|
|
0
|
14074 @itemize @bullet
|
|
|
14075
|
|
|
14076 @item
|
|
|
14077 The look of all buffers can be changed by setting format-like variables
|
|
|
14078 (@pxref{Group Buffer Format} and @pxref{Summary Buffer Format}).
|
|
|
14079
|
|
|
14080 @item
|
|
|
14081 Local spool and several @sc{nntp} servers can be used at once
|
|
|
14082 (@pxref{Select Methods}).
|
|
|
14083
|
|
|
14084 @item
|
|
|
14085 You can combine groups into virtual groups (@pxref{Virtual Groups}).
|
|
|
14086
|
|
|
14087 @item
|
|
|
14088 You can read a number of different mail formats (@pxref{Getting Mail}).
|
|
|
14089 All the mail backends implement a convenient mail expiry scheme
|
|
|
14090 (@pxref{Expiring Mail}).
|
|
|
14091
|
|
|
14092 @item
|
|
|
14093 Gnus can use various strategies for gathering threads that have lost
|
|
|
14094 their roots (thereby gathering loose sub-threads into one thread) or it
|
|
|
14095 can go back and retrieve enough headers to build a complete thread
|
|
|
14096 (@pxref{Customizing Threading}).
|
|
|
14097
|
|
|
14098 @item
|
|
|
14099 Killed groups can be displayed in the group buffer, and you can read
|
|
|
14100 them as well (@pxref{Listing Groups}).
|
|
|
14101
|
|
|
14102 @item
|
|
|
14103 Gnus can do partial group updates---you do not have to retrieve the
|
|
|
14104 entire active file just to check for new articles in a few groups
|
|
|
14105 (@pxref{The Active File}).
|
|
|
14106
|
|
|
14107 @item
|
|
|
14108 Gnus implements a sliding scale of subscribedness to groups
|
|
|
14109 (@pxref{Group Levels}).
|
|
|
14110
|
|
|
14111 @item
|
|
|
14112 You can score articles according to any number of criteria
|
|
|
14113 (@pxref{Scoring}). You can even get Gnus to find out how to score
|
|
|
14114 articles for you (@pxref{Adaptive Scoring}).
|
|
|
14115
|
|
|
14116 @item
|
|
|
14117 Gnus maintains a dribble buffer that is auto-saved the normal Emacs
|
|
|
14118 manner, so it should be difficult to lose much data on what you have
|
|
|
14119 read if your machine should go down (@pxref{Auto Save}).
|
|
|
14120
|
|
|
14121 @item
|
|
|
14122 Gnus now has its own startup file (@file{.gnus}) to avoid cluttering up
|
|
|
14123 the @file{.emacs} file.
|
|
|
14124
|
|
|
14125 @item
|
|
|
14126 You can set the process mark on both groups and articles and perform
|
|
|
14127 operations on all the marked items (@pxref{Process/Prefix}).
|
|
|
14128
|
|
|
14129 @item
|
|
|
14130 You can grep through a subset of groups and create a group from the
|
|
|
14131 results (@pxref{Kibozed Groups}).
|
|
|
14132
|
|
|
14133 @item
|
|
|
14134 You can list subsets of groups according to, well, anything
|
|
|
14135 (@pxref{Listing Groups}).
|
|
|
14136
|
|
|
14137 @item
|
|
|
14138 You can browse foreign servers and subscribe to groups from those
|
|
|
14139 servers (@pxref{Browse Foreign Server}).
|
|
|
14140
|
|
|
14141 @item
|
|
|
14142 Gnus can fetch articles asynchronously on a second connection to the
|
|
|
14143 server (@pxref{Asynchronous Fetching}).
|
|
|
14144
|
|
|
14145 @item
|
|
|
14146 You can cache articles locally (@pxref{Article Caching}).
|
|
|
14147
|
|
|
14148 @item
|
|
|
14149 The uudecode functions have been expanded and generalized
|
|
|
14150 (@pxref{Decoding Articles}).
|
|
|
14151
|
|
|
14152 @item
|
|
|
14153 You can still post uuencoded articles, which was a little-known feature
|
|
|
14154 of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
|
|
|
14155
|
|
|
14156 @item
|
|
|
14157 Fetching parents (and other articles) now actually works without
|
|
|
14158 glitches (@pxref{Finding the Parent}).
|
|
|
14159
|
|
|
14160 @item
|
|
|
14161 Gnus can fetch FAQs and group descriptions (@pxref{Group Information}).
|
|
|
14162
|
|
|
14163 @item
|
|
|
14164 Digests (and other files) can be used as the basis for groups
|
|
|
14165 (@pxref{Document Groups}).
|
|
|
14166
|
|
|
14167 @item
|
|
|
14168 Articles can be highlighted and customized (@pxref{Customizing
|
|
|
14169 Articles}).
|
|
|
14170
|
|
|
14171 @item
|
|
|
14172 URLs and other external references can be buttonized (@pxref{Article
|
|
|
14173 Buttons}).
|
|
|
14174
|
|
|
14175 @item
|
|
|
14176 You can do lots of strange stuff with the Gnus window & frame
|
|
|
14177 configuration (@pxref{Windows Configuration}).
|
|
|
14178
|
|
|
14179 @item
|
|
|
14180 You can click on buttons instead of using the keyboard
|
|
|
14181 (@pxref{Buttons}).
|
|
|
14182
|
|
16
|
14183 @end itemize
|
|
|
14184
|
|
|
14185
|
|
|
14186 @node September Gnus
|
|
|
14187 @subsubsection September Gnus
|
|
|
14188
|
|
|
14189 New features in Gnus 5.2/5.3:
|
|
|
14190
|
|
|
14191 @itemize @bullet
|
|
|
14192
|
|
|
14193 @item
|
|
|
14194 A new message composition mode is used. All old customization variables
|
|
|
14195 for @code{mail-mode}, @code{rnews-reply-mode} and @code{gnus-msg} are
|
|
|
14196 now obsolete.
|
|
|
14197
|
|
|
14198 @item
|
|
|
14199 Gnus is now able to generate @dfn{sparse} threads---threads where
|
|
|
14200 missing articles are represented by empty nodes (@pxref{Customizing
|
|
|
14201 Threading}).
|
|
|
14202
|
|
|
14203 @lisp
|
|
|
14204 (setq gnus-build-sparse-threads 'some)
|
|
|
14205 @end lisp
|
|
|
14206
|
|
|
14207 @item
|
|
|
14208 Outgoing articles are stored on a special archive server
|
|
|
14209 (@pxref{Archived Messages}).
|
|
|
14210
|
|
|
14211 @item
|
|
|
14212 Partial thread regeneration now happens when articles are
|
|
|
14213 referred.
|
|
|
14214
|
|
|
14215 @item
|
|
|
14216 Gnus can make use of GroupLens predictions (@pxref{GroupLens}).
|
|
|
14217
|
|
|
14218 @item
|
|
|
14219 Picons (personal icons) can be displayed under XEmacs (@pxref{Picons}).
|
|
|
14220
|
|
|
14221 @item
|
|
|
14222 A @code{trn}-line tree buffer can be displayed (@pxref{Tree Display}).
|
|
|
14223
|
|
|
14224 @lisp
|
|
|
14225 (setq gnus-use-trees t)
|
|
|
14226 @end lisp
|
|
|
14227
|
|
|
14228 @item
|
|
|
14229 An @code{nn}-like pick-and-read minor mode is available for the summary
|
|
|
14230 buffers (@pxref{Pick and Read}).
|
|
|
14231
|
|
|
14232 @lisp
|
|
|
14233 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
|
|
|
14234 @end lisp
|
|
|
14235
|
|
|
14236 @item
|
|
|
14237 In binary groups you can use a special binary minor mode (@pxref{Binary
|
|
|
14238 Groups}).
|
|
|
14239
|
|
|
14240 @item
|
|
|
14241 Groups can be grouped in a folding topic hierarchy (@pxref{Group
|
|
|
14242 Topics}).
|
|
|
14243
|
|
|
14244 @lisp
|
|
|
14245 (add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
|
|
|
14246 @end lisp
|
|
|
14247
|
|
|
14248 @item
|
|
|
14249 Gnus can re-send and bounce mail (@pxref{Summary Mail Commands}).
|
|
|
14250
|
|
|
14251 @item
|
|
|
14252 Groups can now have a score, and bubbling based on entry frequency
|
|
|
14253 is possible (@pxref{Group Score}).
|
|
|
14254
|
|
|
14255 @lisp
|
|
|
14256 (add-hook 'gnus-summary-exit-hook 'gnus-summary-bubble-group)
|
|
|
14257 @end lisp
|
|
|
14258
|
|
|
14259 @item
|
|
|
14260 Groups can be process-marked, and commands can be performed on
|
|
|
14261 groups of groups (@pxref{Marking Groups}).
|
|
|
14262
|
|
|
14263 @item
|
|
|
14264 Caching is possible in virtual groups.
|
|
|
14265
|
|
|
14266 @item
|
|
|
14267 @code{nndoc} now understands all kinds of digests, mail boxes, rnews
|
|
|
14268 news batches, ClariNet briefs collections, and just about everything
|
|
|
14269 else (@pxref{Document Groups}).
|
|
|
14270
|
|
|
14271 @item
|
|
|
14272 Gnus has a new backend (@code{nnsoup}) to create/read SOUP packets
|
|
|
14273 (@pxref{SOUP}).
|
|
|
14274
|
|
|
14275 @item
|
|
|
14276 The Gnus cache is much faster.
|
|
|
14277
|
|
|
14278 @item
|
|
|
14279 Groups can be sorted according to many criteria (@pxref{Sorting
|
|
|
14280 Groups}).
|
|
|
14281
|
|
|
14282 @item
|
|
|
14283 New group parameters have been introduced to set list-address and
|
|
|
14284 expiry times (@pxref{Group Parameters}).
|
|
|
14285
|
|
|
14286 @item
|
|
|
14287 All formatting specs allow specifying faces to be used
|
|
|
14288 (@pxref{Formatting Fonts}).
|
|
|
14289
|
|
|
14290 @item
|
|
|
14291 There are several more commands for setting/removing/acting on process
|
|
|
14292 marked articles on the @kbd{M P} submap (@pxref{Setting Process Marks}).
|
|
|
14293
|
|
|
14294 @item
|
|
|
14295 The summary buffer can be limited to show parts of the available
|
|
|
14296 articles based on a wide range of criteria. These commands have been
|
|
|
14297 bound to keys on the @kbd{/} submap (@pxref{Limiting}).
|
|
|
14298
|
|
|
14299 @item
|
|
|
14300 Articles can be made persistent with the @kbd{*} command
|
|
|
14301 (@pxref{Persistent Articles}).
|
|
|
14302
|
|
|
14303 @item
|
|
|
14304 All functions for hiding article elements are now toggles.
|
|
|
14305
|
|
|
14306 @item
|
|
|
14307 Article headers can be buttonized (@pxref{Article Washing}).
|
|
|
14308
|
|
|
14309 @lisp
|
|
|
14310 (add-hook 'gnus-article-display-hook
|
|
|
14311 'gnus-article-add-buttons-to-head)
|
|
|
14312 @end lisp
|
|
|
14313
|
|
|
14314 @item
|
|
|
14315 All mail backends support fetching articles by @code{Message-ID}.
|
|
|
14316
|
|
|
14317 @item
|
|
|
14318 Duplicate mail can now be treated properly (@pxref{Duplicates}).
|
|
|
14319
|
|
|
14320 @item
|
|
|
14321 All summary mode commands are available directly from the article
|
|
|
14322 buffer (@pxref{Article Keymap}).
|
|
|
14323
|
|
|
14324 @item
|
|
|
14325 Frames can be part of @code{gnus-buffer-configuration} (@pxref{Windows
|
|
|
14326 Configuration}).
|
|
|
14327
|
|
|
14328 @item
|
|
|
14329 Mail can be re-scanned by a daemonic process (@pxref{Daemons}).
|
|
|
14330
|
|
|
14331 @item
|
|
|
14332 Gnus can make use of NoCeM files to weed out spam (@pxref{NoCeM}).
|
|
|
14333
|
|
|
14334 @lisp
|
|
|
14335 (setq gnus-use-nocem t)
|
|
|
14336 @end lisp
|
|
|
14337
|
|
|
14338 @item
|
|
|
14339 Groups can be made permanently visible (@pxref{Listing Groups}).
|
|
|
14340
|
|
|
14341 @lisp
|
|
|
14342 (setq gnus-permanently-visible-groups "^nnml:")
|
|
|
14343 @end lisp
|
|
|
14344
|
|
|
14345 @item
|
|
|
14346 Many new hooks have been introduced to make customizing easier.
|
|
|
14347
|
|
|
14348 @item
|
|
|
14349 Gnus respects the @code{Mail-Copies-To} header.
|
|
|
14350
|
|
|
14351 @item
|
|
|
14352 Threads can be gathered by looking at the @code{References} header
|
|
|
14353 (@pxref{Customizing Threading}).
|
|
|
14354
|
|
|
14355 @lisp
|
|
|
14356 (setq gnus-summary-thread-gathering-function
|
|
|
14357 'gnus-gather-threads-by-references)
|
|
|
14358 @end lisp
|
|
|
14359
|
|
|
14360 @item
|
|
|
14361 Read articles can be stored in a special backlog buffer to avoid
|
|
|
14362 refetching (@pxref{Article Backlog}).
|
|
|
14363
|
|
|
14364 @lisp
|
|
|
14365 (setq gnus-keep-backlog 50)
|
|
|
14366 @end lisp
|
|
|
14367
|
|
|
14368 @item
|
|
|
14369 A clean copy of the current article is always stored in a separate
|
|
|
14370 buffer to allow easier treatment.
|
|
|
14371
|
|
|
14372 @item
|
|
|
14373 Gnus can suggest where to save articles (@pxref{Saving Articles}).
|
|
|
14374
|
|
|
14375 @item
|
|
|
14376 Gnus doesn't have to do as much prompting when saving (@pxref{Saving
|
|
|
14377 Articles}).
|
|
|
14378
|
|
|
14379 @lisp
|
|
|
14380 (setq gnus-prompt-before-saving t)
|
|
|
14381 @end lisp
|
|
|
14382
|
|
|
14383 @item
|
|
|
14384 @code{gnus-uu} can view decoded files asynchronously while fetching
|
|
|
14385 articles (@pxref{Other Decode Variables}).
|
|
|
14386
|
|
|
14387 @lisp
|
|
|
14388 (setq gnus-uu-grabbed-file-functions 'gnus-uu-grab-view)
|
|
|
14389 @end lisp
|
|
|
14390
|
|
|
14391 @item
|
|
|
14392 Filling in the article buffer now works properly on cited text
|
|
|
14393 (@pxref{Article Washing}).
|
|
|
14394
|
|
|
14395 @item
|
|
|
14396 Hiding cited text adds buttons to toggle hiding, and how much
|
|
|
14397 cited text to hide is now customizable (@pxref{Article Hiding}).
|
|
|
14398
|
|
|
14399 @lisp
|
|
|
14400 (setq gnus-cited-lines-visible 2)
|
|
|
14401 @end lisp
|
|
|
14402
|
|
|
14403 @item
|
|
|
14404 Boring headers can be hidden (@pxref{Article Hiding}).
|
|
|
14405
|
|
|
14406 @lisp
|
|
|
14407 (add-hook 'gnus-article-display-hook
|
|
|
14408 'gnus-article-hide-boring-headers t)
|
|
|
14409 @end lisp
|
|
|
14410
|
|
|
14411 @item
|
|
|
14412 Default scoring values can now be set from the menu bar.
|
|
|
14413
|
|
|
14414 @item
|
|
|
14415 Further syntax checking of outgoing articles have been added.
|
|
0
|
14416
|
|
|
14417 @end itemize
|
|
|
14418
|
|
16
|
14419
|
|
|
14420 @node Red Gnus
|
|
|
14421 @subsubsection Red Gnus
|
|
|
14422
|
|
|
14423 New features in Gnus 5.4/5.5:
|
|
|
14424
|
|
|
14425 @itemize @bullet
|
|
|
14426
|
|
|
14427 @item
|
|
|
14428 @file{nntp.el} has been totally rewritten in an asynchronous fashion.
|
|
|
14429
|
|
|
14430 @item
|
|
|
14431 Article prefetching functionality has been moved up into
|
|
|
14432 Gnus (@pxref{Asynchronous Fetching}).
|
|
|
14433
|
|
|
14434 @item
|
|
|
14435 Scoring can now be performed with logical operators like @code{and},
|
|
|
14436 @code{or}, @code{not}, and parent redirection (@pxref{Advanced
|
|
|
14437 Scoring}).
|
|
|
14438
|
|
|
14439 @item
|
|
|
14440 Article washing status can be displayed in the
|
|
|
14441 article mode line (@pxref{Misc Article}).
|
|
|
14442
|
|
|
14443 @item
|
|
|
14444 @file{gnus.el} has been split into many smaller files.
|
|
|
14445
|
|
|
14446 @item
|
|
|
14447 Suppression of duplicate articles based on Message-ID can be done
|
|
|
14448 (@pxref{Duplicate Suppression}).
|
|
|
14449
|
|
|
14450 @lisp
|
|
|
14451 (setq gnus-suppress-duplicates t)
|
|
|
14452 @end lisp
|
|
|
14453
|
|
|
14454 @item
|
|
|
14455 New variables for specifying what score and adapt files are to be
|
|
|
14456 considered home score and adapt files (@pxref{Home Score File}).
|
|
|
14457
|
|
|
14458 @item
|
|
|
14459 @code{nndoc} was rewritten to be easily extendable (@pxref{Document
|
|
|
14460 Server Internals}).
|
|
|
14461
|
|
|
14462 @item
|
|
|
14463 Groups can inherit group parameters from parent topics (@pxref{Topic
|
|
|
14464 Parameters}).
|
|
|
14465
|
|
|
14466 @item
|
|
|
14467 Article editing has been revamped and is now actually usable.
|
|
|
14468
|
|
|
14469 @item
|
|
|
14470 Signatures can be recognized in more intelligent fashions
|
|
|
14471 (@pxref{Article Signature}).
|
|
|
14472
|
|
|
14473 @item
|
|
|
14474 Summary pick mode has been made to look more @code{nn}-like. Line
|
|
|
14475 numbers are displayed and the @kbd{.} command can be used to pick
|
|
|
14476 articles (@code{Pick and Read}).
|
|
|
14477
|
|
|
14478 @item
|
|
|
14479 Commands for moving the @file{.newsrc.eld} from one server to
|
|
|
14480 another have been added (@pxref{Changing Servers}).
|
|
|
14481
|
|
|
14482 @item
|
|
|
14483 A way to specify that ``uninteresting'' fields be suppressed when
|
|
|
14484 generating lines in buffers (@pxref{Advanced Formatting}).
|
|
|
14485
|
|
|
14486 @item
|
|
|
14487 Several commands in the group buffer can be undone with @kbd{M-C-_}
|
|
|
14488 (@pxref{Undo}).
|
|
|
14489
|
|
|
14490 @item
|
|
|
14491 Scoring can be done on words using the new score type @code{w}
|
|
|
14492 (@pxref{Score File Format}).
|
|
|
14493
|
|
|
14494 @item
|
|
|
14495 Adaptive scoring can be done on a Subject word-by-word basis
|
|
|
14496 (@pxref{Adaptive Scoring}).
|
|
|
14497
|
|
|
14498 @lisp
|
|
|
14499 (setq gnus-use-adaptive-scoring '(word))
|
|
|
14500 @end lisp
|
|
|
14501
|
|
|
14502 @item
|
|
|
14503 Scores can be decayed (@pxref{Score Decays}).
|
|
|
14504
|
|
|
14505 @lisp
|
|
|
14506 (setq gnus-decay-scores t)
|
|
|
14507 @end lisp
|
|
|
14508
|
|
|
14509 @item
|
|
|
14510 Scoring can be performed using a regexp on the Date header. The Date is
|
|
|
14511 normalized to compact ISO 8601 format first (@pxref{Score File Format}).
|
|
|
14512
|
|
|
14513 @item
|
|
|
14514 A new command has been added to remove all data on articles from
|
|
|
14515 the native server (@pxref{Changing Servers}).
|
|
|
14516
|
|
|
14517 @item
|
|
|
14518 A new command for reading collections of documents
|
|
|
14519 (@code{nndoc} with @code{nnvirtual} on top) has been added---@kbd{M-C-d}
|
|
|
14520 (@pxref{Really Various Summary Commands}).
|
|
|
14521
|
|
|
14522 @item
|
|
|
14523 Process mark sets can be pushed and popped (@pxref{Setting Process
|
|
|
14524 Marks}).
|
|
|
14525
|
|
|
14526 @item
|
|
|
14527 A new mail-to-news backend makes it possible to post even when the NNTP
|
|
|
14528 server doesn't allow posting (@pxref{Mail-To-News Gateways}).
|
|
|
14529
|
|
|
14530 @item
|
|
|
14531 A new backend for reading searches from Web search engines
|
|
|
14532 (@dfn{DejaNews}, @dfn{Alta Vista}, @dfn{InReference}) has been added
|
|
|
14533 (@pxref{Web Searches}).
|
|
|
14534
|
|
|
14535 @item
|
|
|
14536 Groups inside topics can now be sorted using the standard sorting
|
|
|
14537 functions, and each topic can be sorted independently (@pxref{Topic
|
|
|
14538 Sorting}).
|
|
|
14539
|
|
|
14540 @item
|
|
|
14541 Subsets of the groups can be sorted independently (@code{Sorting
|
|
|
14542 Groups}).
|
|
|
14543
|
|
|
14544 @item
|
|
|
14545 Cached articles can be pulled into the groups (@pxref{Summary Generation
|
|
|
14546 Commands}).
|
|
|
14547
|
|
|
14548 @item
|
|
|
14549 Score files are now applied in a more reliable order (@pxref{Score
|
|
|
14550 Variables}).
|
|
|
14551
|
|
|
14552 @item
|
|
|
14553 Reports on where mail messages end up can be generated (@pxref{Splitting
|
|
|
14554 Mail}).
|
|
|
14555
|
|
|
14556 @item
|
|
|
14557 More hooks and functions have been added to remove junk from incoming
|
|
|
14558 mail before saving the mail (@pxref{Washing Mail}).
|
|
|
14559
|
|
|
14560 @item
|
|
|
14561 Emphasized text can be properly fontisized:
|
|
|
14562
|
|
|
14563 @lisp
|
|
|
14564 (add-hook 'gnus-article-display-hook 'gnus-article-emphasize)
|
|
|
14565 @end lisp
|
|
|
14566
|
|
|
14567 @end itemize
|
|
0
|
14568
|
|
|
14569
|
|
|
14570 @node Newest Features
|
|
|
14571 @subsection Newest Features
|
|
|
14572 @cindex todo
|
|
|
14573
|
|
|
14574 Also known as the @dfn{todo list}. Sure to be implemented before the
|
|
|
14575 next millennium.
|
|
|
14576
|
|
|
14577 Be afraid. Be very afraid.
|
|
|
14578
|
|
|
14579 @itemize @bullet
|
|
|
14580 @item
|
|
|
14581 Native @sc{mime} support is something that should be done.
|
|
|
14582 @item
|
|
|
14583 Really do unbinhexing.
|
|
|
14584 @end itemize
|
|
|
14585
|
|
|
14586 And much, much, much more. There is more to come than has already been
|
|
|
14587 implemented. (But that's always true, isn't it?)
|
|
|
14588
|
|
16
|
14589 @file{<URL:http://www.ifi.uio.no/~larsi/rgnus/todo>} is where the actual
|
|
0
|
14590 up-to-the-second todo list is located, so if you're really curious, you
|
|
|
14591 could point your Web browser over that-a-way.
|
|
|
14592
|
|
16
|
14593 @iftex
|
|
|
14594
|
|
|
14595 @node The Manual
|
|
|
14596 @section The Manual
|
|
|
14597 @cindex colophon
|
|
|
14598 @cindex manual
|
|
|
14599
|
|
|
14600 This manual was generated from a TeXinfo file and then run through
|
|
|
14601 either @code{texi2dvi}
|
|
|
14602 @iflatex
|
|
|
14603 or my own home-brewed TeXinfo to \LaTeX\ transformer,
|
|
|
14604 and then run through @code{latex} and @code{dvips}
|
|
|
14605 @end iflatex
|
|
|
14606 to get what you hold in your hands now.
|
|
|
14607
|
|
|
14608 The following conventions have been used:
|
|
|
14609
|
|
|
14610 @enumerate
|
|
|
14611
|
|
|
14612 @item
|
|
|
14613 This is a @samp{string}
|
|
|
14614
|
|
|
14615 @item
|
|
|
14616 This is a @kbd{keystroke}
|
|
|
14617
|
|
|
14618 @item
|
|
|
14619 This is a @file{file}
|
|
|
14620
|
|
|
14621 @item
|
|
|
14622 This is a @code{symbol}
|
|
|
14623
|
|
|
14624 @end enumerate
|
|
|
14625
|
|
|
14626 So if I were to say ``set @code{flargnoze} to @samp{yes}'', that would
|
|
|
14627 mean:
|
|
|
14628
|
|
|
14629 @lisp
|
|
|
14630 (setq flargnoze "yes")
|
|
|
14631 @end lisp
|
|
|
14632
|
|
|
14633 If I say ``set @code{flumphel} to @code{yes}'', that would mean:
|
|
|
14634
|
|
|
14635 @lisp
|
|
|
14636 (setq flumphel 'yes)
|
|
|
14637 @end lisp
|
|
|
14638
|
|
|
14639 @samp{yes} and @code{yes} are two @emph{very} different things---don't
|
|
|
14640 ever get them confused.
|
|
|
14641
|
|
|
14642 @iflatex
|
|
|
14643 @c @head
|
|
|
14644 Of course, everything in this manual is of vital interest, so you should
|
|
|
14645 read it all. Several times. However, if you feel like skimming the
|
|
|
14646 manual, look for that gnu head you should see in the margin over
|
|
|
14647 there---it means that what's being discussed is of more importance than
|
|
|
14648 the rest of the stuff. (On the other hand, if everything is infinitely
|
|
|
14649 important, how can anything be more important than that? Just one more
|
|
|
14650 of the mysteries of this world, I guess.)
|
|
|
14651 @end iflatex
|
|
|
14652
|
|
|
14653 @end iftex
|
|
|
14654
|
|
0
|
14655
|
|
|
14656 @node Terminology
|
|
|
14657 @section Terminology
|
|
|
14658
|
|
|
14659 @cindex terminology
|
|
|
14660 @table @dfn
|
|
|
14661
|
|
|
14662 @item news
|
|
|
14663 @cindex news
|
|
|
14664 This is what you are supposed to use this thing for---reading news.
|
|
|
14665 News is generally fetched from a nearby @sc{nntp} server, and is
|
|
|
14666 generally publicly available to everybody. If you post news, the entire
|
|
|
14667 world is likely to read just what you have written, and they'll all
|
|
|
14668 snigger mischievously. Behind your back.
|
|
|
14669
|
|
|
14670 @item mail
|
|
|
14671 @cindex mail
|
|
|
14672 Everything that's delivered to you personally is mail. Some news/mail
|
|
|
14673 readers (like Gnus) blur the distinction between mail and news, but
|
|
|
14674 there is a difference. Mail is private. News is public. Mailing is
|
|
|
14675 not posting, and replying is not following up.
|
|
|
14676
|
|
|
14677 @item reply
|
|
|
14678 @cindex reply
|
|
|
14679 Send a mail to the person who has written what you are reading.
|
|
|
14680
|
|
|
14681 @item follow up
|
|
|
14682 @cindex follow up
|
|
|
14683 Post an article to the current newsgroup responding to the article you
|
|
|
14684 are reading.
|
|
|
14685
|
|
|
14686 @item backend
|
|
|
14687 @cindex backend
|
|
|
14688 Gnus gets fed articles from a number of backends, both news and mail
|
|
|
14689 backends. Gnus does not handle the underlying media, so to speak---this
|
|
|
14690 is all done by the backends.
|
|
|
14691
|
|
|
14692 @item native
|
|
|
14693 @cindex native
|
|
|
14694 Gnus will always use one method (and backend) as the @dfn{native}, or
|
|
|
14695 default, way of getting news.
|
|
|
14696
|
|
|
14697 @item foreign
|
|
|
14698 @cindex foreign
|
|
|
14699 You can also have any number of foreign groups active at the same time.
|
|
|
14700 These are groups that use different backends for getting news.
|
|
|
14701
|
|
|
14702 @item secondary
|
|
|
14703 @cindex secondary
|
|
|
14704 Secondary backends are somewhere half-way between being native and being
|
|
|
14705 foreign, but they mostly act like they are native.
|
|
|
14706
|
|
|
14707 @item article
|
|
|
14708 @cindex article
|
|
16
|
14709 A message that has been posted as news.
|
|
0
|
14710
|
|
|
14711 @item mail message
|
|
|
14712 @cindex mail message
|
|
|
14713 A message that has been mailed.
|
|
|
14714
|
|
|
14715 @item message
|
|
|
14716 @cindex message
|
|
|
14717 A mail message or news article
|
|
|
14718
|
|
|
14719 @item head
|
|
|
14720 @cindex head
|
|
|
14721 The top part of a message, where administrative information (etc.) is
|
|
|
14722 put.
|
|
|
14723
|
|
|
14724 @item body
|
|
|
14725 @cindex body
|
|
|
14726 The rest of an article. Everything that is not in the head is in the
|
|
|
14727 body.
|
|
|
14728
|
|
|
14729 @item header
|
|
|
14730 @cindex header
|
|
|
14731 A line from the head of an article.
|
|
|
14732
|
|
|
14733 @item headers
|
|
|
14734 @cindex headers
|
|
|
14735 A collection of such lines, or a collection of heads. Or even a
|
|
|
14736 collection of @sc{nov} lines.
|
|
|
14737
|
|
|
14738 @item @sc{nov}
|
|
|
14739 @cindex nov
|
|
|
14740 When Gnus enters a group, it asks the backend for the headers of all
|
|
|
14741 unread articles in the group. Most servers support the News OverView
|
|
|
14742 format, which is more compact and much faster to read and parse than the
|
|
|
14743 normal @sc{head} format.
|
|
|
14744
|
|
|
14745 @item level
|
|
|
14746 @cindex levels
|
|
|
14747 Each group is subscribed at some @dfn{level} or other (1-9). The ones
|
|
|
14748 that have a lower level are ``more'' subscribed than the groups with a
|
|
|
14749 higher level. In fact, groups on levels 1-5 are considered
|
|
|
14750 @dfn{subscribed}; 6-7 are @dfn{unsubscribed}; 8 are @dfn{zombies}; and 9
|
|
|
14751 are @dfn{killed}. Commands for listing groups and scanning for new
|
|
|
14752 articles will all use the numeric prefix as @dfn{working level}.
|
|
|
14753
|
|
|
14754 @item killed groups
|
|
|
14755 @cindex killed groups
|
|
|
14756 No information on killed groups is stored or updated, which makes killed
|
|
|
14757 groups much easier to handle than subscribed groups.
|
|
|
14758
|
|
|
14759 @item zombie groups
|
|
|
14760 @cindex zombie groups
|
|
|
14761 Just like killed groups, only slightly less dead.
|
|
|
14762
|
|
|
14763 @item active file
|
|
|
14764 @cindex active file
|
|
|
14765 The news server has to keep track of what articles it carries, and what
|
|
|
14766 groups exist. All this information in stored in the active file, which
|
|
|
14767 is rather large, as you might surmise.
|
|
|
14768
|
|
|
14769 @item bogus groups
|
|
|
14770 @cindex bogus groups
|
|
|
14771 A group that exists in the @file{.newsrc} file, but isn't known to the
|
|
16
|
14772 server (i.e., it isn't in the active file), is a @emph{bogus group}.
|
|
0
|
14773 This means that the group probably doesn't exist (any more).
|
|
|
14774
|
|
|
14775 @item server
|
|
|
14776 @cindex server
|
|
|
14777 A machine than one can connect to and get news (or mail) from.
|
|
|
14778
|
|
|
14779 @item select method
|
|
|
14780 @cindex select method
|
|
|
14781 A structure that specifies the backend, the server and the virtual
|
|
|
14782 server parameters.
|
|
|
14783
|
|
|
14784 @item virtual server
|
|
|
14785 @cindex virtual server
|
|
|
14786 A named select method. Since a select methods defines all there is to
|
|
16
|
14787 know about connecting to a (physical) server, taking the things as a
|
|
0
|
14788 whole is a virtual server.
|
|
|
14789
|
|
16
|
14790 @item washing
|
|
|
14791 @cindex washing
|
|
|
14792 Taking a buffer and running it through a filter of some sort. The
|
|
|
14793 result will (more often than not) be cleaner and more pleasing than the
|
|
|
14794 original.
|
|
|
14795
|
|
|
14796 @item ephemeral groups
|
|
|
14797 @cindex ephemeral groups
|
|
|
14798 Most groups store data on what articles you have read. @dfn{Ephemeral}
|
|
|
14799 groups are groups that will have no data stored---when you exit the
|
|
|
14800 group, it'll disappear into the aether.
|
|
|
14801
|
|
|
14802 @item solid groups
|
|
|
14803 @cindex solid groups
|
|
|
14804 This is the opposite of ephemeral groups. All groups listed in the
|
|
|
14805 group buffer are solid groups.
|
|
|
14806
|
|
|
14807 @item sparse articles
|
|
|
14808 @cindex sparse articles
|
|
|
14809 These are article placeholders shown in the summary buffer when
|
|
|
14810 @code{gnus-build-sparse-threads} has been switched on.
|
|
|
14811
|
|
0
|
14812 @end table
|
|
|
14813
|
|
|
14814
|
|
|
14815 @node Customization
|
|
|
14816 @section Customization
|
|
|
14817 @cindex general customization
|
|
|
14818
|
|
|
14819 All variables are properly documented elsewhere in this manual. This
|
|
|
14820 section is designed to give general pointers on how to customize Gnus
|
|
|
14821 for some quite common situations.
|
|
|
14822
|
|
|
14823 @menu
|
|
|
14824 * Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
|
|
|
14825 * Slow Terminal Connection:: You run a remote Emacs.
|
|
|
14826 * Little Disk Space:: You feel that having large setup files is icky.
|
|
|
14827 * Slow Machine:: You feel like buying a faster machine.
|
|
|
14828 @end menu
|
|
|
14829
|
|
|
14830
|
|
|
14831 @node Slow/Expensive Connection
|
|
|
14832 @subsection Slow/Expensive @sc{nntp} Connection
|
|
|
14833
|
|
|
14834 If you run Emacs on a machine locally, and get your news from a machine
|
|
|
14835 over some very thin strings, you want to cut down on the amount of data
|
|
|
14836 Gnus has to get from the @sc{nntp} server.
|
|
|
14837
|
|
|
14838 @table @code
|
|
|
14839
|
|
|
14840 @item gnus-read-active-file
|
|
|
14841 Set this to @code{nil}, which will inhibit Gnus from requesting the
|
|
|
14842 entire active file from the server. This file is often v. large. You
|
|
16
|
14843 also have to set @code{gnus-check-new-newsgroups} and
|
|
0
|
14844 @code{gnus-check-bogus-newsgroups} to @code{nil} to make sure that Gnus
|
|
|
14845 doesn't suddenly decide to fetch the active file anyway.
|
|
|
14846
|
|
|
14847 @item gnus-nov-is-evil
|
|
|
14848 This one has to be @code{nil}. If not, grabbing article headers from
|
|
|
14849 the @sc{nntp} server will not be very fast. Not all @sc{nntp} servers
|
|
|
14850 support @sc{xover}; Gnus will detect this by itself.
|
|
|
14851 @end table
|
|
|
14852
|
|
|
14853
|
|
|
14854 @node Slow Terminal Connection
|
|
|
14855 @subsection Slow Terminal Connection
|
|
|
14856
|
|
|
14857 Let's say you use your home computer for dialing up the system that
|
|
|
14858 runs Emacs and Gnus. If your modem is slow, you want to reduce the
|
|
|
14859 amount of data that is sent over the wires as much as possible.
|
|
|
14860
|
|
|
14861 @table @code
|
|
|
14862
|
|
|
14863 @item gnus-auto-center-summary
|
|
|
14864 Set this to @code{nil} to inhibit Gnus from re-centering the summary
|
|
|
14865 buffer all the time. If it is @code{vertical}, do only vertical
|
|
|
14866 re-centering. If it is neither @code{nil} nor @code{vertical}, do both
|
|
|
14867 horizontal and vertical recentering.
|
|
|
14868
|
|
|
14869 @item gnus-visible-headers
|
|
|
14870 Cut down on the headers that are included in the articles to the
|
|
|
14871 minimum. You can, in fact, make do without them altogether---most of the
|
|
|
14872 useful data is in the summary buffer, anyway. Set this variable to
|
|
|
14873 @samp{^NEVVVVER} or @samp{From:}, or whatever you feel you need.
|
|
|
14874
|
|
|
14875 @item gnus-article-display-hook
|
|
|
14876 Set this hook to all the available hiding commands:
|
|
|
14877 @lisp
|
|
|
14878 (setq gnus-article-display-hook
|
|
|
14879 '(gnus-article-hide-headers gnus-article-hide-signature
|
|
|
14880 gnus-article-hide-citation))
|
|
|
14881 @end lisp
|
|
|
14882
|
|
|
14883 @item gnus-use-full-window
|
|
|
14884 By setting this to @code{nil}, you can make all the windows smaller.
|
|
|
14885 While this doesn't really cut down much generally, it means that you
|
|
|
14886 have to see smaller portions of articles before deciding that you didn't
|
|
|
14887 want to read them anyway.
|
|
|
14888
|
|
|
14889 @item gnus-thread-hide-subtree
|
|
|
14890 If this is non-@code{nil}, all threads in the summary buffer will be
|
|
|
14891 hidden initially.
|
|
|
14892
|
|
|
14893 @item gnus-updated-mode-lines
|
|
|
14894 If this is @code{nil}, Gnus will not put information in the buffer mode
|
|
|
14895 lines, which might save some time.
|
|
|
14896 @end table
|
|
|
14897
|
|
|
14898
|
|
|
14899 @node Little Disk Space
|
|
|
14900 @subsection Little Disk Space
|
|
|
14901 @cindex disk space
|
|
|
14902
|
|
|
14903 The startup files can get rather large, so you may want to cut their
|
|
|
14904 sizes a bit if you are running out of space.
|
|
|
14905
|
|
|
14906 @table @code
|
|
|
14907
|
|
|
14908 @item gnus-save-newsrc-file
|
|
|
14909 If this is @code{nil}, Gnus will never save @file{.newsrc}---it will
|
|
|
14910 only save @file{.newsrc.eld}. This means that you will not be able to
|
|
|
14911 use any other newsreaders than Gnus. This variable is @code{t} by
|
|
|
14912 default.
|
|
|
14913
|
|
|
14914 @item gnus-save-killed-list
|
|
|
14915 If this is @code{nil}, Gnus will not save the list of dead groups. You
|
|
|
14916 should also set @code{gnus-check-new-newsgroups} to @code{ask-server}
|
|
|
14917 and @code{gnus-check-bogus-newsgroups} to @code{nil} if you set this
|
|
|
14918 variable to @code{nil}. This variable is @code{t} by default.
|
|
|
14919
|
|
|
14920 @end table
|
|
|
14921
|
|
|
14922
|
|
|
14923 @node Slow Machine
|
|
|
14924 @subsection Slow Machine
|
|
|
14925 @cindex slow machine
|
|
|
14926
|
|
|
14927 If you have a slow machine, or are just really impatient, there are a
|
|
|
14928 few things you can do to make Gnus run faster.
|
|
|
14929
|
|
|
14930 Set@code{gnus-check-new-newsgroups} and
|
|
|
14931 @code{gnus-check-bogus-newsgroups} to @code{nil} to make startup faster.
|
|
|
14932
|
|
|
14933 Set @code{gnus-show-threads}, @code{gnus-use-cross-reference} and
|
|
|
14934 @code{gnus-nov-is-evil} to @code{nil} to make entering and exiting the
|
|
|
14935 summary buffer faster.
|
|
|
14936
|
|
|
14937 Set @code{gnus-article-display-hook} to @code{nil} to make article
|
|
|
14938 processing a bit faster.
|
|
|
14939
|
|
|
14940
|
|
|
14941 @node Troubleshooting
|
|
|
14942 @section Troubleshooting
|
|
|
14943 @cindex troubleshooting
|
|
|
14944
|
|
|
14945 Gnus works @emph{so} well straight out of the box---I can't imagine any
|
|
|
14946 problems, really.
|
|
|
14947
|
|
|
14948 Ahem.
|
|
|
14949
|
|
|
14950 @enumerate
|
|
|
14951
|
|
|
14952 @item
|
|
|
14953 Make sure your computer is switched on.
|
|
|
14954
|
|
|
14955 @item
|
|
|
14956 Make sure that you really load the current Gnus version. If you have
|
|
|
14957 been running @sc{gnus}, you need to exit Emacs and start it up again before
|
|
|
14958 Gnus will work.
|
|
|
14959
|
|
|
14960 @item
|
|
|
14961 Try doing an @kbd{M-x gnus-version}. If you get something that looks
|
|
|
14962 like @samp{Gnus v5.46; nntp 4.0} you have the right files loaded. If,
|
|
|
14963 on the other hand, you get something like @samp{NNTP 3.x} or @samp{nntp
|
|
|
14964 flee}, you have some old @file{.el} files lying around. Delete these.
|
|
|
14965
|
|
|
14966 @item
|
|
|
14967 Read the help group (@kbd{G h} in the group buffer) for a FAQ and a
|
|
|
14968 how-to.
|
|
16
|
14969
|
|
|
14970 @item
|
|
|
14971 @vindex max-lisp-eval-depth
|
|
|
14972 Gnus works on many recursive structures, and in some extreme (and very
|
|
|
14973 rare) cases Gnus may recurse down ``too deeply'' and Emacs will beep at
|
|
|
14974 you. If this happens to you, set @code{max-lisp-eval-depth} to 500 or
|
|
|
14975 something like that.
|
|
0
|
14976 @end enumerate
|
|
|
14977
|
|
|
14978 If all else fails, report the problem as a bug.
|
|
|
14979
|
|
|
14980 @cindex bugs
|
|
|
14981 @cindex reporting bugs
|
|
|
14982
|
|
|
14983 @kindex M-x gnus-bug
|
|
|
14984 @findex gnus-bug
|
|
|
14985 If you find a bug in Gnus, you can report it with the @kbd{M-x gnus-bug}
|
|
|
14986 command. @kbd{M-x set-variable RET debug-on-error RET t RET}, and send
|
|
|
14987 me the backtrace. I will fix bugs, but I can only fix them if you send
|
|
|
14988 me a precise description as to how to reproduce the bug.
|
|
|
14989
|
|
|
14990 You really can never be too detailed in a bug report. Always use the
|
|
|
14991 @kbd{M-x gnus-bug} command when you make bug reports, even if it creates
|
|
|
14992 a 10Kb mail each time you use it, and even if you have sent me your
|
|
|
14993 environment 500 times before. I don't care. I want the full info each
|
|
|
14994 time.
|
|
|
14995
|
|
|
14996 It is also important to remember that I have no memory whatsoever. If
|
|
|
14997 you send a bug report, and I send you a reply, and then you send back
|
|
|
14998 just ``No, it's not! Moron!'', I will have no idea what you are
|
|
|
14999 insulting me about. Always over-explain everything. It's much easier
|
|
|
15000 for all of us---if I don't have all the information I need, I will just
|
|
|
15001 mail you and ask for more info, and everything takes more time.
|
|
|
15002
|
|
|
15003 If the problem you're seeing is very visual, and you can't quite explain
|
|
|
15004 it, copy the Emacs window to a file (with @code{xwd}, for instance), put
|
|
|
15005 it somewhere it can be reached, and include the URL of the picture in
|
|
16
|
15006 the bug report.
|
|
0
|
15007
|
|
|
15008 If you just need help, you are better off asking on
|
|
|
15009 @samp{gnu.emacs.gnus}. I'm not very helpful.
|
|
|
15010
|
|
|
15011 @cindex gnu.emacs.gnus
|
|
|
15012 @cindex ding mailing list
|
|
|
15013 You can also ask on the ding mailing list---@samp{ding@@ifi.uio.no}.
|
|
|
15014 Write to @samp{ding-request@@ifi.uio.no} to subscribe.
|
|
|
15015
|
|
|
15016
|
|
|
15017 @node A Programmers Guide to Gnus
|
|
16
|
15018 @section A Programmer@'s Guide to Gnus
|
|
0
|
15019
|
|
|
15020 It is my hope that other people will figure out smart stuff that Gnus
|
|
|
15021 can do, and that other people will write those smart things as well. To
|
|
|
15022 facilitate that I thought it would be a good idea to describe the inner
|
|
|
15023 workings of Gnus. And some of the not-so-inner workings, while I'm at
|
|
|
15024 it.
|
|
|
15025
|
|
|
15026 You can never expect the internals of a program not to change, but I
|
|
|
15027 will be defining (in some details) the interface between Gnus and its
|
|
|
15028 backends (this is written in stone), the format of the score files
|
|
|
15029 (ditto), data structures (some are less likely to change than others)
|
|
|
15030 and general method of operations.
|
|
|
15031
|
|
|
15032 @menu
|
|
|
15033 * Backend Interface:: How Gnus communicates with the servers.
|
|
|
15034 * Score File Syntax:: A BNF definition of the score file standard.
|
|
|
15035 * Headers:: How Gnus stores headers internally.
|
|
|
15036 * Ranges:: A handy format for storing mucho numbers.
|
|
|
15037 * Group Info:: The group info format.
|
|
|
15038 * Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
|
|
|
15039 * Various File Formats:: Formats of files that Gnus use.
|
|
|
15040 @end menu
|
|
|
15041
|
|
|
15042
|
|
|
15043 @node Backend Interface
|
|
|
15044 @subsection Backend Interface
|
|
|
15045
|
|
|
15046 Gnus doesn't know anything about @sc{nntp}, spools, mail or virtual
|
|
|
15047 groups. It only knows how to talk to @dfn{virtual servers}. A virtual
|
|
|
15048 server is a @dfn{backend} and some @dfn{backend variables}. As examples
|
|
|
15049 of the first, we have @code{nntp}, @code{nnspool} and @code{nnmbox}. As
|
|
|
15050 examples of the latter we have @code{nntp-port-number} and
|
|
|
15051 @code{nnmbox-directory}.
|
|
|
15052
|
|
|
15053 When Gnus asks for information from a backend---say @code{nntp}---on
|
|
|
15054 something, it will normally include a virtual server name in the
|
|
|
15055 function parameters. (If not, the backend should use the ``current''
|
|
|
15056 virtual server.) For instance, @code{nntp-request-list} takes a virtual
|
|
|
15057 server as its only (optional) parameter. If this virtual server hasn't
|
|
|
15058 been opened, the function should fail.
|
|
|
15059
|
|
|
15060 Note that a virtual server name has no relation to some physical server
|
|
|
15061 name. Take this example:
|
|
|
15062
|
|
|
15063 @lisp
|
|
|
15064 (nntp "odd-one"
|
|
|
15065 (nntp-address "ifi.uio.no")
|
|
|
15066 (nntp-port-number 4324))
|
|
|
15067 @end lisp
|
|
|
15068
|
|
|
15069 Here the virtual server name is @samp{odd-one} while the name of
|
|
|
15070 the physical server is @samp{ifi.uio.no}.
|
|
|
15071
|
|
|
15072 The backends should be able to switch between several virtual servers.
|
|
|
15073 The standard backends implement this by keeping an alist of virtual
|
|
|
15074 server environments that it pulls down/pushes up when needed.
|
|
|
15075
|
|
|
15076 There are two groups of interface functions: @dfn{required functions},
|
|
|
15077 which must be present, and @dfn{optional functions}, which Gnus will
|
|
|
15078 always check whether are present before attempting to call.
|
|
|
15079
|
|
|
15080 All these functions are expected to return data in the buffer
|
|
|
15081 @code{nntp-server-buffer} (@samp{ *nntpd*}), which is somewhat
|
|
|
15082 unfortunately named, but we'll have to live with it. When I talk about
|
|
16
|
15083 @dfn{resulting data}, I always refer to the data in that buffer. When I
|
|
|
15084 talk about @dfn{return value}, I talk about the function value returned by
|
|
|
15085 the function call. Functions that fail should return @code{nil} as the
|
|
|
15086 return value.
|
|
0
|
15087
|
|
|
15088 Some backends could be said to be @dfn{server-forming} backends, and
|
|
|
15089 some might be said to not be. The latter are backends that generally
|
|
|
15090 only operate on one group at a time, and have no concept of ``server''
|
|
|
15091 -- they have a group, and they deliver info on that group and nothing
|
|
|
15092 more.
|
|
|
15093
|
|
|
15094 In the examples and definitions I will refer to the imaginary backend
|
|
|
15095 @code{nnchoke}.
|
|
|
15096
|
|
|
15097 @cindex @code{nnchoke}
|
|
|
15098
|
|
|
15099 @menu
|
|
|
15100 * Required Backend Functions:: Functions that must be implemented.
|
|
|
15101 * Optional Backend Functions:: Functions that need not be implemented.
|
|
16
|
15102 * Error Messaging:: How to get messages and report errors.
|
|
0
|
15103 * Writing New Backends:: Extending old backends.
|
|
16
|
15104 * Hooking New Backends Into Gnus:: What has to be done on the Gnus end.
|
|
|
15105 * Mail-like Backends:: Some tips on mail backends.
|
|
0
|
15106 @end menu
|
|
|
15107
|
|
|
15108
|
|
|
15109 @node Required Backend Functions
|
|
|
15110 @subsubsection Required Backend Functions
|
|
|
15111
|
|
|
15112 @table @code
|
|
|
15113
|
|
|
15114 @item (nnchoke-retrieve-headers ARTICLES &optional GROUP SERVER FETCH-OLD)
|
|
|
15115
|
|
|
15116 @var{articles} is either a range of article numbers or a list of
|
|
|
15117 @code{Message-ID}s. Current backends do not fully support either---only
|
|
|
15118 sequences (lists) of article numbers, and most backends do not support
|
|
|
15119 retrieval of @code{Message-ID}s. But they should try for both.
|
|
|
15120
|
|
|
15121 The result data should either be HEADs or NOV lines, and the result
|
|
|
15122 value should either be @code{headers} or @code{nov} to reflect this.
|
|
|
15123 This might later be expanded to @code{various}, which will be a mixture
|
|
|
15124 of HEADs and NOV lines, but this is currently not supported by Gnus.
|
|
|
15125
|
|
|
15126 If @var{fetch-old} is non-@code{nil} it says to try to fetch "extra
|
|
|
15127 headers, in some meaning of the word. This is generally done by
|
|
|
15128 fetching (at most) @var{fetch-old} extra headers less than the smallest
|
|
|
15129 article number in @code{articles}, and fill in the gaps as well. The
|
|
|
15130 presence of this parameter can be ignored if the backend finds it
|
|
|
15131 cumbersome to follow the request. If this is non-@code{nil} and not a
|
|
|
15132 number, do maximum fetches.
|
|
|
15133
|
|
|
15134 Here's an example HEAD:
|
|
|
15135
|
|
|
15136 @example
|
|
|
15137 221 1056 Article retrieved.
|
|
|
15138 Path: ifi.uio.no!sturles
|
|
|
15139 From: sturles@@ifi.uio.no (Sturle Sunde)
|
|
|
15140 Newsgroups: ifi.discussion
|
|
|
15141 Subject: Re: Something very droll
|
|
|
15142 Date: 27 Oct 1994 14:02:57 +0100
|
|
|
15143 Organization: Dept. of Informatics, University of Oslo, Norway
|
|
|
15144 Lines: 26
|
|
|
15145 Message-ID: <38o8e1$a0o@@holmenkollen.ifi.uio.no>
|
|
|
15146 References: <38jdmq$4qu@@visbur.ifi.uio.no>
|
|
|
15147 NNTP-Posting-Host: holmenkollen.ifi.uio.no
|
|
|
15148 .
|
|
|
15149 @end example
|
|
|
15150
|
|
|
15151 So a @code{headers} return value would imply that there's a number of
|
|
|
15152 these in the data buffer.
|
|
|
15153
|
|
|
15154 Here's a BNF definition of such a buffer:
|
|
|
15155
|
|
|
15156 @example
|
|
|
15157 headers = *head
|
|
|
15158 head = error / valid-head
|
|
|
15159 error-message = [ "4" / "5" ] 2number " " <error message> eol
|
|
|
15160 valid-head = valid-message *header "." eol
|
|
|
15161 valid-message = "221 " <number> " Article retrieved." eol
|
|
|
15162 header = <text> eol
|
|
|
15163 @end example
|
|
|
15164
|
|
|
15165 If the return value is @code{nov}, the data buffer should contain
|
|
|
15166 @dfn{network overview database} lines. These are basically fields
|
|
|
15167 separated by tabs.
|
|
|
15168
|
|
|
15169 @example
|
|
|
15170 nov-buffer = *nov-line
|
|
|
15171 nov-line = 8*9 [ field <TAB> ] eol
|
|
|
15172 field = <text except TAB>
|
|
|
15173 @end example
|
|
|
15174
|
|
|
15175 For a closer explanation what should be in those fields,
|
|
|
15176 @pxref{Headers}.
|
|
|
15177
|
|
|
15178
|
|
|
15179 @item (nnchoke-open-server SERVER &optional DEFINITIONS)
|
|
|
15180
|
|
|
15181 @var{server} is here the virtual server name. @var{definitions} is a
|
|
|
15182 list of @code{(VARIABLE VALUE)} pairs that defines this virtual server.
|
|
|
15183
|
|
|
15184 If the server can't be opened, no error should be signaled. The backend
|
|
|
15185 may then choose to refuse further attempts at connecting to this
|
|
|
15186 server. In fact, it should do so.
|
|
|
15187
|
|
|
15188 If the server is opened already, this function should return a
|
|
|
15189 non-@code{nil} value. There should be no data returned.
|
|
|
15190
|
|
|
15191
|
|
|
15192 @item (nnchoke-close-server &optional SERVER)
|
|
|
15193
|
|
|
15194 Close connection to @var{server} and free all resources connected
|
|
|
15195 to it. Return @code{nil} if the server couldn't be closed for some
|
|
|
15196 reason.
|
|
|
15197
|
|
|
15198 There should be no data returned.
|
|
|
15199
|
|
|
15200
|
|
|
15201 @item (nnchoke-request-close)
|
|
|
15202
|
|
|
15203 Close connection to all servers and free all resources that the backend
|
|
|
15204 have reserved. All buffers that have been created by that backend
|
|
|
15205 should be killed. (Not the @code{nntp-server-buffer}, though.) This
|
|
|
15206 function is generally only called when Gnus is shutting down.
|
|
|
15207
|
|
|
15208 There should be no data returned.
|
|
|
15209
|
|
|
15210
|
|
|
15211 @item (nnchoke-server-opened &optional SERVER)
|
|
|
15212
|
|
|
15213 If @var{server} is the current virtual server, and the connection to the
|
|
|
15214 physical server is alive, then this function should return a
|
|
|
15215 non-@code{nil} vlue. This function should under no circumstances
|
|
|
15216 attempt to reconnect to a server that is has lost connection to.
|
|
|
15217
|
|
|
15218 There should be no data returned.
|
|
|
15219
|
|
|
15220
|
|
|
15221 @item (nnchoke-status-message &optional SERVER)
|
|
|
15222
|
|
|
15223 This function should return the last error message from @var{server}.
|
|
|
15224
|
|
|
15225 There should be no data returned.
|
|
|
15226
|
|
|
15227
|
|
|
15228 @item (nnchoke-request-article ARTICLE &optional GROUP SERVER TO-BUFFER)
|
|
|
15229
|
|
|
15230 The result data from this function should be the article specified by
|
|
|
15231 @var{article}. This might either be a @code{Message-ID} or a number.
|
|
|
15232 It is optional whether to implement retrieval by @code{Message-ID}, but
|
|
|
15233 it would be nice if that were possible.
|
|
|
15234
|
|
|
15235 If @var{to-buffer} is non-@code{nil}, the result data should be returned
|
|
|
15236 in this buffer instead of the normal data buffer. This is to make it
|
|
|
15237 possible to avoid copying large amounts of data from one buffer to
|
|
|
15238 another, and Gnus mainly request articles to be inserted directly into
|
|
|
15239 its article buffer.
|
|
|
15240
|
|
|
15241 If it is at all possible, this function should return a cons cell where
|
|
|
15242 the car is the group name the article was fetched from, and the cdr is
|
|
|
15243 the article number. This will enable Gnus to find out what the real
|
|
|
15244 group and article numbers are when fetching articles by
|
|
|
15245 @code{Message-ID}. If this isn't possible, @code{t} should be returned
|
|
|
15246 on successful article retrievement.
|
|
|
15247
|
|
|
15248
|
|
16
|
15249 @item (nnchoke-request-group GROUP &optional SERVER FAST)
|
|
0
|
15250
|
|
|
15251 Get data on @var{group}. This function also has the side effect of
|
|
|
15252 making @var{group} the current group.
|
|
|
15253
|
|
16
|
15254 If @var{FAST}, don't bother to return useful data, just make @var{group}
|
|
|
15255 the current group.
|
|
|
15256
|
|
0
|
15257 Here's an example of some result data and a definition of the same:
|
|
|
15258
|
|
|
15259 @example
|
|
|
15260 211 56 1000 1059 ifi.discussion
|
|
|
15261 @end example
|
|
|
15262
|
|
16
|
15263 The first number is the status, which should be 211. Next is the
|
|
0
|
15264 total number of articles in the group, the lowest article number, the
|
|
|
15265 highest article number, and finally the group name. Note that the total
|
|
|
15266 number of articles may be less than one might think while just
|
|
|
15267 considering the highest and lowest article numbers, but some articles
|
|
|
15268 may have been canceled. Gnus just discards the total-number, so
|
|
|
15269 whether one should take the bother to generate it properly (if that is a
|
|
|
15270 problem) is left as an exercise to the reader.
|
|
|
15271
|
|
|
15272 @example
|
|
|
15273 group-status = [ error / info ] eol
|
|
|
15274 error = [ "4" / "5" ] 2<number> " " <Error message>
|
|
|
15275 info = "211 " 3* [ <number> " " ] <string>
|
|
|
15276 @end example
|
|
|
15277
|
|
|
15278
|
|
|
15279 @item (nnchoke-close-group GROUP &optional SERVER)
|
|
|
15280
|
|
|
15281 Close @var{group} and free any resources connected to it. This will be
|
|
|
15282 a no-op on most backends.
|
|
|
15283
|
|
|
15284 There should be no data returned.
|
|
|
15285
|
|
|
15286
|
|
|
15287 @item (nnchoke-request-list &optional SERVER)
|
|
|
15288
|
|
|
15289 Return a list of all groups available on @var{server}. And that means
|
|
|
15290 @emph{all}.
|
|
|
15291
|
|
|
15292 Here's an example from a server that only carries two groups:
|
|
|
15293
|
|
|
15294 @example
|
|
|
15295 ifi.test 0000002200 0000002000 y
|
|
|
15296 ifi.discussion 3324 3300 n
|
|
|
15297 @end example
|
|
|
15298
|
|
|
15299 On each line we have a group name, then the highest article number in
|
|
|
15300 that group, the lowest article number, and finally a flag.
|
|
|
15301
|
|
|
15302 @example
|
|
|
15303 active-file = *active-line
|
|
|
15304 active-line = name " " <number> " " <number> " " flags eol
|
|
|
15305 name = <string>
|
|
|
15306 flags = "n" / "y" / "m" / "x" / "j" / "=" name
|
|
|
15307 @end example
|
|
|
15308
|
|
|
15309 The flag says whether the group is read-only (@samp{n}), is moderated
|
|
|
15310 (@samp{m}), is dead (@samp{x}), is aliased to some other group
|
|
|
15311 (@samp{=other-group} or none of the above (@samp{y}).
|
|
|
15312
|
|
|
15313
|
|
|
15314 @item (nnchoke-request-post &optional SERVER)
|
|
|
15315
|
|
|
15316 This function should post the current buffer. It might return whether
|
|
|
15317 the posting was successful or not, but that's not required. If, for
|
|
|
15318 instance, the posting is done asynchronously, it has generally not been
|
|
|
15319 completed by the time this function concludes. In that case, this
|
|
|
15320 function should set up some kind of sentinel to beep the user loud and
|
|
|
15321 clear if the posting could not be completed.
|
|
|
15322
|
|
|
15323 There should be no result data from this function.
|
|
|
15324
|
|
|
15325 @end table
|
|
|
15326
|
|
|
15327
|
|
|
15328 @node Optional Backend Functions
|
|
|
15329 @subsubsection Optional Backend Functions
|
|
|
15330
|
|
|
15331 @table @code
|
|
|
15332
|
|
|
15333 @item (nnchoke-retrieve-groups GROUPS &optional SERVER)
|
|
|
15334
|
|
|
15335 @var{groups} is a list of groups, and this function should request data
|
|
|
15336 on all those groups. How it does it is of no concern to Gnus, but it
|
|
|
15337 should attempt to do this in a speedy fashion.
|
|
|
15338
|
|
|
15339 The return value of this function can be either @code{active} or
|
|
|
15340 @code{group}, which says what the format of the result data is. The
|
|
|
15341 former is in the same format as the data from
|
|
|
15342 @code{nnchoke-request-list}, while the latter is a buffer full of lines
|
|
|
15343 in the same format as @code{nnchoke-request-group} gives.
|
|
|
15344
|
|
|
15345 @example
|
|
|
15346 group-buffer = *active-line / *group-status
|
|
|
15347 @end example
|
|
|
15348
|
|
|
15349
|
|
|
15350 @item (nnchoke-request-update-info GROUP INFO &optional SERVER)
|
|
|
15351
|
|
|
15352 A Gnus group info (@pxref{Group Info}) is handed to the backend for
|
|
|
15353 alterations. This comes in handy if the backend really carries all the
|
|
26
|
15354 information (as is the case with virtual and imap groups). This
|
|
|
15355 function should destructively alter the info to suit its needs, and
|
|
|
15356 should return the (altered) group info.
|
|
0
|
15357
|
|
|
15358 There should be no result data from this function.
|
|
|
15359
|
|
|
15360
|
|
|
15361 @item (nnchoke-request-type GROUP &optional ARTICLE)
|
|
|
15362
|
|
|
15363 When the user issues commands for ``sending news'' (@kbd{F} in the
|
|
|
15364 summary buffer, for instance), Gnus has to know whether the article the
|
|
|
15365 user is following up is news or mail. This function should return
|
|
|
15366 @code{news} if @var{article} in @var{group} is news, @code{mail} if it
|
|
|
15367 is mail and @code{unknown} if the type can't be decided. (The
|
|
|
15368 @var{article} parameter is necessary in @code{nnvirtual} groups which
|
|
16
|
15369 might very well combine mail groups and news groups.) Both @var{group}
|
|
|
15370 and @var{article} may be @code{nil}.
|
|
0
|
15371
|
|
|
15372 There should be no result data from this function.
|
|
|
15373
|
|
|
15374
|
|
|
15375 @item (nnchoke-request-update-mark GROUP ARTICLE MARK)
|
|
|
15376
|
|
|
15377 If the user tries to set a mark that the backend doesn't like, this
|
|
|
15378 function may change the mark. Gnus will use whatever this function
|
|
|
15379 returns as the mark for @var{article} instead of the original
|
|
|
15380 @var{mark}. If the backend doesn't care, it must return the original
|
|
|
15381 @var{mark}, and not @code{nil} or any other type of garbage.
|
|
|
15382
|
|
|
15383 The only use for this that I can see is what @code{nnvirtual} does with
|
|
|
15384 it---if a component group is auto-expirable, marking an article as read
|
|
|
15385 in the virtual group should result in the article being marked as
|
|
|
15386 expirable.
|
|
|
15387
|
|
|
15388 There should be no result data from this function.
|
|
|
15389
|
|
|
15390
|
|
|
15391 @item (nnchoke-request-scan &optional GROUP SERVER)
|
|
|
15392
|
|
|
15393 This function may be called at any time (by Gnus or anything else) to
|
|
|
15394 request that the backend check for incoming articles, in one way or
|
|
|
15395 another. A mail backend will typically read the spool file or query the
|
|
|
15396 POP server when this function is invoked. The @var{group} doesn't have
|
|
|
15397 to be heeded---if the backend decides that it is too much work just
|
|
|
15398 scanning for a single group, it may do a total scan of all groups. It
|
|
|
15399 would be nice, however, to keep things local if that's practical.
|
|
|
15400
|
|
|
15401 There should be no result data from this function.
|
|
|
15402
|
|
|
15403
|
|
|
15404 @item (nnchoke-request-group-description GROUP &optional SERVER)
|
|
|
15405
|
|
|
15406 The result data from this function should be a description of
|
|
|
15407 @var{group}.
|
|
|
15408
|
|
|
15409 @example
|
|
|
15410 description-line = name <TAB> description eol
|
|
|
15411 name = <string>
|
|
|
15412 description = <text>
|
|
|
15413 @end example
|
|
|
15414
|
|
|
15415 @item (nnchoke-request-list-newsgroups &optional SERVER)
|
|
|
15416
|
|
|
15417 The result data from this function should be the description of all
|
|
|
15418 groups available on the server.
|
|
|
15419
|
|
|
15420 @example
|
|
|
15421 description-buffer = *description-line
|
|
|
15422 @end example
|
|
|
15423
|
|
|
15424
|
|
|
15425 @item (nnchoke-request-newgroups DATE &optional SERVER)
|
|
|
15426
|
|
|
15427 The result data from this function should be all groups that were
|
|
|
15428 created after @samp{date}, which is in normal human-readable date
|
|
|
15429 format. The data should be in the active buffer format.
|
|
|
15430
|
|
|
15431
|
|
|
15432 @item (nnchoke-request-create-group GROUP &optional SERVER)
|
|
|
15433
|
|
|
15434 This function should create an empty group with name @var{group}.
|
|
|
15435
|
|
|
15436 There should be no return data.
|
|
|
15437
|
|
|
15438
|
|
|
15439 @item (nnchoke-request-expire-articles ARTICLES &optional GROUP SERVER FORCE)
|
|
|
15440
|
|
|
15441 This function should run the expiry process on all articles in the
|
|
|
15442 @var{articles} range (which is currently a simple list of article
|
|
|
15443 numbers.) It is left up to the backend to decide how old articles
|
|
|
15444 should be before they are removed by this function. If @var{force} is
|
|
|
15445 non-@code{nil}, all @var{articles} should be deleted, no matter how new
|
|
|
15446 they are.
|
|
|
15447
|
|
|
15448 This function should return a list of articles that it did not/was not
|
|
|
15449 able to delete.
|
|
|
15450
|
|
|
15451 There should be no result data returned.
|
|
|
15452
|
|
|
15453
|
|
|
15454 @item (nnchoke-request-move-article ARTICLE GROUP SERVER ACCEPT-FORM
|
|
|
15455 &optional LAST)
|
|
|
15456
|
|
|
15457 This function should move @var{article} (which is a number) from
|
|
|
15458 @var{group} by calling @var{accept-form}.
|
|
|
15459
|
|
|
15460 This function should ready the article in question for moving by
|
|
|
15461 removing any header lines it has added to the article, and generally
|
|
|
15462 should ``tidy up'' the article. Then it should @code{eval}
|
|
|
15463 @var{accept-form} in the buffer where the ``tidy'' article is. This
|
|
|
15464 will do the actual copying. If this @code{eval} returns a
|
|
|
15465 non-@code{nil} value, the article should be removed.
|
|
|
15466
|
|
|
15467 If @var{last} is @code{nil}, that means that there is a high likelihood
|
|
|
15468 that there will be more requests issued shortly, so that allows some
|
|
|
15469 optimizations.
|
|
|
15470
|
|
|
15471 The function should return a cons where the car is the group name and
|
|
|
15472 the cdr is the article number that the article was entered as.
|
|
|
15473
|
|
|
15474 There should be no data returned.
|
|
|
15475
|
|
|
15476
|
|
|
15477 @item (nnchoke-request-accept-article GROUP &optional SERVER LAST)
|
|
|
15478
|
|
|
15479 This function takes the current buffer and inserts it into @var{group}.
|
|
|
15480 If @var{last} in @code{nil}, that means that there will be more calls to
|
|
|
15481 this function in short order.
|
|
|
15482
|
|
|
15483 The function should return a cons where the car is the group name and
|
|
|
15484 the cdr is the article number that the article was entered as.
|
|
|
15485
|
|
|
15486 There should be no data returned.
|
|
|
15487
|
|
|
15488
|
|
|
15489 @item (nnchoke-request-replace-article ARTICLE GROUP BUFFER)
|
|
|
15490
|
|
|
15491 This function should remove @var{article} (which is a number) from
|
|
|
15492 @var{group} and insert @var{buffer} there instead.
|
|
|
15493
|
|
|
15494 There should be no data returned.
|
|
|
15495
|
|
|
15496
|
|
|
15497 @item (nnchoke-request-delete-group GROUP FORCE &optional SERVER)
|
|
|
15498
|
|
|
15499 This function should delete @var{group}. If @var{force}, it should
|
|
|
15500 really delete all the articles in the group, and then delete the group
|
|
|
15501 itself. (If there is such a thing as ``the group itself''.)
|
|
|
15502
|
|
|
15503 There should be no data returned.
|
|
|
15504
|
|
|
15505
|
|
|
15506 @item (nnchoke-request-rename-group GROUP NEW-NAME &optional SERVER)
|
|
|
15507
|
|
|
15508 This function should rename @var{group} into @var{new-name}. All
|
|
|
15509 articles that are in @var{group} should move to @var{new-name}.
|
|
|
15510
|
|
|
15511 There should be no data returned.
|
|
|
15512
|
|
|
15513 @end table
|
|
|
15514
|
|
|
15515
|
|
16
|
15516 @node Error Messaging
|
|
|
15517 @subsubsection Error Messaging
|
|
|
15518
|
|
|
15519 @findex nnheader-report
|
|
|
15520 @findex nnheader-get-report
|
|
|
15521 The backends should use the function @code{nnheader-report} to report
|
|
|
15522 error conditions---they should not raise errors when they aren't able to
|
|
|
15523 perform a request. The first argument to this function is the backend
|
|
|
15524 symbol, and the rest are interpreted as arguments to @code{format} if
|
|
|
15525 there are many of them, or just a string if there is one of them.
|
|
|
15526 This function always returns @code{nil}.
|
|
|
15527
|
|
|
15528 @lisp
|
|
|
15529 (nnheader-report 'nnchoke "You did something totally bogus")
|
|
|
15530
|
|
|
15531 (nnheader-report 'nnchoke "Could not request group %s" group)
|
|
|
15532 @end lisp
|
|
|
15533
|
|
|
15534 Gnus, in turn, will call @code{nnheader-get-report} when it gets a
|
|
|
15535 @code{nil} back from a server, and this function returns the most
|
|
|
15536 recently reported message for the backend in question. This function
|
|
|
15537 takes one argument---the server symbol.
|
|
|
15538
|
|
|
15539 Internally, these function access @var{backend}@code{-status-string}, so
|
|
|
15540 the @code{nnchoke} backend will have its error message stored in
|
|
|
15541 @code{nnchoke-status-string}.
|
|
|
15542
|
|
|
15543
|
|
0
|
15544 @node Writing New Backends
|
|
|
15545 @subsubsection Writing New Backends
|
|
|
15546
|
|
16
|
15547 Many backends are quite similar. @code{nnml} is just like
|
|
0
|
15548 @code{nnspool}, but it allows you to edit the articles on the server.
|
|
|
15549 @code{nnmh} is just like @code{nnml}, but it doesn't use an active file,
|
|
|
15550 and it doesn't maintain overview databases. @code{nndir} is just like
|
|
|
15551 @code{nnml}, but it has no concept of ``groups'', and it doesn't allow
|
|
|
15552 editing articles.
|
|
|
15553
|
|
|
15554 It would make sense if it were possible to ``inherit'' functions from
|
|
|
15555 backends when writing new backends. And, indeed, you can do that if you
|
|
|
15556 want to. (You don't have to if you don't want to, of course.)
|
|
|
15557
|
|
|
15558 All the backends declare their public variables and functions by using a
|
|
|
15559 package called @code{nnoo}.
|
|
|
15560
|
|
|
15561 To inherit functions from other backends (and allow other backends to
|
|
|
15562 inherit functions from the current backend), you should use the
|
|
|
15563 following macros:
|
|
|
15564 following.
|
|
|
15565
|
|
|
15566 @table @code
|
|
|
15567
|
|
|
15568 @item nnoo-declare
|
|
|
15569 This macro declares the first parameter to be a child of the subsequent
|
|
|
15570 parameters. For instance:
|
|
|
15571
|
|
|
15572 @lisp
|
|
|
15573 (nnoo-declare nndir
|
|
|
15574 nnml nnmh)
|
|
|
15575 @end lisp
|
|
|
15576
|
|
|
15577 @code{nndir} has here declared that it intends to inherit functions from
|
|
|
15578 both @code{nnml} and @code{nnmh}.
|
|
|
15579
|
|
|
15580 @item defvoo
|
|
|
15581 This macro is equivalent to @code{defvar}, but registers the variable as
|
|
|
15582 a public server variable. Most state-oriented variables should be
|
|
|
15583 declared with @code{defvoo} instead of @code{defvar}.
|
|
|
15584
|
|
|
15585 In addition to the normal @code{defvar} parameters, it takes a list of
|
|
|
15586 variables in the parent backends to map the variable to when executing
|
|
|
15587 a function in those backends.
|
|
|
15588
|
|
|
15589 @lisp
|
|
|
15590 (defvoo nndir-directory nil
|
|
|
15591 "Where nndir will look for groups."
|
|
|
15592 nnml-current-directory nnmh-current-directory)
|
|
|
15593 @end lisp
|
|
|
15594
|
|
|
15595 This means that @code{nnml-current-directory} will be set to
|
|
|
15596 @code{nndir-directory} when an @code{nnml} function is called on behalf
|
|
|
15597 of @code{nndir}. (The same with @code{nnmh}.)
|
|
|
15598
|
|
|
15599 @item nnoo-define-basics
|
|
|
15600 This macro defines some common functions that almost all backends should
|
|
|
15601 have.
|
|
|
15602
|
|
|
15603 @example
|
|
|
15604 (nnoo-define-basics nndir)
|
|
|
15605 @end example
|
|
|
15606
|
|
|
15607 @item deffoo
|
|
|
15608 This macro is just like @code{defun} and takes the same parameters. In
|
|
|
15609 addition to doing the normal @code{defun} things, it registers the
|
|
|
15610 function as being public so that other backends can inherit it.
|
|
|
15611
|
|
|
15612 @item nnoo-map-functions
|
|
|
15613 This macro allows mapping of functions from the current backend to
|
|
|
15614 functions from the parent backends.
|
|
|
15615
|
|
|
15616 @example
|
|
|
15617 (nnoo-map-functions nndir
|
|
|
15618 (nnml-retrieve-headers 0 nndir-current-group 0 0)
|
|
|
15619 (nnmh-request-article 0 nndir-current-group 0 0))
|
|
|
15620 @end example
|
|
|
15621
|
|
|
15622 This means that when @code{nndir-retrieve-headers} is called, the first,
|
|
|
15623 third, and fourth parameters will be passed on to
|
|
|
15624 @code{nnml-retrieve-headers}, while the second parameter is set to the
|
|
|
15625 value of @code{nndir-current-group}.
|
|
|
15626
|
|
|
15627 @item nnoo-import
|
|
|
15628 This macro allows importing functions from backends. It should be the
|
|
|
15629 last thing in the source file, since it will only define functions that
|
|
|
15630 haven't already been defined.
|
|
|
15631
|
|
|
15632 @example
|
|
|
15633 (nnoo-import nndir
|
|
|
15634 (nnmh
|
|
|
15635 nnmh-request-list
|
|
|
15636 nnmh-request-newgroups)
|
|
|
15637 (nnml))
|
|
|
15638 @end example
|
|
|
15639
|
|
|
15640 This means that calls to @code{nndir-request-list} should just be passed
|
|
|
15641 on to @code{nnmh-request-list}, while all public functions from
|
|
|
15642 @code{nnml} that haven't been defined in @code{nndir} yet should be
|
|
|
15643 defined now.
|
|
|
15644
|
|
|
15645 @end table
|
|
|
15646
|
|
|
15647 Below is a slightly shortened version of the @code{nndir} backend.
|
|
|
15648
|
|
|
15649 @lisp
|
|
|
15650 ;;; nndir.el --- single directory newsgroup access for Gnus
|
|
|
15651 ;; Copyright (C) 1995,96 Free Software Foundation, Inc.
|
|
|
15652
|
|
|
15653 ;;; Code:
|
|
|
15654
|
|
|
15655 (require 'nnheader)
|
|
|
15656 (require 'nnmh)
|
|
|
15657 (require 'nnml)
|
|
|
15658 (require 'nnoo)
|
|
|
15659 (eval-when-compile (require 'cl))
|
|
|
15660
|
|
|
15661 (nnoo-declare nndir
|
|
|
15662 nnml nnmh)
|
|
|
15663
|
|
|
15664 (defvoo nndir-directory nil
|
|
|
15665 "Where nndir will look for groups."
|
|
|
15666 nnml-current-directory nnmh-current-directory)
|
|
|
15667
|
|
|
15668 (defvoo nndir-nov-is-evil nil
|
|
|
15669 "*Non-nil means that nndir will never retrieve NOV headers."
|
|
|
15670 nnml-nov-is-evil)
|
|
|
15671
|
|
|
15672 (defvoo nndir-current-group "" nil nnml-current-group nnmh-current-group)
|
|
|
15673 (defvoo nndir-top-directory nil nil nnml-directory nnmh-directory)
|
|
|
15674 (defvoo nndir-get-new-mail nil nil nnml-get-new-mail nnmh-get-new-mail)
|
|
|
15675
|
|
|
15676 (defvoo nndir-status-string "" nil nnmh-status-string)
|
|
|
15677 (defconst nndir-version "nndir 1.0")
|
|
|
15678
|
|
|
15679 ;;; Interface functions.
|
|
|
15680
|
|
|
15681 (nnoo-define-basics nndir)
|
|
|
15682
|
|
|
15683 (deffoo nndir-open-server (server &optional defs)
|
|
|
15684 (setq nndir-directory
|
|
16
|
15685 (or (cadr (assq 'nndir-directory defs))
|
|
|
15686 server))
|
|
0
|
15687 (unless (assq 'nndir-directory defs)
|
|
|
15688 (push `(nndir-directory ,server) defs))
|
|
|
15689 (push `(nndir-current-group
|
|
16
|
15690 ,(file-name-nondirectory (directory-file-name nndir-directory)))
|
|
|
15691 defs)
|
|
0
|
15692 (push `(nndir-top-directory
|
|
16
|
15693 ,(file-name-directory (directory-file-name nndir-directory)))
|
|
|
15694 defs)
|
|
0
|
15695 (nnoo-change-server 'nndir server defs))
|
|
|
15696
|
|
|
15697 (nnoo-map-functions nndir
|
|
|
15698 (nnml-retrieve-headers 0 nndir-current-group 0 0)
|
|
|
15699 (nnmh-request-article 0 nndir-current-group 0 0)
|
|
|
15700 (nnmh-request-group nndir-current-group 0 0)
|
|
|
15701 (nnmh-close-group nndir-current-group 0))
|
|
|
15702
|
|
|
15703 (nnoo-import nndir
|
|
|
15704 (nnmh
|
|
|
15705 nnmh-status-message
|
|
|
15706 nnmh-request-list
|
|
|
15707 nnmh-request-newgroups))
|
|
|
15708
|
|
|
15709 (provide 'nndir)
|
|
|
15710 @end lisp
|
|
|
15711
|
|
|
15712
|
|
16
|
15713 @node Hooking New Backends Into Gnus
|
|
|
15714 @subsubsection Hooking New Backends Into Gnus
|
|
|
15715
|
|
|
15716 @vindex gnus-valid-select-methods
|
|
|
15717 Having Gnus start using your new backend is rather easy---you just
|
|
|
15718 declare it with the @code{gnus-declare-backend} functions. This will
|
|
|
15719 enter the backend into the @code{gnus-valid-select-methods} variable.
|
|
|
15720
|
|
|
15721 @code{gnus-declare-backend} takes two parameters---the backend name and
|
|
|
15722 an arbitrary number of @dfn{abilities}.
|
|
|
15723
|
|
|
15724 Here's an example:
|
|
|
15725
|
|
|
15726 @lisp
|
|
|
15727 (gnus-declare-backend "nnchoke" 'mail 'respool 'address)
|
|
|
15728 @end lisp
|
|
|
15729
|
|
|
15730 The abilities can be:
|
|
|
15731
|
|
|
15732 @table @code
|
|
|
15733 @item mail
|
|
|
15734 This is a mailish backend---followups should (probably) go via mail.
|
|
|
15735 @item post
|
|
|
15736 This is a newsish backend---followups should (probably) go via news.
|
|
|
15737 @item post-mail
|
|
|
15738 This backend supports both mail and news.
|
|
|
15739 @item none
|
|
|
15740 This is neither a post or mail backend---it's something completely
|
|
|
15741 different.
|
|
|
15742 @item respool
|
|
|
15743 It supports respooling---or rather, it is able to modify its source
|
|
|
15744 articles and groups.
|
|
|
15745 @item address
|
|
|
15746 The name of the server should be in the virtual server name. This is
|
|
|
15747 true for almost all backends.
|
|
|
15748 @item prompt-address
|
|
|
15749 The user should be prompted for an address when doing commands like
|
|
|
15750 @kbd{B} in the group buffer. This is true for backends like
|
|
|
15751 @code{nntp}, but not @code{nnmbox}, for instance.
|
|
|
15752 @end table
|
|
|
15753
|
|
|
15754
|
|
|
15755 @node Mail-like Backends
|
|
|
15756 @subsubsection Mail-like Backends
|
|
|
15757
|
|
|
15758 One of the things that separate the mail backends from the rest of the
|
|
|
15759 backends is the heavy dependence by the mail backends on common
|
|
|
15760 functions in @file{nnmail.el}. For instance, here's the definition of
|
|
|
15761 @code{nnml-request-scan}:
|
|
|
15762
|
|
|
15763 @lisp
|
|
|
15764 (deffoo nnml-request-scan (&optional group server)
|
|
|
15765 (setq nnml-article-file-alist nil)
|
|
|
15766 (nnmail-get-new-mail 'nnml 'nnml-save-nov nnml-directory group))
|
|
|
15767 @end lisp
|
|
|
15768
|
|
|
15769 It simply just calls @code{nnmail-get-new-mail} will a few parameters,
|
|
|
15770 and @code{nnmail} takes care of all the moving and splitting of the
|
|
|
15771 mail.
|
|
|
15772
|
|
|
15773 This function takes four parameters.
|
|
|
15774
|
|
|
15775 @table @var
|
|
|
15776 @item method
|
|
|
15777 This should be a symbol to designate which backend is responsible for
|
|
|
15778 the call.
|
|
|
15779
|
|
|
15780 @item exit-function
|
|
|
15781 This function should be called after the splitting has been performed.
|
|
|
15782
|
|
|
15783 @item temp-directory
|
|
|
15784 Where the temporary files should be stored.
|
|
|
15785
|
|
|
15786 @item group
|
|
|
15787 This optional argument should be a group name if the splitting is to be
|
|
|
15788 performed for one group only.
|
|
|
15789 @end table
|
|
|
15790
|
|
|
15791 @code{nnmail-get-new-mail} will call @var{backend}@code{-save-mail} to
|
|
|
15792 save each article. @var{backend}@code{-active-number} will be called to
|
|
|
15793 find the article number assigned to this article.
|
|
|
15794
|
|
|
15795 The function also uses the following variables:
|
|
|
15796 @var{backend}@code{-get-new-mail} (to see whether to get new mail for
|
|
|
15797 this backend); and @var{backend}@code{-group-alist} and
|
|
|
15798 @var{backend}@code{-active-file} to generate the new active file.
|
|
|
15799 @var{backend}@code{-group-alist} should be a group-active alist, like
|
|
|
15800 this:
|
|
|
15801
|
|
|
15802 @example
|
|
|
15803 (("a-group" (1 . 10))
|
|
|
15804 ("some-group" (34 . 39)))
|
|
|
15805 @end example
|
|
|
15806
|
|
0
|
15807
|
|
|
15808 @node Score File Syntax
|
|
|
15809 @subsection Score File Syntax
|
|
|
15810
|
|
|
15811 Score files are meant to be easily parsable, but yet extremely
|
|
|
15812 mallable. It was decided that something that had the same read syntax
|
|
|
15813 as an Emacs Lisp list would fit that spec.
|
|
|
15814
|
|
|
15815 Here's a typical score file:
|
|
|
15816
|
|
|
15817 @lisp
|
|
|
15818 (("summary"
|
|
|
15819 ("win95" -10000 nil s)
|
|
|
15820 ("Gnus"))
|
|
|
15821 ("from"
|
|
|
15822 ("Lars" -1000))
|
|
|
15823 (mark -100))
|
|
|
15824 @end lisp
|
|
|
15825
|
|
|
15826 BNF definition of a score file:
|
|
|
15827
|
|
|
15828 @example
|
|
|
15829 score-file = "" / "(" *element ")"
|
|
|
15830 element = rule / atom
|
|
|
15831 rule = string-rule / number-rule / date-rule
|
|
|
15832 string-rule = "(" quote string-header quote space *string-match ")"
|
|
|
15833 number-rule = "(" quote number-header quote space *number-match ")"
|
|
|
15834 date-rule = "(" quote date-header quote space *date-match ")"
|
|
|
15835 quote = <ascii 34>
|
|
|
15836 string-header = "subject" / "from" / "references" / "message-id" /
|
|
|
15837 "xref" / "body" / "head" / "all" / "followup"
|
|
|
15838 number-header = "lines" / "chars"
|
|
|
15839 date-header = "date"
|
|
|
15840 string-match = "(" quote <string> quote [ "" / [ space score [ "" /
|
|
|
15841 space date [ "" / [ space string-match-t ] ] ] ] ] ")"
|
|
|
15842 score = "nil" / <integer>
|
|
|
15843 date = "nil" / <natural number>
|
|
|
15844 string-match-t = "nil" / "s" / "substring" / "S" / "Substring" /
|
|
|
15845 "r" / "regex" / "R" / "Regex" /
|
|
|
15846 "e" / "exact" / "E" / "Exact" /
|
|
|
15847 "f" / "fuzzy" / "F" / "Fuzzy"
|
|
|
15848 number-match = "(" <integer> [ "" / [ space score [ "" /
|
|
|
15849 space date [ "" / [ space number-match-t ] ] ] ] ] ")"
|
|
|
15850 number-match-t = "nil" / "=" / "<" / ">" / ">=" / "<="
|
|
|
15851 date-match = "(" quote <string> quote [ "" / [ space score [ "" /
|
|
|
15852 space date [ "" / [ space date-match-t ] ] ] ] ")"
|
|
|
15853 date-match-t = "nil" / "at" / "before" / "after"
|
|
|
15854 atom = "(" [ required-atom / optional-atom ] ")"
|
|
|
15855 required-atom = mark / expunge / mark-and-expunge / files /
|
|
|
15856 exclude-files / read-only / touched
|
|
|
15857 optional-atom = adapt / local / eval
|
|
|
15858 mark = "mark" space nil-or-number
|
|
|
15859 nil-or-number = "nil" / <integer>
|
|
|
15860 expunge = "expunge" space nil-or-number
|
|
|
15861 mark-and-expunge = "mark-and-expunge" space nil-or-number
|
|
|
15862 files = "files" *[ space <string> ]
|
|
|
15863 exclude-files = "exclude-files" *[ space <string> ]
|
|
|
15864 read-only = "read-only" [ space "nil" / space "t" ]
|
|
|
15865 adapt = "adapt" [ space "nil" / space "t" / space adapt-rule ]
|
|
|
15866 adapt-rule = "(" *[ <string> *[ "(" <string> <integer> ")" ] ")"
|
|
|
15867 local = "local" *[ space "(" <string> space <form> ")" ]
|
|
|
15868 eval = "eval" space <form>
|
|
|
15869 space = *[ " " / <TAB> / <NEWLINE> ]
|
|
|
15870 @end example
|
|
|
15871
|
|
|
15872 Any unrecognized elements in a score file should be ignored, but not
|
|
|
15873 discarded.
|
|
|
15874
|
|
|
15875 As you can see, white space is needed, but the type and amount of white
|
|
|
15876 space is irrelevant. This means that formatting of the score file is
|
|
|
15877 left up to the programmer---if it's simpler to just spew it all out on
|
|
|
15878 one looong line, then that's ok.
|
|
|
15879
|
|
|
15880 The meaning of the various atoms are explained elsewhere in this
|
|
|
15881 manual.
|
|
|
15882
|
|
|
15883
|
|
|
15884 @node Headers
|
|
|
15885 @subsection Headers
|
|
|
15886
|
|
|
15887 Gnus uses internally a format for storing article headers that
|
|
|
15888 corresponds to the @sc{nov} format in a mysterious fashion. One could
|
|
|
15889 almost suspect that the author looked at the @sc{nov} specification and
|
|
|
15890 just shamelessly @emph{stole} the entire thing, and one would be right.
|
|
|
15891
|
|
|
15892 @dfn{Header} is a severely overloaded term. ``Header'' is used in
|
|
16
|
15893 RFC1036 to talk about lines in the head of an article (e.g.,
|
|
0
|
15894 @code{From}). It is used by many people as a synonym for
|
|
|
15895 ``head''---``the header and the body''. (That should be avoided, in my
|
|
|
15896 opinion.) And Gnus uses a format internally that it calls ``header'',
|
|
|
15897 which is what I'm talking about here. This is a 9-element vector,
|
|
|
15898 basically, with each header (ouch) having one slot.
|
|
|
15899
|
|
|
15900 These slots are, in order: @code{number}, @code{subject}, @code{from},
|
|
|
15901 @code{date}, @code{id}, @code{references}, @code{chars}, @code{lines},
|
|
2
|
15902 @code{xref}. There are macros for accessing and setting these
|
|
|
15903 slots---they all have predictable names beginning with
|
|
|
15904 @code{mail-header-} and @code{mail-header-set-}, respectively.
|
|
0
|
15905
|
|
|
15906 The @code{xref} slot is really a @code{misc} slot. Any extra info will
|
|
|
15907 be put in there.
|
|
|
15908
|
|
|
15909
|
|
|
15910 @node Ranges
|
|
|
15911 @subsection Ranges
|
|
|
15912
|
|
|
15913 @sc{gnus} introduced a concept that I found so useful that I've started
|
|
|
15914 using it a lot and have elaborated on it greatly.
|
|
|
15915
|
|
|
15916 The question is simple: If you have a large amount of objects that are
|
|
|
15917 identified by numbers (say, articles, to take a @emph{wild} example)
|
|
16
|
15918 that you want to qualify as being ``included'', a normal sequence isn't
|
|
0
|
15919 very useful. (A 200,000 length sequence is a bit long-winded.)
|
|
|
15920
|
|
|
15921 The solution is as simple as the question: You just collapse the
|
|
|
15922 sequence.
|
|
|
15923
|
|
|
15924 @example
|
|
|
15925 (1 2 3 4 5 6 10 11 12)
|
|
|
15926 @end example
|
|
|
15927
|
|
|
15928 is transformed into
|
|
|
15929
|
|
|
15930 @example
|
|
|
15931 ((1 . 6) (10 . 12))
|
|
|
15932 @end example
|
|
|
15933
|
|
|
15934 To avoid having those nasty @samp{(13 . 13)} elements to denote a
|
|
|
15935 lonesome object, a @samp{13} is a valid element:
|
|
|
15936
|
|
|
15937 @example
|
|
|
15938 ((1 . 6) 7 (10 . 12))
|
|
|
15939 @end example
|
|
|
15940
|
|
|
15941 This means that comparing two ranges to find out whether they are equal
|
|
|
15942 is slightly tricky:
|
|
|
15943
|
|
|
15944 @example
|
|
|
15945 ((1 . 5) 7 8 (10 . 12))
|
|
|
15946 @end example
|
|
|
15947
|
|
|
15948 and
|
|
|
15949
|
|
|
15950 @example
|
|
|
15951 ((1 . 5) (7 . 8) (10 . 12))
|
|
|
15952 @end example
|
|
|
15953
|
|
|
15954 are equal. In fact, any non-descending list is a range:
|
|
|
15955
|
|
|
15956 @example
|
|
|
15957 (1 2 3 4 5)
|
|
|
15958 @end example
|
|
|
15959
|
|
|
15960 is a perfectly valid range, although a pretty long-winded one. This is
|
|
|
15961 also legal:
|
|
|
15962
|
|
|
15963 @example
|
|
|
15964 (1 . 5)
|
|
|
15965 @end example
|
|
|
15966
|
|
|
15967 and is equal to the previous range.
|
|
|
15968
|
|
|
15969 Here's a BNF definition of ranges. Of course, one must remember the
|
|
|
15970 semantic requirement that the numbers are non-descending. (Any number
|
|
|
15971 of repetition of the same number is allowed, but apt to disappear in
|
|
|
15972 range handling.)
|
|
|
15973
|
|
|
15974 @example
|
|
|
15975 range = simple-range / normal-range
|
|
|
15976 simple-range = "(" number " . " number ")"
|
|
|
15977 normal-range = "(" start-contents ")"
|
|
|
15978 contents = "" / simple-range *[ " " contents ] /
|
|
|
15979 number *[ " " contents ]
|
|
|
15980 @end example
|
|
|
15981
|
|
|
15982 Gnus currently uses ranges to keep track of read articles and article
|
|
|
15983 marks. I plan on implementing a number of range operators in C if The
|
|
|
15984 Powers That Be are willing to let me. (I haven't asked yet, because I
|
|
|
15985 need to do some more thinking on what operators I need to make life
|
|
|
15986 totally range-based without ever having to convert back to normal
|
|
|
15987 sequences.)
|
|
|
15988
|
|
|
15989
|
|
|
15990 @node Group Info
|
|
|
15991 @subsection Group Info
|
|
|
15992
|
|
|
15993 Gnus stores all permanent info on groups in a @dfn{group info} list.
|
|
|
15994 This list is from three to six elements (or more) long and exhaustively
|
|
|
15995 describes the group.
|
|
|
15996
|
|
|
15997 Here are two example group infos; one is a very simple group while the
|
|
|
15998 second is a more complex one:
|
|
|
15999
|
|
|
16000 @example
|
|
|
16001 ("no.group" 5 (1 . 54324))
|
|
|
16002
|
|
|
16003 ("nnml:my.mail" 3 ((1 . 5) 9 (20 . 55))
|
|
|
16004 ((tick (15 . 19)) (replied 3 6 (19 . 3)))
|
|
|
16005 (nnml "")
|
|
|
16006 (auto-expire (to-address "ding@@ifi.uio.no")))
|
|
|
16007 @end example
|
|
|
16008
|
|
16
|
16009 The first element is the @dfn{group name}---as Gnus knows the group,
|
|
|
16010 anyway. The second element is the @dfn{subscription level}, which
|
|
|
16011 normally is a small integer. The third element is a list of ranges of
|
|
|
16012 read articles. The fourth element is a list of lists of article marks
|
|
|
16013 of various kinds. The fifth element is the select method (or virtual
|
|
|
16014 server, if you like). The sixth element is a list of @dfn{group
|
|
|
16015 parameters}, which is what this section is about.
|
|
|
16016
|
|
|
16017 Any of the last three elements may be missing if they are not required.
|
|
|
16018 In fact, the vast majority of groups will normally only have the first
|
|
|
16019 three elements, which saves quite a lot of cons cells.
|
|
0
|
16020
|
|
|
16021 Here's a BNF definition of the group info format:
|
|
|
16022
|
|
|
16023 @example
|
|
|
16024 info = "(" group space level space read
|
|
|
16025 [ "" / [ space marks-list [ "" / [ space method [ "" /
|
|
|
16026 space parameters ] ] ] ] ] ")"
|
|
|
16027 group = quote <string> quote
|
|
|
16028 level = <integer in the range of 1 to inf>
|
|
|
16029 read = range
|
|
|
16030 marks-lists = nil / "(" *marks ")"
|
|
|
16031 marks = "(" <string> range ")"
|
|
|
16032 method = "(" <string> *elisp-forms ")"
|
|
|
16033 parameters = "(" *elisp-forms ")"
|
|
|
16034 @end example
|
|
|
16035
|
|
|
16036 Actually that @samp{marks} rule is a fib. A @samp{marks} is a
|
|
|
16037 @samp{<string>} consed on to a @samp{range}, but that's a bitch to say
|
|
|
16038 in pseudo-BNF.
|
|
|
16039
|
|
|
16040
|
|
|
16041 @node Emacs/XEmacs Code
|
|
|
16042 @subsection Emacs/XEmacs Code
|
|
|
16043 @cindex XEmacs
|
|
|
16044 @cindex Emacsen
|
|
|
16045
|
|
|
16046 While Gnus runs under Emacs, XEmacs and Mule, I decided that one of the
|
|
|
16047 platforms must be the primary one. I chose Emacs. Not because I don't
|
|
|
16048 like XEmacs or Mule, but because it comes first alphabetically.
|
|
|
16049
|
|
|
16050 This means that Gnus will byte-compile under Emacs with nary a warning,
|
|
|
16051 while XEmacs will pump out gigabytes of warnings while byte-compiling.
|
|
|
16052 As I use byte-compilation warnings to help me root out trivial errors in
|
|
|
16053 Gnus, that's very useful.
|
|
|
16054
|
|
|
16055 I've also consistently used Emacs function interfaces, but have used
|
|
|
16056 Gnusey aliases for the functions. To take an example: Emacs defines a
|
|
|
16057 @code{run-at-time} function while XEmacs defines a @code{start-itimer}
|
|
|
16058 function. I then define a function called @code{gnus-run-at-time} that
|
|
|
16059 takes the same parameters as the Emacs @code{run-at-time}. When running
|
|
|
16060 Gnus under Emacs, the former function is just an alias for the latter.
|
|
|
16061 However, when running under XEmacs, the former is an alias for the
|
|
|
16062 following function:
|
|
|
16063
|
|
|
16064 @lisp
|
|
|
16065 (defun gnus-xmas-run-at-time (time repeat function &rest args)
|
|
|
16066 (start-itimer
|
|
|
16067 "gnus-run-at-time"
|
|
|
16068 `(lambda ()
|
|
|
16069 (,function ,@@args))
|
|
|
16070 time repeat))
|
|
|
16071 @end lisp
|
|
|
16072
|
|
|
16073 This sort of thing has been done for bunches of functions. Gnus does
|
|
2
|
16074 not redefine any native Emacs functions while running under XEmacs---it
|
|
0
|
16075 does this @code{defalias} thing with Gnus equivalents instead. Cleaner
|
|
|
16076 all over.
|
|
|
16077
|
|
|
16078 Of course, I could have chosen XEmacs as my native platform and done
|
|
|
16079 mapping functions the other way around. But I didn't. The performance
|
|
|
16080 hit these indirections impose on Gnus under XEmacs should be slight.
|
|
|
16081
|
|
|
16082
|
|
|
16083 @node Various File Formats
|
|
|
16084 @subsection Various File Formats
|
|
|
16085
|
|
|
16086 @menu
|
|
|
16087 * Active File Format:: Information on articles and groups available.
|
|
|
16088 * Newsgroups File Format:: Group descriptions.
|
|
|
16089 @end menu
|
|
|
16090
|
|
|
16091
|
|
|
16092 @node Active File Format
|
|
|
16093 @subsubsection Active File Format
|
|
|
16094
|
|
|
16095 The active file lists all groups that are available on the server in
|
|
|
16096 question. It also lists the highest and lowest current article numbers
|
|
|
16097 in each group.
|
|
|
16098
|
|
|
16099 Here's an excerpt from a typical active file:
|
|
|
16100
|
|
|
16101 @example
|
|
|
16102 soc.motss 296030 293865 y
|
|
|
16103 alt.binaries.pictures.fractals 3922 3913 n
|
|
|
16104 comp.sources.unix 1605 1593 m
|
|
|
16105 comp.binaries.ibm.pc 5097 5089 y
|
|
|
16106 no.general 1000 900 y
|
|
|
16107 @end example
|
|
|
16108
|
|
|
16109 Here's a pseudo-BNF definition of this file:
|
|
|
16110
|
|
|
16111 @example
|
|
|
16112 active = *group-line
|
|
|
16113 group-line = group space high-number space low-number space flag <NEWLINE>
|
|
|
16114 group = <non-white-space string>
|
|
|
16115 space = " "
|
|
|
16116 high-number = <non-negative integer>
|
|
|
16117 low-number = <positive integer>
|
|
|
16118 flag = "y" / "n" / "m" / "j" / "x" / "=" group
|
|
|
16119 @end example
|
|
|
16120
|
|
|
16121
|
|
|
16122 @node Newsgroups File Format
|
|
|
16123 @subsubsection Newsgroups File Format
|
|
|
16124
|
|
|
16125 The newsgroups file lists groups along with their descriptions. Not all
|
|
|
16126 groups on the server have to be listed, and not all groups in the file
|
|
|
16127 have to exist on the server. The file is meant purely as information to
|
|
|
16128 the user.
|
|
|
16129
|
|
|
16130 The format is quite simple; a group name, a tab, and the description.
|
|
|
16131 Here's the definition:
|
|
|
16132
|
|
|
16133 @example
|
|
|
16134 newsgroups = *line
|
|
|
16135 line = group tab description <NEWLINE>
|
|
|
16136 group = <non-white-space string>
|
|
|
16137 tab = <TAB>
|
|
|
16138 description = <string>
|
|
|
16139 @end example
|
|
|
16140
|
|
|
16141
|
|
|
16142 @node Emacs for Heathens
|
|
|
16143 @section Emacs for Heathens
|
|
|
16144
|
|
|
16145 Believe it or not, but some people who use Gnus haven't really used
|
|
|
16146 Emacs much before they embarked on their journey on the Gnus Love Boat.
|
|
|
16147 If you are one of those unfortunates whom ``@kbd{M-C-a}'', ``kill the
|
|
|
16148 region'', and ``set @code{gnus-flargblossen} to an alist where the key
|
|
|
16149 is a regexp that is used for matching on the group name'' are magical
|
|
|
16150 phrases with little or no meaning, then this appendix is for you. If
|
|
|
16151 you are already familiar with Emacs, just ignore this and go fondle your
|
|
|
16152 cat instead.
|
|
|
16153
|
|
|
16154 @menu
|
|
|
16155 * Keystrokes:: Entering text and executing commands.
|
|
|
16156 * Emacs Lisp:: The built-in Emacs programming language.
|
|
|
16157 @end menu
|
|
|
16158
|
|
|
16159
|
|
|
16160 @node Keystrokes
|
|
|
16161 @subsection Keystrokes
|
|
|
16162
|
|
|
16163 @itemize @bullet
|
|
|
16164 @item
|
|
|
16165 Q: What is an experienced Emacs user?
|
|
|
16166
|
|
|
16167 @item
|
|
|
16168 A: A person who wishes that the terminal had pedals.
|
|
|
16169 @end itemize
|
|
|
16170
|
|
|
16171 Yes, when you use Emacs, you are apt to use the control key, the shift
|
|
|
16172 key and the meta key a lot. This is very annoying to some people
|
|
|
16173 (notably @code{vi}le users), and the rest of us just love the hell out
|
|
|
16174 of it. Just give up and submit. Emacs really does stand for
|
|
|
16175 ``Escape-Meta-Alt-Control-Shift'', and not ``Editing Macros'', as you
|
|
|
16176 may have heard from other disreputable sources (like the Emacs author).
|
|
|
16177
|
|
|
16178 The shift key is normally located near your pinky fingers, and are
|
|
|
16179 normally used to get capital letters and stuff. You probably use it all
|
|
|
16180 the time. The control key is normally marked ``CTRL'' or something like
|
|
|
16181 that. The meta key is, funnily enough, never marked as such on any
|
|
|
16182 keyboards. The one I'm currently at has a key that's marked ``Alt'',
|
|
|
16183 which is the meta key on this keyboard. It's usually located somewhere
|
|
|
16184 to the left hand side of the keyboard, usually on the bottom row.
|
|
|
16185
|
|
|
16186 Now, us Emacs people doesn't say ``press the meta-control-m key'',
|
|
|
16187 because that's just too inconvenient. We say ``press the @kbd{M-C-m}
|
|
|
16188 key''. @kbd{M-} is the prefix that means ``meta'' and ``C-'' is the
|
|
|
16189 prefix that means ``control''. So ``press @kbd{C-k}'' means ``press
|
|
|
16190 down the control key, and hold it down while you press @kbd{k}''.
|
|
|
16191 ``Press @kbd{M-C-k}'' means ``press down and hold down the meta key and
|
|
|
16192 the control key and then press @kbd{k}''. Simple, ay?
|
|
|
16193
|
|
|
16194 This is somewhat complicated by the fact that not all keyboards have a
|
|
|
16195 meta key. In that case you can use the ``escape'' key. Then @kbd{M-k}
|
|
|
16196 means ``press escape, release escape, press @kbd{k}''. That's much more
|
|
|
16197 work than if you have a meta key, so if that's the case, I respectfully
|
|
|
16198 suggest you get a real keyboard with a meta key. You can't live without
|
|
|
16199 it.
|
|
|
16200
|
|
|
16201
|
|
|
16202
|
|
|
16203 @node Emacs Lisp
|
|
|
16204 @subsection Emacs Lisp
|
|
|
16205
|
|
|
16206 Emacs is the King of Editors because it's really a Lisp interpreter.
|
|
|
16207 Each and every key you tap runs some Emacs Lisp code snippet, and since
|
|
|
16208 Emacs Lisp is an interpreted language, that means that you can configure
|
|
|
16209 any key to run any arbitrary code. You just, like, do it.
|
|
|
16210
|
|
|
16211 Gnus is written in Emacs Lisp, and is run as a bunch of interpreted
|
|
|
16212 functions. (These are byte-compiled for speed, but it's still
|
|
|
16213 interpreted.) If you decide that you don't like the way Gnus does
|
|
|
16214 certain things, it's trivial to have it do something a different way.
|
|
|
16215 (Well, at least if you know how to write Lisp code.) However, that's
|
|
|
16216 beyond the scope of this manual, so we are simply going to talk about
|
|
|
16217 some common constructs that you normally use in your @file{.emacs} file
|
|
|
16218 to customize Gnus.
|
|
|
16219
|
|
|
16220 If you want to set the variable @code{gnus-florgbnize} to four (4), you
|
|
|
16221 write the following:
|
|
|
16222
|
|
|
16223 @lisp
|
|
|
16224 (setq gnus-florgbnize 4)
|
|
|
16225 @end lisp
|
|
|
16226
|
|
|
16227 This function (really ``special form'') @code{setq} is the one that can
|
|
|
16228 set a variable to some value. This is really all you need to know. Now
|
|
|
16229 you can go and fill your @code{.emacs} file with lots of these to change
|
|
|
16230 how Gnus works.
|
|
|
16231
|
|
|
16232 If you have put that thing in your @code{.emacs} file, it will be read
|
|
|
16233 and @code{eval}ed (which is lisp-ese for ``run'') the next time you
|
|
|
16234 start Emacs. If you want to change the variable right away, simply say
|
|
|
16235 @kbd{C-x C-e} after the closing parenthesis. That will @code{eval} the
|
|
|
16236 previous ``form'', which here is a simple @code{setq} statement.
|
|
|
16237
|
|
|
16238 Go ahead---just try it, if you're located at your Emacs. After you
|
|
|
16239 @kbd{C-x C-e}, you will see @samp{4} appear in the echo area, which
|
|
|
16240 is the return value of the form you @code{eval}ed.
|
|
|
16241
|
|
|
16242 Some pitfalls:
|
|
|
16243
|
|
|
16244 If the manual says ``set @code{gnus-read-active-file} to @code{some}'',
|
|
|
16245 that means:
|
|
|
16246
|
|
|
16247 @lisp
|
|
|
16248 (setq gnus-read-active-file 'some)
|
|
|
16249 @end lisp
|
|
|
16250
|
|
|
16251 On the other hand, if the manual says ``set @code{gnus-nntp-server} to
|
|
|
16252 @samp{nntp.ifi.uio.no}'', that means:
|
|
|
16253
|
|
|
16254 @lisp
|
|
|
16255 (setq gnus-nntp-server "nntp.ifi.uio.no")
|
|
|
16256 @end lisp
|
|
|
16257
|
|
|
16258 So be careful not to mix up strings (the latter) with symbols (the
|
|
|
16259 former). The manual is unambiguous, but it can be confusing.
|
|
|
16260
|
|
|
16261
|
|
|
16262 @include gnus-faq.texi
|
|
|
16263
|
|
|
16264 @node Index
|
|
|
16265 @chapter Index
|
|
|
16266 @printindex cp
|
|
|
16267
|
|
|
16268 @node Key Index
|
|
|
16269 @chapter Key Index
|
|
|
16270 @printindex ky
|
|
|
16271
|
|
|
16272 @summarycontents
|
|
|
16273 @contents
|
|
|
16274 @bye
|
|
|
16275
|
|
|
16276 @iftex
|
|
|
16277 @iflatex
|
|
|
16278 \end{document}
|
|
|
16279 @end iflatex
|
|
|
16280 @end iftex
|
|
|
16281
|
|
|
16282 @c End:
|
|
|
16283
|
