From: Thorsten Jolitz <tjolitz@googlemail.com>
To: info-gnus-english@gnu.org
Subject: Re: '=> gmane.emacs.help' as sender?
Date: Thu, 03 May 2012 14:28:16 +0200 [thread overview]
Message-ID: <87y5p9fnz3.fsf@googlemail.com> (raw)
In-Reply-To: <87d36lzd97.fsf@topper.koldfront.dk>
asjo@koldfront.dk (Adam Sjøgren) writes:
> On Thu, 03 May 2012 13:39:36 +0200, Thorsten wrote:
>
>> Tassilo Horn <tassilo@member.fsf.org> writes:
>
>>> That's intended and the reason is that you probably know your own first
>>> and last name, and thus some other display is more useful for own
>>> articles.
>
>> I don't really understand why anybody would want this.
>
> When shown in a group of only emails from a single mailinglist, it
> doesn't add much, agreed. But in, say, a list of emails you have sent,
> it can be nice.
>
>> Is it only me who sees that sender string, or everybody else too?
>
> It is only you who sees it that way, in Gnus, because you know your
> name. Everybody else sees your name.
>
> I.e. in my Summary buffer I see:
>
> OA+ [ 34: Thorsten Jolitz ]
> O + [ 20: => gmane.emacs.gnus.use]
>
> While you would see something like:
>
> OA+ [ 34: => gmane.emacs.gnus.use]
> O + [ 20: Adam Sjøgren ]
>
> The point is that in my nnml+archive:news-2012 I see a list like this:
>
> O. [ 17: => gmane.emacs.gnus.gen] Re: I can haz cloud idea
> O. [ 24: => gmane.discuss ] Re: Expiring Gwene groups?
>
> Which is nicer than a long list of just [ n: Adam Sjøgren ] all
> the way down.
Ok, I begin to understand the rationale. Then it makes sense, and I
might well go back to the original configuration. I thought
everybody else would see => gmane.emacs.gnus.use too, and thus
ignore the message due to its anonimity.
>> Isn't it much more informative to associate messages with sender
>> names?
>
> Yes, but you presumably know your own name quite well, so the space is
> used for something more informative _in Gnus' display_ [only].
>
> o o o
>
> This often pops up as a question quite often, so I do begin to wonder if
> the default should be that this functionality be turned off.
I can confirm that it is very confusing for the non-initiated, but on
the other hand seems to be well thought out (once initiation
happened).
Thanks for your answer.
--
cheers,
Thorsten
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2012-05-03 12:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 10:25 Thorsten Jolitz
2012-05-03 11:04 ` Tassilo Horn
2012-05-03 11:39 ` Thorsten Jolitz
2012-05-03 11:47 ` Thorsten Jolitz
2012-05-03 11:56 ` Thorsten Jolitz
2012-05-03 11:59 ` Adam Sjøgren
2012-05-03 12:28 ` Thorsten Jolitz [this message]
2012-05-03 12:04 ` Tassilo Horn
2012-05-03 12:24 ` Thorsten Jolitz
2012-05-03 14:39 ` Tassilo Horn
2012-05-04 10:48 ` Thorsten Jolitz
2012-05-06 14:19 ` Thorsten Jolitz
2012-05-06 21:06 ` Bastien
2012-05-06 22:24 ` Thorsten Jolitz
2012-05-06 23:48 ` Bastien
2012-05-06 21:25 ` Bastien
2012-05-06 23:14 ` Thorsten Jolitz
2012-05-07 0:16 ` Bastien
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=87y5p9fnz3.fsf@googlemail.com \
--to=tjolitz@googlemail.com \
--cc=info-gnus-english@gnu.org \
/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).