Skip to content
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.

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

Holding key on macOS brings up accent/diacretic menu #5130

Open
ben-goldman opened this issue Dec 12, 2021 · 3 comments
Open

Holding key on macOS brings up accent/diacretic menu #5130

ben-goldman opened this issue Dec 12, 2021 · 3 comments

Comments

@ben-goldman
Copy link

Version: 1.0.167
Platform: macOS x64 20.1.0
Plugins: none
Frontend: xterm

When I hold a key that has accented versions (most values and a few consonants), the macOS menu appears to select an accented version, located off the main window. It becomes a problem when holding down the l key in vim. Is there a way to prevent this from happening?

Thanks! This is a really great piece of software, and I'm excited to see where it goes!

@cpecorari
Copy link

Hey just happened to find out Macos Monterey (Darwin 21.1.0) has strange behavior but you can enable repeat keys with this command :

defaults write NSGlobalDomain ApplePressAndHoldEnabled -bool false

But still got issue with repeated keys with shortcut like alt+arrow left.

@cpecorari
Copy link

Just found out too that on mac Os it works better disabling Tabby Meta key, now all shortcuts, long press etc work perfectly !

Capture d’écran 2022-03-16 à 16 03 44

@SimplyBob
Copy link

SimplyBob commented Oct 2, 2024

I'm experiencing this on macOS Sequoia 15.0

In VIM I'm using home row for navigation, and when I hold "k" to move up, see the popup in the bottom left hand corner for special the special character "ķ". I tried setting the option to Use option as the Meta key - but the special character still appeared after restarting the app.

I've not experienced this problem in Terminal or iterm2. Aside from this, I'm really enjoying Tabby so far, thanks!
image

Edit: I did confirm that disabling the feature system wide and restarting the app did prevent it from popping up, but it's not the desired way to handle it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants