From: Jean Louis <bugs@gnu.support>
To: "Johan Myréen" <johan.myreen@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: C-o (was: Proposal: new default bindings for winner and windmove)
Date: Tue, 13 Aug 2024 11:54:21 +0300 [thread overview]
Message-ID: <ZrsfPWRg0tY324PB@lco2> (raw)
In-Reply-To: <CA+TD5hjLFDyuskJYH4rUqqnezAMDtFv16SYN98Wd5CFLQmtkSg@mail.gmail.com>
* Johan Myréen <johan.myreen@gmail.com> [2024-07-03 22:33]:
> >
> > I can see someone doing C-o foo bar but I don't see the benefit compared
> > to foo bar RET
>
>
> The benefit is that C-o opens a new blank line to type on, instead of
> prepending what you are writing to the pre-existing text on the line, which
> I find very distracting. Also, I might want to do a quick edit to what I
> have typed so far (maybe to fix a typo before I forget it's there), and
> then return to add new text to the line. If I open a new blank line with
> C-o, I just type C-e to continue typing, but if the line is still stringed
> together with the old line, then finding the correct point is a pita.
>
> Note that the vi editor also has not only one, but two "open line" commands
> "o" and "O", for opening a line below and above the current line,
> respectively.
Just confirming on the older thread, that I am frequently using C-o
and find it very useful as explained abve by Johan.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
✡️🛡️ Proudly standing with Israel, a nation rooted in history and culture. Let's condemn hatred and promote understanding.
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2024-08-13 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 19:32 C-o (was: Proposal: new default bindings for winner and windmove) Johan Myréen
2024-08-13 8:54 ` Jean Louis [this message]
2024-08-13 12:41 ` Emanuel Berg
-- strict thread matches above, loose matches on Subject: below --
2021-08-21 19:10 Proposal: new default bindings for winner and windmove Daniel Colascione
2021-08-22 17:52 ` Stefan Monnier
2024-06-21 19:03 ` Stefan Monnier
2024-06-21 20:39 ` Stefan Kangas
2024-06-26 15:48 ` Stefan Monnier
2024-07-01 1:29 ` Stefan Kangas
2024-07-01 10:07 ` Alan Mackenzie
2024-07-01 11:25 ` Dmitry Gutov
2024-07-01 21:24 ` Alan Mackenzie
2024-07-01 22:07 ` Daniel Colascione
2024-07-02 1:00 ` Po Lu
2024-07-02 3:26 ` C-o (was: Proposal: new default bindings for winner and windmove) Stefan Monnier
2024-07-02 22:31 ` Stefan Kangas
2024-07-03 10:07 ` Per Starbäck
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=ZrsfPWRg0tY324PB@lco2 \
--to=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=johan.myreen@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 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).