Repository navigation
Having caps lock on should NOT NUKE the tree instead of discarding the selected file! #5610
digitalrobin
started this conversation in
General
Replies: 1 comment
|
Didn't have this disastrous affect for me but came close, not sure if there's a way for a TUI to detect capslock? But if it is possible it might be handy to throw an error or a warning until capslock is released - I understand though for accessibility reasons it might be the way that some people type capital letters all the time - so not sure the best approach - but can confirm that it can be a bit of a shock when CAPSLOCK is on accidentally. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Imo, this is just horrible design. I have been using lazygit for 2+ years, and today i accidentally had capslock on. Being so used to the controlls, i do everything blindly, resulting in a nuked tree with a couple of days worth of work just GONE.
It just simply should not be the first selected option, and then just NUKE everything without any additional confirmation!
Very disappointed at this.
All reactions