Thomas Adam <tho...@fvwm.org> writes:

> On 28 February 2016 at 23:05, Hendrik Tews <hendrik.t...@fireeye.com> wrote:
>> The XKEYBOARD doc clearly say, no Xkb function should be called
>> if the server does not provide XKEYBOARD. And indeed, inside
>> vnc4server, XkbKeycodeToKeysym does always return 0. (I attach a
>> small test program that shows this behavior.) Inside the loop in
>> AddBinding (file libs/Binding.c) this causes all key bindings to
>> be dropped.
> So?  There is nothing FVWM can do about this.  Nor should it.  If you

Fvwm could and should use the XKEYBOARD extension properly, which
means, check at runtime if XKEYBOARD is supported in the server
and disable all XKEYBOARD calls if the result is negative. I
believe the XKEYBOARD documentation is very clear on this. The
Debian version of Fvwm has definitely a deficiency on this point.
And, as far as I understand, your github Fvwm version could also
be improved here.

> really don't want to use XKB at all with FVWM, then you can undefine
> 'HAVE_X11_XKBLIB_H' -- which will force FVWM to use
> XKeycodeToKeysym().

This is not a solution, because it would require me to keep two
compiled versions of Fvwm around. One for using on ordinary
displays and one for using inside vnc.

>> As conclusion, there are the following solutions to this problem:
>> - downgrade to Debian fvwm 2.5.30 (as suggested by Claude)
>>   because this uses XKeycodeToKeysym
> No.  See suggestion above.

This is definitely a solution. And for Debian users it is still
the simplest one.

>> - compile fvwm without the offending patch, for instance the
> No.  Just use CVS.  Oh, and see above.

What do you mean by no? This is of course a solution. And you are
contradicting yourself here, because using CVS means compiling
Fvwm without the offending patch.


This email and any attachments thereto may contain private, confidential, 
and/or privileged material for the sole use of the intended recipient. Any 
review, copying, or distribution of this email (or any attachments thereto) by 
others is strictly prohibited. If you are not the intended recipient, please 
contact the sender immediately and permanently delete the original and any 
copies of this email and any attachments thereto.

Reply via email to