home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!!HELSINKI,
- X-Envelope-to: NOTABENE@TAUNIVM.BITNET
- X-VMS-To: IN%"NOTABENE@TAUNIVM.BITNET"
- X-VMS-Cc: JTAKALA
- MIME-version: 1.0
- Content-type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-transfer-encoding: 7BIT
- Message-ID: <01GT0U1DD1SYAC4EJ2@hylk.Helsinki.FI>
- Date: Fri, 1 Jan 93 23:59:07 IST
- Sender: Nota Bene List <NOTABENE@TAUNIVM.BITNET>
- From: "J-P Takala, University of Helsinki,
- Sociology" <JTAKALA@FINUHA.BITNET>
- Subject: File Status problem
- Newsgroups: bit.listserv.notabene
- Lines: 17
-
-
- There is an annoying new problem in NB4 (my copy at least): the file
- status value (va$fs) is erratic, or at least different from what it
- was earlier. There can be a file open in every window, but the FS
- value does not know it, at least by earlier standards (i.e., it is
- less than 511). The problem appears if one uses NB4's new possibility
- to start a NEw file with no name (or Create Untitled file). These
- files seem to have no effect on the FS value. Hence programs that
- check the availability of new windows using the FS--as many programs
- at the TAUNIVM archive do--are in trouble, and may mess up things.
- However, NB's own procedures, at least Review, are not fooled by the
- strange FS. So there must be another way to check the availability of
- windows. Does anyone reading this know what it might be? Unless this
- problem is fixed, it seems prudent to keep giving names to new files
- right at beginning.
-
- j-p takala
-