From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Display the key bindings on the screen
Date: Wed, 26 Jun 2013 03:13:46 +0200 [thread overview]
Message-ID: <87fvw57jxx.fsf@web.de> (raw)
In-Reply-To: 8638s7w6eg.fsf@somewhere.org
"Sebastien Vauban" <sva-news@mygooglest.com>
writes:
> I just used it with success, under Emacs 24.3.50.1.
Thanks for testing!
> [...] I'd suggest 3 small (?) improvements:
> - having the same keys not repeated in sequence over separate lines (try to
> write, for example, "Down 47 times").
I totally agree. Although the fact that I want to merge in messages
complicates the matter a bit.
> - respect `ilog-log-max' as soon as the limit is exceeded (for
> example, after
> 10 keystrokes), instead after some apparent idle time.
What is the advantage you have in mind?
> - remove the name of the buffer where things occur -- it makes it
> (much, with
> long buffer names) harder to read, while looking at the screencast
> (if used
> for that) gives all the needed information about where keys are pressed.
>
> - don't write `self-insert-command': useless to read, for such cases,
> that the
> key pressed had no special effect other than inserting itself. I would
> possibly allow the user to be able to customize whether he wants to
> see the
> command for the other cases, but that's really helpful, in many cases (a
> great functionality).
No doubt, that would improve readability. Note that when I wrote it, I
had a totally different use case in mind: to let you reconstruct what
happened the last seconds. I didn't think of presentation.
Anyway, feel free to contact me when you want to answer:
(concat "michael" [95] "heerdegen" [64] "web.de")
Regards,
Michael.
next prev parent reply other threads:[~2013-06-26 1:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-22 19:15 Display the key bindings on the screen marc tfardy
2013-06-23 2:06 ` rustompmody
2013-06-24 16:28 ` Rustom Mody
2013-06-23 3:09 ` Michael Heerdegen
2013-06-24 14:55 ` Tim Visher
[not found] ` <mailman.2233.1371957909.22516.help-gnu-emacs@gnu.org>
2013-06-24 16:30 ` Rustom Mody
2013-06-24 18:05 ` Michael Heerdegen
2013-06-24 19:09 ` marc tfardy
2013-06-24 21:22 ` Sebastien Vauban
2013-06-26 1:13 ` Michael Heerdegen [this message]
[not found] ` <mailman.2321.1372097153.22516.help-gnu-emacs@gnu.org>
2013-06-25 1:51 ` Rustom Mody
2013-06-25 7:41 ` Peter Dyballa
2013-06-25 21:20 ` Michael Heerdegen
[not found] ` <mailman.2425.1372195268.22516.help-gnu-emacs@gnu.org>
2013-06-26 3:56 ` Rustom Mody
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=87fvw57jxx.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).