From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] [PATCH] Gmail style attachment processing
Date: Tue, 29 Apr 2008 22:12:43 +0100 [thread overview]
Message-ID: <1209502890-sup-4022@tomsk> (raw)
In-Reply-To: <1209502678-sup-1941@tangerine.lanl.gov>
On 29.4.2008, John Bent wrote:
> This is excellent. Thanks very much! I don't like doing the patches
> myself but I'm looking forward to this getting into next.
:) I couldnt live without it in gmail so I had to have it in sup! I'd
like to have added the regexanalyser suggested by William so that I
could have a list of attachments on the message object just by
querying the index but this affected searching usability a bit (I get
a lot of attachments with spaces in and using the regexanalyser meant
that you couldnt search for single words from that attachment without
wildcards which didnt seem right). I may work on that a bit and add to
this patch but for now it works really well for my usage.
Marcus
next prev parent reply other threads:[~2008-04-29 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 20:45 Marcus Williams
2008-04-29 21:02 ` John Bent
2008-04-29 21:12 ` Marcus Williams [this message]
2008-05-25 4:10 ` 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=1209502890-sup-4022@tomsk \
--to=marcus-sup@bar-coded.net \
/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