aboutsummaryrefslogtreecommitdiff
path: root/dotfiles/hyprland/.local/bin/waybar-airplane
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-02 12:16:38 -0500
committerCraig Jennings <c@cjennings.net>2026-06-02 12:16:38 -0500
commita816122f49d2c7e43e41308e251e133197a486bc (patch)
tree246b46b53c956cfea07bc9d1c2b81f9f8de53d65 /dotfiles/hyprland/.local/bin/waybar-airplane
parentc8ac4d0040309c9b4226a331bafdfa0bd3f4bb73 (diff)
downloadarchsetup-a816122f49d2c7e43e41308e251e133197a486bc.tar.gz
archsetup-a816122f49d2c7e43e41308e251e133197a486bc.zip
refactor: drop in-repo dotfiles/, move stow tooling to the dotfiles repo
Since the installer clones DOTFILES_REPO into ~/.dotfiles and stows from there, the in-repo dotfiles/ tree was dead weight. Nothing reads it at install time. I removed it (831 files) now that both machines are migrated. The Makefile's stow / restow / reset / unstow / import targets and the dotfile-script unit suites moved to the dotfiles repo. They sit alongside the scripts they manage and run standalone (cd ~/.dotfiles && make ...). This Makefile keeps the VM-integration targets and the installer-helper suite (safe-rm-rf). I updated CLAUDE.md and README.md so stow operations run from ~/.dotfiles, and the dotfile-management, theme, and unit-test sections point at the standalone repo. The README was already describing the old in-repo model from before the installer switched to cloning. This brings it in line.
Diffstat (limited to 'dotfiles/hyprland/.local/bin/waybar-airplane')
-rwxr-xr-xdotfiles/hyprland/.local/bin/waybar-airplane33
1 files changed, 0 insertions, 33 deletions
diff --git a/dotfiles/hyprland/.local/bin/waybar-airplane b/dotfiles/hyprland/.local/bin/waybar-airplane
deleted file mode 100755
index 21f869c..0000000
--- a/dotfiles/hyprland/.local/bin/waybar-airplane
+++ /dev/null
@@ -1,33 +0,0 @@
-#!/bin/sh
-# Airplane-mode indicator for waybar.
-# Reads the state file the airplane-mode toggle maintains; emits one JSON line
-# (text + tooltip + class) for the custom/airplane module. The file holds
-# key=value lines; only `mode` (on/off) matters here. Anything other than
-# "on" reads as off, so a missing or garbled state file fails safe (airplane
-# mode shown as inactive — i.e. radios assumed on).
-#
-# Laptop-only: airplane mode is meaningless on a desktop, so the module hides
-# itself (emits nothing → waybar drops it) on machines with no battery.
-
-STATE_FILE="${XDG_RUNTIME_DIR:-/tmp}/airplane-state"
-PS_DIR="${AIRPLANE_POWER_SUPPLY_DIR:-/sys/class/power_supply}"
-
-# Laptop check: a battery present means this is a portable machine.
-is_laptop() {
- for b in "$PS_DIR"/BAT*; do
- [ -e "$b" ] && return 0
- done
- return 1
-}
-
-is_laptop || exit 0
-
-mode=$(sed -n 's/^mode=//p' "$STATE_FILE" 2>/dev/null | head -n1)
-
-# Same clear plane glyph in both states; the class drives the color (gold when
-# engaged, default gray when not) so there's no slash to obscure the wings.
-if [ "$mode" = "on" ]; then
- echo "{\"text\": \"<span size='large'></span>\", \"tooltip\": \"Airplane mode ON — wifi off, low power\", \"class\": \"active\"}"
-else
- echo "{\"text\": \"<span size='large'></span>\", \"tooltip\": \"Airplane mode OFF\", \"class\": \"inactive\"}"
-fi