emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alexander Vorobiev <alexander.vorobiev@gmail.com>
To: Rainer M Krug <Rainer@krugs.de>
Cc: Adam Porter <adam@alphapapa.net>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Capture with org-directory not working?
Date: Tue, 29 Nov 2016 13:23:39 -0600	[thread overview]
Message-ID: <CAGOCFPX-yt9gMwjHvS8B0b6V69=UDRgepPX4jn_P_scigMfJSg@mail.gmail.com> (raw)
In-Reply-To: <m2k2e5ifiq.fsf@krugs.de>

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

I have recently started having this issue with my capture templates. In my
case I want to ask the user (me) which file should be used to store the
note, so I have a bunch of templates like this

(setq org-capture-templates
             '(("o" "Project todo" entry (file+headline
(av/choose-agenda-file) "Tasks") ))

where av/choose-agenda-file uses completing-read to ask the user to choose
a file from a list it constructs on the fly. This approach has worked for
years and now it results in the "invalid file location" message. The
backquote does not help because the function needs to be called at run
time, not when the variable is defined.

Thanks,
Alex

On Wed, Sep 21, 2016 at 7:49 AM, Rainer M Krug <Rainer@krugs.de> wrote:

> Adam Porter <adam@alphapapa.net> writes:
>
> > Rainer Krug <r.m.krug@gmail.com> writes:
> >
> >> But It seems to abusing the basic idea of custom-set-variables as this
> >> sounds as if it is used by the customise interface.
> >
> > What I mean is, you can use the customize interface to store your
> > org-capture-templates.  It's already set up for that.  You can either
> > edit it through the customize interface, or you can edit it directly in
> > the init file and then evaluate the ~(custom-set-variables~ sexp
> manually.
> >
>
> OK - but I prefer to keep my configurations in my .emacs.el file to make
> it reproducible.
>
>
> Thanks,
>
> Rainer
>
> >
>
> --
> Rainer M. Krug
> email: Rainer<at>krugs<dot>de
> PGP: 0x0F52F982
>

[-- Attachment #2: Type: text/html, Size: 2245 bytes --]

  reply	other threads:[~2016-11-29 19:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 13:46 Capture with org-directory not working? Rainer M Krug
2016-09-19 15:47 ` Nick Dokos
2016-09-20  7:25   ` Rainer M Krug
2016-09-20 15:00     ` Adam Porter
2016-09-20 16:03       ` Rainer Krug
2016-09-20 17:08         ` Adam Porter
2016-09-21  7:05           ` Rainer Krug
2016-09-21 11:51             ` Adam Porter
2016-09-21 12:49               ` Rainer M Krug
2016-11-29 19:23                 ` Alexander Vorobiev [this message]
2016-11-29 21:05                   ` Nick Dokos
2016-11-30  5:15                     ` Alexander Vorobiev
2016-11-30 16:45                       ` Nick Dokos

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='CAGOCFPX-yt9gMwjHvS8B0b6V69=UDRgepPX4jn_P_scigMfJSg@mail.gmail.com' \
    --to=alexander.vorobiev@gmail.com \
    --cc=Rainer@krugs.de \
    --cc=adam@alphapapa.net \
    --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).