|
From: | Pierre Téchoueyres |
Subject: | Re: [O] [PATCH] Add new keyword :coding for #+include directive |
Date: | Wed, 18 Apr 2018 20:40:32 +0200 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Hello, Nicolas Goaziou <address@hidden> writes: > Hello, > ... >> This allow you to specify something like >> >> #+begin_example >> ,#+INCLUDE: "myfile.cmd" src cmd :coding "cp850-dos" >> #+end_example > > The quotes are not necessary. AFAICT, coding systems do not contain > spaces. Ok, I've reworked the rexexp to suppress them. New patch attached
0001-Add-new-keyword-coding-for-include-directive.patch
Description: include-with-coding
> ... > Is it really an Org problem? E.g., couldn't you put a coding: cookie in > your ".cmd" file? IMO, the coding system depends on the includee, not > the includer. I tend to aggree with you that TRTDT is to put cookies or something inside the included file. But : a) This seem to not work as expected (see exemples joinned). b) Sometimes you can't modify the included file (ex: remote file access).
test.org
Description: test.org
file.1.txt
Description: file.1.txt
file.2.txt
Description: file.2.txt
For a I can try to jump into the rabbit hole and find a solution (but for now I'm lost) Regards,
[Prev in Thread] | Current Thread | [Next in Thread] |