unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Tassilo Horn <tsdh@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 19267@debbugs.gnu.org
Subject: bug#19267: 25.0.50; Enhance cycle-spacing with a state where only whitespace after point is deleted
Date: Tue, 17 May 2022 17:55:36 +0200	[thread overview]
Message-ID: <87y1z017d3.fsf@gmail.com> (raw)
In-Reply-To: <8735h82mjz.fsf@gmail.com> (Robert Pluim's message of "Tue, 17 May 2022 17:42:08 +0200")

>>>>> On Tue, 17 May 2022 17:42:08 +0200, Robert Pluim <rpluim@gmail.com> said:

>>>>> On Mon, 16 May 2022 15:04:20 +0200, Tassilo Horn <tsdh@gnu.org> said:
    Tassilo> Lars Ingebrigtsen <larsi@gnus.org> writes:
    >>>> Ah, yes, (repeated) C-us with no number hasn't been handled properly.
    >>>> I've just pushed a change fixing that.
    >>> 
    >>> Thanks; I can confirm that this fixes that issue, too, so `M-SPC' is
    >>> now officially perfect.  😀

    Tassilo> Phew! 😅
    Tassilo> Then I'm closing this issue.

    Robert> There was a small mistake in the defcustom of 'cycle-spacing-actions',
    Robert> but Iʼve just fixed that with 45ec56f5bd

Btw, the reason I noticed this is because I wanted to use
'(delete-all-space -1), meaning delete all space including newlines,
but then leave one space, but I guess thatʼs not supported, so Iʼll
just have to use a function which does '(insert " ") afterwards.

Robert
-- 





  reply	other threads:[~2022-05-17 15:55 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
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 [this message]
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=87y1z017d3.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).