From: Shreyank Gupta <shreyankg@gmail.com>
To: sup-talk@rubyforge.org
Subject: [sup-talk] Signature
Date: Mon, 25 Jan 2010 14:41:48 +0530 [thread overview]
Message-ID: <8b854d6b1001250111i3bf7c27fjc2c91449413cf4e7@mail.gmail.com> (raw)
Hi,
While reading mails in sup, it makes lots of mistakes in identifying
the signature.
Ideally it should identify the last block of text preceded with a '--'
as the signature block. Instead it takes a random block of email body
and condenses it as signature.
Is there any way around this problem?
--
Peace and Love,
Shreyank Gupta
Blog: http://allsortsofshrink.blogspot.com
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2010-01-25 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 9:11 Shreyank Gupta [this message]
2010-01-25 21:27 ` 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=8b854d6b1001250111i3bf7c27fjc2c91449413cf4e7@mail.gmail.com \
--to=shreyankg@gmail.com \
--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