The idea here is to store a copy of the config file in /home/{user}/.megazeux or /Users/{user}/.megazeux or C:\Users\{user}\AppData or C:\Documents and Settings\{user}\you get the idea. There might be other things that could go in there as well. I don't know if there has been much of a demand for this (besides some users having difficulty finding the config file?) but it might be a thing to think about.
Report ID | 583 | Title | OS user directories |
Product | Archived Requests | Status | Implemented (Severity 0 - None Assigned) |
Version | 2.90 | Fixed in | GIT |
Page 1 of 1
Report ID #583: OS user directories
#1
Lachesis
Posted 22 June 2013 - 04:08 PM
"Let's just say I'm a GOOD hacker, AND virus maker. I'm sure you wouldn't like to pay for another PC would you?"
xx̊y (OST) - HELLQUEST (OST) - Zeux I: Labyrinth of Zeux (OST) (DOS OST)
w/ Lancer-X and/or asgromo: Pandora's Gate - Thanatos Insignia - no True(n) - For Elise OST
MegaZeux: Online Help File - Keycode Guide - Joystick Guide - Official GIT Repository
xx̊y (OST) - HELLQUEST (OST) - Zeux I: Labyrinth of Zeux (OST) (DOS OST)
w/ Lancer-X and/or asgromo: Pandora's Gate - Thanatos Insignia - no True(n) - For Elise OST
MegaZeux: Online Help File - Keycode Guide - Joystick Guide - Official GIT Repository
Page 1 of 1
Replies (1 - 3)
#2
ajs
Posted 24 June 2013 - 12:00 AM
IMO this would be best served by supporting magic expansions in the include directive for the config parser. It doesn't make sense to install a 'copy' of the config file into the user's directory; for one, the package management system won't know where to put it, and what happens when new users are added to the system?
The best approach would seem to be to allow users to override keys set by the 'system' config. For example we already have pad.config included by default; maybe just adding support for something like:
include $HOME/.config/megazeux
Allowing that file not to exist, and expanding HOME using getenv() would be enough for Linux/OS X users? Then we slap it on the bottom of the default config and we are done.
--ajs.
The best approach would seem to be to allow users to override keys set by the 'system' config. For example we already have pad.config included by default; maybe just adding support for something like:
include $HOME/.config/megazeux
Allowing that file not to exist, and expanding HOME using getenv() would be enough for Linux/OS X users? Then we slap it on the bottom of the default config and we are done.
--ajs.
#3
Lachesis
Posted 12 June 2017 - 04:57 PM
Updating status to: Implemented
Updating version to: 2.90
Issue fixed in: GIT
Updating version to: 2.90
Issue fixed in: GIT
"Let's just say I'm a GOOD hacker, AND virus maker. I'm sure you wouldn't like to pay for another PC would you?"
xx̊y (OST) - HELLQUEST (OST) - Zeux I: Labyrinth of Zeux (OST) (DOS OST)
w/ Lancer-X and/or asgromo: Pandora's Gate - Thanatos Insignia - no True(n) - For Elise OST
MegaZeux: Online Help File - Keycode Guide - Joystick Guide - Official GIT Repository
xx̊y (OST) - HELLQUEST (OST) - Zeux I: Labyrinth of Zeux (OST) (DOS OST)
w/ Lancer-X and/or asgromo: Pandora's Gate - Thanatos Insignia - no True(n) - For Elise OST
MegaZeux: Online Help File - Keycode Guide - Joystick Guide - Official GIT Repository
Page 1 of 1
0 User(s) are reading this issue
0 Guests and 0 Anonymous Users
Powered by IP.Tracker 1.3.2 © 2025 IPS, Inc.