PS. Most shockingly of all, Windows's Notepad reads and writes Unix-style LF-terminated files.
It's slightly annoying that you have to twiddle a bunch of the preferences to make it a workable plaintext editor. Apple should just delete its rich text functionality, now that they bundle a real word processor (Pages) with the OS.
In TextEdit -> Preferences..., select the "Plain text" radio button. New documents are created as plain text now.
New Document:
Format:
Plain Text (select)
Options:
Check spelling as you type (disable)
Correct spelling automatically (disable)
Smart copy/paste (disable)
Smart quotes (disable)
Smart dashes (disable)
Text replacement (disable)
Open and Save:
When Opening a File:
Display HTML files as HTML code instead of formatted text (enable)
Display RTF files as RTF code instead of formatted text (enable)
When Saving a File:
Add ".txt" extension to plain text files (disable)
Plain Text File Encoding:
Opening files = Unicode (UTF-8)
Saving files = Unicode (UTF-8)[0] https://devblogs.microsoft.com/commandline/extended-eol-in-n...
Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0
https://mobaxterm.mobatek.net/
SSH, remote desktops, hugs & cupcakes for all my friends!
Another consideration is that the free version is licensed for commercial use, which is why I freely recommend it at work and with a clear conscience.
> Tabbed terminal with SSH > Based on PuTTY with antialiased fonts and macro support
MobaXterm and PuTTY cover very different use-cases, PuTTY being a subset with close to 100% feature parity.
The product is of sufficient value that it's worth supporting.
For Terminals, Windows has a number of outstanding terminal apps:
- Windows Terminal (a tabbed terminal made by Microsoft)
- Fluent
- Hyper 3
- Terminus
- ConEmu
And a billion other maintained tabbed terminals, some with an SSH UI if you want it. As an SSH implementation though, openssh is probably the best.
Linux has great terminals. Gnome Terminal and KTerm.
If by 'Linux terminal' you just mean terminal, Windows Terminal and Fluent aren't Electron based and are both quite fast.
Of course there are also fonts, copy/paste, colors, keys customization etc. But slowness is a deal breaker for me.
You probably want alacritty then, it's GPU accelerated and designed to be ultra fast. No tabs, it's expected you add a Windows based tabbing window manager.
Ack re: switching between tmux tabs though.
Have you tried Windows Terminal or Fluent? WT is C++ so should be good (and has a huge team of developers on GitHub who are paid to make it not suck - if you have a bunchmark to show it's slower than putty on a task, they'll probably want to fix it.
Repeat the above in another terminal and compare.
Windows Terminal is actually pretty bad under tmux but ok-ish without. Can't switch off to another tmux window while it's going either so basically locked in. That's unusable.
The argument could be made that tmux is an issue. But since 100% of my ssh is under remote tmux and it's fast in putty/kitty I can only blame other terminals. Even without tmux kitty is 2x faster than windows terminal. And kitty doesn't slow down under tmux.
Alacritty is great if you need actual performance.
Hyper is actually the one with the overall best experience, but it is electron and the usual issues apply.
Fwiw, mobaxterm can also be configured to use wsl.
There are quite a few terminal emulators on windows and I just listed a few I thought noteable.
I didn't even mention the new one from Microsoft!
If you just want a sleek looking terminal for a few commands, cmder is definitely a valid choice. The occasionally broken copy paste is however dangerous, as it can remove characters from the middle of a line
I.e. `rm -rf /tmp/something && echo success` can get shortened to `rm -rf / && echo success`. It's admittedly very unlikely, as it usually just introduces errors such as `rm -rf /tm & echo success`.
Also yes I noticed those issues in Cmder, I'm always looking for better choices that look nice to the eyes.
Also this might be helpful for anyone wanting to follow along: https://devblogs.microsoft.com/commandline/
It looks rather interesting, if still in prerelease. (also, there's a trailer for it on YouTube - so weird [2])
0: https://github.com/microsoft/terminal
1: https://www.microsoft.com/en-us/p/windows-terminal-preview/9...
The 0.5 version is usable as a day to day terminal.
Alternative most stable Terminal is Fluent which I've used for a couple of years now.
I have small reviews of about 8 of the Windows terminal apps at: https://github.com/mikemaccana/powershell-profile
Fwiw, I work on rails + react apps with this setup: - Hyper as my terminal - WSL2. Then just my zsh/vim/tmux setup - Docker's tech preview for WSL2
This has been pretty reliable so far. I'm sure I'll hit a snag at some point, but it has been a relatively smooth experience.
Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0
You can check if ssh is enabled with this command.
Get-WindowsCapability -Online | ? Name -like 'OpenSSH*'
Probably not too helpful if you’re dealing with poorly written windows serial software targeting embedded though.
Also python if you need to programmatically connect and operate a device over serial. Quite easy.
If WSL was not an option, I personally would still use PuTTY
I personally use 'screen'. It's a perfectly capable terminal for serial communications. It can even catch zmodem handshakes (it's in the manual).
That said, does WSL really provide serial devices? That’s pretty awesome. I wonder if USB also is a thing in the WSL2 world.
plink -serial COM1 -sercfg 9600,8,N,1,N
This will connect to serial port COM1 at 9600 baud, 8 databits, no parity bits, 1 stop bit and no flow control.https://devblogs.microsoft.com/commandline/introducing-windo...
I've found that between OpenSSH for Windows, Windows Terminal and WSL, I don't need PuTTY anymore. It's also nice to be able to use the same SSH keys on Windows and Linux instead of converting PuTTY keys to OpenSSH keys and vice versa.