From: "D. Goel" <deego@glue.umd.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Which files to proofread
Date: 17 Aug 2002 23:06:09 -0400 [thread overview]
Message-ID: <ap3ofc0amse.fsf@z.glue.umd.edu> (raw)
In-Reply-To: <200208121705.g7CH5nK06505@wijiji.santafe.edu>
I read through glossary.texi and found no inaccuracies or bugs[1].
combining this with Harald's mails, these are the files remaining. So,
folks, please help out by reading through :-) some of the files
below. It was very entertaining and educational for me :)
Never-read files:
> abbrevs.texi ack.texi anti.texi basic.texi building.texi
> calendar.texi commands.texi display.texi doclicense.texi
> entering.texi files.texi fixit.texi frames.texi glossary.texi
> gnu.texi help.texi indent.texi m-x.texi macos.texi
> maintaining.texi major.texi mark.texi mini.texi misc.texi
> msdog.texi mule.texi picture.texi programs.texi regs.texi
> rmail.texi screen.texi search.texi sending.texi text.texi
> trouble.texi windows.texi xresources.texi
the following files have been read atleast once:
bufs.texi
cmdargs.texi
custom.texi
dired.texi
killing.texi
If you have proofread some other files, please follow up here, and
update the two lists above :)
[1] one minor thing: the entryfor SpellChecking says: Emacs
spellchecks using ispell. More accurately, it should be "By, default
....", since emacs can use aspell etc. But i don't make a big deal of
it. /me likes GNU's ispell :-)
DG
--
next prev parent reply other threads:[~2002-08-18 3:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 17:05 Which files to proofread Richard Stallman
2002-08-13 6:36 ` Harald.Maier.BW
2002-09-02 0:02 ` Richard Stallman
2002-09-02 5:14 ` Eli Zaretskii
2002-09-02 0:02 ` Richard Stallman
2002-09-07 10:58 ` Harald.Maier.BW
2002-08-18 3:06 ` D. Goel [this message]
2002-08-19 0:50 ` Richard Stallman
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=ap3ofc0amse.fsf@z.glue.umd.edu \
--to=deego@glue.umd.edu \
--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).