From: Alex Schroeder <alex@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Procedure for changing the FAQ
Date: Thu, 24 Apr 2003 00:31:22 +0200 [thread overview]
Message-ID: <877k9kn8w5.fsf@gnu.org> (raw)
In-Reply-To: <9743-Wed23Apr2003230222+0300-eliz@elta.co.il> (Eli Zaretskii's message of "Wed, 23 Apr 2003 23:02:23 +0300")
"Eli Zaretskii" <eliz@elta.co.il> writes:
> 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.
I used to (silently) disagree with Eli on this one, but these days I
agree. If people have questions they need answers to, and they can't
find it in the manual, then the manual needs to be changed. Maybe new
text needs to be written, or maybe new features need to be added. The
index search is a prime example. It is very powerful, and I only
learnt about it years after starting to use Emacs. The glossary is
another example, if I remember correctly it was added because people
using Microsoft terms were unable to find the correct information in
the manual. Perhaps we need "dedicated" pages in the manual. Mail
setup. Indentation. Just to name the two most commonly asked
questions on #emacs. :)
The wiki tries to do this kind of thing, of course, but by its very
nature the pages have varying levels of quality, and include personal
assessments of various solutions. This is a good thing, and a new
thing that was not possible before, but it also means that you cannot
just take text from the wiki and incorporate it into the manual.
Perhaps the wiki is an interesting collection of loosely organized
information so that we could pack it into a texinfo file and
distribute it the same way we used to distribute the manuals in the
old days... That might be an interesting alternative.
The wiki is licensed under the FDL, but no copyright assignments were
required of contributors. There used to be a script that translated
the entire site to a texinfo file, but it needs updating. Bitrot. :)
Alex.
next prev parent reply other threads:[~2003-04-23 22:31 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
2003-04-23 22:31 ` Alex Schroeder [this message]
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=877k9kn8w5.fsf@gnu.org \
--to=alex@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).