Mailspring VS zsh

I fully agree, moreover this:

> Rolling release distributions like OpenSUSE Tumbleweed follow upstream much more closely while still maintaining stability through thorough automated testing

Shows the author hasn't used Tumbleweed for any reasonable amount of time himself[0][1][2]. I daily drove it for a short while before moving to Fedora.

0: https://github.com/Foundry376/Mailspring/issues/533

1: https://forums.opensuse.org/t/tumbleweed-breaks-after-update...

2: https://www.reddit.com/r/openSUSE/comments/v09hnc/tumbleweed...

/u/protonmail is the a reason why there's been no effort on this front? It appears that it comes down to some sort of handshake issue but I can't imagine this is that hard to fix.

I was hopeful that https://www.nylas.com/ would be the de-facto "adapter" placing a common API surface on top of the major providers and dragging them into a modern-API world. They even had an email client of their own as a proof of concept (forked by one of the original authors as https://github.com/Foundry376/Mailspring - and its reusable core https://github.com/Foundry376/Mailspring-Sync may be interesting to many here). But they've pivoted towards making their API only available behind B2B contracts and opaque pricing, and primarily used for corporate email monitoring and CRM use cases - perhaps because security and privacy considerations are nontrivial. I'm still rooting for them but it's a shadow of what it could have been.

Mailspring

Mailspring- A great email client for windows (Opensource + Freemium)

I love Mailspring, it's modern and open source: https://getmailspring.com/

The UI uses Electron, but the actual sync engine is in C++, so it's pretty fast.

The only app I’m aware of which translates emails is this; https://getmailspring.com

Mailspring is quite nice. It also has a paid version and is actively updated so I think it's likely to stick around for awhile.

Mailspring, which is open source, is currently my recommendation for a desktop email client.

Mailspring. Open-source and fully local, but an optional account and optional subscription for premium cloud-based features. Thunderbird was too cluttered and Geary, although I really wanted to like it, was just too minimal.

> Now, listen. I wish I could continue here and end with “… and this is why ZSH does it that way!”

https://github.com/zsh-users/zsh/blob/47c7bc9b1493c7374f076b... has a comment about this behaviour, but no justification. I think it's just an optimization to save a little bit of time by not forking, and to avoid having the zsh process hanging around taking resources for no reason.

As a developer, the command line is one of the tools you will be using most frequently. It can be intimidating to venture into the world of CLI tooling but I can assure you it is one of the most rewarding experiences too. In this post I want to walk ya'll through my personal CLI setup. It is based on 3 technologies which I'll coin as the "Holy Trinity" of the command line: TMUX, ZSH, & Neovim.

Just like macOS, bash is included by default in most Linux distributions. Zsh on the other hand, needs to be installed manually. The installation process varies for different distributions but you can always check how to go about it for your distro on zsh website.

POSIX Shell [sh] such as bash[bash] or zsh [zsh] are used to run the commands.

this looks like the zshell implementation.

You can mass rename, using zsh zmv module. Tutorial

I use kitty, with a Nord theme, transparency, and Zsh with Oh My Zsh, using the clean theme.