From: Eli Zaretskii <eliz@gnu.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 39631@debbugs.gnu.org
Subject: bug#39631: Mention how to remove entire keymaps in Your Init File
Date: Sun, 16 Feb 2020 17:20:31 +0200 [thread overview]
Message-ID: <83tv3qmudc.fsf@gnu.org> (raw)
In-Reply-To: <87ftfbf9se.5.fsf@jidanni.org>
> From: 積丹尼 Dan Jacobson
> <jidanni@jidanni.org>
> Date: Sun, 16 Feb 2020 12:14:41 +0800
>
> There are insufficient instructions and examples in
>
> Info 49.3.6 Rebinding Keys in Your Init File
>
> as of emacs-version "26.3"
>
> to allow the user to get rid of e.g., (seen with C-h b)
> C-, flyspell-goto-next-error
> C-. flyspell-auto-correct-word
> C-; flyspell-auto-correct-previous-word
> C-c $ flyspell-correct-word-before-point
>
> Leaving only
> C-M-i flyspell-auto-correct-word
>
> The user tries everything
I think there's a limit to what we can say in the user manual that
describes Lisp facilities. Users who are serious about key-binding
customizations should read the ELisp manual to augment and complement
what is in the user manual.
next prev parent reply other threads:[~2020-02-16 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 3:28 bug#39630: Mention how to unset keys in Your Init File 積丹尼 Dan Jacobson
[not found] ` <handler.39630.C.15829502435362.notifdonectrl.0@debbugs.gnu.org>
2020-02-16 4:14 ` bug#39631: Mention how to remove entire keymaps " 積丹尼 Dan Jacobson
2020-02-16 15:20 ` Eli Zaretskii [this message]
2020-02-16 16:30 ` 積丹尼 Dan Jacobson
2020-02-16 16:37 ` 積丹尼 Dan Jacobson
2020-02-29 4:28 ` Stefan Kangas
2020-02-29 4:51 ` bug#39631: Actually 39802 solves the need for 39630 and 39631 積丹尼 Dan Jacobson
2020-02-29 5:17 ` bug#39631: Zapping a whole keymap 積丹尼 Dan Jacobson
2020-02-16 15:19 ` bug#39630: Mention how to unset keys in Your Init File Eli Zaretskii
2020-02-16 16:28 ` 積丹尼 Dan Jacobson
2020-02-16 16:44 ` 積丹尼 Dan Jacobson
2020-02-29 4:23 ` Stefan Kangas
2020-02-29 5:00 ` Noam Postavsky
2020-02-29 5:22 ` bug#39802: " Stefan Kangas
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=83tv3qmudc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39631@debbugs.gnu.org \
--cc=jidanni@jidanni.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://git.savannah.gnu.org/cgit/emacs.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).