Remix.run Logo
Show HN: Whetuu – a zero-config cross-shell prompt written in Zig(yamafaktory.github.io)
27 points by yamafaktory 3 hours ago | 7 comments
linsomniac 13 minutes ago | parent | next [-]

Unclear 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).

lfx an hour ago | parent | prev | next [-]

This 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?*

seanhunter 33 minutes ago | parent | next [-]

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).

yamafaktory 41 minutes ago | parent | prev [-]

Thanks for the feedback! You can run `whetuu paths` and will get that, I'll fix the readme.

minraws 2 hours ago | parent | prev | next [-]

I didn't quite gel with it, seemed overly, well opinionated for no meaningful performance or otherwise improvement to any other simple prompt.

kedislav 2 hours ago | parent | prev [-]

please stop piping into bash or sh. force people to use the editor, read the install script, and tell them how to run it

GuB-42 32 minutes ago | parent [-]

"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.