A build log analysis tool so that your PDE (Personal Development Environment) can have a list of files that contain errors. Currently, it supports
- alire https://alire.ada.dev/
- angular https://angular.io/
- biome https://biomejs.dev/
- cargo https://github.com/rust-lang/cargo
- clang https://clang.llvm.org/
- dune https://dune.build/
- eslint https://eslint.org/
- go https://go.dev/
- gradle (java only) (Tests are not supported for the moment) https://gradle.org/
- java (Only exceptions) https://www.java.com/en/
- karmaJasmine https://karma-runner.github.io/latest/index.html
- maven https://maven.apache.org/
- nix https://nixos.org/
- odin https://odin-lang.org/
- typos https://github.com/crate-ci/typos
- v https://vlang.io/
- zig https://ziglang.org/
with plans for more.
Regularly tested on
- linux
- Windows 10
Install the rust.
git clone https://github.com/emilycares/logana
cd logana
cargo build --releaseAnd add it to your path
In this case the parser will be guessed by the command.
logana -c "cargo build --color always"In bash "|&" will also pipe sterr.
mvn clean install |& logana --parser maven --input stdinIt will create an output file named ".logana-report".
I use logana to get a faster feedback loop from a build error to a mistake I made in some file. For working on rust projects, i use:
logana -w -c "cargo test"or the other way
find **/*.rs | entr logana -c "cargo test --color always"The point is there are times where this does no hold up or is inconsistant. I have started to build this tool because i sometimes i get different errors in the compiler. Also i want to jump easily to printed paths to sourcecode. Regardless if it is in compilation unit test or at runntime. That is the goal.
The editor support allows the editor to parse the ".logana-report" into its now error list. Plugins are available here: