From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Pterodactyl Gnus v0.48 is released
Date: 16 Nov 1998 02:33:24 -0500 [thread overview]
Message-ID: <2npvao5by3.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: Karl Kleinpaste's message of "15 Nov 1998 20:32:25 -0500"
>>>>> "KK" == Karl Kleinpaste <karl@jprc.com> writes:
KK> I looked at it a bit w/edebug. message-encode-message-body has at
KK> least 2 problems, when using `B m':
KK> - (message-goto-body) leaves (point) at 1, considering what the
KK> following narrow-to-region does, so the entire message is regarded
KK> as body content, and
KK> - when inserting the Content-Type line, it gets put in after the
KK> (search-forward "\n\n"), which leaves point at the end of the
KK> discovered string. Something like (forward-line -1) is in order,
KK> before (insert line).
KK> I'm not sufficiently confident of what's going on here to offer
KK> patches directly, however.
Do not patch message.el.
See "Re: Problem with B m in 0.44"
--
Shenghuo
prev parent reply other threads:[~1998-11-16 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-16 1:00 Lars Magne Ingebrigtsen
1998-11-16 1:32 ` Karl Kleinpaste
1998-11-16 7:33 ` Shenghuo ZHU [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=2npvao5by3.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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).