Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!rpi!uupsi!sunic!dkuug!iesd!iesd.auc.dk!fischer From: fischer@iesd.auc.dk (Lars P. Fischer) Newsgroups: comp.windows.open-look Subject: Re: Endorsement for olvwm Message-ID: Date: 7 May 91 22:27:03 GMT References: <48@ftms.UUCP> Sender: news@iesd.auc.dk Organization: Mathematics and Computer Science, University of Aalborg Lines: 34 In-reply-to: brown@ftms.UUCP's message of 6 May 91 15:56:07 GMT >>>>> On 6 May 91 15:56:07 GMT, brown@ftms.UUCP (Vidiot) said: Vidiot> Last week I brought up olvwm to give it a go. Not only did we Vidiot> go with it, we are running with it. Vidiot> So far the program has been performing flawlessly. It even Vidiot> fixes a problem we have been having with FrameMaker 2.1X. Vidiot> If you are using FrameMaker, it is highly suggested that you Vidiot> bring up olvwm. You will be very happy that you did. We are Vidiot> around here. I very much agree. I compiled olvwm and did a s/olwm/olvwm/ on my .xinitrc, exited from OW and fired it up again. Everything worked as usual, except that I could move around between (virtual) screens. This is nice as it makes you work as usual and slowly get used to using virtual screens. I like olvwm a lot. Having extra screens handy is nice, ie. a news-reader screen, a mail-screen, etc. Being able to jump to a new screen when you get a new idea or for demoing something is neat. I'm still trying to figure out a good virtual screen setup, but the nice thing is that I can *develop* it at an idle pace while doing other things. I've had no problems with olvwm. It works, it does everything olwm does, and it provides useful new features. I like it. A lot. Oh, and it works with both X11R4 and Open Windows 2.0. /Lars -- Lars Fischer, fischer@iesd.auc.dk | It takes an uncommon mind to think of CS Dept., Univ. of Aalborg, DENMARK. | these things. -- Calvin