From: Ted Zlatanov <tzz@lifelogs.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, 14804@debbugs.gnu.org
Subject: bug#14804: Gnus spelling fix: unexist -> nonexistent
Date: Tue, 09 Jul 2013 09:42:30 -0400 [thread overview]
Message-ID: <87li5fvohl.fsf@lifelogs.com> (raw)
In-Reply-To: <51DB74FD.1090507@cs.ucla.edu> (Paul Eggert's message of "Mon, 08 Jul 2013 19:27:09 -0700")
On Mon, 08 Jul 2013 19:27:09 -0700 Paul Eggert <eggert@cs.ucla.edu> wrote:
PE> On 07/08/2013 07:54 AM, Lars Magne Ingebrigtsen wrote:
>> Anyway, I just don't see much of an upside to changing the what symbols
>> are used in internal data structures.
PE> Emacs source code should avoid misspellings even in
PE> comments and in symbols used only internally. This is
PE> because the misspellings can cause confusion among
PE> developers, who are the main audience for the code.
I disagree for internal symbols, and because IMHO this is not a
misspelling. There is very specific meaning to "unexist" that I can't
think of a way to convey easily by any other simple verbs.
PE> I could mark "unexist" as a word that is allowed to be
PE> in Emacs source code and documentation -- but then that word
PE> is more likely to slip into places where it's not wanted.
I don't think that's a huge risk.
Ted
next prev parent reply other threads:[~2013-07-09 13:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-06 9:41 bug#14804: Gnus spelling fix: unexist -> nonexistent Paul Eggert
2013-07-06 15:36 ` Lars Ingebrigtsen
2013-07-06 22:17 ` Paul Eggert
2013-07-08 14:54 ` Lars Magne Ingebrigtsen
2013-07-09 2:27 ` Paul Eggert
2013-07-09 13:42 ` Ted Zlatanov [this message]
2013-07-09 13:54 ` Juanma Barranquero
2013-07-09 14:13 ` Jambunathan K
2013-07-09 14:44 ` Juanma Barranquero
2013-07-09 16:21 ` Ted Zlatanov
2013-07-09 14:45 ` Paul Eggert
2013-07-09 16:22 ` Ted Zlatanov
2013-07-09 13:00 ` Wolfgang Jenkner
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=87li5fvohl.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=14804@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=larsi@gnus.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.