From: Michael Heerdegen <michael_heerdegen@web.de>
To: ding@lists.math.uh.edu
Subject: Re: GCC field with `mail-user-agent' set to 'gnus-user-agent
Date: Fri, 10 Feb 2012 21:40:01 +0100 [thread overview]
Message-ID: <87d39mifry.fsf@web.de> (raw)
In-Reply-To: <87zkcr39eq.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 09 Feb 2012 23:54:21 +0100")
> > How about making `gnus-user-agent' run `message-user-agent' when
> > Gnus is not alive?
>
> That's a good idea. I've now done this.
I must say that I'm skeptical about this solution. I'm new to the Gnus
interna, so maybe I'm missing the point.
But, seemingly, we don't win much comfort with this solution. More
important, the situation we have is distracting. The user might think
(like I did) that he gains functionality from Gnus we he sets
mail-user-agent to 'gnus-user-agent. I, as a user, would not expect
that this only works if I'm already in Gnus.
Just an opinion, of course. For users which have always a running Gnus
in their Emacs session, your solution makes sense. For users who only
start Gnus and then quit it after reading, IMO it doesn't.
If you keep the current solution, please try to make the docs a bit
clearer, where appropriate. E.g. the docstring of `mail-user-agent':
Valid values include:
[...]
`gnus-user-agent' -- like `message-user-agent', but with Gnus
paraphernalia, particularly the Gcc: header for
archiving.
should then tell the user that he gets the paraphernalia only if Gnus is
running.
Michael.
next prev parent reply other threads:[~2012-02-10 20:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 3:30 Michael Heerdegen
2012-02-09 5:48 ` Lars Ingebrigtsen
2012-02-09 8:25 ` Michael Heerdegen
2012-02-09 20:31 ` Lars Ingebrigtsen
2012-02-09 22:49 ` Katsumi Yamaoka
2012-02-09 22:54 ` Lars Ingebrigtsen
2012-02-10 20:40 ` Michael Heerdegen [this message]
2012-02-11 0:50 ` Lars Ingebrigtsen
2012-02-11 1:14 ` Michael Heerdegen
2012-02-11 15:32 ` Lars Ingebrigtsen
2012-02-11 21:16 ` Michael Heerdegen
2012-02-12 20:00 ` Lars Ingebrigtsen
2012-02-13 0:57 ` Michael Heerdegen
2012-02-13 19:44 ` Lars Ingebrigtsen
2012-02-11 3:25 ` Rasmus
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=87d39mifry.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=ding@lists.math.uh.edu \
/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).