dxhd is heavily inspired by sxhkd, written in Go, and has quite elegant syntax for configuration files!
NOTE: the git version, a.k.a. the master version is usually more bug free than the released, binary ones, since introduced bugs first get fixed in this version.
- Arch User Repository
git clone https://aur.archlinux.org/dxhd-git.git
# or binary version - git clone https://aur.archlinux.org/dxhd-bin.git
cd dxhd-git
# or cd dxhd-bin if you cloned binary one
makepkg -sior use an AUR helper like yay - yay -S dxhd
- From the source
git clone https://github.com/dakyskye/dxhd.git
cd dxhd
go build -o dxhd .and copy dxhd executable file to somewhere in your $PATH
- From releases
Download the dxhd executable file from the latest release, from releases page
and copy dxhd executable file to somewhere in your $PATH
- key press events (
super + key, wherekeyis a non-modifier key) - key release events (
super + @keywherekeyis a non-modifier key, and@is specifier) - mouse button press events (
mouseNwherenis button number) - mouse button release events (
@mouseNwherenis button number, and@is specifier) - variants (
{a,b,c}) - ranges (
{1-9},{a-z},{1-3,5-9,i-k,o-z}) - in-place reloading (
dxhd -r) - calculating the time parsing a config file took (
dxhd -p) - support for any shell scripting language (sh, bash, ksh, zsh, python, perl etc.) given as a shebang
- support for scripting, as much as a user wishes!
! outdated gif !
The default config file is located at ~/.config/dxhd/dxhd.sh, however, dxhd can use a file from any path, by passing it to -c:
dxhd -c /my/custom/path/to/a/config/fileA dxhd config file should containt a shebang (defaults to /bin/sh) on top of a file, which is where binding actions take action
* config file *
#! shebang
## a comment
######### a comment
# key + combo
<what to do>
# key + combo + with + {1-9,0,a-z} + ranges
<what to do {with,these,ranges}>
Rather then dxhd self daemonising itself, let other programs do their job.
Use systemd, runit, openrc or other Linux init system to start dxhd on system startup,
or let your DE/WM start it by adding an ampersant at the end dxhd -c path/to/config &,
optionally, use disown keyword to make it not owned by the DE/WM process.
Licensed under the MIT license.
Because I had (and have) 20 workspaces, and sxhkd did not allow me to have 11-19 range,
that was one of the main reasons I started developing dxhd
- dxhd uses shebang to determine which shell to use (so you don't have to set an environment variable)
- dxhd config file syntax matches shell, python, perl and probably some other languages syntax
- dxhd is great with scripting, because of it's elegant syntax. multi line scripts do not need
\at the end of line - dxhd allows you to have different range in a keybinding's action, for example,
1-9in a keybinding, and11-19in it's action - dxhd has support for mouse bindings out of the box, no patching required!
It is simple enough! (I personally used Vim macros when I did it, because if you use Vim, you'll know why:)
- convert any line starting with single
#to a dxhd comment (so ## or more) - put
#before every keybinding (super + ato# super + a) - remove spaces before lines (
echo footoecho foo) (optional) - remove every end-line backslash (
echo bar \toecho bar) (probably optional, unsure)
So you'd end up with:
# print hello world
super + a
echo hello \
echo world
to
#!/bin/sh
## print hello world
# super + a
echo hello
echo worldYes! and no. dxhd has released key events and ranges, but no chords (yet - wip)
They haven't benchmarked yet, so I don't know. However, been using dxhd since the first release and haven't noticed any speed loss!
Because it's statically built, to make sure it will work on any amd64 linux machine! You can build dxhd instead to get much smaller file size. (build with -ldflags "-s -w")