-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Macros not recognized when narrowed-subtrees are exported #7
Comments
Hello @pj-paul. I don't have any answer out of the box for this. What does happen if you put the macros "inlined" (instead of sourcing them via an include file) at the head of the org-file? Does that work? Anyhow, you should report this behavior to the Org mode mailing list. |
PS- Do you have extra macros you'd think would be worth adding for the community? |
@fniessen Thanks for the response.
|
On 3, I found this article on chaining macros. Maybe this might inspire some ideas for you. :) |
Consider an org-file structured as follows:
If I define include the macro setup-file at the head of the org-file, and then try to export a narrowed subtree, I get an error saying 'macro not defined'. However, the export works perfectly if I include the macro set-up file in the narrowed subtree.
Typical set-up files (say defining CSS styling) don't seem to have this problem.
Could you let me know if this has a solution?
The text was updated successfully, but these errors were encountered: