[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Nov 20 02:01:48 2003 
Subject:Re: Mandrake install error - cannot find -libtermcap 
From:dbd 
Volume-ID:1031120.01 

A.Sloman@cs.bham.ac.uk wrote in message news:<bpef5r$1p62$1@soapbox.cs.bham.ac.uk>...
> Paul Broadbent wrote;
> 
> [AS]
> > > I suggest that you remove the whole installation
> > >
> > > rm -rf /usr/local/poplog/v15.53d
> > > rm -rf /usr/local/poplog/local
> > >
> > > and run the install script again:
> > >
> > > ./INSTALL_EVERYTHING_WITH_MOTIF > install.log
> >
 [PB]
> > Thanks, it works now,
> 
> I am relieved to hear it.
> 
> > just 2 small probs:
> > 1) A error message keeps appearing in the console in the background when I
> > run 'poplog xved' from a console window,  the error message is:
> > ;;; WARNING - xtw: X TOOLKIT WARNING (xtRemoveGrab: grabError --
> > XtRemoveGrab asked to remove a widget not on the list)
> 
> I have no idea what that means. I wonder if it depends on what sort of
> window you use to launch it.
> 
> I use only 'xterm' windows, but there are various other types of windows
> in which you can type commands with their own peculiar behaviours.
> 
> E.g. if I run 'kterm' on my RedHat 8 desktop PC I get this printed out
> in the window where I launch it:
> 	Couldn't set locale:
> 		ja_JP.eucJP,ja_JP.ujis,ja_JP.EUC,japanese.euc,Japanese-EUC,ja,japan
> 	
> If I run gnome-terminal I find that the numeric keypad does not work as
> expected in Ved. (Perhaps it needs something special in Xdefaults,
> analogous to what is in $usepop/bin/Xdefaults.poplog (in recent bham
> distributions of poplog).
> 
> Try running 'xterm' if you are not already doing so...

Same error when running xterm, and I have discovered it happens when I
quit and xved window, doesn't matter really, everything seems to work
ok.
> 
> > 2) Also, when I run 'poplog xved' the 0 (or insert) and + keys on the
> > numberpad don't do what they are supposed to,
> 
> Do you mean 'supposed to' according to their labels, or according to the
> XVed key mappings specified in
> 	HELP xvedkeys
> or
> 	$usepop/pop/help/vedxtermkeys
> 
> > it just days unrecognised
> > key. I have num Lock on
> 
> Try turning it off? It has no effect in Xved when I run it.

When I turn it off none of the numpad keys work!
> 
> > and the . (or Del) key works, also they work when I
> > run 'poplog ved' from a proper console (not a window). Not a big problem
> > really though, I'll probably just use ved anyway.
> 
> You can find out what characters are being transmitted in XVed by
> particular fucntion keys if you do
> 	ENTER inkeys
> 
> and then press various function keys separated by spaces. It will
> insert the transmitted codes in the current ved buffer. Terminate
> either by pressing ESC three times or CTRL-C.
> 
> When you know the codes transmitted you can specify what you want the
> keys to do by using either vedsetkey or vedset (see HELP vedsetkey,
> HELP vedset) in your vedinit.p file in you $poplib directory (usually
> ~~/Poplib/vedinit.p).
> 
> For reasons unknown to me the same keypad keys seem to transmit
> different character sequences on different machines. E.g. sometimes
> the 0/Ins key transmits
> 
> 	ESC O p
> 
> and on some machines something completely different.
> 
> The xkeycaps program can be quite useful for finding out how
> your keyboard is viewed by X. If you don't have it you can find it
> using google and download. It should show that the 0/Insert key
> is recognized as both KP_0 and KP_Insert, and the dot/Del
> key is recognized as both KP_Decimal and KP_Delete.
> 
> You can use xmodmap to change those mappings or you can use vedkeys
> or vedsetkey to change the way Ved/Xved reacts to the keys.
> 
> Aaron

Thanks, I now have now setup the keys to work as described in help
xvedkeys.

Paul