all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "N. Jackson" <nljlistbox2@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 16455@debbugs.gnu.org
Subject: bug#16455: 24.3; (Emacs Info) h command behaves like H command
Date: Wed, 15 Jan 2014 23:03:46 -0400	[thread overview]
Message-ID: <CABcSQd6iqgdgytesn7WpMLS6KgVWx+ZcG6e-o_HcV6FsH8AqSw@mail.gmail.com> (raw)
In-Reply-To: <b7k3e1hrnx.fsf@fencepost.gnu.org>

On Wed, Jan 15, 2014 at 5:16 PM, Glenn Morris <rgm@gnu.org> wrote:
> Use standard Emacs commands for listing key bindings, eg `C-h m'.

Ah! Thank you Glen. That's exactly what I wanted to see. I had no idea
that C-h m listed key bindings, I thought it just provided information
about the prevailing modes. Of course, key bindings in a mode are
information about the mode. I'd just never thought of it. I haven't
used C-h m since I ran the Emacs tutorial three and a half years ago.
From there it brings up information about fundamental mode, no obvious
key binding documentation, and I had filed the command in my head as
"rather useless"! My mistake.

So the confusion turns out to be my ignorance plus the inconsistent
Info documentation, and no bug in Emacs [Currently. Although if the
Info documentation is fixed to be self-consistent, it seems that Emacs
Info mode might need to change so that H invokes the Info tutorial?],
so please close this bug. Sorry for wasting time.





  reply	other threads:[~2014-01-16  3:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 15:28 bug#16455: 24.3; (Emacs Info) h command behaves like H command N. Jackson
2014-01-15 17:09 ` Glenn Morris
2014-01-15 20:45   ` N. Jackson
2014-01-15 21:16     ` Glenn Morris
2014-01-16  3:03       ` N. Jackson [this message]
2014-01-16  3:15         ` N. Jackson
2014-01-16  8:28         ` Glenn Morris
2014-01-16 16:25           ` N. Jackson
2014-02-28  2:17             ` Glenn Morris

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABcSQd6iqgdgytesn7WpMLS6KgVWx+ZcG6e-o_HcV6FsH8AqSw@mail.gmail.com \
    --to=nljlistbox2@gmail.com \
    --cc=16455@debbugs.gnu.org \
    --cc=rgm@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.