From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: 51138@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#51138: Increase the value of kill-ring-max
Date: Tue, 12 Oct 2021 14:57:58 +0200 [thread overview]
Message-ID: <87a6jecsdl.fsf@gnus.org> (raw)
In-Reply-To: <87v922amfq.fsf@mail.linkov.net> (Juri Linkov's message of "Tue, 12 Oct 2021 09:46:57 +0300")
Juri Linkov <juri@linkov.net> writes:
>> The value of kill-ring-max was last increased in 1998, when it was
>> doubled from 30 to 60. See commit bffa4d92e152.
>>
>> Given that RAM is cheaper these days, how about doubling it to 120?
Sounds like a good idea to me. (Or bigger.)
> A long time ago I customized kill-ring-max to 1024,
> and the only problem with such a big value is that
> it produces too long submenu in "Paste from Kill Menu".
> This is because menu-bar-update-yank-menu
> truncates to the length of kill-ring-max,
> but it should introduce a new variable
> separately customized for the paste menu's size.
Yup.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-12 12:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 20:19 bug#51138: Increase the value of kill-ring-max Stefan Kangas
2021-10-12 6:46 ` Juri Linkov
2021-10-12 12:57 ` Lars Ingebrigtsen [this message]
2021-10-12 13:23 ` Stefan Kangas
2021-10-12 13:26 ` Lars Ingebrigtsen
2021-10-12 23:21 ` Stefan Kangas
2021-10-13 11:36 ` Lars Ingebrigtsen
2021-10-13 22:28 ` Stefan Kangas
2021-10-13 17:45 ` Juri Linkov
2021-10-13 18:22 ` Juri Linkov
2021-10-13 18:27 ` Eli Zaretskii
2021-10-13 18:30 ` Eli Zaretskii
2021-10-13 18:38 ` Juri Linkov
2021-10-13 22:28 ` Stefan Kangas
2021-10-14 16:10 ` Juri Linkov
2021-10-14 18:51 ` Stefan Kangas
2021-10-15 6:59 ` Juri Linkov
2021-10-13 18:33 ` Stefan Kangas
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=87a6jecsdl.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=51138@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=stefan@marxist.se \
/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.