Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!sugar!ficc!peter From: peter@ficc.uu.net (Peter da Silva) Newsgroups: comp.sources.d Subject: Re: Browse Message-ID: <7336@ficc.uu.net> Date: 18 Dec 89 16:37:45 GMT References: <13494@s.ms.uky.edu> Reply-To: peter@ficc.uu.net (Peter da Silva) Organization: Xenix Support, FICC Lines: 51 OK. Browse was written on a Version-7 UNIX system, ported to BSD, and ported to System III and then System V. The directory reading stuff is a set of minimal System III/System V/BSD compatibility routines. They were written some time around 1982, before I'd ever heard of Doug Gwyn's code. The BSD source startes at the second comment line. Everything before that is trying to figure out what system you're on. It can be trashed. I guess it's not quite as easy to figure that out as I thought... In article <13494@s.ms.uky.edu> sean@ms.uky.edu (Sean Casey) writes: > Tried a make, which bombed because OFILES didn't get defined. Doesn't BSD make understand $(var:pat=replacement)? > Did "browse /tmp". Got an error message, and it put a line up for /tmp. What was the error message? > Tried "?" for help. Got a bunch of nulls at the bottom of my screen. There's no help. '?' displays text from the current file. > Did a ^Z to stop. Browse left my terminal in a strange mode. I'll bet. > Messed with a bit. Commands not very intuitive. Sorry. They're mostly a subset of 'vi'. > "rm -rf browse" Sigh. > I wish people gave more thought to user interfaces. Sounds like the big problem is getting it working on your system at all. What's it run? Sounds like a BSD derivitive. I've also heard it doesn't run on a Sun-4. If I had one to try it on maybe I could get it working. Send me mail... -- `-_-' Peter da Silva. +1 713 274 5180. . 'U` Also or . "It was just dumb luck that Unix managed to break through the Stupidity Barrier and become popular in spite of its inherent elegance." -- gavin@krypton.sgi.com