From: D. Goel <deego@glue.umd.edu>
Subject: Re: capturing commands
Date: 18 Oct 2002 15:31:46 -0400 [thread overview]
Message-ID: <87n0pb5ysd.fsf@computer.localdomain> (raw)
In-Reply-To: aopicm$sm2$1@news.btv.ibm.com
> I think you are looking for:
>
> M-x view-lossage
>
What i thought the OP was looking for, was a list of commands
executed --whether through a keystroke or through M-x calls.. the
hook i posted, did that, i think.
I guess one might be able to somehow parse the results of view-lossage
to do that (how?) --- but that could get (even more) complicated very
soon---one would have to figure out which minor mode the user was in
when they issued a particular keystroke..
DG http://deego.gnufans.org/~deego/
--
prev parent reply other threads:[~2002-10-18 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 22:08 capturing commands merik
2002-10-16 22:22 ` Barry Margolin
2002-10-16 23:14 ` Michael Slass
2002-10-17 0:15 ` merik
2002-10-17 1:43 ` Michael Slass
2002-10-18 3:29 ` Artist
2002-10-18 7:40 ` Bernd Wolter
2002-10-18 16:28 ` Clemens Fischer
2002-10-17 15:03 ` D. Goel
2002-10-18 18:03 ` kgold
2002-10-18 19:31 ` D. Goel [this message]
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=87n0pb5ysd.fsf@computer.localdomain \
--to=deego@glue.umd.edu \
/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).