all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 42916@debbugs.gnu.org
Subject: bug#42916: 26.3; `view-lossage': include timestamp
Date: Tue, 18 Aug 2020 10:12:17 -0700 (PDT)	[thread overview]
Message-ID: <9b7f542a-81a1-47cb-a2d2-1bac5b4b55df@default> (raw)

Possible enhancement:

If bug #38796 gets taken care of then users could have very long
`view-lossage' logs (if they choose).

Especially in such a context, it could be useful to provide a timestamp
with each event.  This could be via a `help-echo' property, for example.
Or it could be made available as a separate column, or in some other
way.

I know it doesn't make a lot of sense with the current state of the
output, but with much longer logs it could be helpful.

A `help-echo' property provides a tooltip, but it won't help with
searching.  A UI that lets you search, or filter (e.g. `occur') on not
only the event/key/command name but also the time/date, could be useful.

Just a thought.  `view-lossage' is essentially a log.  It could be made
more useful than it is now, I expect.

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.18362
Configured using:
 `configure --without-dbus --host=x86_64-w64-mingw32
 --without-compress-install 'CFLAGS=-O2 -static -g3''





             reply	other threads:[~2020-08-18 17:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18 17:12 Drew Adams [this message]
2020-08-19  9:49 ` bug#42916: 26.3; `view-lossage': include timestamp Lars Ingebrigtsen
2020-08-19 12:59   ` Drew Adams
2020-08-19 13:09   ` Peder O. Klingenberg
2020-08-22 21:26     ` Lars Ingebrigtsen

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=9b7f542a-81a1-47cb-a2d2-1bac5b4b55df@default \
    --to=drew.adams@oracle.com \
    --cc=42916@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 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.