unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, storm@cua.dk
Subject: Re: cua-mode and the tutorial
Date: Tue, 22 Aug 2006 14:17:12 -0400	[thread overview]
Message-ID: <E1GFaoK-0004uu-FY@fencepost.gnu.org> (raw)
In-Reply-To: <44EB151A.2000102@student.lu.se> (message from Lennart Borgman on Tue, 22 Aug 2006 16:30:50 +0200)

    Do you mean that it does not work when cua-mode is enabled? Well, it is 
    a problem. One solution would be to remove CUA mode from the tutorial 
    buffer as you suggests. However I feel uncomfortable with that solution. 
    It puts a burden on the user, "please learn this now, but later on you 
    are going to use that".

I think we just need to warn people that the tutorial is not useful
for learning to use Emacs with CUA mode.

  parent reply	other threads:[~2006-08-22 18:17 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 [this message]
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

  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=E1GFaoK-0004uu-FY@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).