From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: typos
Date: Fri, 29 Nov 2002 10:03:44 -0500 [thread overview]
Message-ID: <E18HmgC-00027E-00@fencepost.gnu.org> (raw)
In-Reply-To: <20021127214742.A31191@creon.profinet.sk> (message from Adrian Mrva on Wed, 27 Nov 2002 21:47:43 +0100)
I looked through the list of typos. Most of them are
real errors and should be fixed as you said; here is
a list of the exceptions.
Would someone like to begin installing these fixes?
"Iff" is correct in general.
etc/ONEWS.1:
reeexutes -> re-executes
I would write it "reexecutes".
etc/ONEWS.3: nonrecomended -> non-recommended
I would write it "nonrecommended".
etc/SERVICE: satelliate -> satellite
The file etc/SERVICE is maintained separately.
nt/gmake.defs: hysterical -> historical
raisons -> reasons
These should be left unchanged.
lisp/double.el: iff -> if
lisp/ediff-diff.el: iff -> if
These should be left unchanged.
lisp/emacs-lisp/cl-indent.el: pprint-logical-block -> print-logical-block
pprint-logical-block is correct, as someone pointed out.
lisp/emacs-lisp/easymenu.el: Memoize -> Memorize
Memoize is correct.
lisp/emacs-lisp/elint.el: Augment -> Argument
Augment is correct.
lisp/emacs-lisp/find-func.el: ananother -> an another
It should be just "another".
lisp/loaddefs.el: charater -> character
varaibles -> variables
Don't bother with loaddefs.el; it is copied from other files.
digrams -> diagrams
"Digrams" is correct.
lisp/log-edit.el: iff -> if
memoizing -> memorizing
"Iff" and "memoizing" are correct.
lisp/obsolete/sun-fns.el: Slymoblics -> Symbolics
It should be Slymebolics.
lisp/progmodes/sh-script.el: (easy-mmode-defsyntax -> (easy-mode-defsyntax
This should not be changed.
prev parent reply other threads:[~2002-11-29 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 20:47 typos Adrian Mrva
2002-11-27 21:27 ` typos Jason Rumney
2002-11-28 2:44 ` typos John Paul Wallington
2002-11-28 6:05 ` typos Adrian Mrva
2002-11-29 15:03 ` Richard Stallman [this message]
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=E18HmgC-00027E-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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 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).