A user reported, that he feels like being spammed on the command line by the output, the program produces when called in a terminal window (and this is my feeling too).

Indeed, bluefish makes an inconsistent usage of debugging output. Sometimes it uses macros (DEBUG_MSG), which only produce output if bluefish is configured to do so. But often there is output added via printf() or g_print(). Sometimes such messages show possible programming errors or corner cases, but the related Glib functions are not used (like g_warn_if_fail() etc.), although they would provide us useful information like the line number or enable backtraces.

IMO we should completely rework, which information is printed, how and when and improve the usefulness of this information. I would like to make this an item for target 2.2.4 or 2.2.5.