Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!uwm.edu!linac!att!ucbvax!hwcae.cfsat.honeywell.com!rand
From: rand@hwcae.cfsat.honeywell.com (Douglas K. Rand)
Newsgroups: comp.sys.apollo
Subject: Re: DM in OSF
Message-ID: <9105160039.AA26879@hwcae.cfsat.honeywell.com>
Date: 16 May 91 00:39:44 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 31

** kumorek@apollo.hp.com  (James Kumorek) on 15 May 91 18:41:55 GMT
** in [Re: DM in OSF] writes:

In article <1130004@hpcndjdz.CND.HP.COM>, jason@hpcndjdz.CND.HP.COM (Jason Zions) writes:

|> I admit to only passing knowledge of the use of the DM, so bear
|> with me for one tyro question. Could you explain what editing
|> features you'd like that you can't get with ksh in an xterm or
|> hpterm window with a good cut-buffer manager?

James> The primary difference between DM input pads and ksh command
James> line editing is the dm input pads lets you edit the input to
James> *any* program running in the pad, not just the input to ksh.
James> The editing is done in the dm, not in the program that is
James> running in the pad.

Most of what has been requested for editing features can be had by
using Epoch. (Epoch being a X windows implementation of Emacs.)
Command history for all programs (not just the shells), a built in
editor for pointing to files and clicking mouse button 3, and more.

The only things that Epoch/Emacs won't do that the DM does, is keep
you input synchronized with your prompt and editing multiple input
lines. I can live with out the first, and there are (difficult) ways
to do the second.

(Sorry, this wasn't supposed to be an advertizement.)
--
Douglas Keenan Rand                Honeywell -- Air Transport Systems Division
Phone: +1 602 436 2814               US Snail: P.O. Box 21111 Phoenix AZ 85036
NSFnet: rand@hwcae.cfsat.honeywell.com   UUCP: uunet!asuvax!apciphx!hwcae!rand