unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Bart Bunting <bart@bunting.net.au>
To: notmuch@notmuchmail.org
Subject: notmuch-show-toggle-message behavior
Date: Fri, 28 Aug 2015 11:15:16 +1000	[thread overview]
Message-ID: <m2y4gwmcwr.fsf@ursys.com.au> (raw)

Hi,

Following the discussion in: id:874mjk614c.fsf@qmul.ac.uk regarding the
behavior of notmuch-show-toggle-message and following hyperlinks, I
wanted to chime in on a similar but not exactly the same topic.

I am blind and use emacspeak (a speech subsystem for emacs) to do all of
my emacs work including reading email with notmuch.

I often arrow down to a part and hit enter only to find that
notmuch-show-toggle-message hides all of the message body because the
point is at the beginning of the line and the part I'm actually trying
to toggle is indented.

Would it make sense to have notmuch-show-toggle-message activate any
item on the same line rather than take the generic action of hiding all
the message text.

I would also like it if for example there was an id or hyperlink on the
line that it was activated.  In the case that there was more than one
then activating the first one unless point is on the second or
subsiquent link sounds like predictable behavior to me.
.

The implication of the current behaviour for me is that when this
happens i need to unhide the message and then move to the part I want to
expand makeing sure I move off the empty space at the beginning of the
line before triggering notmuch-show-toggle-message.

Is this behaviour annoying to anyone else?

If not I'm sure I can work around it using advice or something.


Kind regards
Bart
-- 

Bart Bunting

             reply	other threads:[~2015-08-28  1:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28  1:15 Bart Bunting [this message]
2015-08-28  5:50 ` notmuch-show-toggle-message behavior Tomi Ollila

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=m2y4gwmcwr.fsf@ursys.com.au \
    --to=bart@bunting.net.au \
    --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).