argc
just
argc | just | |
---|---|---|
14 | 169 | |
646 | 17,513 | |
- | - | |
9.3 | 9.0 | |
11 days ago | 7 days ago | |
Rust | Rust | |
Apache License 2.0 | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
argc
- Argc: Easily create feature-rich CLIs in bash
- Easily create a feature-rich command-line application in Bash.
- Docopt.sh β Command-Line Argument Parser for Bash 3.2, 4, and 5
-
Runme: A shell-script based task runner written in rust
Runme is based on argc, which can flexibly define task parameters and generate informative completions
- Whats the easiest way to configure argument parsing in bash
- GitHub - fumieval/clap4shell: Standalone wrapper of clap for shell scripts
- Argc: A bash cli framework, also a task management & automation tool.
-
A cross-plaform task runner
See docs/task-runner for more details.
- Argc: The easiest way to handle bash command-line options
-
IT Pro Tuesday #194 - AutoHotkey Scripts, Command-Line Tool, PowerShell Tutorial & More
Argc is an easier way to handle sh/bash cli parameters. Allows you to create a command line program by simply describing the options, parameters, and subcommands in comments. Once you set it to work, Argc extracts parameter definitions from comments, parses command line arguments, outputs error text/help info for an abnormal parameter or the parsed parameter variable for a normal one, and finally, calls any subcommand function. A shout out to sigoden for this suggestion.
just
-
I stopped worrying and loved Makefiles
I don't like makefiles, but I've been enjoying justfiles: https://github.com/casey/just
- Just a Command Runner
-
Ask HN: Any tool for managing large and variable command lines?
I started using just [0] on my projects and have been very happy so far. It is very similar to make but focused on commands rather than build outputs.
Define your recipes and then you can compose them as needed.
[0] https://github.com/casey/just
-
Ask HN: What software sparks joy when using?
just - https://github.com/casey/just
-
GitHub switched to Docker Compose v2, action needed
Welp there is absolute chaos in that thread -- guess it's not an April Fools joke.
I wonder if relying on CI for anything other than provisioning machines is a mistake -- maybe we should have never moved from doing things from local scripts written in $LANGUAGE.
That said, I'm probably biased since I'm a massive fan of things like `make` and more appropriately for the current age, `just`[0]
[0]: https://github.com/casey/just
-
Which command did you run 1731 days ago?
> When a command has some cognitive requirements I create a script with some ${1:-default} values and I store them all in $PATH enabled local/bin
I would consider using just for this:
https://github.com/casey/just
-
Using Make β writing less Makefile
Your coworker's experience is more principled: Make is a mediocre tool for executing commands. It wasn't ever designed for that. Although it is pretty common to see what you are mentioning in projects because it doesn't require installing a dependency.
For a repo where an easy to install (single binary) dependency is a non-issue, consider using just. [1] You get `just -l` where you can see all the command available, the ability to use different languages, and overall simpler command writing.
[1] https://github.com/casey/just
-
Show HN: Just.sh β compiler that turns Justfiles into portable shell scripts
This is fantastic, but I'd say that this solution is somewhat in response to this open issue from 2019:
https://github.com/casey/just/issues/429
I really wish just was included as a package in distributions.
-
Sharing Saturday #496
So far, I didn't work on new features at all but on stabilizing the ground for further development: 1. CMake lists and modules were rewritten a lot, now managing builds and their configurations is much lesser pain. 2. Brought in Justfile for regular tasks, and it's great, no less. 3. Linters, formatters, analyzers for almost all the code (except for Janet for now, as because of it being a niche and young technology, it didn't get enough attention yet). 4. ECS stub. Now runtime class doesn't look like a god object. 5. Started writing unit tests which didn't happen with my personal projects before and maybe indicates how serious am I about this one :D 6. Some of previously hardcoded data has been moved to INI files. Now, if I release the game in 10 years, and in 10 more years some eccentric person decides to make a variant of it, it will be slightly simpler.
-
Whatβs with DevOps engineers using `make` of all things?
i've grown to like this for my personal projects. https://github.com/casey/just
What are some alternatives?
argi - Argument parsing for the future π
Task - A task runner / simpler Make alternative written in Go
docopts - Shell interpreter for docopt, the command-line interface description language.
cargo-make - Rust task runner and build tool.
slap - Painless shell argument parsing and dependency check.
cargo-xtask
Trash-Generator - A Rust program that generates files containing random characters (AKA trash)
Taskfile - Repository for the Taskfile template.
clap4shell - Standalone wrapper of clap for shell scripts
CodeLLDB - A native debugger extension for VSCode based on LLDB
docopt - This project is no longer maintained. Please see https://github.com/jazzband/docopt-ng
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.