From: marc.hartstein@alum.vassar.edu (Marc Hartstein)
Subject: [sup-talk] About newlines
Date: Fri, 04 Apr 2008 12:16:09 -0400 [thread overview]
Message-ID: <1207325501-sup-8401@cabinet> (raw)
In-Reply-To: <1207309393-sup-2829@ausone.inria.fr>
Excerpts from Nicolas Pouillard's message of Fri Apr 04 08:14:06 -0400 2008:
> I'm hitting a bug concerning forwarding, all newlines get trimmed off. I'm
> trying to fix the bug, but I don't understand if arrays of lines are supposed
> to be ended by newlines or not.
After a bit of chat in #sup on freenode, I have a workaround and some
comments.
Workaround (tested): make sure you instruct your editor to save the
temporary file even when you are making no changes. This will force sup
to capture the contents of the file, which will include the newlines.
New bug: the same bug exists when replying if you don't edit your
message before sending (why would you ever do that?)
The problem seems to be that when the body of forward/reply messages is
built, it is built without a newline terminator at the end of every
line. This is infrequently noticed because those newlines get added to
the temporary file for editing.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080404/0ecde927/attachment.bin
next prev parent reply other threads:[~2008-04-04 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 12:14 Nicolas Pouillard
2008-04-04 16:08 ` William Morgan
2008-04-04 16:10 ` Nicolas Pouillard
2008-04-04 16:16 ` Marc Hartstein [this message]
2008-04-04 13:13 kendall at clarkparsia.com
2008-04-04 16:17 kendall at clarkparsia.com
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=1207325501-sup-8401@cabinet \
--to=marc.hartstein@alum.vassar.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