-
Notifications
You must be signed in to change notification settings - Fork 5
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
Parse all ledger errors / warnings #1
Comments
Also, there are no column numbers printed by |
Ledger's output right now is a kind of "stack", which you're right, does not indicate columnar information since that info is implicit in the layout. We could perhaps add a "--machine-readable" option or something, which would output error messages intended for programmatic consumption? |
Yeah, that'd be nice if it's easy to do, but I wouldn't want you to add any extra complexity on my account. It's really satisfying to get this feedback inline in the buffer, and perhaps supporting machine-readable output directly would lead to better tools... Please let me know if you give Oh, and thanks for ledger. It made last week as enjoyable for me as a week of accounting could ever be. |
That's awesome that you're doing this, @purcell, I really appreciate it. :) I will definitely get |
I haven't looked in the ledger repo, but perhaps it has some files with example errors? |
There are a few expected-failing cases in the regression test directory, but they aren't just pure input files. |
This would be really great :) |
This initial version of
flycheck-ledger
was mainly developed in order to display errors for unbalanced transactions, e.g.However, other
ledger
error messages are laid out differently, e.g.I'd love to get feedback from @jwiegley on whether it might make sense to review
ledger
's error/warning output with a view to making it consistent and easily machine-readable. Or perhaps there's already such a solution available.The text was updated successfully, but these errors were encountered: