Make interface colors customizable

[unxed]

For sure turbo vision should allow this :)

[magiblot]

The main setback here is that I have to choose a configuration system, but I have never used one. Configuration files should be human-readable. Any suggestions?

[okbob]

čt 3. 12. 2020 v 1:03 odesílatel magiblot <notifications@github.com> napsal:

The main setback here is that I have to choose a configuration system, but I have never used one. Configuration files should be human-readable. Any suggestions?

https://turbo-c.soft32.com/screenshots/ http://gsntechnologies.net/blog/turbo-c-for-windows-7-and-vista.html

…

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEFO43GZLQLFITPRI5YZIDSS3IVJANCNFSM4ULCK3HA> .

[okbob]

https://github.com/caglartoklu/borlandp.vim čt 3. 12. 2020 v 5:07 odesílatel Pavel Stehule <pavel.stehule@gmail.com> napsal:

…

čt 3. 12. 2020 v 1:03 odesílatel magiblot ***@***.***> napsal: > The main setback here is that I have to choose a configuration system, > but I have never used one. Configuration files should be human-readable. > Any suggestions? > https://turbo-c.soft32.com/screenshots/ http://gsntechnologies.net/blog/turbo-c-for-windows-7-and-vista.html > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#9 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAEFO43GZLQLFITPRI5YZIDSS3IVJANCNFSM4ULCK3HA> > . >

[unxed]

The main setback here is that I have to choose a configuration system, but I have never used one. Configuration files should be human-readable. Any suggestions?

Why not to use well-known .ini file syntax?
For example, this is ready to use code to work with it from far2l (GPLv2):
https://github.com/elfmz/far2l/blob/master/utils/src/KeyFileHelper.cpp

[exebook]

JSON!

[magiblot]

Hey exebook,

JSON!

Yeah, I also think JSON makes everything simpler. But I'm not sure plain JSON is good enough, as it doesn't support comments. libconfig not only is adapted to the use case of storing configuration, but also uses a syntax very similar to JSON: http://hyperrealm.github.io/libconfig/libconfig_manual.html#Configuration-Files.

[exebook]

JSON allows /* */ AFAIK but not //. But anyway you can strip comments before calling JSONParse in your library of choice. Also you can put your comments in string properties like { comment: "blah" }

[ziotom78]

JSON allows /* */ AFAIK but not //. But anyway you can strip comments before calling JSONParse in your library of choice. Also you can put your comments in string properties like { comment: "blah" }

I know for sure that a few JSON parsers recognize comments, but this does not seem to be in the standard; it is however supported by JSON5.

Another option could be to use TOML: it was designed specifically for configuration files written by humans, it looks reasonably similar to INI files, it is easy to support it in C++ because there are header-only libraries, it is widely used and so it's likely that people already know how to write TOML files.