stevenguh / spacecode Goto Github PK

idea

Right now the only way to customize the actions is to completely redefine "spacecode.bindings" in your settings.json.

There should be a way to add or override single key bindings without deleting all the others.

example

If I put this in my settings.json, SPC f f should be edited, SPC f q should be added because it doesn't exist yet and all the other key bindings should remain as defined by default.

{
  "spacecode.mybindings": [
    {
      "key": "f",
      "name": "File...",
      "type": "bindings",
      "bindings": [
        {
          "key": "f",
          "name": "New Action Name",
          "type": "command",
          "command": "action.which.I.prefer.over.default"
        },
        {
          "key": "q",
          "name": "New Action Name",
          "type": "command",
          "command": "my.action.for.this.new.key.binding"
        },
        
      ]
    }
  ]
}

I followed this instruction from the readme:

To customize the menu, copy the default spacecode.bindings value in package.json in this repo and put the updated spacecode.bindings config in your own setting.json.

When I copy spacecode.bindings I get the following error:

Instead something like this works:

{
   "spacecode.bindings":[
      {
         "key":"f",
         "name":"File...",
         "type":"bindings",
         "bindings":[
            {
               "key":"f",
               "name":"Open file",
               "type":"command",
               "command":"workbench.action.files.openFileFolder"
            },
            {
               "key":"i",
               "name":"Indentation...",
               "type":"bindings",
               "bindings":[
                  {
                     "key":"i",
                     "name":"Change indentation",
                     "type":"command",
                     "command":"changeEditorIndentation"
                  },
                  {
                     "key":"d",
                     "name":"Detect indentation",
                     "type":"command",
                     "command":"editor.action.detectIndentation"
                  }
               ]
            }
         ]
      }
   ]
}

example here

Draft:

to test the project:

1. clone and project
2. checkout develop branch
3. open the folder with vscode
4. Press F5 to run a debug vscode with extension in development installed on that instance.

When the migration to VSpaceCode is finished, this repo should be archived and there should be a link to the new repo in the README.

I am opening this to track the issue where space cannot be in vim command.
The solution is use vim's configuration to trigger the spacecode.space command. However, we need to have a popup to notify user to migrate when they the extension is updated.

• Update README
• Add popup when updating to new version to use different configuration

This idea is coming from #8. It would be great to have a script in the prepublish step to generate a markdown table from the default bindings in the package.json to use in README.md. I am thinking this would generate a separate markdown file at the root directory like KEYBINDINGS.md then the README.md can refer to all the default key bindings we have.

I try to get double space to execute command "workbench.action.showCommands" like this

It do appear in my quickOpenList,but it doesn't work when I press space and space like spacemacs

I installed all the required extension, I have a settings file like the one from VSpaceCode

Installed plugins:

But when I press space this popup appears:

I'm happy to see a Spacemacs like keybinding and menu scheme brought to vscode. I have tried it out and it already works really well for what it does. Thank you for writing this!

I see that you've already been speaking with @MarcoIeni in another issue. I didn't see him mention it, but he maintains similar extensions for some other editors (spaceclipse and intellimacs). I think that the keybinding list that he created could be especially useful for a new project like this.