2 ms·
The 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 res
by yamafaktory 2mo ago
The 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 2mo 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 2mo agoThanks for the hint.
- drdexebtjl 2mo agoWe’ve been over this. Atuin is not a shell prompt.
- yamafaktory 2mo agoI'll try to make that a constructive argument and assume that the project shouldn't use the word "prompt".
- drdexebtjl 2mo 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.