From: Kyle Meyer <kyle@kyleam.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Default location for "./" with respect to capture file+headline
Date: Fri, 05 Feb 2016 22:55:15 -0500 [thread overview]
Message-ID: <877fii7asc.fsf@kyleam.com> (raw)
In-Reply-To: <CA+M2ft9QxEOop2_E-1maKqsmUKkg2UjE22-i7uA=FCOyDU0ffg@mail.gmail.com> (John Hendy's message of "Fri, 5 Feb 2016 21:19:58 -0600")
Hello,
John Hendy <jw.hendy@gmail.com> writes:
> When I do =C-c c= to try a capture example, it's trying to file it
> with respect to ~/org and I'm not sure why. Here's the capture section
> of dir/setup/example-config:
>
> (setq org-capture-templates
> '(("l" "log" entry (file+headline "./demo/org-demo_capture.org" "Log")
> "* %? \n%u " :clock-in t :clock-resume t)
> ("t" "task" entry (file+headline "./demo/org-demo_article.org" "Tasks")
> "* todo %? %^g\n%u" :prepend t)
> ("c" "clock" entry (file+datetree "./demo/org-demo_clocking.org")
> "* %?\n%u" :clock-in t :clock-keep t)))
>
> The capture buffer wants to create the directory ~/org/demo.
The variable org-directory affects this:
--8<---------------cut here---------------start------------->8---
Documentation:
Directory with Org files.
This is just a default location to look for Org files. There is no need
at all to put your files into this directory. It is used in the
following situations:
1. When a capture template specifies a target file that is not an
absolute path. The path will then be interpreted relative to
‘org-directory’
2. When the value of variable ‘org-agenda-files’ is a single file, any
relative paths in this file will be taken as relative to
‘org-directory’.
--8<---------------cut here---------------end--------------->8---
--
Kyle
next prev parent reply other threads:[~2016-02-06 3:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 3:19 Default location for "./" with respect to capture file+headline John Hendy
2016-02-06 3:55 ` Kyle Meyer [this message]
2016-02-07 15:30 ` John Hendy
2016-02-07 17:00 ` Kyle Meyer
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=877fii7asc.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@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).