Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
yamafaktory.github.io
Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
1–10 of 40 posts
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#2please stop piping into bash or sh. force people to use the editor, read the install script, and tell them how to run it
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#3I didn't quite gel with it, seemed overly, well opinionated for no meaningful performance or otherwise improvement to any other simple prompt.
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#4This is awesome -
*A history picker on the up arrow*
*Commands are recorded once they finish, and only when they exited cleanly, so typos never clutter the list.*
Where the history is stored? Is it possible to store in single place like user root dir?*
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#5This is awesome - *A history picker on the up arrow* *Commands are recorded once they finish, and only when they exited cleanly, so typos never clutter the list.* Where the history is stored? Is it possible to store in single place like user root dir?*
Thanks for the feedback! You can run `whetuu paths` and will get that, I'll fix the readme.
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#6This is awesome - *A history picker on the up arrow* *Commands are recorded once they finish, and only when they exited cleanly, so typos never clutter the list.* Where the history is stored? Is it possible to store in single place like user root dir?*
Does that mean you can't go up and fix a typo? If so, that sounds strictly worse than what you get by default from the shell (which is up arrow, ctrl-r and various other methods of history searching, and history substitution or editing to fix errors).
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#7please stop piping into bash or sh. force people to use the editor, read the install script, and tell them how to run it
"curl | sh" certainly feels wrong, but in the end, even if you download and read the script before running commands, let's be real: you are going to run a binary that you didn't inspect.
Not saying you shouldn't check your scripts, I usually do, I like to know where the files are going in case the installer messes up, but the risks tend to be overstated compared to running the executable itself.
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#8Unclear to me: does this also do shell history? I'm using atuin and not interested in changing that. I did just switch over to oh-my-posh a few weeks ago and it's good, but I would be open to trying something else to compare, particularly since I have some directories with monorepos where oh-my-posh goes out to lunch for a couple seconds. Also oh-my-posh sometimes loses its mind and switches back to the default prompt rather than my customized one.
I'm on the fence about my current "2-line prompt, collapsing to a single line" when I press enter. I like that it gives me a lot of room, but there's some information I find I'm wishing was persisted in my shell history (git branch, previous command execution time for long running commands).
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#9I don’t want my prompt to also handle shell history, and especially in such an “opinionated” way.
What happens to my actual shell-provided history?
Does too much for me.
edit:
> Both files follow the XDG base directory spec, so neither lives in the install directory. Removing whetuu with rm -rf ~/.whetuu cannot take your history with it. whetuu paths prints both locations.
Please stop creating directories in my $HOME.
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#10please stop piping into bash or sh. force people to use the editor, read the install script, and tell them how to run it
What if this project offered binaries from GitHub releases instead? How do you read those?
It's more realistic to decide if you trust the source, GitHub user yamafaktory in this case. Then you can ensure that your method of download uses TLS.