-
-
Notifications
You must be signed in to change notification settings - Fork 274
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
[test] Trying to use just
and see how it goes...
#1875
base: dev
Are you sure you want to change the base?
Conversation
You can see all the [hidden] default tasks with
and if you want to know what is going on, you can
in nushell to save the result to a file |
I've always been curious as to why espanso encourages external build tools at all -- it seems like it increases the complexity of the build process, and I'm not sure what the upside is. For example, on macOS, I just ignore cargo make and build with the standard cargo tooling -- the compilation succeed and the binary works as expected. Is it just for the extra steps of e.g. creating One of the only parts of rust that I don't care for is how the small standard library leads to lots and lots of external dependencies, which IME have a poor track record of being maintained over time. I'm definitely of the camp that tries to minimize external dependencies when I can! |
Nice point. This test was introduced by my frustration using cargo-make, which I consider still unintuitive at its latest version. I wanted to
in addition, this binary has to be packaged in different formats
This is even more difficult because you need to compile everything above with different scripts (bash, zsh or powershell). There is no silver bullet here. |
Thanks for a thorough response. I agree on all points that it's a tough issue! I think my preference would be to use neither if possible:
|
Hi! This is a test, bip bop
I'm testing how complex is just, to replace
cargo-make
This is a great example to take note
cargo binstall justfile