Hi Hugo, Your idea rings bells from the time I wrote my PhD ;-) Answers inline…
On 22 Jan 2025 Hugo writes: > >I have recently been using the LaTeX subfiles package a lot, with org >mode. The package lets your compile multi-file projects in convenient >ways, but (in order to do this) requires that: 1. each subfile uses >the `subfile' class, 2. with the path of the master file passed as an >argument > >My workflow is that I have a master file in LaTeX, which includes >various other LaTeX files (which are exports from org files) as >subfiles, thus: > >,---- >| /project-folder >| ├ main.tex >| ├ chapterOne >| │ ├ chapterone.org >| │ └ chapterone.tex (org export) >| ├ chapterTwo >| │ ├ chaptertwo.org >| │ └ chaptertwo.tex (org export) >| └ chapterThree >| ├ chapterthree.org >| └ chapterthree.tex (org export) >`---- Sounds familiar and after reading the subfiles package, it looks like it would have been very useful if it had been available :-) For a structure like yours, your proposal might be helpful. But what about a project with more levels? Another question: In my case, the chapters were inspiered by the different publications. I had subdirectories for figures, code and data for each of the chapters and imported files for the different sections. My bibliography files and other common resources like acronyms were in the main project folder. Could you please ellaborate on who all these features would be treated in your case. Maybe #+LATEX_CLASS_OPTIONS ends up to be the more sensible solution. It also makes the different org files "self-documenting", so when you come back to your thesis after some time or after 'real life stuff' like work, you can easily see what you were doing and retake your thesis at the point you left it. Just my .2cents, /PA
