From: ndame via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 41168@debbugs.gnu.org
Subject: bug#41168: Add variable to limit save-interprogram-paste-before-kill by size
Date: Sun, 10 May 2020 08:56:40 +0000 [thread overview]
Message-ID: <ZGTBiZitvuxEDdh-VICfhlv0YhY0KI3zBgEbUXEp3wm08K5NdzxIYCJ0FhEvu0RONT7v4H2X6dJ4AXumoeZHUoPDIkc7-ONs1zId-jfxBJQ=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
I like to set save-interprogram-paste-before-kill to t, so emacs does not clobber clipboard data without saving it.
However, sometimes I have large data on the clipboard which I don't want to end up in emacs as the manual also warns:
Optionally, you can change
‘save-interprogram-paste-before-kill’ to ‘t’. Then Emacs will first
save the clipboard to its kill ring, preventing you from losing the old
clipboard data—at the risk of high memory consumption if that data turns
out to be large.
How about a variable which allows the user to limit the size of data saved on the kill ring? Data larger than the limit is not copied.
save-interprogram-paste-before-kill itself could specify this limit. If it's not t but a number then it's the limit as number of bytes or maybe kilobytes, because I imagine the user sets such a limit to at least a few hundred kilobytes or higher.
[-- Attachment #2: Type: text/html, Size: 1081 bytes --]
next reply other threads:[~2020-05-10 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 8:56 ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-05-10 14:04 ` bug#41168: Add variable to limit save-interprogram-paste-before-kill by size Eli Zaretskii
2021-06-13 12:04 ` Lars Ingebrigtsen
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='ZGTBiZitvuxEDdh-VICfhlv0YhY0KI3zBgEbUXEp3wm08K5NdzxIYCJ0FhEvu0RONT7v4H2X6dJ4AXumoeZHUoPDIkc7-ONs1zId-jfxBJQ=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=41168@debbugs.gnu.org \
--cc=ndame@protonmail.com \
/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).