On 1 Jun 2005, at 10:08, Liam Bedford wrote:
> On Tue, May 31, 2005 at 10:30:06AM +0100, Niall O Broin wrote:
>> fine, so I don't need to use the workaround mentioned. However, it was
>> my understanding that as an X client, albeit a fairly large one, KDE
>> had to take what it was given from the X server. Clearly my
>> understanding of the interaction between the X server and KDE was
> ever met the setxkbmap app?
> or even the deprecated keymap changing stuff?
>> the client can change keyboard settings on the server with
> impunity. At a guess, KDE and GNOME provide the service so the
> user doesn't need to edit config files etc.
Yes, of course I've manipulated the keymap etc. in various ways,
deprecated and now. And now that you mention it, that's of course the
way to look at it.
I was wondering why KDE was ignoring what the X server hands it but of
course, it's not doing that. What it IS doing is when it starts, it
sets the X server up the way it knows the user wants. Now, I hadn't
told KDE what I wanted but that didn't matter - KDE made certain
default assumptions for me, and told the X server to use those.
Thanks for that Liam - just needed to hold my head in a different way
to see the light.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!