From: Lawrence Mitchell <wence@gmx.li>
To: bug-gnu-emacs@gnu.org
Cc: emacs-pretest-bug@gnu.org
Subject: bug#1476: 23.0.60; spelling of (un)writeable should be (un)writable
Date: Wed, 03 Dec 2008 11:03:36 +0000 [thread overview]
Message-ID: <?fnord?y3h6ljuxldvb.fsf@ID-97657.user.individual.net> (raw)
In-Reply-To: 001601c954d2$1362b0b0$0200a8c0@us.oracle.com
Drew Adams wrote:
> Emacs manual, node Directory Variables.
> Please change "unwriteable" to "unwritable".
> Not very important, since this is just an invented name in an example,
> but it can lead users to think that's the spelling and thus to look
> for such a term in the future. Googling shows that similar bugs have
> been logged for Scheme, Python, man pages, and elsewhere.
FWIW the OED says both are fine:
writable, a.
Also writeable.
Lawrence
--
Lawrence Mitchell <wence@gmx.li>
next prev parent reply other threads:[~2008-12-03 11:03 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 ` Lawrence Mitchell [this message]
2008-12-03 13:43 ` bug#1476: 23.0.60; spelling of (un)writeable should be (un)writable 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='?fnord?y3h6ljuxldvb.fsf@ID-97657.user.individual.net' \
--to=wence@gmx.li \
--cc=1476@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.