I'm not a full-blown sysadmin, but my job involves accessing several servers running Linux on VMWare with a special operational database. When I SSH into these servers, I end up in a captive menu terminal that lets me handle my admin tasks.
I've been trying to switch from using PuTTY to the built-in SSH in Windows Terminal, but I'm struggling to replicate the essential settings from PuTTY that help me work efficiently. Here are the key settings I rely on:
- Backspace key set to Control-? (127)
- Implicit carriage return with every line feed (I think I spotted this in the Windows Terminal config file)
- Function keys and keypad configured for Xterm R6
- Different behavior for Control-Alt compared to AltGr (maybe I can adjust this in the WT config?)
- Remote character set using font encoding
I'm really unsure about how to define the keybindings for my SSH sessions. I tried creating a custom profile with a generated GUID, but I got lost. Has anyone else done this or can someone suggest how to create custom keybindings for SSH in Windows Terminal?
1 Answer
Honestly, the Windows Terminal is a bit behind compared to the full features of PuTTY. It's neat and all, but it lacks some of the robustness that a dedicated terminal emulator like PuTTY offers. I get your frustration!
If you're working with a TUI app that requires all those keys and modifiers, I totally get wanting that functionality from Windows Terminal. It just doesn't compete in that area yet. If you're trying to run two apps side by side, that seamless setup with multiple panes could improve your workflow a lot.
I completely agree! The ability to run side by side in splits would definitely make it a lot easier to manage everything without constantly switching between windows.