sxhkd — Simple X HotKey Daemon

zeltak · 2013-06-19 12:05:28

hya

im trying the new Chain cords feature using latest git from today but cant get it to work. im using the example from the github readme:

super + o ; {a,2,q}
{gvim,firefox,spacefm}

with no sucess, am i missing something. is the above command correspond to pressing super+o letting to and then pressing 'a' to launch gvim?

best

Z

bloom · 2013-06-19 12:21:14

zeltak wrote:

super + o ; {a,2,q}
    {gvim,firefox,spacefm}
Is the above command correspond to pressing super + o letting to and then pressing a to launch gvim?

It works for me.

In the context of your example, to launch gvim, you should press super + o, release both super and o, and finally, press and release a.

You might also want to make sure that super + o is not already grabbed.

Last edited by bloom (2013-06-19 15:21:36)

VCoolio · 2013-06-19 21:39:01

I already expressed my appreciation for sxhkd, but this chaining stuff makes it super awesome! Thanks again.

zeltak · 2013-06-20 00:16:31

Hya Bloom

thx for the answer but no matter what i do it dosent work for me. i updated to latest git, tried different key combos, nothing works. any idea what could casue this? the rest of the functions work just not the chaining

best

Z

bloom · 2013-06-20 09:09:24

zeltak wrote:

Tried different key combos, nothing works.

Create a configuration file with the following content:

a ; b ; c
    echo abc

Then create a debug binary with:

make clean debug

Then run (supposing the aforementioned configuration file exists at ~/foorc):

./sxhkd -c ~/foorc

And finally, paste the output of the above command produced after performing the a, b, c chain.

zeltak · 2013-06-20 12:15:31

bloom wrote:

Then create a debug binary with:
make clean debug

thx bloom, but im really not technical at all, i created a config and launched the make clean debug in the same folder as config and got an error:

make: *** No rule to make target `clean'. Stop.

i assume i need to run in while compiling (i installed it through AUR), is that correct or am i missing something?

best

Z

progandy · 2013-06-20 12:33:01

i assume i need to run in while compiling (i installed it through AUR), is that correct or am i missing something?

Right. While you are testing it, just pull the git, open a terminal there, compile and run it without installing (only duplicate the build() function manually, not package())

bloom · 2013-06-20 13:45:30

zeltak wrote:

thx bloom, but im really not technical at all, i created a config and launched the make clean debug in the same folder as config

Here's the step by step instructions:

git clone https://github.com/baskerville/sxhkd
cd sxhkd
make clean debug
printf "a;b;c\n\techo abc" > foorc
./sxhkd -c foorc

After pressing a, b and c, you shall press ctrl + c to kill the process.

Last edited by bloom (2013-06-20 13:49:26)

cippaciong · 2013-06-20 16:26:00

This new chain feature is really useful, thanks for implementing it.
Anyway I noticed that sxhkd is not reloading the config file after receiving a SIGUSR1 signal (it used to do it); I had to kill the process and relaunch it to be able to use the new chain keybindings. Is it the same for you?

bloom · 2013-06-20 17:23:14

cippaciong wrote:

Anyway I noticed that sxhkd is not reloading the config file after receiving a SIGUSR1 signal (it used to do it); I had to kill the process and relaunch it to be able to use the new chain keybindings.

Reload on SIGUSR1 still works fine: what happened is that you sent a SIGUSR1 signal to the current running instance of sxhkd, but that instance did not know how to handle chord chains because it had been instantiated from the previous version of sxhkd. Quod erat demonstrandum.

Last edited by bloom (2013-06-20 17:34:33)

zeltak · 2013-06-20 17:57:57

bloom wrote:

what happened is that you sent a SIGUSR1 signal to the current running instance of sxhkd, but that instance did not know how to handle chord chains because it had been instantiated from the previous version of sxhkd. Quod erat demonstrandum.

hehe ok thats why i wasnt getting the chain command to work....once i killed and restarted then it finally works

thx alot bloom, really loving sxhkd, such a great little app, was fed up with xbindkeys!

best

Z

cippaciong · 2013-06-20 20:02:28

bloom wrote:

cippaciong wrote:
Anyway I noticed that sxhkd is not reloading the config file after receiving a SIGUSR1 signal (it used to do it); I had to kill the process and relaunch it to be able to use the new chain keybindings.
Reload on SIGUSR1 still works fine: what happened is that you sent a SIGUSR1 signal to the current running instance of sxhkd, but that instance did not know how to handle chord chains because it had been instantiated from the previous version of sxhkd. Quod erat demonstrandum.

You are totally right, thanks again!

Supplantr · 2013-06-22 08:05:01

While using love I discovered that in the case of chords such as:

super + o ; {e,w,m}
    {gvim,firefox,thunderbird}

the e, w, and m keys are only detected by the love window upon being released. However, xev reports both KeyPress and KeyRelease events for these keys.

bloom · 2013-06-22 13:14:56

Supplantr wrote:

The e, w, and m keys are only detected by the love window upon being released. However, xev reports both KeyPress and KeyRelease events for these keys.

With the following:

:button1
    echo hello

love gets both button press and release events and yet the event replaying mechanism is the same for key and button events!

I also noticed I only get key press events on the daemon's side with your example chain : I can get release events if I grab in asynchronous mode, but then I can't replay the events...

So... it would seem to indicate that X was not conceived at Bell Labs

bloom · 2013-06-22 17:18:28

As of 710f69d, the following is handled:

super + alt + control + {h,j,k,l} ; {0-9}
    bspc fence_ratio {left,down,up,right} 0.{0-9}

The above notation generates 40 bindings: sequences on the same line are nested, and parallel otherwise.

zeltak · 2013-06-22 22:43:34

Hya again

cant thank you enough and tell you how much i enjoy using sxhkd!

i have a suggestion, would it be possible to add some kind of on screen visual clue for button pressed (especially when chaining keys). this could either be done via send to notify-osd or maybe dzen2? thx alot for your work!!

Z

Supplantr · 2013-06-23 00:05:14

bloom wrote:

So... it would seem to indicate that X was not conceived at Bell Labs

This went over my head. Are you saying it's a problem with love, a problem with X, or maybe a third case?
Just to clarify, I only mentioned this here because the issue occurs when the keys are merely bound, i.e. as per this example:

super + alt + control + {h,j,k,l} ; {0-9}
    bspc fence_ratio {left,down,up,right} 0.{0-9}

none of the number keys' press events will be picked up by love, even when pressed independent of the rest of the keybinding.

Also, using the above example, after the super + alt + control + {h,j,k,l} chord is pressed, if another keybinding is pressed (such as super + Return, which launches a terminal), sxhkd seems to "jam." A terminal isn't launched, pressing the number keys doesn't complete the above keybinding, and no other keybindings are executed until the above keybinding "times out."

bloom · 2013-06-23 09:53:49

Supplantr wrote:

Are you saying it's a problem with love, a problem with X, or maybe a third case?

Probably X.Org.

Supplantr wrote:

Also, using the above example, after the super + alt + control + {h,j,k,l} chord is pressed, if another keybinding is pressed (such as super + Return, which launches a terminal), sxhkd seems to "jam." A terminal isn't launched, pressing the number keys doesn't complete the above keybinding, and no other keybindings are executed until the above keybinding "times out."

The issue is partially fixed by 7c4c42e: when there's no active chord in chain mode we shall exit the chain mode.

If I read you correctly, you'd also like for the chord that (intentionally?) broke the chain to be retested for matches at level 0 ?

Supplantr wrote:

None of the number keys' press events will be picked up by love, even when pressed independent of the rest of the keybinding.

Yes, I was able to reproduce.

One possible workaround would be to grab only when needed.

But it requires to be very careful:

d
a → b → c
a → c
a → d
a → e

Initially only d and a are grabbed. If a is pressed b, c and e are grabbed. If b is pressed: only e and b are ungrabbed because d is required at level 0 and c must be grabbed to complete the longest chain.

Last edited by bloom (2013-06-23 09:59:36)

bloom · 2013-06-23 13:10:21

I've a introduced a notation for empty sequence elements: the underscore.

Example:

super + {_,shift + }{h,j,k,l}
    bspc {focus,shift} {left,down,up,right}

bloom · 2013-06-24 08:13:26

zeltak wrote:

I have a suggestion, would it be possible to add some kind of on screen visual clue for button pressed (especially when chaining keys).

Yes, it will.

Supplantr · 2013-06-24 09:46:53

bloom wrote:

Probably X.Org.

This is the second shortcoming of X we've discovered.

bloom wrote:

If I read you correctly, you'd also like for the chord that (intentionally?) broke the chain to be retested for matches at level 0 ?

I think this would make the most sense.

bloom · 2013-06-24 15:00:52

Supplantr wrote:

I think this would make the most sense.

It should be happening as of 6610d42.

Supplantr · 2013-06-25 07:11:50

bloom wrote:

It should be happening as of 6610d42.

It works as expected.

With the latest updates to vim-sxhkdrc the syntax highlighting breaks in this case.

bloom · 2013-06-25 08:19:36

Supplantr wrote:

With the latest updates to vim-sxhkdrc the syntax highlighting breaks in this case.

You shall insert a space between --keep-focus and }.

This quirk comes from the underlying sh syntax.

On a side note: you can split long lines into multiple lines by ending each partial line with a backslash.

Supplantr · 2013-06-25 20:33:48

bloom wrote:

You shall insert a space between --keep-focus and }.

That was easy! Thanks.

Arch Linux

#101 2013-06-19 12:05:28

Re: sxhkd — Simple X HotKey Daemon

#102 2013-06-19 12:21:14

Re: sxhkd — Simple X HotKey Daemon

#103 2013-06-19 21:39:01

Re: sxhkd — Simple X HotKey Daemon

#104 2013-06-20 00:16:31

Re: sxhkd — Simple X HotKey Daemon

#105 2013-06-20 09:09:24

Re: sxhkd — Simple X HotKey Daemon

#106 2013-06-20 12:15:31

Re: sxhkd — Simple X HotKey Daemon

#107 2013-06-20 12:33:01

Re: sxhkd — Simple X HotKey Daemon

#108 2013-06-20 13:45:30

Re: sxhkd — Simple X HotKey Daemon

#109 2013-06-20 16:26:00

Re: sxhkd — Simple X HotKey Daemon

#110 2013-06-20 17:23:14

Re: sxhkd — Simple X HotKey Daemon

#111 2013-06-20 17:57:57

Re: sxhkd — Simple X HotKey Daemon

#112 2013-06-20 20:02:28

Re: sxhkd — Simple X HotKey Daemon

#113 2013-06-22 08:05:01

Re: sxhkd — Simple X HotKey Daemon

#114 2013-06-22 13:14:56

Re: sxhkd — Simple X HotKey Daemon

#115 2013-06-22 17:18:28

Re: sxhkd — Simple X HotKey Daemon

#116 2013-06-22 22:43:34

Re: sxhkd — Simple X HotKey Daemon

#117 2013-06-23 00:05:14

Re: sxhkd — Simple X HotKey Daemon

#118 2013-06-23 09:53:49

Re: sxhkd — Simple X HotKey Daemon

#119 2013-06-23 13:10:21

Re: sxhkd — Simple X HotKey Daemon

#120 2013-06-24 08:13:26

Re: sxhkd — Simple X HotKey Daemon

#121 2013-06-24 09:46:53

Re: sxhkd — Simple X HotKey Daemon

#122 2013-06-24 15:00:52

Re: sxhkd — Simple X HotKey Daemon

#123 2013-06-25 07:11:50

Re: sxhkd — Simple X HotKey Daemon

#124 2013-06-25 08:19:36

Re: sxhkd — Simple X HotKey Daemon

#125 2013-06-25 20:33:48

Re: sxhkd — Simple X HotKey Daemon

Board footer