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

theorem like environment are conflicted with template using cls file that already define it. #1001

Closed
cderv opened this issue Oct 29, 2020 · 1 comment · Fixed by #1145
Closed
Labels
bug an unexpected problem or unintended behavior next to consider for next release

Comments

@cderv
Copy link
Collaborator

cderv commented Oct 29, 2020

This comes from test in rstudio/rticles#288

lipics-v2019.cls already defines theorem like environment. When using this articles with pdf_book to get the \@ref syntax, this does not work because bookdown will add in the tex template theorem like environment, but it conflicts with the one already defined by the the cls file.

Try

bookdown::pdf_book:
    base_format: rticles::lipics_article()

with LIPICs template from rticles

@cderv cderv added bug an unexpected problem or unintended behavior next to consider for next release labels Mar 30, 2021
cderv added a commit that referenced this issue Apr 20, 2021
This is useful for rticles format than can define environment in .cls

Closes #1001
@cderv cderv linked a pull request Apr 20, 2021 that will close this issue
3 tasks
@github-actions
Copy link

This old thread has been automatically locked. If you think you have found something related to this, please open a new issue by following the issue guide (https://yihui.org/issue/), and link to this old issue if necessary.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug an unexpected problem or unintended behavior next to consider for next release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant