From: Chong Yidong <cyd@stupidchicken.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Proposal for DEL to delete the active region
Date: Sun, 02 May 2010 10:34:24 -0400 [thread overview]
Message-ID: <87y6g274pb.fsf@stupidchicken.com> (raw)
In-Reply-To: <jwvhbmruine.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 01 May 2010 22:54:15 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> + (defcustom delete-backward-char-delete-region t
>
> But this doesn't seem right: we're not going to have one such variable
> for delete-backward-char, delete-char, delete-backward-char-untabify,
> and the handful of other commands that
>
> grep "'delete-selection 'supersede" lisp/**/*.el
>
> indicate will want a similar treatment.
I count ten such commands, all variants of delete-char or
delete-backward-char. I think these should all obey the same two
variables. For instance, `c-electric-backspace' should obey
`delete-backward-char-delete-region', and `org-delete-char' should obey
`delete-char-delete-region'.
>> + (defun delete-backward-char (n killflag)
> [...]
>> + (interactive "p\nP")
>> + (unless (integerp n)
>> + (signal 'wrong-type-argument (list 'integerp n)))
>> + (cond ((and (use-region-p)
>> + delete-backward-char-delete-region
>> + (= n 1))
>
> the other problem here is that this change also affects calls from Lisp
> rather than only interactive calls.
Good point. How about splitting up the functions, similar to next-line
vs forward-line?
So, we'd leave delete-backward-char unchanged, and create a new command
`delete-backward' which is the default binding for [DEL]. Similarly, a
new function `delete-forward', which is the default binding for
[delete].
next prev parent reply other threads:[~2010-05-02 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 3:23 Proposal for DEL to delete the active region Chong Yidong
2010-05-02 2:54 ` Stefan Monnier
2010-05-02 6:04 ` Thierry Volpiatto
2010-05-02 14:34 ` Chong Yidong [this message]
2010-05-03 6:00 ` Richard Stallman
2010-05-03 17:12 ` 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=87y6g274pb.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).