reitzig/texlogparser

View on GitHub
README.md

Summary

Maintainability
Test Coverage

Showing 47 of 47 total issues

Line length
Open

Any feedback about the code quality and usefulness of the documentation would be
Severity: Info
Found in README.md by markdownlint

Fenced code blocks should be surrounded by blank lines
Open

```
Severity: Info
Found in README.md by markdownlint

Ordered list item prefix
Open

4. Expected message with
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

Severity: Info
Found in README.md by markdownlint

Headers should be surrounded by blank lines
Open

### Contributors
Severity: Info
Found in README.md by markdownlint

Consider starting bulleted lists at the beginning of the line
Open

* Use `_latex` option `-file-line-error` to get higher accuracy regarding source files and lines.
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

The interface is rather narrow; your main entry point is class
Severity: Info
Found in README.md by markdownlint

Line length
Open

[![Yard docs](http://img.shields.io/badge/yard-docs-green.svg)](http://www.rubydoc.info/gems/tex_log_parser/) **Ë™**
Severity: Info
Found in README.md by markdownlint

Line length
Open

By default, `texlogparser` reads from stdin and writes to stdout. That is, you can use it like so:
Severity: Info
Found in README.md by markdownlint

Lists should be surrounded by blank lines
Open

* Issues around messages below warning level have low priority.
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

* The shell output of the initial run of `pdflatex` et al. on a new file can
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

(La)TeX gourmets and Ruby developers.
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

provided helpful test cases and insight in LaTeX Stack Exchange chat.
Severity: Info
Found in README.md by markdownlint

Line length
Open

**Bonus:** Convince as many package maintainers to use the same standardized, robust way of writing to the log.
Severity: Info
Found in README.md by markdownlint

Line length
Open

This adds so little runtime overhead that there are few reasons _not_ to use it.
Severity: Info
Found in README.md by markdownlint

Line length
Open

Please report any logs that get parsed wrong, be it because whole messages are not found,
Severity: Info
Found in README.md by markdownlint

Ordered list item prefix
Open

3. Expected number of error, warning, and info messages (the latter optional).
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

to improve overall efficacy. Bad linebreaks are
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

It is therefore more robust to use the log file as written to disk, and/or
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

the output resp. log file produced by a subsequent run.
Severity: Info
Found in README.md by markdownlint

Line length
Open

[![Test Coverage](https://api.codeclimate.com/v1/badges/748992a2c5f6570797d4/test_coverage)](https://codeclimate.com/github/reitzig/texlogparser/test_coverage) **Ë™**
Severity: Info
Found in README.md by markdownlint

Unordered list indentation
Open

* log line numbers (where the message starts and ends),
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

This adds so little runtime overhead that there are few reasons _not_ to use it.
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

For bug reports and feature requests, the usual rules apply: search for
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

Any feedback about the code quality and usefulness of the documentation would be
Severity: Info
Found in README.md by markdownlint

Line length
Open

There are two ways to parse logs: with the command-line program and via the underlying Ruby API.
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

Calling `parse` on it will yield a list of
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

contain output of subprograms, and be complicated in other ways as well.
Severity: Info
Found in README.md by markdownlint

Ordered list item prefix
Open

2. The engine(s) you use, e.g. `pdflatex`, `xelatex`, or `lualatex`.
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

and note on which lines it changes file scopes in wrong ways.
Severity: Info
Found in README.md by markdownlint

Headers should be surrounded by blank lines
Open

### Rubyists
Severity: Info
Found in README.md by markdownlint

Consider starting bulleted lists at the beginning of the line
Open

* [egreg](https://tex.stackexchange.com/users/4427/egreg) and
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

If you _also_ know a little Ruby, please consider translating those data into
Severity: Info
Found in README.md by markdownlint

Line length
Open

* [Increase the maximum line length](https://tex.stackexchange.com/a/52994/3213) as much as possible
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

Note that the original log file will still be written to `example.log`,
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

Severity: Info
Found in README.md by markdownlint

Line length
Open

* Use `_latex` option `-file-line-error` to get higher accuracy regarding source files and lines.
Severity: Info
Found in README.md by markdownlint

Line length
Open

[![Maintainability](https://api.codeclimate.com/v1/badges/748992a2c5f6570797d4/maintainability)](https://codeclimate.com/github/reitzig/texlogparser/maintainability)
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

The usual options and, later, update mechanisms of Rubygems apply;
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

[Message](http://www.rubydoc.info/gems/tex_log_parser/LogParser/Message)
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

(Don't worry, real errors will stick around!)
Severity: Info
Found in README.md by markdownlint

Ordered list item prefix
Open

5. _Advanced_: In case of wrong source files, run `texlogparser -d` on the log
Severity: Info
Found in README.md by markdownlint

Consider starting bulleted lists at the beginning of the line
Open

* Is the API designed in useful ways?
Severity: Info
Found in README.md by markdownlint

Trailing spaces
Open

[![Maintainability](https://api.codeclimate.com/v1/badges/748992a2c5f6570797d4/maintainability)](https://codeclimate.com/github/reitzig/texlogparser/maintainability)
Severity: Info
Found in README.md by markdownlint
Category
Status