A user reports notifications not working on their setup because there is
no display id contained in the `ps`/`pgrep` output concerning the Xorg
process.
This commit checks if there's a display server running at all, and if so
it sends notifications even if there's no display id.
Resolves https://github.com/LukeSmithxyz/mutt-wizard/issues/661
remove old vars like pass_prefix, muttdir
reorder mailbox detection to find inbox case and later delim
offline delim set to _ which should avoid most issues
When the transition is made from an offline profile to an online
profile, there is still someone else's macro - side effects...
Variables, macros, and so on must be taken-into-account
**symmetrically** with any of the `mutt-wizard`'s profiles.
Part 2 of 2 for "Log-on not successful" bug when using ProtonMail.
The curl login check uses the imap(s) protocol, which means it will use
the default ports. However, when using ProtonMail, these ports are
different (namely 1143 instead of 993).
We now use the port variable in the curl login command, defaulting to
993 when the port was not overridden.
The port variable was already set when the ProtonMail flag (-p) was set.
Bug mentioned in:
Fixes:
- https://github.com/LukeSmithxyz/mutt-wizard/issues/608
- https://github.com/LukeSmithxyz/mutt-wizard/issues/622
Part 1 of 2 for "Log-on not successful" bug when using ProtonMail.
The curl login check defaults to `imaps` when `protocol` isn't set.
Because ProtonMail isn't using any TLS, we have to use the `imap`
protocol.
The `protocol` variable was never set, so now we set it when the
ProtonMail flag (-p) is set.
Bug mentioned in:
Fixes:
- https://github.com/LukeSmithxyz/mutt-wizard/issues/608
- https://github.com/LukeSmithxyz/mutt-wizard/issues/622