Message logging
#29 (closed) was a specific issue about printing network status to stderror, but the discussion that it prompted raised the broader issue of how Balsa communicates with the user. Copying some of that discussion:
Albrecht Dreß @albrecht · 1 week ago
Balsa's terminal logging is in a mess, to be honest… We already discussed it ~two years ago, and in some places, the g_log (and friends) mechanism has been implemented; I typically use it in the code I contribute, see the README file for some log domains (not sure if all are listed).
As the user will usually never see them (unless Balsa is stared from the command line), IIRC the issue has been regarded as very low priority. But it's good to have it as ticket, so it's not forgotten!
So here it is, not forgotten!