From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: Procedure for changing the FAQ
Date: Wed, 23 Apr 2003 23:02:23 +0300 [thread overview]
Message-ID: <9743-Wed23Apr2003230222+0300-eliz@elta.co.il> (raw)
In-Reply-To: <uof2xs3vq.fsf@hschmi22.userfqdn.rz-online.de> (message from Frank Schmitt on Wed, 23 Apr 2003 16:08:25 +0200)
> From: Frank Schmitt <ich@Frank-Schmitt.net>
> Date: Wed, 23 Apr 2003 16:08:25 +0200
>
> I partly disagree, partly agree. First of all, the main documentation
> is huge and the answers to the questions especially newbies have are
> often in sections where they wouldn't expect them.
That's what the indexing is for, and the `i' command inside Info. We
should educate users to use that much more than they do, and we should
strive to make our indexing even better.
> Therefor a FAQ should explain all major concepts
I disagree: I think explaining major concepts is something the FAQ
should _not_ do; they are already explained in the manual.
Yes, I know many computer users are used to look in the FAQ before
they look in the manual, but I think we should convince Emacs users
that's not the right way of looking something up in the docs.
next prev parent reply other threads:[~2003-04-23 20:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 15:45 Procedure for changing the FAQ Glenn Morris
2003-04-23 10:15 ` Eli Zaretskii
2003-04-23 13:11 ` Stefan Monnier
2003-04-23 14:08 ` Frank Schmitt
2003-04-23 20:02 ` Eli Zaretskii [this message]
2003-04-23 22:31 ` Alex Schroeder
2003-04-24 6:03 ` Eli Zaretskii
2003-04-24 7:46 ` Kai Großjohann
2003-04-26 2:32 ` Richard Stallman
2003-04-26 21:24 ` Kai Großjohann
2003-04-28 4:38 ` Richard Stallman
2003-04-24 23:14 ` Richard Stallman
2003-04-23 18:48 ` Glenn Morris
2003-04-23 19:50 ` Eli Zaretskii
2003-04-23 18:37 ` Glenn Morris
2003-04-23 20:06 ` Eli Zaretskii
2003-04-24 12:44 ` Simon Josefsson
2003-04-23 20:40 ` Robert J. Chassell
2003-04-26 13:46 ` 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=9743-Wed23Apr2003230222+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--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).