You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Accidentally hitting esc/q and losing the flow of what you are doing isn't the end of the world, but atm it seems a little too easy to accidentally do.
As it stands those keybinds insta-quit the dashboard, even in circumstances where instincts from other UIs & general expectations suggest it shouldn't.
Most notably, when you have hit ? and have the 'help' (cheatsheet?) open, it is quite easy to absent mindedly expect at least esc to just close that, not exit the entire program.
I'd propose hitting those keys when you most recently opened up a kinda sub-window like that, it should close those in reverse order before attempting to quit the whole dashboard.
I think perhaps a 'really quit?' prompt would be a nice QoL improvement. Imo having quick and easy options to confirm the quit (e.g. hitting esc or q again, hitting y, hitting return, etc.) should mean the nag is outweighed by avoiding the flow-breaking drop back to the terminal.
The text was updated successfully, but these errors were encountered:
Accidentally hitting
esc
/q
and losing the flow of what you are doing isn't the end of the world, but atm it seems a little too easy to accidentally do.As it stands those keybinds insta-quit the dashboard, even in circumstances where instincts from other UIs & general expectations suggest it shouldn't.
Most notably, when you have hit
?
and have the 'help' (cheatsheet?) open, it is quite easy to absent mindedly expect at leastesc
to just close that, not exit the entire program.I'd propose hitting those keys when you most recently opened up a kinda sub-window like that, it should close those in reverse order before attempting to quit the whole dashboard.
I think perhaps a 'really quit?' prompt would be a nice QoL improvement. Imo having quick and easy options to confirm the quit (e.g. hitting
esc
orq
again, hittingy
, hittingreturn
, etc.) should mean the nag is outweighed by avoiding the flow-breaking drop back to the terminal.The text was updated successfully, but these errors were encountered: