From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 14804@debbugs.gnu.org
Subject: bug#14804: Gnus spelling fix: unexist -> nonexistent
Date: Mon, 08 Jul 2013 16:54:13 +0200 [thread overview]
Message-ID: <m3a9lxf6ga.fsf@stories.gnus.org> (raw)
In-Reply-To: <51D8977B.2060009@cs.ucla.edu> (Paul Eggert's message of "Sat, 06 Jul 2013 15:17:31 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> On 07/06/2013 08:36 AM, Lars Ingebrigtsen wrote:
>> `unexist' has been in use for a couple of years, so this would break
>> people's Gnus files.
>
> Sorry, I thought 'unexist' was a more recent edition. In that case,
> how about if gnus-clean-old-newsrc automatically updates the old Gnus
> files from 'unexist' to 'nonexistent'? The code already does that for
> the old bad seplling 'unexists', so there's precedent for fixing
> spelling in this area.
Yeah, but `unexists' didn't last that long. :-)
Anyway, I just don't see much of an upside to changing the what symbols
are used in internal data structures. Calling them `gazonk' instead of
`unexist' makes as much sense. So there's a downside (people flipping
back and forth between versions will have to resync stuff), and the
upside remains to be demonstrated.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2013-07-08 14:54 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 [this message]
2013-07-09 2:27 ` Paul Eggert
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=m3a9lxf6ga.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=14804@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).