tidalcycles/vscode-tidalcycles

shift+enter keybinding overrides other extensions/default behaviours

Opened this issue · 1 comments

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

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