Should Windows have a default CLI editor?

The author is confused about what CLI means. None of the programs listed are command-line editors. Ed and sed are examples of command-line editors. These are not. (Vim and Emacs <i>have</i> command lines within them, but so does VSCode, for that matter.)

I&#x27;d be happy to see Edit come back, but honestly I think MS wants people doing as little commandline as possible.<p>In fact, there newest tactic is to hide configuration changes they don&#x27;t want users to mess with in commandline only powershell options that are typically poorly documented, and have odd syntax.<p>maybe isn&#x27;t malicious, but it feels like it.

I would love a modern take. I don&#x27;t want to see vim or emacs recreated (they exist already).

Does anyone know why they removed &quot;edit&quot; from 64 bit versions of windows? I assume there&#x27;s a newoldthing about it.

that discussion is wild... just install a few of the most popular editors and be done with it. default to whatever the smallest, simplest one is—nano or similar? support setting $EDITOR or whatever the fuck the Windows equivalent should be and you&#x27;re done.

I guess using winget to install neovim, micro or helix isn&#x27;t that problematic.

It’d be much more impactful if critical OS configuration was done either via text files (ala *nix) or cli. Either would need to be feature complete and discoverable&#x2F;documented very well.

Edlin, of course.

Bring back EDLIN!