emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs-diffs Digest, Vol 50, Issue 7


From: Eli Zaretskii
Subject: Re: Emacs-diffs Digest, Vol 50, Issue 7
Date: Wed, 03 Jan 2007 00:00:05 +0200

IMO this change in the manual of the text I wrote is ridiculous:

> --- msdog.texi        27 Dec 2006 12:49:00 -0000      1.64
> +++ msdog.texi        2 Jan 2007 21:00:44 -0000       1.65
> @@ -334,11 +334,14 @@
>  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},
> address@hidden, 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
> address@hidden@key{SPC}}.  You can redefine some of them with meanings more
> +like the MS-Windows meanings by enabling CUA Mode (@pxref{CUA
> +Bindings}).

The original text was completely neutral, whereas the new one is so
grotesque that it's at best suitable for anti.texi, and at worst is an
insult to the reader's intelligence.

To add insult to injury, the ChangeLog entry accuses me of being
lopsided towards Windows:

        * msdog.texi (Windows Keyboard): Explain that Windows was incompatible
        with Emacs, not vice versa.

Such incidents make me wonder why I still spend almost all my free
time working on Emacs, if what I get in return is this kind of
rudeness.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]