I'm a long time Vim user, and I want to move to VS Code for a while. I like to script my editor a lot (PDE-style). How should I approach this?

• dotfiles

  1 26 7.8 Lua

  My dot files (by skanev)

Trying to explain it, while working in Vim, I can decide to add a custom command that I'm going to be using, so I can just open a `.vim` file that has my commans (or `.lua`), add it in there, reload it, check if it works as I intended, and just keep going on what I was doing before. This is primarily the experience I want to achieve in customizing VS Code. I've went through the Extension writing tutorial, but this one seems to be a bit more complicated. I'm also keen to just store everything in git, so I can share it with other people (e.g. my dotfiles for vim, zsh, and so on: github.com/skanev/dotfiles).

• code-settings-sync

  6 4,001 0.0 TypeScript

  🌴💪 Synchronize your Visual Studio Code Settings Across Multiple Machines using GitHub GIST 💪🌴

Note: If you do, be aware of this bug and workaround.

• SurveyJS

  surveyjs.io sponsored

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• joyride

  17 443 7.9 Clojure

  Making VS Code Hackable like Emacs since 2022 (by BetterThanTomorrow)

  

This is why we created Joyride, which lets you script VS Code in user space. Not only that, it gives you a REPL letting you control VS Code and modify your script as they are running. The main inspiration comes from Emacs, the definition of a hackable editor. https://github.com/BetterThanTomorrow/joyride

Suggest a related project