Path: utzoo!news-server.csri.toronto.edu!rutgers!uwm.edu!bionet!hayes.ims.alaska.edu!acad3.alaska.edu!ifjrs From: ifjrs@acad3.alaska.edu (STANNARD JOHN R) Newsgroups: comp.sys.next Subject: Re: using tip Message-ID: <1991Mar5.093436.26777@ims.alaska.edu> Date: 5 Mar 91 09:34:36 GMT References: <1991Mar3.035806.28203@leland.Stanford.EDU> <1163@tokio.cs.utexas.edu> Sender: usenet@ims.alaska.edu (J Random USENET) Reply-To: ifjrs@acad3.alaska.edu Distribution: usa Organization: University of Alaska Fairbanks Lines: 37 News-Software: VAX/VMS VNEWS 1.3-4 Nntp-Posting-Host: acad3.alaska.edu In article <1163@tokio.cs.utexas.edu>, garnett@cs.utexas.edu (John William Garnett) writes... >In article hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy)) writes: >>A question for all you tip-sters and the author of Terminal/Stuart: >>(I have had my NeXT only 3 days, so forgive my ignorance, and I come >>from SysV HP-UX): >>1. When using tip (or cu) ~p works fine, but ~t opens a file, but never >>wites (or closes it) on the NeXT. > >I'm using 2.0 on an 030 cube. Tip works okay for normal no-frills usage. >however, i see the same problem you do when trying to use ~t. This >command worked under 1.0 on the same cube. > >Perhaps this is a bug? Anyone else seeing this behavior? > The same thing happened to me the one time I tried it while dialed into the VAX. Since I'm also a neophyte, I haven't tried it a second time, yet. This is on an '030/1.0a Cube (I'm STILL waiting for the upgrade I ordered on Oct. 4th!) However, it's quite possible I did something else wrong... John > >-- >John Garnett > University of Texas at Austin >garnett@cs.utexas.edu Department of Computer Science > Austin, Texas -- John Stannard ifjrs@acad3.fai.alaska.edu BITNET: IFJRS@ALASKA KL7JL@KL7JL.AK.USA.NA kl7jl.ampr.org [44.22.0.1] "God is the Answer!" "Oh?? ... er, ... What was the Question?" --