Xref: utzoo gnu.emacs.help:2037 comp.emacs:10701 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!heimdall!ctron.com!hendrick From: hendrick@ctron.com (Jim Hendrick) Newsgroups: gnu.emacs.help,comp.emacs Subject: Re: Emacs (GNU Emacs?) for IBM 370 ? Message-ID: Date: 14 May 91 18:15:38 GMT References: <1991May13.054028.3183@dartvax.dartmouth.edu> Sender: hendrick@heimdall.ctron.com Followup-To: gnu.emacs.help Organization: Cabletron Systems Inc. Lines: 12 In-reply-to: harelb@cabot's message of 13 May 91 05:40:28 GMT Wow, now THAT would be a port . . . First, the entire set of unix related system calls can be trashed. Next all that can be redesigned to work in a single-process, non tree structured file system (bag dired, spawning sub-processes, you get the idea). To play the devils advocate for a moment, the default editor on a VM system (XEDIT) is not bad in that realm. I have worked extensively with it and it plays well with the system product interpreter language (REXX) as well as having a reasonable macro facility itself (I wrote an entire "window" user interface including pop-ups etc. using just REXX and XEDIT macros.) Not that it compares with emacs for friendliness (although some would disagree using the "M-x C-\ ESC-footpedal ..." argument). I just wanted to point out the other side of the coin. Tell your friend to learn to live with XEDIT ,or get a job in a unix shop like I did :-).