From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Juri Linkov <juri@jurta.org>,
"18100@debbugs.gnu.org" <18100@debbugs.gnu.org>
Subject: bug#18100: 24.4.50; Restore simplicity of (put 'self-insert-command 'delete-selection 'kill)
Date: Wed, 11 May 2022 20:09:01 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488CC5F2DCBFABF9D2AC867F3C89@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87k0as6rk7.fsf@gnus.org>
> This was somewhat rewritten in 2015, and there's now a
> delete-selection-uses-region-p. So this would be
> simpler to express now:
> (put 'self-insert-command 'delete-selection
> (lambda () (and (delete-selection-uses-region-p)
> 'kill)))
>
> And I think that's sufficient here, and I'm therefore closing this bug
> report.
Perhaps you didn't read the bug thread.
Or perhaps you did, but decided to ignore it
and reply to something unrelated.
The bug:
___
Maybe so, but that is not at all what the
`delete-selection-mode' doc & comments tell users.
If this is a new requirement/guideline, then
it needs to be documented.
But I wonder why this must now be so. In the past,
a user could just put `kill' as the property. The
code does not seem so clean now.
One of the benefits of the `delsel.el' design ...
is its simplicity for users.
This seems to go against that. Is it really
necessary? Isn't there another way to accomplish
the same thing (whatever that is), so we can
keep the simple and clean design for users?
...
Users should be able to `put' a single,
understandable symbol as the `delete-selection'
property value. They should not need to fiddle
with obscure lambda forms (or symbols whose names
are not simple to understand). Symbol `kill' is
simple - it says that you want the region to be killed.
...
This new bug is about restoring the ability to use
a simple `put' to configure `delete-selection-mode'
behavior for a given command, rather than having to
jump through hoops with incomprehensible lambda forms
in the `put' value.
___
All of that is still relevant. The bug wasn't fixed.
Just another "wont-fix". Please own up to that, here
and elsewhere. This doesn't go in the "fix" column.
It's not "Done". Not at all.
next prev parent reply other threads:[~2022-05-11 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 17:22 bug#18100: 24.4.50; Restore simplicity of (put 'self-insert-command 'delete-selection 'kill) Drew Adams
2022-05-11 15:02 ` Lars Ingebrigtsen
2022-05-11 20:09 ` Drew Adams [this message]
2022-05-12 16:56 ` Juri Linkov
2022-05-12 17:30 ` Drew Adams
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=SJ0PR10MB5488CC5F2DCBFABF9D2AC867F3C89@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=18100@debbugs.gnu.org \
--cc=juri@jurta.org \
--cc=larsi@gnus.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 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).