From: storm@cua.dk (Kim F. Storm)
Cc: jasonr@gnu.org, rms@gnu.org, emacs-devel@gnu.org,
md5i@cs.cmu.edu, eliz@gnu.org, jan.h.d@swipnet.se
Subject: Re: Emacs-diffs Digest, Vol 50, Issue 7
Date: Mon, 08 Jan 2007 16:35:11 +0100 [thread overview]
Message-ID: <m33b6lilao.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <jwvbqlatmup.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun\, 07 Jan 2007 18\:56\:19 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> a historical accident.
The current text suggests it was done deliberately:
Many key combinations (known as ``keyboard shortcuts'') that have
conventional uses in MS-Windows programs conflict with traditional
Emacs commands. This conflict arose because the designers of the CUA
interface implemented by MS-Windows did not try to avoid conflict with
Emacs.
The second sentense is superfluous at best.
The text continues:
Examples of conflicts include @kbd{C-c}, @kbd{C-x}, @kbd{C-z},
@kbd{C-a}, and @kbd{W-@key{SPC}}. You can redefine some of them with
meanings more like the MS-Windows meanings by enabling CUA Mode
(@pxref{CUA Bindings}).
As I've tried to say, the CUA (or rather C-[zxcv]) bindings are
no longer MS-Windows specific ... the text could just as well
have said GNOME [in a non-MS-DOG context].
Also the text is overly cryptic ... why not just say:
You can resolve these conflicts by enabling CUA Mode.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2007-01-08 15:35 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
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 [this message]
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
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=m33b6lilao.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 \
--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).