From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Drew Adams" <drew.adams@oracle.com>, 1476@emacsbugs.donarmstrong.com
Cc: Lawrence Mitchell <wence@gmx.li>,
bug-gnu-emacs@gnu.org, emacs-pretest-bug@gnu.org
Subject: bug#1476: 23.0.60; spelling of (un)writeable should be (un)writable
Date: Wed, 3 Dec 2008 15:08:56 +0100 [thread overview]
Message-ID: <f7ccd24b0812030608m4fc07e60w4851d30d28bbc5dc@mail.gmail.com> (raw)
In-Reply-To: <007701c9554d$1a7619c0$0200a8c0@us.oracle.com>
On Wed, Dec 3, 2008 at 14:43, Drew Adams <drew.adams@oracle.com> wrote:
> It's about general usage, in practice. Whether "both are fine" is really beside
> the point.
Googling for "writable -writeable" gets about 2,6 Mhits, while
"writeable -writable" gets around 0,9 Mhits. Fewer, but still sizable.
I don't think anyone has trouble understanding "writeable".
Juanma
next prev parent reply other threads:[~2008-12-03 14:08 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 ` Juanma Barranquero [this message]
2008-12-03 15:03 ` bug#1476: 23.0.60; spelling of (un)writeable should be (un)writable 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=f7ccd24b0812030608m4fc07e60w4851d30d28bbc5dc@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=1476@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=wence@gmx.li \
/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.