From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: cua-mode and the tutorial
Date: Tue, 22 Aug 2006 15:26:48 +0200 [thread overview]
Message-ID: <m3bqqc3nqf.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <m3hd043odj.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Tue, 22 Aug 2006 15:12:56 +0200")
storm@cua.dk (Kim F. Storm) writes:
> I tried to enter the tutorial after enabling viper-mode,
> but I didn't see any information about VIPER in the help
> buffer... so I don't know how to activate the stuff about
> vi in your patch...
Well, I tried again, and now I see it -- and I still think
my objection below is valid.
> In any case, I think that emacs should simply reject to run the
> tutorial if VIPER is enabled (or turn it off in the tutorial and NOT
> give the option to enable it in the tutorial).
>
> The current code to deal with this is overly complex -- and
> the tutorial is about learning to use basic Emacs bindings.
>
> Does the tutorial make sense at all in viper mode???
The first instruction is to type C-v ... and it doesn't work
as described!
However, in general, your changes have a big problem.
The new informational (yellow) area may take so much
space on the frame that the instructions:
>> Now type C-v (View next screen) to move to the next screen.
(go ahead, do it by holding down the CONTROL key while typing v).
From now on, you should do this again whenever you finish
reading the screen.
is partially or even completely hidden, so the whole point of the
tutorial is lost (you have to know how to scroll before you can
learn how to scroll ...).
It would be much better if you just placed a few yellow lines
near the top with the following wording:
Some of the standard key bindings described in this tutorial
have been modified, so Emacs may behave differently from
what you learn here. Click here for more details: [Details]
And then restore all key bindings (if possible) to their default
inside the tutorial.
This way, you can also structure your code so there is:
- one function which simply checks if any keys are changed
- one function which setup the standard key bindings
- one function to show the details (in a *Help* buffer).
WDYT? WDOT?
>
>
> BTW, the patch mixes two sets of changes ... for the key binding
> stuff and for running multiple tutorials at the same time.
>
> The latter part should IMO, never be installed -- it is just
> too obscure for normal users!
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-08-22 13:26 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3bqqc3nqf.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.