all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Robert Pluim <rpluim@gmail.com>, 19267@debbugs.gnu.org
Subject: bug#19267: 25.0.50; Enhance cycle-spacing with a state where only whitespace after point is deleted
Date: Mon, 16 May 2022 14:28:29 +0200	[thread overview]
Message-ID: <87y1z1acde.fsf@gnu.org> (raw)
In-Reply-To: <87k0alfz59.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

Hi Lars,

>> It's pushed.  And obviously I've seen that I've forgotten the
>> "perform action as if M-- was given" modifier in the defcustom
>> afterwards which is now also added in another commit.
>
> Thanks; works great.  I now have
>
> (setq cycle-spacing-actions '((just-one-space -) delete-all-space restore))
>
> which makes `M-SPC' do exactly what I want.

Perfect!

> With "emacs -Q', though, and:
>
> `C-u M-SPC'
>
> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p (4))
>   cycle-spacing((4))
>   funcall-interactively(cycle-spacing (4))
>   call-interactively(cycle-spacing nil nil)
>   command-execute(cycle-spacing)
>
> `C-u 4 M-SPC' works fine.

Ah, yes, (repeated) C-us with no number hasn't been handled properly.
I've just pushed a change fixing that.

Bye,
Tassilo





  reply	other threads:[~2022-05-16 12:28 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y1z1acde.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=19267@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=rpluim@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.