From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: 19267@debbugs.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 04:16:06 +0200 [thread overview]
Message-ID: <874k1v3389.fsf@gnus.org> (raw)
In-Reply-To: <87lhmnon3l.fsf@thinkpad-t440p.tsdh.org> (Tassilo Horn's message of "Thu, 04 Dec 2014 09:06:38 +0100")
Tassilo Horn <tsdh@gnu.org> writes:
> I like the new `cycle-spacing' command but I frequently would like to
> have an additional space where only the whitespace after point is
> deleted. That'd be useful when manually formatting text (code) where
> auto-indentation isn't available. My prime use-case is laying out
> example code snippets in comments and docstrings which I copied & pasted
> from somewhere else. E.g., I start with a docstring
>
> "Example:
>
> (let [x :something]
> | (foo x)
> (bar x))"
>
> where | is the position of point. In that case, I'd like if M-SPC would
> change the text to
>
> "Example:
>
> (let [x :something]
> |(foo x)
> (bar x))"
>
> instead of
>
> "Example:
>
> (let [x :something]
> |(foo x)
> (bar x))"
>
> i.e., it first M-SPC only deletes whitespace after point but not before.
> I don't really care if that's the first state (although that would be
> plausible, i.e., states are cycled from more space to less spaces), but
> at least it should be a reachable state.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
I think that sounds like a good feature -- we don't have any other
commands for "delete all whitespace after point", do we?
We could implement this as a new third state for `cycle-spacing', and
move the "restore" to the fourth state. Does anybody think that will be
annoying for people?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-12 2: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 [this message]
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
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=874k1v3389.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=19267@debbugs.gnu.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).