From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46621@debbugs.gnu.org, larsi@gnus.org,
Juri Linkov <juri@linkov.net>,
rms@gnu.org, mardani29@yahoo.es
Subject: bug#46621: Copy line
Date: Mon, 22 Feb 2021 21:51:40 +0100 [thread overview]
Message-ID: <87v9ajsu5f.fsf@rub.de> (raw)
In-Reply-To: <83eeh8w1jz.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 22 Feb 2021 17:43:28 +0200")
On Mon, 22 Feb 2021 17:43:28 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
> Bottom line, if we want to consider this command, we should somehow
> come up with the relevant use cases, and then weigh them against the
> added complexity and maintenance costs. I therefore urge people who
> think they know these details to please speak up and contribute to
> this discussion.
I frequently use the following command (bound to `C-c l'), which suits
my needs better than the proposed command would or dabbrev-expand does:
(defun srb-select-line ()
"Select line at point and copy to kill ring."
(interactive)
(copy-region-as-kill (line-beginning-position) (line-end-position)))
A common use case for me is copying somewhat complex shell commands I
keep stored in a file; they are stored as one liners to be easy to copy.
I don't want them to be immediately yanked into the file and for these
cases I don't need the feature of multiple copies via a prefix argument
(though in some documents I often do want multiple copies of a single
line, but usually at different parts of the document, so then just
yanking at the different locations is better than moving the copies).
Steve Berman
next prev parent reply other threads:[~2021-02-22 20:51 UTC|newest]
Thread overview: 117+ 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
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 [this message]
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
[not found] <87a6aal3l5.fsf@simenheg@gmail.com>
2022-06-18 12:56 ` Lars Ingebrigtsen
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=87v9ajsu5f.fsf@rub.de \
--to=stephen.berman@gmx.net \
--cc=46621@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=mardani29@yahoo.es \
--cc=rms@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.