Mutt is exactly something that would be nice to rewrite in Rust, moreover, splitting into various crates of working with email, so that it will be possible to reuse the same code for both TUI and GUI clients.
[deleted]
Mutt on Windows Without WSL
11–20 of 78 posts
Re: Mutt on Windows Without WSL
#12Mutt is exactly something that would be nice to rewrite in Rust, moreover, splitting into various crates of working with email, so that it will be possible to reuse the same code for both TUI and GUI clients.
Already done: https://pimalaya.org/
And also: https://meli-email.org/
Re: Mutt on Windows Without WSL
#13re: using Unix tools on Windows, I do like that you can pipe the output of a program in WSL to the Windows clipboard (clip.exe). I was really surprised by this! I use pbcopy on the Mac for this all the time.
Beware that clip.exe clobbers unicode. For example, `echo caña | clip.exe` sets the clipboard to `ca├a`.
And there's no unclip.exe. You'd have to use `powershell.exe get-clipboard`, which is pretty slow.
I use this simple alternative: https://github.com/equalsraf/win32yank
`echo caña | win32clip.exe -i` and `win32yank.exe -o`
Re: Mutt on Windows Without WSL
#14re: using Unix tools on Windows, I do like that you can pipe the output of a program in WSL to the Windows clipboard (clip.exe). I was really surprised by this! I use pbcopy on the Mac for this all the time.
Beware that clip.exe clobbers unicode. For example, `echo caña | clip.exe` sets the clipboard to `ca├a`. And there's no unclip.exe. You'd have to use `powershell.exe get-clipboard`, which is pretty slow. I use this simple alternative: https://github.com/equalsraf/win32yank `echo caña | win32clip.exe -i` and `win32yank.exe -o`
I made a simple paste.exe utility for this actually. I suppose I should put it up on GitHub. Though win32yank pretty much does it all already.
Re: Mutt on Windows Without WSL
#15The general case here would be that to be POSIX compliant doesn't demand the underlying OS is unix, only that the API/ABI and commands work in very narrow limits.
If you write to libc and a small set of dependencies and if you are in C, it should be possible to do things. If you want curses, you are walking into hairy areas.
Re: Mutt on Windows Without WSL
#16re: using Unix tools on Windows, I do like that you can pipe the output of a program in WSL to the Windows clipboard (clip.exe). I was really surprised by this! I use pbcopy on the Mac for this all the time.
Oh wow, I didn't know about this, thanks for posting! For others, it really is just as easy as `ls | clip.exe` to pipe into your clipboard on WSL. `ls | tee clip.exe` if you want to print as well as copy. And of course you can just set an alias if you want to shorten clip.exe to clip. Great tip! Thank you!
It's implimented as a magic filename? Not a virtual or real file that actually appears in a filesystem? You don't have to do something like mount a virtual fs that maps to your host windows fs like a bind mount or nfs mount, and also add that fs to PATH?
If so, that sounds terrible, and very Microsoft.
Re: Mutt on Windows Without WSL
#17I wonder if this author has tried Justin Tuney's Cosmopolitan to run Linux tools on Windows. Her last releases are shipping full set of multiplatfom compiled GNU tools. They do work on windows. Even bash works. They do break sometimes but work when they do still. I used cosmopolitan's rsync on windows to copy stuff from sdcard but it was terminating randomly sometimes and I ended up using wsl.
This comment just made me realize Cosmo rsync might fix my weird issues with getting Vagrant to sync files over to my Unix VMs on my corporate Windows laptop. Thanks!
Re: Mutt on Windows Without WSL
#18Omg scoop looks awesome, how have I not heard of it before?
Have you heard about WinGet? It's the official package manager for Windows:
https://github.com/microsoft/winget-cli