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.

Sign up for GitHub

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

Jump to bottom

\subimport checks grammar in filenames #207

Closed
mfbehrens99 opened this issue Dec 13, 2022 · 2 comments
Closed

\subimport checks grammar in filenames #207

mfbehrens99 opened this issue Dec 13, 2022 · 2 comments
Assignees
@valentjn
Labels
1-bug 🐛 Issue type: Bug report (something isn't working as expected) 2-confirmed Issue status: Confirmed, reproducible bug in LTeX 3-fixed Issue resolution: Issue has been fixed on the develop branch
Milestone
16.0.0

Comments

@mfbehrens99
Copy link

Describe the bug
\subimport*{../}{sitzung_daten.tex}
and
\subimport{../}{sitzung_daten.tex}
throws an error that two dots are not allowed
@mfbehrens99 mfbehrens99 added 1-bug 🐛 Issue type: Bug report (something isn't working as expected) 2-unconfirmed Issue status: Bug that needs to be reproduced (all new bugs have this label) labels Dec 13, 2022
@valentjn valentjn added 2-confirmed Issue status: Confirmed, reproducible bug in LTeX and removed 2-unconfirmed Issue status: Bug that needs to be reproduced (all new bugs have this label) labels Feb 12, 2023
@valentjn valentjn self-assigned this Feb 12, 2023
@valentjn valentjn added this to the 16.0.0 milestone Feb 12, 2023
valentjn added a commit that referenced this issue Feb 12, 2023
@valentjn
Add support for \import and \subimport
220379d 
Fixes #207.
@valentjn
Copy link
Owner

Fixed for \import and \subimport. The starred variants of those macros are the same as the non-starred macros since version 6.0 of the import package, but they are ignored now nevertheless.

@valentjn valentjn added the 3-fixed Issue resolution: Issue has been fixed on the develop branch label Feb 12, 2023
@github-actions
Copy link

This issue is now fixed on develop. The fix will be included in the next release of LTEX.

If you don't want to wait, you can try out the nightly pre-release tomorrow. Nightly pre-releases are published every morning at around 4am UTC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@valentjn valentjn

Labels
1-bug 🐛 Issue type: Bug report (something isn't working as expected) 2-confirmed Issue status: Confirmed, reproducible bug in LTeX 3-fixed Issue resolution: Issue has been fixed on the develop branch
Projects
None yet
Milestone
16.0.0
Development

No branches or pull requests
2 participants
@valentjn @mfbehrens99