clearto erase the gCLI, or drag-select the output until I reach the left edge.
We'd definitely want to log all gCLI input and output.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.
To follow up on this, last June @Rinn added logPreferenceChangeFilter to filter out changes that drive you spare.yeah, the Swing element is the issue.
Testudinal Teachings is an enormous string to encode an array with no breaks. The more familiars you have, the more it gets ridiculous. QT makes it stand out as a problem because familiars last 11 rounds, but Autoscend or other familiar swapping scripts can do the same. The Swing element just scrolls the text in the viewport if it overflows, and leaves it with the assumption that you really want to see the rightmost character and not the many, many short charactered lines at the left margin.
Maximizer prefs also frequently cause this, but they often have spaces.