From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: a colon with forward-slashes kicks lines to the top - why?
Date: Tue, 05 Sep 2006 08:17:03 +0900 [thread overview]
Message-ID: <b4m7j0jxlw0.fsf@jpl.org> (raw)
In-Reply-To: <edhpn9$g8e$1@sea.gmane.org>
>>>>> In <edhpn9$g8e$1@sea.gmane.org> Tomasz Mieszkowski wrote:
> Hello everyone,
> I've been wrestling with this for quite long (without success), so maybe
> here I'll find some light :)
> The problem is when I use a combination of colon and forward-slashes (an
> URL for example) in the body of my posts, the line which contains them,
> irrespective of its original location, is moved somehow to the top when
> I hit C-c C-c. Because of that, my posts are screwed quite often and I
> have to supersede them. I thought that maybe article fontisizing is
> responsible for this behavior, but it seems that it has nothing to do
> with it. And the only function I have on message-send-news-hook is
> message-sort-headers.
I think it is just the cause of your problem.
`message-sort-headers' requires that there is a separator (i.e.,
"--text follows this line--") between header and body. However,
it isn't at the time when `message-send-news-hook' is run. How
about using `message-send-hook' instead?
P.S.
No Gnus users don't have to run `message-sort-headers' by
yourself since it is always run by Gnus (see the function
definition of `message-fix-before-sending') when sending a
message.
next prev parent reply other threads:[~2006-09-04 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 18:02 Tomasz Mieszkowski
2006-09-04 23:17 ` Katsumi Yamaoka [this message]
2006-09-05 13:22 ` Tomasz Mieszkowski
-- strict thread matches above, loose matches on Subject: below --
2006-09-03 12:06 Tomasz Mieszkowski
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=b4m7j0jxlw0.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).