From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: please. Hekp me to start
Date: Sat, 04 Jan 2014 12:06:08 -0500 [thread overview]
Message-ID: <87ppo77k3j.fsf@gmail.com> (raw)
In-Reply-To: 52C82815.8030203@gmail.com
Renato <renato.pontefice@gmail.com> writes:
> Hi,
> I know, ther's a lot of doc around there. But: can someone show me
> "the best" road map" to start using (and learning) org-mode?
>
Org is a swiss army knife: if you open up all the blades and try to use
them at once, you are going to hurt yourself.
Start with one or two things that are interesting to you and ignore
everything else: e.g. agenda and TODO lists for organizing your life;
writing up notes for latex or html export. I mention these two because
they account for about 95% of my personal usage, but you will have to
adjust to taste.
Resist the temptation to learn everything at once. Once you've used org
for a while for the things that matter to *you*, extensions and further
uses will come naturally.
For example, learning about tables comes naturally in the note-taking
process; then you learn about the spreadsheet and doing data analysis in
org; then you go on to babel and "reproducible" research. That might
lead to citations (a field of active research on the list
currently). Then you might want to publish your notes so others can read
them; or start a blog...
Or you decide to organize your life even more and start clocking all
your activities; track your habits; go on to quantify your life...
All of these things and more are possible with org, but just because
they are possible does not mean that you have to do them all (and
certainly not all at once) in order to use org productively.
Just remember: one blade at a time.
> I've past the few days, learning emacs, and now, I think I'm able to
> start using org-mode.
>
> TIA
>
> Renato
>
>
--
Nick
next prev parent reply other threads:[~2014-01-04 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 15:26 please. Hekp me to start Renato
2014-01-04 15:37 ` Bastien
2014-01-04 17:06 ` Nick Dokos [this message]
2014-01-19 16:55 ` Bernt Hansen
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=87ppo77k3j.fsf@gmail.com \
--to=ndokos@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).