Discussion:
how to debug non-zero exit code
Victor A. Stoichita
2016-10-17 07:47:48 UTC
Permalink
Hi list,

Since yesterday my mu4e signals an error "Update process returned with
non-zero exit code".

Usually I’d look for the cause by running "mbsync -a" then "mu index" in
a terminal. This time, both commands exit with zero status in the
shell (checked it with "echo $?"). Is there a way to get more verbose
debug output from mu4e itself ?

I have mu 0.9.16 and emacs 24.5.1

Cheers,
Victor
--
You received this message because you are subscribed to the Google Groups "mu-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mu-discuss+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Dirk-Jan C. Binnema
2016-10-18 19:37:37 UTC
Permalink
Post by Victor A. Stoichita
Hi list,
Since yesterday my mu4e signals an error "Update process returned with
non-zero exit code".
Usually I’d look for the cause by running "mbsync -a" then "mu index" in
a terminal. This time, both commands exit with zero status in the
shell (checked it with "echo $?"). Is there a way to get more verbose
debug output from mu4e itself ?
I have mu 0.9.16 and emacs 24.5.1
Perhaps try to replicate what mu4e does as closely as possible, ie;

(start-process-shell-command "test-mu4e" "test-mu4e"
mu4e-get-mail-command)

Then check what's in the test-mu4e buffer.

Kind regards,
Dirk.
--
Dirk-Jan C. Binnema Helsinki, Finland
e:***@djcbsoftware.nl w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C
--
You received this message because you are subscribed to the Google Groups "mu-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mu-discuss+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Victor A. Stoichita
2016-10-25 13:28:45 UTC
Permalink
Post by Dirk-Jan C. Binnema
Perhaps try to replicate what mu4e does as closely as possible, ie;
(start-process-shell-command "test-mu4e" "test-mu4e"
mu4e-get-mail-command)
Then check what's in the test-mu4e buffer.
Thanks Dirk-Jan!

It’s probably an instance of Murphy’s law applied to asking for help,
but the error vanished "by itself" and now I can’t reproduce it any
longer. I’m positive though it was here for a few days before I asked.
I’ll use your advice to debug if it comes back.

All the best,
Victor
--
You received this message because you are subscribed to the Google Groups "mu-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mu-discuss+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Continue reading on narkive:
Loading...