junegunn / junegunn/fzf

fzf incompatible with xcape/setxkbmap

Open
#1,376 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
83k
Forks
2.9k
Avg merge
17h 8m
Merged PRs (30d)
10

Description

- Category
- [x] fzf binary
- [ ] fzf-tmux script
- [x] Key bindings
- [ ] Completion
- [ ] Vim
- [ ] Neovim
- [ ] Etc.
- OS
- [x] Linux
- [ ] Mac OS X
- [ ] Windows
- [ ] Windows Subsystem for Linux
- [ ] Etc.
- Shell
- [x] bash
- [ ] zsh
- [ ] fish

In my bashrc map my caps lock key to be ctrl on hold and escape on tap as follows:
```
setxkbmap -option ctrl:nocaps
xcape -e 'Control_L=Escape'
```
When I launch fzf after this setup, tapping escape to exit does not work - I need to press ctrl-c (caps-c since I've remapped it) to exit. Moreover, it seems that for every tap of escape I need to press ctrl-c to pop it off some stack before the final ctrl-c quits. I think this is related to a general problem of respecting keyboard mappings (see https://github.com/junegunn/fzf/issues/1291). On OSX w/ karabiner and/or keyboard maestro I did not have this problem.

I am running fzf version 0.17.3

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the issue from the bashrc setup using setxkbmap, xcape, and fzf 0.17.3, then compare the keyboard-mapping behavior discussed in issue 1291. Done means tapping the remapped Escape exits fzf without requiring repeated Ctrl-C presses.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash, go, linux
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.