From: David Abrahams <dave@boost-consulting.com>
Subject: (Ping) [message] Extra newlines in replies
Date: Mon, 10 Jul 2006 16:24:17 -0400 [thread overview]
Message-ID: <upsgdryxa.fsf@boost-consulting.com> (raw)
In-Reply-To: <uirnj2whg.fsf@boost-consulting.com>
David Abrahams <dave@boost-consulting.com> writes:
> occasionally embedding extra newlines. For example:
> http://sourceforge.net/mailarchive/message.php?msg_id=16826842
>
> My NTEmacs version is "22.0.50.1", a fairly recent build from CVS.
>
> In all the buffers I'm replying to that cause me problems, the mode
> line starts with "-*". I'm afraid I don't understand how to parse my
> mode-line format (quoted below, "%e" doesn't show up in the
> documentation for that variable), so I don't know what that means, but
> it does seem to be the distinguishing factor.
>
> Can anyone help me fix this problem? Thanks!
Ping?
New information: it only seems to happen when I reply to a message
with a "Content-Transfer-Encoding: 8bit" header. I'm pretty sure the
"%e" has something to do with buffer encoding.
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
next prev parent reply other threads:[~2006-07-10 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 19:22 David Abrahams
2006-07-10 20:24 ` David Abrahams [this message]
2006-07-12 23:45 ` Is this the wrong forum? David Abrahams
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=upsgdryxa.fsf@boost-consulting.com \
--to=dave@boost-consulting.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).