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
Describe the bug
On macOS the base directory for cheats and config are different without NAVI_* environmental variables being present.
To Reproduce
% echo $(navi info config-path)
/Users/parkero/.config/navi/config.yaml
% echo $(navi info cheats-path)`
/Users/parkero/Library/Application Support/navi/cheats
Expected behavior
Base navi path would be the same for both in the absence of user configuration
Versions:
Navi: 2.23.0
macOS: 13.6.6
zsh 5.9 (x86_64-apple-darwin22.0)
Additional context
This came to my attention as I had a previous config.yaml changing my colors, but when I went to edit the config (through the default navi cheat "edit config file") it showed an empty file.
Either location seems fine, but odd to have them spread throughout the file tree.
I can write up a pull request if I know what the desired behavior should be, or feel free to close if working as intended.
The text was updated successfully, but these errors were encountered:
Thanks for opening your first issue here! In case you're facing a bug, please update navi to the latest version first. Maybe the bug is already solved! :)
Describe the bug
On macOS the base directory for cheats and config are different without
NAVI_*
environmental variables being present.To Reproduce
Expected behavior
Base navi path would be the same for both in the absence of user configuration
Versions:
Additional context
This came to my attention as I had a previous config.yaml changing my colors, but when I went to edit the config (through the default navi cheat "edit config file") it showed an empty file.
Either location seems fine, but odd to have them spread throughout the file tree.
I can write up a pull request if I know what the desired behavior should be, or feel free to close if working as intended.
The text was updated successfully, but these errors were encountered: