This is just a "because I wanted to" project. And I get that; done a lot of those myself just to understand what the hell was going on. But the rewrite of turbo vision into FPC and compiling to half a dozen targets has been around for 20 years. Turbo vision is probably the best text mode windowing library in existence. The cool fun kicks in when you can map a whole text screen to an array like so: var Screen: Array[1…
For those curious, here is a modern port of the C++ Turbo Vision that also supports Unicode: https://github.com/magiblot/tvision
Microsoft Edit
101–110 of 337 posts
Re: Microsoft Edit
#102I used to recommend micro[1] to people like those in the target audience of this editor. I wonder if that should change or not. -- 1: https://micro-editor.github.io/
Re: Microsoft Edit
#103Earlier quoted context omitted.
As they explained, they needed a text editor that works in a command line (for Windows Core server installs), works across SSH (because for a while now Windows included an SSH Server so you can completely manage it through SSH), and can be used by non-vi-experienced Windows administrators (i.e. a modeless editor).
Telling people to use nano would of course have been next to impossible. Much easier to rewrite a DOS-era editor in Rust, naturally.
Rust + EDITOR.COM is kind of like remaking/remastering an old video game.
Re: Microsoft Edit
#104Now I'm waiting for EDLIN but with unicode. I remember you could use it in a batch file to script some kinds of editing by piping the keypresses in from stdin. Sort of a replacement for a subset of sed or awk. I haven't tried but this should be possible with vi too. Whether that is deeply cursed is another question.
Re: Microsoft Edit
#105Earlier quoted context omitted.
I think not. Edit is to edit files in the terminal. What kind of files do you expect people to edit in the terminal? Most certainly files that would benefit from colors, not prose.
A lot of authors, myself included, want a "distraction free" editor. Its a whole over-populated market segment. Prose thrives in the terminal. Ice and Fire was written in WordStar, as just one popular example.
I can't find the link but I think at some point she compiled her own nano with some "helpful" feature patched out again.
Re: Microsoft Edit
#106Microsoft loves to own general terminology like "edit" for their products. I have no idea how this flys. SqlServer like it's the one that found sql or it's the only product that serves sql.
Sure "chcp" is a mouthful, but "del" or "erase" makes as much sense as learning that "rm" is short for remove. You pick up either convention quickly enough, except that I'm constantly using "where" when I meant "which". Maybe I should make an alias or something.
Don't get me started on powershell's look-we-can-use-proper-words-lets-see-how-long-we-can-make-this.
Re: Microsoft Edit
#107Earlier quoted context omitted.
For those curious, here is a modern port of the C++ Turbo Vision that also supports Unicode: https://github.com/magiblot/tvision
lmao is any body still using turbo cpp?
Admitted, a few things have changed in last couple of years. MATLAB is being replaced by Python. Teaching 8085 & 8051 is being replaced by RasPi/Arduino. 8086 is taught alongside ARM & RISC, and not touted as SoTA.
I last saw Turbo being used in 2016-17 in a university setting, inside a DosBox (because Windows 7+ have dropped support for such old programs). Insane, but true.
Re: Microsoft Edit
#108Earlier quoted context omitted.
As they explained, they needed a text editor that works in a command line (for Windows Core server installs), works across SSH (because for a while now Windows included an SSH Server so you can completely manage it through SSH), and can be used by non-vi-experienced Windows administrators (i.e. a modeless editor).
Telling people to use nano would of course have been next to impossible. Much easier to rewrite a DOS-era editor in Rust, naturally.
Re: Microsoft Edit
#109Earlier quoted context omitted.
I think not. Edit is to edit files in the terminal. What kind of files do you expect people to edit in the terminal? Most certainly files that would benefit from colors, not prose.
I met someone recently that still uses WordStar. Yes I'm serious. He runs it in QEMU on FreeDOS. He's a writer for a living.