fix #H4060 - sysconf is re-read if no config file
Config file handling remembers the name of the last config file read in order for options processing to use it in messages, but it was also reused as default config file name if user-supplied config file name failed access() test. So the SYSCF file became the default user config file after it was used. The config file handling was a real mess. This patch fixes it for Unix but there is a lot of scope for typos in the changes for other platforms. Testing is needed.
This commit is contained in:
@@ -288,6 +288,8 @@ using /? to look up something by name, supplying multiple spaces (with no
|
||||
add support for the 'altmeta' option to the 'what-does' command ('&' or '?f')
|
||||
when wielded weapon becomes untouchable (after alignment change or polymorph)
|
||||
hero could be 'blasted by its power' twice in succession
|
||||
at startup, if sysconf had been read but user's own config file couldn't be
|
||||
read, sysconf got processed again as if it contained user's options
|
||||
|
||||
|
||||
Fixes to Post-3.6.0 Problems that Were Exposed Via git Repository
|
||||
|
||||
Reference in New Issue
Block a user