From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@jurta.org>
Cc: 13312@debbugs.gnu.org
Subject: bug#13312: 24.3.50; delete selection mode not killing on overwrite
Date: Sat, 19 Oct 2013 08:37:22 -0700 (PDT) [thread overview]
Message-ID: <761f4d61-cd53-4371-9744-70f08619c75b@default> (raw)
In-Reply-To: <87wql9i8l5.fsf@mail.jurta.org>
> > I don't think this should be on the wishlist. It's a clear bug.
> >
> > (put 'ANY-COMMAND 'delete-selection 'kill) should kill the
> > text in the active region. It does not do so in the case
> > where ANY-COMMAND is `self-insert-command'. A bug.
> >
> > The fact that "usually the delete text is still available from the
> > "PRIMARY" selection" is irrelevant. (Not to mention that there is
> > no "PRIMARY" selection on some platforms.)
> >
> > Putting `kill' as the property value should kill the text, pure
> > and simple.
>
> There is no bug. In delete-selection-mode with overwrite-mode
> selecting a region and typing a self-inserting key deletes the
> selected region and replaces it with the typed key.
Did you read the bug description and the associate StackOverflow
question? The bug is that when you put `kill' as the
`delete-selection' property value on `self-insert-command' the
region is not killed - it is not added to the `kill-ring'. And
the first char to be self-inserted is not inserted.
This is not about the out-of-the-box behavior of self-inserting
in delete-selection mode, i.e., with the property value having
its default value.
next prev parent reply other threads:[~2013-10-19 15:37 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
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 [this message]
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=761f4d61-cd53-4371-9744-70f08619c75b@default \
--to=drew.adams@oracle.com \
--cc=13312@debbugs.gnu.org \
--cc=juri@jurta.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).