Hacker News new | ask | show | jobs
by mike-cardwell 558 days ago
I don't have my work laptop to hand to compare, but I usually run "just" to get a list of commands and what they do, rather than "just --list". Hope that saves you 7 key presses going forwards.
2 comments

Running `just` will invoke the first recipe, so you need to add one that invokes `just --list` for this to work — see https://just.systems/man/en/listing-available-recipes.html and my sibling comment.
That seems like the most useless pattern to take from make, especially when you name your tool ”just”.

Just what?

> Just what?

"Oh... come on! Just... <waving hands angrily>"

Pretty clear to me :).

The same applies to make without arguments though, make what? Grammar / word meaning aside, unknown / missing commands printing the help file or suggestions is a good pattern.
I think it's less grammatically ambiguous with make. It implicitly means "make <the project>". For most projects that's pretty well defined (and also grammatically correct since 'make' is a verb and 'just' is not).

But even so it would have been a better design for `make` to list top level targets or something.

Just execute.
Hmm. Maybe the dev that set it up made the first recipe run `just --list`
Yeah, I've been adding `just help` as an alias for `just --list` and making it the first recipe for this reason.
Not as much as 7, you can just type `just -l`.