mu VS Mosh

I like mu4e (https://github.com/djcb/mu) for reading emails. You'll need to run mu init [email protected] (append as many --my-address entries as email addresses you receive mail at) in your Maildir and mu4e should start reading it.

For all details, see https://github.com/djcb/mu/blob/release/1.10/NEWS.org (and I'd recommend

And djcb already fixed it: https://github.com/djcb/mu/issues/2420 !

I've tried to follow the release notes here, but find it hard to follow... for instance, the releases jump from 1.4.15 to 1.6.0? (So where is 1.5.5?) Is there a compilation of all these changes from e.g. ~ to -- and other general refactoring?

> Surely there is a space for minimalist office suites and email clients,

FWIW, my email life improved massively when I left the likes of Thunderbird and KMail behind for the simplicity of mu/mu4e [1]. I hear similarly stellar things about Notmuch [2]. I'm never going back to an email client that even thinks about itself in relation to "office suites".

[1] https://www.djcbsoftware.nl/code/mu/

[2] https://notmuchmail.org/

and maildir-utils to index for search, https://www.djcbsoftware.nl/code/mu/

If you haven’t already, and I know this doesn’t hold up for GUI emacs or vim, but consider running them through https://mosh.org/

FWIW, I wouldn't try to parse escape sequences "directly" from the input bytestream -- it's easy to end up with annoying bugs. Longer-term it's probably better to separate the logic e.g.:

- First step (for a UTF-8-input terminal emulator) means "lexing" the input bytestream as UTF-8 into a stream of USVs, which involves some subtleties (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- Second step is to run the DEC parser/FSM logic on the sequence of USVs, which is independent of the escape sequences (https://vt100.net/emu/dec_ansi_parser ; https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- And then the third step is for the terminal to execute the "dispatch"/"execute"/etc. actions coming from the FSM, which is where the escape sequences and control chars get implemented (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

Without this separation, it's easier to end up with bugs where, e.g., a UTF-8 sequence or an ANSI escape sequence is treated differently when it's split between multiple read() calls vs. all in one call.

Btw, you can use mosh to hide the latency of SSH. https://mosh.org/

I've been using Kitty's SSH features for as long as I can remember but I recently setup Mosh and I really like how it doesn't drop connections and supports roaming.

I am surprised many people write about ssh into a server. Mosh[1] feels more responsive and it also supports longer sessions.

[1] - https://mosh.org/

Also they support Mosh which I install on my servers. It's way better than plain ssh when you're on mobile networks and wifi, especially with connections that are unreliable or bandwidth-constrained.

I’ve recently been experimenting with MoSH (Mobile Shell). Basically think SSH but with UDP - so more resilient to shoddy network conditions, roaming access points, etc.

If it is not for production (e.g. running as a daemon or a server) and you only care about the development, another ad-hoc way is using screen/tmus-like software incl. byobu, and combine it with mosh.