From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: superfluous empty lines message-headers
Date: Tue, 18 May 2004 00:05:02 +0200 [thread overview]
Message-ID: <m38yfqvhf5.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <86ekpi226m.fsf@doze.rz-berlin.mpg.de>
Jochen Küpper <jochen@fhi-berlin.mpg.de> writes:
> Since tonight I get plenty of empty lines in message-composition
> buffers, i.e.
It's extremely likely that this is due to the header filling changes
I did earlier today, but I'm unable to reproduce the bug.
Which X/Emacs are you using?
And what's the value of your `message-header-format-alist' variable?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2004-05-17 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 21:06 Jochen Küpper
2004-05-17 22:05 ` Lars Magne Ingebrigtsen [this message]
2004-05-18 4:46 ` Norbert Koch
2004-05-18 13:49 ` Lars Magne Ingebrigtsen
2004-05-18 15:05 ` Norbert Koch
[not found] ` <m38yfqvhf5.fsf-qBEgNjfYAPolG3ThADb//ti2O/JbrIOy@public.gmane.org>
2004-05-18 11:33 ` Jochen Küpper
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=m38yfqvhf5.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).