From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 38796@debbugs.gnu.org
Subject: bug#38796: 26.3; `view-lossage': Use a variable for the lossage limit
Date: Sun, 29 Dec 2019 19:30:15 +0200 [thread overview]
Message-ID: <83zhfbm448.fsf@gnu.org> (raw)
In-Reply-To: <43aac56d-ecf1-44ed-9be1-ffb8e5f8a7ce@default> (message from Drew Adams on Sun, 29 Dec 2019 09:04:54 -0800 (PST))
severity 38796 wishlist
thanks
> Date: Sun, 29 Dec 2019 09:04:54 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
>
> This report is a follow-up to this emacs-devel thread:
>
> https://lists.gnu.org/archive/html/emacs-devel/2019-12/msg00678.html
>
> and to the older thread that it references:
>
> https://lists.gnu.org/archive/html/emacs-devel/2006-03/msg01012.html
>
> Please use a variable for the limit of how many characters to use for
> recording lossage.
>
> Doing that will give users (and Lisp code) control over the limit.
> Having a limit that is hard-coded in C is not user-friendly - it's even
> unemacsy.
It's a constant size of a vector that records the keys in a cyclical
fashion. So it isn't enough to expose the value to Lisp; one must
also write code that reallocates the vector when the value changes,
and copies the keystrokes from the old to the new vector in the
correct order. Not rocket science, but still.
Patches are welcome.
next prev parent reply other threads:[~2019-12-29 17:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 17:04 bug#38796: 26.3; `view-lossage': Use a variable for the lossage limit Drew Adams
2019-12-29 17:30 ` Eli Zaretskii [this message]
2019-12-29 17:34 ` Drew Adams
2020-06-26 21:58 ` Tino Calancha
2020-06-27 8:32 ` Eli Zaretskii
2020-06-28 16:55 ` Tino Calancha
2020-06-28 18:00 ` Stefan Monnier
2020-06-28 20:01 ` Drew Adams
2020-06-28 21:52 ` Tino Calancha
2020-06-29 0:05 ` Drew Adams
2020-08-22 21:24 ` Lars Ingebrigtsen
2020-08-22 22:54 ` Drew Adams
2020-08-27 21:28 ` Tino Calancha
2020-08-28 6:04 ` Eli Zaretskii
2020-09-04 9:31 ` Tino Calancha
2020-09-04 12:07 ` Eli Zaretskii
2020-09-12 12:29 ` Tino Calancha
2020-09-17 14:35 ` Tino Calancha
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=83zhfbm448.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38796@debbugs.gnu.org \
--cc=drew.adams@oracle.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 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.