Fix for missing "end verbatim" in doc #210
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GitMensch
requested changes
Jan 9, 2025
There was a problem hiding this comment.
Comparing the versions from January 3rd and 9th:
the first has a text
@section Call environment
@verbatim
in Appendix I, the second an actual section in the PDF - so LGTM for upstream
just one requested change in the Changelog - but this can directly go upstream
There was a problem hiding this comment.
As this is the first 2025 entry: please add 2025 to the copyright years found at the end of the file
There was a problem hiding this comment.
Actually, 2023 and 2024 are also missing though they have some ChangeLog entries. Should those be added too ?
There was a problem hiding this comment.
correct, please adjust to 2009-2025
|
Merged in SVN @ 5418. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a missing "end verbatim" in the file generated by
cbrunt.tex.gen. Seems it's been like this for ages, but we only notice now because the MacOS CI began to fail for no apparent reason (in fact brew'stexinfoversion was updated from 7.1 to 7.2, which is probably the reason for this error to be detected).