Re: [O] [PATCH] No completion when querying for property value in capture template

[Eric Danan]

Thanks.

I did some testing and it seems towork except in one case: if the
template target is of type "file+headline" (I guess "file+olp" etc as
well), the target file has an in-buffer setting "#+PROPERTY PROP_ALL
AAA BBB", and the target entry has a property ":PROP_ALL:  CCC DDD"
overriding the in-buffer setting, then completion is done on "AAA BBB"
whereas it would make more sense to me to do it on "CCC DDD".

It is perhaps not a major issue, but could be a convenient way to
specify different sets of allowed values for different target entries
in the same file (it already works, however, if the target file has no
in-buffer setting for the allowed values). An alternative could be to
allow patterns of the form "%^{prop|allowed1|allowed2|...}p" in the
capture template (that would in fact be even more flexible because it
would allow to specify different sets of allowed values for different
capture templates with the same target entry).

Eric
On Sat, Jun 16, 2018 at 5:06 PM Nicolas Goaziou <address@hidden> wrote:
>
> Hello,
>
> Eric Danan <address@hidden> writes:
>
> > OK I think I understand why it doesn't work. I'm attaching a simple
> > patch that hopefully solves the issue. I've put comments in the commit
> > message. Please let me know if anything is not clear or if you see
> > issues.
>
> Thank you for the analysis and the patch. As you have guessed, the
> problem is that the property is set in a different buffer than the
> target buffer.
>
> I committed a different solution. Does it fix your problem?
>
> Regards,
>
> --
> Nicolas Goaziou