From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: Time of last command invoked
Date: Sat, 27 Feb 2021 09:21:56 +0300 [thread overview]
Message-ID: <YDnlBAhh3gvRIMx7@protected.rcdrun.com> (raw)
In-Reply-To: <87mtvqmr16.fsf@zoho.eu>
* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2021-02-27 00:57]:
> Jean Louis wrote:
>
> > Is there some internal log in Emacs that keeps the date and
> > time of last command invoked by a key or M-x?
>
> That would imply a huge overhead.
>
> For the command subset that is relevant to whatever you want
> to do you can alias a logger, perhaps.
Is "logger" some function that exists in Emacs, or should I simply
make it?
(defun rcd/emacs-lisp-log (log)
"Allows functions to log their usage"
(let* ((function (second (backtrace-frame 5 nil)))
(timestamp (format-time-string "%Y-%m-%d-%H:%M:%S"))
(log (format "%s %s %s\n" timestamp function log))
(save-silently t))
(with-temp-buffer
(insert log)
(append-to-file (point-min) (point-max) *emacs-lisp-log*))))
(defun rcd-space ()
(interactive)
(rcd/emacs-lisp-log "SPACE")
(self-insert-command 1 32))
Then I made global-set-key SPC to rcd-space and now I log each SPACE
as *emacs-lisp-log* is like ~/tmp/lisp.log. Typing is not obstracted.
It is useful for self supervision.
next prev parent reply other threads:[~2021-02-27 6:21 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 [this message]
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
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=YDnlBAhh3gvRIMx7@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@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.
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).