curlconverter-vscode
Vim
Our great sponsors
curlconverter-vscode | Vim | |
---|---|---|
1 | 41 | |
15 | 11,473 | |
- | 1.2% | |
1.7 | 9.1 | |
5 months ago | 8 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
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.
curlconverter-vscode
We haven't tracked posts mentioning curlconverter-vscode yet.
Tracking mentions began in Dec 2020.
Vim
- 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.
-
Coming Home to Vim
Are you familiar with vim q macros? It's a similar thing but you don't need to use maps/remaps to use them: q to start recording and q (in normal mode, so q sometimes) to stop recording. Then you can rerun the macro with @ (or @@ is rerun the last macro). (Even fun things like @ work to rerun the macro a number of times.)
VSCodeVim seems to support q-macros just fine. The lone silly missing bit is that VSCodeVim makes it slightly tougher to save/reuse q-macros than proper Vim [1]. In Vim those letters are the exact same "registers" as copy/paste so that you can record a macro to register 'a' with `qa…q` and then if you want to save that macro for later you can just paste it into a document somewhere `"a` (paste register a) and pull the macro back in with the right motion and yank to the register you want (`ya`). VSCodeVim unfortunately uses separate registers for now and it is a bit more work to save/restore q-macros.
-
What are some useful practices/tools that were utilized in your past/current company, that could be of great value if more people knew about them?
Checkmate: https://github.com/VSCodeVim/Vim
-
Vim, infamous for its steep learning curve, often leaves new users confused where to start. Today is the 10th anniversary of the infamous "How do I exit Vim" question, which made news when it first hit 1 million views.
I don’t think either currently allows defining those on top of the extension, but you could in the extension itself. Or write it as a plugin extension, effectively, and bind it to whatever you want.
-
rip atom and fuck microsoft (vs code is kinda nice tbh doe)
You might be interested in VSCodeVim giving you the power of vims workflow with the flexibility and extensibility of vscode.
-
You get in a time machine and go forward 5 years. What version of neovim is about to be released, and what features does it have?
Firenvim embeds Neovim in the browser, Qnvim in QtCreator, VSCodeVim/VSCode-neovim in VSCode... Why aren't they good examples in your opinion? :)
-
VSCode integration
For these situations, I just use the regular Vim extension. It's portable and works well enough out-of-the-box. I'm not sure if it's worth going through the Neovim integration unless you want to configure it.
-
School sucks
if you’re used to vscode and would prefer to keep using it while also using vim, there are two major plugins that provide support for it within vscode. vscode-neovim utilizes neovim’s goal of providing an api so that one can use the actual neovim program within other IDEs/text editors rather than simulating it, and VSCodeVim seeks to emulate vim within vscode (and has been extant for much longer than vscode-neovim).
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 VS Code using embedded Neovim
NvChad - An attempt to make neovim cli functional like an IDE while being very beautiful, blazing fast startuptime
SpaceVim - A community-driven modular vim/neovim distribution - The ultimate vimrc
coc-java - Java extension for coc.nvim
vimrc - The ultimate Vim configuration (vimrc)
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
vim-mark - Highlight several words in different colors simultaneously.
vscode-emacs-mcx - Awesome Emacs Keymap - VSCode emacs keybinding with multi cursor support
vundle - Vundle, the plug-in manager for Vim
nnn.vim - File manager for vim/neovim powered by n³
vscode-live-sass-compiler - Compile Sass or Scss file to CSS at realtime with live browser reload feature.