-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.vimrc support #463
Comments
Yup, assign this to me as I'm working on a prototype. |
sick! |
Re-opening this -- we don't have .vimrc support. |
I'm gonna close this as although it's true that we don't support .vimrc, I believe our settings.json support is a solid equivalent, except better because it has autocomplete and documentation popups. If anyone disagrees, feel free to open a conversation on this issue. |
Well, I have a shared vimrc file for vim and vsvim. I would have loved to include that from here as well. |
I also expect vimrc support feature. Almost everyone using vscodevim knows how to config vimrc. So documentation popups feature is not that important as far as I see. I agree setting.json is good, but I think reuse and DRY means much. We can use vimrc in vsvim, ideavim, neovim, etc, but we cant't use vscode setting.json anywhere else. That's the problem. Maybe support both setting.json and vimrc is a better way? |
I see your argument. Reopening this issue. |
+1 for this feature. Is there any update? |
It's certainly on my radar, however it is currently deprioritized because:
If a bunch of people thumbs up the original issue, I'll certainly reconsider :) |
+1 for this feature. Is there any update? |
@polunzh The update is the post I made 9 days ago right above you. :P If you're curious, we pretty much tackle issues in this order: https://github.com/VSCodeVim/Vim/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc |
Just discovered Visual Studio Code, and immediately installed this plugin only to discover my .vimrc isn't being recognized 😢 I can't use vim mode without my vimrc, too many keybindings that I have developed over the years and too lazy to port them over to this plugin. |
Read key remapping commands from $HOME/.vimrc, $HOME/_vimrc, or a user-specified Vim configuration file. For each, build an IKeyRemapping object and append it to the appropriate collection, _if_ doing so will not override a remapping specified in the VS Code settings. Partially addresses #463. This implementation borrows heavily from Sheepolution/vimrc-to-json. * Add `editVimrc` command * Add .vimrc validator, correct usage of new config names * Source .vimrc automatically after saving it
For instance, `nnoremap gs workbench.action.showAllSymbols` will now work. Refs #463
For instance, `nnoremap gs workbench.action.showAllSymbols` will now work. Refs #463
Hey all! With the release of 1.12, I'm excited to announce that VSCodeVim now supports remappings from a .vimrc file! Special thanks go to @rdnlsmith and @Sheepolution for their great work on this. To get started, set Please note that other settings, plugins, etc. are still not supported via .vimrc. In addition, this feature shouldn't be considered 100% stable, so please test it out and submit issues with any feedback you have! |
@J-Fields Do we have some examples of what we currently support? |
It looks that inoremap doesn't work, while imap and nnoremap are fine. |
- Implement unmap and mapclear commands from vimrc with all possible values - Update the mapping regex to include all possible values (except the ones specific for SelectMode and TerminalMode) - Create tests for the new implementations (Refs VSCodeVim#463 )
Does this support EDIT: It turns out that you must set the leader key in VSCode's settings, not just in your .vimrc |
Currently only the remaps are read from the .vimrc. Everything else needs to be set in vscode settings. |
This is a pretty massive change; see pull request #4735 for full details Most notably: - Support for operator-pending mode, including remaps and a half-cursor decoration - Correct handling of ambiguous remaps with timeout - Correct handling of recursive special case when the RHS starts with the LHS - Correct handling of multi-key remaps in insert mode - Failed movements that occur partway through a remap stop & discard the rest of the remap - Implement `unmap` and `mapclear` in .vimrc Refs #463, refs #4908 Fixes #1261, fixes #1398, fixes #1579, fixes #1821, fixes #1835 Fixes #1870, fixes #1883, fixes #2041, fixes #2234, fixes #2466 Fixes #2897, fixes #2955, fixes #2975, fixes #3082, fixes #3086 Fixes #3171, fixes #3373, fixes #3413, fixes #3742, fixes #3768 Fixes #3988, fixes #4057, fixes #4118, fixes #4236, fixes #4353 Fixes #4464, fixes #4530, fixes #4532, fixes #4563, fixes #4674 Fixes #4756, fixes #4883, fixes #4928, fixes #4991, fixes #5016 Fixes #5057, fixes #5067, fixes #5084, fixes #5125
Just my 2 cents, but as a long time vim user often with intellij this not being figured out is my number one reason why I haven't more seriously considered switching to vscode for a while now. Don't really want to learn vscodes unique syntax for how to set up settings.json for my vimrc file. |
EDIT: Looks like I spoke too soon and this is actually working, modulo a bug! |
jetbrains can read .vimrc just fine, hope vscode can do the same some day. |
I'm not sure if it's considered or untrivial, but I enjoy how jetbrains just swallows my vimrc and am not annoyed by the silent failures (basically it reads and supports what it can). It still works even after refactoring my vimrc into subfolders (few years ago) and just "plugged" from my main vimrc I'm excited to see active development on this. |
The VSCodeVim team prioritizes issues based on reaction count.
Support an actual .vimrc file alongside our current settings.json.
Allow users to specify a location for the .vimrc insite the settings.json file.
Support basic .vimrc commands.
The text was updated successfully, but these errors were encountered: