I believe this addresses issue #456 where if you add a protonmail account you get an error. This is caused by prematurely returning from the case statement that queries whether you have a protonmail account or not.
Co-authored-by: rjl6789 <rlives6789@gmail.com>
I think a recent change tried to send output from crontab to dev/null to avoid messages appearing a) when setting the crontab, b) whenever mailsync is run. However the redirection was for the string concatenation meaning a null string was piped to cron obliterating the crontab (thank goodness for backups). I have put the redirection in the correct location (similar to a few lines above when removing the mailsync line). I have also redirected all output of the mailsync (both errors and normal messages) to dev null.
Co-authored-by: rjl6789 <rlives6789@gmail.com>
the prefix is not correct at least for Ubuntu distro. Since doc clearly
states the dependencis. We assume msmpt is on the PATH environment.
Co-authored-by: Lingyu Zhu <lynuszhu@gmail.com>
when u have multiple emails in neomutt at the same time, you can sometimes forget which email u'r currently viewing, so with this addition youll be able to see.
all i did was add the email to the default status bar configuration
* Run serverinfo query based on if proton or not
* If domain is already protonmail don't ask if it is
* Fix protonmail fingerprint extraction
* Update docs re: protonmail bridge timing out
This patch puts the environment variable PREFIX in more use. If
specified, mull-wizard Makefile substitute all instances of prefix with
the provided environment variable.
Signed-off-by: Ayman Bagabas <ayman.bagabas@gmail.com>
The current test did not terminate the script in cases when the user
already has a private GPG key, but they'd not initialized the password
store.
This leads to an infinite loop in the `getpass()` function.
The commit fixes https://github.com/LukeSmithxyz/mutt-wizard/issues/204
Checking for a secret key with format `<foo@bar.com>` may not work for
people that store key IDs in .gpg-id. Removing the `<` and `>` makes it
work for both beople that use emails and people that use IDs.
