For some odd reason, my 2nd tag can't be viewed with any other tag using the keyboard hotkey Mod + Control + #. Right clicking the tag works fine. Viewing other tags from the 2nd tag works fine however. I did not touch the default config for those hotkeys. I'm using awesome-git. What could cause this odd behavior?
On Mon, 18 Jun 2012, Hong Shick Pak wrote: > What could cause this odd behavior? What's the keycode of 2? It's expected to be 11 to properly bind. -- -- Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618
On Tue, 19 Jun 2012, Adrian C. wrote: > On Mon, 18 Jun 2012, Hong Shick Pak wrote: > > > What could cause this odd behavior? > > What's the keycode of 2? It's expected to be 11 to properly bind. ...this was once a problem with strange layouts. -- -- Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618
From xev:
KeyRelease event, serial 33, synthetic NO, window 0x1e00001,
root 0xca, subw 0x0, time 13371951, (420,279), root:(421,296),
state 0x0, keycode 11 (keysym 0x32, 2), same_screen YES,
XLookupString gives 1 bytes: (32) "2"
XFilterEvent returns: False
What do you mean strange layouts?
My layouts from rc.lua:
tags = {} for s = 1, screen.count() do
-- Each screen has its own tag table.
tags[s] = awful.tag({ "term", "web", "code", "off", "extr", "vbox"
}, s, layouts[1])
end
On Mon, Jun 18, 2012 at 9:11 PM, Adrian C. <anrxc <at> sysphere.org> wrote:
> On Tue, 19 Jun 2012, Adrian C. wrote:
>
>> On Mon, 18 Jun 2012, Hong Shick Pak wrote:
>>
>> > What could cause this odd behavior?
>>
>> What's the keycode of 2? It's expected to be 11 to properly bind.
>
> ...this was once a problem with strange layouts.
>
>
> --
> Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618
(Continue reading)
On Mon, 18 Jun 2012, Hong Shick Pak wrote:
> What do you mean strange layouts?
I ment strange keyboard layouts, not tiling layouts :)
The least you can do is add some debug print() statements to those
bindings to see if it's being executed at all maybe it thinks there is
no tag 2 on that screen. Start like this
awful.key({ modkey, "Control" }, "#" .. i + 9, function ()
local screen = mouse.screen
if tags[screen][i] then
print("Found tag " .. tags[screen][i])
awful.tag.viewtoggle(tags[screen][i])
else
print("Did not find tag " .. tags[screen][i])
end
end),
--
--
Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618
PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618
Just found out what was wrong. I remapped my Caps Lock to Ctrl with
xmodmap and this:
remove Lock = Caps_Lock
remove Control = Control_L
keysym Caps_Lock = Control_L
add Lock = Caps_Lock
add Control = Control_L
If I use the actual Ctrl key, everything works fine. I popped up xev
and I guess it's a problem with
XKeysymToKeycode returns keycode: 37
because the actual keycode for the Caps Lock is 66.
Why would this only bug that one special case with viewing tags?
On Fri, Jun 22, 2012 at 7:27 PM, Adrian C. <anrxc <at> sysphere.org> wrote:
> On Mon, 18 Jun 2012, Hong Shick Pak wrote:
>
>> What do you mean strange layouts?
>
> I ment strange keyboard layouts, not tiling layouts :)
>
> The least you can do is add some debug print() statements to those
> bindings to see if it's being executed at all maybe it thinks there is
> no tag 2 on that screen. Start like this
>
> awful.key({ modkey, "Control" }, "#" .. i + 9, function ()
(Continue reading)
On 23/06/12 01:28, Hong Shick Pak wrote: > Just found out what was wrong. I remapped my Caps Lock to Ctrl with > xmodmap and this: > > remove Lock = Caps_Lock > remove Control = Control_L > keysym Caps_Lock = Control_L > add Lock = Caps_Lock > add Control = Control_L > > If I use the actual Ctrl key, everything works fine. I popped up xev > and I guess it's a problem with > > XKeysymToKeycode returns keycode: 37 > > because the actual keycode for the Caps Lock is 66. > > Why would this only bug that one special case with viewing tags? > I had a similar issue, but I had Caps_Lock remapped to Mod4. As far as I remember the issue is that some key combinations can't be registered because kernel does not recognize them. This might be a hardware level problem. So the problem doesn't have to do anything with awesome. Cheers, I.(Continue reading)
RSS Feed