sxhkd — Simple X HotKey Daemon

bloom · 2013-04-11 10:11:53

sxhkd now has a mailing list:
sxhkd at librelist dot com

I would appreciate if the priority was given to this communication channel as it would allow me (and everybody else) to reply without having to visit the Arch BBS.

The first sent email will be your subscription email: http://librelist.com/help.html.

Sirsurthur · 2013-04-25 19:54:35

Hello Bloom,

I am trying to use sxhkd with bspwm and had one question. Is there a way to make sxhkd aware of azerty keyboards ? Actually, as an example, my w and z keys are mixed when used in sxhkd.

Thanks a lot for your help,

bloom · 2013-04-25 21:00:23

Sirsurthur wrote:

Is there a way to make sxhkd aware of azerty keyboards?

What's the output of

setxkbmap -query

?

Sirsurthur · 2013-04-26 05:15:30

You can find the output of

setxkbmap -query

there :

rules : evdev
model : evdev
layout : fr
options : terminate : ctrl_alt_bksp

bloom · 2013-04-26 08:29:52

(In sxhkd's source directory:)

Make a debug executable

make clean debug

Create the following configuration file (call it testrc):

q
    echo foo

w
    echo bar

What's the output of:

./sxhkd -c testrc

Sirsurthur · 2013-04-27 06:24:31

Hello,

I post from an other computer and your testrc seems to work. I will send the output from my laptop on monday.

However, with my current keyboard, it seems that I have an issue with {1-9,0} keys. Both issues might be related :

setxkbmap -query
rules:      evdev
model:      logitech_g15
layout:     fr
options:    terminate:ctrl_alt_bksp

 ./sxhkd -c testrc
keysym for 'Alt_L' is 0xFFE9.
keysym for 'Alt_R' is 0xFFEA.
keysym for 'Super_L' is 0xFFEB.
keysym for 'Super_R' is 0xFFEC.
keysym for 'Hyper_L' is 0xFFED.
keysym for 'Hyper_R' is 0xFFEE.
keysym for 'Mode_switch' is 0xFF7E.
keysym for 'Num_Lock' is 0xFF7F.
keysym for 'Scroll_Lock' is 0xFF14.
lock fields 16 2 0
load configuration 'testrc'
hotkey 65307 0 64 2 echo foo
Couldn't extract sequence from 'super+{1-9,0}' or 'echo bar'.
grab
keycode for 65307 is 9
grab key 9 64
grab key 9 80
grab key 9 66
grab key 9 82

Thanks for your help,

Last edited by Sirsurthur (2013-04-27 07:01:43)

bloom · 2013-04-27 08:18:39

Sirsurthur wrote:

Couldn't extract sequence from 'super+{1-9,0}' or 'echo bar'.

Well, this:

super + {1-9,0}
    echo bar

is an invalid binding.

Here's an example of a valid sequence binding:

super + {1-9,0}
    echo {a-j}

Sirsurthur · 2013-04-27 08:34:44

Sorry for the mistake. You can find the output with the valid sequence binding there : http://pastebin.com/Mxj5T3zU

However, super + {1-9,0} still wont work, as on my keyboard those numbers are on top of letters like these ones {& é " ' ( - è _ ç à ) =}.

The layout of the keybord looks like this : http://i.imgur.com/MAl3lgh.png

Regards,

bloom · 2013-04-27 08:59:59

Sirsurthur wrote:

However, super + {1-9,0} still wont work, as on my keyboard those numbers are on top of letters like these ones {& é " ' ( - è _ ç à ) =}.

It does work but, on your keyboard, super + 1 is performed via super + shift + ampersand.

There's multiple solutions to this problem:

Make bindings based on the actual layout of your keyboard (i.e. use ampersand instead of 1, etc.).
Change the layout of the number row via xmodmap (the output of xmodmap -pke | grep '=.* [0-9] ' might be helpful).
Buy a QWERTY keyboard.

Supplantr · 2013-05-30 23:40:18

I don't mean to distract you from bspwm, but I have three feature requests.

Would it be possible to implement prefix style key combos, such as in ratpoison? Maybe the syntax could go something like:

super + o - {some,keys}

where pressing super + o would instruct sxhkd to wait for the next keypress and if it matches one of the given keys the corresponding command would be executed as usual.

And would it be viable to make the { , } notation in the commands optional? For instance, I currently have to use:

XF86MonBrightness{Down,Up}
    thor-brightness{ , }

Along these lines, if it wouldn't be too difficult, could multiline { , } be allowed? Some commands can be rather lengthy and while it's always possible to use a script, without one it would make it easier to differentiate between commands in situations such as:

super + alt + {q,r}
    {bspc quit 1,
     bspc list_monitors > "$BSPWM_LAYOUT"; bspc list_history > "$BSPWM_HISTORY"; bspc quit}

Thanks for all of your hard work on these wonderful projects!

progandy · 2013-05-31 01:30:33

Would it be possible to implement prefix style key combos, such as in ratpoison? Maybe the syntax could go something like:

That already exists with the xchainkeys daemon.

Supplantr · 2013-05-31 12:41:06

progandy wrote:

That already exists with the xchainkeys daemon.

Ah, I'll admit I wasn't aware of this. Still, (I realize I don't really have a say in the matter, but) if similar functionality could be easily implemented in sxhkd, it would be pretty handy. Running two different hotkey daemons doesn't exactly seem ideal. The addition of key chaining would (in my humble opinion) greatly increase the flexibility of sxhkd and in turn render it "the go to daemon for all of your X-related hotkey needs."

If only I knew enough C to contribute...

Last edited by Supplantr (2013-06-01 09:02:06)

zeltak · 2013-06-01 00:04:46

Wow

just discovered this today and loving it, will def replace my old and buggy xbindkeys..

one question if you dont mind, would you consider adding chained command to sxhkd? IE press supet+a, RELEASE and then press 1 to exe a command?

best

Z

bloom · 2013-06-01 08:08:55

Supplantr wrote:

Would it be possible to implement prefix style key combos, such as in ratpoison?

It's in my TODO list and has the highest priority.

Supplantr wrote:

And would it be viable to make the { , } notation in the commands optional?
Along these lines, if it wouldn't be too difficult, could multiline { , } be allowed?

Also in TODO.md.

cippaciong · 2013-06-02 17:41:42

I've been using sxhkd in combination with bspwm for some months without any problem until some days ago when, after logging in my system I found it unusable because keybindings were not working anymore. I managed to launch a terminal in X from tty and started sxhkd; trying different keybinding returned always the same error:

Spawning failed

Any idea about this?

bloom · 2013-06-02 20:30:22

cippaciong wrote:

I've been using sxhkd in combination with bspwm for some months without any problem until some days ago when, after logging in my system I found it unusable because keybindings were not working anymore. I managed to launch a terminal in X from tty and started sxhkd; trying different keybinding returned always the same error:
Spawning failed
Any idea about this?

(I personally encountered some small hitches lately in relation to the Arch migration to /usr/bin, but I can't tell if it might be the case for you or not.)

I don't detect anything wrong with sxhkd in the description of your issue: you should try to run the commands associated with your bindings manually.

bloom · 2013-06-03 18:56:49

cippaciong wrote:

Any idea about this?

I've just updated my system by following the given instructions and after the first command, sxhkd stopped responding, but I had a root shell opened on one of the virtual terminals so I did manage to finish the update and after the last command, sxhkd went back on its feet.

Which leads me to think that your problem is actually related to the /usr/bin/ migration.

Last edited by bloom (2013-06-04 10:16:19)

cippaciong · 2013-06-05 05:59:40

I'm afraid this is not my case because the first time I had this problem was at least one (or even a bit more) weeks ago, while the filesystem update is matter of these days. Also, unless I did it without being aware of (can still be a possibility ) I didn't update filesystem on the machine where I run bspwm yet.
Anyway this evening I'll check if the problem can actually be as you say. Thank you by now.

Edit: forgot to mention, commands associated works perfectly, I can even send bspc messages from the shell.
I even tried with a new config file with only one binding (the check if this could be a config error) but the result was the same.

Last edited by cippaciong (2013-06-05 06:04:02)

bloom · 2013-06-05 17:05:40

cippaciong wrote:

I'm afraid this is not my case

In fact, the only possible cause of the aforementioned error message is a bogus shell path (all commands are executed via ${SXHKD_SHELL:-${SHELL}}).

And it's precisely what the /usr/bin migration can produce: your shell is not in /bin anymore but /bin is not yet a symlink to /usr/bin...

Last edited by bloom (2013-06-05 18:43:47)

cippaciong · 2013-06-06 17:15:36

EDIT: I've upgraded filesystem without any problem but sxhkd problem persists.
I don't know if this can be handy but:

echo ${SXHKD_SHELL:-${SHELL}}
/.bin/dash

echo $SHELL
/bin/bash

EDIT 2
SXHKD_SHELL was not set. If set it to /bin/bash the problem disappear.

Last edited by cippaciong (2013-06-06 18:29:36)

cippaciong · 2013-06-06 18:56:37

Sorry, it was my fault from the beginning. I had this entry in ~/.profile

export SXHKD_SHELL=/.bin/dash

I don't even know when I set something so absurd.

bloom · 2013-06-18 12:53:00

Supplantr wrote:

I don't mean to distract you from bspwm, but I have three feature requests.

All the requested features are brought by 8e57c53.

aparthia · 2013-06-18 18:06:44

Nice addition! I have a question:

What do you call the 'alt gr' modifier in sxhkd?

Last edited by aparthia (2013-06-18 18:12:35)

bloom · 2013-06-18 18:52:48

aparthia wrote:

What do you call the 'alt gr' modifier in sxhkd?

Probably mode_switch.

aparthia · 2013-06-18 19:02:26

That worked, thanks!

Arch Linux

#76 2013-04-11 10:11:53

Re: sxhkd — Simple X HotKey Daemon

#77 2013-04-25 19:54:35

Re: sxhkd — Simple X HotKey Daemon

#78 2013-04-25 21:00:23

Re: sxhkd — Simple X HotKey Daemon

#79 2013-04-26 05:15:30

Re: sxhkd — Simple X HotKey Daemon

#80 2013-04-26 08:29:52

Re: sxhkd — Simple X HotKey Daemon

#81 2013-04-27 06:24:31

Re: sxhkd — Simple X HotKey Daemon

#82 2013-04-27 08:18:39

Re: sxhkd — Simple X HotKey Daemon

#83 2013-04-27 08:34:44

Re: sxhkd — Simple X HotKey Daemon

#84 2013-04-27 08:59:59

Re: sxhkd — Simple X HotKey Daemon

#85 2013-05-30 23:40:18

Re: sxhkd — Simple X HotKey Daemon

#86 2013-05-31 01:30:33

Re: sxhkd — Simple X HotKey Daemon

#87 2013-05-31 12:41:06

Re: sxhkd — Simple X HotKey Daemon

#88 2013-06-01 00:04:46

Re: sxhkd — Simple X HotKey Daemon

#89 2013-06-01 08:08:55

Re: sxhkd — Simple X HotKey Daemon

#90 2013-06-02 17:41:42

Re: sxhkd — Simple X HotKey Daemon

#91 2013-06-02 20:30:22

Re: sxhkd — Simple X HotKey Daemon

#92 2013-06-03 18:56:49

Re: sxhkd — Simple X HotKey Daemon

#93 2013-06-05 05:59:40

Re: sxhkd — Simple X HotKey Daemon

#94 2013-06-05 17:05:40

Re: sxhkd — Simple X HotKey Daemon

#95 2013-06-06 17:15:36

Re: sxhkd — Simple X HotKey Daemon

#96 2013-06-06 18:56:37

Re: sxhkd — Simple X HotKey Daemon

#97 2013-06-18 12:53:00

Re: sxhkd — Simple X HotKey Daemon

#98 2013-06-18 18:06:44

Re: sxhkd — Simple X HotKey Daemon

#99 2013-06-18 18:52:48

Re: sxhkd — Simple X HotKey Daemon

#100 2013-06-18 19:02:26

Re: sxhkd — Simple X HotKey Daemon

Board footer