[Top][All Lists]

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

bug#10421: Don't use the abbreviation "win" to refer to Windows.

From: Daniel Colascione
Subject: bug#10421: Don't use the abbreviation "win" to refer to Windows.
Date: Mon, 02 Jan 2012 01:12:44 -0800
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0

On 1/1/12 10:45 PM, Paul Eggert wrote:
> I found several instances in the Emacs source code of its
> unnecessarily using the abbreviation "win" to refer to Windows.
> Here's a proposed patch.

This stance is ridiculous. As Eli mentioned elsewhere in the thread,
"Win32" is the most common name for the Windows desktop API. It's no
more an endorsement than "Scunthorpe" is an obscenity.

Furthermore, though the difference is not particularly relevant for
Emacs, "Win32" is more specific than "Windows API": the latter term
encompasses the Win16 API, Windows CE, and so on. "Win32" is exactly
the right term here. Eschewing it because it contains "win" is petty
and ridiculous.  Can I prepare a patch that introduces "Mac OS suX"
into the tree?

>  Depending on whether we are in arrange mode either:
> @@ -139,7 +139,7 @@
>  (defun ly-process-basic (body params)
>    "Execute a lilypond block in basic mode"
> -  
> +

Can we make whitespace changes separately?  Mixing whitespace cleanups
with (even marginally) more important changes makes commit history messy.

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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