Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
* [sup-talk] Loosing first line of body, intentional or bug?
@ 2011-02-09 19:45 Philippe LeCavalier
  2011-02-10 14:52 ` Michael Stapelberg
  0 siblings, 1 reply; 3+ messages in thread
From: Philippe LeCavalier @ 2011-02-09 19:45 UTC (permalink / raw)
  To: sup-talk

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
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [sup-talk] Loosing first line of body, intentional or bug?
  2011-02-09 19:45 [sup-talk] Loosing first line of body, intentional or bug? Philippe LeCavalier
@ 2011-02-10 14:52 ` Michael Stapelberg
  2011-02-10 15:31   ` Philippe LeCavalier
  0 siblings, 1 reply; 3+ messages in thread
From: Michael Stapelberg @ 2011-02-10 14:52 UTC (permalink / raw)
  To: sup-talk

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
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [sup-talk] Loosing first line of body, intentional or bug?
  2011-02-10 14:52 ` Michael Stapelberg
@ 2011-02-10 15:31   ` Philippe LeCavalier
  0 siblings, 0 replies; 3+ messages in thread
From: Philippe LeCavalier @ 2011-02-10 15:31 UTC (permalink / raw)
  To: Michael Stapelberg; +Cc: sup-talk

Excerpts from Michael Stapelberg's message of Thu Feb 10 09:52:14 -0500 2011:
> 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.
> 
I'm referring to the diff between this:

--------
References: <1297277984-sup-9281@plc.intranet.plecavalier.com> <1297349497-sup-2501@midna.zekjur.net>

 Hi Michael
---------

And this:
---------
References: <1297277984-sup-9281@plc.intranet.plecavalier.com> <1297349497-sup-2501@midna.zekjur.net>
 Hi Michael
--------

If I leave the latter the "Hi Michael" ends up looking like this:
----------
References: <1297277984-sup-9281@plc.intranet.plecavalier.com> <1297349497-sup-2501@midna.zekjur.net>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
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-02-10 15:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-02-09 19:45 [sup-talk] Loosing first line of body, intentional or bug? Philippe LeCavalier
2011-02-10 14:52 ` Michael Stapelberg
2011-02-10 15:31   ` Philippe LeCavalier

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox