crash.log: loaded plugin

[hius07]

Every start of the program, then every opening a book, then every switching to file browser and back we have a record in the crash.log

koreader/frontend/apps/filemanager/filemanager.lua

Line 528 in 859327d

logger.info("FM loaded plugin", name,

and the same from reader.
Is it necessary? Can it be changed to the debug info to lighten regular crash.log?

[poire-z]

I exactly do this in my own patch.

-            logger.info("RD loaded plugin", plugin_module.name,
+            logger.dbg("RD loaded plugin", plugin_module.name,

No real idea if it can be useful for some users, to know one plugin has loaded correctly - and/or if we need to do something to log them only once for FM and only once for RD.
Pinging @zwim @yparitcher : has this ever been useful to you when developping your own plugins ?

[zwim]

The message is/was usefull. But it would be no problem if it is changed from logger.info to logger.dbg

[NiLuJe]

Keep in mind that there's one in filemanager and one in readerui ;).

[hius07]

@NiLuJe, I have permanently errors in crash.log about these kindle fonts
cannot register font </usr/java/lib/fonts/Caecilia_LT_66_Medium_Italic.ttf>
cannot register font </usr/java/lib/fonts/Caecilia_LT_76_Bold_Italic.ttf>

May I change to true? (I've tried and the errors have gone)

koreader/frontend/fontlist.lua

Line 76 in ed68445

["Caecilia_LT_66_Medium_Italic.ttf"] = false,

koreader/frontend/fontlist.lua

Line 78 in ed68445

["Caecilia_LT_76_Bold_Italic.ttf"] = false,

[NiLuJe]

It possibly depends on FW version, but, sure, go ahead ;).

[yparitcher]

The message is/was usefull. But it would be no problem if it is changed from logger.info to logger.dbg

Same here