emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Greg Troxel <gdt@ir.bbn.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org expert mode?
Date: Thu, 10 Mar 2011 07:38:41 -0500	[thread overview]
Message-ID: <rmi4o7bm9pq.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87hbbbe148.fsf@gnu.org> (Bastien's message of "Thu, 10 Mar 2011 11:11:35 +0100")

[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]


Bastien <bzg@altern.org> writes:

> Bastien <bzg@altern.org> writes:
>
>> So I naturally thought of something like an "Org Expert mode": when
>> turned off, the UI would *not* give access to complex features
>
> More precisely: the UI would not _display_ complex features, which will
> still be available anyway (of course).

I started using org only last summer, and found it a little daunting,
but reading the intro manual was easier than I thought.  There are lots
of complicated features, but I found it entirely easy to ignore
exporting, clocking, and many others.

Looking back, the hardest thing for a new person to learn is the
keybindings for scheduling, priorities, etc. in both the org mode view
and agenda view.

I don't see where having a mode to turn on and off would help any of
this.  I can sort of see the point about the export help, but I type
"C-e C-h h" so fast that it barely blinks by.  (Were I still on dialup I
would be cranky.)

Overall, I suggest enumerating what changes ought to be made for
non-expert mode, and then seeing if the complexity of having a mode is
really worth it, rather than inventing a mechanism and then looking for
ways to apply it.

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

  parent reply	other threads:[~2011-03-10 12:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 10:05 Org expert mode? 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2011-03-10 13:12 Rustom Mody
2011-03-10 13:44 ` Rainer M Krug
2011-03-10 14:11   ` Matthew Sauer
2011-03-10 22:37 ` Christian Moe

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=rmi4o7bm9pq.fsf@fnord.ir.bbn.com \
    --to=gdt@ir.bbn.com \
    --cc=bzg@altern.org \
    --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).