3 ms·
I 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 m
by drdexebtjl 3mo ago
I 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.
- yamafaktory 3mo agoWhy not, plenty of tools - atuin included - are doing that.
- drdexebtjl 3mo agoNo, 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.
- yamafaktory 3mo agowe 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.
- drdexebtjl 3mo agoThe 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.
- yamafaktory 3mo agoThe XDG Base Directory spec covers config/data/cache/state, it does not define where executables go. Whetuu history & cache are both compliant as both go to respectively ~/.local/share/whetuu/ ($XDG_DATA_HOME) & ~/.cache/whetuu/ ($XDG_CACHE_HOME).Atuin, cargo and many other tools are doing the same. By the way, Atuin also rebinds the up arrow.
- em-bee 3mo agoThe XDG Base Directory spec covers config/data/cache/state, it does not define where executables go. it does: https://specifications.freedesktop.org/basedir/latest/ https://specifications.freedesktop.org/basedir/latest/ User-specific executable files may be stored in $HOME/.local/bin. Distributions should ensure this directory shows up in the UNIX $PATH environment variable, at an appropriate place. i prefer ~/bin/ but this is better than creating you own directory that needs to be added to the path.
- yamafaktory 3mo agoThanks for the hint.
- drdexebtjl 3mo agoWe’ve been over this. Atuin is not a shell prompt.
- yamafaktory 3mo agoI'll try to make that a constructive argument and assume that the project shouldn't use the word "prompt".
- drdexebtjl 3mo ago> it does not define where executables go It does. Read the spec. It’s in $HOME/.local/bin. It’s just not configurable like the other paths.
- reddit_clone 3mo agoI 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.
- drdexebtjl 3mo agoYeah, I do too. From a shell history tool. Not from a shell prompt.