emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: gnuric@pm.me
To: orgmode@tec.tecosaur.net
Cc: yantar92@posteo.net, emacs-orgmode@gnu.org
Subject: Re: [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)
Date: Thu, 30 Mar 2023 18:17:08 +0000	[thread overview]
Message-ID: <WEcQEhwKn0ZobAf7tCxgLmcvtw94rqHUErAWkRXFSNuL4Eqb3QfxMiuhEC5TqQ_nOmtMDbO1NNki2g-TSWcJSwR2otyaqGbBTed58Kcrq4k=@pm.me> (raw)
In-Reply-To: <87ttz5a2zt.fsf@pm.me>

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

Hi,

I was wondering if anyone had any new ideas on this question (or an explanation on what Timothy meant by a :dir parameter).

Right now I'm having to use a search and replace back on the whole generated html buffer, which is fragile and inefficient.

Thanks,
Omid

-------- Original Message --------
On Feb 28, 2023, 1:34 PM, wrote:

> Hi Timothy, Thanks for your reply. "Timothy"  writes: > Hi Ihor, > >> This sounds like a reasonable request. >> What we may do here is allowing a new parameter :verbatim > > From a read of the original email, it sounds like a `:dir' > parameter could also > solve this use case, and allow for a bit more flexibility. > Is `:dir' a parameter to pass to `#+INCLUDE:'? I don't see it in the manual: https://orgmode.org/manual/Include-Files.html > All the best, > Timothy Regards, Omid

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

  reply	other threads:[~2023-04-01 12:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-26  1:52 Have export treat file: paths in INCLUDED file relative to the INCLUDING file's dir gnuric
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 [this message]
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:
  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='WEcQEhwKn0ZobAf7tCxgLmcvtw94rqHUErAWkRXFSNuL4Eqb3QfxMiuhEC5TqQ_nOmtMDbO1NNki2g-TSWcJSwR2otyaqGbBTed58Kcrq4k=@pm.me' \
    --to=gnuric@pm.me \
    --cc=emacs-orgmode@gnu.org \
    --cc=orgmode@tec.tecosaur.net \
    --cc=yantar92@posteo.net \
    /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
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

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