@item dummy
@vindex gnus-summary-dummy-line-format
+@vindex gnus-summary-make-false-root-always
Gnus will create a dummy summary line that will pretend to be the
parent. This dummy line does not correspond to any real article, so
selecting it will just select the first real article after the dummy
article. @code{gnus-summary-dummy-line-format} is used to specify the
format of the dummy roots. It accepts only one format spec: @samp{S},
which is the subject of the article. @xref{Formatting Variables}.
+If you want all threads to have a dummy root, even the non-gathered
+ones, set @code{gnus-summary-make-false-root-always} to t.
@item empty
Gnus won't actually make any article the parent, but simply leave the
To see e.g. security buttons but no other buttons, you could set this
variable to @code{("multipart/signed")} and leave
-@code{gnus-unbuttonized-mime-types} to the default value.
+@code{gnus-unbuttonized-mime-types} at the default value.
+
+@item gnus-inhibit-mime-unbuttonizing
+@vindex gnus-inhibit-mime-unbuttonizing
+If this is non-nil, then all @sc{mime} parts get buttons. The default
+value is @code{nil}.
@item gnus-article-mime-part-function
@vindex gnus-article-mime-part-function
@item gnus-uu-digest-headers
@vindex gnus-uu-digest-headers
List of regexps to match headers included in digested messages. The
-headers will be included in the sequence they are matched.
+headers will be included in the sequence they are matched. If
+@code{nil} include all headers.
@item gnus-add-to-list
@vindex gnus-add-to-list
string, then Gnus will try to regexp match it against the group name.
If it is the form @code{(header MATCH REGEXP)}, then Gnus will look in
the original article for a header whose name is MATCH and compare that
-REGEXP. MATCH and REGEXP are strings. If it's a function symbol, that
-function will be called with no arguments. If it's a variable symbol,
-then the variable will be referenced. If it's a list, then that list
-will be @code{eval}ed. In any case, if this returns a non-@code{nil}
-value, then the style is said to @dfn{match}.
+REGEXP. MATCH and REGEXP are strings. (There original article is the
+one you are replying or following up to. If you are not composing a
+reply or a followup, then there is nothing to match against.) If the
+@code{match} is a function symbol, that function will be called with no
+arguments. If it's a variable symbol, then the variable will be
+referenced. If it's a list, then that list will be @code{eval}ed. In
+any case, if this returns a non-@code{nil} value, then the style is said
+to @dfn{match}.
Each style may contain an arbitrary amount of @dfn{attributes}. Each
attribute consists of a @code{(@var{name} @var{value})} pair. The
@kindex S x
@kindex M s x
@findex gnus-summary-mark-as-spam
-(@code{gnus-summary-mark-as-spam})
+@code{gnus-summary-mark-as-spam}.
Mark current article as spam, showing it with the @samp{H} mark.
Whenever you see a spam article, make sure to mark its summary line
@kindex M s t
@kindex S t
@findex spam-bogofilter-score
-(@code{spam-bogofilter-score}
+@code{spam-bogofilter-score}.
You must have bogofilter processing enabled for that command to work
properly.
also useful for the article numbers to start at 1 to avoid running out
of numbers as long as possible.
+Note that by convention, backends are named @code{nnsomething}, but
+Gnus also comes with some @code{nnnotbackends}, such as
+@file{nnheader.el}, @file{nnmail.el} and @file{nnoo.el}.
+
In the examples and definitions I will refer to the imaginary back end
@code{nnchoke}.
alterations. This comes in handy if the back end really carries all the
information (as is the case with virtual and imap groups). This
function should destructively alter the info to suit its needs, and
-should return the (altered) group info.
+should return a non-nil value.
There should be no result data from this function.
projects / elisp / gnus.git- / blobdiff