https://github.com/vhdirk/inox
Email with notmuch rust
https://github.com/vhdirk/inox
email gtk4 gtk4-rs mail notmuch rust
Last synced: 9 months ago
JSON representation
Email with notmuch rust
- Host: GitHub
- URL: https://github.com/vhdirk/inox
- Owner: vhdirk
- License: gpl-3.0
- Created: 2018-03-17T16:03:00.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2022-01-18T09:37:45.000Z (over 4 years ago)
- Last Synced: 2025-04-12T19:09:53.007Z (about 1 year ago)
- Topics: email, gtk4, gtk4-rs, mail, notmuch, rust
- Language: Rust
- Homepage:
- Size: 1.02 MB
- Stars: 28
- Watchers: 7
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Inox
> Email with Notmuch Rust
[](https://travis-ci.org/vhdirk/inox)
An experimental email client based on notmuch, along with other utilities like
afew and offlineimap/isync.
The UI is ported from [Geary](https://wiki.gnome.org/Apps/Geary), and a lot of inspiration comes from [Astroid](https://github.com/astroidmail/astroid) and [alot](https://github.com/pazz/alot).
I like how alot is all command driven. I also like how VSCode/Atom/Textmate work.
So that's probably how I want this thing to work, too.
## Status
You can read mails, and even that needs improvements.
## Goals
* UI: although I'm an avid terminal user, I like mail to be displayed in a proper
desktop client. I'm aiming for a nice and full-featured and command-driven UI.
For now, the toolkit of choice is GTK. However; VsCode's extension model
seems to work pretty well. A sort of vscode for mail would be pretty cool.
* Settings: should be stored in easily readable/editable config files,
so you can centralize them in your dotfiles.
* Editor: While Astroid relies on an external editor for writing emails, I aim for a
default embedded editor. I do like the option of using the editor of your
liking, though.
The embedded editor would be plaintext (not WYSIWYG) with rendering markdown
or reStructuredText to html (like github/gitlab).
* Plug-ins/extensions. If everything stays in rust, WASM would be the way to go.
If not, it would probably look like vscodes extension model.
* Core: Everything not UI related should end up centralized. Somewhat like
Mailcore2.