all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Why does C-M-o `split-line' leave trailing space on the old line?
Date: Fri, 17 Nov 2023 18:59:39 +0000	[thread overview]
Message-ID: <ZVe4G0NB5aP4R1Qb@ACM> (raw)
In-Reply-To: <83leawns39.fsf@gnu.org>

Hello, Eli.

On Fri, Nov 17, 2023 at 20:38:02 +0200, Eli Zaretskii wrote:
> > Date: Fri, 17 Nov 2023 17:40:27 +0000
> > From: Alan Mackenzie <acm@muc.de>

> > Hello, Emacs.

> > C-M-o, on something like:

> >      foo bar baz
> >             ^
> > 	  point

> > will split the line into

> >      foo bar
> >              baz

> > , but will leave a trailing space on the first line.  This is in
> > accordance with its documentation in emacs.info, but this peculiarity
> > isn't mentioned in the doc string.

> > I find this trailing space irritating, as I frequently have to remove it
> > by hand.  What is the motivation for this trailing space

> It lets you keep typing right after that.

Ah, is that it?  It seems strange indeed to have a command which does two
disjoint things (first move point then split the line) rather than just
splitting the line at point.

I typically don't want to type further on the old line after C-M-o.  If I
did, I would expect to type the space myself, or alternatively first move
point to after the space before typing C-M-o.

Maybe I should make my own private version of split-line.

-- 
Alan Mackenzie (Nuremberg, Germany).



      reply	other threads:[~2023-11-17 18:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 17:40 Why does C-M-o `split-line' leave trailing space on the old line? Alan Mackenzie
2023-11-17 18:38 ` Eli Zaretskii
2023-11-17 18:59   ` Alan Mackenzie [this message]

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=ZVe4G0NB5aP4R1Qb@ACM \
    --to=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 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.