From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastien <bzg@gnu.org>
Subject: Re: Capture templates with "function" type
Date: Wed, 06 Nov 2013 15:24:24 +0100
Message-ID: <87mwlhsj53.fsf@bzg.ath.cx>
References: <ir4y55f20km.fsf@lycastus.phy.bnl.gov>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44617)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@gmail.com>) id 1Ve426-0002mM-G4
	for emacs-orgmode@gnu.org; Wed, 06 Nov 2013 09:24:39 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bastienguerry@gmail.com>) id 1Ve420-0004B9-UO
	for emacs-orgmode@gnu.org; Wed, 06 Nov 2013 09:24:34 -0500
Received: from mail-wg0-x22d.google.com ([2a00:1450:400c:c00::22d]:48192)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@gmail.com>) id 1Ve420-0004Ap-JM
	for emacs-orgmode@gnu.org; Wed, 06 Nov 2013 09:24:28 -0500
Received: by mail-wg0-f45.google.com with SMTP id z12so5081092wgg.24
	for <emacs-orgmode@gnu.org>; Wed, 06 Nov 2013 06:24:27 -0800 (PST)
In-Reply-To: <ir4y55f20km.fsf@lycastus.phy.bnl.gov> (Brett Viren's message of
	"Sat, 26 Oct 2013 17:18:17 -0400")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Brett Viren <bv@bnl.gov>
Cc: emacs-orgmode@gnu.org

Hi Brett,

Brett Viren <bv@bnl.gov> writes:

> Can someone say how I might get this behavior for the "function" capture
> type as well?

I'm still investigating this bug, but in the meantime you may want to
try using file+function, which does not have the bug.

-- 
 Bastien