On Mon, Nov 22, 2021 at 09:29:13AM -0500, Antoine Beaupré wrote:
hehe. well, it's a matter of taste I guess. i also don't like
excessively long manual pages either, but in this case this can fairly
easily be solved by moving the configuration file documentation to a
`mbsyncrc(5)` manpage. The examples could live there or in the main
manpage. Or at least refer to the shipped examples file.
most of the manual is about the config file, so that wouldn't *really*
solve the problem (having the example in the main page would be kinda
backwards). but i like the idea of referring to the example file (i've
seen precedents for that on my debian system), so that's a settled
matter anyway. ^^
of course. i guess what i would like to see is a single summary line,
at the end of the job. basically the last printf would be enough, i
would guess.
that's a good idea. i'll even make it a bit more human-readable.
what i find really confusing about the config file syntax is that
sections are really not obvious at first. it's really a trial-and-error
process to generate a valid configuration file, and i think that could
be improved.
the manual explains it thoroughly and the example file kinda hints at it
(though i could make it more explicit), so someone approaching the whole
thing more systematically shouldn't have a problem. :P
*not* using a DSL and instead a more "standard" format would help...
well, that ship has kinda sailed even before i took over the project.
and i don't see this as a big enough pain point to warrant a format
change.
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
