Save Screen Space: option to view logs vertically at right

Code is usually a fairly narrow column.

So, rather than

__________________________________________
code
code                   [wasted space]
code
------------------------------------------
logs
logs                   [wasted space]
logs
__________________________________________

how about

__________________________________________
code                      |     logs
code                      |     logs
code                      |     logs
code                      |     logs
code                      |     logs
code                      |     logs
code                      |     logs
___________________________________________

Presto! Easier to see more of both.

That depends on the code length and the whatever’s coming out of the logs, because:

___________________________________________________________________________
code-------------------------------<MOSTLY GET REQUESTS WITH LARGER PATHS>
code---------------------------------------------------------------------
code---------------------------------------------------------------------
code
__________________________________________________________________________
LOGS
(node:544) UnhandledPromiseRejectionWarning: Error: Something took too long to do.
    at timeout.client.setTimeout (/rbd/pnpm-volume/0be04d99-7540-41f3-96f0-0d16fc82a413/node_modules/.registry.npmjs.org/discord.js/11.5.1/erlpack@0.1.0/node_modules/discord.js/src/client/ClientManager.js:40:57)
    at Timeout.setTimeout [as _onTimeout] (/rbd/pnpm-volume/0be04d99-7540-41f3-96f0-0d16fc82a413/node_modules/.registry.npmjs.org/discord.js/11.5.1/erlpack@0.1.0/node_modules/discord.js/src/client/Client.js:436:7)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
(node:544) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 11)
(node:544) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Such logs would look congested in that space.

Yes, I agree that that’s common too.

That’s why I suggested the column view as an option, rather than a default.