From: Chris Searle <chris@manamind.com>
Subject: Re: gnus-posting-styles - using header match
Date: Mon, 28 Jan 2002 13:14:39 +0100 [thread overview]
Message-ID: <xmwit9moeog.fsf@feynman.oslo.infostream.no> (raw)
In-Reply-To: <xmwzo2ypwv0.fsf@feynman.oslo.infostream.no>
>>>>> "Chris" == Chris Searle <chris@manamind.com> writes:
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
Lars> I've had a look over the code, and I can't really see
Lars> anything odd about how `header' is used as opposed to the
Lars> other rule types.
Chris> OK. I've just updated to latest cvs - and have tried to
Chris> repeat the problem. For now, it seems to be OK again :-),
Chris> but I'll keep an eye on it.
Ack - still here. But now, it's become less repeatable. I reckon I'll
just give up on that header rule :-)
I think I saw something on style setting at post time - but I can't
remember enough to find it using search - anyone recall what
function/hook it was?
Thanks again
--
Chris Searle
prev parent reply other threads:[~2002-01-28 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 15:27 Chris Searle
2002-01-19 22:40 ` Lars Magne Ingebrigtsen
2002-01-28 10:56 ` Chris Searle
2002-01-28 12:14 ` Chris Searle [this message]
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=xmwit9moeog.fsf@feynman.oslo.infostream.no \
--to=chris@manamind.com \
/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).