Reference/citation completion fails with non-standard line endings #1
Comments
sorbits
pushed a commit
that referenced
this issue
Sep 25, 2014
When we search for bibliography items or labels we also try to include all files specified via `input` and `include`. We might however also use `input` and `include` inside generic macros. This could can cause trouble. For example: Before this commit we would to try to include the “location” `Code/#1` when searching for cites if we used the following TeX code: \newcommand{\codeinput}[1] { \begin{leftbar} \input{Code/#1} \end{leftbar} }
sanssecours
added a commit
that referenced
this issue
Jul 8, 2015
“Typeset & View (PDF)” will now ignore file paths that contain hash signs included via `input`. This is useful since `#` signs are used as placeholders in tex macros. This change means “Typeset & View” will not display a warning for the non-existent file `Code/#1` for macros such as the following one: \newcommand{\codeinput}[1] { \begin{leftbar} \input{Code/#1} \end{leftbar} }
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The regexp used to scan files should use /\r?\n/ as line endings, more info in this thread: http://lists.macromates.com/textmate/2010-January/030360.html
The text was updated successfully, but these errors were encountered: