[comp.windows.x] cm under tvtwm???

mitch@hq.af.mil (Mitch Wright) (05/19/91)

Greetings!

I've been wrestling with some of the utilities that come with OpenWindows 2.0
by trying to get them to work under tvtwm.  In particular, I've been trying
to get "cm", the calendar manager to display properly on my screen.

After setting up all of the KraZy variables so it will know where to find
fonts and whatnot, it still claims to be unable to find the font it wants.
I've tried changing the font, but it doesn't seem to help.

I also get the error:

	XView warning: invalid object (not a pointer), xv_get

System: Sun 386i, 4.0.2
WM: tvtwm
X11R4 patch through 18

Any help is greatly appreciated.  Please don't suggest that I still run the
openwin script and keep my WM the same... This crashes after a short time...

--
  ~mitch
_______________________________________________________________________________

   mitch@hq.af.mil (Mitch Wright) | The Pentagon, 1B1046 | (703) 695-0262
_______________________________________________________________________________

doug@genmri.UUCP (Doug Becker) (05/21/91)

    After setting up all of the KraZy variables so it will know where to find
    fonts and whatnot, it still claims to be unable to find the font it wants.
    I've tried changing the font, but it doesn't seem to help.
    
Your cm problem stems from using the MIT server rather than the X11/NeWS
server, not from using olwm rather than tvtwm.

To get cm to work if you're using the MIT server, you'll need to add the
following two lines to the fonts.alias file in whatever directory your
Lucida fonts are kept (on my system, it's /usr/lib/X11/fonts/75dpi).  Note
that the lines are split here only for legibility:

    -b&h-lucida-medium-r-normal-sans-9-90-75-75-p-0-iso8859-1 
        -b&h-lucida-medium-r-normal-sans-10-100-75-75-p-58-iso8859-1

    -b&h-lucida-bold-r-normal-sans-9-90-75-75-p-66-iso8859-1 
        -b&h-lucida-bold-r-normal-sans-10-100-75-75-p-66-iso8859-1

Then you'll need to do an 'xset fp rehash' to cause the server to reread
the font databases.  cm should run fine after that.

-- 

Doug Becker
doug@nmri.ge.com
crdgw1!sane!doug