Subject: [sup-talk] Loosing first line of body, intentional or bug?

From: Philippe LeCavalier <[email-masked]>
Date: Wed, 09 Feb 2011 14:45:35 -0500

If I forget to add an extra linebreak when top-posting the first line of my reply is brought back up into the headers(references) and therefore doesn't appear in the body. This is especially annoying if I reply with a one liner.
-- 
Thanks,
Phil
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Michael Stapelberg <[email-masked]>
Date: Thu, 10 Feb 2011 15:52:14 +0100

Hi Philippe,

Excerpts from Philippe LeCavalier's message of 2011-02-09 20:45:35 +0100:
> If I forget to add an extra linebreak when top-posting the first line of my
> reply is brought back up into the headers(references) and therefore doesn't
> appear in the body. This is especially annoying if I reply with a one liner.
Well, how would you distinguish text from an additional header? I would call
the behaviour intentional.

Best regards,
Michael

---

From: Philippe LeCavalier <[email-masked]>
Date: Thu, 10 Feb 2011 10:31:39 -0500

> the behaviour intentional.
I'm referring to the diff between this:

--------
References: <[email-masked]> <[email-masked]>

 Hi Michael
---------

And this:
---------
References: <[email-masked]> <[email-masked]>
 Hi Michael
--------

If I leave the latter the "Hi Michael" ends up looking like this:
----------
References: <[email-masked]> <[email-masked]>Hi Michael
                                                                                                      ^here^

I suspect a rather obvious workaround is adding a linebreak to:

/usr/bin/vim '+/^\s*\n'

In config.yaml

but shouldn't this be considered a bug? Or is this just happening to me?
-- 
Thanks,
Phil
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk