From: Michal Soltys <soltys@ziu.info>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: Re: [kbd] unicode option for not working correctly since commit: bad17ea03
Date: Tue, 20 Sep 2016 20:13:00 +0200
Message-ID: <d1b13e17-a967-8e5e-e8d2-aa1984b35859@ziu.info> (raw)
In-Reply-To: <20160919235801.GA412@nyan>
On 2016-09-20 01:58, Felix Janda wrote:
> Michal Soltys wrote:
> [..]
>> On pre-2.0 versions all will be working fine (or to be precise,
>> pre-commit I bisected). After that commit some will be failing. If you
>> do setfont -m 8859-2 - this will provide the workaround.
>
> It might be useful to further bisect: I can see that compilation of
> dumpkeys will fail directly after commit
>
> http://git.kernel.org/cgit/linux/kernel/git/legion/kbd.git/commit/?id=3fdbff332a6ef88a2447584c47a8616dceb19548
>
> (e.g. because of missing lk_list_charsets). But is it in this situation
> maybe still possible to directly build loadkeys ("make loadkeys" in the
> src directory)?
>
The last commit that did compile (where it was working fine) was:
http://git.kernel.org/cgit/linux/kernel/git/legion/kbd.git/commit/?id=8d37c0e76fdb487845da74bdf0bbce13eebf7596
(so directly preceeding the one you mentioned)
And since:
http://git.kernel.org/cgit/linux/kernel/git/legion/kbd.git/commit/?id=bad17ea033bf571e03b05e1330e81e6238fd61f0
loadkeys -u have issues
My earlier mail where I reported it:
https://lists.altlinux.org/pipermail/kbd/2016-June/000591.html
next prev parent reply other threads:[~2016-09-20 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 1:06 Michal Soltys
2016-09-06 19:26 ` Alexey Gladkov
2016-09-19 20:10 ` Michal Soltys
2016-09-19 23:58 ` Felix Janda
2016-09-20 18:13 ` Michal Soltys [this message]
2016-09-20 19:33 ` Felix Janda
2016-09-21 9:53 ` Alexey Gladkov
2016-10-19 19:36 ` Alexey Gladkov
2016-10-19 21:36 ` Michal Soltys
2016-10-31 15:28 ` Michal Soltys
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=d1b13e17-a967-8e5e-e8d2-aa1984b35859@ziu.info \
--to=soltys@ziu.info \
--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