Re: Bug: relative paths for links not preserved with #+INCLUDE [9.1.6 (release_9.1.6-419-g4b2006 @ /Users/gvoysey/.emacs.d/straight/build/org/)]

[gvoysey <gvoysey@bu.edu>]

[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]

Hi,

Confirmed, this works on 9.1.13 and is not a bug, just user error.  Cheers!

On Tue, Jun 26, 2018 at 6:07 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> gvoysey <gvoysey@bu.edu> writes:
>
> > I use org as my lab notebook.  Fairly often, I include figures and
> > plots.  I have the following style of file structure:
> >
> > Project
> > ├── project.org
> > └── subproject
> >     ├── figures
> >     │   └── foo.png
> >     └── subproject.org
> >
> > I have been using #+INCLUDE to "lift" subproject.org up into project.org
> as
> > a subheading, so I can export the whole thing at once.
> >
> > so project.org looks like:
> >
> > #+begin_src org
> > * project
> > here are my notes
> > #+INCLUDE: "./subproject/subproject.org"
> > #+end_src
> >
> >
> > and subproject:
> >
> > #+begin_src org
> > * notes
> > see this plot:
> > [[./figures/foo.png]]
> > #+CAPTION: a cool figure.
> > #+end_src
> >
> > When I export =project.org= as HTML or LaTeX, the figures are not
> > included.  When I instead export =subproject.org= directly, they are.
> >
> > Is there a way to insert file links to specify "relative to exactly this
> > file no matter where you've found yourself", or is  #+INCLUDE mangling
> > filepaths kind of unavoidable?  If the latter, what's the recommended
> > course of action here?
>
> Could you upgrade Org? IIRC, it was fixed some time ago?
>
> Regards,
>
> --
> Nicolas Goaziou
>



-- 
Graham Voysey
Boston University College of Engineering
HRC Research Engineer
Auditory Biophysics and Simulation Laboratory
ERB 413

[-- Attachment #2: Type: text/html, Size: 3048 bytes --]