4 ms·

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

tonyedgecombe 3y ago
A command line version of VSCode would be interesting.
thesuperbigfrog 3y ago
>> I don't want to see vim or emacs recreated (they exist already). Why would they need to be recreated? Windows ports of vim and emacs exist and they would be excellent choices along with a simple editor like nano. I agree with those in the thread that they should just include vim, emacs, and nano. They are mature, have excellent features and would target all the major groups of users who use text editors. Creating an entirely new text editor seems silly when there are so many good choices with full ecosystems and user communities.
- Pet_Ant 3y ago
  > Why would they need to be recreated? Windows ports of vim and emacs exist I think you are missing the point here. It's not about litterally rewriting them, but about copying their design. It'd be nice to see a new advanced text editor written using what we've learned over the last 40 years and about usability, discoverability, etc.
  - thesuperbigfrog 3y ago
    >> I think you are missing the point here. No, the point is to select one or more existing text editors to add to Windows: "The goal would be to install the selected editor(s) by default such that their commands work out-of-the-box. Example editors include but are not limited to: • Edit • Pico • Nano • Vim • Emacs • etc. Installing one or more of these editors by default will offer immediate CLI text editor capabilities on all Windows machines, preventing the need for additional installs or workarounds when operating on local machines, remote connections, or Windows containers." Microsoft is not trying to create a new text editor. If anyone wants to write their own new advanced text editor or whatever, they can, but that is not what the GitHub issue is about.
jayflux 3y ago
I agree, I would love to see something modern that works for devs today and isn’t just a port of something that was put together in the past. Helix feels like a cli VSCode to me, in the sense it has TreeSitter and LSP built-in and support for most languages out the box. It’s doesn’t require loads of plugins to be useful.

A command line version of VSCode would be interesting.

>> I don't want to see vim or emacs recreated (they exist already). Why would they need to be recreated? Windows ports of vim and emacs exist and they would be excellent choices along with a simple editor like nano. I agree with those in the thread that they should just include vim, emacs, and nano. They are mature, have excellent features and would target all the major groups of users who use text editors. Creating an entirely new text editor seems silly when there are so many good choices with full ecosystems and user communities.

Pet_Ant 3y ago
> Why would they need to be recreated? Windows ports of vim and emacs exist I think you are missing the point here. It's not about litterally rewriting them, but about copying their design. It'd be nice to see a new advanced text editor written using what we've learned over the last 40 years and about usability, discoverability, etc.
- thesuperbigfrog 3y ago
  >> I think you are missing the point here. No, the point is to select one or more existing text editors to add to Windows: "The goal would be to install the selected editor(s) by default such that their commands work out-of-the-box. Example editors include but are not limited to: • Edit • Pico • Nano • Vim • Emacs • etc. Installing one or more of these editors by default will offer immediate CLI text editor capabilities on all Windows machines, preventing the need for additional installs or workarounds when operating on local machines, remote connections, or Windows containers." Microsoft is not trying to create a new text editor. If anyone wants to write their own new advanced text editor or whatever, they can, but that is not what the GitHub issue is about.

jayflux 3y ago

I agree, I would love to see something modern that works for devs today and isn’t just a port of something that was put together in the past. Helix feels like a cli VSCode to me, in the sense it has TreeSitter and LSP built-in and support for most languages out the box. It’s doesn’t require loads of plugins to be useful.