diff options
author | Gnus developers <ding@gnus.org> | 2010-10-08 23:55:33 +0000 |
---|---|---|
committer | Katsumi Yamaoka <yamaoka@jpl.org> | 2010-10-08 23:55:33 +0000 |
commit | 36d3245fbc0ad82c81da146e0fa21bd6843f2795 (patch) | |
tree | 0409ed734487810378991a18c4d49a3c1a327a7d /doc | |
parent | 2187e5bba7722193286a75c43a91bf1a22d9300b (diff) | |
download | emacs-36d3245fbc0ad82c81da146e0fa21bd6843f2795.tar.gz |
shr.el (shr-insert): Don't insert double spaces.
auth.texi (Help for users, GnuPG and EasyPG Assistant Configuration): Update docs.
gnus-registry.el, nnregistry.el: Remove nnregistry refer method auto-install and update docs.
gnus.texi (Finding the Parent, The Gnus Registry, Registry Article Refer Method): Update docs for nnregistry.el.
gnus-demon.el, gnus-group.el, gnus-msg.el, gnus-sum.el, gnus-util.el, gnus.el: Rename `gnus-pull' to `gnus-alist-pull'.
gnus.texi (Article Washing): Add mm-shr.
mm-decode.el (mm-text-html-renderer): Add mm-shr in choice list.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/misc/ChangeLog | 14 | ||||
-rw-r--r-- | doc/misc/auth.texi | 61 | ||||
-rw-r--r-- | doc/misc/gnus.texi | 57 |
3 files changed, 119 insertions, 13 deletions
diff --git a/doc/misc/ChangeLog b/doc/misc/ChangeLog index b06cfe1394b..aa1715551c8 100644 --- a/doc/misc/ChangeLog +++ b/doc/misc/ChangeLog @@ -1,3 +1,17 @@ +2010-10-08 Julien Danjou <julien@danjou.info> + + * gnus.texi: add mm-shr + +2010-10-08 Ludovic Courtès <ludo@gnu.org> + + * gnus.texi (Finding the Parent, The Gnus Registry) + (Registry Article Refer Method): Update docs for nnregistry.el. + +2010-10-08 Daiki Ueno <ueno@unixuser.org> + + * auth.texi (Help for users) + (GnuPG and EasyPG Assistant Configuration): Update docs. + 2010-10-08 Glenn Morris <rgm@gnu.org> * cl.texi (Organization, Installation, Old CL Compatibility): diff --git a/doc/misc/auth.texi b/doc/misc/auth.texi index ed04d98ef92..f7ee7b9f3de 100644 --- a/doc/misc/auth.texi +++ b/doc/misc/auth.texi @@ -59,6 +59,7 @@ It is a way for multiple applications to share a single configuration * Help for users:: * Secret Service API:: * Help for developers:: +* GnuPG and EasyPG Assistant Configuration:: * Index:: * Function Index:: * Variable Index:: @@ -176,16 +177,8 @@ for details. If you don't customize @code{auth-sources}, you'll have to live with the defaults: any host and any port are looked up in the netrc -file @code{~/.authinfo.gpg}. This is an encrypted file if and only if -you set up EPA, which is strongly recommended. - -@lisp -(require 'epa-file) -(epa-file-enable) -;;; VERY important if you want symmetric encryption -;;; irrelevant if you don't -(setq epa-file-cache-passphrase-for-symmetric-encryption t) -@end lisp +file @code{~/.authinfo.gpg}, which is a GnuPG encrypted file. +@xref{GnuPG and EasyPG Assistant Configuration}. The simplest working netrc line example is one without a port. @@ -271,6 +264,54 @@ users' netrc files. @end defun +@node GnuPG and EasyPG Assistant Configuration +@appendix GnuPG and EasyPG Assistant Configuration + +In Emacs 23 or later there is an option @code{auto-encryption-mode} to +automatically decrypt @code{*.gpg} files and it is enabled by default +so there is no setting is needed. If you are using earlier versions +of Emacs for some reason, you will need: + +@lisp +(require 'epa-file) +(epa-file-enable) +@end lisp + +If you want your GnuPG passwords to be cached, setup @code{gpg-agent} +or EasyPG Assitant +@pxref{Caching Passphrases, , Caching Passphrases, epa} + +For those who are using older vesions of Emacs, here are some portion +copied from the EasyPG Assitant manual: + +Here are some questions: + +@enumerate +@item Do you use GnuPG version 2 instead of GnuPG version 1? +@item Do you use symmetric encryption rather than public key encryption? +@item Do you want to use gpg-agent? +@end enumerate + +Here are configurations depending on your answers: + +@multitable {111} {222} {333} {configuration configuration configuration} +@item @b{1} @tab @b{2} @tab @b{3} @tab Configuration +@item Yes @tab Yes @tab Yes @tab Nothing to do. +@item Yes @tab Yes @tab No @tab You can't, without gpg-agent. +@item Yes @tab No @tab Yes @tab Nothing to do. +@item Yes @tab No @tab No @tab You can't, without gpg-agent. +@item No @tab Yes @tab Yes @tab Set up elisp passphrase cache. +@item No @tab Yes @tab No @tab Set up elisp passphrase cache. +@item No @tab No @tab Yes @tab Nothing to do. +@item No @tab No @tab No @tab You can't, without gpg-agent. +@end multitable + +To setup gpg-agent, follow the instruction in GnuPG manual. +@pxref{Invoking GPG-AGENT, , Invoking GPG-AGENT, gnupg}. + +To set up elisp passphrase cache, set +@code{epa-file-cache-passphrase-for-symmetric-encryption}. + @node Index @chapter Index @printindex cp diff --git a/doc/misc/gnus.texi b/doc/misc/gnus.texi index 1f78e8c563f..74db0e3d620 100644 --- a/doc/misc/gnus.texi +++ b/doc/misc/gnus.texi @@ -9812,6 +9812,10 @@ Customization, emacs-mime, The Emacs MIME Manual}) to convert the can use include: @table @code +@item mm-shr +Use Gnus simple html renderer. + +@table @code @item gnus-article-html Use Gnus rendered based on w3m. @@ -10989,9 +10993,12 @@ do not do a particularly excellent job at it. That is, @code{nnmbox}, @code{nnbabyl}, @code{nnmaildir}, @code{nnml}, are able to locate articles from any groups, while @code{nnfolder}, and @code{nnimap} are only able to locate articles that have been posted to the current -group. (Anything else would be too time consuming.) @code{nnmh} does -not support this at all. +group. @code{nnmh} does not support this at all. +Fortunately, the special @code{nnregistry} back end is able to locate +articles in any groups, regardless of their back end (@pxref{Registry +Article Refer Method, fetching by @code{Message-ID} using the +registry}). @node Alternative Approaches @section Alternative Approaches @@ -12452,7 +12459,7 @@ section only describes the default method. @item mm-text-html-renderer @vindex mm-text-html-renderer If set to @code{gnus-article-html}, Gnus will use the built-in method, -that's based on @code{curl} and @code{w3m}. +that's based on @code{w3m}. @item gnus-blocked-images @vindex gnus-blocked-images @@ -25374,6 +25381,13 @@ the sender in addition to the Message-ID. Several strategies are available. @item +Refer to messages by ID + +Commands like @code{gnus-summary-refer-parent-article} can take +advantage of the registry to jump to the referred article, regardless +of the group the message is in. + +@item Store custom flags and keywords The registry can store custom flags and keywords for a message. For @@ -25392,6 +25406,7 @@ of all messages matching a particular set of criteria. @menu * Setup:: * Fancy splitting to parent:: +* Registry Article Refer Method:: * Store custom flags and keywords:: * Store arbitrary data:: @end menu @@ -25468,6 +25483,42 @@ registry will keep. The file where the registry will be stored between Gnus sessions. @end defvar +@node Registry Article Refer Method +@subsection Fetching by @code{Message-ID} Using the Registry + +The registry knows how to map each @code{Message-ID} to the group it's +in. This can be leveraged to enhance the ``article refer method'', +the thing that tells Gnus how to look up an article given its +Message-ID (@pxref{Finding the Parent}). + +@vindex nnregistry +@vindex gnus-refer-article-method + +The @code{nnregistry} refer method does exactly that. It has the +advantage that an article may be found regardless of the group it's +in---provided its @code{Message-ID} is known to the registry. It can +be enabled by augmenting the start-up file with something along these +lines: + +@example +;; Keep enough entries to have a good hit rate when referring to an +;; article using the registry. Use long group names so that Gnus +;; knows where the article is. +(setq gnus-registry-max-entries 2500 + gnus-registry-use-long-group-names t) + +(gnus-registry-initialize) + +(setq gnus-refer-article-method + '(current + (nnregistry) + (nnweb "gmane" (nnweb-type gmane)))) +@end example + +The example above instructs Gnus to first look up the article in the +current group, or, alternatively, using the registry, and finally, if +all else fails, using Gmane. + @node Fancy splitting to parent @subsection Fancy splitting to parent |