From: Austin Clements <amdragon@mit.edu>
To: Jameson Graef Rollins <jrollins@finestructure.net>
Cc: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: tweaks for handling parts in reply
Date: Thu, 9 Jun 2011 21:58:41 -0400 [thread overview]
Message-ID: <BANLkTikT9HgD=UijeBWLOEVz+rbKPtmFZQ@mail.gmail.com> (raw)
In-Reply-To: <1307561409-5646-1-git-send-email-jrollins@finestructure.net>
It's too bad this requires lots of special-casing. I dug into mutt,
hoping to find some simpler way to choose what to reply to, but all I
found was a far more complicated collection of heuristics (see
mutt_body_handler if you're interested).
Should reply *ever* include a "Non-text part" message? It certainly
doesn't help the receiver of the reply and presumably the sender will
either notice that a part is missing if they care about it, or
probably miss the Non-text part message anyway if they don't.
On Wed, Jun 8, 2011 at 3:30 PM, Jameson Graef Rollins
<jrollins@finestructure.net> wrote:
> This is a small set of tweaks to remove unneccessary "Non-text part:"
> lines in reply, for parts that really don't need to be mentioned.
>
> This patch set is not really related to the series that it is being
> sent in reply to, but it has been worked on top of the message/rfc822
> rework of the multipart test, so it's being sent in reply to that
> message.
>
> jamie.
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
>
next prev parent reply other threads:[~2011-06-10 1:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 17:13 problems with message/rfc822 parts Jameson Graef Rollins
2011-06-06 0:29 ` improving message/rfc822 part handling Jameson Graef Rollins
2011-06-06 0:29 ` [PATCH 1/5] test: some small fixes to multipart test Jameson Graef Rollins
2011-06-06 0:29 ` [PATCH 2/5] test: Fix date in test message in " Jameson Graef Rollins
2011-06-06 0:29 ` [PATCH 3/5] test: overhaul multipart test to test for improved message/rfc822 handling Jameson Graef Rollins
2011-06-06 0:29 ` [PATCH 4/5] Improve handling of message/rfc822 parts by adding a new header_message_part function to the formating structure Jameson Graef Rollins
2011-06-06 0:29 ` [PATCH 5/5] emacs: Improve support for message/rfc822 parts Jameson Graef Rollins
2011-06-08 19:30 ` tweaks for handling parts in reply Jameson Graef Rollins
2011-06-08 19:30 ` [PATCH 1/4] test/multipart: test for absence of "Non-text part:" lines in reply for multipart/* and message/rfc822 parts Jameson Graef Rollins
2011-06-08 19:30 ` [PATCH 2/4] Fix notmuch-reply to not output "Non-text part:" lines for non-leafnode parts Jameson Graef Rollins
2011-06-08 19:30 ` [PATCH 3/4] test: test for absence of "Non-text part: application/pgp-*" lines in reply Jameson Graef Rollins
2011-06-08 19:30 ` [PATCH 4/4] Ignore "application/pgp-*" parts " Jameson Graef Rollins
2011-06-10 1:58 ` Austin Clements [this message]
2011-10-06 13:29 ` tweaks for handling " David Bremner
2011-10-06 17:24 ` Jameson Graef Rollins
2011-09-05 19:01 ` [PATCH] test: overhaul multipart test to test for improved message/rfc822 handling Jameson Graef Rollins
2011-09-06 2:08 ` David Bremner
2011-09-05 12:06 ` [PATCH 2/5] test: Fix date in test message in multipart test David Bremner
2011-06-06 0:33 ` improving message/rfc822 part handling Jameson Graef Rollins
2011-06-06 3:56 ` Jameson Graef Rollins
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTikT9HgD=UijeBWLOEVz+rbKPtmFZQ@mail.gmail.com' \
--to=amdragon@mit.edu \
--cc=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).