From: Evans Winner <thorne@timbral.net>
To: help-gnu-emacs@gnu.org
Subject: Re: problem with emacs wiki
Date: Tue, 10 Jun 2008 20:55:48 -0600 [thread overview]
Message-ID: <86fxrk65or.fsf@timbral.net> (raw)
In-Reply-To: f5cbd995-768a-41fd-96f3-d7f91a3ac184@w1g2000prd.googlegroups.com
Xah <xahlee@gmail.com> writes:
[The Emacs tutorial was] written in 1980's mindset [...]
It is not [...] practicality oriented[.]
Can you explain exactly what that means? I live in the
2000's and, though it's been a few years since I went
through the tutorial, I don't recall reading anything that
did not seem clearly focused on the specific and practical
realities of how to use the Emacs editor. Or is your
criticism really of Emacs itself?
The emacs manual is a bit quaint in today, but it is
very well written and complete. It is systematic, topics
well organized, jargons are well defined and has several
comprehensive index, the writing is clear, is well
cross-linked.[...] The writing quality and content of
emacs manual, is far better than most OpenSource docs
such as perl, python, apache, unix man.
What precisely do you mean by the term ``quaint?'' Given
your own description, ``quaint'' does not seem the
appropriate term. Terms like ``intelligent'' and
``professional'' leap to mind instead. I have found the
Emacs documentation and its integration and availability or
``discoverability'' the best of any computer system, program
or programming language I have ever dealt with.
The wiki software used is Oddmuse [on EmacsWIki], which
is a perl script of 4k lines, using flat files as
database. As such, it is not comprehensive or powerful.
I don't know much about wiki software. What kind of
features are you missing specifically? You mentioned
discussing this with Alex Schröder; what did he say about
your suggestions?
I also suggested that the writing guidlines should
follow Wikipedia's style. Specifically, the content
editing should be one with the goal of creating a
comprehensive, coherent, article that gives readers info
or tutorial about the subject. (as opposed to,
maintaining the coherence of a dialogue and comments
between wiki users)
Guidelines such as those used by Wikipedia might have some
positive effect on the content that is added to the wiki,
however Wikipedia has the key to really making something
like that work: an army of busybodies ready to enforce the
guidelines. EmacsWiki (I suspect) does not have such
resources. It is arguable that strict guidelines on
EmacsWiki would have a dampening effect on the frequency of
contributions, which I would guess is not the goal of its
maintainers. In some contexts a slightly anarchic and
disorganized something is better than a tightly organized
nothing.
next prev parent reply other threads:[~2008-06-11 2:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.11479.1210553320.18990.help-gnu-emacs@gnu.org>
2008-05-12 14:17 ` What alternatives are there to learn Emacs? Mike Treseler
2008-05-12 20:31 ` Drew Adams
[not found] ` <mailman.11528.1210624366.18990.help-gnu-emacs@gnu.org>
2008-06-10 16:51 ` David Combs
2008-06-10 21:43 ` Xah
2008-06-10 23:13 ` problem with emacs wiki (was: What alternatives are there to learn Emacs?...) Xah
2008-06-11 2:39 ` tyler
2008-06-11 2:55 ` Evans Winner [this message]
2008-06-11 8:25 ` problem with emacs wiki Xah
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=86fxrk65or.fsf@timbral.net \
--to=thorne@timbral.net \
--cc=help-gnu-emacs@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.
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).