unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: VAX/VMS (was: Re: Debian/GFDL)
Date: Thu, 23 Nov 2006 11:38:13 +0100	[thread overview]
Message-ID: <rjejru8n3e.fsf_-_@sheridan.dina.kvl.dk> (raw)
In-Reply-To: mailman.528.1163456488.2155.help-gnu-emacs@gnu.org

Dieter Wilhelm <dieter@duenenhof-wilhelm.de> writes:

> You made curious, how could--I assume--an old, probably not further
> developed OS be better than our modern OSs?  I guess you've purity or
> cleanliness concerning the design in mind, haven't you?  Would it be
> advantages even nowadays to run VAX/VMS from a user point of view?
>
> Sorry for my total ignorance of VAX/VMS.

VAX/VMS had a strongly typed file system, which made it impossible to
do any kind of generic file operations, and forced you to learn a
separate set of commands for each type of file.  It also had a really
obscure syntax for file names, using []:. among other special
characters.  And a zillion different kind of hardwired interacting
privileges that meant that ordinary users rarely were able to do what
they want, but hackers could do anything as there were always some
obscure path from "may use the printer privilege" to "can overwrite
system files privilege".

The editors were EDT and later TPU.  They were much better than vi, I
have to give them that.  You can suffer them in Emacs with M-x
edt-emulation-on <ref> or M-x tpu-edt <ret>. (TPU was really a system
for writing editors in).

Some people liked VAX/VMS, typically the same who preferred Wirth
Pascal over K&R C.  For the rest of us, Ultrix was a much more
productive environment, once you had installed Emacs in it.

(There were also an Emacs port to VAX/VMS, but as EDT was never as bad
as vi, the need for it was less desperate).

  parent reply	other threads:[~2006-11-23 10:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 17:06 Debian/GFDL Nicolas Neuss
2006-11-10 22:01 ` Debian/GFDL Eli Zaretskii
2006-11-10 22:14 ` Debian/GFDL David Hansen
2006-11-13 10:49   ` Debian/GFDL Ismael Valladolid Torres
2006-11-13 12:33     ` Debian/GFDL Juanma Barranquero
2006-11-13 15:04       ` Debian/GFDL Ismael Valladolid Torres
2006-11-13 15:09         ` Debian/GFDL Juanma Barranquero
2006-11-13 16:11           ` Debian/GFDL Ismael Valladolid Torres
2006-11-13 17:56           ` Debian/GFDL Gian Uberto Lauri
     [not found]           ` <mailman.509.1163443911.2155.help-gnu-emacs@gnu.org>
2006-11-14  2:09             ` Debian/GFDL Will Parsons
2006-11-13 22:21       ` Debian/GFDL Dieter Wilhelm
2006-11-13 22:33         ` Debian/GFDL Juanma Barranquero
     [not found]       ` <mailman.528.1163456488.2155.help-gnu-emacs@gnu.org>
2006-11-23 10:38         ` Per Abrahamsen [this message]
2006-11-24 19:13           ` VAX/VMS (was: Re: Debian/GFDL) Juanma Barranquero
2006-11-24 21:06             ` VAX/VMS Dieter Wilhelm
     [not found] ` <mailman.417.1163196096.2155.help-gnu-emacs@gnu.org>
2006-11-11 13:50   ` Debian/GFDL David Kastrup
2006-11-11 15:30     ` Debian/GFDL David Hansen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=rjejru8n3e.fsf_-_@sheridan.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).