unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: emacs tree view usability improvement: notmuch-tree should indicate which message is being shown
Date: Mon, 11 Feb 2019 13:34:59 -0500	[thread overview]
Message-ID: <87wom6uqb0.fsf@fifthhorseman.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]

hi all--

TIL about tree-view -- pressing 'Z' from a "notmuch-show" buffer is very
nice, thanks to all who worked on this feature.

I have a small usability improvement to ask for, sorry that my elisp is
too weak to propose a patch.

when i've hit Z, i get a split emacs view with two buffers -- one is the
"notmuch-tree" buffer, and the other is a "notmuch-show" buffer.

when i hit enter on a point inside the notmuch-tree buffer, the
notmuch-show buffer's contents change.

It would be great if the notmuch-tree buffer would maintain a specific
marker indicating which message is being shown.  As it stands, the
highlighted row in notmuch-tree can change if i move where the point is,
but don't hit enter -- so one message in notmuch-tree is highlighted,
but a different message in displayed in notmuch-show.

There are hints that they don't match already, of course -- the metadata
about each message is likely to be different, and an astute reader can
catch it.

Avoiding the confusion entirely by having a distinct indicator of the
shown message (e.g. maybe a "─►" to the left of the line corresponding
to the message in notmuch-tree) would be pretty nice.

    --dkg

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

                 reply	other threads:[~2019-02-11 18:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87wom6uqb0.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.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).