emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: "Alan E. Davis" <lngndvs@gmail.com>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: Defining capture-templates: custom and init file
Date: Mon, 7 Mar 2011 21:39:32 -0800	[thread overview]
Message-ID: <20110307213932.4dbda28a@bhishma.homelinux.net> (raw)
In-Reply-To: <AANLkTi=j+2Ng05qYTzRS++0QwY7Ab703oVp0rGqDHvOj@mail.gmail.com>

On Tue, 8 Mar 2011 12:17:58 +1000
"Alan E. Davis" <lngndvs@gmail.com> wrote:

> I would like to request advice, on how can I set up so most of my
> capture templates are loaded from a file (~/org/capture-templates.el
> in my case) and still retain the ability to define new capture
> templates on the fly.  I want the best of both worlds:

Sorry, can't be done. The customize interface stores the
(custom-set-variables ... ) block in the init file. Having more than
one such code block might lead to unpredictable Emacs behaviour. Your
only two choices are:

1. Use customize. Then your capture templates are stored with your other
   emacs customisations in your init file (e.g. ~/.emacs,
   ~/.emacs.d/init.el or whatever).

2. Use setq to define your templates outside of customize. If you choose
   this, you lose the ability to define templates using customize and
   save it. You can still however save a template temporarily `C-c C-c'.

I hope this answers your query.

-- 
Suvayu

Open source is the future. It sets us free.

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08  2:17 Defining capture-templates: custom and init file Alan E. Davis
2011-03-08  5:39 ` Suvayu Ali [this message]
2011-03-08  6:13   ` Alan E. Davis
2011-03-08  6:33     ` Suvayu Ali
2011-03-08 11:05       ` Alan E. Davis
  -- strict thread matches above, loose matches on Subject: below --
2011-03-08 11:19 Rustom Mody

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=20110307213932.4dbda28a@bhishma.homelinux.net \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=emacs-orgmode@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 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).