Annyoing [appimage/stdout] and [appimage/stderr] strings in log files about linuxdeploy-plugin-appimage HOT 6 CLOSED

This is not a mess, but actually very useful. This way, one can clearly see what's going on in plugins, and what output belongs to the plugins. This helps debugging issues on systems like Travis CI.

It's more like a mess that appimagetool doesn't use stderr/stdout correctly.

Nothing to fix here.

from linuxdeploy-plugin-appimage.

"appimage" sounds like some "AppImage" problem when in fact it is the "linuxdeploy AppImage plugin"

from linuxdeploy-plugin-appimage.

Instead of prefixing each(!) line, you could have one line saying *** linuxdeploy AppImage plugin running now *** or something like that, so users would know where the following lines belong to

from linuxdeploy-plugin-appimage.

That's a feature, and documented behavior. qt stands for the qt plugin, etc.

I think there is a general issue with "plugin names". For instance, as you noticed --list-plugins does show the plugin names, but they might not be taken as such by the user.

from linuxdeploy-plugin-appimage.

Instead of prefixing each(!) line, you could have one line saying *** linuxdeploy AppImage plugin running now *** or something like that, so users would know where the following lines belong to

That used to be the default, however one could never be sure who's created what message (especially when plugins use the logging framework linuxdeploy's libraries provide). Prefixing the output clarifies the situation.

from linuxdeploy-plugin-appimage.

Maybe it's a matter of personal preference, but I think the current solution looks too "technical" and too "complicated". Not eye-friendly to me.

from linuxdeploy-plugin-appimage.