![]() ![]() ST3 works nicely on my Debian (Sid) machine running dev-version, but I’m eagerly awaiting ST4 to continue supporting it. NeoVintageous should make my Sublime experience better, not try to make it the other way around. Moreover, I plan to use rstmarkup for all my writings and found everything is (still) there. Sublime Text - enabling vintage - YouTube 0:00 / 15:03 Intro Sublime Text - enabling vintage budlabs 3.52K subscribers Subscribe 15 1. Installed Anaconda, jinja2, tailwind…plugins so I can work with python-powered static-site generator ( Nikola. Vintage Mode lets you to use a list of vi commands in the Sublime editor. However I simply do not like JS-stuff and having license for ST3 wanted to give it another try. Vintage mode in Sublime text editor is a package that includes a combination of editing features of vi. Same here…After abandoning Emacs and desire to settle on (neo)vim and having problems with Actualvim, I wanted to settle on plain (neo)vim, but then tried VSCode in order to minimize need for fiddling with (neo)vim plugins. NeoVintageous has gotten so much better I’m now back to Sublime (for the most part). Neither one of them replicate Vim or its configurability perfectly or as well as evil-mode, but I’m kinda glad they don’t. I have all the built in editor power, functionality, and commands with both NeoVintageous and VSCode Vim. The best ones accentuate the native program experience, they don’t try to replace or conceal them. The ActualVim issues raises an important point with Vim emulators. SublimeSix - Knowing that Vim emulators are often more sketchy than useful (holy crap the one for XCode is a disaster I can’t imagine anyone thinking it “works”) I can’t see myself paying for one. However, no auto-complete or snippet pop ups, and no multiple cursor support? Ummm… no thank you. This means you can use your vimrc, which means you can use some of the Vim plugins. It uses the real NeoVim instead of trying to recreate Vim. Vintage - If all you want to do is navigate around the page, it’s ok, but NeoVintageous does it and much more.ĪctualVim - I had high hopes for this. They both still have issues (and maybe NeoVintageous even has a few more), but they don’t get in the way of what you’re wanting to do. I know you didn’t ask how it compares to VSCode Vim, but I think their quality is similar enough to mention them both in the same vein. I can’t express just how much more awesome it is to configure Vim bindings in a format that’s so close to my vimrc than in json. One thing that edges NeoVintageous past VSCode Vim is the neovintageousrc file. They’re not as complete as evil-mode in Emacs, but they’re completely useable. As far as feature compatibility with Vim, I’d say they’re about the same. Working with them was a constant stream of frustration where I was thinking about the problems with the emulators more than the code I was writing. ![]() I was coming from Vim and all of Sublime’s emulators were far too basic and buggy for me to tolerate. VSCode’s Vim emulator was the reason I left Sublime. ![]()
0 Comments
Leave a Reply. |