`mu4e~start` is now `mu4e--start`.
shamefulCake1 opened this issue · 1 comments
shamefulCake1 commented
$SUBJ
A trivial fix seems to work.
mkcms commented
Thanks for reporting it! Fixed on master.
I'm gonna leave this issue open for a time to remind myself to look into using a higher level function instead. mu4e--start
looks internal and we shouldn't rely on it.