From: morioka Date: Tue, 12 Jan 1999 07:55:30 +0000 (+0000) Subject: Merge chao-gnus-6_12_5. X-Git-Tag: chaos-1_12_0~2 X-Git-Url: http://git.chise.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c1880fb1ec3845e37eb577b7b9493b5ed26667f6;p=elisp%2Fgnus.git- Merge chao-gnus-6_12_5. --- diff --git a/texi/Makefile.in b/texi/Makefile.in index eb05e11..77db83e 100644 --- a/texi/Makefile.in +++ b/texi/Makefile.in @@ -20,6 +20,8 @@ PAPERTYPE=a4 all: gnus message +ja: gnus-ja message-ja + most: texi2latex.elc latex latexps .SUFFIXES: .texi .dvi .ps @@ -115,7 +117,7 @@ distclean: install: $(SHELL) $(top_srcdir)/mkinstalldirs $(infodir) - @for file in gnus message; do \ + @for file in gnus message gnus-ja message-ja; do \ for ifile in `echo $$file $$file-[0-9] $$file-[0-9][0-9]`; do \ if test -f $$ifile; then \ echo " $(INSTALL_DATA) $$ifile $(infodir)/$$ifile"; \ diff --git a/texi/gnus-ja.texi b/texi/gnus-ja.texi index b742de3..8d32fd1 100644 --- a/texi/gnus-ja.texi +++ b/texi/gnus-ja.texi @@ -1,7 +1,7 @@ \input texinfo @c -*-texinfo-*- @setfilename gnus-ja -@settitle Semi-gnus 6.9.2 Manual +@settitle Semi-gnus 6.8.19 Manual @synindex fn cp @synindex vr cp @synindex pg cp @@ -345,7 +345,7 @@ into another language, under the above conditions for modified versions. @tex @titlepage -@title Semi-gnus 6.9.2 Manual +@title Semi-gnus 6.8.19 Manual @author by Lars Magne Ingebrigtsen @author by members of Semi-gnus mailing-list @@ -399,7 +399,7 @@ Semi-gnus $B$O!"Bg$-$J3($,F~$C$F$$$?$j$5$^$6$^$J7A<0$rMQ$$$?$j$7$F$$$k$A$g$C(B $B$J8@8l7w$r:9JL$7$^$;$s!#$"$"!"%/%j%s%4%s$NJ}$O(B Unicode Next Generation$B$r(B $B$*BT$A$/$@$5$$!#(B -$B$3$N@bL@=q$O(B Semi-gnus 6.9.2 $B$KBP1~$7$^$9!#(B +$B$3$N@bL@=q$O(B Semi-gnus 6.8.19 $B$KBP1~$7$^$9!#(B @end ifinfo @@ -722,7 +722,7 @@ Gnus $B$O!"IaDL$O%0%k!<%W$,?7$7$$$+$I$&$+$r!"9XFI$7$F$$$k%0%k!<%W$H:o=|$5(B @vindex gnus-subscribe-newsgroup-method $B?7$7$$%0%k!<%W$KAx6x$7$?$H$-$K(B gnus $B$,2?$r$9$k$+$O!"JQ?t(B -@code{gnus-subscribe-newsroup-method} $B$K$h$C$F7hDj$5$l$^$9!#(B +@code{gnus-subscribe-nesgroup-method} $B$K$h$C$F7hDj$5$l$^$9!#(B $B$3$NJQ?t$O4X?t$r4^$s$G$$$kI,MW$,$"$j$^$9!#$3$N4X?t$O?7$7$$%0%k!<%W$NL>A0(B $B$rM#0l$N0z?t$H$7$F8F$P$l$^$9!#(B @@ -802,10 +802,10 @@ options -n !alt.all !rec.all sci.all @vindex gnus-options-not-subscribe @vindex gnus-options-subscribe -$B%U%!%$%k(B @file{.newsrc} $B$r$$$8$j$?$/$J$$>l9g$O!"(B +$B%U%!%$%k(B @file{.newrc} $B$r$$$8$j$?$/$J$$>l9g$O!"(B @code{gnus-options-subscribe} $B$H(B @code{gnus-options-not-subscribe} $B$N#2(B $B$D$NJQ?t$@$1$r@_Dj$9$k$3$H$b$G$-$^$9!#$3$N#2$D$NJQ?t$O%U%!%$%k(B -@file{.newsrc} $B$N(B @samp{optinos -n} $B9T$HA4$/F1$8$3$H$r$7$^$9!#$I$A$i$NJQ(B +@file{.newrc} $B$N(B @samp{optinos -n} $B9T$HA4$/F1$8$3$H$r$7$^$9!#$I$A$i$NJQ(B $B?t$b@55,I=8=$G!"?7$7$$%0%k!<%W$OA0r7o$K9XFI$5$l!"8epJs$OEAE}E*$K$3$N%U%!%$%k$KC_@Q$5$l$^$9!#(B @sc{GNUS} $B$G$OJ*;v$,>/!9J#;($K$J$C$F$$$^$9!#%U%!%$%k(B @file{.newsrc} $B$r:G(B @@ -4040,8 +4040,8 @@ Prefixes})$B!#(B $B5-;v$KIU$1$i$l$k0u$O$$$/$D$+$"$j$^$9!#(B -$B5-;v$N(B @dfn{$B9XFIEY(B}$B!J$*$)!"$9$s$4$$?78l6g$@!*!K$r7hDj$9$k0u$,$"$j$^(B -$B$9!#1Q;z$N0u$O0lHLE*$K$O(B @dfn{$B4{FI(B}$B$r0UL#$7!"1Q;z$G$J$$J8;z$O0lHLE*$K(B +$B5-;v$N(B @dfn{$B9XFIEY(B}$B!J$*$)!"%K!<%H!&%-!<%N?78l6g$@!*!K$r7hDj$9$k0u$,$"$j$^(B +$B$9!#1Q;z$N0u$O0lHLE*$K$O(B@dfn{$B4{FI(B}$B$r0UL#$7!"1Q;z$G$J$$J8;z$O0lHLE*$K(B @dfn{$BL$FI(B}$B$r0UL#$7$^$9!#(B $B2C$($F!"9XFIEY$K1F6A$7$J$$0u$b$"$j$^$9!#(B @@ -7470,7 +7470,7 @@ Parameters}) $B$rJT=8$7$^$9(B (@code{gnus-summary-edit-parameters})$B!#(B @kindex Z s $B!J35N,!K(B @findex gnus-summary-save-newsrc $B8=:_$N4{FI(B/$B0uIU$-5-;v$N?t$r%I%j%V%k%P%C%U%!(B (dribble buffer) $B$KJ]B8$7!"(B -$B$=$l$+$i%I%j%V%k%P%C%U%!$rJ]B8$7$^$9(B (@code{gnus-summary-save-newsrc})$B!#(B +$B$=$l$+$i%I%j%V%k%P%C%U%!$rJ]B8$7$^$9(B (@code{gnus-summary-save-newrc})$B!#(B $B$b$7@\F,0z?t$rM?$($i$l$l$P!"%U%!%$%k(B @file{.newsrc} $B$bJ]B8$7$^$9!#$3$NL?(B $BNa$r;H$&$H!"99?7$J$7$GH4$1=P$k;v(B (@kbd{Q} $BL?Na(B) $B$O0UL#$,L5$/$J$j$^$9!#(B @end table @@ -11003,8 +11003,8 @@ To: alt-religion-emacs@@GATEWAY @table @code @item nngateway-simple-header-transformaton -@var{newsgroup}@@@code{nngateway-address} $B$N$h$&$J(B @code{To} $B%X%C%@!<$r(B -$B$D$/$j$^$9!#(B +@var{nesgroup}@@@code{nngateway-address} $B$N$h$&$J(B @code{To} $B%X%C%@!<$r$D(B +$B$/$j$^$9!#(B @findex nngateway-mail2news-header-transformation @@ -15524,11 +15524,11 @@ Gnus $B$OA4$F$N(B @sc{gnus} $B5/F0%U%!%$%k$rM}2r$7$^$9!#(B Gnus $B$O(B MIME $B$N07$$$r$;$:!"$3$NI8=`$K$J$k$b$N$O(B $B$9$4$/NI$$$H9M$($F$$$k$N(B $B$G!"2f!9$O$3$3$KBg$-$J7j$,6u$$$F$$$k;v$K$J$j$^$9!#(B -@item X-Newsreader +@item X-Nesreader $B$3$l$O(B ``$B$D$^$i$J$$%X%C%@!<(B'' $B$H9M$($i$l$F$$$^$9$,!";d$O>CHqpJs$G$"(B $B$k$H8+$J$7$F$$$^$9!#(B@code{tin} $B$H(B @code{Netscape} $B$+$iAw$i$l$F$/$kHs>o$K(B $BB?$/$NMM<0$K1h$C$F$$$J$$5-;v$r8+$?8e$G!";d$O$=$l$i$r5-;v$rEj9F$9$k$?$a$K(B -$B$O;H$o$J$$J}$,NI$$$H$$$&;v$rCN$j$^$7$?!#$b$7(B @code{X-Newsreader} $B%X%C%@!<(B +$B$O;H$o$J$$J}$,NI$$$H$$$&;v$rCN$j$^$7$?!#$b$7(B @code{X-Nesreader} $B%X%C%@!<(B $B$,L5$1$l$P;d$O$=$N>pJs$rF@$k;v$O$J$+$C$?$G$7$g$&!#(B @end table @@ -17823,8 +17823,8 @@ Solve the halting problem. @item $B%P%C%/%(%s%I(B (backend) @cindex backend Gnus $B$O%K%e!<%9$H%a!<%k$NN>J}$N$$$m$$$m$J%P%C%/%(%s%I$,M?$($?5-;v$rF@$^(B -$B$9!#(BGnus $B$O!"$$$o$f$k2<$K2#$?$o$C$F$$$k%a%G%#%"$r07$&;v$O$7$^$;$s(B---$B$3$l(B -$B$O$9$Y$F%P%C%/%(%s%I$K$h$C$F$J$5$l$^$9!#(B +$B$9!#(BGnus $B$O$O!"$$$o$f$k2<$K2#$?$o$C$F$$$k%a%G%#%"$r07$&;v$O$7$^$;$s(B---$B$3(B +$B$l$O$9$Y$F%P%C%/%(%s%I$K$h$C$F$J$5$l$^$9!#(B @item $B4pK\(B (native) @cindex native @@ -18126,7 +18126,7 @@ Gnus $B$OH"$+$i=P$7$F$9$0$K(B @emph{$BHs>o$K(B} $B$h$/F0:n$7$^$9(B---$B2? @item @kbd{M-x gnus-version} $B$r;n$7$F2<$5$$!#$b$7!"(B -@samp{Semi-gnus 6.9.2 (based on Gnus 5.6.45; for SEMI 1.11, FLIM 1.12)} +@samp{Semi-gnus 6.8.19 (based on Gnus 5.6.44; for SEMI 1.8, FLIM 1.9/1.9)} $B$N$h$&$J$b$N$,=P$F$-$?$J$i!"@5$7$$%U%!%$%k$,FI$_9~$^$l$F$$$^$9!#(B $B$b$7!"(B@samp{NNTP 3.x} $B$d(B @samp{nntp flee} $B$N$h$&$J$b$N$,=P$F$-$?$H$-$O!"(B $B$=$3$K$"$k$$$/$D$+$N8E$$(B @file{.el} $B%U%!%$%k$,FI$_9~$^$l$F$$$^$9!#$=$l$i(B diff --git a/texi/gnus.texi b/texi/gnus.texi index 998270d..8a8e990 100644 --- a/texi/gnus.texi +++ b/texi/gnus.texi @@ -1,7 +1,7 @@ \input texinfo @c -*-texinfo-*- @setfilename gnus -@settitle Gnus 5.6.45 Manual +@settitle Chaos 1.12.0 Manual @synindex fn cp @synindex vr cp @synindex pg cp @@ -291,7 +291,7 @@ into another language, under the above conditions for modified versions. @ifinfo -This file documents Gnus, the GNU Emacs newsreader. +This file documents gnus, the GNU Emacs newsreader. Copyright (C) 1995,96 Free Software Foundation, Inc. @@ -318,7 +318,7 @@ into another language, under the above conditions for modified versions. @tex @titlepage -@title Gnus 5.6.45 Manual +@title Chaos 1.12.0 Manual @author by Lars Magne Ingebrigtsen @page @@ -345,16 +345,23 @@ into another language, under the above conditions for modified versions. @node Top -@top The Gnus Newsreader +@top The gnus Newsreader @ifinfo -You can read news (and mail) from within Emacs by using Gnus. The news +You can read news (and mail) from within Emacs by using gnus. The news can be gotten by any nefarious means you can think of---@sc{nntp}, local spool or your mbox file. All at the same time, if you want to push your luck. -This manual corresponds to Gnus 5.6.45. +Chaos provides MIME features based on SEMI API. So Chaos +supports your right to read strange messages including big images or +other various kinds of formats. Chaos also supports +internationalization/localization and multiscript features based on MULE +API. So Chaos does not discriminate various language communities. +Oh, if you are a Klingon, please wait Unicode Next Generation. + +This manual corresponds to Chaos 1.12.0. @end ifinfo @@ -378,7 +385,7 @@ even read news with it! Gnus tries to empower people who read news the same way Emacs empowers people who edit text. Gnus sets no limits to what the user should be -allowed to do. Users are encouraged to extend Gnus to make it behave +allowed to do. Users are encouraged to extend gnus to make it behave like they want it to behave. A program should not control people; people should be empowered to do what they want by using (or abusing) the program. @@ -402,18 +409,18 @@ the program. @end menu @node Starting Up -@chapter Starting Gnus +@chapter Starting gnus @cindex starting up @kindex M-x gnus @findex gnus -If your system administrator has set things up properly, starting Gnus +If your system administrator has set things up properly, starting gnus and reading news is extremely easy---you just type @kbd{M-x gnus} in your Emacs. @findex gnus-other-frame @kindex M-x gnus-other-frame -If you want to start Gnus in a different frame, you can use the command +If you want to start gnus in a different frame, you can use the command @kbd{M-x gnus-other-frame} instead. If things do not go smoothly at startup, you have to twiddle some @@ -425,11 +432,11 @@ terminology section (@pxref{Terminology}). @menu * Finding the News:: Choosing a method for getting news. -* The First Time:: What does Gnus do the first time you start it? +* The First Time:: What does gnus do the first time you start it? * The Server is Down:: How can I read my mail then? -* Slave Gnusae:: You can have more than one Gnus active at a time. -* Fetching a Group:: Starting Gnus just to read a group. -* New Groups:: What is Gnus supposed to do with new groups? +* Slave Gnusae:: You can have more than one gnus active at a time. +* Fetching a Group:: Starting gnus just to read a group. +* New Groups:: What is gnus supposed to do with new groups? * Startup Files:: Those pesky startup files---@file{.newsrc}. * Auto Save:: Recovering from a crash. * The Active File:: Reading the active file over a slow line Takes Time. @@ -444,11 +451,11 @@ terminology section (@pxref{Terminology}). @vindex gnus-select-method @c @head -The @code{gnus-select-method} variable says where Gnus should look for +The @code{gnus-select-method} variable says where gnus should look for news. This variable should be a list where the first element says @dfn{how} and the second element says @dfn{where}. This method is your -native method. All groups not fetched with this method are -foreign groups. +native method. All groups not fetched with this method are foreign +groups. For instance, if the @samp{news.somewhere.edu} @sc{nntp} server is where you want to get your daily dosage of news from, you'd say: @@ -469,11 +476,12 @@ certainly be much faster. @vindex gnus-nntpserver-file @cindex NNTPSERVER @cindex @sc{nntp} server -If this variable is not set, Gnus will take a look at the +If this variable is not set, gnus will take a look at the @code{NNTPSERVER} environment variable. If that variable isn't set, -Gnus will see whether @code{gnus-nntpserver-file} +gnus will see whether @code{gnus-nntpserver-file} (@file{/etc/nntpserver} by default) has any opinions on the matter. If -that fails as well, Gnus will try to use the machine running Emacs as an @sc{nntp} server. That's a long shot, though. +that fails as well, gnus will try to use the machine running Emacs as an +@sc{nntp} server. That's a long shot, though. @vindex gnus-nntp-server If @code{gnus-nntp-server} is set, this variable will override @@ -481,9 +489,9 @@ If @code{gnus-nntp-server} is set, this variable will override @code{gnus-nntp-server} to @code{nil}, which is what it is by default. @vindex gnus-secondary-servers -You can also make Gnus prompt you interactively for the name of an +You can also make gnus prompt you interactively for the name of an @sc{nntp} server. If you give a non-numerical prefix to @code{gnus} -(i.e., @kbd{C-u M-x gnus}), Gnus will let you choose between the servers +(i.e., @kbd{C-u M-x gnus}), gnus will let you choose between the servers in the @code{gnus-secondary-servers} list (if any). You can also just type in the name of any server you feel like visiting. @@ -518,23 +526,23 @@ would typically set this variable to @section The First Time @cindex first time usage -If no startup files exist, Gnus will try to determine what groups should +If no startup files exist, gnus will try to determine what groups should be subscribed by default. @vindex gnus-default-subscribed-newsgroups -If the variable @code{gnus-default-subscribed-newsgroups} is set, Gnus +If the variable @code{gnus-default-subscribed-newsgroups} is set, gnus will subscribe you to just those groups in that list, leaving the rest killed. Your system administrator should have set this variable to something useful. -Since she hasn't, Gnus will just subscribe you to a few arbitrarily +Since she hasn't, gnus will just subscribe you to a few arbitrarily picked groups (i.e., @samp{*.newusers}). (@dfn{Arbitrary} is defined here as @dfn{whatever Lars thinks you should read}.) -You'll also be subscribed to the Gnus documentation group, which should +You'll also be subscribed to the gnus documentation group, which should help you with most common problems. -If @code{gnus-default-subscribed-newsgroups} is @code{t}, Gnus will just +If @code{gnus-default-subscribed-newsgroups} is @code{t}, gnus will just use the normal functions for handling new groups, and not do anything special. @@ -543,9 +551,9 @@ special. @section The Server is Down @cindex server errors -If the default server is down, Gnus will understandably have some +If the default server is down, gnus will understandably have some problems starting. However, if you have some mail groups in addition to -the news groups, you may want to start Gnus anyway. +the news groups, you may want to start gnus anyway. Gnus, being the trusting sort of program, will ask whether to proceed without a native select method if that server can't be contacted. This @@ -560,7 +568,7 @@ buffer. But, hey, that's your problem. Blllrph! @c @head If you know that the server is definitely down, or you just want to read your mail without bothering with the server at all, you can use the -@code{gnus-no-server} command to start Gnus. That might come in handy +@code{gnus-no-server} command to start gnus. That might come in handy if you're in a hurry as well. This command will not attempt to contact your primary server---instead, it will just activate all groups on level 1 and 2. (You should preferably keep no native groups on those two @@ -571,27 +579,27 @@ levels.) @section Slave Gnusae @cindex slave -You might want to run more than one Emacs with more than one Gnus at the -same time. If you are using different @file{.newsrc} files (e.g., if you -are using the two different Gnusae to read from two different servers), -that is no problem whatsoever. You just do it. +You might want to run more than one Emacs with more than one gnus at the +same time. If you are using different @file{.newsrc} files (e.g., if +you are using the two different gnusae to read from two different +servers), that is no problem whatsoever. You just do it. The problem appears when you want to run two Gnusae that use the same @code{.newsrc} file. -To work around that problem some, we here at the Think-Tank at the Gnus -Towers have come up with a new concept: @dfn{Masters} and -@dfn{slaves}. (We have applied for a patent on this concept, and have -taken out a copyright on those words. If you wish to use those words in -conjunction with each other, you have to send $1 per usage instance to -me. Usage of the patent (@dfn{Master/Slave Relationships In Computer -Applications}) will be much more expensive, of course.) +To work around that problem some, we here at the Think-Tank at the gnus +Towers have come up with a new concept: @dfn{Masters} and @dfn{slaves}. +(We have applied for a patent on this concept, and have taken out a +copyright on those words. If you wish to use those words in conjunction +with each other, you have to send $1 per usage instance to me. Usage of +the patent (@dfn{Master/Slave Relationships In Computer Applications}) +will be much more expensive, of course.) -Anyways, you start one Gnus up the normal way with @kbd{M-x gnus} (or -however you do it). Each subsequent slave Gnusae should be started with +Anyways, you start one gnus up the normal way with @kbd{M-x gnus} (or +however you do it). Each subsequent slave gnusae should be started with @kbd{M-x gnus-slave}. These slaves won't save normal @file{.newsrc} files, but instead save @dfn{slave files} that contain information only -on what groups have been read in the slave session. When a master Gnus +on what groups have been read in the slave session. When a master gnus starts, it will read (and delete) these slave files, incorporating all information from them. (The slave files will be read in the sequence they were created, so the latest changes will have precedence.) @@ -606,7 +614,7 @@ information in the normal (i.e., master) @code{.newsrc} file. @findex gnus-fetch-group It is sometimes convenient to be able to just say ``I want to read this -group and I don't care whether Gnus has been started or not''. This is +group and I don't care whether gnus has been started or not''. This is perhaps more useful for people who write code than for users, but the command @code{gnus-fetch-group} provides this functionality in any case. It takes the group name as a parameter. @@ -624,13 +632,13 @@ also save you some time at startup. Even if this variable is @code{nil}, you can always subscribe to the new groups just by pressing @kbd{U} in the group buffer (@pxref{Group Maintenance}). This variable is @code{ask-server} by default. If you set this variable to -@code{always}, then Gnus will query the backends for new groups even +@code{always}, then gnus will query the backends for new groups even when you do the @kbd{g} command (@pxref{Scanning New Messages}). @menu * Checking New Groups:: Determining what groups are new. -* Subscription Methods:: What Gnus should do with new groups. -* Filtering New Groups:: Making Gnus ignore certain new groups. +* Subscription Methods:: What gnus should do with new groups. +* Filtering New Groups:: Making gnus ignore certain new groups. @end menu @@ -640,7 +648,7 @@ when you do the @kbd{g} command (@pxref{Scanning New Messages}). Gnus normally determines whether a group is new or not by comparing the list of groups from the active file(s) with the lists of subscribed and dead groups. This isn't a particularly fast method. If -@code{gnus-check-new-newsgroups} is @code{ask-server}, Gnus will ask the +@code{gnus-check-new-newsgroups} is @code{ask-server}, gnus will ask the server for new groups since the last time. This is both faster and cheaper. This also means that you can get rid of the list of killed groups altogether, so you may set @code{gnus-save-killed-list} to @@ -652,15 +660,15 @@ I bet I know what you're thinking now: How do I find out whether my server supports @code{ask-server}? No? Good, because I don't have a fail-safe answer. I would suggest just setting this variable to @code{ask-server} and see whether any new groups appear within the next -few days. If any do, then it works. If none do, then it doesn't -work. I could write a function to make Gnus guess whether the server -supports @code{ask-server}, but it would just be a guess. So I won't. -You could @code{telnet} to the server and say @code{HELP} and see -whether it lists @samp{NEWGROUPS} among the commands it understands. If -it does, then it might work. (But there are servers that lists -@samp{NEWGROUPS} without supporting the function properly.) - -This variable can also be a list of select methods. If so, Gnus will +few days. If any do, then it works. If none do, then it doesn't work. +I could write a function to make gnus guess whether the server supports +@code{ask-server}, but it would just be a guess. So I won't. You could +@code{telnet} to the server and say @code{HELP} and see whether it lists +@samp{NEWGROUPS} among the commands it understands. If it does, then it +might work. (But there are servers that lists @samp{NEWGROUPS} without +supporting the function properly.) + +This variable can also be a list of select methods. If so, gnus will issue an @code{ask-server} command to each of the select methods, and subscribe them (or not) using the normal methods. This might be handy if you are monitoring a few servers for new groups. A side effect is @@ -672,7 +680,7 @@ Use the mantra ``dingnusdingnusdingnus'' to achieve permanent bliss. @subsection Subscription Methods @vindex gnus-subscribe-newsgroup-method -What Gnus does when it encounters a new group is determined by the +What gnus does when it encounters a new group is determined by the @code{gnus-subscribe-newsgroup-method} variable. This variable should contain a function. This function will be called @@ -709,9 +717,9 @@ up. Or something like that. @item gnus-subscribe-interactively @vindex gnus-subscribe-interactively -Subscribe new groups interactively. This means that Gnus will ask -you about @strong{all} new groups. The groups you choose to subscribe -to will be subscribed hierarchically. +Subscribe new groups interactively. This means that gnus will ask you +about @strong{all} new groups. The groups you choose to subscribe to +will be subscribed hierarchically. @item gnus-subscribe-killed @vindex gnus-subscribe-killed @@ -722,7 +730,7 @@ Kill all new groups. @vindex gnus-subscribe-hierarchical-interactive A closely related variable is @code{gnus-subscribe-hierarchical-interactive}. (That's quite a -mouthful.) If this variable is non-@code{nil}, Gnus will ask you in a +mouthful.) If this variable is non-@code{nil}, gnus will ask you in a hierarchical fashion whether to subscribe to new groups or not. Gnus will ask you for each sub-hierarchy whether you want to descend the hierarchy or not. @@ -834,11 +842,11 @@ that you have on your native groups. Use with caution. Now, you all know about the @file{.newsrc} file. All subscription information is traditionally stored in this file. -Things got a bit more complicated with @sc{gnus}. In addition to +Things got a bit more complicated with @sc{GNUS}. In addition to keeping the @file{.newsrc} file updated, it also used a file called @file{.newsrc.el} for storing all the information that didn't fit into the @file{.newsrc} file. (Actually, it also duplicated everything in -the @file{.newsrc} file.) @sc{gnus} would read whichever one of these +the @file{.newsrc} file.) @sc{GNUS} would read whichever one of these files was the most recently saved, which enabled people to swap between @sc{gnus} and other newsreaders. @@ -849,12 +857,14 @@ recent, but it will never write a @file{.newsrc.el} file. You should never delete the @file{.newsrc.eld} file---it contains much information not stored in the @file{.newsrc} file. +In addition, gnus does not change anything. Hail comrade Lars! + @vindex gnus-save-newsrc-file You can turn off writing the @file{.newsrc} file by setting @code{gnus-save-newsrc-file} to @code{nil}, which means you can delete -the file and save some space, as well as exiting from Gnus faster. +the file and save some space, as well as exiting from gnus faster. However, this will make it impossible to use other newsreaders than -Gnus. But hey, who would want to, right? +gnus. But hey, who would want to, right? @vindex gnus-save-killed-list If @code{gnus-save-killed-list} (default @code{t}) is @code{nil}, Gnus @@ -894,11 +904,11 @@ startup files. If you want to turn backup creation off, say something like: @end lisp @vindex gnus-init-file -When Gnus starts, it will read the @code{gnus-site-init-file} +When gnus starts, it will read the @code{gnus-site-init-file} (@file{.../site-lisp/gnus} by default) and @code{gnus-init-file} (@file{~/.gnus} by default) files. These are normal Emacs Lisp files and can be used to avoid cluttering your @file{~/.emacs} and -@file{site-init} files with Gnus stuff. Gnus will also check for files +@file{site-init} files with gnus stuff. Gnus will also check for files with the same names as these, but with @file{.elc} and @file{.el} suffixes. In other words, if you have set @code{gnus-init-file} to @file{~/.gnus}, it will look for @file{~/.gnus.elc}, @file{~/.gnus.el}, @@ -911,24 +921,24 @@ and finally @file{~/.gnus} (in this order). @cindex dribble file @cindex auto-save -Whenever you do something that changes the Gnus data (reading articles, +Whenever you do something that changes the gnus data (reading articles, catching up, killing/subscribing groups), the change is added to a special @dfn{dribble buffer}. This buffer is auto-saved the normal Emacs way. If your Emacs should crash before you have saved the @file{.newsrc} files, all changes you have made can be recovered from this file. -If Gnus detects this file at startup, it will ask the user whether to -read it. The auto save file is deleted whenever the real startup file is -saved. +If gnus detects this file at startup, it will ask the user whether to +read it. The auto save file is deleted whenever the real startup file +is saved. @vindex gnus-use-dribble-file -If @code{gnus-use-dribble-file} is @code{nil}, Gnus won't create and +If @code{gnus-use-dribble-file} is @code{nil}, gnus won't create and maintain a dribble buffer. The default is @code{t}. @vindex gnus-dribble-directory Gnus will put the dribble file(s) in @code{gnus-dribble-directory}. If -this variable is @code{nil}, which it is by default, Gnus will dribble +this variable is @code{nil}, which it is by default, gnus will dribble into the directory where the @file{.newsrc} file is located. (This is normally the user's home directory.) The dribble file will get the same file permissions as the @code{.newsrc} file. @@ -943,14 +953,14 @@ read the dribble file on startup without querying the user. @cindex active file @cindex ignored groups -When Gnus starts, or indeed whenever it tries to determine whether new +When gnus starts, or indeed whenever it tries to determine whether new articles have arrived, it reads the active file. This is a very large file that lists all the active groups and articles on the server. @vindex gnus-ignored-newsgroups -Before examining the active file, Gnus deletes all lines that match the +Before examining the active file, gnus deletes all lines that match the regexp @code{gnus-ignored-newsgroups}. This is done primarily to reject -any groups with bogus names, but you can use this variable to make Gnus +any groups with bogus names, but you can use this variable to make gnus ignore hierarchies you aren't ever interested in. However, this is not recommended. In fact, it's highly discouraged. Instead, @pxref{New Groups} for an overview of other variables that can be used instead. @@ -962,15 +972,15 @@ Groups} for an overview of other variables that can be used instead. @vindex gnus-read-active-file @c @head The active file can be rather Huge, so if you have a slow network, you -can set @code{gnus-read-active-file} to @code{nil} to prevent Gnus from +can set @code{gnus-read-active-file} to @code{nil} to prevent gnus from reading the active file. This variable is @code{some} by default. Gnus will try to make do by getting information just on the groups that you actually subscribe to. Note that if you subscribe to lots and lots of groups, setting this -variable to @code{nil} will probably make Gnus slower, not faster. At -present, having this variable @code{nil} will slow Gnus down +variable to @code{nil} will probably make gnus slower, not faster. At +present, having this variable @code{nil} will slow gnus down considerably, unless you read news over a 2400 baud modem. This variable can also have the value @code{some}. Gnus will then @@ -980,9 +990,9 @@ support the @code{LIST ACTIVE group} command), on others this isn't fast at all. In any case, @code{some} should be faster than @code{nil}, and is certainly faster than @code{t} over slow lines. -If this variable is @code{nil}, Gnus will ask for group info in total +If this variable is @code{nil}, gnus will ask for group info in total lock-step, which isn't very fast. If it is @code{some} and you use an -@sc{nntp} server, Gnus will pump out commands as fast as it can, and +@sc{nntp} server, gnus will pump out commands as fast as it can, and read all the replies in one swoop. This will normally result in better performance, but if the server does not support the aforementioned @code{LIST ACTIVE group} command, this isn't very nice to the server. @@ -1001,21 +1011,21 @@ secondary select methods. @item gnus-load-hook @vindex gnus-load-hook -A hook run while Gnus is being loaded. Note that this hook will +A hook run while gnus is being loaded. Note that this hook will normally be run just once in each Emacs session, no matter how many -times you start Gnus. +times you start gnus. @item gnus-before-startup-hook @vindex gnus-before-startup-hook -A hook run after starting up Gnus successfully. +A hook run after starting up gnus successfully. @item gnus-startup-hook @vindex gnus-startup-hook -A hook run as the very last thing after starting up Gnus +A hook run as the very last thing after starting up gnus @item gnus-started-hook @vindex gnus-started-hook -A hook that is run as the very last thing after starting up Gnus +A hook that is run as the very last thing after starting up gnus successfully. @item gnus-started-hook @@ -1025,7 +1035,7 @@ generating the group buffer. @item gnus-check-bogus-newsgroups @vindex gnus-check-bogus-newsgroups -If non-@code{nil}, Gnus will check for and delete all bogus groups at +If non-@code{nil}, gnus will check for and delete all bogus groups at startup. A @dfn{bogus group} is a group that you have in your @file{.newsrc} file, but doesn't exist on the news server. Checking for bogus groups can take quite a while, so to save time and resources it's @@ -1041,11 +1051,11 @@ of doing your job. Note that this variable is used before @item gnus-no-groups-message @vindex gnus-no-groups-message -Message displayed by Gnus when no groups are available. +Message displayed by gnus when no groups are available. @item gnus-play-startup-jingle @vindex gnus-play-startup-jingle -If non-@code{nil}, play the Gnus jingle at startup. +If non-@code{nil}, play the gnus jingle at startup. @item gnus-startup-jingle @vindex gnus-startup-jingle @@ -1060,8 +1070,8 @@ default is @samp{Tuxedomoon.Jingle4.au}. @cindex group buffer The @dfn{group buffer} lists all (or parts) of the available groups. It -is the first buffer shown when Gnus starts, and will never be killed as -long as Gnus is active. +is the first buffer shown when gnus starts, and will never be killed as +long as gnus is active. @iftex @iflatex @@ -1141,7 +1151,7 @@ a @code{printf} specifications, for those of you who use (feh!) C. There should always be a colon on the line; the cursor always moves to the colon after performing an operation. Nothing else is required---not even the group name. All displayed text is just window dressing, and is -never examined by Gnus. Gnus stores all real information it needs using +never examined by gnus. Gnus stores all real information it needs using text properties. (Note that if you make a really strange, wonderful, spreadsheet-like @@ -1324,7 +1334,7 @@ topic being inserted. @end table When the forms are @code{eval}ed, point is at the beginning of the line -of the group in question, so you can use many of the normal Gnus +of the group in question, so you can use many of the normal gnus functions for snarfing info on the group. @vindex gnus-group-update-hook @@ -1423,11 +1433,11 @@ is @code{t}. Select the current group, switch to the summary buffer and display the first unread article (@code{gnus-group-read-group}). If there are no unread articles in the group, or if you give a non-numerical prefix to -this command, Gnus will offer to fetch all the old articles in this +this command, gnus will offer to fetch all the old articles in this group from the server. If you give a numerical prefix @var{N}, @var{N} -determines the number of articles Gnus will fetch. If @var{N} is -positive, Gnus fetches the @var{N} newest articles, if @var{N} is -negative, Gnus fetches the @var{abs(N)} oldest articles. +determines the number of articles gnus will fetch. If @var{N} is +positive, gnus fetches the @var{N} newest articles, if @var{N} is +negative, gnus fetches the @var{abs(N)} oldest articles. @item RET @kindex RET (Group) @@ -1446,7 +1456,7 @@ minimum amount of fuzz (@code{gnus-group-quick-select-group}). No scoring/killing will be performed, there will be no highlights and no expunging. This might be useful if you're in a real hurry and have to enter some humongous group. If you give a 0 prefix to this command -(i.e., @kbd{0 M-RET}), Gnus won't even generate the summary buffer, +(i.e., @kbd{0 M-RET}), gnus won't even generate the summary buffer, which is useful if you want to toggle threading before generating the summary buffer (@pxref{Summary Generation Commands}). @@ -1469,9 +1479,9 @@ manner will have no permanent effects. @end table @vindex gnus-large-newsgroup -The @code{gnus-large-newsgroup} variable says what Gnus should consider +The @code{gnus-large-newsgroup} variable says what gnus should consider to be a big group. This is 200 by default. If the group has more -(unread and/or ticked) articles than this, Gnus will query the user +(unread and/or ticked) articles than this, gnus will query the user before entering the group. The user can then specify how many articles should be fetched from the server. If the user specifies a negative number (@code{-n}), the @code{n} oldest articles will be fetched. If it @@ -1589,8 +1599,8 @@ Also @pxref{Group Levels}. @c @icon{gnus-group-catchup-current} Mark all unticked articles in this group as read (@code{gnus-group-catchup-current}). -@code{gnus-group-catchup-group-hook} is called when catching up a group from -the group buffer. +@code{gnus-group-catchup-group-hook} is called when catching up a group +from the group buffer. @item C @kindex C (Group) @@ -1622,7 +1632,7 @@ caution. All groups have a level of @dfn{subscribedness}. For instance, if a group is on level 2, it is more subscribed than a group on level 5. You -can ask Gnus to just list groups on a given level or lower +can ask gnus to just list groups on a given level or lower (@pxref{Listing Groups}), or to just check for new articles in groups on a given level or lower (@pxref{Scanning New Messages}). @@ -1856,7 +1866,7 @@ for a directory name (@code{gnus-group-make-directory-group}). @kindex G h (Group) @cindex help group @findex gnus-group-make-help-group -Make the Gnus help group (@code{gnus-group-make-help-group}). +Make the gnus help group (@code{gnus-group-make-help-group}). @item G a @kindex G a (Group) @@ -1865,7 +1875,7 @@ Make the Gnus help group (@code{gnus-group-make-help-group}). @findex gnus-group-make-archive-group @vindex gnus-group-archive-directory @vindex gnus-group-recent-archive-directory -Make a Gnus archive group (@code{gnus-group-make-archive-group}). By +Make a gnus archive group (@code{gnus-group-make-archive-group}). By default a group pointing to the most recent articles will be created (@code{gnus-group-recent-archive-directory}), but given a prefix, a full group will be created from @code{gnus-group-archive-directory}. @@ -1898,7 +1908,7 @@ command, you will be prompted for a file name and a file type. Currently supported types are @code{babyl}, @code{mbox}, @code{digest}, @code{mmdf}, @code{news}, @code{rnews}, @code{clari-briefs}, @code{rfc934}, @code{rfc822-forward}, and @code{forward}. If you run -this command without a prefix, Gnus will guess at the file type. +this command without a prefix, gnus will guess at the file type. @xref{Document Groups}. @item G u @@ -1954,7 +1964,7 @@ methods. @vindex gnus-activate-foreign-newsgroups If @code{gnus-activate-foreign-newsgroups} is a positive number, -Gnus will check all foreign groups with this level or lower at startup. +gnus will check all foreign groups with this level or lower at startup. This might take quite a while, especially if you subscribe to lots of groups from different @sc{nntp} servers. Also @pxref{Group Levels}; @code{gnus-activate-level} also affects activation of foreign @@ -1973,10 +1983,10 @@ Here's an example group parameter list: (auto-expire . t)) @end example -We see that each element consists of a "dotted pair"---the thing before -the dot is the key, while the thing after the dot is the value. All the -parameters have this form @emph{except} local variable specs, which are -not dotted pairs, but proper lists. +We see that each element consists of a ``dotted pair''---the thing +before the dot is the key, while the thing after the dot is the value. +All the parameters have this form @emph{except} local variable specs, +which are not dotted pairs, but proper lists. The following group parameters can be used: @@ -2045,7 +2055,7 @@ posts in that group will be sent to @code{some.group.name}. @item newsgroup @cindex newsgroup -If you have @code{(newsgroup . t)} in the group parameter list, Gnus +If you have @code{(newsgroup . t)} in the group parameter list, gnus will treat all responses as if they were responses to news articles. This can be useful if you have a mail group that's really a mirror of a news group. @@ -2115,10 +2125,9 @@ ticked articles. @end table @item comment -Elements that look like @code{(comment . "This is a comment")} -are arbitrary comments on the group. They are currently ignored by -Gnus, but provide a place for you to store information on particular -groups. +Elements that look like @code{(comment . "This is a comment")} are +arbitrary comments on the group. They are currently ignored by gnus, +but provide a place for you to store information on particular groups. @item @var{(variable form)} You can use the group parameters to set variables local to the group you @@ -2480,42 +2489,43 @@ there) (@code{gnus-browse-describe-briefly}). @node Exiting Gnus -@section Exiting Gnus -@cindex exiting Gnus +@section Exiting gnus +@cindex exiting gnus -Yes, Gnus is ex(c)iting. +Yes, gnus is ex(c)iting. @table @kbd @item z @kindex z (Group) @findex gnus-group-suspend -Suspend Gnus (@code{gnus-group-suspend}). This doesn't really exit Gnus, -but it kills all buffers except the Group buffer. I'm not sure why this -is a gain, but then who am I to judge? +Suspend gnus (@code{gnus-group-suspend}). This doesn't really exit +gnus, but it kills all buffers except the Group buffer. I'm not sure +why this is a gain, but then who am I to judge? @item q @kindex q (Group) @findex gnus-group-exit @c @icon{gnus-group-exit} -Quit Gnus (@code{gnus-group-exit}). +Quit gnus (@code{gnus-group-exit}). @item Q @kindex Q (Group) @findex gnus-group-quit -Quit Gnus without saving the @file{.newsrc} files (@code{gnus-group-quit}). -The dribble file will be saved, though (@pxref{Auto Save}). +Quit gnus without saving the @file{.newsrc} files +(@code{gnus-group-quit}). The dribble file will be saved, though +(@pxref{Auto Save}). @end table @vindex gnus-exit-gnus-hook @vindex gnus-suspend-gnus-hook -@code{gnus-suspend-gnus-hook} is called when you suspend Gnus and -@code{gnus-exit-gnus-hook} is called when you quit Gnus, while +@code{gnus-suspend-gnus-hook} is called when you suspend gnus and +@code{gnus-exit-gnus-hook} is called when you quit gnus, while @code{gnus-after-exiting-gnus-hook} is called as the final item when -exiting Gnus. +exiting gnus. @findex gnus-unload @cindex unloading -If you wish to completely unload Gnus and all its adherents, you can use +If you wish to completely unload gnus and all its adherents, you can use the @code{gnus-unload} command. This command is also very handy when trying to customize meta-variables. @@ -2759,7 +2769,7 @@ Delete an empty topic (@code{gnus-topic-delete}). @item A T @kindex A T (Topic) @findex gnus-topic-list-active -List all groups that Gnus knows about in a topics-ified way +List all groups that gnus knows about in a topics-ified way (@code{gnus-topic-list-active}). @item G p @@ -2923,10 +2933,10 @@ happens. You just have to be careful if you do stuff like that. @section Misc Group Stuff @menu -* Scanning New Messages:: Asking Gnus to see whether new messages have arrived. -* Group Information:: Information and help on groups and Gnus. -* Group Timestamp:: Making Gnus keep track of when you last read a group. -* File Commands:: Reading and writing the Gnus files. +* Scanning New Messages:: Asking gnus to see whether new messages have arrived. +* Group Information:: Information and help on groups and gnus. +* Group Timestamp:: Making gnus keep track of when you last read a group. +* File Commands:: Reading and writing the gnus files. @end menu @table @kbd @@ -3015,9 +3025,9 @@ Activate absolutely all groups (@code{gnus-activate-all-groups}). @kindex R (Group) @cindex restarting @findex gnus-group-restart -Restart Gnus (@code{gnus-group-restart}). This saves the @file{.newsrc} +Restart gnus (@code{gnus-group-restart}). This saves the @file{.newsrc} file(s), closes the connection to all servers, clears up all run-time -Gnus variables, and then starts Gnus all over again. +gnus variables, and then starts gnus all over again. @end table @@ -3051,7 +3061,7 @@ that case, giving a prefix to this command will allow you to choose between the various sites. @code{ange-ftp} (or @code{efs}) will be used for fetching the file. -If fetching from the first site is unsuccessful, Gnus will attempt to go +If fetching from the first site is unsuccessful, gnus will attempt to go through @code{gnus-group-faq-directory} and try to open them one by one. @item H d @@ -3069,7 +3079,7 @@ a prefix, force Gnus to re-read the description from the server. @kindex M-d (Group) @findex gnus-group-describe-all-groups Describe all groups (@code{gnus-group-describe-all-groups}). If given a -prefix, force Gnus to re-read the description file from the server. +prefix, force gnus to re-read the description file from the server. @item H v @itemx V @@ -3077,7 +3087,7 @@ prefix, force Gnus to re-read the description file from the server. @kindex H v (Group) @cindex version @findex gnus-version -Display current Gnus version numbers (@code{gnus-version}). +Display current gnus version numbers (@code{gnus-version}). @item ? @kindex ? (Group) @@ -3089,7 +3099,7 @@ Give a very short help message (@code{gnus-group-describe-briefly}). @cindex info @cindex manual @findex gnus-info-find-node -Go to the Gnus info node (@code{gnus-info-find-node}). +Go to the gnus info node (@code{gnus-info-find-node}). @end table @@ -3098,7 +3108,7 @@ Go to the Gnus info node (@code{gnus-info-find-node}). @cindex timestamps @cindex group timestamps -It can be convenient to let Gnus keep track of when you last read a +It can be convenient to let gnus keep track of when you last read a group. To set the ball rolling, you should add @code{gnus-group-set-timestamp} to @code{gnus-select-group-hook}: @@ -3230,12 +3240,14 @@ You can have as many summary buffers open as you wish. @vindex gnus-extract-address-components Gnus will use the value of the @code{gnus-extract-address-components} variable as a function for getting the name and address parts of a -@code{From} header. Two pre-defined functions exist: +@code{From} header. Three pre-defined functions exist: @code{gnus-extract-address-components}, which is the default, quite -fast, and too simplistic solution; and -@code{mail-extract-address-components}, which works very nicely, but is -slower. The default function will return the wrong answer in 5% of the -cases. If this is unacceptable to you, use the other function instead. +fast, and too simplistic solution; +@code{mail-extract-address-components}, which works nicely, but is +slower; and @code{std11-extract-address-components}, which works very +nicely, but is slower. The default function will return the wrong +answer in 5% of the cases. If this is unacceptable to you, use the +other function instead. @vindex gnus-summary-same-subject @code{gnus-summary-same-subject} is a string indicating that the current @@ -3346,7 +3358,7 @@ into the summary just like information from any other summary specifier. @end table The @samp{%U} (status), @samp{%R} (replied) and @samp{%z} (zcore) specs -have to be handled with care. For reasons of efficiency, Gnus will +have to be handled with care. For reasons of efficiency, gnus will compute what column these characters will end up in, and ``hard-code'' that. This means that it is invalid to have these specs after a variable-length spec. Well, you might not be arrested, but your summary @@ -3355,7 +3367,7 @@ buffer will look strange, which is bad enough. The smart choice is to have these specs as far to the left as possible. (Isn't that the case with everything, though? But I digress.) -This restriction may disappear in later versions of Gnus. +This restriction may disappear in later versions of gnus. @node Summary Buffer Mode Line @@ -3486,7 +3498,7 @@ Ask for an article number and then go to the summary line of that article without displaying the article (@code{gnus-summary-goto-subject}). @end table -If Gnus asks you to press a key to confirm going to the next group, you +If gnus asks you to press a key to confirm going to the next group, you can use the @kbd{C-n} and @kbd{C-p} keys to move around the group buffer, searching for the next group to read without actually returning to the group buffer. @@ -3498,12 +3510,12 @@ Variables related to summary movement: @vindex gnus-auto-select-next @item gnus-auto-select-next If you issue one of the movement commands (like @kbd{n}) and there are -no more unread articles after the current one, Gnus will offer to go to +no more unread articles after the current one, gnus will offer to go to the next group. If this variable is @code{t} and the next group is -empty, Gnus will exit summary mode and return to the group buffer. If -this variable is neither @code{t} nor @code{nil}, Gnus will select the +empty, gnus will exit summary mode and return to the group buffer. If +this variable is neither @code{t} nor @code{nil}, gnus will select the next group, no matter whether it has any unread articles or not. As a -special case, if this variable is @code{quietly}, Gnus will select the +special case, if this variable is @code{quietly}, gnus will select the next group without asking for confirmation. If this variable is @code{almost-quietly}, the same will happen only if you are located on the last article in the group. Finally, if this variable is @@ -3528,7 +3540,7 @@ Instead, they will choose the current article. @item gnus-auto-center-summary @vindex gnus-auto-center-summary -If non-@code{nil}, Gnus will keep the point in the summary buffer +If non-@code{nil}, gnus will keep the point in the summary buffer centered at all times. This makes things quite tidy, but if you have a slow network connection, or simply do not like this un-Emacsism, you can set this variable to @code{nil} to get the normal Emacs scrolling @@ -3826,7 +3838,7 @@ reason (wrong address, transient failure), you can use this command to resend that bounced mail (@code{gnus-summary-resend-bounced-mail}). You will be popped into a mail buffer where you can edit the headers before sending the mail off again. If you give a prefix to this command, and -the bounced mail is a reply to some other mail, Gnus will try to fetch +the bounced mail is a reply to some other mail, gnus will try to fetch that mail and display it for easy perusal of its headers. This might very well fail, though. @@ -3846,7 +3858,7 @@ This command is mainly used if you have several accounts and want to ship a mail to a different account of yours. (If you're both @code{root} and @code{postmaster} and get a mail for @code{postmaster} to the @code{root} account, you may want to resend it to -@code{postmaster}. Ordnung muß sein! +@code{postmaster}. Ordnung mu,A_(B sein! This command understands the process/prefix convention (@pxref{Process/Prefix}). @@ -4007,7 +4019,7 @@ header by substituting one of those words for the word you would do normally. The previous article will be canceled/superseded. -Just remember, kids: There is no 'c' in 'supersede'. +Just remember, kids: There is no `c' in `supersede'. @node Marking Articles @@ -4145,8 +4157,7 @@ Marked as expirable (@code{gnus-expirable-mark}). Marking articles as @dfn{expirable} (or have them marked as such automatically) doesn't make much sense in normal groups---a user doesn't control expiring of news articles, but in mail groups, for instance, -articles marked as @dfn{expirable} can be deleted by Gnus at -any time. +articles marked as @dfn{expirable} can be deleted by gnus at any time. @end table @@ -4164,7 +4175,7 @@ read or not. You can set a bookmark in the current article. Say you are reading a long thesis on cats' urinary tracts, and have to go home for dinner before you've finished reading the thesis. You can then set a bookmark -in the article, and Gnus will jump to this bookmark the next time it +in the article, and gnus will jump to this bookmark the next time it encounters the article. @xref{Setting Marks} @item @@ -4635,7 +4646,7 @@ displayed as empty lines in the summary buffer. @cindex customizing threading @menu -* Loose Threads:: How Gnus gathers loose threads into bigger threads. +* Loose Threads:: How gnus gathers loose threads into bigger threads. * Filling In Threads:: Making the threads displayed look fuller. * More Threading:: Even more variables for fiddling with threads. * Low-Level Threading:: You thought it was over... but you were wrong! @@ -4651,13 +4662,13 @@ displayed as empty lines in the summary buffer. @table @code @item gnus-summary-make-false-root @vindex gnus-summary-make-false-root -If non-@code{nil}, Gnus will gather all loose subtrees into one big tree +If non-@code{nil}, gnus will gather all loose subtrees into one big tree and create a dummy root at the top. (Wait a minute. Root at the top? Yup.) Loose subtrees occur when the real root has expired, or you've read or killed the root in a previous session. -When there is no real root of a thread, Gnus will have to fudge -something. This variable says what fudging method Gnus should use. +When there is no real root of a thread, gnus will have to fudge +something. This variable says what fudging method gnus should use. There are four possible values: @iftex @@ -4707,17 +4718,17 @@ Don't gather loose threads. @item gnus-summary-gather-subject-limit @vindex gnus-summary-gather-subject-limit Loose threads are gathered by comparing subjects of articles. If this -variable is @code{nil}, Gnus requires an exact match between the +variable is @code{nil}, gnus requires an exact match between the subjects of the loose threads before gathering them into one big super-thread. This might be too strict a requirement, what with the presence of stupid newsreaders that chop off long subject lines. If you think so, set this variable to, say, 20 to require that only the first 20 characters of the subjects have to match. If you set this -variable to a really low number, you'll find that Gnus will gather +variable to a really low number, you'll find that gnus will gather everything in sight into one thread, which isn't very helpful. @cindex fuzzy article gathering -If you set this variable to the special value @code{fuzzy}, Gnus will +If you set this variable to the special value @code{fuzzy}, gnus will use a fuzzy string comparison algorithm on the subjects (@pxref{Fuzzy Matching}). @@ -4831,16 +4842,16 @@ something like: @table @code @item gnus-fetch-old-headers @vindex gnus-fetch-old-headers -If non-@code{nil}, Gnus will attempt to build old threads by fetching -more old headers---headers to articles marked as read. If you -would like to display as few summary lines as possible, but still -connect as many loose threads as possible, you should set this variable -to @code{some} or a number. If you set it to a number, no more than -that number of extra old headers will be fetched. In either case, -fetching old headers only works if the backend you are using carries -overview files---this would normally be @code{nntp}, @code{nnspool} and +If non-@code{nil}, gnus will attempt to build old threads by fetching +more old headers---headers to articles marked as read. If you would +like to display as few summary lines as possible, but still connect as +many loose threads as possible, you should set this variable to +@code{some} or a number. If you set it to a number, no more than that +number of extra old headers will be fetched. In either case, fetching +old headers only works if the backend you are using carries overview +files---this would normally be @code{nntp}, @code{nnspool} and @code{nnml}. Also remember that if the root of the thread has been -expired by the server, there's not much Gnus can do about that. +expired by the server, there's not much gnus can do about that. This variable can also be set to @code{invisible}. This won't have any visible effects, but is useful if you use the @kbd{A T} command a lot @@ -4852,12 +4863,12 @@ Fetching old headers can be slow. A low-rent similar effect can be gotten by setting this variable to @code{some}. Gnus will then look at the complete @code{References} headers of all articles and try to string together articles that belong in the same thread. This will leave -@dfn{gaps} in the threading display where Gnus guesses that an article +@dfn{gaps} in the threading display where gnus guesses that an article is missing from the thread. (These gaps appear like normal summary -lines. If you select a gap, Gnus will try to fetch the article in -question.) If this variable is @code{t}, Gnus will display all these +lines. If you select a gap, gnus will try to fetch the article in +question.) If this variable is @code{t}, gnus will display all these ``gaps'' without regard for whether they are useful for completing the -thread or not. Finally, if this variable is @code{more}, Gnus won't cut +thread or not. Finally, if this variable is @code{more}, gnus won't cut off sparse leaf nodes that don't lead anywhere. This variable is @code{nil} by default. @@ -4915,9 +4926,9 @@ The default is 4. @item gnus-parse-headers-hook @vindex gnus-parse-headers-hook Hook run before parsing any headers. The default value is -@code{(gnus-decode-rfc1522)}, which means that QPized headers will be -slightly decoded in a hackish way. This is likely to change in the -future when Gnus becomes @sc{MIME}ified. +@code{(gnus-set-summary-default-charset)}, which sets up local value of +@code{default-mime-charset} in summary buffer based on variable +@code{gnus-newsgroup-default-charset-alist}. @item gnus-alter-header-function @vindex gnus-alter-header-function @@ -5167,22 +5178,22 @@ say something like: If you read your news from an @sc{nntp} server that's far away, the network latencies may make reading articles a chore. You have to wait for a while after pressing @kbd{n} to go to the next article before the -article appears. Why can't Gnus just go ahead and fetch the article +article appears. Why can't gnus just go ahead and fetch the article while you are reading the previous one? Why not, indeed. First, some caveats. There are some pitfalls to using asynchronous -article fetching, especially the way Gnus does it. +article fetching, especially the way gnus does it. Let's say you are reading article 1, which is short, and article 2 is quite long, and you are not interested in reading that. Gnus does not know this, so it goes ahead and fetches article 2. You decide to read -article 3, but since Gnus is in the process of fetching article 2, the +article 3, but since gnus is in the process of fetching article 2, the connection is blocked. -To avoid these situations, Gnus will open two (count 'em two) +To avoid these situations, gnus will open two (count 'em two) connections to the server. Some people may think this isn't a very nice thing to do, but I don't see any real alternatives. Setting up that -extra connection takes some time, so Gnus startup will be slower. +extra connection takes some time, so gnus startup will be slower. Gnus will fetch more articles than you will read. This will mean that the link between your machine and the @sc{nntp} server will become more @@ -5214,7 +5225,8 @@ pre-fetched. The default is @code{gnus-async-read-p}, which returns @code{nil} on read articles. The function is called with an article data structure as the only parameter. -If, for instance, you wish to pre-fetch only unread articles shorter than 100 lines, you could say something like: +If, for instance, you wish to pre-fetch only unread articles shorter +than 100 lines, you could say something like: @lisp (defun my-async-short-unread-p (data) @@ -5227,8 +5239,8 @@ If, for instance, you wish to pre-fetch only unread articles shorter than 100 li @end lisp These functions will be called many, many times, so they should -preferably be short and sweet to avoid slowing down Gnus too much. -It's probably a good idea to byte-compile things like this. +preferably be short and sweet to avoid slowing down gnus too much. It's +probably a good idea to byte-compile things like this. @vindex gnus-prefetched-article-deletion-strategy Articles have to be removed from the asynch buffer sooner or later. The @@ -5320,7 +5332,7 @@ variables, the group is not cached. @vindex gnus-cache-active-file The cache stores information on what articles it contains in its active file (@code{gnus-cache-active-file}). If this file (or any other parts -of the cache) becomes all messed up for some reason or other, Gnus +of the cache) becomes all messed up for some reason or other, gnus offers two functions that will try to set things right. @kbd{M-x gnus-cache-generate-nov-databases} will (re)build all the @sc{nov} files, and @kbd{gnus-cache-generate-active} will (re)generate the active @@ -5379,17 +5391,17 @@ interested in persistent articles: If you have a slow connection, but the idea of using caching seems unappealing to you (and it is, really), you can help the situation some -by switching on the @dfn{backlog}. This is where Gnus will buffer +by switching on the @dfn{backlog}. This is where gnus will buffer already read articles so that it doesn't have to re-fetch articles you've already read. This only helps if you are in the habit of re-selecting articles you've recently read, of course. If you never do -that, turning the backlog on will slow Gnus down a little bit, and +that, turning the backlog on will slow gnus down a little bit, and increase memory usage some. @vindex gnus-keep-backlog -If you set @code{gnus-keep-backlog} to a number @var{n}, Gnus will store +If you set @code{gnus-keep-backlog} to a number @var{n}, gnus will store at most @var{n} old articles in a buffer for later re-fetching. If this -variable is non-@code{nil} and is not a number, Gnus will store +variable is non-@code{nil} and is not a number, gnus will store @emph{all} read articles, which means that your Emacs will grow without bound before exploding and taking your machine down with you. I put that in there just to keep y'all on your toes. @@ -5408,7 +5420,7 @@ approach (uudecoding, unsharing) you should use @code{gnus-uu} (@pxref{Decoding Articles}). @vindex gnus-save-all-headers -If @code{gnus-save-all-headers} is non-@code{nil}, Gnus will not delete +If @code{gnus-save-all-headers} is non-@code{nil}, gnus will not delete unwanted headers before saving the article. @vindex gnus-saved-headers @@ -5494,7 +5506,7 @@ files. @vindex gnus-default-article-saver You can customize the @code{gnus-default-article-saver} variable to make -Gnus do what you want it to. You can use any of the four ready-made +gnus do what you want it to. You can use any of the four ready-made functions below, or you can create your own. @table @code @@ -5577,11 +5589,11 @@ File names like @file{~/News/alt.andrea-dworkin}. @end table @vindex gnus-split-methods -You can have Gnus suggest where to save articles by plonking a regexp into -the @code{gnus-split-methods} alist. For instance, if you would like to -save articles related to Gnus in the file @file{gnus-stuff}, and articles -related to VM in @code{vm-stuff}, you could set this variable to something -like: +You can have gnus suggest where to save articles by plonking a regexp +into the @code{gnus-split-methods} alist. For instance, if you would +like to save articles related to gnus in the file @file{gnus-stuff}, and +articles related to VM in @code{vm-stuff}, you could set this variable +to something like: @lisp (("^Subject:.*gnus\\|^Newsgroups:.*gnus" "gnus-stuff") @@ -5606,9 +5618,8 @@ then be prompted for what you really want to use as a name, with file name completion over the results from applying this variable. This variable is @code{((gnus-article-archive-name))} by default, which -means that Gnus will look at the articles it saves for an -@code{Archive-name} line and use that as a suggestion for the file -name. +means that gnus will look at the articles it saves for an +@code{Archive-name} line and use that as a suggestion for the file name. Here's an example function to clean up file names somewhat. If you have lots of mail groups called things like @@ -5687,7 +5698,7 @@ Gnus guesses what articles are in the series according to the following simplish rule: The subjects must be (nearly) identical, except for the last two numbers of the line. (Spaces are largely ignored, however.) -For example: If you choose a subject called @samp{cat.gif (2/3)}, Gnus +For example: If you choose a subject called @samp{cat.gif (2/3)}, gnus will find all the articles that match the regexp @samp{^cat.gif ([0-9]+/[0-9]+).*$}. @@ -5735,7 +5746,7 @@ entire newsgroup, you'd typically do @kbd{M P a} (@code{gnus-uu-decode-uu-and-save}). All this is very much different from how @code{gnus-uu} worked with -@sc{gnus 4.1}, where you had explicit keystrokes for everything under +@sc{GNUS 4.1}, where you had explicit keystrokes for everything under the sun. This version of @code{gnus-uu} generally assumes that you mark articles in some way (@pxref{Setting Process Marks}) and then press @kbd{X u}. @@ -5873,7 +5884,7 @@ say something like: @item gnus-uu-user-view-rules-end @vindex gnus-uu-user-view-rules-end -This variable is consulted if Gnus couldn't make any matches from the +This variable is consulted if gnus couldn't make any matches from the user and default view rules. @item gnus-uu-user-archive-rules @@ -6028,15 +6039,15 @@ Default is @code{t}. @cindex viewing files @cindex pseudo-articles -After decoding, if the file is some sort of archive, Gnus will attempt +After decoding, if the file is some sort of archive, gnus will attempt to unpack the archive and see if any of the files in the archive can be viewed. For instance, if you have a gzipped tar file @file{pics.tar.gz} -containing the files @file{pic1.jpg} and @file{pic2.gif}, Gnus will +containing the files @file{pic1.jpg} and @file{pic2.gif}, gnus will uncompress and de-tar the main file, and then view the two pictures. This unpacking process is recursive, so if the archive contains archives of archives, it'll all be unpacked. -Finally, Gnus will normally insert a @dfn{pseudo-article} for each +Finally, gnus will normally insert a @dfn{pseudo-article} for each extracted file into the summary buffer. If you go to these ``articles'', you will be prompted for a command to run (usually Gnus will make a suggestion), and then the command will be run. @@ -6147,7 +6158,7 @@ Maximum possible length for a citation prefix (default 20). @vindex gnus-cite-face-list List of faces used for highlighting citations (@pxref{Faces and Fonts}). When there are citations from multiple articles in the same message, -Gnus will try to give each citation from each article its own face. +gnus will try to give each citation from each article its own face. This should make it easier to see who wrote what. @item gnus-supercite-regexp @@ -6421,7 +6432,7 @@ Toggle whether to display all headers in the article buffer permanently @item W m @kindex W m (Summary) @findex gnus-summary-toggle-mime -Toggle whether to run the article through @sc{mime} before displaying +Toggle whether to display the article as @sc{mime} message (@code{gnus-summary-toggle-mime}). @item W o @@ -6450,15 +6461,6 @@ when filling. Remove CR (i. e., @samp{^M}s on the end of the lines) (@code{gnus-article-remove-cr}). -@item W q -@kindex W q (Summary) -@findex gnus-article-de-quoted-unreadable -Treat quoted-printable (@code{gnus-article-de-quoted-unreadable}). -Quoted-Printable is one common @sc{mime} encoding employed when sending -non-ASCII (i. e., 8-bit) articles. It typically makes strings like -@samp{déjà vu} look like @samp{d=E9j=E0 vu}, which doesn't look very -readable to me. - @item W f @kindex W f (Summary) @cindex x-face @@ -6845,9 +6847,9 @@ summary buffer, point will just move to this article. If given a positive numerical prefix, fetch that many articles back into the ancestry. If given a negative numerical prefix, fetch just that -ancestor. So if you say @kbd{3 ^}, Gnus will fetch the parent, the +ancestor. So if you say @kbd{3 ^}, gnus will fetch the parent, the grandparent and the grandgrandparent of the current article. If you say -@kbd{-3 ^}, Gnus will only fetch the grandgrandparent of the current +@kbd{-3 ^}, gnus will only fetch the grandgrandparent of the current article. @item A R (Summary) @@ -6911,7 +6913,7 @@ consuming.) @code{nnmh} does not support this at all. @section Alternative Approaches Different people like to read news using different methods. This being -Gnus, we offer a small selection of minor modes for the summary buffers. +gnus, we offer a small selection of minor modes for the summary buffers. @menu * Pick and Read:: First mark articles and then read them. @@ -7030,7 +7032,7 @@ command, when you have turned on this mode @cindex trees @vindex gnus-use-trees -If you don't like the normal Gnus summary display, you might try setting +If you don't like the normal gnus summary display, you might try setting @code{gnus-use-trees} to @code{t}. This will create (by default) an additional @dfn{tree buffer}. You can execute all summary mode commands in the tree buffer. @@ -7099,8 +7101,8 @@ nodes to their children. The default is @code{(?- ?\\ ?|)}. @item gnus-tree-minimize-window @vindex gnus-tree-minimize-window -If this variable is non-@code{nil}, Gnus will try to keep the tree -buffer as small as possible to allow more room for the other Gnus +If this variable is non-@code{nil}, gnus will try to keep the tree +buffer as small as possible to allow more room for the other gnus windows. If this variable is a number, the tree buffer will never be higher than that number. The default is @code{t}. Note that if you have several windows displayed side-by-side in a frame and the tree @@ -7246,7 +7248,7 @@ which means that the current group select method will be used instead. Edit the current article (@code{gnus-summary-edit-article}). To finish editing and make the changes permanent, type @kbd{C-c C-c} (@kbd{gnus-summary-edit-article-done}). If you give a prefix to the -@kbd{C-c C-c} command, Gnus won't re-highlight the article. +@kbd{C-c C-c} command, gnus won't re-highlight the article. @item B q @kindex B q (Summary) @@ -7279,7 +7281,7 @@ just not have arrived yet. @vindex gnus-move-split-methods @cindex moving articles -If you move (or copy) articles regularly, you might wish to have Gnus +If you move (or copy) articles regularly, you might wish to have gnus suggest where to put the articles. @code{gnus-move-split-methods} is a variable that uses the same syntax as @code{gnus-split-methods} (@pxref{Saving Articles}). You may customize that variable to create @@ -7324,11 +7326,11 @@ some other ungodly manner. I don't care. @vindex gnus-summary-ignore-duplicates @item gnus-summary-ignore-duplicates -When Gnus discovers two articles that have the same @code{Message-ID}, +When gnus discovers two articles that have the same @code{Message-ID}, it has to do something drastic. No articles are allowed to have the same @code{Message-ID}, but this may happen when reading mail from some sources. Gnus allows you to customize what happens with this variable. -If it is @code{nil} (which is the default), Gnus will rename the +If it is @code{nil} (which is the default), gnus will rename the @code{Message-ID} (for display purposes only) and display the article as any other article. If this variable is @code{t}, it won't display the article---it'll be as if it never existed. @@ -7369,7 +7371,7 @@ keystrokes (@code{gnus-summary-describe-briefly}). @item H i @kindex H i (Summary) @findex gnus-info-find-node -Go to the Gnus info node (@code{gnus-info-find-node}). +Go to the gnus info node (@code{gnus-info-find-node}). @end table @@ -7577,7 +7579,7 @@ group. @vindex gnus-kill-summary-on-exit If you're in the habit of exiting groups, and then changing your mind about it, you might set @code{gnus-kill-summary-on-exit} to @code{nil}. -If you do that, Gnus won't kill the summary buffer when you exit it. +If you do that, gnus won't kill the summary buffer when you exit it. (Quelle surprise!) Instead it will change the name of the buffer to something like @samp{*Dead Summary ... *} and install a minor mode called @code{gnus-dead-summary-mode}. Now, if you switch back to this @@ -7654,11 +7656,10 @@ For an alternative approach, @pxref{Duplicate Suppression}. @node Duplicate Suppression @section Duplicate Suppression -By default, Gnus tries to make sure that you don't have to read the same +By default, gnus tries to make sure that you don't have to read the same article more than once by utilizing the crossposting mechanism (@pxref{Crosspost Handling}). However, that simple and efficient -approach may not work satisfactory for some users for various -reasons. +approach may not work satisfactory for some users for various reasons. @enumerate @item @@ -7705,7 +7706,7 @@ If non-@code{nil}, suppress duplicates. @vindex gnus-save-duplicate-list If non-@code{nil}, save the list of duplicates to a file. This will make startup and shutdown take longer, so the default is @code{nil}. -However, this means that only duplicate articles read in a single Gnus +However, this means that only duplicate articles read in a single gnus session are suppressed. @item gnus-duplicate-list-length @@ -7719,11 +7720,11 @@ The name of the file to store the duplicate suppression list in. The default is @file{~/News/suppression}. @end table -If you have a tendency to stop and start Gnus often, setting +If you have a tendency to stop and start gnus often, setting @code{gnus-save-duplicate-list} to @code{t} is probably a good idea. If -you leave Gnus running for weeks on end, you may have it @code{nil}. On +you leave gnus running for weeks on end, you may have it @code{nil}. On the other hand, saving the list makes startup and shutdown much slower, -so that means that if you stop and start Gnus often, you should set +so that means that if you stop and start gnus often, you should set @code{gnus-save-duplicate-list} to @code{nil}. Uhm. I'll leave this up to you to figure out, I think. @@ -7734,11 +7735,11 @@ to you to figure out, I think. The articles are displayed in the article buffer, of which there is only one. All the summary buffers share the same article buffer unless you -tell Gnus otherwise. +tell gnus otherwise. @menu * Hiding Headers:: Deciding what headers should be displayed. -* Using MIME:: Pushing articles through @sc{mime} before reading them. +* Using MIME:: Pushing to mime articles as @sc{mime} messages. * Customizing Articles:: Tailoring the look of the articles. * Article Keymap:: Keystrokes available in the article buffer. * Misc Article:: Other stuff. @@ -7790,8 +7791,8 @@ variable is set (and @code{gnus-visible-headers} is @code{nil}), it should be a regular expression that matches all lines that you want to hide. All lines that do not match this variable will remain visible. -For instance, if you just want to get rid of the @code{References} line -and the @code{Xref} line, you might say: +For instance, if you just want to get rid of the @code{References} field +and the @code{Xref} field, you might say: @lisp (setq gnus-ignored-headers "^References:\\|^Xref:") @@ -7819,7 +7820,8 @@ and then the subject, you might say something like: @end lisp Any headers that are to remain visible, but are not listed in this -variable, will be displayed in random order after all the headers listed in this variable. +variable, will be displayed in random order after all the headers listed +in this variable. @findex gnus-article-hide-boring-headers @vindex gnus-article-display-hook @@ -7829,7 +7831,7 @@ You can hide further boring headers by entering @code{gnus-article-display-hook}. What this function does depends on the @code{gnus-boring-article-headers} variable. It's a list, but this list doesn't actually contain header names. Instead is lists various -@dfn{boring conditions} that Gnus can check and remove from sight. +@dfn{boring conditions} that gnus can check and remove from sight. These conditions are: @table @code @@ -7878,22 +7880,15 @@ of the characters, and it also makes it possible to embed pictures and other naughty stuff in innocent-looking articles. @vindex gnus-show-mime -@vindex gnus-show-mime-method +@vindex gnus-article-display-method-for-mime @vindex gnus-strict-mime -@findex metamail-buffer +@findex gnus-article-display-mime-message Gnus handles @sc{mime} by pushing the articles through -@code{gnus-show-mime-method}, which is @code{metamail-buffer} by -default. This function calls the external @code{metamail} program to -actually do the work. One common problem with this program is that is -thinks that it can't display 8-bit things in the Emacs buffer. To tell -it the truth, put something like the following in your -@file{.bash_profile} file. (You do use @code{bash}, don't you?) - -@example -export MM_CHARSET="iso-8859-1" -@end example - -For more information on @code{metamail}, see its manual page. +@code{gnus-article-display-method-for-mime}, which is +@code{gnus-article-display-mime-message} by default. This function +calls the SEMI MIME-View program to actually do the work. For more +information on SEMI MIME-View, see its manual page (however it is not +existed yet, sorry). Set @code{gnus-show-mime} to @code{t} if you want to use @sc{mime} all the time. However, if @code{gnus-strict-mime} is @@ -7902,18 +7897,24 @@ non-@code{nil}, the @sc{mime} method will only be used if there are set, then you'll see some unfortunate display glitches in the article buffer. These can't be avoided. -It might be best to just use the toggling functions from the summary -buffer to avoid getting nasty surprises. (For instance, you enter the -group @samp{alt.sing-a-long} and, before you know it, @sc{mime} has -decoded the sound file in the article and some horrible sing-a-long song -comes screaming out your speakers, and you can't find the volume -button, because there isn't one, and people are starting to look at you, -and you try to stop the program, but you can't, and you can't find the -program to control the volume, and everybody else in the room suddenly -decides to look at you disdainfully, and you'll feel rather stupid.) +In GNUS or Gnus, it might be best to just use the toggling functions +from the summary buffer to avoid getting nasty surprises. (For instance, +you enter the group @samp{alt.sing-a-long} and, before you know it, +@sc{mime} has decoded the sound file in the article and some horrible +sing-a-long song comes screaming out your speakers, and you can't find +the volume button, because there isn't one, and people are starting to +look at you, and you try to stop the program, but you can't, and you +can't find the program to control the volume, and everybody else in the +room suddenly decides to look at you disdainfully, and you'll feel +rather stupid.) Any similarity to real events and people is purely coincidental. Ahem. +To avoid such kind of situation, gnus stops to use +@code{metamail-buffer}. So now, you can set @code{gnus-show-mime} to +non-@code{nil} every-time, then you can push button in the article +buffer when there are nobody else. + @node Customizing Articles @section Customizing Articles @@ -8084,14 +8085,14 @@ where you can edit the article all you like, before you send the article by pressing @kbd{C-c C-c}. @xref{Top, , Top, message, The Message Manual}. If you are in a foreign news group, and you wish to post the article using the foreign server, you can give a prefix to @kbd{C-c C-c} -to make Gnus try to post using the foreign server. +to make gnus try to post using the foreign server. @menu * Mail:: Mailing and replying. * Post:: Posting and following up. * Posting Server:: What server should you post via? * Mail and Post:: Mailing and posting at the same time. -* Archived Messages:: Where Gnus stores the messages you've sent. +* Archived Messages:: Where gnus stores the messages you've sent. * Posting Styles:: An easier way to specify who you are. * Drafts:: Postponing messages and rejected messages. * Rejected Articles:: What happens if the server doesn't like your article? @@ -8134,7 +8135,7 @@ user whether to re-send the mail. (This is primarily useful when dealing with @sc{soup} packets and the like where one is apt to send the same packet multiple times.) This variable says what the name of this history file is. It is @file{~/News/Sent-Message-IDs} by default. Set -this variable to @code{nil} if you don't want Gnus to keep a history +this variable to @code{nil} if you don't want gnus to keep a history file. @item gnus-sent-message-ids-length @@ -8155,7 +8156,7 @@ Thank you for asking. I hate you. @vindex gnus-post-method -It can be quite complicated. Normally, Gnus will use the same native +It can be quite complicated. Normally, gnus will use the same native server. However. If your native server doesn't allow posting, just reading, you probably want to use some other server to post your (extremely intelligent and fabulously interesting) articles. You can @@ -8171,10 +8172,10 @@ can use a non-zero prefix to the @kbd{C-c C-c} command to force using the ``current'' server for posting. If you give a zero prefix (i.e., @kbd{C-u 0 C-c C-c}) to that command, -Gnus will prompt you for what method to use for posting. +gnus will prompt you for what method to use for posting. You can also set @code{gnus-post-method} to a list of select methods. -If that's the case, Gnus will always prompt you for what method to use +If that's the case, gnus will always prompt you for what method to use for posting. Finally, if you want to always post using the same select method as @@ -8229,7 +8230,7 @@ store the messages. If you want to disable this completely, the is the default. @vindex gnus-message-archive-method -@code{gnus-message-archive-method} says what virtual server Gnus is to +@code{gnus-message-archive-method} says what virtual server gnus is to use to store sent messages. The default is: @lisp @@ -8318,7 +8319,7 @@ Now, when you send a message off, it will be stored in the appropriate group. (If you want to disable storing for just one particular message, you can just remove the @code{Gcc} header that has been inserted.) The archive group will appear in the group buffer the next time you start -Gnus, or the next time you press @kbd{F} in the group buffer. You can +gnus, or the next time you press @kbd{F} in the group buffer. You can enter it and read the articles in it just like you'd read any other group. If the group gets really big and annoying, you can simply rename if (using @kbd{G r} in the group buffer) to something @@ -8450,7 +8451,7 @@ the message you are writing so that you can continue editing it some other day, and send it when you feel its finished. Well, don't worry about it. Whenever you start composing a message of -some sort using the Gnus mail and post commands, the buffer you get will +some sort using the gnus mail and post commands, the buffer you get will automatically associate to an article in a special @dfn{draft} group. If you save the buffer the normal way (@kbd{C-x C-s}, for instance), the article will be saved there. (Auto-save files also go to the draft @@ -8520,10 +8521,10 @@ doesn't like your face. Perhaps it just feels miserable. Perhaps @emph{there be demons}. Perhaps you have included too much cited text. Perhaps the disk is full. Perhaps the server is down. -These situations are, of course, totally beyond the control of Gnus. +These situations are, of course, totally beyond the control of gnus. (Gnus, of course, loves the way you look, always feels great, has angels fluttering around inside of it, doesn't care about how much cited text -you include, never runs full and never goes down.) So Gnus saves these +you include, never runs full and never goes down.) So gnus saves these articles until some later time when the server feels better. The rejected articles will automatically be put in a special draft group @@ -10421,7 +10422,6 @@ your @file{.emacs} file: @end table - @findex nnfolder-generate-active-file @kindex M-x nnfolder-generate-active-file If you have lots of @code{nnfolder}-like files you'd like to read with @@ -11071,7 +11071,7 @@ group as read. If the search engine changes its output substantially, @code{nnweb} won't be able to parse it and will fail. One could hardly fault the Web -providers if they were to do this---their @emph{raison d'être} is to +providers if they were to do this---their @emph{raison d',Aj(Btre} is to make money off of advertisements, not to provide services to the community. Since @code{nnweb} washes the ads off all the articles, one might think that the providers might be somewhat miffed. We'll see. @@ -11736,7 +11736,7 @@ Fetch all eligible articles in all groups @kindex J S (Agent Group) @findex gnus-group-send-drafts Send all sendable messages in the draft group -(@code{gnus-agent-fetch-session}). @xref{Drafts} +(@code{gnus-agent-send-draft}). @xref{Drafts} @item J a @kindex J a (Agent Group) @@ -12108,7 +12108,7 @@ Score on the body. Score on the head. @item t -Score on thead. +Score on thread. @end table @@ -13495,7 +13495,7 @@ then this operator will return @code{false}. @item ! @itemx not -@itemx ¬ +@itemx ,A,(B This logical operator only takes a single argument. It returns the logical negation of the value of its argument. @@ -15350,7 +15350,7 @@ Most Gnus storage path variables will be initialized from this variable, which defaults to the @samp{SAVEDIR} environment variable, or @file{~/News/} if that variable isn't set. -Note that Gnus is mostly loaded when the @file{.gnus.el} file is read. +Note that gnus is mostly loaded when the @file{.gnus.el} file is read. This means that other directory variables that are initialized from this variable won't be set properly if you set this variable in @file{.gnus.el}. Set this variable in @file{.emacs} instead. @@ -15786,7 +15786,7 @@ David Moore---rewrite of @file{nnvirtual.el} and many other things. Kevin Davidson---came up with the name @dfn{ding}, so blame him. @item -François Pinard---many, many interesting and thorough bug reports, as +Fran,Ag(Bois Pinard---many, many interesting and thorough bug reports, as well as autoconf support. @end itemize @@ -15799,7 +15799,7 @@ The following people have contributed many patches and suggestions: Christopher Davis, Andrew Eskilsson, Kai Grossjohann, -David Kågedal, +David K,Ae(Bgedal, Richard Pieri, Fabrice Popineau, Daniel Quinlan, @@ -15870,7 +15870,7 @@ Marc Horowitz, Gunnar Horrigmo, Richard Hoskins, Brad Howes, -François Felix Ingrand, +Fran,Ag(Bois Felix Ingrand, Ishikawa Ichiro, @c Ishikawa Lee Iverson, Iwamuro Motonori, @c Iwamuro @@ -17295,8 +17295,8 @@ From: Jason L Tibbitts III @end example @item - tanken var at når du bruker `gnus-startup-file' som prefix (FOO) til å lete -opp en fil FOO-SERVER, FOO-SERVER.el, FOO-SERVER.eld, kan du la den være en + tanken var at n,Ae(Br du bruker `gnus-startup-file' som prefix (FOO) til ilete +opp en fil FOO-SERVER, FOO-SERVER.el, FOO-SERVER.eld, kan du la den v,Af(Bre en liste hvor du bruker hvert element i listen som FOO, istedet. da kunne man hatt forskjellige serveres startup-filer forskjellige steder. @@ -17369,8 +17369,8 @@ there was a sci.somethingelse group or section, then it should prompt for sci? first the sci.something? then sci.somethingelse?... @item -Ja, det burde være en måte å si slikt. Kanskje en ny variabel? -`gnus-use-few-score-files'? Så kunne score-regler legges til den +Ja, det burde v,Af(Bre en m,Ae(Bte ,Ae(B si slikt. Kanskje en ny variabel? +`gnus-use-few-score-files'? S,Ae(B kunne score-regler legges til den "mest" lokale score-fila. F. eks. ville no-gruppene betjenes av "no.all.SCORE", osv. @@ -17700,7 +17700,7 @@ the current process mark set onto the stack. @item gnus-article-hide-pgp -Selv ville jeg nok ha valgt å slette den dersom teksten matcher +Selv ville jeg nok ha valgt islette den dersom teksten matcher @example "\\(This\s+\\)?[^ ]+ has been automatically signed by" @end example @@ -17825,7 +17825,7 @@ file, for instance. @item With dummy roots, `^' and then selecing the first article -in any other dummy thread will make Gnus highlight the +in any other dummy thread will make gnus highlight the dummy root instead of the first article. @item diff --git a/texi/message-ja.texi b/texi/message-ja.texi index 7cf6523..3a152d3 100644 --- a/texi/message-ja.texi +++ b/texi/message-ja.texi @@ -1,7 +1,7 @@ \input texinfo @c -*-texinfo-*- @setfilename message-ja -@settitle Message 5.6.45 Manual +@settitle Message 5.6.33 Manual @synindex fn cp @synindex vr cp @synindex pg cp @@ -60,7 +60,7 @@ into another language, under the above conditions for modified versions. @tex @titlepage -@title Message 5.6.45 Manual +@title Message 5.6.22 Manual @author by Lars Magne Ingebrigtsen @translated by members of Semi-gnus mailing-list @@ -112,7 +112,7 @@ Gnus $B$NA4$F$N%a%C%;!<%8$N:n@.(B ($B%a!<%k$H%K%e!<%9$NN>J}(B) $B$O%a%C%;!< * Key Index:: $B%a%C%;!<%8%b!<%I%-!<$N0lMw!#(B @end menu -$B$3$N%^%K%e%"%k$O(B Message 5.6.45 $B$KBP1~$7$^$9!#(BMessage $B$O$3$N%^%K%e%"%k$H(B +$B$3$N%^%K%e%"%k$O(B Message 5.6.22 $B$KBP1~$7$^$9!#(BMessage $B$O$3$N%^%K%e%"%k$H(B $BF1$8HGHV9f$N(B Gnus $B$NG[I[$H6&$KG[I[$5$l$^$9!#(B