From: "Allen S. Rout" <asr@ufl.edu>
To: emacs-orgmode@gnu.org
Subject: Re: would take more than an org-mode strip-down.
Date: Mon, 03 Oct 2011 16:44:20 -0400 [thread overview]
Message-ID: <4E8A1EA4.60107@ufl.edu> (raw)
In-Reply-To: <92B42F15-B849-473D-9E4C-F513A5DD80E8@me.com>
On 09/27/2011 01:04 PM, James Levine wrote:
> I thought I’d zoom out and tell you what a consumer experience is
> like:
I'm replying off the list. BTW, are you either The Conductor, or The
Author? ;)
Your experience seems to be informed by a sense that 'org-mode' is
eager for market share or some such. I think you'll find that's not a
common case. Certainly, org-mode afficionados are eager to expound on
their preferred tools; but that doesn't mean they're after mass-market
appeal.
For example:
> 2) Some things are just better with a gui.
to a project subtitled "Your life in plain text" suggests your
perspective is not aligned with that of many of the project
participants. I do not mean by this a disparagement of your
perspective, merely discriminating it from that of the average nerd.
Your composition style is literate and prolific; you might enjoy this
series of essays by Neal Stephenson, entitled "In the beginning was
the Command Line".
http://steve-parker.org/articles/others/stephenson/
(also available from the author's website in other formats)
http://www.cryptonomicon.com/beginning.html
but the discussion of 'fallibility...' includes several paragraphs
which I feel might be illuminating, especially on the topic of
documentation.
http://steve-parker.org/articles/others/stephenson/fallibility.shtml
In My Opinion, the current docs in org-mode are targeted at those who
expect to have their own heads and shoulders inside the 'engine
compartment' of org and emacs. This makes them a poor tool to
communicate with End-Users. But this might be acceptable, because
there's no hood on the engine, and the bloody thing is steered with a
rudder and laterals, instead of the nice sane wheel and pedals
everyone else uses. :)
- Allen S. Rout
next prev parent reply other threads:[~2011-10-03 20:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 17:04 would take more than an org-mode strip-down James Levine
2011-09-28 9:28 ` Jude DaShiell
2011-09-28 9:39 ` Eric S Fraga
2011-09-28 13:27 ` Jambunathan K
2011-09-28 14:18 ` Jambunathan K
2011-09-28 14:47 ` James Levine
2011-09-28 14:58 ` Jude DaShiell
2011-09-28 15:33 ` Russell Adams
2011-09-28 18:34 ` Rasmus
2011-09-28 14:54 ` James Levine
2011-09-30 6:00 ` Carsten Dominik
2011-09-30 9:38 ` Jambunathan K
2011-09-30 16:59 ` Thomas S. Dye
2011-10-04 0:13 ` suvayu ali
2011-10-03 20:44 ` Allen S. Rout [this message]
2011-10-04 13:28 ` Carson Chittom
-- strict thread matches above, loose matches on Subject: below --
2011-09-29 7:46 Rustom Mody
2011-09-29 7:57 ` Rustom Mody
2011-09-29 8:01 ` Rainer M Krug
2011-10-04 6:33 ` Rustom Mody
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E8A1EA4.60107@ufl.edu \
--to=asr@ufl.edu \
--cc=emacs-orgmode@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/org-mode.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).