An Illustrated Guide to Useful Command Line Tools
1–10 of 108 posts
Re: An Illustrated Guide to Useful Command Line Tools
#2Amazing how many of those are written in Rust and Go.
Re: An Illustrated Guide to Useful Command Line Tools
#3Can someone explain the misuse of cat, which bat solves?
Re: An Illustrated Guide to Useful Command Line Tools
#4Amazing how many of those are written in Rust and Go.
unless I'm missing something, jq isn't[1]
Re: An Illustrated Guide to Useful Command Line Tools
#5Can someone explain the misuse of cat, which bat solves?
I guess they just meant it as in "reading code," when in fact bat is better tool just for reading code.
Re: An Illustrated Guide to Useful Command Line Tools
#6Can someone explain the misuse of cat, which bat solves?
Using cat to catenate a file to standard input isn't misuse, but it looks like bat performs syntax highlighting.
Re: An Illustrated Guide to Useful Command Line Tools
#7Re: An Illustrated Guide to Useful Command Line Tools
#8Can someone explain the misuse of cat, which bat solves?
They are referring to using cat to print out a file to the terminal. I'm not sure that's a "misuse", but personally I've never done it, using "more" or "less" instead. "bat" really is a replacement for more/less, only with additional features such as syntax highlighting in source code.
Re: An Illustrated Guide to Useful Command Line Tools
#9Can someone explain the misuse of cat, which bat solves?
They are referring to using cat to print out a file to the terminal. I'm not sure that's a "misuse", but personally I've never done it, using "more" or "less" instead. "bat" really is a replacement for more/less, only with additional features such as syntax highlighting in source code.
I use:
cless() {
pygmentize -O style= "$1" 2>/dev/null | less
}
I have programs that depend on pygmentize so I am not sure I will use bat anytime soon when I already have pygmentize and less, or at least not for it having syntax highlighting.Re: An Illustrated Guide to Useful Command Line Tools
#10Amazing how many of those are written in Rust and Go.
I don't think it says much about the tools themselves though, it just makes sense when you look at the author's GitHub and see a bunch of Rust projects.