From b53d52ca26581bc70fa02da4bc243678e4a44daa Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Thu, 21 Feb 2013 04:56:19 +0000 Subject: [PATCH] gnus-faq.texi, gnus.texi: Port documentation to Texinfo 5.0 --- texi/gnus-faq.texi | 8 ++++---- texi/gnus.texi | 12 +++++++++++- 2 files changed, 15 insertions(+), 5 deletions(-) diff --git a/texi/gnus-faq.texi b/texi/gnus-faq.texi index e73677300..ede957a5c 100644 --- a/texi/gnus-faq.texi +++ b/texi/gnus-faq.texi @@ -3,8 +3,8 @@ @c %**start of header @c Copyright (C) 1995, 2001-2013 Free Software Foundation, Inc. @c -@setfilename gnus-faq.info -@settitle Frequently Asked Questions +@c @setfilename gnus-faq.info +@c @settitle Frequently Asked Questions @c %**end of header @c @@ -41,7 +41,7 @@ Please submit features and suggestions to the @email{ding@@gnus.org, ding list}. @node FAQ - Changes -@subheading Changes +@subsection Changes @@ -57,7 +57,7 @@ reference to discontinued service. @end itemize @node FAQ - Introduction -@subheading Introduction +@subsection Introduction This is the Gnus Frequently Asked Questions list. diff --git a/texi/gnus.texi b/texi/gnus.texi index c563fe045..41b33f8a7 100644 --- a/texi/gnus.texi +++ b/texi/gnus.texi @@ -14542,6 +14542,7 @@ maildir, for instance. @menu * Mail Source Specifiers:: How to specify what a mail source is. +* Mail Source Functions:: * Mail Source Customization:: Some variables that influence things. * Fetching Mail:: Using the mail source specifiers. @end menu @@ -15001,6 +15002,7 @@ useful when you use local mail and news. @end table @end table +@node Mail Source Functions @subsubsection Function Interface Some of the above keywords specify a Lisp function to be executed. @@ -16069,6 +16071,10 @@ Spool}). * Mail Spool:: Store your mail in a private spool? * MH Spool:: An mhspool-like back end. * Maildir:: Another one-file-per-message format. +* nnmaildir Group Parameters:: +* Article Identification:: +* NOV Data:: +* Article Marks:: * Mail Folders:: Having one file for each group. * Comparing Mail Back Ends:: An in-depth looks at pros and cons. @end menu @@ -16376,6 +16382,7 @@ different in the future. If your split rules create new groups, remember to supply a @code{create-directory} server parameter. @end table +@node nnmaildir Group Parameters @subsubsection Group parameters @code{nnmaildir} uses several group parameters. It's safe to ignore @@ -16486,6 +16493,7 @@ that are either marked with @code{tick} or not marked with @code{read}, plus a little extra. @end table +@node Article Identification @subsubsection Article identification Articles are stored in the @file{cur/} subdirectory of each maildir. Each article file is named like @code{uniq:info}, where @code{uniq} @@ -16498,6 +16506,7 @@ about the corresponding article. The full pathname of an article is available in the variable @code{nnmaildir-article-file-name} after you request the article in the summary buffer. +@node NOV Data @subsubsection NOV data An article identified by @code{uniq} has its @acronym{NOV} data (used to generate lines in the summary buffer) stored in @@ -16511,6 +16520,7 @@ file, but @emph{beware}: this will also cause @code{nnmaildir} to assign a new article number for this article, which may cause trouble with @code{seen} marks, the Agent, and the cache. +@node Article Marks @subsubsection Article marks An article identified by @code{uniq} is considered to have the mark @code{flag} when the file @file{.nnmaildir/marks/flag/uniq} exists. @@ -25851,8 +25861,8 @@ of all messages matching a particular set of criteria. @menu * Gnus Registry Setup:: -* Fancy splitting to parent:: * Registry Article Refer Method:: +* Fancy splitting to parent:: * Store custom flags and keywords:: * Store arbitrary data:: @end menu -- 2.25.1