all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Samuel Loury <konubinix@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: "atomic knowledge" modeling tool
Date: Tue, 16 Feb 2016 16:18:18 +0000	[thread overview]
Message-ID: <87ziv0r5md.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87wpq4u4gz.fsf@gmail.com> (Samuel Loury's message of "Tue, 16 Feb 2016 15:14:52 +0100")

On Tuesday, 16 Feb 2016 at 15:14, Samuel Loury wrote:

[...]

> I still like a lot the liberty of the "plain text approach" of
> org-mode. It is VERY powerful, but it becomes a real problem when
> needing to use that power without emacs.

Yes, org works well because of the plain-text approach but only because
it has the power of emacs behind it!  Without emacs, org would not be
anywhere as useful as it is.  It's the whole customisation capability
that makes it useful for as many people as it does.  All other tools
force you to conform to the decisions the authors of the tool made
whereas, with emacs, I can customise almost everything that relates to
my interaction with org.

Simple example: I use evil in Emacs as I prefer a modal interface to
alleviate RSI.  I therefore do not actually use any of the default key
bindings that come with org.  For instance, ", e" invokes
org-export-dispatch. ">" is org-meta-right.  Etc.

Actually, this reminds me of one problem area in org: the org export
dispatcher has key bindings hard coded in ("l" for LaTeX, etc.).  I wish
I could customise these.  My bugbear is ox-reveal that requires me to
hit a shift key, something I prefer to avoid as much as possible.

(I know the bindings come from the individual ox- files, not the
dispatcher per se.)
-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.90.1, Org release_8.3.3-597-gcaf66e

  reply	other threads:[~2016-02-16 16:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 18:21 "atomic knowledge" modeling tool luke call
2016-01-31 12:32 ` Eric S Fraga
2016-02-01 22:15   ` luke call
2016-02-02  8:49     ` Eric S Fraga
2016-02-03  9:33     ` Marcin Borkowski
2016-02-03 14:47       ` luke call
2016-02-03 17:15     ` Bingo UV
2016-02-03 18:22       ` luke call
2016-01-31 15:37 ` Ramon Diaz-Uriarte
2016-02-01 21:25   ` luke call
2016-02-03  8:04     ` Ramon Diaz-Uriarte
2016-02-02  7:23 ` Robert Klein
2016-02-02 15:20   ` luke call
2016-02-16 14:14     ` Samuel Loury
2016-02-16 16:18       ` Eric S Fraga [this message]
2016-02-16 16:44       ` Nicolas Goaziou
2016-02-16 19:52         ` Eric S Fraga
2016-02-20 18:09         ` Samuel Loury
2016-02-21 11:21           ` Nicolas Goaziou
2016-02-22  9:04             ` Samuel Loury
2016-02-24 16:46               ` Eric S Fraga
2016-02-29 13:31                 ` Samuel Loury
2016-03-06 19:26                   ` Samuel Loury
2016-03-07 15:28                     ` Eric S Fraga
2016-03-10  8:01                       ` Samuel Loury
2016-03-18 21:44                       ` Samuel Loury

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=87ziv0r5md.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=konubinix@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.