Authors of Pine decided to make it semi graphical application with it’s own window, menus and buttons. Nano predecessor UW Pico unfortunately never did have console terminal Windows port. Version that comes with Mingw/MSYS is not portable and so far I failed in attempts to build a static windows binary by hand. The official build looks like a fusion of cygwin, mingw, pdcurses and other horrible stuff. Unfortunately Windows port is lacking quite a lot, especially for things like resizing Window or handling file names. In it’s native habitat, it’s very popular and stable editor making it a perfect choice for a text mode console. When on topic of Unix, lets talk about GNU Nano. Emacs.exe binary is whopping 83 MB in size and the zip file contains two of them just in case. Both editors come with hundreds of supporting files and are massive in size. Also portability suffers a lot at least for Emacs. The problem is that both are completely foreign and just plain unusable to a typical Windows user and learning curve is pretty steep. These two had ports to Windows for as long as I can remember and in terms of quality and stability definitely up top. I use VIM every day and Emacs every now and then. If you search for a Windows Console Editor VIMand Emacswill naturally pop up first.These editors don’t need any introduction or praising. I also cry a lot about 64-bit Windows builds because I work a lot in WinPE and other environments where syswow64 is not available.įirst lets start with most obvious choices well known through intertubes. exe file that can be carried around on a USB pen drive or network share. Note that throughout the article I will be repeatedly referring to a “portable” editor, that for me means single. This article aims to be a grand tour of whatever is available out there. So, are there any 3rd party alternatives? Yes, and there are and quite a lot of them! Unfortunately none are perfect and most are old and unmaintained. Seems that Redmond forgot to include most crucial tool in sysadmin’s job – a simple text mode editor. This overall is good news and great improvement since previous generations of Windows, but what if you need to create or edit a PowerShell, CMD script or some config file? Nowadays everything seems to be text mode. Even System Center is a front end for PowerShell. Just take a look at Server Core, WinPE, Nano, PS Remoting, Windows SSH server, Recovery Console and Emergency Management Services.
No more wizards and forms, MMC and GUI based administration is suddenly thing of a past. I remember sitting through countless TechEd / Ignite sessions year after year and all I could see were blue PowerShell command prompts everywhere. Since 2012 or so Microsoft is pushing concept of running Windows Server headless without GUI and administering everything through PowerShell. (This is a guest post by Antoni Sawicki aka Tenox)
0 kommentar(er)
