feat: reworked the structure for communication/neomutt

Using neomutt as the module for email instead of just "email" as used
previously.
"email" was ambigious in that it was too vague on what it was supposed
to do with email, now neomutt clearly specifies that we plan to use
neomutt as our email client.
However mbsync and notmuch are still used under the hood that is not
reflected in the module name "neomutt". This is fine as they only serve
the purpose of downloading and querying the emails which may be
considered a background feature.

1 files changed, 0 insertions, 7 deletions

diff --git a/modules/communication/neomutt/assertions.nix b/modules/communication/neomutt/assertions.nix
index 22434a4..b85280e 100644
--- a/modules/communication/neomutt/assertions.nix
+++ b/modules/communication/neomutt/assertions.nix
@@ -17,13 +17,6 @@
       '';
     }
     {
-      assertion = !config.communication.neomutt.enable || config.communication.email.enable;
-      message = ''
-        communication.neomutt is enabled but communication.email.enable is not.
-        neomutt requires the email module (mbsync + notmuch) to be enabled.
-      '';
-    }
-    {
       assertion = !config.communication.neomutt.enable || config.terminal.kitty.enable;
       message = ''
         communication.neomutt is enabled but terminal.kitty.enable is not.