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

Regression in package detection #2170

Closed
clason opened this issue Sep 13, 2021 · 1 comment
Closed

Regression in package detection #2170

clason opened this issue Sep 13, 2021 · 1 comment
Labels

Comments

@clason
Copy link
Contributor

clason commented Sep 13, 2021

Description

The commit 92d268a introduced a regression in the detection of packages that are included "recursively".

Consider the following minimal(!) example:

  • test.sty
\RequirePackage{cleveref}
  • test1.tex
\cref{foo}
  • test.tex
\documentclass{minimal}
\usepackage{test}

\begin{document}
\include{test1}
\end{document}

A similar issue occurs with packages loaded in a custom myclass.cls.

Steps to reproduce

  1. pdflatex test.tex
  2. nvim --clean -u minimal.vim test1.tex (note: subfile!)

Expected behavior

Syntax highlighting for \cref.

Actual behavior

No syntax highlighting for \cref.

Do you use a latexmkrc file?

N/A

VimtexInfo

VimTeX project: test
  base: test.tex
  root: /Users/clason
  tex: /Users/clason/test.tex
  main parser: recursive search
  document class: minimal
  packages: test
  source files:
    test.tex
    test1.tex
  compiler: latexmk
    engine: -pdf
    options:
      -verbose
      -file-line-error
      -synctex=1
      -interaction=nonstopmode
    callback: 1
    continuous: 1
    executable: latexmk
  viewer: General
  qf method: LaTeX logfile
@clason clason added the bug label Sep 13, 2021
lervag added a commit that referenced this issue Sep 13, 2021
This fixes a regression from commit 92d268a.

refer: #2170
@lervag
Copy link
Owner

lervag commented Sep 13, 2021

Thanks! Should be fixed now.

@lervag lervag closed this as completed Sep 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants