Vim
vscode-emacs-mcx
Our great sponsors
Vim | vscode-emacs-mcx | |
---|---|---|
52 | 4 | |
13,217 | 349 | |
1.5% | - | |
9.4 | 9.3 | |
7 days ago | 7 days ago | |
TypeScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Vim
- The IDEs we had 30 years ago and we lost
- The Loneliness of the Mid-Level Vimmer
-
Multiple Notepad++ Flaws Let Attackers Execute Arbitrary Code
I find the Vim extension for VS Code has macro support that is good enough for most of my use cases (if you’re a fan of Vim key bindings - obviously).
https://github.com/VSCodeVim/Vim/blob/master/ROADMAP.md#repe...
-
VSCode with Neovim?
that's why I just use https://github.com/VSCodeVim/Vim if I have to use VSCode
This post is all over the place. What are you asking? What problem exactly did you have with the https://github.com/vscode-neovim/vscode-neovim (ensure that you did not install https://github.com/VSCodeVim/Vim , which people often confuse with the other).
-
Neovim vs VSCode Neovim - what are the tradeoffs?
What you would learn from using a neovim addon for VS Code covers most of the first point and some of the second - VSCode Vim lets you run neovim in a headless mode that relays keypresses to it, and emulates several popular addons. It also comes without quite as much hassle as comes from the second step of learning to configure vim/neovim yourself. Most VSCode extensions work pretty well out of the box, maybe requiring you to add the path to a compiler/interpreter that is not on your PATH.
-
I'm stuck between CB-GK-16 and 617, I like 617 more cause it looks better. Now the situation is I'm a programmer, I don't mind learning new bindings but is it worth it? If you have any experiences that would help me, please share them with me :)
Either I go with K552 or save for RK84 if not CB-GK-16 and both of these are pretty good choice that's certain, or I go with 617 Fizz and use VIM keybinding which Isn't an issue for me cause I've been using NeoVim for more than 1 year, you can grab my dotfiles if you want. Most people won't go with 60% cause they are used to arrow, home, end ... keys so am I with vs code but today I found out about vscodevim extension which enables vim keybinding , these keybindings pretty easy to use more than arrow, home, end .. keys if yo're a vim user like Shift + $ = end, Shift + 0 = home, in visual mode V to select text etc ...
- Showing VS Code to a Vim user be like
-
Optimize nvim in VS Code
There is also VSCodeVim extension: https://github.com/VSCodeVim/Vim which afaik does not use any external programms.
-
New to modal editing, can't decide whether I should learn Neovim or Helix
We're all biased here because you're asking in a neovim community. You should ask in a helix community but I think they'll also agree that you should learn vim first. Neovim and vim are the same in terms of modal editing. You may try vscodevim so that it doesn't change too much of your workflow and you can focus on the basic movement. And also you don't need to think about the neovim plugin ecosystem for now until you're comfortable with vanilla vim movement. For jetbrains products there are vim binding emulators too so it's more universal. I use vim emulator in intellij.
vscode-emacs-mcx
-
Paredit 25 Released
Hi Mickey, ah no -- you've done WAY more than me in this area! I had been meaning to try your combobulate package.
FWIW: after 20 years of Emacs I personally switched to VSCode a couple of years ago because I felt that in Emacs I was missing out on the LSP experience that VSCode provided in Rust, Typescript, Scala, etc. (I was using Eglot). In any case, there's a very nice Emacs emulation mode in VSCode
https://github.com/whitphx/vscode-emacs-mcx
which includes some paredit functionality courtesy of
https://robert.kra.hn/past-projects/paredit-js.html
and I'm working on porting my favorite paredit function, paredit-kill. Unfortunately that's the one where the paredit author left this comment in the code:
;;; Please do not try to understand this code unless you have a VERY
-
Just sharing this Emacs keybinding extension I made for VSCode
It has been requested in the issue, but not been implemented yet; https://github.com/whitphx/vscode-emacs-mcx/issues/772
Yes. You can configure key assignments through keybindings.json. See https://code.visualstudio.com/docs/getstarted/keybindings#\_advanced-customization Combining multi commands are also possible with multi-command extension. These are examples. https://github.com/whitphx/vscode-emacs-mcx/issues/392 https://github.com/whitphx/vscode-emacs-mcx/issues/965
What are some alternatives?
vscode-live-server - Launch a development local Server with live reload feature for static & dynamic pages.
vscode-neovim - Vim mode for VSCode, powered by Neovim
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
vscode-gitlens - Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more
vscode-drawio - This unofficial extension integrates Draw.io (also known as diagrams.net) into VS Code.
coc-java - Java extension for coc.nvim
SpaceVim - A community-driven modular vim/neovim distribution - The ultimate vimrc
vimrc - The ultimate Vim configuration (vimrc)
vim-mark - Highlight several words in different colors simultaneously.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
vundle - Vundle, the plug-in manager for Vim
codetour - VS Code extension that allows you to record and play back guided tours of codebases, directly within the editor.