From bf3d5342c22af342dd0bfe919aaa40ab1ee14ffd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A9ment=20DOUIN?= Date: Mon, 9 Dec 2024 21:51:31 +0100 Subject: [PATCH] doc(readme): add FAQ entry about aerc, mutt and alpine comparison --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index 565a095b..5b746d7d 100644 --- a/README.md +++ b/README.md @@ -501,6 +501,16 @@ You can also manually edit your own configuration, from scratch: ## FAQ +
+ How different is it from aerc, mutt or alpine? + + Aerc, mutt and alpine can be categorized as Terminal User Interfaces (TUI). When the program is executed, your terminal is locked into an event loop and you interact with your emails using keybinds. + + Himalaya is also a TUI, but more specifically a Command-Line Interface (CLI). There is no event loop: you interact with your emails using shell commands, in a stateless way. + + Additionaly, Himalaya CLI is based on `email-lib`, which is also part of the Pimalaya project. The aim is not just to propose a new terminal interface, but also to expose Rust tools to deal with emails. Anyone who knows Rust language can build his own email interface, without re-inventing the wheel. +
+
How to compose a message?