emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Michael Hannon <jm_hannon@yahoo.com>
Cc: nicholas.dokos@hp.com, Org-Mode List <emacs-orgmode@gnu.org>
Subject: Re: Conflict between Org-Mode versions?
Date: Fri, 29 Apr 2011 15:58:32 -0400	[thread overview]
Message-ID: <6571.1304107112@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from Michael Hannon <jm_hannon@yahoo.com> of "Fri, 29 Apr 2011 12:32:19 PDT." <790495.34626.qm@web161916.mail.bf1.yahoo.com>

Michael Hannon <jm_hannon@yahoo.com> wrote:

> 
> > From: Eric S Fraga <e.fraga@ucl.ac.uk>
> 
> 
> > [...]
> 
> >> FWIW, in Emacs I typed:
> >>
> >>     C-h v org<TAB>
> >>
> >> and got no fewer than 931 completions.  A lot of knobs to turn!
> > 
> > yes, indeed!  the info manual is your friend here.  it is very difficult
> > to figure out what you need to set from just the list of org- variables.
> 
> Heh.  Yes, thanks, Eric.  I'm not crazy enough to try to bootstrap my way
> through 900+ variables, but that sets the scale of the challenge for me.
> 

IIRC, Carsten had run a poll for the nomination of the 50 most-use{d|ful}
variables. The results must be somewhere (Worg? Mailing list?). That
would probably serve as a better starting point than a 931-element list
with no other indicator of importance.

Also, Bernt's document (http://doc.norang.ca/org-mode.html ) probably
contains settings for most (if not all) of the important variables.

After that, you can start looking at more obscure ones. Many of those
were introduced as part of a user-requested feature, so you can probably
get some background information on them by searching the mailing list.

> > The best approach here is to use some of the specific functions (often
> > with already defined key bindings) that are set up for just this type of
> > case: =org-insert-link= in this case.  These will insert things with the
> > right formatting automatically!
> 
> Very good suggestion!  I just used C-c C-l to add a link, and, of course, it
> worked perfectly (as did the manual edit suggested by Nick D.).  I note that
> by my count there are no fewer than 1612 "org*" functions ;-)
> 

Be ready to explain them all by heart. Quiz tomorrow.

Nick

  reply	other threads:[~2011-04-29 19:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 20:10 Conflict between Org-Mode versions? Michael Hannon
2011-04-27 20:33 ` Nick Dokos
     [not found] ` <4433.1303935870@alphaville.americas.hpqcorp.net>
2011-04-27 22:13   ` Michael Hannon
2011-04-27 22:19     ` Jambunathan K
2011-04-28  0:20       ` Michael Hannon
2011-04-28 11:01     ` Eric S Fraga
2011-04-29 19:32       ` Michael Hannon
2011-04-29 19:58         ` Nick Dokos [this message]
2011-04-29 20:58           ` Michael Hannon
2011-04-29 21:07             ` Nick Dokos
2011-04-29 21:34               ` Michael Hannon
2011-04-29 23:00           ` Memnon Anon
2011-04-30  5:11             ` Jambunathan K

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=6571.1304107112@alphaville.americas.hpqcorp.net \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jm_hannon@yahoo.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 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).