carapace-bin
hishtory
carapace-bin | hishtory | |
---|---|---|
6 | 19 | |
703 | 2,363 | |
14.5% | - | |
9.8 | 9.8 | |
4 days ago | 6 days ago | |
Go | Go | |
MIT License | MIT License |
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.
carapace-bin
- FLaNK AI Weekly for 29 April 2024
- Carapace: A multi-shell completion library and binary
-
Release Radar • March 2024 Edition
It's exciting when something breaks out on its own, and that's what's happened with Carapace. Originally part of a 13-piece project, it now has a major first version and it's a multi-shell completion library and binary. Carapace consists of a pflag fork, a yaml spec, a shell lexer, a completion bridge and various scrapers. Congratulations to the team on shipping your first version 🥳.
- Show HN: Inshellisense – IDE style shell autocomplete
- Carapace-bin: multi-shell multi-command argument completer
-
Fish (shell) porting to Rust from C++
I use Carapace which provides completions across tons of shells.
hishtory
-
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?
complete - bash completion written in go + bash completion for go command
atuin - ✨ Magical shell history
The Platinum Searcher - A code search tool similar to ack and the_silver_searcher(ag). It supports multi platforms and multi encodings.
mcfly - Fly through your shell history. Great Scott!
subcmd - Another approach to parsing and running subcommands. Works alongside the standard flag package.
butterfish - A shell with AI superpowers
cobra - A Commander for modern Go CLI interactions
ckp - Store and reuse your history and one liner scripts from anywhere, better than gists
job - JOB, make your short-term command as a long-term job. 将命令行规划成任务的工具
fzshell - Fuzzy shell completions you didn't know you needed
elvish - Powerful scripting language & Versatile interactive shell
inshellisense - IDE style command line auto complete