termcolor
committed
| termcolor | committed | |
|---|---|---|
| 5 | 5 | |
| 446 | 94 | |
| - | - | |
| 5.8 | 7.9 | |
| 4 months ago | about 22 hours ago | |
| Rust | Rust | |
| The Unlicense | Apache License 2.0 |
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.
termcolor
-
Feedback on project idea
If you're going after a rice utility, you'll probably want to at least take a look at termcolor
-
Announcing erdtree 3.0.0: A multi-threaded general purpose disk-usage and filesystem utility
I personally regret adding NO_COLOR support to termcolor. See https://github.com/BurntSushi/termcolor/pull/63 and https://github.com/BurntSushi/termcolor/issues/72.
-
What is your favorite terminal colors library?
https://github.com/BurntSushi/termcolor, 345, 66k Recommended by https://blessed.rs/crates
-
Ouch 0.3.0 released!
I'm a little leery of clap taking on the role of color control. I've found that each library with "auto" support does it slightly differently and that really the best place for that policy is in the caller so there is a consistent experience and so it can adapt to the caller's needs. The WG-CLI has talked about this in the past and concolor family of crates is the result. I'm waiting on feedback for termcolor's use case (non-ANSI) before going 1.0 at which point we will probably make this the backend for clap's auto color support.
committed
-
Any good alternative to husky in rust to enforce and write conventional commits and for pre-commit source code linting??
I use https://github.com/crate-ci/committed and pre-commit (the python app)
-
[Gitoxide December Update]: a new object database and upcoming multi-pack index support
committed just reads commit messages between a range of commits, after resolving refs
-
Ouch 0.3.0 released!
For colors, I've found yansi to be great to work with. I then use concolor-control (example) and `concolor-clap (no clap3 support yet, example part 1 and example part 2). As you can see, I also like to organize my colors by the styling role they fill. The only reason I wrapped in that example is its part of the crate's API and didn't want the public API tied to yansi.
-
Git-cliff: generate changelog files from the Git history
While auto-generated changelogs aren't the best, they are better than nothing. Too often I've seen projects without a changelog which is especially annoying when dealing with breaking changes.
I've been considering switching to a changelog generator, either from Conventional Commits or from a folder of files just to avoid merge conflicts with the CHANGELOG file.
If people want enforcement of Conventional Commit, check out https://github.com/crate-ci/committed
- Committed – A commit message linter optionally supporting conventional commits
What are some alternatives?
rust-ansi-term - Rust library for ANSI terminal colours and styles (bold, underline)
auto-changelog-action
erdtree - A modern, cross-platform, multi-threaded, and general purpose filesystem and disk-usage utility that is aware of .gitignore and hidden file rules.
onefetch - Command-line Git information tool
ouch - Painless compression and decompression in the terminal
gitoxide - An idiomatic, lean, fast & safe pure Rust implementation of Git
clap-rs - A full featured, fast Command Line Argument Parser for Rust
git-hooks.nix - Seamless integration of https://pre-commit.com git hooks with Nix.
owo-colors - A zero-allocation no_std-compatible zero-cost way to add color to your Rust terminal
GitHub Changelog Generator - Automatically generate change log from your tags, issues, labels and pull requests on GitHub.
no_color - Website data for no-color.org
gnulib - upstream mirror