Hi,
in regard to https://sourceforge.net/p/abook/feature-requests/15/ , it became obvious that the abook application overrides structure information added manually to the addressbook file:
When removing comments from the original file, it will not be possible to add any structural documentation (like user-level sectioning). This is not crutial but it limits the freedom of the user to use the addressbook file as a "normal" configuration file. Although the addressbook's syntax seems identical to INI-styled configuration files.
Would it be possible to instead of overriding the addressbook file with a simple version of configuration syntax by the abook application, to use a more sophisticated configuration file handling mechanism which provides CRUD methods?
And thus preserve any user's valuable comments within the addressbook file?
What do you think?
abook overrides the whole file when saving.
It comes with mentioned drawbacks but any modification in the direction of "CRUD file operations" would inevitable imply much more code to create/debug/maintain which is something no-one is currently willing (aside from maintenance, there is no active abook developer currently)
Last edit: Raphaël 2022-03-14