-
-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor the way output works #74
Comments
In fact the |
Logs added for |
Should Perhaps it would be helpful to distinguish between two kinds of outputs: "content" vs "logging". And use |
It's a good point indeed, I like the idea! |
In fact it depends on the ouptut type. For |
Another idea that comes to mind is to send all logging output to |
I am not so fan of this idea, it sounds a bit "hacky". I prefer to keep the
|
Added in v0.2.4 🎉 |
I use the following script to bulk move emails to another folder:
This script doesn't output anything, so I have no way of knowing the list of messages that just got moved by that command (that I constructed on the fly). I can script the logging manually, but it would be more convenient if the CLI had an option to log all mutable actions that himalaya takes on my mail account.
The text was updated successfully, but these errors were encountered: