unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 38796@debbugs.gnu.org
Subject: bug#38796: 26.3; `view-lossage': Use a variable for the lossage limit
Date: Sun, 29 Dec 2019 09:04:54 -0800 (PST)	[thread overview]
Message-ID: <43aac56d-ecf1-44ed-9be1-ffb8e5f8a7ce@default> (raw)

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.

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''





             reply	other threads:[~2019-12-29 17:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-29 17:04 Drew Adams [this message]
2019-12-29 17:30 ` bug#38796: 26.3; `view-lossage': Use a variable for the lossage limit Eli Zaretskii
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

  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=43aac56d-ecf1-44ed-9be1-ffb8e5f8a7ce@default \
    --to=drew.adams@oracle.com \
    --cc=38796@debbugs.gnu.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).