all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
Subject: Re: VAX/VMS (was: Re: Debian/GFDL)
Date: Fri, 24 Nov 2006 20:13:30 +0100	[thread overview]
Message-ID: <f7ccd24b0611241113t835899cpbc7824bcfe0b5a4d@mail.gmail.com> (raw)
In-Reply-To: <rjejru8n3e.fsf_-_@sheridan.dina.kvl.dk>

On 11/23/06, Per Abrahamsen <abraham@dina.kvl.dk> wrote:

> VAX/VMS had a strongly typed file system

This is a feature. As it was its automatic versioning of files.

> It also had a really
> obscure syntax for file names, using []:. among other special
> characters.

Obscure only from another system's mindset. There was nothing obscure
in its filename syntax from my POV.

> 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".

As if that didn't ever happen on Unix, did it? :-)

> 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).

The usual TPU editor was called EVE (Extensible Vax Editor).

> 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.

Thought I'm no Pascal freak, about the only language I wouldn't prefer
over K&R C is BASIC...

                    /L/e/k/t/u

  reply	other threads:[~2006-11-24 19:13 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         ` VAX/VMS (was: Re: Debian/GFDL) Per Abrahamsen
2006-11-24 19:13           ` Juanma Barranquero [this message]
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

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

  git send-email \
    --in-reply-to=f7ccd24b0611241113t835899cpbc7824bcfe0b5a4d@mail.gmail.com \
    --to=lekktu@gmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.