all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thibaut Verron <thibaut.verron@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: Make <delete> save the deleted text into the killing ring
Date: Thu, 15 Dec 2022 11:18:42 +0100	[thread overview]
Message-ID: <08d59878-ad1c-00fe-387b-f91022b1137b@gmail.com> (raw)
In-Reply-To: <83mt7pkpgv.fsf@gnu.org>

On 15/12/2022 10:04, Eli Zaretskii wrote:
>> Date: Thu, 15 Dec 2022 09:31:43 +0100
>> From: aitor <aitors2005@gmail.com>
>>
>>> Any reason why you think you need that?  Doing so will fill the
>>> kill-ring with meaningless single-character entries.  You have 'undo',
>>> which can undelete the deleted text, so why do you want to put every
>>> single character you delete in the kill-ring?
>> I usually select portions of text using shift+arrow keys, and then
>> delete them by pressing <delete>.
> Then press "C-u <delete>" instead.  That will allow you to control
> when the deleted text goes to the kill-ring and when not.  Doing that
> by default makes little sense, because <delete> is also used to delete
> single characters or very short stretches of text.

One could also have a delete function which saves to the kill ring only 
when the region is active. This should keep most short deletions out.








  reply	other threads:[~2022-12-15 10:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 11:12 Make <delete> save the deleted text into the killing ring aitor
2022-12-14 11:23 ` aitor
2022-12-14 17:44   ` Emanuel Berg
2022-12-14 19:52     ` John Haman
2022-12-14 19:58       ` Emanuel Berg
2022-12-14 20:17 ` Gregory Heytings
2022-12-14 20:43   ` Emanuel Berg
2022-12-15  8:40   ` aitor
2022-12-15  8:48     ` Emanuel Berg
2022-12-15  6:14 ` Eli Zaretskii
2022-12-15  6:15   ` Emanuel Berg
2022-12-15  8:31   ` aitor
2022-12-15  9:04     ` Eli Zaretskii
2022-12-15 10:18       ` Thibaut Verron [this message]
2022-12-15 10:24         ` Gregory Heytings
2022-12-15 10:46           ` Emanuel Berg

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=08d59878-ad1c-00fe-387b-f91022b1137b@gmail.com \
    --to=thibaut.verron@gmail.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.