Line length
Any feedback about the code quality and usefulness of the documentation would be
Fenced code blocks should be surrounded by blank lines
```
Ordered list item prefix
4. Expected message with
Headers should be surrounded by blank lines
### Contributors
Consider starting bulleted lists at the beginning of the line
* Use `_latex` option `-file-line-error` to get higher accuracy regarding source files and lines.
Trailing spaces
The interface is rather narrow; your main entry point is class
Line length
[](http://www.rubydoc.info/gems/tex_log_parser/) **Ë™**
Line length
By default, `texlogparser` reads from stdin and writes to stdout. That is, you can use it like so:
Lists should be surrounded by blank lines
* Issues around messages below warning level have low priority.
Trailing spaces
* The shell output of the initial run of `pdflatex` et al. on a new file can
Trailing spaces
(La)TeX gourmets and Ruby developers.
Trailing spaces
provided helpful test cases and insight in LaTeX Stack Exchange chat.
Line length
**Bonus:** Convince as many package maintainers to use the same standardized, robust way of writing to the log.
Line length
This adds so little runtime overhead that there are few reasons _not_ to use it.
Line length
Please report any logs that get parsed wrong, be it because whole messages are not found,
Ordered list item prefix
3. Expected number of error, warning, and info messages (the latter optional).
Trailing spaces
to improve overall efficacy. Bad linebreaks are
Trailing spaces
It is therefore more robust to use the log file as written to disk, and/or
Trailing spaces
the output resp. log file produced by a subsequent run.
Line length
[](https://codeclimate.com/github/reitzig/texlogparser/test_coverage) **Ë™**
Unordered list indentation
* log line numbers (where the message starts and ends),
Trailing spaces
This adds so little runtime overhead that there are few reasons _not_ to use it.
Trailing spaces
For bug reports and feature requests, the usual rules apply: search for
Trailing spaces
Any feedback about the code quality and usefulness of the documentation would be
Line length
There are two ways to parse logs: with the command-line program and via the underlying Ruby API.
Trailing spaces
Calling `parse` on it will yield a list of
Trailing spaces
contain output of subprograms, and be complicated in other ways as well.
Ordered list item prefix
2. The engine(s) you use, e.g. `pdflatex`, `xelatex`, or `lualatex`.
Trailing spaces
and note on which lines it changes file scopes in wrong ways.
Headers should be surrounded by blank lines
### Rubyists
Consider starting bulleted lists at the beginning of the line
* [egreg](https://tex.stackexchange.com/users/4427/egreg) and
Trailing spaces
If you _also_ know a little Ruby, please consider translating those data into
Line length
* [Increase the maximum line length](https://tex.stackexchange.com/a/52994/3213) as much as possible
Trailing spaces
Note that the original log file will still be written to `example.log`,
Line length
* Use `_latex` option `-file-line-error` to get higher accuracy regarding source files and lines.
Line length
[](https://codeclimate.com/github/reitzig/texlogparser/maintainability)
Trailing spaces
The usual options and, later, update mechanisms of Rubygems apply;
Trailing spaces
[Message](http://www.rubydoc.info/gems/tex_log_parser/LogParser/Message)
Trailing spaces
(Don't worry, real errors will stick around!)
Ordered list item prefix
5. _Advanced_: In case of wrong source files, run `texlogparser -d` on the log
Consider starting bulleted lists at the beginning of the line
* Is the API designed in useful ways?
Trailing spaces
[](https://codeclimate.com/github/reitzig/texlogparser/maintainability)
There are no issues that match your filters.