Live data from Hacker News

Switching to Sublime Text from Vim in 2017

eduardobautista.com

31–40 of 71 posts

Re: Switching to Sublime Text from Vim in 2017

#31
I hate these types of posts...

"Why I'm no longer using vim and now using X" typically result from not digging into Vim enough. All the issues the OP is having have been resolved from either updates to vim, switching terminals, or just understanding vim basics.

NOTE: Plugs can be slow and the OP is correct that some are hacky, but typically there's the Vanilla Vim solution to a problem that takes a little bit of reading and/or finding to solve.

If plugin/loading speed is really an issue then switch to using Alacritty and Neovim, use vim-plug for async & lazy loading plugins. You get truecolor support and you're using your GPU to render everything. If plugin speed is still a problem, learn why they're loading slowly, then dig into why rather than just saying "they're hacky or clunky". Silver search is great, but if you understand how to execute terminal commands from vim (:!) then you can grep everything and remove the need for silver search. I use FZF (https://github.com/junegunn/fzf) which is another fuzzy searcher that's optimized for speed, built with Go.

For those that don't want to put in the time to optimize and learn vim, then by all means switch editors. But don't blame the editor ("I will not use shitty software just because it’s open source.") unless it's truly the root of the problems, explore and find better ways. A key thing to remember as a Vim user is there's always a faster way and your .vimrc will always be different from another's.

Edit: For those interested in my setup (https://github.com/hhsnopek/dotfiles/blob/master/.nvimrc)

Re: Switching to Sublime Text from Vim in 2017

#33

I only have two comments: > Any popular editor usually has a “Vim mode” that you can install and you can achieve native Vim productivity. I would editorialize this to say "closish to native vim productivity", since there are virtually no vim mode plugins for popular editors which offer a complete set of vim features. Even EVIL mode (as of the last time I checked it) has a few notable discrepancies which arise from ma…

I have never considered moving though, because although the other editors may emulate vim itself pretty closely, I highly doubt that the vim econsystem of plugins which I'm used to (my particular flavoring of keyboard-only window management, autocomplete, file tree navigation, searchability, etc) would be portable over. Vim is more than just hitting j to go down a line and ce to replace a word to me.

At the absolute minimum I need a port or something very, very similar to NERDTree and vim-easymotion in the new environment.

Re: Switching to Sublime Text from Vim in 2017

#34

I hate these types of posts... "Why I'm no longer using vim and now using X" typically result from not digging into Vim enough. All the issues the OP is having have been resolved from either updates to vim, switching terminals, or just understanding vim basics. NOTE: Plugs can be slow and the OP is correct that some are hacky, but typically there's the Vanilla Vim solution to a problem that takes a little bit of read…

> If plugin/loading speed is really an issue then switch to using Alacritty and Neovim, use vim-plug for async & lazy loading plugins.

I already do.

> Silver search is great, but if you understand how to execute terminal commands from vim (:!) then you can grep everything and remove the need for silver search

I used that for CtrlP and in my experience returned better results. I know how to use grep and I use it frequently outside of Vim.

Re: Switching to Sublime Text from Vim in 2017

#35

I only have two comments: > Any popular editor usually has a “Vim mode” that you can install and you can achieve native Vim productivity. I would editorialize this to say "closish to native vim productivity", since there are virtually no vim mode plugins for popular editors which offer a complete set of vim features. Even EVIL mode (as of the last time I checked it) has a few notable discrepancies which arise from ma…

I think a lot of us can agree with the last bit, but that said VS Code is actually pretty darn nice.

Do you know how to remove 5 stupid menus on the left; explorer, search, git, debug, and extension.

I don't agree with all these as default.

Explorer (basically the nav tree): Just give me a toggle key and hide it by default please (I mean hide its icon nav too)

Search: really? something + F is fine for short key like the others do.

Git: I haven't even tried to use version control inside text editor. It is just illusion of ease. It's not significantly different from switching to a terminal. A terminal has its jobs to do, please use it. You will use it anyway for other tasks.

Extension: This is even worse to be default. I don't think I have something to frequently do with extensions.

I like its light computation compared to Atom. I had switched to VS Code for a while, then switched back to Atom. Maybe I'm just lazy to remember new keys.

Edit:: Just found it, "Hide activity bar". Sorry for being lazy :/

Re: Switching to Sublime Text from Vim in 2017

#37

I hate these types of posts... "Why I'm no longer using vim and now using X" typically result from not digging into Vim enough. All the issues the OP is having have been resolved from either updates to vim, switching terminals, or just understanding vim basics. NOTE: Plugs can be slow and the OP is correct that some are hacky, but typically there's the Vanilla Vim solution to a problem that takes a little bit of read…

> If plugin/loading speed is really an issue then switch to using Alacritty and Neovim, use vim-plug for async & lazy loading plugins. I already do. > Silver search is great, but if you understand how to execute terminal commands from vim (:!) then you can grep everything and remove the need for silver search I used that for CtrlP and in my experience returned better results. I know how to use grep and I use it frequ…

CtrlP has okay results, the best is to perform your own search and do a reverse grep match on files you want to exclude.

If you were already using Alacritty and Neovim, you should expand on why these did not solve your problems as many if not all speed/optimizations can be matched or better than Sublime Text

Re: Switching to Sublime Text from Vim in 2017

#38

I would recommend vim-easymotion and command-t for a big speed improvement over relativenumbers and CtrlP. In my experience Sublime is _much_ slower than Vim.

I'd recommend fzf over CtrlP and Command-T. It is incredibly quick and extremely reliable. Reason why it's so fast: not really a vim plugin, fzf is just a wrapper to an external fzf command.

Once installed, you'll also get shell extensions in bash/zsh also as a bonus (fuzzy auto-completion, fuzzy command history with Ctrl-R).

https://github.com/junegunn/fzf

Re: Switching to Sublime Text from Vim in 2017

#39

I hate these types of posts... "Why I'm no longer using vim and now using X" typically result from not digging into Vim enough. All the issues the OP is having have been resolved from either updates to vim, switching terminals, or just understanding vim basics. NOTE: Plugs can be slow and the OP is correct that some are hacky, but typically there's the Vanilla Vim solution to a problem that takes a little bit of read…

I will blame whoever I want.

Re: Switching to Sublime Text from Vim in 2017

#40
post #22

To go to the reverse route, I'm a SublimeText and Vim user that's debating going back to pure vim. Much of the functionality that I used ST for I found Vim could do naturally, with no plugins. This presentation taught me alot ( https://www.youtube.com/watch?v=3TX3kV3TICU ), such as basic command completion. There is some stuff that Sublime can still do that I don't think Vim can (multi-cursor editing comes to mind, a…

> There is some stuff that Sublime can still do that I don't think Vim can (multi-cursor editing comes to mind, and that's still really handy when I'm making edits to HTML) […]. https://github.com/terryma/vim-multiple-cursors I use this with NeoVim and it works perfectly.

Good to know! Although based on my scenario above, I'd prefer to keep it to vanilla vim, at least until I feel I've mastered it. I thought I had at least a moderate understanding, but 20 minutes of 'vim' searches on youtube demonstrates that the rabbit hole goes far deeper than I could have imagined.
Post reply on HN