From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-pretest-bug@gnu.org
Subject: bug#1476: 23.0.60; spelling of (un)writeable should be (un)writable
Date: Wed, 03 Dec 2008 16:46:27 -0500 [thread overview]
Message-ID: <jwvej0pvsrr.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <?fnord?y3h6ljuxldvb.fsf@ID-97657.user.individual.net> (Lawrence Mitchell's message of "Wed, 03 Dec 2008 11:03:36 +0000")
> FWIW the OED says both are fine:
That doesn't make it undesriable to try and only use one of the two.
`grep' seems to indicate that `writable' is used a lot more right now
in Emacs. Google seems to think that the same is true for the part of
the Internet about which it cares.
So I agree that it's good to change occurences of "writeable" to
"writable".
It's not a high priority, tho. So let's only do it when it's easy and
harmless (e.g. not for global variables and things like that).
Stefan
prev parent reply other threads:[~2008-12-03 21:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <878wqykkb2.fsf@cyd.mit.edu>
2008-12-02 23:02 ` bug#1476: 23.0.60; spelling of (un)writeable should be (un)writable Drew Adams
2008-12-02 23:48 ` Stephen Berman
2008-12-03 3:35 ` bug#1476: marked as done (23.0.60; spelling of (un)writeable should be (un)writable) Emacs bug Tracking System
2008-12-03 11:03 ` bug#1476: 23.0.60; spelling of (un)writeable should be (un)writable Lawrence Mitchell
2008-12-03 13:43 ` Drew Adams
2008-12-03 14:00 ` Lawrence Mitchell
2008-12-03 15:00 ` bug#1476: 23.0.60; spelling of (un)writeable should be(un)writable Drew Adams
2008-12-03 14:08 ` bug#1476: 23.0.60; spelling of (un)writeable should be (un)writable Juanma Barranquero
2008-12-03 15:03 ` Drew Adams
2008-12-03 15:06 ` Juanma Barranquero
2008-12-03 15:25 ` Drew Adams
2008-12-03 14:13 ` Jason Rumney
2008-12-03 15:09 ` Drew Adams
2008-12-03 21:46 ` Stefan Monnier [this message]
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=jwvej0pvsrr.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=1476@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@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).