You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a project utilising a similar config file syntax as rlog does.
The logic consequence was to join them both.
It's working, but rlog complains about unkown or malformed settings:
rlog - Malformed line in config file file:line. Ignored. rlog - Unknown or illegal setting name in config file file:line. Ignored.
Having multiple config file for a single application is a nightmare for me.
So I decided to comment out corresponding lines in my version of rlog.
What about officially supporting multi function config files instead?
Regards,
Trickx
The text was updated successfully, but these errors were encountered:
This could probably be done and would require 'sections' of sorts to be introduced. I don't want to break the old config file format, though.
We could do something like in the .ini file format. But if the first non-blank or non-comment line is NOT a section identifier then we'd still assume it's the old style file format. Rlog could have an '[rlog]' section heading.
greetings to the most far away location from my perspective :-)
Sectioning the config file sounds good to me.
Currently the log file, I would like to merge with looks simirlar to the following example.
I can easily add an [rlog] section.
I'm working on a project utilising a similar config file syntax as rlog does.
The logic consequence was to join them both.
It's working, but rlog complains about unkown or malformed settings:
rlog - Malformed line in config file file:line. Ignored.
rlog - Unknown or illegal setting name in config file file:line. Ignored.
Having multiple config file for a single application is a nightmare for me.
So I decided to comment out corresponding lines in my version of rlog.
What about officially supporting multi function config files instead?
Regards,
Trickx
The text was updated successfully, but these errors were encountered: