From: storm@cua.dk (Kim F. Storm)
Cc: lennart.borgman.073@student.lu.se, emacs-devel@gnu.org
Subject: Re: cua-mode and the tutorial
Date: Thu, 24 Aug 2006 09:30:28 +0200 [thread overview]
Message-ID: <m3lkpe6163.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1GG7db-0004um-0G@fencepost.gnu.org> (Richard Stallman's message of "Thu, 24 Aug 2006 01:20:19 -0400")
Richard Stallman <rms@gnu.org> writes:
> Other than that, the tutorial is quite useful even for users of CUA!
> So one approach is to just bind locally bind cua-enable-cua-keys to
> nil in the tutorial buffer and make a note like this:
>
> The purpose of the tutorial is to teach you the basic, standard
> Emacs key bindings. Therefore, CUA mode's C-z C-x C-c and C-v
> bindinds have been disabled in this tutorial buffer. [Details]
>
> I have no objection to that. If you think it does a good job of
> dealing with CUA mode, then let's do it.
IMO, it is ok.
> But we should make it offer to delete the customization
> in case the user was not asked about it.
Too complex for very little benefit IMHO.
We don't know what method was used to enable CUA-mode. It could be a
customization, but it could also be an explicit call to CUA-mode in
emacs. So that is not trivial to do right in all cases.
> In theory we could do this, but is it adequate for learning to use
> Emacs with viper? I doubt it.
Ok, I agree. So we seem to agree that the tutorial should not start
at all if viper is enabled, but just list the differences in
key bindings.
> The purpose of the tutorial is to teach you the basic, standard
> Emacs key bindings. Therefore, some non-standard key bindinds
> have been disabled in this tutorial buffer. [Details]
>
> No, in general this is not a useful way to deal with the situation.
Ok.
> So I reject this approach in general, but I will accept it for CUA mode.
Ok.
Lennart, comments?
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-08-24 7:30 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 [this message]
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
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=m3lkpe6163.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
/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).