unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Demonstration mode...
Date: Sun, 26 Jun 2005 11:04:12 -0400	[thread overview]
Message-ID: <E1DmYg8-0007U0-KO@fencepost.gnu.org> (raw)
In-Reply-To: <85ekas99mg.fsf@lola.goethe.zz> (message from David Kastrup on Thu, 23 Jun 2005 21:05:43 +0200)

    whenever I find myself doing a demonstration of Emacs capabilities and
    features, I find myself using keyboard commands.  That is not helpful
    to onlookers who just see magic happening.

    So I have to force myself to use the mouse.

I don't understand how using the mouse makes things clearer.
Is it that you use menus to invoke the commands?  How inconvenient.

I used to teach classes in editing with Emacs, and people would
watch a big screen acting as a secondary monitor for my computer.
I would tell them what I was typing as I typed it, and go slow enough
that they could follow what I did and what effect it had.

    whenever Emacs finds that I used a key sequence from the current major
    mode (it should be configurable which keymaps it consults for a
    particular demo) that is also available as a menu, Emacs should fake
    myself using the mouse:

Why not just display the keys you type in another window?
That would also enable people to follow what you are doing.
It would be easier to implement, and it would show them
a good method to imitate, instead of a bad one.

  reply	other threads:[~2005-06-26 15:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23 19:05 Demonstration mode David Kastrup
2005-06-26 15:04 ` Richard M. Stallman [this message]
2005-06-26 18:57   ` David Kastrup
2005-06-27  5:37     ` Richard M. Stallman
2005-06-27 14:04       ` David Kastrup
2005-06-28  4:17         ` Richard M. Stallman
2005-06-28  6:59           ` David Kastrup
2005-06-28 21:29             ` Richard M. Stallman
2005-06-27 15:57       ` Drew Adams
2005-06-27 16:58         ` David Kastrup

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=E1DmYg8-0007U0-KO@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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