-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong macOS configuration path #147
Comments
I noticed that when irust is launched, the above configuration file gets overwritten and reverts back to the default config. |
For the the second issue you mentioned: if you close all instances of irust, then modify the config files then open irust, it should work , otherwise its a new bug |
Yes, after closing an instance of irust, editing the configuration file, and then launching irust again, the modified settings are not applied. Upon opening the configuration file again, it is confirmed to have reverted to the default settings. |
Then it's a different bug but I can't reproduce on Linux, so this might take some time to get fixed. |
First of all, it seems that the config path for macOS in the README is incorrect. I checked the real path by using
irust -h
.As mentioned above, the location of the path on macOS being in
Application Support
, which is not very user-friendly, is problematic. I feel that many macOS users prefer to place their config files under~/.config/
. For example, tools like Nushell default to placing config files inApplication Support
, but some users are dissatisfied with this setup.Personally, I think the best approach is the one used by Alacritty, where config files are searched for in the following locations. Would it be possible to adopt a similar configuration setup?
The text was updated successfully, but these errors were encountered: