From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Difficulty of using Org mode
Date: Tue, 5 Jun 2012 19:25:29 +0200 [thread overview]
Message-ID: <CAMXnza0p=gN-qkerb-2XpxpvCZpgugKB0KAOVFHGVhUVSg81+A@mail.gmail.com> (raw)
In-Reply-To: <t5xd35d7q3i.fsf@rgc.damtp.cam.ac.uk>
Hi,
On Tue, Jun 5, 2012 at 5:09 PM, Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk> wrote:
> I guess if you were to ask me what I found difficult, was that it was
> quite overwhelming knowing where to start. (So I started small by
> learning the agenda features...)
IMO the reason many have this problem because they think "I need to know
everything Org-mode can do" or "I want to customise Org-mode" from the
very beginning.
The way I went about it was to get an overview of the capabilities from
Worg and start using only the features I needed (in my case note taking
and export). As I became more familiar, I delved into other features
(like agenda, babel) and customisation of the already familiar features
(e.g. custom export hooks, personalised colour theme etc).
Idea: Maybe this could be a nice entry on the FAQ, "Where do I start?".
Maybe even a dedicated page on the Worg Index page. Any volunteers?
:)
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2012-06-05 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2mx4m6qb6.fsf@damtp.cam.ac.uk>
[not found] ` <CANROs4cfX6d6Xx-JhM+CfS4x5bt8eubKPqHFg3EdMh=MkbpjgA@mail.gmail.com>
[not found] ` <m2ehpxv7yw.fsf@damtp.cam.ac.uk>
[not found] ` <CANROs4eR9PC8DiwbNS2K6odWMHhCC1k4e3VfdReTmByqQ526Hg@mail.gmail.com>
2012-06-02 22:21 ` Difficulty of using Org mode Michael Hannon
2012-06-04 6:29 ` Bastien
2012-06-04 7:46 ` Michael Hannon
2012-06-05 15:09 ` Stephen Eglen
2012-06-05 17:25 ` suvayu ali [this message]
2012-06-06 16:48 ` Memnon Anon
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='CAMXnza0p=gN-qkerb-2XpxpvCZpgugKB0KAOVFHGVhUVSg81+A@mail.gmail.com' \
--to=fatkasuvayu+linux@gmail.com \
--cc=S.J.Eglen@damtp.cam.ac.uk \
--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).