5 ms·
Here's hoping some Microsoft big-wig read this and remembers they don't have a default terminal editor at all since edit died. I don't mind powershell, but havi
by OptionX 6y ago
Here's hoping some Microsoft big-wig read this and remembers they don't have a default terminal editor at all since edit died.
I don't mind powershell, but having a self-proclaimed management platform with no out-of-the-box text editor is just silly.
And no, notepad doesn't count.
- mariusmg 6y agoThey should just bundle https://github.com/zyedidia/micro https://github.com/zyedidia/micro
- majkinetor 6y agomicro is nice. It doesn't work in powershell remoting session just like anything else CLI based.
- YeGoblynQueenne 6y agoWhen did this happen? I used vim over a powershell remoting throughout 2013-14 (to edit SQL scripts on a remote server without using rdp). Was this capability killed in recent powershell versions?
- majkinetor 6y agoIt never worked for me. I tried vim and everything, even less can't be used. For less to work you must use it on local station, i.e. icm -Computer remote -Script { ls | less} #blocks icm -Computer remote -Script { ls } | less #works
- YeGoblynQueenne 6y agoI don't know then. I might be wrong and might have been using vim in a local session but over a UNC path (and did other stuff with remoting, that didn't need an editor). It's been a while :)
- majkinetor 6y agoYeah, I asked on powershell repository. It wasn't supported ever and there is no plan to do so - its not an interactive terminal protocol.
- majkinetor 6y agoIndeed. Its emberresing really. Notepad doesn't count as it is GUI app and unusable in terminal, remote powershell session etc.
- qwerty456127 6y agoI actually would really love good old Edit to be reviewed - it had a really intuitive and cozy TUI - just modernize it a little bit (i.e. add UTF-8 and modern programming/mark-up languages syntax awareness) and it could be so sweet...