Skip to content

Conversation

@stsquad
Copy link
Contributor

@stsquad stsquad commented Apr 14, 2022

As described in the second patch. This is very much an RFC and I'm open to suggestions of better ways to solve the problem.

stsquad added 2 commits April 14, 2022 10:33
If you are using a system like "pass" to manage credentials you will
get a different form of error as you need a passphrase. Attempt to
catch the various forms. While we are it also fix a doc change which
was missed when mu4e--get-mail-password-regexp was changed.
This is an attempt to give a passive indication of hung email
collections by exposing a status on the main page. The typical failure
case for me is an expired ssh key session leading to background update
hanging because non-interactive sessions shouldn't interrupt the user
for key information. I also occasionally see mbsync hanging during
collection and just never exiting. At least this way I could see an
update started many hours ago and never completed.

However it's apparent that there are other notification and logging
mechanisms which such a thing should maybe use but none seemed to be
good fits. I'm open to a cleaner way to implement this even if it's
just in user hooks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant