emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: gnuric@pm.me
To: emacs-orgmode@gnu.org
Subject: Have export treat file: paths in INCLUDED file relative to the INCLUDING file's dir
Date: Sun, 26 Feb 2023 01:52:38 +0000	[thread overview]
Message-ID: <87h6v9gpno.fsf@pm.me> (raw)


I have a file s.org in ./ (current directory), which includes
another file s0.org living under ./media/s/:


#+TITLE: s
#+INCLUDE: "./media/s/s0.org"


* s0
** s01

I want the org export to html to treat the file: paths in
./media/s/s0.org with respect to the directory of the ./s.org
file. In other words, I want export NOT TO TOUCH the file: paths
as written included files and effectively just paste the text of
s0.org verbatim in s.org (basically similar to what #include
directive in C preprocessor would do, e.g.). As of now, the above
s.org exports to s.html which has the file: link converted to


I want that link to instead become


which used to be the default behavior in a previous version of Org
mode (I don't recall which one). Is there a flag that could be
passed to #+INCLUDE: to change the 'relativeness' of the link
treatment when it comes to #+INCLUDE: directives?

I see in ox.el,

(defun org-export-expand-include-keyword (&optional included dir
  "Expand every include keyword in buffer.
Optional argument INCLUDED is a list of included file names along
with their line restriction, when appropriate.  It is used to
avoid infinite recursion.  Optional argument DIR is the current
working directory.  It is used to properly resolve relative
paths.  Optional argument FOOTNOTES is a hash-table used for
storing and resolving footnotes.  It is created automatically."

Is this DIR what's needed (to be given to #+INCLUDE: with a flag)
to change the link translation behavior?

Org mode version 9.4.4 (release_9.4.4)
GNU Emacs 27.2


             reply	other threads:[~2023-02-26  1:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-26  1:52 gnuric [this message]
2023-02-28 10:34 ` [FR] Allow to #+include files verbatim without any processing (was: Have export treat file: paths in INCLUDED file relative to the INCLUDING file's dir) Ihor Radchenko
2023-02-28 15:12   ` Timothy
2023-02-28 21:34     ` gnuric
2023-03-30 18:17       ` gnuric
2023-04-02 10:24         ` Ihor Radchenko
2023-04-02 21:32           ` gnuric
2023-04-03  9:18             ` Ihor Radchenko
2023-04-04  1:04               ` Samuel Wales
2023-04-04  8:57                 ` Ihor Radchenko
2023-04-05  0:16                   ` Samuel Wales
2023-04-04  8:07               ` gnuric
2023-04-04  8:26                 ` Ihor Radchenko
2023-03-01  9:58     ` Ihor Radchenko
2023-02-28 15:03 ` Have export treat file: paths in INCLUDED file relative to the INCLUDING file's dir Max Nikulin
2023-02-28 21:42   ` gnuric
2023-03-02 12:14     ` Max Nikulin

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:

  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=87h6v9gpno.fsf@pm.me \
    --to=gnuric@pm.me \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


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).