From: Servilio Afre Puentes <servilio@gmail.com>
To: David Edmondson <dme@dme.org>
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: pull request
Date: Thu, 22 Apr 2010 10:10:15 -0400 [thread overview]
Message-ID: <w2tb22065d01004220710y986e144ct5f276ac7a1af3928@mail.gmail.com> (raw)
In-Reply-To: <87aasvk6tx.fsf@ut.hh.sledj.net>
On 22 April 2010 08:30, David Edmondson <dme@dme.org> wrote:
> On Thu, 22 Apr 2010 04:58:16 -0400, Servilio Afre Puentes <servilio@gmail.com> wrote:
>> On 21 April 2010 17:03, Carl Worth <cworth@cworth.org> wrote:
>> > On Mon, 19 Apr 2010 09:27:39 +0100, David Edmondson <dme@dme.org> wrote:
>> [...]
>> > Meanwhile, another issue with the result of this series is that I now
>> > seem to get rendering for both the text/plain and the text/html
>> > alternatives when a message has both. For now, the paragraphs are
>> > wrapped much more nicely in the rendering of the html portion, but links
>> > are apparently entirely missing. The link URLs at least appear in the
>> > text/plain rendering, (which is pretty ugly, but at least not impossible
>> > to use).
>> >
>> > If we could get one version or the other working completely, then it
>> > would be nice to display only one.
>>
>> I think that a better approach here would be to list them as parts if
>> they are present, then have a [configurable] way to show only one by
>> default, and the other would be available to show in-line.
>
> Showing only one (with a variable allowing you to express preference) is
> my intention. Any non-shown parts will appear as attachments - you can
> save them using the button (and perhaps later view them).
Why not see them in-line if possible?
> This can make quite a big difference in a 200 message thread with lots
> of 'text/plain or text/html ?' choices - using the text/plain part will
> improve the performance of building the show buffer significantly.
Yes, it can make a big difference.
>> What I miss in this view sometimes is the possibility of being able to
>> see the structure of the thread. A way to toggle the expanded state of
>> the messages originally expanded when I first opened the view would do
>> this very nicely.
>
> Ah, so you want a "go back to how it was initially" command?
Yep, then bind it to a key that would alternate between collapsing all
messages and expanding the ones that were originally expanded.
Servilio
next prev parent reply other threads:[~2010-04-22 14:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 10:29 pull request David Edmondson
2010-04-19 8:27 ` David Edmondson
2010-04-19 18:07 ` Carl Worth
2010-04-19 18:18 ` Carl Worth
2010-04-20 5:27 ` David Edmondson
2010-04-20 16:25 ` Carl Worth
2010-04-21 12:39 ` David Edmondson
2010-04-21 19:15 ` Carl Worth
2010-04-21 19:47 ` Jameson Rollins
2010-04-23 11:57 ` David Edmondson
2010-04-23 12:49 ` Jameson Rollins
2010-04-22 6:04 ` David Edmondson
2010-04-21 21:03 ` Carl Worth
2010-04-22 6:59 ` David Edmondson
2010-04-23 19:44 ` Carl Worth
2010-04-22 8:24 ` [PATCH] emacs/notmuch-show.el: Add `notmuch-show-toggle-all' bound to M-RET David Edmondson
2010-04-23 19:34 ` Carl Worth
2010-04-24 0:29 ` Carl Worth
2010-04-22 8:58 ` pull request Servilio Afre Puentes
2010-04-22 12:30 ` David Edmondson
2010-04-22 14:10 ` Servilio Afre Puentes [this message]
2010-04-22 14:41 ` David Edmondson
-- strict thread matches above, loose matches on Subject: below --
2010-04-01 14:41 David Edmondson
2010-04-01 21:09 ` Carl Worth
2010-04-01 22:50 ` David Bremner
2010-04-02 8:53 ` David Edmondson
2010-04-02 22:53 ` Carl Worth
2010-04-03 6:34 ` David Edmondson
2010-04-03 19:42 ` Carl Worth
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=w2tb22065d01004220710y986e144ct5f276ac7a1af3928@mail.gmail.com \
--to=servilio@gmail.com \
--cc=dme@dme.org \
--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).