From 668ef058b81aea2d1dd12f428a83078268240d67 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Tue, 2 Jan 2007 21:00:44 +0000 Subject: [PATCH] (Windows Keyboard): Explain that Windows was incompatible with Emacs, not vice versa. --- man/msdog.texi | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/man/msdog.texi b/man/msdog.texi index 69126dca207..a94fe7b7126 100644 --- a/man/msdog.texi +++ b/man/msdog.texi @@ -334,11 +334,14 @@ directory, whereas @file{.emacs} does not. keyboard input in Emacs. @cindex MS-Windows keyboard shortcuts - Many key combinations (known as ``keyboard shortcuts'') that are in -widespread use in MS-Windows programs are taken by various Emacs -features. Examples include @kbd{C-C}, @kbd{C-X}, @kbd{C-Z}, -@kbd{C-A}, and @kbd{W-SPC}. You can get some of them back by turning -on CUA Mode (@pxref{CUA Bindings}). + 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 Windows +did not concern themselves with how Emacs used these characters. +Examples 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}). @kindex F10 @r{(MS-Windows)} @cindex menu bar access using keyboard @r{(MS-Windows)} -- 2.39.2