From: GMX Christoph 13 <christoph-13@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: how do scientists use org mode?
Date: Fri, 3 Feb 2012 22:06:55 +0100 [thread overview]
Message-ID: <BE31FE9B-4A02-4F24-8F47-7EACE8F6CC0D@gmx.net> (raw)
Hi all
Real life took precedence for a while and also I realized that making the step towards org mode would be a rather more substantial leap than I had anticipated. Given how dissatisfied I had become with the more "traditional" solutions to the problem one would expect a shift in paradigms though.
This is to do more with the underlying emacs rather than org mode itself but sadly one cannot have one without the other. I hope that I will learn to appreciate one as well as the other but my previous exposure to emacs was limited to one mind-blowingly powerful major emacs mode which I treated strictly as a tool (RALEE by S. Griffiths-Jones), ignoring the emacs specifics for the most part. It seems that now is the time to dive into emacs for real, and org mode is the culprit...
At the moment decades of muscle memory get in the way in accomplishing even simple tasks, but Aquamacs provides some basic familiarity and alleviates at least some of the pain.
For the moment I will limit myself to one project notebook with embedded todos and go from there. This is BTW the main reason I asked for feedback from fellow scientists (no offense to anyone else). GTD and other task management systems are generally discussed in a way that implies that most tasks simply appear out of nowhere presumably from your superior hence little thought is devoted to WHY or even IF it should be done. The thing about science is that we tend to grow our ideas as well as create the market for them. I have no real experience in the corporate world, maybe there is a difference maybe not, but the context of tasks is very important hence the idea of having it available when needed but hidden when not required is one of the most appealing features of org mode for me now.
I will probably be around and asking silly questions for a while. Thanks for the friendly welcome and your constructive tips, all of which I studied most attentively but it may take a while.
May the force be with me :-)
Christoph
next reply other threads:[~2012-02-03 21:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 21:06 GMX Christoph 13 [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-26 21:21 how do scientists use org mode? GMX Christoph 13
2012-01-27 1:35 ` Thomas S. Dye
2012-01-27 17:07 ` Eric S Fraga
2012-01-27 18:27 ` John Hendy
2012-01-28 17:39 ` Tomas Grigera
2012-01-30 17:37 ` Christopher W. Ryan
2012-01-30 19:51 ` cberry
2012-01-31 19:20 ` Christopher W Ryan
2012-01-31 20:13 ` Thomas S. Dye
2012-02-02 17:19 ` Christopher W. Ryan
2012-01-31 19:58 ` Simon Thum
2012-02-02 4:25 ` Christopher W. Ryan
2012-02-02 5:10 ` Nick Dokos
2012-01-28 15:38 ` Bodhi
2012-02-01 8:41 ` Sven Bretfeld
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BE31FE9B-4A02-4F24-8F47-7EACE8F6CC0D@gmx.net \
--to=christoph-13@gmx.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.