From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 64185@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
me@eshelyaron.com, zkanfer@gmail.com
Subject: bug#64185: proposal for new function: copy-line
Date: Sun, 25 Jun 2023 21:46:55 +0200 [thread overview]
Message-ID: <62289D18-9F94-47E5-8D2B-DBDB35C2E2DB@gmail.com> (raw)
In-Reply-To: <86a5wnmu3x.fsf@mail.linkov.net>
25 juni 2023 kl. 19.24 skrev Juri Linkov <juri@linkov.net>:
> I don't see from where we can get such assumption - e.g. extending the region
> to the copied text also makes sense.
No, it's actually a firm requirement. Extending the region would only allow making exponentially more copies which is useless in practice. Try it yourself and you'll see.
> When the users will request a setting for columns, then we could
> add a new option e.g. `duplicate-dwim-final-column`.
Request submitted then!
>> If we use separate settings they should naturally work the same way,
>> or users will wonder who is running the asylum.
>
> It would be crazy to mix apples and oranges. `duplicate-line-final-line`
> should be applied only to `duplicate-line`.
No, what I meant is that it would make little sense to use different types and values for settings affecting the exact same operation on different pieces of text.
> And if the users need to
> do the same with regions, then a separate option could be added
> e.g. `duplicate-dwim-final-region`.
How about we, for a change, attempt this thing called design, instead of the customary Emacs piecemeal hodgepodge?
> (Not sure why now one example uses boring "abcde"
> instead of the overall style with "foo", "bar", "zot").
Yes there are oodles of those so I just fix the ones in examples I'm changing for other reasons.
Maybe we should take a day off and do them all in one batch.
next prev parent reply other threads:[~2023-06-25 19:46 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
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 [this message]
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
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=62289D18-9F94-47E5-8D2B-DBDB35C2E2DB@gmail.com \
--to=mattias.engdegard@gmail.com \
--cc=64185@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--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 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).