From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 19267@debbugs.gnu.org, Tassilo Horn <tsdh@gnu.org>
Subject: bug#19267: 25.0.50; Enhance cycle-spacing with a state where only whitespace after point is deleted
Date: Thu, 12 May 2022 14:16:45 +0200 [thread overview]
Message-ID: <87ee0z3pzm.fsf@gmail.com> (raw)
In-Reply-To: <87lev7ymto.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 12 May 2022 14:09:23 +0200")
>>>>> On Thu, 12 May 2022 14:09:23 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> Tassilo Horn <tsdh@gnu.org> writes:
>> I'd say just create a cycle-spacing-actions defcustom and use that in
>> the existing cycle-spacing instead of the hard-coded sequence. And bind
>> M-SPC to cycle-spacing by default because it's simply superior (a
>> super-set) of just-one-space.
Lars> It's two actions, and one which can't be done via Customize...
Which is why we should change the default binding of M-SPC to
cycle-spacing. I know some people will complain, but all they have to
do is not type M-SPC twice. In short: Iʼm with Tassilo, letʼs be
disruptive.
Robert
--
next prev parent reply other threads:[~2022-05-12 12:16 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 8:06 bug#19267: 25.0.50; Enhance cycle-spacing with a state where only whitespace after point is deleted Tassilo Horn
2022-05-12 2:16 ` Lars Ingebrigtsen
2022-05-12 4:53 ` Tassilo Horn
2022-05-12 11:45 ` Lars Ingebrigtsen
2022-05-12 11:56 ` Tassilo Horn
2022-05-12 12:09 ` Lars Ingebrigtsen
2022-05-12 12:16 ` Robert Pluim [this message]
2022-05-12 12:21 ` Lars Ingebrigtsen
2022-05-12 14:45 ` Tassilo Horn
2022-05-13 8:50 ` Tassilo Horn
2022-05-13 13:33 ` Robert Pluim
2022-05-13 18:48 ` Tassilo Horn
2022-05-13 12:19 ` Lars Ingebrigtsen
2022-05-13 13:36 ` Robert Pluim
2022-05-13 13:39 ` Lars Ingebrigtsen
2022-05-13 19:01 ` Tassilo Horn
2022-05-13 19:26 ` Lars Ingebrigtsen
2022-05-13 21:11 ` Tassilo Horn
2022-05-14 2:24 ` Lars Ingebrigtsen
2022-05-14 6:54 ` Tassilo Horn
2022-05-14 15:51 ` Lars Ingebrigtsen
2022-05-15 9:02 ` Tassilo Horn
2022-05-15 12:27 ` Lars Ingebrigtsen
2022-05-15 19:04 ` Tassilo Horn
2022-05-16 1:05 ` Lars Ingebrigtsen
2022-05-16 8:05 ` Tassilo Horn
2022-05-16 12:19 ` Lars Ingebrigtsen
2022-05-16 12:28 ` Tassilo Horn
2022-05-16 12:32 ` Lars Ingebrigtsen
2022-05-16 13:04 ` Tassilo Horn
2022-05-17 15:42 ` Robert Pluim
2022-05-17 15:55 ` Robert Pluim
2022-05-17 15:57 ` Tassilo Horn
2022-05-17 16:12 ` Robert Pluim
2022-05-16 7:33 ` Robert Pluim
2022-05-12 12:20 ` Tassilo Horn
2022-05-12 5:40 ` Eli Zaretskii
2022-05-12 5:46 ` Tassilo Horn
2022-05-12 8:25 ` Robert Pluim
2022-05-12 8:29 ` Eli Zaretskii
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=87ee0z3pzm.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=19267@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=tsdh@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.
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).