From: Drew Adams <drew.adams@oracle.com>
To: Dmitry Gutov <dgutov@yandex.ru>,
Howard Melman <hmelman@gmail.com>,
"46621@debbugs.gnu.org" <46621@debbugs.gnu.org>
Subject: bug#46621: [External] : bug#46621: Copy line
Date: Tue, 28 Jun 2022 14:28:44 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488937D059B920B3CD5025CF3B89@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <a163f596-36c8-b064-440d-d42c697158f3@yandex.ru>
> > > In emacs terminology it's not copying the text
> > > (like to the kill-ring) but inserting or yanking
> > > it into the buffer (just not from the kill-ring
> > > but from the previous line). It seems closer in
> > > concept to how dabbrev and hippie use the term
> > > "expand".
This is important, IMO.
The name is awful - not helpful.
> > Why on earth is this called `copy-from-above-command'?
> >
> > "-command"?
> >
> > Maybe it would help to add a more discoverable alias?
>
> Both good points.
The command inserts chars from the previous line at
point. By default it inserts all of the text of the
previous line, starting just above point.
Can we please rename this poorly named command?
E.g. defalias a new name and deprecate the old one.
Do I need to create a separate bug / enhancement
request for this, or could it be taken care of in
this thread?
Maybe a name such as `insert-from-previous-line'?
___
`yank' isn't appropriate in the name, because the
`kill-ring' isn't involved.
`insert' is pretty good, though it might not be
super helpful for discovery.
`duplicate' could maybe be used in the name, but
I'm not sure how. The name shouldn't include both
`duplicate' and `line', as that would be misleading.
next prev parent reply other threads:[~2022-06-28 14:28 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 19:07 bug#46621: Copy line Juri Linkov
2021-02-18 19:30 ` bug#46621: [External] : " Drew Adams
2021-02-20 6:58 ` Richard Stallman
2021-02-19 13:09 ` Lars Ingebrigtsen
2021-02-19 20:27 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-20 6:54 ` Eli Zaretskii
2021-02-20 13:05 ` Lars Ingebrigtsen
2021-02-20 13:12 ` Eli Zaretskii
2021-02-20 13:18 ` Lars Ingebrigtsen
2021-02-20 14:15 ` Eli Zaretskii
2021-02-20 14:35 ` Dmitry Gutov
2021-02-20 13:03 ` Lars Ingebrigtsen
2021-02-20 18:28 ` Juri Linkov
2021-02-21 6:16 ` Richard Stallman
2021-02-21 6:21 ` Richard Stallman
2021-02-21 8:54 ` Juri Linkov
2021-02-21 10:41 ` Eli Zaretskii
2021-02-21 13:12 ` Lars Ingebrigtsen
2021-02-21 13:19 ` Eli Zaretskii
2021-02-21 15:51 ` Lars Ingebrigtsen
2021-02-21 17:06 ` Eli Zaretskii
2021-02-21 17:39 ` Lars Ingebrigtsen
2021-02-21 18:00 ` bug#46621: [External] : " Drew Adams
2021-02-21 17:45 ` Drew Adams
2021-02-22 6:22 ` Richard Stallman
2021-02-21 17:41 ` bug#46621: [External] : " Drew Adams
2021-02-21 20:37 ` Juri Linkov
2021-02-21 22:06 ` bug#46621: [External] : " Drew Adams
2021-02-22 15:45 ` Eli Zaretskii
2021-02-21 23:04 ` Howard Melman
2021-02-22 6:23 ` Richard Stallman
2021-02-22 9:07 ` Juri Linkov
2021-02-22 15:43 ` Eli Zaretskii
2021-02-22 16:28 ` Helmut Eller
2021-02-22 16:58 ` Andreas Schwab
2021-02-22 18:32 ` Helmut Eller
2021-02-22 19:41 ` Howard Melman
2021-02-22 19:46 ` bug#46621: [External] : " Drew Adams
2021-02-23 19:29 ` Dmitry Gutov
2022-06-28 14:28 ` Drew Adams [this message]
2021-02-22 17:08 ` Eli Zaretskii
2021-02-22 18:42 ` Helmut Eller
2021-02-22 17:04 ` Gregory Heytings
2021-02-22 17:16 ` Eli Zaretskii
2021-02-22 17:54 ` Gregory Heytings
2021-02-22 20:51 ` Stephen Berman
2021-02-21 13:13 ` Lars Ingebrigtsen
2022-06-17 17:34 ` Lars Ingebrigtsen
2022-06-18 9:32 ` Simen Heggestøyl
2022-06-20 18:28 ` Richard Stallman
2022-06-18 18:02 ` Mattias Engdegård
2022-06-18 18:09 ` Eli Zaretskii
2022-06-19 15:02 ` Mattias Engdegård
2022-07-03 17:21 ` Mattias Engdegård
2022-07-04 3:24 ` Pankaj Jangid
2022-07-05 16:02 ` Mattias Engdegård
2022-07-05 16:52 ` Lars Ingebrigtsen
2022-07-05 20:19 ` Mattias Engdegård
2022-06-19 11:43 ` Lars Ingebrigtsen
2022-06-19 15:20 ` Mattias Engdegård
2022-06-19 15:22 ` Lars Ingebrigtsen
2022-06-20 9:26 ` Mattias Engdegård
2022-06-21 10:35 ` Lars Ingebrigtsen
2022-06-21 11:13 ` Mattias Engdegård
2022-06-22 4:11 ` Lars Ingebrigtsen
2022-06-21 17:41 ` Juri Linkov
2022-06-22 4:07 ` Lars Ingebrigtsen
2022-06-22 7:28 ` Juri Linkov
2022-06-22 7:54 ` Lars Ingebrigtsen
2022-06-22 17:21 ` Pankaj Jangid
2022-06-22 18:24 ` Juri Linkov
2022-06-22 18:45 ` Lars Ingebrigtsen
2022-06-23 7:49 ` Lars Ingebrigtsen
2022-06-23 8:08 ` Pankaj Jangid
2022-06-23 8:17 ` Andreas Schwab
2022-06-23 9:05 ` Lars Ingebrigtsen
2022-07-06 17:34 ` Juri Linkov
2022-07-07 7:58 ` Lars Ingebrigtsen
2022-07-07 16:45 ` Juri Linkov
2022-07-07 18:03 ` Lars Ingebrigtsen
2022-07-07 18:20 ` Juri Linkov
2022-07-07 18:24 ` Lars Ingebrigtsen
2022-07-08 17:10 ` Juri Linkov
2022-07-10 12:57 ` Lars Ingebrigtsen
2022-07-14 17:16 ` Juri Linkov
2022-07-14 17:47 ` Andreas Schwab
2022-07-14 19:30 ` Juri Linkov
2022-06-23 9:22 ` Robert Pluim
2022-06-23 11:16 ` Pankaj Jangid
2022-06-23 11:34 ` Lars Ingebrigtsen
2022-06-23 9:04 ` Lars Ingebrigtsen
2022-06-23 11:12 ` Pankaj Jangid
2022-06-23 15:10 ` Mattias Engdegård
2022-06-23 15:20 ` Lars Ingebrigtsen
2022-06-25 16:35 ` Mattias Engdegård
2022-06-23 17:35 ` Juri Linkov
2022-06-23 17:49 ` Drew Adams
2022-06-25 16:51 ` Mattias Engdegård
2022-06-25 17:48 ` Drew Adams
2022-06-27 19:40 ` Juri Linkov
2022-06-28 8:41 ` Mattias Engdegård
2022-06-28 12:10 ` Helmut Eller
2022-06-22 14:10 ` Drew Adams
2022-06-22 17:27 ` Pankaj Jangid
2022-06-22 20:44 ` Sean Whitton
2022-06-22 20:50 ` Drew Adams
2022-06-23 15:47 ` Helmut Eller
2022-06-23 16:07 ` Eli Zaretskii
2022-06-23 17:46 ` Drew Adams
2022-06-23 5:47 ` Eli Zaretskii
2022-06-23 17:00 ` Sean Whitton
2022-06-23 17:37 ` Sean Whitton
2022-06-23 18:31 ` Eli Zaretskii
2022-06-30 16:31 ` Sean Whitton
2022-07-01 9:27 ` Lars Ingebrigtsen
2022-07-01 16:34 ` Sean Whitton
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=SJ0PR10MB5488937D059B920B3CD5025CF3B89@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=46621@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=hmelman@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).