https://bugs.kde.org/show_bug.cgi?id=218297
--- Comment #12 from Simon <freisi...@gmail.com> --- The problem with letting KSharedConfig handle the path is, that it is not clearly specified what it does given an "invalid" path (e.g. a directory, a non-existing parent directory), so I decided to handle this myself and always use the standard location of the given path isn't valid. What do you want to achieve by changing the database directory given at command line in the configuration dialogue, which in general is different from the one in the config file? I mean even if that just resets the database directory at runtime and leaves the config file be, that is in my opinion misleading, as on next startup the new location won't be used (neither the config file nor the command line option is automatically changed to the new path). -- You are receiving this mail because: You are watching all bug changes.