Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!athena.mit.edu!watcher
From: watcher@athena.mit.edu (0)
Newsgroups: comp.sys.apollo
Subject: tabs (was Re: prmgr/prsvr SR10.1 woes)
Summary: idle curiosity -- why does aegis software choke on tabs?
Message-ID: <10438@bloom-beacon.MIT.EDU>
Date: 8 Apr 89 19:26:10 GMT
References: <5400035@iuvax> <5400036@iuvax>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: watcher@athena.mit.edu (0)
Organization: Massachusetts Institute of Technology
Lines: 14

In article <5400036@iuvax> jec@iuvax.cs.indiana.edu writes:
>By the way, I talked to Apollo earlier about this and found another error.  It
>appears that prsvr will totally freak out if you use tabs in the configuration
>file.  Just thought you all might be interested.

This seems to be a common problem with Aegis O/S applications,
notably the binder and the Display Manager.  Could someone in
Apollo R&D explain why tabs aren't considered legal whitespace?

I'd hazard a guess and say it's a deficiency of vfmt_$read,
but being a C person I have never used the vfmt calls.

_____________________________________
chris ross <0> watcher@athena.mit.edu