From: Marcin Borkowski <mbork@mbork.pl>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Keybinding to transpose current line with next line
Date: Wed, 23 Sep 2020 10:09:49 +0200 [thread overview]
Message-ID: <874knoap82.fsf@mbork.pl> (raw)
In-Reply-To: <87blhx2ihm.fsf@ebih.ebihd>
On 2020-09-23, at 07:02, Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> Yuri Khan wrote:
>
>> This might be good for you
>
> ...
>
>> but org-drag-line-* have a couple advantages over
>> this:
>>
>> * They do not pollute the kill ring.
>
> OK, so use `let', `thing-at-point' (with 'line) and
> `insert' instead.
>
>> * As you drag the line, point stays on the same
>> character where you started.
>
> If you want to edit the line, why start with moving
> it? It is more likely you wish to edit the
> other line.
Why? Imagine working on a book, and in the file, every sentence has its
own line. You may want to move some sentence and then reword it
(e.g., change "above" to "below" etc.).
And a similar case can be made for code, JSON, whatever.
Best,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2020-09-23 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 14:31 Keybinding to transpose current line with next line Christopher Dimech
2020-09-22 14:53 ` Yuri Khan
2020-09-22 20:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-23 4:29 ` Yuri Khan
2020-09-23 5:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-23 8:09 ` Marcin Borkowski [this message]
2020-09-23 22:48 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-23 23:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-23 23:32 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-23 23:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-22 19:39 ` Francis Belliveau
2020-09-22 19:55 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=874knoap82.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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.
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).