As a HPC system administrator, I have imagej installed in a module system (https://lmod.readthedocs.io/en/latest/) in a read-only location.
When a user attempts to change a setting, they are presented with this:
because of course the installation location is read-only for them.
ImageJ should honour Unix/Linux standards of placing configs either in $HOME/.imagej or even better the XDG standard, https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html which is configurable, but defaults to $HOME/.confg for config files.
As a HPC system administrator, I have imagej installed in a module system (https://lmod.readthedocs.io/en/latest/) in a read-only location.
When a user attempts to change a setting, they are presented with this:
because of course the installation location is read-only for them.
ImageJ should honour Unix/Linux standards of placing configs either in
$HOME/.imagejor even better the XDG standard, https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html which is configurable, but defaults to$HOME/.confgfor config files.