emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: gvoysey <gvoysey@bu.edu>
Cc: emacs-orgmode@gnu.org
Subject: 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/)]
Date: Tue, 26 Jun 2018 12:07:50 +0200	[thread overview]
Message-ID: <87d0wdsvwp.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAC3+WKZN78u+gw-zjzt8TanQ5bfn7pC5M1YaswV3W1_ZpynN1g@mail.gmail.com> (gvoysey's message of "Mon, 25 Jun 2018 23:17:23 -0400")

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

next prev parent reply	other threads:[~2018-06-26 10:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26  3:17 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
2018-06-26 10:07 ` Nicolas Goaziou [this message]
2018-06-26 16:23   ` gvoysey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d0wdsvwp.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=gvoysey@bu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).