-
Notifications
You must be signed in to change notification settings - Fork 71
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
Document the (likely) on-disk location of settings clearly #135
Comments
I'd rather defer to the backing API documentation than redocument it and risk introducing errors or confusion. You're almost certainly better off not using no-arg if you care about these details. But it is (apparently) possible to supply a custom |
Hello there @chris-hatton and @russhwolf , did you guys manage to find an easy way of deleting the preferences for a jvm application whilst using in dev mode?? |
It would still be nice to know where the preferences are on disk. I can't catch it editing anything either on Linux. |
@i3vie Assuming you're talking about JVM preferences on Linux, take a look at |
@chris-hatton , did you find the location where the settings were being stored ? |
I'm using the JVM target on macOS, with no-arg
Settings()
API and despite following up the documentation forPreferences.userRoot()
I am unable to find where the settings are stored on disk. This is really important for development, to be able to inspect/backup/clear them etc. Suggest this would make a valuable improvement to the docs.Edit: This is actually driving me nuts(!) The settings are persisting between runs alright, I just can't find where they are! Inspecting the
Preferences
object in debugger doesn't enlighten much either, giving anabsolutePath
of/
, but I wouldn't expect that App to be successfully writing to the root of my drive, and sure enough it isn't. Triedlsof
but can't catch the App in the act of accessing theplist
. I'm going to have to switch to using the arg-ful constructor forSettings
just to be able to specify the file location.The text was updated successfully, but these errors were encountered: