Would you accept a documentation patch to make that more discoverable, or is that just something obvious that I didn't know?
Great, maybe I'll make this my first contribution.
I'm trying to debug a problem connecting to an Office 365 account, but the only feedback the TUI gives me isLOGIN FAILED. To facilitate working through this problem as well as perhaps to implement other features, I'd like to be able to find logging output somewhere.
aerc.goI see that if stdout is a a TTY, logging is a no-op (if it's not a TTY, I'm not sure how I could interact with it anyway?). Am I missing a way to configure logging output, or is it planned?