Re: [O] 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/)]

[Nicolas Goaziou]

Hello,

Phil Hudson <address@hidden> 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"... ?

Also, could you provide a patch using `git format-patch'?

Thank you.

Regards,

-- 
Nicolas Goaziou