[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
You can change the format of the lines in the summary buffer by changing
the gnus-summary-line-format
variable. It works along the same
lines as a normal format
string, with some extensions
(see section 8.4 Formatting Variables).
There should always be a colon or a point position marker on the line;
the cursor always moves to the point position marker or the colon after
performing an operation. (Of course, Gnus wouldn't be Gnus if it wasn't
possible to change this. Just write a new function
gnus-goto-colon
which does whatever you like with the cursor.)
See section 8.4.6 Positioning Point.
The default string is `%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n'.
The following format specification characters and extended format specification(s) are understood:
gnus-list-identifies
. See section 3.17.3 Article Hiding.
gnus-summary-same-subject
otherwise.
(gnus-summary-same-subject
defaults to ""
.)
From
header.
From
header).
To
header or the Newsgroups
header (see section 3.1.2 To From Newsgroups).
From
header). This differs from the n
spec in that it uses the function designated by the
gnus-extract-address-components
variable, which is slower, but
may be more thorough.
From
header). This works the same way as
the a
spec.
> +-> | +-> | | \-> | | \-> | \-> +-> \-> |
You can customize the appearance with the following options. Note that it is possible to make the thread display look really neat by replacing the default ASCII characters with graphic line-drawing glyphs.
gnus-sum-thread-tree-root
nil
, use subject
instead. The default is `> '.
gnus-sum-thread-tree-false-root
nil
, use subject instead. The default is `> '.
gnus-sum-thread-tree-single-indent
nil
, use subject
instead. The default is `'.
gnus-sum-thread-tree-vertical
gnus-sum-thread-tree-indent
gnus-sum-thread-tree-leaf-with-other
gnus-sum-thread-tree-single-leaf
gnus-summary-default-score
and the score is less than
gnus-summary-zcore-fuzz
, this spec will not be used.
Xref
.
Date
.
Date
in DD-MMM
format.
Date
in YYYYMMDDT
HHMMSS format.
Message-ID
.
References
.
gnus-not-empty-thread-mark
) will be displayed if the
article has any children.
gnus-user-date-format-alist
.
gnus-user-format-function-x
, where x is the letter
following `%u'. The function will be passed the current header as
argument. The function should return a string, which will be inserted
into the summary just like information from any other summary specifier.
Text between `%(' and `%)' will be highlighted with
gnus-mouse-face
when the mouse point is placed inside the area.
There can only be one such area.
The `%U' (status), `%R' (replied) and `%z' (zcore) specs have to be handled with care. For reasons of efficiency, Gnus will compute what column these characters will end up in, and "hard-code" that. This means that it is invalid to have these specs after a variable-length spec. Well, you might not be arrested, but your summary buffer will look strange, which is bad enough.
The smart choice is to have these specs as far to the left as possible. (Isn't that the case with everything, though? But I digress.)
This restriction may disappear in later versions of Gnus.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |