X-Git-Url: https://code.delx.au/gnu-emacs/blobdiff_plain/3a8b7013042adae3c27327a75662fd8e884d4896..7f55d4251806e4712762bef0a3ed41a53f850a58:/doc/misc/gnus.texi diff --git a/doc/misc/gnus.texi b/doc/misc/gnus.texi index cb808743ec..ed4d1a58f7 100644 --- a/doc/misc/gnus.texi +++ b/doc/misc/gnus.texi @@ -11482,7 +11482,7 @@ who wrote the article, the date it was written and the subject of the article. That's well and nice, but there's also lots of information most people do not want to see---what systems the article has passed through before reaching you, the @code{Message-ID}, the -@code{References}, etc. ad nauseam---and you'll probably want to get rid +@code{References}, etc.@: ad nauseam---and you'll probably want to get rid of some of those lines. If you want to keep all those lines in the article buffer, you can set @code{gnus-show-all-headers} to @code{t}. @@ -14182,6 +14182,7 @@ from different locations, or with different user agents. * Connecting to an IMAP Server:: Getting started with @acronym{IMAP}. * Customizing the IMAP Connection:: Variables for @acronym{IMAP} connection. * Client-Side IMAP Splitting:: Put mail in the correct mail box. +* Support for IMAP Extensions:: Getting extensions and labels from servers. @end menu @@ -14328,6 +14329,29 @@ Here's a complete example @code{nnimap} backend with a client-side @end example +@node Support for IMAP Extensions +@subsection Support for IMAP Extensions + +@cindex Gmail +@cindex X-GM-LABELS +@cindex IMAP labels + +If you're using Google's Gmail, you may want to see your Gmail labels +when reading your mail. Gnus can give you this information if you ask +for @samp{X-GM-LABELS} in the variable @code{gnus-extra-headers}. For +example: + +@example +(setq gnus-extra-headers + '(To Newsgroups X-GM-LABELS)) +@end example + +This will result in Gnus storing your labels in message header +structures for later use. The content is always a parenthesized +(possible empty) list. + + + @node Getting Mail @section Getting Mail @cindex reading mail @@ -25881,7 +25905,7 @@ Store custom flags and keywords The registry can store custom flags and keywords for a message. For instance, you can mark a message ``To-Do'' this way and the flag will persist whether the message is in the nnimap, nnml, nnmaildir, -etc. backends. +etc.@: backends. @item Store arbitrary data @@ -25964,7 +25988,7 @@ registry will be pruned back to less than @code{gnus-registry-max-entries}. This option controls exactly how much less: the target is calculated as the maximum number of entries minus the maximum number times this factor. The default is 0.1: -i.e. if your registry is limited to 50000 entries, pruning will try to +i.e., if your registry is limited to 50000 entries, pruning will try to cut back to 45000 entries. Entries with keys marked as precious will not be pruned. @end defvar