Skip to content

fix: caps-remap restarts only its own xcape instance #63

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
YASoftwareDev merged 1 commit into from
Sep 26, 2026
Merged

fix: caps-remap restarts only its own xcape instance #63

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion x11/caps-remap.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,8 +41,10 @@ xmodmap -e "add Control = Hyper_L" || true

# (Re)start xcape. -t 200: taps shorter than 200 ms produce Escape; anything
# longer is treated as a Ctrl hold. Raise to 300-500 if taps feel missed.
# Only our own instance is replaced: other tools may run xcape for other keys
# (xcape rewrites its argv in place, so '=' shows up as a space).
if command -v xcape >/dev/null 2>&1; then
pkill -x xcape 2>/dev/null || true
pkill -f '^xcape .*-e Hyper_L' 2>/dev/null || true
xcape -t 200 -e 'Hyper_L=Escape'
else
echo "caps-remap: xcape not found - tap-to-Escape will not work" >&2
Expand Down
Loading