Hi,
in 2011 there was a thread mentioning the same problem
http://lists.freedesktop.org/pipermail/xorg/2011-February/thread.html#52308
, but there was no answer to the problem and the problem still exists. There's
even some Software, that fails to work, due to this problem:
#
Hey Knut,
sorry for the bad news, but as far as I understand it, you cannot use ctrl as a
modifier with xmodmap.
From xmodmap(1):
keycode NUMBER = KEYSYMNAME ...
The list of keysyms is assigned to the indicated keycode (which
may be specified in decimal, hex or octal and c
Sorry for the noise, but as I wrote in my first reply, xmodmap does not have
any desired effect.
With my tests, all I can change is normal and shifted behaviour. So only the
first two columns of a
keycode definition has an effect in the keysym output. I assume that is because
evdev processes the
Hey Knut,
it's not that strange, that you cannot configure your keyboard as you where
used to twenty years ago,
as the input layers developed to focus more input devices and more important,
more languages and
character systems.
Quite likely your X11 Server is configured to use the kernel evdev
, but
understandable in the end.
I would recommend to forget about xmodmap and use xkbcomp(1) and setxkbmap(1) to
temporarily modify the produced symbols. You can define more than FOUR_LEVEL
symbols. I found
definitions with up to EIGHT_LEVEL types. Can you define even more?
Another left-over ques
es keycode 92 for AltGr, though the
> layout
> uses " = 108;" so it should produce 108.
>
> I leave that last question for anyone who knows even more.
>
> After all I would say that the xkb configuration is too complex and bad
> documented, but
> understandable i
Hey Hendry,
the IDs are a property of the XINPUT extension and the xinput(1) tool can be
used to modify XINPUT properties. It's the tool of choice for XINPUT devices.
What you might think of is a modification of the kernel (evdev) devices, for
example USB, which are listed in /sys/bus/usb/devic
> On Mon, 8 Jun 2015, at 03:17 PM, Ingo Krabbe wrote:
>> the IDs are a property of the XINPUT extension and the xinput(1) tool can
>> be used to modify XINPUT properties. It's the tool of choice for XINPUT
>> devices. What you might think of is a modification of the kern
> On Mon, 8 Jun 2015, at 03:27 PM, Ingo Krabbe wrote:
>> No, I say, you can view/change USB Properties finding the a devices
>> through USB IDs and you can view/change XINPUT Properties addressing the
>> device via xinput and it's XINPUT.ID.
>
> Ok, I think I un
" are boot
options that go to the grub boot image, or whatever boot manager is on that CD
and on the layout of the ram filesystem when the system is started from CD.
Regards,
Ingo Krabbe
> hi,
>
> i'm writing to you to ask you how to specify to X i don't want
> hard
10 matches
Mail list logo
