Update from SublimeText/LaTeXTools@master #6
Conversation
This file contains hidden or 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
evandrocoan
force-pushed
the
master
branch
3 times, most recently
from
37a283e to
4213fbc
Compare
deathaxe
force-pushed
the
master
branch
9 times, most recently
from
09e9dda to
d0cd603
Compare
deathaxe
force-pushed
the
master
branch
8 times, most recently
from
38346cc to
fc0d179
Compare
deathaxe
force-pushed
the
master
branch
3 times, most recently
from
c8c0ec3 to
62af315
Compare
deathaxe
force-pushed
the
master
branch
2 times, most recently
from
cfd468b to
792c189
Compare
Fixes #1500
This commit adds support for `\usepackage{foo,bar,baz}`.
1. Use same contexts to scope exceptions and fatal errors.
Exception:
! Any error message.
Fatal Errors:
! LaTeX Error: Any error message.
2. Ensure a gap of `meta` scopes between subsequent items, if they are not
terminated as expected by e.g. empty line or trailing period.
That's required to extract items separately via `view.find_by_selector()`.
3. Extend bailout strategy from incomplete log entries.
Note: Box warnings use `embed` as those likely contain unbalanced brackets.
With WSL in the house a log file might contain Unix paths on Windows and Windows path on Unix. This commit therefore ensures prev_result/next_result handle them all on any OS.
This commit implements a workaround for a ST core bug, which causes `view.syntax()` method to return `None`, if syntax is (successfully) assigned by specifying syntax filename, only.
Fixes #1683 Some builder like latexmk skip processing, if input resources haven't changed, thus also don't create new logfiles. Common workflows seem to include re-opening build output panels using `ctrl+b` to just re-run (or skip) a build. To keep showing log output of most recently executed build process, log file must not be removed, even if it may contain invalid or out dated error indicators, in case latexmk actually started the 2nd run but failed without touching log file.
This commit replaces old `parse_tex_log()` function with a completely fresh approach. 1. Open logfile in hidden output panel 2. tokenize content with LaTeXTools Log.sublime-syntax 3. extract relevant log items (errors/warnings/badboxes) via find_by_selector() 4. associate them with source location (file:line) 5. output results in tuple, same as old function did. Fixing parsing bugs, primarily means fixing syntax bugs in LaTeXTools Log.sublime-syntax, which should be a bit more maintainable and testable, compared to a home grown implementation of a python based parser.
This commit addresses behavior of pdfLaTeX, which creates ANSI encoded logfiles, likely using OS's default encoding (at least on Windows), and LuaLaTeX/XeLaTeX, which create utf-8 encoded log files. There maybe other factors, hence use charset_normalizer package to auto-detect file encoding.
... to also detect encoding issues.
We don't need a traceback for missing files.
deathaxe
force-pushed
the
master
branch
2 times, most recently
from
3db7466 to
b084211
Compare
Closes #1690
Be little less restrictive as CWL e.g. provides \Ref completion instead of \ref
Ensure get_tex_root to always return normalized absolute paths.
If job name is specified e.g. via TEX directives, before this commit ... 1. latexmk failed to build the document with error 10. 2. logfile and created pdf documents were not found.
1. Fix [Finished ...] not being highlighted 2. print "1 page" vs. "n pages"
This commit adds support for unquoted filenames with whitespace appearing at the beginning of blocks. It's MikTeX, which creates such output.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
The upstream repository
SublimeText/LaTeXTools@masterhas some new changes that aren't in this fork. So, here they are, ready to be merged!This Pull Request was created programmatically by the githubpullrequests.