unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: rms@gnu.org, Michael Kifer <kifer@cs.sunysb.edu>, emacs-devel@gnu.org
Subject: Re: cua-mode and the tutorial
Date: Thu, 21 Sep 2006 16:24:35 +0200	[thread overview]
Message-ID: <m3mz8tjo0s.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <44F6FBEB.70008@student.lu.se> (Lennart Borgman's message of "Thu\, 31 Aug 2006 17\:10\:35 +0200")


Sorry for not following up before ...


Lennart Borgman <lennart.borgman.073@student.lu.se> writes:

> I have attempted to make a new solution in accordance with our
> discussion. This new solution has the following changes:
>
> 1) The yellow area in the tutorial buffer is now small and has a
> "Details"-link (Kim's suggestion)

Looks good!

>
> 2) The "Details"-link displays information in the help buffer.

Good.

> 3) Changed keys are now marked in the tutorial buffer in two ways:
>    a) The key (like C-v) has yellow background

Looks good.  Perhaps the shade of yellow could be a little less LOUD ?

>    b) There is a line under the key telling what can be used instead
> (in English)

BAD!  (sorry!)

This is very distracting and really makes it difficult to follow the
ordinary text.  Also, on some pages, the same text is shown several
times.

What about giving a combined help in the echo area about the "yellow
keys":

For example:

** Rebound keys: C-v: <next>  M-v: <prior>

You can color the keys in yellow too.

Of course, you would have to somehow regenerate that message as the
user moves through the tutorial to reflect the yellow keys on the
current page (can't bee too hard with a buffer-local post-command-hook
which scans the buffer from (window-start) to (window-end nil t)).


> 4) The yellow areas in 3 are readonly.
>
> 5) There is a link called "Explain" in the yellow areas in 3 that
> moves the point to (point-min)

This is very confusing too.  I tried it and would have expected it to
tell me something about the specific binding (in the echo area or Help
buffer).  But it would go along with the yellow line, so it's not a
big deal.

Maybe you could show the details buffer if the user clicks on any
of the "yellow keys" (like an anonymouse button).

> The support for Viper is still there. I see no reason to remove it
> since I do believe it is useful for Viper users and it does not in any
> way disturb those not using Viper. (Except that the code is more
> complicated of course, but that is only loaded when the tutorial is
> run.)

Ok.

One problem:

When CUA is enabled, your code doesn't detect that M-v is rebound.


I don't know whether this should be installed before the release,
but in any case it is not (IMHO) ready yet.

WDOT?

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2006-09-21 14:24 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
2006-08-31 15:10                     ` Lennart Borgman
2006-09-21 14:24                       ` Kim F. Storm [this message]
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=m3mz8tjo0s.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=kifer@cs.sunysb.edu \
    --cc=rms@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).