From: Tony Day <tonyday567@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 13312@debbugs.gnu.org
Subject: bug#13312: 24.3.50; delete selection mode not killing on overwrite
Date: Tue, 1 Jan 2013 11:06:04 +1100 [thread overview]
Message-ID: <CAOmqhoZRXBL9XqH3ADr86nse5o03iZee=kAb-NpDSTH71kHk-A@mail.gmail.com> (raw)
In-Reply-To: <3hpq1rm2l5.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
On Mon, Dec 31, 2012 at 12:29 PM, Glenn Morris <rgm@gnu.org> wrote:
> Why did you expect `delete-selection-mode' to kill rather than delete?
I asked on stack exchange for how to change the behaviour and someone
suggested it was a bug. I figured delete-selection-mode was less of a
mouthful than maybe-delete-or-kill-selection-mode ;)
The critical code lines were was also ambiguous and beyond my powers of
comprehension:
(put 'self-insert-command 'delete-selection
(lambda ()
(not (run-hook-with-args-until-success
'self-insert-uses-region-functions))))
Thanks for confirming the default behaviour. On changing to kill rather
than delete with:
(put 'self-insert-command 'delete-selection 'kill)
I get no self-inserted key, and an extra blank item in the kill ring.
Regardless, why don't we call this a hack and not a bug.
Tony
[-- Attachment #2: Type: text/html, Size: 1423 bytes --]
next prev parent reply other threads:[~2013-01-01 0:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 23:58 bug#13312: 24.3.50; delete selection mode not killing on overwrite Tony Day
2012-12-31 1:29 ` Glenn Morris
2013-01-01 0:06 ` Tony Day [this message]
2013-01-03 17:10 ` Stefan Monnier
2013-10-19 14:44 ` Drew Adams
2013-10-19 15:28 ` Juri Linkov
2013-10-19 15:37 ` Drew Adams
2013-10-19 16:28 ` Juri Linkov
2013-10-19 17:42 ` Drew Adams
2013-10-19 21:08 ` Juri Linkov
2013-10-19 21:18 ` Drew Adams
2013-12-11 1:11 ` Juri Linkov
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='CAOmqhoZRXBL9XqH3ADr86nse5o03iZee=kAb-NpDSTH71kHk-A@mail.gmail.com' \
--to=tonyday567@gmail.com \
--cc=13312@debbugs.gnu.org \
--cc=rgm@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).