Skip to content

shift+enter keybinding overrides other extensions/default behaviours #35

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

Open
jarmitage opened this issue Nov 10, 2022 · 1 comment
Open
Labels
bug Something isn't working

Comments

@jarmitage
Copy link

E.g. when in a .py file, Shift+Enter will cause Tidal process to start, when instead it should only start when the user is in a .tidal file, and a Python interpreter should be able to launch with Shift+Enter as normal

Currently I have to disable the Tidal extension in order to launch a Python interpreter

@jarmitage jarmitage added the bug Something isn't working label Nov 10, 2022
@jarmitage
Copy link
Author

Workaround is to use two workspaces and disable Tidal extension globally, then enable it only for a single workspace where you're doing Tidal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant