-
-
Notifications
You must be signed in to change notification settings - Fork 805
Keyboard Shortcut resets to default after relaunch #1715
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
Comments
I have the same problem on Windows 11 23H2 , but I also can't change the default shortcuts / they don't work after changing them to something other than the default. |
Same is occurring on Windows 10 22H2, they reset on relaunch. |
Related: #1629 |
Also happening for me after updating to 1.0.1-a.5 |
Experiencing this on 1.0.1-a.5 on Linux as well, no modifications to any shortcuts are persisting between launches. |
Shortcuts is a disaster, to be honest. |
same here. deleted and made a new profile, issue persists but ctrl + seems to work now. |
Same here, after customizing the keybindings, everything works fine for a while then suddenly they are all reset to default keybindings without any notice :| |
do they update once you reload the preferences page? You also need to press "esc" to save them |
Yes, I did press |
Same issue on Macbook M1. Shortcuts are reset to default. |
Doesn't matter if you press I've done this 5-10 times now on both Linux and Windows, same result every time. |
did esc to save, & reloading the preferences page doesn't reset, relaunching the app reset shortcuts |
Same here, at first it worked on one PC (Windows 10) but not on the other (Windows 11). After a restart of both PCs it shortly worked on the second one, but now it does not work on either. |
Same here on my linux machine (Fedora 40 Gnome) |
same here, also when i try to change the "New Tab" shortcut to |
It seems to happen whenever a new Zen window is launched.
Shortcuts are then reset to default Linux 6.10.10-arch1-1 x86_64 |
I'm having the same issue, I changed the keymap and saved with esc, put after relaunch they reset to default. Previously, they worked fine, but after an update they got reset, and they keep resetting. This is happening on Linux. |
Update: this will be fixed on the next release, thanks |
Thank you @mauro-balades! Can you confirm if this also fixes the macOS cmd key being mapped to a "meta" key in the shortcuts settings as well? |
@mauro-balades cmd+q for close and cmd + ; for settings are also not working. Would be nice to fix too 🙂 |
Check which version you're on, This issue was solved on last update, It's works now |
I'm on Alpha build - 1.0.1-a.5. After restarting Zen it works again. Thx. |
Can i close? |
A wait, actually after remapping some other shortcuts, it stopped working for me... |
Keymaps are being cleared whenever a new Zen window opens, could be the issue. A fix is in the next patch. |
I'm still having the same problem on win 11 with the latest version, it keeps resetting after relaunch |
I guess we have to wait for the new release. |
I am having the same issues meantioned here. I miss a lot of the 'old' shortcuts as well like switching workspaces and jumping back and forth in tabs. anyone else is missing them? I miss them on all my machines. |
+1 |
+1 I am having this same issue and now can't access next tab and previous tab shortcuts. |
+1 |
I'd also like to add the 'Open Settings' shortcut back. |
+1 here |
In my case the problem mysteriously went away after a few browser restarts, a few Windows restarts and some try's of setting the shortcuts. |
I'm on macOS Sonoma 14.6.1 and am having trouble regardless of restart or not. Setting |
This has been fixed, thanks a lot! |
Exact same issue - but on Sequoia |
Captchas
What happened?
After quiting and reopening the app, Keyboard Shortcut resets to default. Also after setting F13 as Close Tab, it doesn't work insstead "F" closes the tab, F13 don't work as keyboard shortcut. but because everything resets to default, F13 doesn't matter now anyway, please fix it.
Reproducible?
Version
1.0.1-a.5
What platform are you seeing the problem on?
macOS - Intel
Relevant log output
No response
The text was updated successfully, but these errors were encountered: