-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add a command-line option --porcelain
for machine-readable output
#15
Conversation
EmacsIn emacs, open a file such as M-x compile
explcheck --porcelain -- e102.tex This will cause emacs to execute explcheck and let you navigate among the errors by clicking or using Lines in a different format such as file-wide warnings and errors are ignored by emacs, as expected. However, all issues are recognized as errors by emacs, whereas we would like it to recognize warnings. VimIn vim, open a file such as :set errorformat=%f:%l:%c:\ %m
:set makeprg=explcheck\ --porcelain\ --\ %
:make This will cause vim to execute explcheck and let you navigate among the errors with commands Lines in a different format such as file-wide warnings and errors are ignored by vim, as expected. |
Emacs seems to use a collection of different patterns
Adding |
I made this change in commit 0a4aa68 from this PR: Demonstration
EmacsWarnings and errors are now correctly recognized by emacs: |
@FrankMittelbach: I believe that this should conclude this PR. |
Am 13.12.24 um 22:53 schrieb Vít Starý Novotný:
@FrankMittelback: I believe that this should conclude this PR.
yes Vit, except for misspelling my name :-)
|
Sorry about that, should be all good now. 👍 |
don't worry... with my track record of typos ... it is just that misspelling might result in not reaching me (it did, but that is because I already contributed to this issue I guess). |
This PR makes the following changes:
--porcelain
for machine-readable output.Demonstration
This change was made after a discussion with @FrankMittelbach in #8 (comment) and below. It should enable better integration with text editors in the absence of language sever protocol (LSP) support in this early version of explcheck, as discussed in #8 (comment).
I will test this change with Vim and emacs later today and will post screenshots as an interim documentation of the feature. Please, let me know if this is what you had in mind, @FrankMittelbach.
This PR closes ticket #8, together with pull requests #14 and #16.