Commits (2)
  • Gigadoc 2's avatar
    enable numlock by default · 1e98bf13
    Gigadoc 2 authored
  • Gigadoc 2's avatar
    … and back to scopes · c6f26fd9
    Gigadoc 2 authored
    Semantics were just too wrong, as some applications re-launch themselves
    (for reloading or for opening a second instance) without going through
    anything I can inject a systemd-run into. Then when the original process
    quits, the service is considered stopping.
    On a side note, some logs seem to get attributed properly with scopes.
......@@ -31,11 +31,15 @@ set $down j
set $up k
set $right l
# Your preferred terminal emulator
set $term /usr/bin/konsole
# Launch applications through wofi, in a transient systemd service.
# Why exit status 1? Because thats what wofi exits with when I cancel launch.
set $menu systemd-run --user --service-type=forking -q \
-p PartOf=graphical-session.target -p SuccessExitStatus=1 \
set $term /usr/bin/systemd-run --user --scope -q \
-p PartOf=graphical-session.target \
--unit="konsole-$(systemd-id128 new).scope" \
--description="sway-launched terminal" \
-- /usr/bin/konsole
# Launch applications through wofi, in a transient systemd scope.
set $menu /usr/bin/systemd-run --user --scope -q \
-p PartOf=graphical-session.target \
--unit="wofi-$(systemd-id128 new).scope" \
--description="sway-wofi-launched application" \
-- /usr/bin/wofi -S drun -i -t $term
# Set up workspaces with names
......@@ -121,6 +125,7 @@ input "1:1:AT_Translated_Set_2_keyboard" {
xkb_layout de
xkb_model "pc105"
xkb_options "caps:hyper,altwin:swap_lalt_lwin,shift:both_capslock_cancel"
xkb_numlock enabled
input "2689:517:CHESEN_PS2_to_USB_Converter" {
xkb_layout de
......@@ -158,9 +163,7 @@ font SF Pro Display 9
# Basics:
# start a terminal
bindsym $mod+Return exec systemd-run --user --service-type=exec -q \
-p PartOf=graphical-session.target \
--description="sway-launched terminal" -- $term
bindsym $mod+Return exec $term
# kill focused window
bindsym $mod+Shift+q kill