-
- Eza --hyperlink doesn't have "auto" mode so if I alias ls to it, ls | sed hacks will likely behave unexpectedly if I enable it: https://github.com/eza-community/eza/issues/703 and this also seems like an instance of it: https://github.com/eza-community/eza/issues/693
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
-
I'm totally the other way around, I rely on colorized output heavily.
But! There's supposed to be a solution to this, set $NO_COLOR to some value. https://no-color.org
Totally reasonable to file a bug report against tools which don't check and respect that env variable.
-
Seems quite similar to https://github.com/lsd-rs/lsd . How do they compare?
I know though lsd has one annoying bug when using it for grepping: https://github.com/lsd-rs/lsd/issues/1052
-
solarized
precision color scheme for multiple applications (terminal, vim, etc.) with both dark/light modes
Solarized is easy on the eyes and the colours are chosen for readability.
https://ethanschoonover.com/solarized/
The list on the site lacks some entries. Konsole has it built in and i bet Gnome Terminal too.
-
If tooling would simply use the Base16 Framework[0] instead of arbitrary colors from “256 color” or “RGB” color modes, this would be much less of a problem.
[0] https://github.com/chriskempson/base16
-
I think they are not referring to ls, but to exa [0], which is not maintained anymore.
[0]https://github.com/ogham/exa
-
- Let the user set their shell colors however they want (presumably using [2]), and use the ANSI shell colors (and a few more) according to the base16 style guide [1]. Some translation between shell colors and base16 colors will be necessary, e.g. base16 says that a language keyword should use the color base0E, which in [2] corresponds to ANSI shell color 13.
My impression is that the base16 specification is not sufficiently general for most tools to implement it in a totally unbambiguous way, but if users can set their own colorschemes with a config file, it's not hard for a user to come up with a base16-approximating colorscheme template file, from which other users can generate a config file that sets a specific base16 colorscheme.
[1]: https://github.com/chriskempson/base16/blob/main/styling.md
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
This link also has a large list of additional tools I hadn't heard of but look interesting.
https://github.com/ibraheemdev/modern-unix
-
Related: https://github.com/uutils/coreutils "Cross-platform Rust rewrite of the GNU coreutils"
-
If you don't like the default tab bar, you can use the zjstatus plugin (https://github.com/dj95/zjstatus) to replace it with a customizable one that can show the tab index.
-
maintained-modern-unix
A collection of modern/faster/great alternatives to common unix commands, which is maintained.
this one is maintained
https://github.com/johnalanwoods/maintained-modern-unix
-
NOTE OF WARNING:
BY DEFAULT these ignores anything included in your `.gitignore` folder. So if you think it is a straight find replacement, you'll likely be surprised. fd discussion here[0]
Just make sure that when recommending people these tools that this is clear because if they don't read the docs (lol who does) they'll miss this part.
This is a pet peeve of mine. I wish the people that make these replacement coreutils (and others) would leave the defaults as very similar to the original tool. I do really like the new functionalities but if you market it as "an alternative" ("It is a simple, fast and user-friendly alternative to find") then they should respect the defaults of the original because it reduces new user surprise. I mean aliases exist... So it is better to have in your ~/.${SHELL##*/}rc file to have `alias fd='fd --ignore'` than `alias fd='fd --no-ignore'`.
Side note/pro tip: use `\command` if you want to use an unaliased version. An example of this is that I have `alias grep='grep --color=always --no-messages --binary-files=without-match` but this can sometimes be problematic because the color option can change the character representation so if you pipe this into `curl` you will get errors. This is not the case in all piping, but it is a shocking and confusing experience when you first encounter it. You can validate this by `echo "Hello world" | \grep --color=always "Hello" | hexdump` and then `!!:s^always^never`
[0] https://github.com/sharkdp/fd/issues/612