From: Richard Stallman <rms@gnu.org>
Cc: storm@cua.dk, emacs-devel@gnu.org
Subject: Re: cua-mode and the tutorial
Date: Tue, 29 Aug 2006 13:18:40 -0400 [thread overview]
Message-ID: <E1GI7EW-00013f-NL@fencepost.gnu.org> (raw)
In-Reply-To: <44F36EF8.5040808@student.lu.se> (message from Lennart Borgman on Tue, 29 Aug 2006 00:32:24 +0200)
> 1) Remove all non-default key bindings in the tutorial. I used that
> approach from the beginning so I have code for that.
>
> I don't like the approach of having the tutorial teach standard
> bindings in an Emacs where they won't work.
>
I can see four main possibilities:
1) Like above, but you do not like that option
It is not a very useful thing to do. Anyway, the user can turn off
the nonstandard bindings and run the tutorial, by running `emacs -q'.
2) Keep the nonstandard bindings and tell the user about it. This can be
done the way Kim suggested (a small yellow screen with a details link).
The changed bindings can be marked in the tutorial text or they can be
marked and replaced.
There is nothing inherently bad about offering this possibility is no
harm in itself. But people pointed out various inconveniences of the
attempt to do it.
3) A combination of 1 and 2. Let the user decide. (This is perhaps a bit
complicated for a tutorial.)
My response is a combination of the two responses above.
4) Stop the user from running the tutorial. I do not like this option.
If practical inconveniences makes #2 a bad idea, #4 is what we are
left with.
next prev parent reply other threads:[~2006-08-29 17:18 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44C8F069.1070002@student.lu.se>
2006-08-22 13:12 ` cua-mode and the tutorial Kim F. Storm
2006-08-22 13:26 ` Kim F. Storm
2006-08-22 14:30 ` Lennart Borgman
2006-08-22 15:02 ` Kim F. Storm
2006-08-22 15:57 ` Lennart Borgman
2006-08-22 18:17 ` Richard Stallman
2006-08-23 4:06 ` Richard Stallman
2006-08-23 4:37 ` Lennart Borgman
2006-08-24 5:20 ` Richard Stallman
2006-08-23 7:21 ` Kim F. Storm
2006-08-24 5:20 ` Richard Stallman
2006-08-24 7:30 ` Kim F. Storm
2006-08-25 20:25 ` Richard Stallman
2006-08-25 22:12 ` Kim F. Storm
2006-08-26 12:22 ` Richard Stallman
2006-08-26 12:44 ` David Kastrup
2006-08-27 14:34 ` Richard Stallman
2006-08-26 14:19 ` Stefan Monnier
2006-08-26 15:07 ` Drew Adams
2006-08-26 21:15 ` Kim F. Storm
2006-08-27 14:34 ` Richard Stallman
2006-08-27 15:06 ` David Kastrup
2006-08-28 22:09 ` Richard Stallman
2006-08-27 21:30 ` Kim F. Storm
2006-08-26 21:14 ` Kim F. Storm
2006-08-28 9:52 ` Richard Stallman
2006-08-28 10:07 ` David Kastrup
2006-08-28 11:21 ` Kim F. Storm
2006-08-29 17:18 ` Richard Stallman
2006-08-27 8:35 ` Lennart Borgman
2006-08-28 9:52 ` Richard Stallman
2006-08-28 10:17 ` Slawomir Nowaczyk
2006-08-29 17:18 ` Richard Stallman
2006-08-29 17:55 ` Drew Adams
2006-08-29 18:13 ` Lennart Borgman
2006-08-28 22:32 ` Lennart Borgman
2006-08-29 17:18 ` Richard Stallman [this message]
2006-08-31 15:10 ` Lennart Borgman
2006-09-21 14:24 ` Kim F. Storm
2006-08-22 14:05 ` Lennart Borgman
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=E1GI7EW-00013f-NL@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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).