[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Kconsole



On Fri, Mar 02, 2001 at 11:11:56PM -0700, Ivan E. Moore II wrote:

> > After the later update to KDE2.1 in Debian unstable it appears in the 
> > "Settings" for Kconsole that the "Keyboard" settings for 'xterm (xfree 3x)' 
> > and 'xterm (xfree 4x)' have not only swapped places but they both now do the 
> > same thing which is the xfree 4x style of keyboard.
> 
> that's very strange as I took the old default (x4) and created a new Keytab
> file for it and took the old X3 Keytab and copied it to default...weird that
> they would be the same..unless they were the same to begin with.

They are not the same, but something's broken anyway :->

Ivan: Apparently you did the following between the last two released
versions of konsole:

 * make default.Keytab xfree4.keytab
 * make x11r5.keytab default.Keytab

Now, this is a bit confusing, because it seems that default.Keytab is
a config file just like the *.keytab files, is loaded dynamically, and
can thus be changed by the system administrator.
But, this turns out not to be the case: default.Keytab contains

# This file is used to create the buildin keyboard table.
# It is included for reference purpose with the *.keytab
# files that are loaded dynamically.
#
# Modifying it does not have any effect (unless you
# derive the default.keytab.h and recompile konsole).

So, apparently it seems that you have moved the files around, but not
"derived the default.keytab.h" (whatever that means :-/ ) before
building the konsole deb.

I'm downloading the source right now and I'll see whether I can give you
further assistance on what to do to make konsole's keys work well.


Everybody: A quick workaround to make your current konsole binaries
work, is to (as root, and note the spelling of Keytab vs. keytab)

cd /usr/share/apps/konsole/
cp default.Keytab working.keytab

then (as ordinary user) start a new konsole, select the *second* entry 
"xterm (XFree 3.x.x)" in the keyboard configuration menu, and save your
settings. Et voilà: your home/end keys will work again ;)

You will probably have to rechange and resave your settings when there
will be fixed packages, though.

-- 
Andreas Trottmann <andreas.trottmann@werft22.com>



Reply to: