[awesome bugs] #1053 - "Proper" text input via xkb and libxkbcommon

[awesome]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened. Details are below.

User who did this - Uli Schlachter (psychon)

Attached to Project - awesome
Summary - "Proper" text input via xkb and libxkbcommon
Task Type - Bug Report
Category - Core
Status - New
Assigned To -
Operating System - All
Severity - Very Low
Priority - Low
Reported Version - git/master
Due in Version - 4.0
Due Date - Undecided
Details - Someone (I bet that means "Uli") should look closely at [0], understand all the implications and figure out what gets fixed by doing this.
Perhaps it solves all of our problems? :-)

[0]: http://lists.freedesktop.org/archives/xcb/2012-October/007930.html

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1053

You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

[awesome]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1053 - "Proper" text input via xkb and libxkbcommon
User who did this - Uli Schlachter (psychon)

----------
02:08:08 < horsik> is there some keycode list for xcb?
02:08:50 < horsik> tutorial doesn't say too much ( TODO: Talk about getting the ASCII code from the key code)
02:16:46 <horsik> i know the ascii code is in the event detail but i'd rather use something more verbose like constants
[...]
11:53:44 <jd__> horsik: take a look at awesome source code
11:56:05 <psychon> dont ;-)
11:56:53 <psychon> I'd rather suggest i3, AFAIR sECuRE_ made that one use libxkbcommon to do things properly (aka "with XKB")
12:02:41 <sECuRE_> i3lock specifically, yeah
12:03:36 <sECuRE> http://code.stapelberg.de/git/i3lock/tree/i3lock.c#n94 and http://code.stapelberg.de/git/i3lock/tree/i3lock.c#n310 are good starting points, i think

----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1053#comment3929

You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

[awesome]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1053 - "Proper" text input via xkb and libxkbcommon
User who did this - Uli Schlachter (psychon)

----------
FS#1279 ("Dead keys (and compose key) not working in prompt") is a duplicate
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1053#comment4100

You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

[awesome]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1053 - "Proper" text input via xkb and libxkbcommon
User who did this - Uli Schlachter (psychon)

----------
FS#1305 ("setxkbmap switching breaks input in rum prompt") is another duplicate.
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1053#comment4163

You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.