You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes org files are split into multiple org files. This could be due to multiple org files using the same parts, so it's sort of "DRY", or you simply have modular stuff you want to bring into one file. The INCLUDE word can be used to include lines from other files when exporting.
Currently, you have to do something like this with ntangle:
However, it does make sense if the maintainer doesn't want this in ntangle since the default org-babel-load-file (which ntangle sort of mimics?) doesn't have this behavior as far as I know. Thoughts on throwing this onto the backlog or nay?
The text was updated successfully, but these errors were encountered:
The #+include is a pretty loaded functionality.. it then opens up the need to support the full include functionality, which I am not open to. PR's are of course welcome.
But I don't mind adding functionality for just the basic#+include: /path/to/the/other/file.org.
Sometimes org files are split into multiple org files. This could be due to multiple org files using the same parts, so it's sort of "DRY", or you simply have modular stuff you want to bring into one file. The
INCLUDE
word can be used to include lines from other files when exporting.Currently, you have to do something like this with
ntangle
:it could be nice if we could just do:
However, it does make sense if the maintainer doesn't want this in ntangle since the default
org-babel-load-file
(which ntangle sort of mimics?) doesn't have this behavior as far as I know. Thoughts on throwing this onto the backlog or nay?The text was updated successfully, but these errors were encountered: