View Single Post
Old 10-05-2022, 12:48 PM   #17
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,911
Karma: 6120478
Join Date: Nov 2009
Device: many
I think since we already keep additional info in the gitignored .bookinfo file we should probably go that way. I want to keep checkpoint code reasonably self contained and relying on compiling a binary git library for every platform is a bit too much in my opinion.

I guess we could revisit the idea of creating a checkpoint now prompting for a message but only if a settings says yes. But I really do not like that.

So lets explore serializing a list of tags and tag messages to .bookinfo that can be easily parsed to supply that info first before moving on.

How does that sound?
KevinH is offline   Reply With Quote