Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

50% Positive

Analyzed from 179 words in the discussion.

Trending Topics

#history#fix#run#didn#arrow#commands#where#read#script#running

Discussion (6 Comments)Read Original on HackerNews

minrawsabout 2 hours ago
I didn't quite gel with it, seemed overly, well opinionated for no meaningful performance or otherwise improvement to any other simple prompt.
lfx39 minutes ago
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?*

seanhunter20 minutes ago
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).
yamafaktory28 minutes ago
Thanks for the feedback! You can run `whetuu paths` and will get that, I'll fix the readme.
kedislavabout 2 hours ago
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-4219 minutes ago
"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.