Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!dptg!ulysses!andante!alice!debra
From: debra@alice.UUCP (Paul De Bra)
Newsgroups: comp.unix.questions
Subject: Re: Strangeness in shell
Message-ID: <9747@alice.UUCP>
Date: 4 Aug 89 22:58:27 GMT
References: <432@mccc.UUCP> <9700009@osiris.cso.uiuc.edu> <2277@auspex.auspex.com> <10639@smoke.BRL.MIL> <5404@ficc.uu.net> <9729@alice.UUCP> <10665@smoke.BRL.MIL>
Reply-To: debra@alice.UUCP ()
Organization: AT&T, Bell Labs
Lines: 29

In article <10665@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes:
}In article <9729@alice.UUCP> debra@alice.UUCP () writes:
}>We could hardly believe our eyes when we discovered that this local command
}>line editing went away in the new and "improved" AT&T 630 MTG terminal. (sigh)
}
}Well you shouldn't believe your eyes!  The 630 firmware, unlike the 5620
}which was comparatively "plain", supports mouse-driven cut, paste, and
}send.  I use it continually.  It's not quite like Rob's "mux" interface,
}alas, but the capability's there.

I don't know the 5620 firmware, only Rob's "mux" interface.
On the 630 I cannot type a command, say "ls file", then click before the
"f", type "-l", click at the end of the line, press return and have
the shell execute "ls -l file". That's what I mean by local command line
editing, and that's not possible on the 630 because it operates in full
duplex.

}...
}The 630 has these features all the time, even when used with
}non-UNIX systems.  I can't think of any way in which the 630
}is inferior to the 5620..

I could, but comp.unix.questions is not the forum for this discussion.

Paul.
-- 
------------------------------------------------------
|debra@research.att.com   | uunet!research!debra     |
------------------------------------------------------