> Pronounced FEH-too (/ˈfɛ.tuː/). Stress the first syllable. In Māori wh is an f sound, not a w. The macron in ū makes that vowel long, which is why the ASCII spelling doubles it.
oof. deliberate choice?
Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
11–20 of 40 posts
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#12> Pronounced FEH-too (/ˈfɛ.tuː/). Stress the first syllable. In Māori wh is an f sound, not a w. The macron in ū makes that vowel long, which is why the ASCII spelling doubles it. oof. deliberate choice?
You're right. Whetuu is actually correct in ASCII. I did study study some Te reo Māori a while ago. Will fix.
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#13I 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…
Why not, plenty of tools - atuin included - are doing that.
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#14I 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…
Why not, plenty of tools - atuin included - are doing that.
No, they are not? Atuin is not a shell prompt, you can use it with any prompt. Like Starship, Spaceship, liquidprompt, etc. None of those hijack shell history.
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#15Earlier quoted context omitted.
Why not, plenty of tools - atuin included - are doing that.
No, they are not? Atuin is not a shell prompt, you can use it with any prompt. Like Starship, Spaceship, liquidprompt, etc. None of those hijack shell history.
we are not talking about the same thing. I'm talking about ~/.whetuu - the tool doesn't hijack the shell history at all. You can rm -rf the store and your shell history is intact.
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#16please 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.
It already does. The releases page has prebuilt binaries for four targets plus a SHA256SUMS file. You can download the tarball straight from GitHub over TLS, verify it against the checksums, and run it. No script involved.
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#17Earlier quoted context omitted.
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.
It already does. The releases page has prebuilt binaries for four targets plus a SHA256SUMS file. You can download the tarball straight from GitHub over TLS, verify it against the checksums, and run it. No script involved.
[dead]
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#18It used to be the case that seeing cool Show HN projects would get me excited. Ever since the advent of agentic coding, that has been completely lost for me. 9/10 times now they are just claude produced slop with a 3 day long commit history. Quite sad.
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#19Earlier quoted context omitted.
No, they are not? Atuin is not a shell prompt, you can use it with any prompt. Like Starship, Spaceship, liquidprompt, etc. None of those hijack shell history.
we are not talking about the same thing. I'm talking about ~/.whetuu - the tool doesn't hijack the shell history at all. You can rm -rf the store and your shell history is intact.
The XDG spec tells you exactly where to place your files. It isn’t in $HOME/.your-project ever. You know about XDG enough to mention in your docs, so you should know.
It does hijacks shell history. If I press the up arrow, I expect _my shell_ to handle it how I configured it, not your tool. Because you’re saying your tool is a shell prompt!
A shell prompt is the program that runs before and after every shell command to show me contextual information like the current directory, and the exit code of the last command.
If you want this to be include customizations beyond the prompt, stop calling it a prompt.
Re: Show HN: Whetuu – a zero-config cross-shell prompt written in Zig
#20I 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…
I do want shell history with folders.
I tried a few (Atuin? McFly?) but the performance wasn't good with my massive zsh history (going back several years).
Zsh+fzf does a buttery smooth job (no folders though, unfortunately). Other tools start to stutter at scale.