From: Rainer M Krug <r.m.krug@gmail.com>
To: Rustom Mody <rustompmody@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Org expert mode?
Date: Thu, 10 Mar 2011 14:44:57 +0100 [thread overview]
Message-ID: <AANLkTim3BqDyTQb3EZ6EfQaz20Y1+feiecb0+=U9xjyC@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=pZ-pZpz9DY0bTN7MZcoLevKRfzub6h_1rJ7Ss@mail.gmail.com>
On Thu, Mar 10, 2011 at 2:12 PM, Rustom Mody <rustompmody@gmail.com> wrote:
> Bastien wrote:
>> I've just added the ability to run a custom function for bulk agenda actions (thanks to Puneeth for the patch!) This is clearly for
>> power users -- or those who are willing to take the time to find functions that we might document in Worg.
>
>> So I naturally thought of something like an "Org Expert mode": when turned off, the UI would *not* give access to complex features
>> and perhaps display more helpful messages on simple ones; when turned on, Org would have a less verbose UI (think of the C-c C-e
>> window, do we really want to *read* it all the times?) and give access to all the complex features.
>
> Org is a large and diverse system and something to help (us perennial
> :-) newbies is always welcome.
>
> But I wonder if there are really too many experts as against users
> whose patterns of usage are expert in one area and noob in others.
> For example consider: Using org for:
> * Brainstorming
> * GTD, mobile org
> * Publishing
> * Literate Programming (via babel)
> * Statistical analysis (spreadsheet, R)
>
> Is it not likely that most people are going to be expert in (at most)
> a few of these and not really expert in the others?
I completely agree - and that is the direction my suggestion is aiming at.
Somebody using org mode for literate programming might be an expert in
literal programming with R, but no idea (yet?) about GTD and mobile
org.
So a system which provides usage pattern specific menues and enabled /
disabled functions, would be from my point of view the perfect
solutions.
And if this could be set on a file basis, that would even be better.
Rainer
>
>
--
NEW GERMAN FAX NUMBER!!!
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa
Cell: +27 - (0)83 9479 042
Fax: +27 - (0)86 516 2782
Fax: +49 - (0)321 2125 2244
email: Rainer@krugs.de
Skype: RMkrug
Google: R.M.Krug@gmail.com
next prev parent reply other threads:[~2011-03-10 13:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 13:12 Org expert mode? Rustom Mody
2011-03-10 13:44 ` Rainer M Krug [this message]
2011-03-10 14:11 ` Matthew Sauer
2011-03-10 22:37 ` Christian Moe
-- strict thread matches above, loose matches on Subject: below --
2011-03-10 10:05 Bastien
2011-03-10 10:11 ` Bastien
2011-03-10 10:36 ` Rainer M Krug
2011-03-20 2:08 ` Matt Lundin
2011-03-21 7:25 ` Rainer M Krug
2011-03-10 12:38 ` Greg Troxel
2011-03-10 14:14 ` John Hendy
2011-03-10 10:35 ` Filippo A. Salustri
2011-03-10 15:30 ` Julien Danjou
2011-03-10 17:43 ` Scott Randby
2011-03-10 18:46 ` Samuel Wales
2011-03-10 23:46 ` Suvayu Ali
2011-03-10 19:33 ` Robert Pluim
2011-03-10 21:25 ` Joost Helberg
2011-03-10 21:41 ` Eric Schulte
2011-03-10 23:22 ` Bernt Hansen
2011-03-11 8:28 ` Bastien
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='AANLkTim3BqDyTQb3EZ6EfQaz20Y1+feiecb0+=U9xjyC@mail.gmail.com' \
--to=r.m.krug@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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 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.