From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org Tutorials need more structure
Date: Sun, 29 Sep 2013 09:28:01 +0200 [thread overview]
Message-ID: <20130929072801.GS12411@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <CA+M2ft9bph7RiTmYYQrSPv7aih5D=4O623sZtGhZqd4YOT0WQA@mail.gmail.com>
Hi,
On Sat, Sep 28, 2013 at 07:29:26PM -0500, John Hendy wrote:
> On Sat, Sep 28, 2013 at 6:29 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
> >
> > In this vein, I think it would be useful to have a brief statement about
> > Org-mode that gives the interested reader from any background a good
> > feel for the scope of Org-mode and how it presents itself to the user.
> > I don't think the current statements about what Org-mode "is" do this
> > very effectively, though they might have done so in the past.
> >
>
> Absolutely love that, and this puts some of your earlier comments in
> perspective -- you're looking for the 30sec elevator pitch for
> Org-mode, and saying "this outline-y task manager" is not cutting it.
To me the best way to describe Org is: a programmable and dynamic
plain-text note taking platform. All its features are essentially built
on this ability: planning & task management, authoring or publishing,
literate programming, and what not. On top of this, it can interact
with external applications for tasks like referencing (links, citation,
etc). Of course trying to faithfully outline this in a few words is a
herculean task.
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2013-09-29 7:28 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-28 6:11 Org Tutorials need more structure Carsten Dominik
2013-09-28 7:22 ` Joseph Vidal-Rosset
2013-09-28 8:37 ` Marcin Borkowski
2013-09-28 10:30 ` Suvayu Ali
2013-09-28 11:59 ` Joseph Vidal-Rosset
2013-09-28 12:36 ` Eric Schulte
2013-09-28 13:10 ` Joseph Vidal-Rosset
2013-09-28 16:02 ` Suvayu Ali
2013-09-28 17:19 ` Joseph Vidal-Rosset
2013-10-01 7:59 ` Eric S Fraga
2013-10-01 20:34 ` David Rogers
2013-10-01 21:00 ` Marcin Borkowski
2013-09-28 8:48 ` Marcin Borkowski
2013-09-28 10:09 ` Carsten Dominik
2013-09-28 14:26 ` Charles Millar
2013-09-28 16:35 ` Carsten Dominik
2013-09-28 17:14 ` Ian Barton
2013-09-28 17:43 ` Marcin Borkowski
2013-09-28 17:48 ` Carsten Dominik
2013-09-28 19:06 ` Ramon Diaz-Uriarte
2013-09-28 19:52 ` Thomas S. Dye
2013-09-28 20:50 ` Charles Millar
2013-09-28 21:31 ` Marcin Borkowski
2013-09-28 21:52 ` John Hendy
2013-09-28 23:14 ` Charles Millar
2013-09-28 23:29 ` Thomas S. Dye
2013-09-29 0:29 ` John Hendy
2013-09-29 7:28 ` Suvayu Ali [this message]
2013-09-30 8:04 ` Alan Schmitt
2013-09-30 17:01 ` Eric S Fraga
2013-09-30 18:36 ` Peter Neilson
2013-09-30 21:07 ` Eduardo Ochs
2013-10-01 8:52 ` Michael Brand
2013-10-01 5:34 ` Suvayu Ali
2013-10-01 8:55 ` Marcin Borkowski
2013-10-01 12:40 ` Joseph Vidal-Rosset
2013-09-30 17:56 ` Thomas S. Dye
2013-09-29 8:44 ` Eric Abrahamsen
2013-09-29 15:31 ` Matt Price
2013-09-30 7:25 ` Eric Abrahamsen
2013-10-01 14:08 ` William Denton
2013-10-02 1:10 ` M
2013-10-02 18:06 ` Alan E. Davis
-- strict thread matches above, loose matches on Subject: below --
2013-09-29 16:43 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=20130929072801.GS12411@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--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).