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
{{ message }}
This repository has been archived by the owner on Mar 12, 2020. It is now read-only.
In short, installing SQLTools has ruined my keyboard navigation because "ctrl+e" no longer takes me to the end of the line.
If it occurred only when writing SQL code then it would be one thing but this (and then the accompanying "You need to setup your connections first." pop up) is, for example, affecting me when trying to write in Python.
Basically, since said key-binding is one of the most frequently used bindings of text navigation for OS X and also taking this into account re: Windows, you might want to consider something totally different as far as keybindings go.
Lastly, as an aside, you should also think about starting your pop up messages with "SQLTools: " or something similar so that a user will immediately know which package is causing the issue instead of having to blindly resort to Google.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In short, installing SQLTools has ruined my keyboard navigation because "ctrl+e" no longer takes me to the end of the line.
If it occurred only when writing SQL code then it would be one thing but this (and then the accompanying "You need to setup your connections first." pop up) is, for example, affecting me when trying to write in Python.
Basically, since said key-binding is one of the most frequently used bindings of text navigation for OS X and also taking this into account re: Windows, you might want to consider something totally different as far as keybindings go.
Lastly, as an aside, you should also think about starting your pop up messages with "SQLTools: " or something similar so that a user will immediately know which package is causing the issue instead of having to blindly resort to Google.
The text was updated successfully, but these errors were encountered: