bug#39630: Mention how to unset keys in Your Init File

bug#39630: Mention how to unset keys in Your Init File

[積丹尼 Dan Jacobson]

49.3.5 Changing Key Bindings Interactively.
       mentions how to set and unset keys.
49.3.6 Rebinding Keys in Your Init File
       mentions how to set keys, but not how to unset keys.
emacs-version "26.3"

bug#39631: Mention how to remove entire keymaps in Your Init File

[積丹尼 Dan Jacobson]

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
(eval-after-load "flyspell-mode"
  '(add-hook
    'flyspell-mode-hook
    (lambda ()
      (setq flyspell-mode-map nil)
      ;;too close to C-/ (undo) and already on ESC TAB:
      ;;(define-key flyspell-mode-map [(control ?\.)] [])
      (define-key flyspell-mode-map (kbd "C-,") (lambda () (interactive))) #<---last time what I was told to try
      (define-key flyspell-mode-map (kbd "C-.") (lambda () (interactive)))
      (define-key flyspell-mode-map [(control ?\,)] (lambda () (interactive)))
      (define-key flyspell-mode-map [(control ?\.)] (lambda () (interactive)))
      (define-key flyspell-mode-map [(control ?\;)] (lambda () (interactive)))
      (global-unset-key [(control ?\,)])
      (global-unset-key [(control ?\.)])
      (global-unset-key [(control ?\;)])
      (setq flyspell-mode-map nil)
      )))
(global-unset-key [(control ?\,)])
(global-unset-key [(control ?\.)])
(global-unset-key [(control ?\;)])
(defvar flyspell-mode-map "")
(add-hook 'flyspell-mode-hook
	  (lambda ()
	    (define-key flyspell-mode-map (kbd "C-M-i")
                    'flyspell-auto-correct-word)))
(setq flyspell-mode-map nil)
(global-set-key (kbd "C-M-i") 'flyspell-auto-correct-word)

Alas nothing will give the user the aforementioned desired result.
Please put examples in
Info 49.3.6 Rebinding Keys in Your Init File
showing how to remove entire keymaps with one line,
and then how to sparsely populate them back. Thanks.

bug#39630: Mention how to unset keys in Your Init File

[Eli Zaretskii]

> From: 積丹尼 Dan Jacobson
>  <jidanni@jidanni.org>
> Date: Sun, 16 Feb 2020 11:28:41 +0800
> 
> 49.3.5 Changing Key Bindings Interactively.
>        mentions how to set and unset keys.
> 49.3.6 Rebinding Keys in Your Init File
>        mentions how to set keys, but not how to unset keys.

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 co0mplement
what is in the user manual.

bug#39631: Mention how to remove entire keymaps in Your Init File

[Eli Zaretskii]

> 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.

bug#39630: Mention how to unset keys in Your Init File

[積丹尼 Dan Jacobson]

Fine. Users can only unset keys interactively.

bug#39631: Mention how to remove entire keymaps in Your Init File

[積丹尼 Dan Jacobson]

Fine. Keymaps can only be added to.

bug#39631: Mention how to remove entire keymaps in Your Init File

[積丹尼 Dan Jacobson]

OK the answer is not in
(info "(eintr) Keymaps")
(info "(elisp) Creating Keymaps")
however possibly in
(info "(elisp) Changing Key Bindings")

bug#39630: Mention how to unset keys in Your Init File

[積丹尼 Dan Jacobson]

I'm just saying that
(info "(emacs) Init Rebinding")
has 16 mentions of global-set-key, and not even one mention of
unsetting.

It also has two mentions of define-key, and not even the define-key
docstring mentions what to do about the lack of a undefine-key function
that the user is perhaps supposed to search for as
(info "(emacs) Init Rebinding")
doesn't have any reverse examples.

bug#39630: Mention how to unset keys in Your Init File

[Stefan Kangas]

close 39630
tags 39630 + wontfix notabug
thanks

Eli Zaretskii <eliz@gnu.org> writes:

>> From: 積丹尼 Dan Jacobson
>>  <jidanni@jidanni.org>
>> Date: Sun, 16 Feb 2020 11:28:41 +0800
>> 
>> 49.3.5 Changing Key Bindings Interactively.
>>        mentions how to set and unset keys.
>> 49.3.6 Rebinding Keys in Your Init File
>>        mentions how to set keys, but not how to unset keys.
>
> 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 co0mplement
> what is in the user manual.

I agree.  Since no one besides the OP has expressed a different
opinion within two weeks, I'm closing this bug now.

Best regards,
Stefan Kangas

bug#39631: Mention how to remove entire keymaps in Your Init File

[Stefan Kangas]

tags 39631 + wontfix notabug
close 39631
thanks

Eli Zaretskii <eliz@gnu.org> writes:

>> 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.

I agree.  Since no one besides the OP has expressed a different
opinion within two weeks, I'm closing this bug now.

Best regards,
Stefan Kangas

bug#39631: Actually 39802 solves the need for 39630 and 39631

[積丹尼 Dan Jacobson]

Actually 39802 solves the need for 39630 and 39631.

bug#39630: Mention how to unset keys in Your Init File

[Noam Postavsky]

tags 39630 - notabug wontfix
forcemerge 39802 39630
quit

Stefan Kangas <stefan@marxist.se> writes:

>> 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 co0mplement
>> what is in the user manual.
>
> I agree.  Since no one besides the OP has expressed a different
> opinion within two weeks, I'm closing this bug now.

積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:

> Actually 39802 solves the need for 39630 and 39631.

I don't know about 39631, but 39630 is clearly the same as 39802 (I did
have a feeling of familiarity when I initially read that one), so it
doesn't make sense to mark it as wontfix when we are actually fixing it.

bug#39631: Zapping a whole keymap

[積丹尼 Dan Jacobson]

NP> I don't know about 39631

OK, I suppose to solve 39631 somebody could use the lisp equivalent of
for(all the keys present in a given keymap){use the method of 39802 to unbind it}

So maybe document that in some elisp manual or something, mentioning
that maybe there is no way to zap the whole keymap with one line of lisp(?).

bug#39802: bug#39630: Mention how to unset keys in Your Init File

[Stefan Kangas]

Noam Postavsky <npostavs@gmail.com> writes:

> I don't know about 39631, but 39630 is clearly the same as 39802 (I did
> have a feeling of familiarity when I initially read that one), so it
> doesn't make sense to mark it as wontfix when we are actually fixing it.

Thanks.  I had missed the ongoing work in Bug#39802.

Best regards,
Stefan Kangas