You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There are a few stdpath("data") hardcoded throughout the code, e.g. for history's path and frecency's store_file.
It'd be nice to have an option to make sure any state file has customizable path, so we can use stdpath("state") if desired, putting those files in ~/.local/state/nvim/[snacks/] by default, and keeping ~/.local/share/nvim clean.
Describe the solution you'd like
Ensure no path is hardcoded, and can be customized.
Describe alternatives you've considered
Overriding $XDG_DATA_HOME can achieve this, but also can mess with any program/command spawned from neovim which depend from it being set to the proper path. Overrding stdpath itself is possible, but quite hacky.
Additional context
Modern XDG specifications recommend putting "state files" (files which are written at runtime based on user's interactions) in $XDG_STATE_HOME (usually ~/.local/state), leaving $XDG_DATA_HOME for user-owned program files and assets instead.
The text was updated successfully, but these errors were encountered:
Did you check the docs?
Is your feature request related to a problem? Please describe.
There are a few
stdpath("data")
hardcoded throughout the code, e.g. for history'spath
and frecency'sstore_file
.It'd be nice to have an option to make sure any state file has customizable path, so we can use
stdpath("state")
if desired, putting those files in~/.local/state/nvim/[snacks/]
by default, and keeping~/.local/share/nvim
clean.Describe the solution you'd like
Ensure no path is hardcoded, and can be customized.
Describe alternatives you've considered
Overriding
$XDG_DATA_HOME
can achieve this, but also can mess with any program/command spawned from neovim which depend from it being set to the proper path.Overrding stdpath itself is possible, but quite hacky.
Additional context
Modern XDG specifications recommend putting "state files" (files which are written at runtime based on user's interactions) in
$XDG_STATE_HOME
(usually~/.local/state
), leaving$XDG_DATA_HOME
for user-owned program files and assets instead.The text was updated successfully, but these errors were encountered: