From: Jean Louis <bugs@gnu.support>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org, Robert Thorpe <rt@robertthorpeconsulting.com>
Subject: Re: Time of last command invoked
Date: Mon, 1 Mar 2021 09:45:54 +0300 [thread overview]
Message-ID: <YDyNohBjPIQsr2AT@protected.rcdrun.com> (raw)
In-Reply-To: <jwvim6cusfk.fsf-monnier+emacs@gnu.org>
* Stefan Monnier <monnier@iro.umontreal.ca> [2021-02-28 20:55]:
> > There are also those advise functions. I have not express myself
> > well first time as first I was thinking maybe each command like in
> > lossage would have somewhere its timestamp which is maybe hidden and
> > I could just access it and find out my times of work. It would be
> > possible before exit from Emacs to make a report of full work and
> > statistics. It is for self observation.
> >
> > Working in the area with frequent power outages is difficult. Then
> > some information about my last work helps me find out other pieces
> > of information and analyze what I was doing at what time.
>
> BTW, it's not hard to do what you want:
> Use a `post-command-hook` or `pre-command-hook` where you record the
> current time the `this-command` and/or the `(this-command-keys)`.
Ah, yes, that is right. Thank you.
next prev parent reply other threads:[~2021-03-01 6:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 14:20 Time of last command invoked Jean Louis
2021-02-26 21:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-27 6:21 ` Jean Louis
2021-03-02 3:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-07 9:26 ` Jean Louis
2021-03-07 9:47 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-27 15:31 ` Stefan Monnier
2021-02-28 6:17 ` Robert Thorpe
2021-02-28 7:22 ` Jean Louis
2021-02-28 15:25 ` Stefan Monnier
2021-03-01 6:45 ` Jean Louis [this message]
2021-03-02 3:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=YDyNohBjPIQsr2AT@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rt@robertthorpeconsulting.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.
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).