You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried using a new build of himalaya with neovim and the rust log debug coming on stderr confuse neovim in that it believes something went wrong.
Eg when sending an email:
Save draft [OK]
Sending email…
^[[2m2025-01-10T15:13:56.747012Z^[[0m ^[[33m WARN^[[0m ^[[2mimap_client::client::tokio^[[0m^[[2m:^[[0m IMAP BINARY extension not supported, using fallback
Error detected while processing function <lambda>79[1]..<SNR>43_on_exit[6]..function <lambda>79[1]..<SNR>43_on_exit:
line 6:
E605: Exception not caught: CLI error, see :messages for more information
A solution is to make an intermediate shell script the quiets down debug messages:
himalaya_fix.sh
One idea coming to my mind is to use stdout for any user output or error, and stderr for logs. This way we can easily play with the exit code (which is actually discarded by the Vim plugin — everything captured on stderr is an error):
If exit code 0, then stdout contains output
If exit code not 0, then stdout contains an error
Any data on stderr is a log, and can easily be put in a dedicated buffer.
I tried using a new build of himalaya with neovim and the rust log debug coming on stderr confuse neovim in that it believes something went wrong.
Eg when sending an email:
A solution is to make an intermediate shell script the quiets down debug messages:
himalaya_fix.sh
and in nvim/init.lua:
setting the environment variable inside the init.lua file did not work, neither did setting the variable at nvim call.
The text was updated successfully, but these errors were encountered: