Re: Colons in :var header arguments

[Stefano Ghirlanda]

Thanks, and sorry for the slow reply! I was wondering if it would be
more intuitive to try to resolve the reference in the same file before
looking in other files. I think this would make little practical
difference as I think files named sec, tab, eq and fig are rare
(although I often use fig for a figure directory, I wonder what
happens then). But looking externally first is more compatible with
current behavior, so maybe that should have priority.

Thanks again for considering.

On Sat, Oct 21, 2023 at 3:11 AM Ihor Radchenko <yantar92@posteo.net> wrote:
>
> Stefano Ghirlanda <dr.ghirlanda@gmail.com> writes:
>
> > I have run into an inconvenience in that colons in :var header
> > arguments to source blocks are invariably interpreted as referring to
> > another file. However, I use cleveref in LaTeX export (via org-ref) to
> > automatically format references using labels like tab:data, and in
> > these cases :var data=tab:data gives a reference not found because tab
> > is interpreted as a filename.
>
> I agree that it is a problem.
> Attaching tentative patch that will make Org babel fall back to
> searching in current file when FILE in FILE:REF does not exist.
>
> It is technically a breaking change. If this is affecting someone's
> workflow, please chime in.
>
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>



-- 
Stefano Ghirlanda
CTO, DataWorks - https://dataworks.consulting
Guest Professor - Stockholm University Centre for Cultural Evolution