[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#38796: closed (26.3; `view-lossage': Use a variable for the lossage

From: GNU bug Tracking System
Subject: bug#38796: closed (26.3; `view-lossage': Use a variable for the lossage limit)
Date: Thu, 17 Sep 2020 14:36:02 +0000

Your message dated Thu, 17 Sep 2020 16:35:22 +0200
with message-id <87363gwjx1.fsf@gmail.com>
and subject line Re: bug#38796: 26.3; `view-lossage': Use a variable for the 
lossage limit
has caused the debbugs.gnu.org bug report #38796,
regarding 26.3; `view-lossage': Use a variable for the lossage limit
to be marked as done.

(If you believe you have received this mail in error, please contact

38796: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=38796
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 26.3; `view-lossage': Use a variable for the lossage limit Date: Sun, 29 Dec 2019 09:04:54 -0800 (PST)
This report is a follow-up to this emacs-devel thread:


and to the older thread that it references:


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

The latter thread mentioned above ended with RMS's decision to have this
taken care of after the release that was then incipient.  But this was
never done.

I'd prefer to see this as a user option, but an ordinary defvar would
already be a great improvement.

I don't think it's uncommon to have mistakenly typed some keys, gotten
in a strange or unfamiliar situation as a result of that, and then tried
to find out just what keys led to that.  Depending on what else you did
in the meantime, before hitting `C-h l' (e.g., to get out of the strange
situation), `view-lossage' might not reach far enough backward to show
you the mistake you made.

It shouldn't be a big deal to move this limit to a Lisp variable.  Can
this please be done now?


Not part of this bug report, but `view-lossage' could also be improved
by letting you (or Lisp code) filter the recorded "keystroke" history,
to remove stuff that you feel is really extraneous (e.g. not keyboard
keystrokes).  Such filtering could be just hiding that from view.

(This is all the more relevant if we can control the lossage limit.  The
really relevant user input is sometimes a relatively small subset of the
full list of recorded events you see now with `C-h l'.)

In GNU Emacs 26.3 (build 1, x86_64-w64-mingw32)
 of 2019-08-29
Repository revision: 96dd0196c28bc36779584e47fffcca433c9309cd
Windowing system distributor `Microsoft Corp.', version 10.0.17763
Configured using:
 `configure --without-dbus --host=x86_64-w64-mingw32
 --without-compress-install 'CFLAGS=-O2 -static -g3''

--- End Message ---
--- Begin Message --- Subject: Re: bug#38796: 26.3; `view-lossage': Use a variable for the lossage limit Date: Thu, 17 Sep 2020 16:35:22 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
Tino Calancha <tino.calancha@gmail.com> writes:

> I am glad to push the following patch next week if there are no
> complaints.

Pushed into master branch as commit
'Give Lisp control on the lossage size'

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]