unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: 14804@debbugs.gnu.org
Subject: bug#14804: Gnus spelling fix: unexist -> nonexistent
Date: Mon, 08 Jul 2013 19:27:09 -0700	[thread overview]
Message-ID: <51DB74FD.1090507@cs.ucla.edu> (raw)
In-Reply-To: <m3a9lxf6ga.fsf@stories.gnus.org>

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.

Emacs source code should avoid misspellings even in
comments and in symbols used only internally.  This is
because the misspellings can cause confusion among
developers, who are the main audience for the code.

I could mark "unexist" as a word that is allowed to be
in Emacs source code and documentation -- but then that word
is more likely to slip into places where it's not wanted.

> Calling them `gazonk' instead of `unexist' makes as much sense.

Actually, it'd make more sense to call them 'gazonk'.

When I look for spelling errors, my heuristics ignore
strings like 'gazonk' -- which are obviously intended
and are unlikely to cause confusion or inconsistencies --
and focus on strings like 'unexist' and 'inaccessable'
and 'chedule' because they look more like English words
and so are more likely to cause confusion.

I could change 'unexist' to 'gazonk', if you like.
That would be better to what we have now, for the
reasons mentioned above.  Still, as long as we're
changing it, why not to the usual word?





  reply	other threads:[~2013-07-09  2:27 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 [this message]
2013-07-09 13:42         ` Ted Zlatanov
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

  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=51DB74FD.1090507@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=14804@debbugs.gnu.org \
    --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 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).