all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Alan E. Davis'" <lngndvs@gmail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: Possibility of combining custom and init-file setup (Org modecapture templates)
Date: Sun, 13 Mar 2011 06:39:57 -0700	[thread overview]
Message-ID: <345FA257C5694F7B8CCD1A868249885E@us.oracle.com> (raw)
In-Reply-To: <AANLkTim5TgLpuQGSKvH64nb3Oz1qmZpSprKqik2UJ7GG@mail.gmail.com>

> I find org-mode's custom interface for capture templates
> extremely helpful for quick, one-off templates, without
> having to edit the init-file.  Especially for somewhat
> complicated templates it provides a starting point.  However,
> to use this custom buffer interface seems to conflict, in many
> a non-obvious way, with the manually loaded templates.  One
> receives a message suggesting that unpredictable results may
> ensue from modifying this variable that was set outside of
> the custom interface.

Too abstract for me to be able to help you.  Hopefully someone familiar with
org-mode or its code will be able to help.

In the abstract, you should be able to do everything via Lisp that you can do
using Customize.  Dunno what warning messages you are referring to, but as a
start try setting values using `custom-set-variables', not `setq'.  Check
whether the `defcustom' forms use :set or :init etc.  If so then you will need
to do something similar from Lisp - they mean that `setq' is not sufficient.
Keyword :type tells you what form the value must take.  And so on.  Use the
org-mode `defcustom' forms as your guide.




      reply	other threads:[~2011-03-13 13:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12 22:24 Possibility of combining custom and init-file setup (Org mode capture templates) Alan E. Davis
2011-03-13 13:39 ` Drew Adams [this message]

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=345FA257C5694F7B8CCD1A868249885E@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=lngndvs@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.