bug#19267: 25.0.50; Enhance cycle-spacing with a state where only whitespace after point is deleted

[Robert Pluim <rpluim@gmail.com>]

>>>>> On Sun, 15 May 2022 21:04:05 +0200, Tassilo Horn <tsdh@gnu.org> said:

    Tassilo> Lars Ingebrigtsen <larsi@gnus.org> writes:
    >>> However, that has one major drawback: now you cannot delete all
    >>> whitespace including newlines before/after point because that would
    >>> require you to provide (zerop N) and (< N 0) at the same time.
    >> 
    >> Isn't `M--' the magic incantation for deleting newlines for these
    >> commands?  `M--' isn't the same as `C-u -1'...

    Tassilo> Indeed, they are not the same but their prefix-numeric-value is the
    Tassilo> same.  So now I've made it so that the prefix arg `-' has the general
    Tassilo> meaning of including newlines but it's up to the action to decide how it
    Tassilo> is interpreted as a number, e.g., just-one-space treats it as -1 as
    Tassilo> usual but delete-space-before/after treat it as zero.

    Tassilo> New patch attached.  Some final nitpicking please.  And some thoughts
    Tassilo> about default value for cycle-spacing-actions.  Maybe only

    Tassilo>   (just-one-space delete-all-space restore)

    Tassilo> which would mimic the current cycle-spacing behavior?

Yes, I think thatʼs best. Having five options in the default value
seems a bit too much.

Thanks for working on this.

Robert
--