-
-
Notifications
You must be signed in to change notification settings - Fork 196
Description
Feature Request Description
Coming from Rectangle, I used to use ctrl-opt as my trigger key. So when configuring Loop, I bound ctrl-opt-backspace to Undo. Later, I discovered that Loop could use fn as the trigger key, so I changed to that.
You might see the problem here...delete (fn-backspace) ended up being bound to Undo. It doesn't trigger the Undo functionality, either. I never noticed this though, because I guess I never really use Undo. Besides, fn-backspace still deletes text normally (without triggering Loop) in 1.3.0.
However, in 1.4.0, delete (fn-backspace) randomly stops working, presumably because of the trigger key improvements. It still doesn't seem to trigger the Undo functionality, though.
I confirmed that Loop was breaking the delete key by:
- Wait until delete stops working
- Open Loop using Raycast
- alt-tab back to the other app to make sure delete is still broken
- alt-tab to Loop to quit it
- Confirm that delete works again
I don't really consider this a bug, since I did create the keybind. But the behaviour is undesired because it sometimes breaks the delete key without actually providing the Undo functionality.
I'm not really sure how this should be handled. I don't think someone would intentionally bind fn-backspace to Loop?! I'm guessing the best way to resolve this would be to prevent users from accidentally binding fn-backspace.
Screenshots
No response
Additional Context
No response
Final Checks
- My issue is written in English
- My issue title is descriptive
- This is a single feature request (multiple feature requests should be reported individually)
- I can help with the improvement or development of this feature (tick if you can help)