From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: posting name in summary buffer
Date: Sat, 20 Jan 2007 13:33:51 +0100 [thread overview]
Message-ID: <v93b65j2s0.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87bqkuf954.fsf@fukaolx15.rish.kuins.net>
On Sat, Jan 20 2007, Gernot Hassenpflug wrote:
> I am confused and don't know what to look for. The problem is that in
> my own posts in a group I see an arrow and the name of the group in
> the summary buffer where I expect to see my own name for the post I
> made. I don't know what that field is called. In the manual it seems
> to be called "the name from the From header".
,----[ <f1> v gnus-summary-line-format RET ]
| Documentation:
| *The format specification of the lines in the summary buffer.
|
| It works along the same lines as a normal formatting string,
| with some simple extensions.
|
| %F Contents of the From: header (string)
| %f Contents of the From: or To: headers (string)
`----
Doing an index search in the manual for this variable (<f1> i d m gnus
RET i gnus-summary-line-format RET), I get:
,----[ (info "(gnus)Summary Buffer Lines") ]
| `f'
| The name, `To' header or the `Newsgroups' header (*note To From
| Newsgroups::).
`----
Maybe we should add the part about Newsgroups in the doc string as
well.
,----[ (info "(gnus)To From Newsgroups") ]
| In some groups (particularly in archive groups), the `From' header
| isn't very interesting, since all the articles there are written by
| you. To display the information in the `To' or `Newsgroups' headers
| instead, you need to decide three things: What information to gather;
| where to display it; and when to display it.
|
| 1. The reading of extra header information is controlled by the
| `gnus-extra-headers'. This is a list of header symbols. For
| instance:
|
| (setq gnus-extra-headers
| '(To Newsgroups X-Newsreader))
|
| This will result in Gnus trying to obtain these three headers, and
| storing it in header structures for later easy retrieval.
`----
So removing Newsgroups from `gnus-extra-headers' should help.
> I look in the manual, [...]
If you can give us some keyword which you tried for your search, we
could add them to the index of the manual.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-01-20 12:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-20 7:29 Gernot Hassenpflug
2007-01-20 10:46 ` Gernot Hassenpflug
2007-01-20 11:50 ` Adam Sjøgren
2007-01-20 13:54 ` Gernot Hassenpflug
2007-01-20 23:07 ` Martin Jørgensen
2007-01-21 0:11 ` Adam Sjøgren
2007-01-21 10:36 ` Martin Jørgensen
2007-01-21 11:13 ` Charles philip Chan
2007-01-21 12:47 ` Adam Sjøgren
2007-01-21 15:25 ` Springfield
2007-01-21 20:34 ` Adam Sjøgren
2007-01-23 7:59 ` Martin Jørgensen
2007-01-23 17:33 ` Adam Sjøgren
2007-01-24 14:52 ` Martin Jørgensen
2007-01-24 15:33 ` David Z Maze
2007-01-24 21:13 ` Kai Großjohann
2007-01-23 8:07 ` Martin Jørgensen
2007-01-21 0:06 ` Adam Sjøgren
2007-01-20 12:33 ` Reiner Steib [this message]
2007-01-22 4:18 ` Gernot Hassenpflug
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=v93b65j2s0.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).