From: prj@po.cwru.edu (Paul Jarc)
Cc: ding@gnus.org
Subject: Re: Two gnus-posting-styles problems
Date: Mon, 03 Jun 2002 11:04:47 -0400 [thread overview]
Message-ID: <m36610v1wa.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <sxs4rgk9zto.fsf@florida.munich.redhat.com> (Hrvoje Niksic's message of "Mon, 03 Jun 2002 16:55:31 +0200")
Hrvoje Niksic <hniksic@xemacs.org> wrote:
> 1a. Even worse, it uses the "gnus article copy" buffer even when it is
> completely unrelated to the message currently being composed.
I've seen this too.
> But that didn't work because `gnus-configure-posting-styles' is
> called from `message-mode-hook', which gets run when the Message
> buffer is still completely empty. It should be called at a later
> stage, when the buffer has already been set up.
Maybe you'd like header-action.el.
paul
next prev parent reply other threads:[~2002-06-03 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 14:55 Hrvoje Niksic
2002-06-03 15:04 ` Paul Jarc [this message]
2002-06-03 15:36 ` David S Goldberg
2002-06-03 17:40 ` Simon Josefsson
2002-06-03 17:49 ` Hrvoje Niksic
2002-06-03 18:23 ` Simon Josefsson
2002-06-03 19:48 ` Kai Großjohann
2002-06-04 13:48 ` Hrvoje Niksic
2002-06-04 16:07 ` Simon Josefsson
2002-06-03 19:45 ` 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=m36610v1wa.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=ding@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).