all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: eliz@gnu.org, jan.h.d@swipnet.se, emacs-devel@gnu.org,
	md5i@cs.cmu.edu, jasonr@gnu.org
Subject: Re: Emacs-diffs Digest, Vol 50, Issue 7
Date: Fri, 05 Jan 2007 14:39:03 +0100	[thread overview]
Message-ID: <m3slepfv9k.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1H2bAF-0003K1-4O@fencepost.gnu.org> (Richard Stallman's message of "Thu\, 04 Jan 2007 17\:34\:23 -0500")

Richard Stallman <rms@gnu.org> writes:

>     > So is Ctrl-C/V/X really part of CUA at all?
>
>     If you enable CUA mode it is :-)
>
> There is a miscommunication here.  He is not asking about the Emacs
> CUA mode.  He's asking about what was in the spec that the MS Windows
> designers started with.

I did understand that ... it was a joke!

>
> Lennart Borgman wrote:
>
>     I found someone saying that is was added in CUA 2.0. I have a vauge 
>     memory of seeing something like that before too.
>
> If that is true, what was the date of CUA 2.0?  And did MS Windows
> copy those commands from CUA 2.0?

Why does it matter whether it was IBM, Apple or M$ who invented the
C-z C-x C-c C-v shortcuts (and thus broke compatibility with Emacs)?

No matter what we think or feel, or whether history is on our side,
most "modern" applications use these bindings -- including GNOME, KDE
and Firefox, so today it is Emacs which is "incompatible" with "common
practice".

That's a fact, and trying to blame "the designers of CUA" for creating
a consistent (and IMHO excellent) interface is plain silly IMO.

So for users who like the consistency with their other application,
Emacs 22 has CUA mode which provide the functionality without
breaking existing Emacs bindings.

So IMO (but I'm biased of course), there's no reason to have a
negative attitude towards CUA at all -- if people like those bindings,
just use them.  And that's it.

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

  reply	other threads:[~2007-01-05 13:39 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1H1qoi-0001av-Hq@monty-python.gnu.org>
2007-01-02 22:00 ` Emacs-diffs Digest, Vol 50, Issue 7 Eli Zaretskii
2007-01-02 22:28   ` Juanma Barranquero
2007-01-02 23:02   ` Lennart Borgman (gmail)
2007-01-03  3:46   ` Nick Roberts
2007-01-03 13:05   ` Kim F. Storm
2007-01-03 14:07   ` Jason Rumney
2007-01-03 15:54     ` Kim F. Storm
2007-01-03 18:23       ` Eli Zaretskii
2007-01-04  2:31     ` Richard Stallman
2007-01-04  4:33       ` Michael Welsh Duggan
2007-01-04  7:30         ` David Kastrup
2007-01-04  9:28           ` Kim F. Storm
2007-01-04 10:24             ` David Kastrup
2007-01-04 11:35         ` Jan Djärv
2007-01-04 12:25           ` Kim F. Storm
2007-01-04 12:49             ` Lennart Borgman (gmail)
2007-01-04 22:34             ` Richard Stallman
2007-01-05 13:39               ` Kim F. Storm [this message]
2007-01-06  2:55                 ` Richard Stallman
2007-01-06 23:55                   ` Juri Linkov
2007-01-07 23:23                   ` Kim F. Storm
2007-01-07 23:56                     ` Stefan Monnier
2007-01-08  0:16                       ` Drew Adams
2007-01-08 15:35                       ` Kim F. Storm
2007-01-08 18:24                         ` David Kastrup
2007-01-08 21:10                           ` Kim F. Storm
2007-01-08 19:46                     ` Richard Stallman
2007-01-04 22:33         ` Richard Stallman
2007-01-04  8:08       ` Jason Rumney
2007-01-03 21:11   ` Richard Stallman
2007-01-09  0:05 kevin.gal
2007-01-09  1:16 ` Chris Moore
2007-01-11  2:16   ` Kevin Gallagher
2007-01-11 16:49     ` Richard Stallman
2007-01-11 17:46       ` Peter Whaite
2007-01-11 17:55         ` tomas
2007-01-11 18:35           ` Stuart D. Herring
2007-01-14 20:46         ` Richard Stallman

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=m3slepfv9k.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=jasonr@gnu.org \
    --cc=md5i@cs.cmu.edu \
    /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.