[prev in list] [next in list] [prev in thread] [next in thread]
List: freenx-knx
Subject: Re: [FreeNX-kNX] problems with Mac OS X client
From: perkel <perkel () u ! washington ! edu>
Date: 2005-08-12 19:52:12
Message-ID: 42FCFDEC.5060902 () u ! washington ! edu
[Download RAW message or body]
Thanks for this suggestion. Unfortunately, I'm still missing something.
I can start the X server, open xterm and do the xmodmap step and can
confirm that this has had the desired effect by checking with xmodmap -pk.
But then when I use nxclient (or even ssh -X to another machine) and
then open konsole, I still don't get '*' or '+' from the normal keyboard
locations (shift-8 or shift-=). I do also confirm that these characters
from the numeric keypad work fine. So at this point I don't even know
what to try next.
Also, although I'm clearly not ready for this yet, I was unable to find
source for session_gate. Any pointers?
Thanks for your ideas,
David
lists.freenx@web19.eml.cc wrote:
> On Thursday 11 August 2005 23:57, David Perkel wrote:
>
>>OK, the problem with ignoring '*' and '+' seems to occur only with
>>certain applications, notably konsole.
>>
>>This suggests nxclient is off the hook. My apologies.
>>David
>
>
> I also had this problem using konsole over NX. It's been a while, but
> here is my recollection of the solution: the * on shift-8 generates
> some other weird keystroke that for me switched konsole tabs, but the
> * on the numeric keypad (for my PowerBook I think it's fn-0) works
> fine. So I remap the shift-8 version to send the same X Windows
> keysym as the keypad * by putting the following lines:
>
> keycode 75 = asterisk
> keycode 77 = plus
>
> in a file (I use ~/.Xmodmap) and then running
>
> xmodmap ~/.Xmodmap
>
> to apply the settings. (I had the same problem with +.) You need
> these settings to affect the *local* X Server running on your mac. I
> don't remember whether it works to do this inside the NX session (I
> think it does), or if you have to start X11.app manually on your mac,
> open up a terminal window, run xmodmap, and then start nxclient. You
> can automate this using a .xinitrc file, but make sure you understand
> how to use .xinitrc - specifically, that your X session will end when
> the .xinitrc script returns, so you need to have something in there
> that doesn't quit until you're done with X. For that purpose I
> compile session_gate from MIT Athena and use a .xinitrc that looks
> like this:
>
> xmodmap ${HOME}/.Xmodmap
> rxvt &
> konsole &
> quartz-wm &
> exec /usr/local/bin/session_gate
>
> ... although it also works to exec xterm or some such if you don't
> mind the requirement that you always keep that xterm open.
>
> Hope this helps,
> -Jesse
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX@kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
--
David J. Perkel, Ph.D., Associate Professor |
Departments of Biology and Otolaryngology |
University of Washington |
1959 NE Pacific St. HSB BB 1165 | Tel. 206-221-2477
Box 356515 | FAX: 206-543-5152
Seattle, WA 98195-6515 | perkel@u.washington.edu
_______________________________________________
FreeNX-kNX mailing list
FreeNX-kNX@kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic