Last 12 weeks · 113 commits
3 of 6 standards met
Right now manual says that "bat should be in path" in Syntax tests section. Inside update.sh there's a call of python script that generates highlighted files. For me that wasn't obvious why script generated un highlighted file firstly. I'd recommend rewrite python script in such a way that it'll use version if it's presented or somehow ask what program to use. Or adding lines in the manual to ease friction of setting up tests.
Repository: sharkdp/bat. Description: A cat(1) clone with wings. Stars: 57523, Forks: 1467. Primary language: Rust. Languages: Rust (97.4%), Python (1.8%), Shell (0.7%), Nix (0.2%), Batchfile (0%). License: Apache-2.0. Topics: cli, command-line, git, hacktoberfest, rust, syntax-highlighting, terminal, tool. Latest release: v0.26.1 (3mo ago). Open PRs: 26, open issues: 314. Last activity: 17h ago. Community health: 85%. Top contributors: sharkdp, dependabot[bot], keith-hall, Enselic, eth-p, dependabot-preview[bot], cyqsimon, einfachIrgendwer0815, mohamed-abdelnour, Oliver-Looney and others.
Rust
The package indicated itself as architecture, which is nonexistent on Debian, it still uses codename even if the package if only.
This PR improves the documentation for running syntax tests. Clarifies that the syntax test script (tests/syntax-tests/update.sh) calls from the PATH. Explains that the script regenerates the highlighted output files under tests/syntax-tests/highlighted/, which are used to verify syntax highlighting. Adds explicit instructions for adding the debug build to PATH when only is used. Provides example error message when is not found on PATH. Notes that places in ~/.cargo/bin, usually already in PATH. This change addresses Issue #2376 by making the syntax tests documentation more concrete and beginner-friendly.