GNU bug report logs - #66386
28.2; RFE: Provide global key bindings for increasing/decreasing numbers at point

Previous Next

To reply to this bug, email your comments to 66386 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Tim Landscheidt <tim <at> tim-landscheidt.de>
To: bug-gnu-emacs <at> gnu.org
Subject: 28.2; RFE: Provide global key bindings for increasing/decreasing
 numbers at point
Date: Sat, 07 Oct 2023 10:57:34 +0000

Package: emacs
Version: 28.2
Severity: wishlist

When entering a number with read-number or skeleton-read or
just editing text, it can be very useful to increase/de-
crease the number at point.  For Org, Emacs ships the func-
tions org-increase-number-at-point and
org-decrease-number-at-point for this purpose and binds them
to C-M-S-<right> and C-M-S-<left>, respectively, in
org-mode-map.

It would be nice if these functions or some variant could be
bound to global key bindings that are active by default in
all modes.

Message #8 received at 66386 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Tim Landscheidt <tim <at> tim-landscheidt.de>
Cc: 66386 <at> debbugs.gnu.org
Subject: Re: bug#66386: 28.2;
 RFE: Provide global key bindings for increasing/decreasing numbers at
 point
Date: Sat, 07 Oct 2023 14:03:55 +0300

> From: Tim Landscheidt <tim <at> tim-landscheidt.de>
> Date: Sat, 07 Oct 2023 10:57:34 +0000
> 
> Package: emacs
> Version: 28.2
> Severity: wishlist
> 
> When entering a number with read-number or skeleton-read or
> just editing text, it can be very useful to increase/de-
> crease the number at point.  For Org, Emacs ships the func-
> tions org-increase-number-at-point and
> org-decrease-number-at-point for this purpose and binds them
> to C-M-S-<right> and C-M-S-<left>, respectively, in
> org-mode-map.
> 
> It would be nice if these functions or some variant could be
> bound to global key bindings that are active by default in
> all modes.

These are trivial functions that everyone who needs them can easily
code, and bind to any keys they want.  For example, I'd prefer to bind
them to S-<kp-add> and S-<kp-subtract> instead.  Is it really
justified to have these in Emacs by default, let alone usurp some
global key bindings for them?  Why not keep them available only in
modes where they are really needed?

Message #11 received at 66386 <at> debbugs.gnu.org (full text, mbox):

From: Tim Landscheidt <tim <at> tim-landscheidt.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 66386 <at> debbugs.gnu.org
Subject: Re: bug#66386: 28.2; RFE: Provide global key bindings for
 increasing/decreasing numbers at point
Date: Sat, 07 Oct 2023 14:28:24 +0000

Eli Zaretskii <eliz <at> gnu.org> wrote:

>> When entering a number with read-number or skeleton-read or
>> just editing text, it can be very useful to increase/de-
>> crease the number at point.  For Org, Emacs ships the func-
>> tions org-increase-number-at-point and
>> org-decrease-number-at-point for this purpose and binds them
>> to C-M-S-<right> and C-M-S-<left>, respectively, in
>> org-mode-map.

>> It would be nice if these functions or some variant could be
>> bound to global key bindings that are active by default in
>> all modes.

> These are trivial functions that everyone who needs them can easily
> code, and bind to any keys they want.  For example, I'd prefer to bind
> them to S-<kp-add> and S-<kp-subtract> instead.  Is it really
> justified to have these in Emacs by default, let alone usurp some
> global key bindings for them?  Why not keep them available only in
> modes where they are really needed?

For me, part of the charm of Emacs is that some concepts are
"universal".  For example, forward-sexp (C-M-<right>) will
move forward one "balanced expression" in an Emacs Lisp buf-
fer, and it will do so in a Python buffer as well.  I do not
have to learn different key bindings (or look them up) be-
cause a "balanced expression" is something that exists in
many/most modes.

I probably would have missed that the Python mode had such a
function if I had not known it from Emacs Lisp mode and just
intuitively used it.  I would neither have written and main-
tained some code to add this functionality just for Python
mode.

The same reasoning applies to the concept of "numbers": They
exist in many/most modes, writing personal code is a dupli-
cation of effort, and I had never realized that org-mode
provides such functions because I have never had the need to
increase/decrease numbers in Org buffers, but instead at
prompts and in (other) programming languages.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.