unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Neeum Zawan <mailinglists@nawaz.org>
To: notmuch@notmuchmail.org
Subject: Re: Preventing the user shooting themself in the foot
Date: Sat, 09 Jul 2011 10:09:09 -0700	[thread overview]
Message-ID: <87aacns7nu.fsf@fester.com> (raw)
In-Reply-To: 86iproe86u.fsf@greenrd.plus.com

Hi,

My wishes:

1. Space shouldn't archive. All too often it happens by mistake. It
   should just go to the end of the thread and stop, or return to the
   query results without archiving.

2. The unread tag should be kept as is. I find it useful (although
   admittedly mostly to resolve accidental archiving!) Regardless, even
   if that issue is fixed, I can see unread being useful.

3. One thing I *sorely* would like: Keybindings to go to the
   next/previous messages *in the query*. This would be my primary way
   of dealing with emails. If only one message in the middle of the
   thread matches the query, then I should be able to go to the next
   match with one keystroke (and no, defining a macro for "q", "n",
   "Enter" won't always work - what if two messages in a query match the
   search?) If there's a way to do this now, I'd like to know...

4. I'd also really like a way to display only messages matching a query
   (without rebuilding the thread). When viewing a message, if desired,
   a keybinding could construct just that thread. 

  parent reply	other threads:[~2011-07-09 18:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29 19:42 Preventing the user shooting themself in the foot Robin Green
2011-06-29 20:37 ` Jameson Graef Rollins
2011-06-29 22:40 ` Carl Worth
2011-06-30  3:04   ` Brian May
2011-06-30  4:10     ` Jameson Graef Rollins
2011-06-30  5:40     ` Carl Worth
2011-06-30  7:45       ` Pieter Praet
2011-06-30 21:26       ` Michael Hudson-Doyle
2011-07-01 16:37         ` Jameson Graef Rollins
2011-07-01 17:17           ` Austin Clements
2011-07-01 17:11         ` Pieter Praet
2011-06-30 23:02       ` Stewart Smith
2011-06-30  6:29   ` Sebastian Spaeth
2011-07-04 20:09     ` Michal Sojka
2011-07-04 21:36 ` Dangerous space bar key (was: Preventing the user shooting themself in the foot) Matthieu Lemerre
2011-07-05  0:03   ` Jameson Graef Rollins
2011-07-05 20:23     ` Matthieu Lemerre
2011-07-06 13:25       ` Austin Clements
2011-07-07 18:49         ` Matthieu Lemerre
2011-07-07 20:40           ` Jameson Graef Rollins
2011-07-07 20:58             ` Austin Clements
2011-07-07 21:17               ` Jameson Graef Rollins
2011-07-09 17:09 ` Neeum Zawan [this message]
2011-07-09 20:32   ` Preventing the user shooting themself in the foot Daniel Schoepe
  -- strict thread matches above, loose matches on Subject: below --
2011-06-29 23:53 Austin Clements
2011-06-30  7:50 ` Pieter Praet
2011-06-30  8:51   ` Pieter Praet
2011-07-01  1:28   ` Brian May
2011-07-01 21:44     ` Pieter Praet

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=87aacns7nu.fsf@fester.com \
    --to=mailinglists@nawaz.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).