I disagree.
> Please, not every shitty Lisp interpreter which can print to the screen and take user input is an operating system. Not every Lisp program which can send mail is an operating system.
I agree with that point.
Calling Emacs an OS is dubious, it certainly isn't a general purpose OS, and won't run on real hardware. But, let me make the case that Emacs is an OS.
Emacs has two parts, the C part, and the Emacs Lisp part.
The C part isn't just a Lisp interpreter, it is a Lisp Machine emulator. It doesn't particularly resemble any of the real Lisp machines. The TCP, Keyboard/Mouse, display support, and filesystem are done at the hardware level (the operations to work with these things are among the primitive operations provided by the hardware). Of these, the display being handled by the hardware isn't particularly uncommon, historically; the filesystem is a little stranger.
The Lisp part of Emacs is the operating system that runs on that emulated hardware. It's not a particularly powerful OS, it not a multi-tasking system. It has many packages available for it (though not until recently was there a official package manager). It has reasonably powerful IPC mechanisms. It has shells, mail clients (MUAs and MSAs), web browsers, web servers and more, all written entirely in Emacs Lisp.
My might say "but a lot of that is being done by the host operating system!" Sure, some of it is, but all of it is sufficiently low level. If you wanted to share the filesystem with another OS running in a VM, you might do it by sharing it as a network filesystem; this is necessary when the VM OS is not designed around running in a VM. However, because Emacs OS will always be running in the Emacs VM, we can optimize it by having the Emacs VM include processor features mapping the native OS, and have the Emacs OS be aware of them. It would be slower and more code to do that all over the network.
AutoLisp is far less powerful than elisp - e.g. AutoLisp has no macros. It also ceased being enhanced many years ago, while elisp rolls ever onward to the point where it now includes lexical scoping.
A remark because writing my nitpick got me going:
The degree to which Emacs is an OS depends on a person's definition of OS - if it is the primary means of interacting with the computer from the user's chair then Emacs looks more like an OS. On the other hand, if we start from a more formal stance, then it looks less like one.
Pretty pictures aside, how much more or less of an OS is Emacs than Chrome, and if different, in what fundamental ways?
How different is Chrome running on a VM on a Linux box from Emacs running on the same box?
I think your definition attempt renders the term Operating System useless.
We have pretty good definitions of 'operating system' already, no need to invent new useless ones.
When an Emacs user greps from Emacs why is this less blessed than my grepping from Bash? Is it considered blasphemy against vi?
Yes, I see that Bash is not the OS and vi is not the OS and neither of course is grep, for the OS is the turtle upon which these things rest and it is turtles all the way down until you get to microcode. Just because someone calls themselves "a computer scientist" it does not make their abstractions are any less metaphysical.
It is when we use an human centered definition of "operating system" rather than a machine centered one that Emacs can be seen in a different light. It is not that either group is failing to develop a scientific model. It is that each model has orthogonal metrics.
If the computer is never used for any other application, then that's an arguable position.
But "Operating System" is being used ambiguously. Can Emacs be an OS kernel? Um, no. Can Emacs be a shell/UI replacement? Yes, I think so. The discussion appears to be partly about that.
It's not - it actually was done[1]. There were OSes written in other high-level languages, like Smalltalk and Forth (which may not be "high-level", but at least it's higher level than C).
Definitely with you on the second point.
Emacs is an editor extensible in Lisp. Nothing more. Just like Autocad is a cad program extensible in Lisp. Autocad is also no Lisp OS. Just like Quicksilver is a publishing program extensible in Lisp. It's still no OS. Just like Audacity is a sound editor extensible in Lisp. Still no OS.
An OS is Movitz. Written in Lisp. Runs on Intel and talks to the hardware. Talks to the graphics card. Keyboard. Network card.
Please, not every shitty Lisp interpreter which can print to the screen and take user input is an operating system. Not every Lisp program which can send mail is an operating system.
How do you know that some Lisp is actually an operating system? A good rule of thumb is this: Is the network stack talking to the ethernet interface written in Lisp? Is the file system and the block level interface to the disk written in Lisp? Is the routine which formats the disk written in Lisp? Is the routine which puts a file system onto a blank disk written in Lisp? If that's the case, then you have a winner. Then it looks like it is a Lisp OS.