Path: utzoo!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!ames!amelia!eos!shelby!neon!cm-next-9!grd
From: grd@cm-next-9.Stanford.EDU (glen diener)
Newsgroups: comp.sys.next
Subject: Re: Invisible text in WriteNow, ... bombing.
Keywords: WriteNow, horror
Message-ID: <1990Jun1.035305.4470@Neon.Stanford.EDU>
Date: 1 Jun 90 03:53:05 GMT
Article-I.D.: Neon.1990Jun1.035305.4470
References: <1990May30.213509.23353@agate.berkeley.edu> <2665cd47.3a7a@petunia.CalPoly.EDU>
Sender: news@Neon.Stanford.EDU (USENET News System)
Organization: CCRMA, Stanford University
Lines: 28

In article <2665cd47.3a7a@petunia.CalPoly.EDU> dstaas@polyslo.CalPoly.EDU ((That's two a's)) writes:
>
>
>adams@jif.berkeley.edu (Jeffrey P. Adams) politely asks:
>>
>>... changed the line height field in the ruler, just
>>like normal.  To my horror, My entire document "disappeared."
>>
>>Has anything like this happened to anyone else?
>
>As a matter of fact, just yesterday I was finishing up a 40+ page document
>when this happened -- everything went blank, then 30 seconds later, WriteNow
>died.  Unfortunately, I forgot to look for console messages.  I, like you,
>was changing the line height when this happened.
>
I've had WriteNow just up and vanish on me in the middle of typing. 
This has happened several times, including once as I was about half-way
through doing a three-hour exam :-(. Thank god for an understanding
prof.  I've noticed that often the side of my left hand accidently depresses
the left Alternate key, converting subsequent keystrokes into alt sequences.
I've hypothesized that there is some undocumented alt-key sequence which causes 
WriteNow to quit without further ado.  Whatever the reason, WriteNow is number
1 on my ``Top 10 Things I Like Least on the NeXT machine''. I believe it is
the main reason people perceive the machine as slow.  What a pity so
much of the documentation is in WriteNow.

-glen diener
grd@cm-next-9.stanford.edu