From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: Capture Bug?
Date: Wed, 21 Sep 2016 06:54:59 -0500 [thread overview]
Message-ID: <87bmzhsc18.fsf@alphapapa.net> (raw)
In-Reply-To: 660bdacc1d49d4c46a36cc4edf42db66@wilkesley.net
lists@wilkesley.net writes:
> I have a capture template which prompts for a file name and uses this
> to create a filename with a datestamp:
>
> (defun capture-pelican-draft-file (path)
> (let ((name (read-string "Name: ")))
> (expand-file-name (format "%s-%s.org"
> (format-time-string "%Y-%m-%d")
> name) path)))
>
>
> ("g"
> "New blog post (ianbarton.net)"
> plain
> (file (capture-pelican-draft-file
> "~/Documents/emacs/web_sites/ianbarton.net/org/_posts"))
> "#+AUTHOR: Ian Barton\n#+DATE: %u\n#+PROPERTY: MODIFIED:
> \n#+TITLE\n#+CATEGORY: Blog \n#+PROPERTY: TAGS \n#+PROPERTY: SUMMARY
> \n#+SETUPFILE: ../setup.org\n\n")
Are you using custom-set-variables to set org-capture-templates? If
not, I think you need to unquote capture-pelican-draft-file.
>> On the current git master the function capture-pelican-draft-file
> doesn't seem to be evaluated, resulting in a "File name doesn't exist"
> error. Doing git bisect seems to point at the commit below:
>
> 8860c92f62dac87267416708e81bc8aec026fcc7 is the first bad commit
> commit 8860c92f62dac87267416708e81bc8aec026fcc7
> Author: Nicolas Goaziou <mail@nicolasgoaziou.fr>
> Date: Fri Jun 24 00:55:03 2016 +0200
That commit is about org-babel, which I don't think should have anything
to do with org-capture. But you said you bisected it, so you mean that
before that commit, your code works as-is?
next prev parent reply other threads:[~2016-09-21 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 8:58 Capture Bug? lists
2016-09-21 11:54 ` Adam Porter [this message]
2016-09-21 18:24 ` lists
2016-09-21 20:01 ` Adam Porter
2016-09-21 20:51 ` Nicolas Goaziou
2016-09-22 9:14 ` Ian Barton
2016-09-21 21:38 ` Nick Dokos
2016-09-22 2:54 ` Adam Porter
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=87bmzhsc18.fsf@alphapapa.net \
--to=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).