From: Philippe LeCavalier <support@plecavalier.com>
To: Michael Stapelberg <michael+sup@stapelberg.de>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Loosing first line of body, intentional or bug?
Date: Thu, 10 Feb 2011 10:31:39 -0500 [thread overview]
Message-ID: <1297351086-sup-7177@plc.intranet.plecavalier.com> (raw)
In-Reply-To: <1297349497-sup-2501@midna.zekjur.net>
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
prev parent reply other threads:[~2011-02-10 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 19:45 Philippe LeCavalier
2011-02-10 14:52 ` Michael Stapelberg
2011-02-10 15:31 ` Philippe LeCavalier [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=1297351086-sup-7177@plc.intranet.plecavalier.com \
--to=support@plecavalier.com \
--cc=michael+sup@stapelberg.de \
--cc=sup-talk@rubyforge.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