From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: RE: Updated proposal for DEL to delete active region
Date: Sat, 22 May 2010 17:30:50 -0700 [thread overview]
Message-ID: <9FFF03C06E824A4EB7488DBD9A9138A9@us.oracle.com> (raw)
In-Reply-To: <87ljbby08e.fsf@stupidchicken.com>
> > So we now break any existing code that counts on `delete-char'
> > or `delete-backward-char' being key-bound. In particular,
> > customizations (e.g. key remappings) involving those commands
> > no longer work.
>
> Yes, this is a clear downside.
I'm glad we agree on that.
> > So instead of having one such var per command (bad), or one var
> > for all such commands (bad), or using a property on a command
> > symbol such as delsel does (good), we now have two new commands
> > whose implementations hard-code this feature (bad). The new
> > commands and the new option hard-code each other.
>
> First, the goal is not to replace delete-selection mode. It's to
> eliminate the special-case handling of mouse selections
Yes, I know. And I agree with that initiative.
I was against that special case from the beginning.
I think you are going beyond mouse-selection in the proposed change, however.
> and make active selections behave more consistently.
(I'm not sure what that means, so I can't speak to it.)
> Second, a huge number of commands already hard-code specific
> behavior when Transient Mark mode is active. That's the point
> of Transient Mark mode.
That might be, but I don't think it's the same kind of behavior. That
`query-replace' might behave differently depending on whether there is an active
region is one thing. That doesn't affect basic editing commands and their
traditional keys. When you replace the bindings of the basic character-deletion
commands it can affect any mode or user code that remaps those commands.
I didn't even mention that the proposal changes the behavior of
`delete-backward-char'. I didn't notice that part of the proposal at first
reading. IIUC, That would break any code (or interactive use) that invokes
`delete-backward-char' and expects it to untabify.
Can we not please find some other way to simply "eliminate the special-case
handling of mouse selections"? What about going back to the code that was there
before that feature was added?
next prev parent reply other threads:[~2010-05-23 0:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 17:44 Updated proposal for DEL to delete active region Chong Yidong
2010-05-22 18:37 ` Drew Adams
2010-05-22 19:02 ` Eli Zaretskii
2010-05-22 20:43 ` Drew Adams
2010-05-22 21:39 ` David Kastrup
2010-05-22 22:14 ` Drew Adams
2010-05-22 21:37 ` David Kastrup
2010-05-22 23:40 ` Chong Yidong
2010-05-23 0:30 ` Drew Adams [this message]
2010-05-23 17:10 ` Andreas Schwab
2010-05-24 21:03 ` Stefan Monnier
2010-05-23 1:33 ` Stefan Monnier
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=9FFF03C06E824A4EB7488DBD9A9138A9@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@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 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).