Gnus Manual. Node: Summary Buffer Lines

prev UPSummary Buffer Format NEXTSummary Buffer Mode Line

3.1.1: Summary Buffer Lines

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 Formatting Variables).

The default string is `%U%R%z%I%(%[%4L: %-20,20n%]%) %s\n'.

The following format specification characters are understood:


Article number.

`S' Subject string.
`s' Subject if the article is the root of the thread or the previous article had a different subject, gnus-summary-same-subject otherwise. (gnus-summary-same-subject defaults to "".)
`F' Full From header.
`n' The name (from the From header).
`a' The name (from the 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.
`A' The address (from the From header). This works the same way as the a spec.
`L' Number of lines in the article.
`c' Number of characters in the article.
`I' Indentation based on thread level (see Customizing Threading).
`T' Nothing if the article is a root and lots of spaces if it isn't (it pushes everything after it off the screen).
`[' Opening bracket, which is normally `[', but can also be `<' for adopted articles (see Customizing Threading).
`]' Closing bracket, which is normally `]', but can also be `>' for adopted articles.
`>' One space for each thread level.
`<' Twenty minus thread level spaces.
`U' Unread.


This misleadingly named specifier is the secondary mark. This mark will say whether the article has been replied to, has been cached, or has been saved.


Score as a number (see Scoring).

`z' Zcore, `+' if above the default level and `-' if below the default level. If the difference between gnus-summary-default-score and the score is less than gnus-summary-zcore-fuzz, this spec will not be used.
`V' Total thread score.
`x' Xref.
`D' Date.
`d' The Date in DD-MMM format.
`o' The Date in YYYYMMDDTHHMMSS format.
`M' Message-ID.
`r' References.
`t' Number of articles in the current sub-thread. Using this spec will slow down summary buffer generation somewhat.
`e' An `=' (gnus-not-empty-thread-mark) will be displayed if the article has any children.
`P' The line number.
`O' Download mark.
`u' User defined specifier. The next character in the format string should be a letter. Gnus will call the function 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.

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.

prev UPSummary Buffer Format NEXTSummary Buffer Mode Line