Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: kendall@clarkparsia.com (kendall at clarkparsia.com)
Subject: [sup-talk] About newlines
Date: Fri, 4 Apr 2008 12:17:55 -0400 (EDT)	[thread overview]
Message-ID: <40985.192.168.1.71.1207325875.webmail@192.168.1.71> (raw)

This is precisely what my correspondents see when I forward messages w/out editing them from sup -- and they yell at me, which isn't fun. :>

Cheers,
Kendall

PS--Sorry for the top post, but it seemed reasonable here (and I'm not using sup today!).

On Friday, April 4, 2008 12:10pm, Nicolas Pouillard <nicolas.pouillard at gmail.com> said:

> _______________________________________________
> sup-talk mailing list
> sup-talk at rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-talk
> Excerpts from William Morgan's message of Fri Apr 04 18:08:02 +0200 2008:>
> Reformatted excerpts from nicolas.pouillard's message of 2008-04-04:> > 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.> > I don't see this behavior, either in the
> forward mode buffer or in the> resulting message.> > Newlines shouldn't exist in
> arrays of lines.> ForwardMode#forward_body_lines is the relevant method. Let me
> know what> you discover.I hope that my bunch of patches will makes this clear.--
> Nicolas Pouillard aka Ertai




             reply	other threads:[~2008-04-04 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 16:17 kendall at clarkparsia.com [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-04 13:13 kendall at clarkparsia.com
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

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=40985.192.168.1.71.1207325875.webmail@192.168.1.71 \
    --to=kendall@clarkparsia.com \
    /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