From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Buttons and posting style
Date: 13 Aug 2000 18:38:48 +0200 [thread overview]
Message-ID: <m3u2cpce07.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <qwwln1h6kw5.fsf@decibel.fi.muni.cz>
Petr Konecny <pekon@informatics.muni.cz> writes:
> I buttonize headers of articles in all my groups. When I click on a
> button representing address in a header, it creates the message buffer
> for reply, but does not use the posting style of the group. In fact it
> does not even have Gcc header.
I'm not sure that's not the right thing to do. If you're responding
inside a group with the normal commands, the posting styles should be
in effect. But when clicking mail addresses, you might want the
"default" setup. I don't know...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2000-08-13 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-11 17:45 Petr Konecny
2000-08-13 16:38 ` Lars Magne Ingebrigtsen [this message]
2000-08-13 19:20 ` Kai Großjohann
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=m3u2cpce07.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).