From: Rainer M Krug <r.m.krug@gmail.com>
To: Rustom Mody <rustompmody@gmail.com>
Cc: levinejames@me.com, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: would take more than an org-mode strip-down.
Date: Thu, 29 Sep 2011 10:01:28 +0200 [thread overview]
Message-ID: <CAGhLh6EchcRiD7ySvHaghx6xtZGEf+5pbUvd4a4LyJ9Ejeg0Hg@mail.gmail.com> (raw)
In-Reply-To: <CAJ+TeofxSjMszgJgLJS3jkA420s4KQO9CuweRFQ+hDB=HAbckQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3556 bytes --]
On Thu, Sep 29, 2011 at 9:46 AM, Rustom Mody <rustompmody@gmail.com> wrote:
> Hi James.
>
> If you do not grok text its unlikely you will appreciate a text editor.
> emacs is not just a text editor its an exceptionally powerful text editor
> -- a power which is likely to alienate you even more.
> So the best suggestion to someone who wishes to get into orgmode but finds
> text (and text editors) unpleasant is to give up on orgmode, just dig into
> emacs' simpler uses for a while and when a little more comfortable (with
> emacs) try org again. Hopefully then your questions will be more focused to
> this list and the answers will be more useful to you.
>
> That said, there is some merit in (some of) what you say.
> org is so many different things at the same time that for a noob to find
> one's way through the documentation to make his usecase work with minimum
> pain seems to be unnecessarily hard.
>
>
> The beginner's customization guide:
> http://orgmode.org/worg/org-configs/org-customization-guide.html
> is of course a starting point.
>
> But I wonder if it would be possible to structure it into something like
> this outline so that different beginners could start at different places?
>
> * Brainstorming-n-outlining
> TAB and the basic structure navigation and editing features
> * Exporting and Publishing
> *** html export
> *** Odt export
> *** Web publishing
> *** Latex publishing
> *** Presentations
> ***** Lightweight options
> http://orgmode.org/worg/org-configs/org-customization-guide.html
> ***** Beamer
> * Babel
> *** For programming
> *** For teaching programming
> *** For doing science (R)
> *** For scientific publishing (R+Latex)
> * Time/project mgmt (GTD)
> *** Agenda
> *** Time tracking
> *** capture-archive
> *** Journalling
> *** org-habit
> * Tables and spreadsheets
> * Integration with other emacs uses
> *** gnus
> *** bbdb/ org-contacts
> *** firefox (org-protocol)
> *** graphics (R, ditaa...)
>
>
I would actually suggest to have a general introduction (what is org, what
can it do, what are the principles of org) and then go into different usage
scenarios and how to fulfill certain tasks. For example, I am using org-mode
exclusively for literate programming and some document writing, but not for
task management, calendar, email, etc. So at the beginning, I was really
confused by the whole agenda and publishing stuff, until I realized, that I
don't need it at all for what I am doing.
And after looking at your suggested outline, it is going into that
direction, but I would put e.g. "Exporting and Publishing" after the
different usage scenarios. so:
* Basic org
** what is it and what is it not
** what can it do
** principles and basics of org
*** org capture
* Usage scenarios
** Time Management
*** calendar
*** ...
** spreadsheets
*** ...
** task manager
** literate programming
*** general principles
*** examples for different programming languages
**** R
**** sh
**** ...
I like the headings "org for doing ...", but one has to be careful, that
they do not end uop in repeating to many things - so subheadings as links to
the relevant sections above would be quite useful.
Cheers,
Rainer
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax (F): +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: Rainer@krugs.de
Skype: RMkrug
[-- Attachment #2: Type: text/html, Size: 4324 bytes --]
next prev parent reply other threads:[~2011-09-29 8:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 7:46 would take more than an org-mode strip-down Rustom Mody
2011-09-29 7:57 ` Rustom Mody
2011-09-29 8:01 ` Rainer M Krug [this message]
2011-10-04 6:33 ` Rustom Mody
-- strict thread matches above, loose matches on Subject: below --
2011-09-27 17:04 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
2011-10-04 13:28 ` Carson Chittom
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=CAGhLh6EchcRiD7ySvHaghx6xtZGEf+5pbUvd4a4LyJ9Ejeg0Hg@mail.gmail.com \
--to=r.m.krug@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=levinejames@me.com \
--cc=rustompmody@gmail.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).