From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: 64185@debbugs.gnu.org, me@eshelyaron.com, zkanfer@gmail.com,
juri@linkov.net
Subject: bug#64185: proposal for new function: copy-line
Date: Fri, 23 Jun 2023 14:07:15 +0300 [thread overview]
Message-ID: <83mt0q1lp8.fsf@gnu.org> (raw)
In-Reply-To: <098B9138-4BC1-481B-A1A3-19B935787858@gmail.com> (message from Mattias Engdegård on Fri, 23 Jun 2023 12:50:52 +0200)
> From: Mattias Engdegård <mattias.engdegard@gmail.com>
> Date: Fri, 23 Jun 2023 12:50:52 +0200
> Cc: juri@linkov.net,
> 64185@debbugs.gnu.org,
> me@eshelyaron.com,
> zkanfer@gmail.com
>
> 23 juni 2023 kl. 12.28 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > This is a new feature in Emacs 29, so adding customization
> > opportunities to it that allow fine control of its behavior is fine at
> > this stage. Of course, if the proposal is controversial, we shouldn't
> > rush. My impression till now was that it wasn't controversial. If
> > the only issue is better documentation and/or whether the value should
> > be a number or a symbol, then I see no problem with installing this on
> > the release branch.
>
> The new setting would be quite incomplete if it doesn't apply to the
> more general and useful duplicate-dwim as well.
It is? why? The difference between these two commands is that
duplicate-dwim is sensitive to the active region, but in that case how
is it useful to talk about lines, given that region could be a part of
a line or several lines plus a part of the first and the last one?
So it sounds to me that we could easily leave duplicate-dwim as it is
now, i.e. disregard this option in that command.
Why isn't that "good enough" for Emacs 29?
next prev parent reply other threads:[~2023-06-23 11:07 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 5:07 bug#64185: proposal for new function: copy-line Zachary Kanfer
2023-06-20 6:15 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-20 11:44 ` Eli Zaretskii
2023-06-22 3:33 ` Zachary Kanfer
2023-06-22 5:08 ` Eli Zaretskii
2023-06-22 6:57 ` Juri Linkov
2023-06-22 16:25 ` Eli Zaretskii
2023-06-22 17:27 ` Juri Linkov
2023-06-22 17:45 ` Eli Zaretskii
2023-06-22 18:13 ` Drew Adams
2023-06-22 18:29 ` Juri Linkov
2023-06-22 18:42 ` Drew Adams
2023-06-22 18:52 ` Juri Linkov
2023-06-22 19:05 ` Drew Adams
2023-06-22 18:17 ` Juri Linkov
2023-06-22 18:30 ` Eli Zaretskii
2023-06-23 5:46 ` Zachary Kanfer
2023-06-23 5:56 ` Eli Zaretskii
2023-06-23 7:08 ` Robert Pluim
2023-06-23 7:19 ` Eli Zaretskii
2023-06-23 9:01 ` Robert Pluim
2023-06-23 16:46 ` Juri Linkov
2023-06-23 9:07 ` Mattias Engdegård
2023-06-23 10:28 ` Eli Zaretskii
2023-06-23 10:50 ` Mattias Engdegård
2023-06-23 11:07 ` Eli Zaretskii [this message]
2023-06-23 16:45 ` Juri Linkov
2023-06-24 11:29 ` Mattias Engdegård
2023-06-25 17:24 ` Juri Linkov
2023-06-25 19:46 ` Mattias Engdegård
2023-06-26 17:37 ` Juri Linkov
2023-06-26 17:56 ` Drew Adams
2023-06-26 18:35 ` Eli Zaretskii
2023-06-27 15:35 ` Mattias Engdegård
2023-06-27 18:28 ` Juri Linkov
2023-06-28 13:17 ` Mattias Engdegård
2023-06-28 17:42 ` Juri Linkov
2023-06-28 18:37 ` Eli Zaretskii
2023-06-29 7:13 ` Juri Linkov
2023-06-30 17:13 ` Mattias Engdegård
2023-06-30 19:03 ` Eli Zaretskii
2023-07-01 8:45 ` Mattias Engdegård
2023-07-01 9:53 ` Eli Zaretskii
2023-07-01 10:07 ` Mattias Engdegård
2023-07-01 10:22 ` Eli Zaretskii
2023-07-01 10:33 ` Mattias Engdegård
2023-06-25 3:45 ` Zachary Kanfer
2023-06-25 17:19 ` Juri Linkov
[not found] ` <CAFXT+RPRwpZgfPKsyz22+-v6vy7RJwyuwaOEkmunc2MAMSoqZA@mail.gmail.com>
[not found] ` <86h6qut970.fsf@mail.linkov.net>
2023-06-26 19:18 ` Zachary Kanfer
2023-06-27 2:25 ` Eli Zaretskii
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=83mt0q1lp8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64185@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=mattias.engdegard@gmail.com \
--cc=me@eshelyaron.com \
--cc=zkanfer@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 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.