Hello, Aaron Ecay <aarone...@gmail.com> writes:
> Now that this has come up, I have looked at it more. It appears that > the /usr/share/emacs/site-lisp directory is not added to load-path in > the async export process. I guess that it should be, since users’ > init.el files could rely on libraries that are found there. This is debatable. I think that the sub-process shouldn't load too much libraries. In your case, you effectively need to tweak `org-export-async-init-file'. > This will make the problem very difficult, if not impossible. Generally > speaking, the buffer that the export functions see bears only a loose > relationship to the original buffer, since babel blocks, #+include > directives, etc. have changed the text. I have tried to think of ways > to get around this fact, since working with the synctex file requires > knowing the original line number. This is the best I could do. [...] > Do you have any ideas about how this might be overcome? What is needed > is to know, for any line in the exported output, which line of the org > file it corresponds to (within some small margin of error). I don't think there is a complete solution to this problem. Though `org-export-before-processing-hook' allows to work on an exact copy of the buffer being exported before any file is included and any Babel block executed. You can add text properties there. And with `org-export-before-parsing-hook', you can check what parts of the buffer are new (generated from include keywords, macros and blocks). From there it may be possible to implement a lookup function which would find the appropriate line in the original buffer. Regards, -- Nicolas Goaziou
