This has a lot of red flags: it looks like it's mostly machine translated, the packages come from unclear sources, and the GitHub repository itself appears to mostly contain scaffolding, none of the actual code of the manager itself[2]
2. All X-CMD code is hosted on the `main` branch. You can find direct links to each module's source code by browsing the modules section on our website: https://x-cmd.com/mod/env.
3. As a team based in China, we are continuously working to improve our English documentation. Our current priority is to first refine the Chinese documentation, which will then serve as the foundation for more accurate and comprehensive English translations.
4. All of the packages managed by x-cmd team, we collect them from developer official sources. Not maintained by third party contributors.
https://www.x-cmd.com/mod/jq is good example. `jq` and a couple of other tools that I run not-so-often leads to me needing to run i tseveral times with different arguments to get it correct, or read the manual once again. This tool might be helpful for those scenarios.
I think I was looking at distrobox or toolbox at the time, for graphical dev containers. And it has some helpers for that. There was a ton of other general quality of life stuff, for random laptop tasks. As much as anything I'm just so curious to see what all is packed in. Much smaller list, only like 60 subcommands.
Big contrast: afaik what I ran across relies on a lot of actually good open source software being already installed. In retrospect it seems really cool having a curated means to operate a laptop, to not have to go seek out tools for z y then z, never knowing what you are missing, when someone can have a nice all in one command for all kinds of little system management tasks.
Liftyee•5mo ago
lijunhao•5mo ago
1. In its early development, `x-cmd` was designed to integrate its modules directly into the shell's namespace. This approach meant that common commands, such as `ping`, could potentially be overridden to run `x ping`, leading to conflicts and behavior. 2. Recognizing these potential issues, we decided to retain the `x` prefix for all `x-cmd` commands. This ensures clarity and prevents namespace pollution. The `x` is intentionally short and acts as a dedicated namespace for `x-cmd`'s features.
I think this will provide a kind of flexibility for our users. Users could try something new or interesting using x-cmd script. But if these sripts fail, users could alway return to the mature original command and finish the tasks.
Future versions of `x-cmd` will introduce a comprehensive cross-shell shortcut configuration system, empowering users to easily manage their personalized command shortcuts.