From e81161a7900556a563594a051d4fad58733cafb7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Moritz=20Mei=C3=9Felbach?= Date: Fri, 15 Nov 2019 20:30:59 +0100 Subject: [PATCH] Include note about the AUR --- README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index c4a39d7..94ffe1f 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,11 @@ Despite its name, it does not (read: no longer) depend on the Sway window manage ## Installation -Make sure you have `fzf` installed and download this repository +Make sure you have `fzf` installed and download this repository. +Arch Linux used can also grab it from the AUR (thanks @turtlewit) + +* [sway-launcher-desktop](https://aur.archlinux.org/packages/sway-launcher-desktop/) +* [sway-launcher-desktop-git](https://aur.archlinux.org/packages/sway-launcher-desktop-git/) Configure it in Sway like this: ``` @@ -24,5 +28,7 @@ set $menu exec urxvt -geometry 55x18 -name launcher -e env TERMINAL_COMMAND="urx bindsym $mod+d exec $menu ``` + + ### Setup a Terminal command Some of your desktop entries will probably be TUI programs that expect to be launched in a new terminal window. Those entries have the `Terminal=true` flag set and you need to tell the launcher which terminal emulator to use. Pass the `TERMINAL_COMMAND` environment variable with your terminal startup command to the script to use your preferred terminal emulator. The script will default to `urxvt -e`