Re: Orion doesn't respond to keyboard after startup

Hi David,

> Seems like the focus is in the wrong/no window (that was a big mess all
> the time). You could try to start an initial application from within
> the .xsession file just before you start Orion (e.g. "xterm &")... maybe
> that helps Orion to get into the right state again.

Thanks for the reply!  I tried starting an xterm from the .xsession
file, but it never seemed to receive the focus (at any rate, I
couldn't type into it and the cursor stayed hollow).  I think that
focus issue may be a result of my X setup more than an orion issue,
though (I have encountered the same "xterm won't focus" behaviour when
trying other window managers).

I did manage to figure out my problem (where none of orion's keys
seemed to work) a little while ago:  The culprit was Num Lock.  Orion
seems to treat M-c or F12 as a different key when Num Lock is on than
when it's off.  (Presumably because all keys arrive with an extra
modifier when num lock is on).

That seems like a bug to me, although I have to admit I can't see an
easy way to fix it given that Num Lock could in theory be on any
modifier.  And of course the work-around (just turn off Num Lock) is
pretty trivial.

> Sorry for the late reply.

Not at all!  I'm sorry I didn't forward the solution to the mailing
list earlier.

Thanks!
      James
-- 
James Wright
Ask me about my vow of silence!