Skip to content
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

Failure with non-article documentclass #60

Open
mabney opened this issue Nov 10, 2022 · 5 comments
Open

Failure with non-article documentclass #60

mabney opened this issue Nov 10, 2022 · 5 comments

Comments

@mabney
Copy link

mabney commented Nov 10, 2022

I use the exam documentclass which defines certain commands (e.g. \lhead). Xenops replaces this with the article document class and then fails when it encounters the \lhead command, which appears only in the preamble. Ideally, xenops would work with document classes that define commands that might appear in the preamble, for instance by using the document class of the document.

@egstatsml
Copy link

Have a look at the issue here which describes how you can set the org-format-latex-header variable to help make xenops work with other document classes

@mabney
Copy link
Author

mabney commented Mar 13, 2023

Thanks for pointing this out. It does provide a workaround, of sorts, but it's not entirely satisfactory. Changing org-format-latex-header in init.el doesn't really work because I have different documents that use different classes. It does work when setting it as a file local variable (with some edits), but it's pretty awkward to do this for the various different files. Ideally it should just work when specifying a different document class, but it looks like development/maintenance of the package has ended, unfortunately.

@egstatsml
Copy link

no worries, I usually set the org-format-latex-header in my .dir-locals.el file for each project and has worked really well for me. Once I have time I would like to help contribute to this package to make things a little more automatic where possible to help out dandavison :)

@dandavison
Copy link
Owner

but it looks like development/maintenance of the package has ended, unfortunately.

Hi all, I am still reading these at least. But it's true that I'm not currently doing anything where I could use Xenops and I don't currently have time for Xenops development. If anyone would like to try to contribute that would be great; it is quite fun to work on.

@mabney
Copy link
Author

mabney commented Mar 13, 2023

Thanks for the great package. I really enjoy using it. Time constraint issues are totally understandable. Hopefully others will be able to step in and contribute to keeping the package going and even improve the rough edges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants