Microsoft Releases Classic MS-DOS Editor For Linux (arstechnica.com) 66
Microsoft has released a modern, open-source version of its classic MS-DOS Editor -- built with Rust and compatible with Windows, macOS, and Linux. It's now simple called "Edit." Ars Technica reports:
Aside from ease of use, Microsoft's main reason for creating the new version of Edit stems from a peculiar gap in modern Windows. "What motivated us to build Edit was the need for a default CLI text editor in 64-bit versions of Windows," writes [Christopher Nguyen, a product manager on Microsoft's Windows Terminal team] while referring to the command-line interface, or CLI. "32-bit versions of Windows ship with the MS-DOS editor, but 64-bit versions do not have a CLI editor installed inbox." [...]
Linux users can download Edit from the project's GitHub releases page or install it through an unofficial snap package. Oh, and if you're a fan of the vintage editor and crave a 16-bit text-mode for your retro machine that actually runs MS-DOS, you can download a copy on the Internet Archive. [...]
At 250KB, the new Edit maintains the lightweight philosophy of its predecessor while adding features the original couldn't dream of: Unicode support, regular expressions, and the ability to handle gigabyte-sized files. The original editor was limited to files smaller than 300KB depending on available conventional memory -- a constraint that seems quaint in an era of terabyte storage. But the web publication OMG! Ubuntu found that the modern Edit not only "works great on Ubuntu" but noted its speed when handling gigabyte-sized documents.
Linux users can download Edit from the project's GitHub releases page or install it through an unofficial snap package. Oh, and if you're a fan of the vintage editor and crave a 16-bit text-mode for your retro machine that actually runs MS-DOS, you can download a copy on the Internet Archive. [...]
At 250KB, the new Edit maintains the lightweight philosophy of its predecessor while adding features the original couldn't dream of: Unicode support, regular expressions, and the ability to handle gigabyte-sized files. The original editor was limited to files smaller than 300KB depending on available conventional memory -- a constraint that seems quaint in an era of terabyte storage. But the web publication OMG! Ubuntu found that the modern Edit not only "works great on Ubuntu" but noted its speed when handling gigabyte-sized documents.
Thanks for Edit, now how about MASM64 (Score:2)
Re: (Score:1)
There is one for Windows already.
There was an Edit for Windows too. :-)
And if you are going to re-write it in cross-platform code you might as well target Windows too. A single codebase for updates going forward.
How do you think 64-bit windows applications are made? It's called ml64.exe, comes with Visual Studio. As for cross-platform MASM compatible look at UASM.
I'd go NASM, but I'd prefer MASM to be cross platform. A single source code implementation for assembly based projects. Yeah, calling conventions differ, some of that can be dealt with via macros, minimizing the conditional assembly.
Re: um what? (Score:2)
We use NASM for all of our x86_64 platforms, and clang for arm64. We even cross-compile Windows on Arm using clang-cl on Linux. Some team members would like to use clang for everything and eliminate VS Studio, gcc and perhaps even Apple clang, but that would also mean updating a bunch of old assembly.
Whatâ(TM)s the appeal of MASM? Why would somebody want that to be cross-platform given the existing alternatives?
Re: Thanks for Edit, now how about MASM64 (Score:2)
Who even needs this? Just use edlin :-) (or tap two wires together to morse code out your file.)
Re: (Score:1)
Who even needs this?
Linux and Mac developers. It allows better sharing of source code across platforms. Makes your code more compatible with Intel and AMD documentation and their code samples.
Re: (Score:2)
It appears there's no qbasic and no gorilla.bas or nibbles.bas.
Useless.
Re: (Score:2)
Wouldn't you really rather have a WordStar?
Version 3 was probably the best before the cruft set in.
Why would a Linux user bother with it (Score:2, Insightful)
Re: Why would a Linux user bother with it (Score:1)
"ChatGPT, write a simple vim clone in Rust", too difficult? ;-)
Re:Why would a Linux user bother with it (Score:5, Interesting)
Well yeah, but this is intended for windows where a lot of old timers muscle memory is msedit.
On the subject of good linux ones, check out "micro" if you get a chance. Its in a similar conceptual space as nano , simple editor, not really designed for big coding jobs, but great for quickly editing a config file or whatever, but its got a few modern affordances.Wordpress style command sequences, and works great with a mouse in a way nano never quite managed to pull off well. Sure I'll still use Emacs (and I suppose most folks would use vi) for bigger stuff, but its become my daily driver for quick config file edits on servers and stuff.
Re: (Score:2)
Er, word perfect command sequences I mean. ^C ^V ^X etc. Still waiting for that morning coffee to kick in, and this ridiculous website still hasn't got an edit button.
Re: (Score:2)
Re: (Score:2)
Well yeah, but this is intended for windows where a lot of old timers muscle memory is msedit.
I find it hard to believe that anyone still has muscle memory from msedit.
Re: (Score:2)
If the claimed large file size support is actually good it could fill a niche.
Re: (Score:2)
edlin (Score:3, Insightful)
Re: edlin (Score:3)
Absolutely. I could pick right up with edlin like I never stopped. It was so handy for really quick edits.
Re: (Score:1)
You ain't lived until you've relied on ed, awk, and sed!
Re: edlin (Score:3)
That's too overkill. Just tap out your edits using a bit of wire. :-)
Re: (Score:2)
This reminds me of a guy I knew who wrote DOS software with debug. He'd got the opcodes memorized, and did all the math for offsets and whatnot in his head.
Unfortunately, he was an infamous USENET troll, and turned out to be a nonce.
Re: edlin (Score:1)
Why (Score:1)
Re: (Score:1)
I started vim once by accident on Mandrake Linux, and it was an obvious trap with no way out. I had to hit the reset button.
Re:Why - Oblig. (Score:4, Funny)
I started using vim over 3 decades ago. I am still using vim today, mostly because I can't figure out how to quit.
Re: (Score:2)
If that were true, your comment would have ended with :wq!
Re: Why - Oblig. (Score:2)
Ah, so THAT'S how you quit!
Re: (Score:2)
All of my comments end with :wq.
Re:Why (Score:4, Insightful)
which is included with all Linux?
The only Linux you've used are clearly mega distros. No there's countless of distros out there which don't have vim on them. On those universally GNU nano is the default installed text editor ... which incidentally is far more similar to Edit than Vi.
Re: universally GNU nano (Score:2, Insightful)
Are you sure you've used Linux?
Re: universally GNU nano (Score:2)
Re: universally GNU nano (Score:4, Interesting)
Are you sure you've used Linux?
I agree that there are tons of Linux distributions which don't include vi at all out of the box, and they do indeed default to using nano as the editor. I will follow this up by saying that this is an absolutely reasonable thing to do. Nobody who is not expecting to use a genuine glass terminal has a great reason to learn any vi variant today, unless they want to play nethack without using the number pad for movement and want to practice using vi keys. Nobody should ever find themselves in vi without knowing what they're doing, the poor fuckers. I disconnected to get out of it more than once before I got someone to explain to me how to use it by pointing me to a quick reference.
Yes, I do still use vim when I want to edit in the console, I used to use vi even on DOS. No, I don't use it the rest of the time, mousing in gvim is cumbersome and I no longer love fiddling with software settings so honestly I don't even care if it can be fixed, I'd rather keep things minimally reconfigured to do the job I want done.
Re: (Score:2)
Are you sure you've used Linux?
Yes. In fact I have seven devices running Linux in this room and three of them are running a distro without vim packaged by default. Hint: Ever wonder why raspberry pi projects tell you to use nano to edit /boot/config.txt using nano? - Note this isn't a question it's an example framed as a question to hopefully make you realise there's more to the Linux world than you running Ubuntu desktop or whatever off the shelf common distro you seem to think is the only one which exists.
Re: (Score:2)
Many don't preinstall vim, but most have some minimal version of vi. Minimal vi is still annoying if you're used to vim, but better than just having nano.
Re: (Score:2)
No, they did not. (Score:4)
Microsoft did release the source code of Edit (written in C) but this is NOT the classic editor because it is total rewrite (in Rust) with no shared history with the C implementation. This thing is a different animal and it will have different bugs.
Re: (Score:2)
why? (Score:2)
the only thing that made EDIT look good was EDLIN.
but my vote doesn't count... I was a TECO maven.
Re: (Score:2)
Now that TECO was mentioned, the last of the great old ones that remain unmentioned is QED on Berkeley timesharing system, the Ken Thompson's favorite editor, that was eventually ported to CTSS, Multics and GCOS/GECOS, and eventually morphed into ed for Unix.
Re: (Score:2)
Shame on me, I forgot the IBM family of editors, with the mighty XEDIT, and its modern incarnations like THE.
Also? (Score:2)
Is QBASIC also included or does the new EDIT not require it any longer?
Re: (Score:2)
Edit had a QBASIC dependency??
Re: (Score:3, Informative)
DOS edit is built into qbasic and it's not a stand-alone program.
You can get to it by typing "edit" at the dos command line, or by typing "qbasic /edit" at the dos command line. They both do the same thing.
Re: (Score:2)
Yep, sure does.
Re:Also? (Score:4, Informative)
Edit had a QBASIC dependency??
The DOS version did. The Windows 95 version didn't, because 95 didn't install with qbasic. (It would run fine if you copied it from DOS, though, and ofc especially if you dropped into DOS mode which was just actually DOS. Also wasn't it on the CD or something?
(research occurs)
yes, qbasic was on the Windows 95 A CD in other\oldmsdos.)
Re: Also? (Score:2)
So are we supposed to pay for QBasic now?
Re: (Score:2)
I'd say you should go find a Windows 95 ISO or some DOS floppy images in one of the usual locations, I don't think Microsoft is going to come after you for running their old software they don't sell any more on their new software. Ironically though, it will probably run better in someone else's software (like dosbox) than under any solution they've ever sold or given away that is supposed to let you run it on modern Windows. I've heard that DOS doesn't run well in Hyper-V. I can confirm that Windows 95 is h
Re: (Score:2)
Most versions of Win95 run perfectly fine on 86Box.
Re: (Score:2)
Most versions of Win95 run perfectly fine on 86Box.
Sure. Like I said, software which is not from Microsoft. Thanks.
Re: (Score:2)
QB64 is free, open source, and much more modern version of QB that you can use. Not written in rust though, unless I missed something.
"for Linux" (Score:2)
Articles like this always limit it to "for Linux" - but its just a general F/OSS piece of software which works on a number of platforms, including Windows itself, FreeBSD, and more.
MidnightCommander's mcedit called from 1994 (Score:2)
Still going strong with community support for the past 31 years.
So what is M$ bragging about now?
Why stop there? (Score:2)
What Linux really needs is a native port of the MS-DOS prompt, complete the ability to select an arbitrary rectangle of text, copy-and-paste via context-menu, 8.3 filenames, 255-character path-length limits, and full support for executing all your favorite .BAT files.
Re: (Score:2)
and a friendly reminder that 640Kb of RAM ought to be enough for everyone.
Re: Why stop there? (Score:1)
Thanks (Score:2)
We'll put it over there with all the others, because what Linux distributions need is another editor
This fills up a much-needed gap in the Linux world (Score:2)
Re: (Score:3)
Why? (Score:2)
Who's been asking for that? *I* want brief to run in Linux.