From: Stefan Kangas <stefan@marxist.se>
To: Juri Linkov <juri@linkov.net>
Cc: 51138@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#51138: Increase the value of kill-ring-max
Date: Wed, 13 Oct 2021 11:33:26 -0700 [thread overview]
Message-ID: <CADwFkmm+3mjH8Onn9nzEfYw_P7Fs87RstPz=dz0pH1N_C=rWWQ@mail.gmail.com> (raw)
In-Reply-To: <87mtncvmx2.fsf@mail.linkov.net>
Juri Linkov <juri@linkov.net> writes:
> Thanks. It makes sense to reduce the default value of yank-menu-max-items
> because long menus are hard to navigate, but OTOH indeed maybe better
> to leave it at the previous max number.
Right, I guess having a ridiculously large number like 60 can't hurt, as
you anyways will start out at the top of the menu.
OTOH, I'd be fine with reducing it to 40 to restore some sanity here.
I mean, we also now provide a user-option for this.
>> (defcustom yank-menu-length 20
>> - "Maximum length to display in the `yank-menu'."
>> + "Maximum length of entries in the `yank-menu'."
>
> The previous docstring was unclear, but the new docstring
> doesn't make it clearer. I don't have a concrete suggestion,
> but it needs to say that this length truncates the text
> of each menu item.
How about:
"Maximum length to which entries in the 'yank-menu' will be truncated."
?
prev parent reply other threads:[~2021-10-13 18:33 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
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 [this message]
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='CADwFkmm+3mjH8Onn9nzEfYw_P7Fs87RstPz=dz0pH1N_C=rWWQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=51138@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.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).