Add keybindings

Author: kylebarron

package.json

@@ -21,11 +21,11 @@
     "commands": [
       {
         "command": "vscode-jupyter-python.run-inferred-block",
-        "title": "Run inferred code block"
+        "title": "Jupyter Python: Run inferred code block"
       },
       {
         "command": "vscode-jupyter-python.run-inferred-block-and-move-down",
-        "title": "Run inferred code block and move down"
+        "title": "Jupyter Python: Run inferred code block and move down"
       }
     ],
     "configuration": {
@@ -54,7 +54,20 @@
           "description": "If the above setting is enabled, this list will be passed to a regex. Any of these items in the list need to occur on the same intentation level as the first line. You may define your own custom elements to modify the code to your preferred behaviour. In the default setting, else, elif, except, finally, as well as all closing braces are expanded on."
         }
       }
-    }
+    },
+    "keybindings": [
+      {
+        "command": "vscode-jupyter-python.run-inferred-block",
+        "key": "ctrl+enter",
+        "mac": "cmd+enter",
+        "when": "editorTextFocus && editorLangId == python && !findInputFocussed && !replaceInputFocussed && jupyter.ownsSelection && !notebookEditorFocused"
+      },
+      {
+        "command": "vscode-jupyter-python.run-inferred-block-and-move-down",
+        "key": "shift+enter",
+        "when": "editorTextFocus && editorLangId == python && !findInputFocussed && !replaceInputFocussed && jupyter.ownsSelection && !notebookEditorFocused"
+      }
+    ]
   },
   "extensionDependencies": [
     "ms-toolsai.jupyter"

vsc-extension-quickstart.md

@@ -1,33 +1,38 @@
 # Welcome to your first VS Code Extension
 
 ## What's in the folder
-* This folder contains all of the files necessary for your extension
-* `package.json` - this is the manifest file in which you declare your extension and command.
-The sample plugin registers a command and defines its title and command name. With this information
-VS Code can show the command in the command palette. It doesn’t yet need to load the plugin.
-* `src/extension.ts` - this is the main file where you will provide the implementation of your command.
-The file exports one function, `activate`, which is called the very first time your extension is
-activated (in this case by executing the command). Inside the `activate` function we call `registerCommand`.
-We pass the function containing the implementation of the command as the second parameter to
-`registerCommand`.
+
+- This folder contains all of the files necessary for your extension
+- `package.json` - this is the manifest file in which you declare your extension and command.
+  The sample plugin registers a command and defines its title and command name. With this information
+  VS Code can show the command in the command palette. It doesn’t yet need to load the plugin.
+- `src/extension.ts` - this is the main file where you will provide the implementation of your command.
+  The file exports one function, `activate`, which is called the very first time your extension is
+  activated (in this case by executing the command). Inside the `activate` function we call `registerCommand`.
+  We pass the function containing the implementation of the command as the second parameter to
+  `registerCommand`.
 
 ## Get up and running straight away
-* press `F5` to open a new window with your extension loaded
-* run your command from the command palette by pressing (`Ctrl+Shift+P` or `Cmd+Shift+P` on Mac) and typing `Hello World`
-* set breakpoints in your code inside `src/extension.ts` to debug your extension
-* find output from your extension in the debug console
+
+- press `F5` to open a new window with your extension loaded
+- run your command from the command palette by pressing (`Ctrl+Shift+P` or `Cmd+Shift+P` on Mac) and typing `Hello World`
+- set breakpoints in your code inside `src/extension.ts` to debug your extension
+- find output from your extension in the debug console
 
 ## Make changes
-* you can relaunch the extension from the debug toolbar after changing code in `src/extension.ts`
-* you can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your extension to load your changes
+
+- you can relaunch the extension from the debug toolbar after changing code in `src/extension.ts`
+- you can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your extension to load your changes
 
 ## Explore the API
-* you can open the full set of our API when you open the file `node_modules/vscode/vscode.d.ts`
+
+- you can open the full set of our API when you open the file `node_modules/vscode/vscode.d.ts`
 
 ## Run tests
-* open the debug viewlet (`Ctrl+Shift+D` or `Cmd+Shift+D` on Mac) and from the launch configuration dropdown pick `Launch Tests`
-* press `F5` to run the tests in a new window with your extension loaded
-* see the output of the test result in the debug console
-* make changes to `test/extension.test.ts` or create new test files inside the `test` folder
-    * by convention, the test runner will only consider files matching the name pattern `**.test.ts`
-    * you can create folders inside the `test` folder to structure your tests any way you want
+
+- open the debug viewlet (`Ctrl+Shift+D` or `Cmd+Shift+D` on Mac) and from the launch configuration dropdown pick `Launch Tests`
+- press `F5` to run the tests in a new window with your extension loaded
+- see the output of the test result in the debug console
+- make changes to `test/extension.test.ts` or create new test files inside the `test` folder
+  - by convention, the test runner will only consider files matching the name pattern `**.test.ts`
+  - you can create folders inside the `test` folder to structure your tests any way you want