From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Alan Schmitt <alan.schmitt@polytechnique.org>, emacs-orgmode@gnu.org
Cc: "Thomas S. Dye" <tsd@tsdye.com>
Subject: Re: Org Tutorials need more structure
Date: Tue, 1 Oct 2013 07:34:14 +0200 [thread overview]
Message-ID: <20131001053414.GA2622@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <8761tiuttm.fsf@ucl.ac.uk>
Hi Alan, Eric, Thomas, and others,
On Mon, Sep 30, 2013 at 06:01:57PM +0100, Eric S Fraga wrote:
> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
> > fatkasuvayu+linux@gmail.com writes:
> >
> >> To me the best way to describe Org is: a programmable and dynamic
> >> plain-text note taking platform.
> >
> > I really like this description. Short, and to the point.
>
> but it's missing what for me is the key point which got me into org:
> time management! So how about
>
> a programmable and dynamic plain-text note taking time management platform
>
> but I'm sure somebody else will think something is missing and make
> this sentence even longer ;-)
I'm glad people seem to like it :). Although I would refrain from
extending that particular sentence. This is what was going through my
head:
1. What does an Org document look like? It is primarily a text outline.
2. Is there more to the outline? Well I can:
- export it,
- put metadata on it, like: timestamps, clocks, etc,
- put TODO markers on it, ... and so on
3. What about the text (content)? It is really just text, but supports
a few nifty things.
- Links to other documents, other applications, executable lisp, etc.
- It also supports nifty formatting and structural markup.
- Tables with a deceptively advanced math engine underneath to do
spreadsheet tasks.
- Source blocks, optionally which can be evaluated and can interact
with other text content in the Org file: tables, other source
blocks, etc.
But then I thought, "Hmm, I can't put all that." So what is at the
core? Outline with text, lets just call that notes. And all the cool
features? I can use special markup to add enhance the text, aggregate
and filter it, and present it in many ways; that is quite dynamic. I
can also program it in pretty much any language.
Hence: Org is a programmable and dynamic note taking platform.
This still does not do justice, so lets put in supporting follow-up
sentences highlighting my favourite bits.
Hence my following sentence: All its features are essentially built on
this ability: planning & task management, authoring or publishing,
literate programming, and what not.
Now others can tack on a description for their favourite bit of Org as
supporting sentences. Anyway, I thought clarifying my thoughts would
help improve the discussion.
Hope this helps,
:)
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2013-10-01 5:34 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
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 [this message]
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=20131001053414.GA2622@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.com \
/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).