Linux console tools development discussion
 help / color / mirror / Atom feed
From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Alexey Gladkov <gladkov.alexey@gmail.com>
Cc: kbd@lists.altlinux.org
Subject: Re: [kbd] Test failures in kbd-2.0.0 on ppc
Date: Mon, 23 Sep 2013 01:31:57 +0100
Message-ID: <20130923003157.GA27169@milliways> (raw)
In-Reply-To: <20130920002712.GA18001@milliways>

On Fri, Sep 20, 2013 at 01:27:12AM +0100, Ken Moffat wrote:
> =========================================
> 2 of 8 tests failed
> Please report to gladkov.alexey@gmail.com
> =========================================

 The situation is a bit more serious than I thought.  Mac keyboards
were generally dire and weird, plus I use a KVM switch to share one
keyboard and monitor between my desktop machines, so I've got a
regular x86 British keyboard.  This has always worked ok (apart from
the 101st key being not recognized - that's a kernel problem), and I
normally use my own keymap [ uk-utf ] to add a lot of things and to
make the compose settings for accents closer to the Xorg dead keys.

 With kbd-2.0 (whether compiled with or without the separate lib),
loadkeys returns a status of 0 but doesn't change the keymap.  Same
with the shipped uk map.  I've now dropped back to 1.15.5 here and
my own keymap is working fine.

 For anyone else who wants to test this, and who has a ppc with a
regular US keyboard, "loadkeys uk" ought to load the British map
(double quotes on shifted 2, at-sign on shifted comma, pound
(sterling) on shifted 3 instead of has-sign.  And if working,
"loadkeys us" ought to restore it.

 I repeat that this is with everything else up-to-date, maybe it
still works with old toolchains, I don't know.

ĸen
-- 
das eine Mal als Tragödie, dieses Mal als Farce


  reply	other threads:[~2013-09-23  0:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20  0:27 Ken Moffat
2013-09-23  0:31 ` Ken Moffat [this message]
2013-09-23  6:43   ` Alexey Gladkov
2013-09-23  8:13   ` Alexey Gladkov
2013-10-10  7:17 ` Alexey Gladkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130923003157.GA27169@milliways \
    --to=zarniwhoop@ntlworld.com \
    --cc=gladkov.alexey@gmail.com \
    --cc=kbd@lists.altlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux console tools development discussion

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/kbd/0 kbd/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kbd kbd/ http://lore.altlinux.org/kbd \
		kbd@lists.altlinux.org kbd@lists.altlinux.ru kbd@lists.altlinux.com
	public-inbox-index kbd

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.kbd


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git