Previous requests have focused on things that only go to the gCLI. Their absence in the session logs makes after the fact analysis difficult. The conversation seems to cease when people realize the mirror command will capture the gCLI content to a file. And then we go down a rabbit hole because the gCLI "interprets" HTML but the session and mirror logs just treat it as text.
I want an after the session file that is as verbose as it can be. I can then accept a less verbose gCLI (and tail -f the session log if I get warm fuzzy feelings from seeing things scroll by). So a variable logging level probably needs a guarantee that everything that goes to the gCLI gets into the log. When that happens then variable display levels makes sense. That will break the utility of mirror but I think that would be acceptable if the session log were unconditionally verbose.
I quickly checked the code and I'm not seeing a quick fix for the gCLI wrapping/scrolling.
We'd definitely want to log all gCLI input and output.
If we had log levels ala Log4J, it would totally break all existing log parsing, but it would be more friendly to more tools. Session logs could be unconditionally verbose, with gCLI logging being by level.
It's a big project, since you have to assign a log level to every logging message we have. We might also decide to get rid of the debug/session log difference. but unclear if that's needed in the verbose session log model.
We could also create a "things scrolling by too fast to read" pane for those who want a fuzzy feeling.
I've got some shelved code for making a context menu in the gCLI pane, btw. It lets you do things like "select an item you've just received and look it up in the wiki" or "select a weapon you've just checked Inventory for and equip it". If we make the gCLI pane less of a gCLI/Log window multi-purpose window, that makes more sense.