From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: 25175@debbugs.gnu.org
Cc: manuel serrano <manuel.serrano@sophia.inria.fr>
Subject: bug#25175: flyspell-mode: stay off of C-c . best
Date: Mon, 12 Dec 2016 02:23:28 +0800 [thread overview]
Message-ID: <87bmwi9vfj.fsf@jidanni.org> (raw)
X-Debbugs-cc: Manuel Serrano <Manuel.Serrano@sophia.inria.fr>
Here binding C-. is too dangerous, as it is too close to undo, C-/,
and it will subtly change words not on the screen, far up in the document, with the only
evidence being some choices in the modeline. Easy to overlook when doing
a lot of undos and ones finger slips a little.
Also well gosh if flyspell-use-meta-tab is already true by default, so
isn't one key enough. Why do you have to bind two keys to the same thing?
(defvar flyspell-mode-map
(let ((map (make-sparse-keymap)))
(if flyspell-use-meta-tab
(define-key map "\M-\t" 'flyspell-auto-correct-word))
(define-key map flyspell-auto-correct-binding 'flyspell-auto-correct-previous-word)
(define-key map [(control ?\,)] 'flyspell-goto-next-error)
(define-key map [(control ?\.)] 'flyspell-auto-correct-word)
(define-key map [?\C-c ?$] 'flyspell-correct-word-before-point)
map)
"Minor mode keymap for Flyspell mode--for the whole buffer.")
OK in .emacs I will do
(eval-after-load "flyspell-mode"
'(progn ;too close to C-/ (undo) and already on ESC TAB:
(define-key flyspell-mode-map [(control ?\.)] [])))
Also we see
;; Some user variables control the behavior of flyspell. They are
;; those defined under the `User variables' comment.
but below is
;;*---------------------------------------------------------------------*/
;;* User configuration ... */
;;*---------------------------------------------------------------------*/
not 'User variables'. So change one or the other. emacs-version "25.1.1".
next reply other threads:[~2016-12-11 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 18:23 積丹尼 Dan Jacobson [this message]
2019-10-14 19:59 ` bug#25175: flyspell-mode: stay off of C-c . best Lars Ingebrigtsen
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=87bmwi9vfj.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=25175@debbugs.gnu.org \
--cc=manuel.serrano@sophia.inria.fr \
/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).