From mboxrd@z Thu Jan 1 00:00:00 1970 From: lists@wilkesley.net Subject: Capture Bug? Date: Wed, 21 Sep 2016 09:58:37 +0100 Message-ID: <660bdacc1d49d4c46a36cc4edf42db66@wilkesley.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33500) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bmdMi-0006V4-HS for emacs-orgmode@gnu.org; Wed, 21 Sep 2016 04:58:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bmdMe-00010v-8I for emacs-orgmode@gnu.org; Wed, 21 Sep 2016 04:58:51 -0400 Received: from mail2.wilkesley.net ([176.58.110.121]:42976 helo=li40-130.members.linode.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bmdMe-0000z6-2U for emacs-orgmode@gnu.org; Wed, 21 Sep 2016 04:58:48 -0400 Received: from wilkesley.org (localhost [127.0.0.1]) (Authenticated sender: lists@wilkesley.net) by li40-130.members.linode.com (Postfix) with ESMTPA id 9AF5BDC6DD for ; Wed, 21 Sep 2016 08:58:37 +0000 (UTC) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org 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") 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 Date: Fri Jun 24 00:55:03 2016 +0200 ob-exp: Small fix * lisp/ob-exp.el (org-babel-exp-src-block): Use `symbol-name' instead of `eval' since the argument is a dynamically scoped variable anyhow. Ian.