Skip to content
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

Support multiple configuration file locations #28

Open
haimgel opened this issue Sep 20, 2020 · 2 comments
Open

Support multiple configuration file locations #28

haimgel opened this issue Sep 20, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@haimgel
Copy link
Owner

haimgel commented Sep 20, 2020

The app should support multiple configuration file locations:

Linux

  • Per-user config file ~/.config/display-switch/display-switch.ini
  • Global config file /etc/display-switch.ini

MacOS

  • Per user config file ~/Library/Preferences/display-switch.ini
  • Global config file /Library/Preferences/display-switch.ini

Windows

  • Per user config file same-as-now
  • Global config file TBD

Should try to load per-user config file, and fall back to a global config file.

@haimgel haimgel added the enhancement New feature or request label Sep 20, 2020
@haimgel haimgel mentioned this issue Sep 20, 2020
@pm215
Copy link
Contributor

pm215 commented Feb 22, 2021

I think that supporting "use config file specified via a command line argument" would be useful as well; this would be handy for testing a new config file without having to copy it into the official installed-on-the-system location.

@chocmake
Copy link

chocmake commented Oct 28, 2022

Would be nice if the CLI could detect the config file in the application directory on Windows (ie: wherever the CLI binary is located). In that sense it'd make it more portable. Perhaps could be considered for the global config file location, which would also match the behavior of various CLI programs (eg: yt-dlp, Nirsoft tools).

I also like the suggestion of being able to override the default path via an argument, particularly if one could bypass a per-user directory from being created initially.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants