From: Christopher Dimech <dimech@gmx.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Viewing Info Files - Introduce Top Menu also before end of buffer
Date: Sat, 17 Oct 2020 21:03:26 +0200 [thread overview]
Message-ID: <trinity-fb6d15c4-eb60-4a02-8a54-7567017325b0-1602961406463@3c-app-mailcom-bs03> (raw)
In-Reply-To: <229af73a-c83c-4150-8445-ef9ce02468be@default>
That figures. You put bindings in one place. Incidentally, I am
writing an abbreviated manual for Elisp for release as Part of
the Gnu Project.
> Sent: Saturday, October 17, 2020 at 8:39 PM
> From: "Drew Adams" <drew.adams@oracle.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: RE: RE: RE: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer
>
> > I recommend putting a list of the keybindings so one can easily
> > figure it they interfere with those already set by the user.
>
> The keys that get bound depend on the context, options,
> system etc. Hard-coding doc that lists the bindings is
> impractical.
>
> `C-h b' shows you the currently available bindings.
>
> This section of `info+.el' provides the key bindings,
> so you can see what you're getting (assuming some
> knowledge of reading Elisp):
>
> ;;; KEYS & MENUS ;;;;;;;;;;;;;;;;;;;;;;;;
>
> If you use library `help-fns+.el' then `C-h M-k'
> describes the bindings of a keymap. For `Info-mode-map'
> it describes the bindings for Info mode.
>
> https://www.emacswiki.org/emacs/download/help-fns%2b.el
>
>
prev parent reply other threads:[~2020-10-17 19:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 20:37 Viewing Info Files - Introduce Top Menu also before end of buffer Christopher Dimech
2020-10-16 21:11 ` Drew Adams
2020-10-16 21:18 ` Christopher Dimech
2020-10-16 21:23 ` Christopher Dimech
2020-10-16 21:46 ` Christopher Dimech
2020-10-16 21:58 ` Drew Adams
2020-10-16 22:58 ` Christopher Dimech
2020-10-16 23:08 ` Drew Adams
2020-10-16 23:51 ` Christopher Dimech
2020-10-17 16:37 ` Drew Adams
2020-10-17 18:01 ` Christopher Dimech
2020-10-17 18:05 ` RE: RE: RE: " Christopher Dimech
2020-10-17 18:39 ` Drew Adams
2020-10-17 19:03 ` Christopher Dimech [this message]
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-fb6d15c4-eb60-4a02-8a54-7567017325b0-1602961406463@3c-app-mailcom-bs03 \
--to=dimech@gmx.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@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.
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).