unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Matt Armstrong <marmstrong@google.com>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Emacs and the missing 'g'
Date: Tue, 12 Feb 2019 21:04:56 -0800	[thread overview]
Message-ID: <CAF5O0erPcqR=wrNt0GCUvBuA4-xdvKkxrJAoNNB9Chn9cCW=QA@mail.gmail.com> (raw)

I'm returning to notmuch after a hiatus.  It is still nice!

First thing I've noticed: the Emacs modes seem to ignore the 'g' key.  I
would like to bind it (by default) to the relevant "refresh" commands.
I'll explain.

notmuch-hello mode leaves 'b' bound to self-insert-command, and
notmuch-search mode does as well.

Most notmuch modes are "special" modes -- i.e. their text is generated
by Emacs and does not reflect a file.  In these modes 'g' has
traditionally been bound to revert the buffer [1].

You see this across many modes: dired, vc, gnus, etc.

I was actually going to report this as a bug until I realized that
notmuch consistently uses '=' for the same thing.

Any objection to also binding 'g'?


For context, here is the list of other bindings in a "special" mode
(from Emacs' simple.el).  Notmuch already follows some of these (such as
<, > and q).

    SPC             scroll-up-command
    -               negative-argument
    0 .. 9          digit-argument
    <               beginning-of-buffer
    >               end-of-buffer
    ?               describe-mode
    g               revert-buffer
    h               describe-mode
    q               quit-window
    DEL             scroll-down-command
    S-SPC           scroll-down-command

[1] (elisp) Basic Major Modes

             reply	other threads:[~2019-02-13  5:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13  5:04 Matt Armstrong [this message]
2019-02-13 20:34 ` Emacs and the missing 'g' Carl Worth
2019-02-13 20:39 ` David Bremner

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='CAF5O0erPcqR=wrNt0GCUvBuA4-xdvKkxrJAoNNB9Chn9cCW=QA@mail.gmail.com' \
    --to=marmstrong@google.com \
    --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).