From: yamaoka Date: Fri, 14 Oct 2005 12:20:27 +0000 (+0000) Subject: Synch to No Gnus 200510141220. X-Git-Tag: t-gnus-6_17_4-quimby-~301 X-Git-Url: http://git.chise.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7000383a53ecfcc84c02aa295d8fbf0341f0dcf9;p=elisp%2Fgnus.git- Synch to No Gnus 200510141220. --- diff --git a/texi/ChangeLog b/texi/ChangeLog index bf6047e..3ac542f 100644 --- a/texi/ChangeLog +++ b/texi/ChangeLog @@ -1,3 +1,7 @@ +2005-10-14 Katsumi Yamaoka + + * gnus.texi (Document Server Internals): Addition. + 2005-10-13 Katsumi Yamaoka * gnus.texi (A note on namespaces): Fix RFC reference. diff --git a/texi/gnus.texi b/texi/gnus.texi index b14b871..2369db7 100644 --- a/texi/gnus.texi +++ b/texi/gnus.texi @@ -17093,34 +17093,48 @@ totally ignored. @item article-begin This setting has to be present in all document type definitions. It -says what the beginning of each article looks like. +says what the beginning of each article looks like. To do more +complicated things that cannot be dealt with a simple regexp, you can +use @code{article-begin-function} instead of this. -@item head-begin-function -If present, this should be a function that moves point to the head of -the article. +@item article-begin-function +If present, this should be a function that moves point to the beginning +of each article. This setting overrides @code{article-begin}. -@item nndoc-head-begin +@item head-begin If present, this should be a regexp that matches the head of the -article. +article. To do more complicated things that cannot be dealt with a +simple regexp, you can use @code{head-begin-function} instead of this. -@item nndoc-head-end +@item head-begin-function +If present, this should be a function that moves point to the head of +the article. This setting overrides @code{head-begin}. + +@item head-end This should match the end of the head of the article. It defaults to @samp{^$}---the empty line. +@item body-begin +This should match the beginning of the body of the article. It defaults +to @samp{^\n}. To do more complicated things that cannot be dealt with +a simple regexp, you can use @code{body-begin-function} instead of this. + @item body-begin-function If present, this function should move point to the beginning of the body -of the article. +of the article. This setting overrides @code{body-begin}. -@item body-begin -This should match the beginning of the body of the article. It defaults -to @samp{^\n}. +@item body-end +If present, this should match the end of the body of the article. To do +more complicated things that cannot be dealt with a simple regexp, you +can use @code{body-end-function} instead of this. @item body-end-function If present, this function should move point to the end of the body of -the article. +the article. This setting overrides @code{body-end}. -@item body-end -If present, this should match the end of the body of the article. +@item file-begin +If present, this should match the beginning of the file. All text +before this regexp will be totally ignored. @item file-end If present, this should match the end of the file. All text after this @@ -17151,6 +17165,19 @@ understand. It is called with the article number as a parameter, and is expected to generate a nice head for the article in question. It is called when requesting the headers of all articles. +@item generate-article-function +If present, this function is called to generate an entire article that +Gnus can understand. It is called with the article number as a +parameter when requesting all articles. + +@item dissection-function +If present, this function is called to dissect a document by itself, +overriding @code{first-article}, @code{article-begin}, +@code{article-begin-function}, @code{head-begin}, +@code{head-begin-function}, @code{head-end}, @code{body-begin}, +@code{body-begin-function}, @code{body-end}, @code{body-end-function}, +@code{file-begin}, and @code{file-end}. + @end table Let's look at the most complicated example I can come up with---standard