From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] When replying to an attachment...
Date: Sat, 01 Dec 2007 13:35:38 +0100 [thread overview]
Message-ID: <1196512356-sup-396@ausone.local> (raw)
In-Reply-To: <1196411410-sup-5575@ausone.local>
Excerpts from Nicolas Pouillard's message of Fri Nov 30 09:34:13 +0100 2007:
> Hi,
>
> Sometimes some (bad) mailers wrap the entire body in an attachment, that is
> considered by sup as just an attachment (still opened by default). When
> replying to this kind of email the original message is not present in the
> answer mode.
>
> That's quite annoying to copy, paste, quote manually to reply to these mails.
I've found a way to fix it. But I don't known if it's a bug or if it was intentional.
What about making Attachments 'quotable?' when they are text/plain?
Patch attached!
--
Nicolas Pouillard aka Ertai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sup-text-plain-is-quotable.patch
Type: application/octet-stream
Size: 447 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071201/8305ab74/attachment.obj
next prev parent reply other threads:[~2007-12-01 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 8:34 Nicolas Pouillard
2007-12-01 12:35 ` Nicolas Pouillard [this message]
2007-12-08 22:06 ` William Morgan
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=1196512356-sup-396@ausone.local \
--to=nicolas.pouillard@gmail.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