ckp
Store and reuse your history and one liner scripts from anywhere, better than gists (by elhmn)
hishtory
Your shell history: synced, queryable, and in context (by ddworken)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
ckp
Posts with mentions or reviews of ckp.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-06-03.
-
How do you store you bash scripts and history so that you can access them from other machines ?
you can check it out here https://github.com/elhmn/ckp
hishtory
Posts with mentions or reviews of hishtory.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-06.
-
Show HN: Inshellisense – IDE style shell autocomplete
If you're more used to ctrl+r, you could try hiSHtory (https://github.com/ddworken/hishtory)
-
hiSHtory: Your shell history on steroids: Stored in context, synced to all your machines, and easily queryable
Including the server as part of the release sounds reasonable to me. I'm inclined to keep it as a separate file since most people don't need that feature, so I'd rather not unnecessarily increase the size of the main binary size. I filed https://github.com/ddworken/hishtory/issues/78 to track this.
- hiSHtory
- `hishtory` is a better shell history
- GitHub - ddworken/hishtory: Your shell history: synced, queryable, and in context
-
Show HN: HiSHtory: Your shell history in context, synced, and queryable
Ah, thank you commenting on this! This is absolutely unintentional and was the fault of a missing comment in the bash script (that I didn't notice because I generally use zsh). See https://github.com/ddworken/hishtory/commit/72ff95ab8b23c3be... and if you run `hishtory update` it should be all fixed.
What are some alternatives?
When comparing ckp and hishtory you can also consider the following projects:
bash-funk - bash-funk is a collection of useful commands for Bash 3.2 or higher.
atuin - ✨ Magical shell history
yq - yq is a portable command-line YAML, JSON, XML, CSV, TOML and properties processor
mcfly - Fly through your shell history. Great Scott!