From: Richard Copley <rcopley@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: simonfv@gmail.com, Emacs Development <emacs-devel@gnu.org>,
Richard Stallman <rms@gnu.org>,
nikolay.kudryavtsev@gmail.com, Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: emacs-losedows-builder
Date: Fri, 2 Sep 2016 18:44:28 +0100 [thread overview]
Message-ID: <CAPM58oj_5J_b=+HXHKBSRiqBOCDNrFrEebKvEYZU_vjCQERtTw@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY2MUu8pAZzH36oknLf7iaOj4Qy=D9YDZf2O0EENPv5fxA@mail.gmail.com>
On 2 September 2016 at 15:15, Kaushal Modi <kaushal.modi@gmail.com> wrote:
>
>
> On Fri, Sep 2, 2016, 7:12 AM Richard Stallman <rms@gnu.org> wrote:
>>
>> Or perhaps
>> you think of Microsoft as a competitor that deserves respect, rather
>> than as an enemy that has subjugated millions of people.
>
>
> Actually before you brought this up, I never thought of the "win" part in
> Windows could mean any respect at all. "Win" gives a positive message
> probably just in English language and happens to be the first part of the
> word windows. This kind of micro-digging to find ways of name calling the
> competitor does not suit well to our community. If we should find and
> advertise tangible reasons to why we are better than the competitor.
>
> For all many would care, windows might as well be foodows, and the code in
> the patch used foo- instead of win-. That "win-" part means nothing else
> than happening to be the first part of Windows. Victory flags do not go
> waving in my mind when I read some code with "win-". I believe such trivial
> refactoring feedback would be demoralizing to contributors.
I agree. The ancestor of the word "window" came from words meaning
"wind" and "eye", according to the OED, but it's natural and near-universal
to treat it as an atomic unit.
There's no particular need to use "win" as an abbreviation and it's not
very pleasing, so I don't mind trying to avoid it. The exception is when
referring to Win32 (the subsystem, the API or whatever). That's its name
and it's silly to call it anything else.
> But I agree with the similar change suggested by Glenn on the grounds of
> coding consistency.
next prev parent reply other threads:[~2016-09-02 17:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 19:47 emacs-win-builder Nikolay Kudryavtsev
2016-08-31 14:17 ` emacs-win-builder Eli Zaretskii
2016-09-01 12:39 ` emacs-win-builder Nikolay Kudryavtsev
2016-09-01 14:05 ` emacs-win-builder Eli Zaretskii
2016-08-31 21:45 ` emacs-losedows-builder Richard Stallman
2016-09-01 8:37 ` emacs-losedows-builder Simon Friis Vindum
2016-09-01 18:54 ` emacs-losedows-builder Richard Stallman
2016-09-01 23:17 ` emacs-losedows-builder Dmitry Gutov
2016-09-02 1:36 ` emacs-losedows-builder Paul Eggert
2016-09-12 17:14 ` emacs-losedows-builder Nikolay Kudryavtsev
2016-09-02 13:10 ` emacs-losedows-builder Richard Stallman
2016-09-02 13:19 ` emacs-losedows-builder Dmitry Gutov
2016-09-02 14:15 ` emacs-losedows-builder Kaushal Modi
2016-09-02 17:44 ` Richard Copley [this message]
2016-09-03 12:02 ` emacs-losedows-builder Richard Stallman
2016-09-04 6:51 ` emacs-losedows-builder Tim Cross
2016-09-04 13:48 ` emacs-losedows-builder Richard Stallman
2016-09-02 18:46 ` emacs-losedows-builder Richard Stallman
2016-09-02 20:12 ` emacs-losedows-builder Emanuel Berg
2016-09-02 1:05 ` emacs-losedows-builder John Wiegley
2016-09-01 12:44 ` emacs-losedows-builder Nikolay Kudryavtsev
2016-09-01 18:55 ` emacs-losedows-builder Richard Stallman
2016-09-12 17:43 ` emacs-losedows-builder Nikolay Kudryavtsev
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='CAPM58oj_5J_b=+HXHKBSRiqBOCDNrFrEebKvEYZU_vjCQERtTw@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=nikolay.kudryavtsev@gmail.com \
--cc=rms@gnu.org \
--cc=simonfv@gmail.com \
/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).