GNU bug report logs - #42916
26.3; `view-lossage': include timestamp

Previous Next

To reply to this bug, email your comments to 42916 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 26.3; `view-lossage': include timestamp
Date: Tue, 18 Aug 2020 10:12:17 -0700 (PDT)

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

Message #8 received at 42916 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 42916 <at> debbugs.gnu.org
Subject: Re: bug#42916: 26.3; `view-lossage': include timestamp
Date: Wed, 19 Aug 2020 11:49:17 +0200

Drew Adams <drew.adams <at> oracle.com> writes:

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

This would mean querying (and storing) the time stamp of all keystrokes,
which seems excessive for such a marginal feature.

Anybody got an opinion here?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #11 received at 42916 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 42916 <at> debbugs.gnu.org
Subject: RE: bug#42916: 26.3; `view-lossage': include timestamp
Date: Wed, 19 Aug 2020 05:59:49 -0700 (PDT)

> > 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.
> 
> This would mean querying (and storing) the time stamp of all keystrokes,
> which seems excessive for such a marginal feature.

Yes.  It was just a thought.

Perhaps an optional behavior (via mode or otherwise)
would be in order - something you could turn on when
interested in more complete logging.  That could help
with some kinds of debugging or learning, for instance.

Certainly, if this were a performance drag it shouldn't
be the default behavior.

Message #14 received at 42916 <at> debbugs.gnu.org (full text, mbox):

From: "Peder O. Klingenberg" <peder <at> klingenberg.no>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 42916 <at> debbugs.gnu.org, Drew Adams <drew.adams <at> oracle.com>
Subject: Re: bug#42916: 26.3; `view-lossage': include timestamp
Date: Wed, 19 Aug 2020 15:09:19 +0200

On on., 2020-08-19 kl. 11.49 +0200 +0200, Lars Ingebrigtsen wrote:

> This would mean querying (and storing) the time stamp of all keystrokes,
> which seems excessive for such a marginal feature.

An alternative could be to dump a dedicated timestamp event into the log
every <mumble> minutes or so.  It wouldn't give you exact timings, but
could tell you whether you're looking at something you typed last month
or five minuts ago, and wouldn't require more work on every keystroke.

...Peder...

Message #17 received at 42916 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: "Peder O. Klingenberg" <peder <at> klingenberg.no>
Cc: 42916 <at> debbugs.gnu.org, Drew Adams <drew.adams <at> oracle.com>
Subject: Re: bug#42916: 26.3; `view-lossage': include timestamp
Date: Sat, 22 Aug 2020 23:26:13 +0200

"Peder O. Klingenberg" <peder <at> klingenberg.no> writes:

> On on., 2020-08-19 kl. 11.49 +0200 +0200, Lars Ingebrigtsen wrote:
>
>> This would mean querying (and storing) the time stamp of all keystrokes,
>> which seems excessive for such a marginal feature.
>
> An alternative could be to dump a dedicated timestamp event into the log
> every <mumble> minutes or so.  It wouldn't give you exact timings, but
> could tell you whether you're looking at something you typed last month
> or five minuts ago, and wouldn't require more work on every keystroke.

Hm, yes, that might be a good idea...

On the other hand, the last time I poked at the lossage data, it wasn't
a lot of fun: It's used by normal typing as well as the keyboard macro
binding stuff, so it's a bit of a prickly data structure.  If I remember
correctly; it's been at least a couple of years since I poked at it.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.