From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: Glenn Morris <gmorris@ast.cam.ac.uk>
Subject: Re: Emacs-diffs Digest, Vol 6, Issue 5
Date: Sat, 03 May 2003 11:15:16 +0300 [thread overview]
Message-ID: <8011-Sat03May2003111515+0300-eliz@elta.co.il> (raw)
In-Reply-To: <E19BiZh-00012A-00@monty-python.gnu.org> (emacs-diffs-request@gnu.org)
Glenn, I have a few comments regarding the last changes in the FAQ.
> + Sometimes users are unsure as to where their @file{.emacs} file should
> + be found. Visiting the file as @file{~/.emacs} from Emacs will find
> + the correct file.
I think every useful piece of information in the FAQ should be
indexed. A FAQ, even more than a manual, is a large collection of
small pieces of information, so it is practically impossible to
quickly get to the info one is looking for without that info being
indexed. The above snippet should certainly have an index entry,
IMHO.
> + The version available from @uref{http://meltin.net/hacks/emacs/} is
> + more recent, and has been tested under Emacs 21.2.
I think "under Emacs" sounds awkward. "has been tested with Emacs
21.2" is better, in my opinion.
> ! The Emacs Lisp List (ELL),
> ! @uref{http://www.anc.ed.ac.uk/~stephen/emacs/ell.html}, maintained by
I think it's better to use @uref with 2 arguments here, like this:
@uref{http://www.anc.ed.ac.uk/~stephen/emacs/ell.html, The Emacs
Lisp List (ELL)}, maintained by
The results will look better in HTML, for example.
> ! internet. The ELL can be browsed over the web, or from Emacs using the
> ! @file{ell} package, @uref{http://www.anc.ed.ac.uk/~stephen/emacs/ell.el}.
Same here: make "@file{ell} package" be part of @uref.
> ! Many authors post their packages to the newsgroup
> ! @uref{news:gnu.emacs.sources}.
And here. I'd rewrite this as
Many authors post their packages to the @uref{news:gnu.emacs.sources,
Emacs sources news group}.
There are more such instances in the changes; I think almost all of
them should be revised as above.
> ! For a long time, the Emacs Lisp Archive provided a central repository
> ! for Emacs packages. Sadly, it has not been active for some time,
> ! although you can still access the old files at
This should probably have an index entry, about the archive being
unmaintained.
> ! * AUC-TeX::
> * BBDB::
> * Ispell::
> * w3-mode::
> --- 3874,3880 ----
> * Supercite::
> * Calc::
> * VIPER::
> ! * AUCTeX::
Isn't "AUC-TeX" the official spelling of the package, as Per wants it?
Last, but not least, thanks for working on these changes!
next parent reply other threads:[~2003-05-03 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E19BiZh-00012A-00@monty-python.gnu.org>
2003-05-03 8:15 ` Eli Zaretskii [this message]
2003-05-03 12:26 ` Emacs-diffs Digest, Vol 6, Issue 5 Glenn Morris
2003-05-03 17:57 ` extended @uref command? (was: Emacs-diffs Digest, Vol 6, Issue 5) Reiner Steib
2003-05-03 18:55 ` Eli Zaretskii
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=8011-Sat03May2003111515+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=gmorris@ast.cam.ac.uk \
/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).