Latency and friction - Githubissues

pimalaya / himalaya-vim

Vim frontend for Himalaya CLI email client

https://github.com/pimalaya

MIT License

22 stars 2 forks source link

Latency and friction #4

Closed alecandido closed 3 years ago

alecandido commented 3 years ago

Sorry to bother you with issues, I'm finding them while trying it.

There are a couple of things that are quite annoying, even if not preventing usage:

every time you change view he asked to press ENTER
- I know it's probably because you are running a shell program and I don't know how to solve it
every time you change view you have to wait a bit
- I believe it's because it's downloading every time all the information, maybe it can be solved by caching a bit and update asynchronously

Of course they are just ux improvements.

soywod commented 3 years ago

every time you change view he asked to press ENTER

This may be because of your Vim cmd height. The quick fix is to increase it with set cmdheight=3. I will check how to prevent logs showing on more than 1 line.

every time you change view you have to wait a bit

Indeed, a call is made each time you do an action. The quick fix is to use an offline IMAP synchroniser (like isync or OfflineIMAP). This way you remove the network latency. I will see how to add cache to improve UX.

alecandido commented 3 years ago

This may be because of your Vim cmd height. The quick fix is to increase it with set cmdheight=3. I will check how to prevent logs showing on more than 1 line.

This I will try, indeed I keep cmdheight=1, maybe I can search a bit.

The quick fix is to use an offline IMAP synchroniser (like isync or OfflineIMAP).

Perfect, if you have any working setup, with external utilities, can you share some details?

soywod commented 3 years ago

Perfect, if you have any working setup, with external utilities, can you share some details?

Check out mutt-wizard. It allows you to set up with ease a isync/msmtp/neomutt environment.

[EDIT] See also the ArchWiki about isync, it is a valuable resource.

soywod commented 3 years ago

For now, the tool can only fetch messages from a local/remote IMAP server. But it could be great to fetch from a local Maildir folder, this way no latency!

alecandido commented 3 years ago

I don't have your experience with mail protocols, but while waiting for some native implementation, is there any way to have himalaya itself spawning a third-party IMAP server locally to interact with? Or maybe is it as expensive as implementing Maildir support?

soywod commented 3 years ago

I need to read more about Maildir, but it seems to be just files in folders. So it should be easier and faster than a local IMAP server. I'm analysing a Rust crate that parses Maildirs, I will let you know! For now I try to focus on other "mandatory" features (the one I miss to use Himalaya in production), like copy/move/delete a msg, add attachments when writting a msg etc

alecandido commented 3 years ago

Perfectly fine!

soywod commented 3 years ago

I move the issue there, since it's not related to the UI: https://github.com/soywod/himalaya/issues/43.