From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Hudson Subject: Re: Bug: Capture template file source variant support in Customize [8.3.4 (8.3.4-47-gaf853d-elpa @ /home/phil/.emacs.d/elpa/org-20160502/)] Date: Tue, 10 May 2016 23:12:45 +0100 Message-ID: <87r3d9ftpe.fsf@quiz.hudson-it.ddns.net> References: <87r3dehru8.fsf@quiz.hudson-it.ddns.net> <87d1otk3sn.fsf@saiph.selenimh> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41228) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b0FsF-0001Iz-32 for emacs-orgmode@gnu.org; Tue, 10 May 2016 18:11:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b0FsA-0005DN-RF for emacs-orgmode@gnu.org; Tue, 10 May 2016 18:11:26 -0400 Received: from mail-wm0-x22c.google.com ([2a00:1450:400c:c09::22c]:37660) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b0FsA-0005DF-3t for emacs-orgmode@gnu.org; Tue, 10 May 2016 18:11:22 -0400 Received: by mail-wm0-x22c.google.com with SMTP id a17so51537453wme.0 for ; Tue, 10 May 2016 15:11:22 -0700 (PDT) Received: from quiz.hudson-it.ddns.net.quiz.hudson-it.ddns.net (82-71-5-38.dsl.in-addr.zen.co.uk. [82.71.5.38]) by smtp.gmail.com with ESMTPSA id u12sm5175699wmu.12.2016.05.10.15.11.20 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 May 2016 15:11:20 -0700 (PDT) In-Reply-To: <87d1otk3sn.fsf@saiph.selenimh> (Nicolas Goaziou's message of "Tue, 10 May 2016 23:21:12 +0200") 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 On Tue, 10 May 2016 at 10:21:12 pm BST, Nicolas Goaziou wrote: > Hello, > > Phil Hudson writes: > >> Expected: When using the Customize interface to create/edit an Org >> capture template, we expect to be able to specify a file to write the >> captured item into using (according to the documentation) any one of: >> * a literal filename >> * a function >> * a variable >> * a form >> But the Customize UI supports only the first of these. The attached >> patch adds Customize support for the other three variants, in the proper >> order (increasing generality/decreasing specificity). >> >> Note that using Lisp to specify a capture template's target file using a >> function, variable or sexp *does* work fine and as documented, except >> that thereafter Customize fails to present the resulting variable >> correctly; it reverts to showing the alist as one Lisp form. This patch >> simply "catches up" the Customize UI with what Org can do and is >> documented as doing. > > Sounds good. > > However, wouldn't it make sense to also add these types to other file > related target locations, e.g., "File & Headline", "File & Outline > path"... ? Thanks for the perceptive feedback. I hadn't even thought about it. Your suggestion definitely sounds like the right thing to do. I'll be back with a fuller patch, properly gitted and committed. -- Phil Hudson http://hudson-it.ddns.net @UWascalWabbit PGP/GnuPG ID: 0x887DCA63