No. I'll keep using vim, because I'm efficient in it and I enjoy using it.
Just Use Sublime Text
31–40 of 112 posts
Re: Just Use Sublime Text
#32noobs.
Re: Just Use Sublime Text
#33I sort of, but very reluctantly, agree. I would add that modern VIm package systems like SPF13 make it much easier and more accessible, I'd suggest the author check that out instead of continuing to maintain that 700 like vimrc file. That having been said, I still end up fixing a lot of bugs that crop up even with my SPF13 setup (the bright side is I can now contribute those fixes back to a project so others don't ne…
> 1. Split management that is easy to work with.
Command-K, Command-Up to do open a new vertical split pane in Sublime with the current file.
Command-K, Command-Down to close the pane and move the file back, or just Option-Command-1 to switch everything back to a single column no matter how many were open.
Re: Just Use Sublime Text
#34Yikes. I've been trying to use vim without plugins for 15 years. I'm glad somebody told me it's unusable, otherwise I may not have noticed.
Re: Just Use Sublime Text
#35I don't use Sublime Text because it's not free software and it doesn't run in a terminal. I like vim, but I'm not "stuck in my ways" and would gladly switch to a better editor that meets those two requirements.
Then just use Kate or Geany. I love Kate. It even has a vim mode!
Re: Just Use Sublime Text
#36Refreshing to see this after all the Vim gospel programmers out there claiming it's benefits. I do have to say though, I've seen some videos of real Vim pros at work and it's -majestic- how swiftly they move through lines and duplicating lines, editing params, refactoring, etc - a thing of beauty akin to watching videos on /r/artisanvideos[0]. I'll stick to Sublime Text and Nano when I need some ssh terminal editing.…
Our industry works this way and I don't understand why programmers who are always "using the right tool" call anything new that they disagree with "gospel" or "evangelizing." SublimeText isn't that old. Somehow you found out about it, learned its keyboard shortcuts, found out what plugins to install to do your work, and made it your editor. That's how I learned Vim. I'll admit that I have a bias, and that learning to…
The issue, really, is that vim is stuck in terminal land. It can't have easily navigable GUI menus, it can't really have overlays, it can't have a minimap, it can't have differently sized text, it can't have all sorts of things as a result of its dependence on the terminal. It doesn't even have autocomplete for its commands, at least out of the box, which would make it significantly more usable without disappearing into help files every time I want to do something I don't do often.
Add on to that its awful configuration language and the fact that it's not really usable out of the box unlike Sublime Text, it's easy to see why some people consider it unmodern and, for them, inferior.
Re: Just Use Sublime Text
#37I really want to like sublime but the rules around its extensibility are too rigid: you can't change the UI.
As a Vim user I feel like we are all just waiting for either Atom to become fast or for NeoVim mature.
Re: Just Use Sublime Text
#38"Everyone talks about the steep learning curve but no one talks about what happens once you finally get hjkl in your brain for movement. The answer is months of frustration, followed by finally having a usable editor, followed by knowing some cool tricks that you use in 1% of your daily workflow." I've seen a lot of people saying this. I've met people who actually experienced this. And I can't listen to it anymore -…
For example, if you can't get used to, or you're not productive with h j k l keys for movement, just don't use them. I don't use them. I use arrow keys all the time. Vim "masters" will probably judge me because of this - cause it's not the "Vim way". So what? I don't care. Arrow keys work for me the best, and I'm happy with it.
I started using elvis and vim somewhere in the nineties and used the cursor keys until ~five years ago. I like hjkl more now, since I don't have to leave the home row and the cursor keys are awkward on Macs, but there is indeed nothing wrong with using the cursor keys if it's more convenient.
My approach to learning vim has been the following: start using it as any text editor until you are comfortable. Then take O'Reilly's vim pocket reference. Look for a command/movement that you think would increase your productivity. Try to integrate that command (and only that command) in your workflow. If you believe after a week that it indeed improves your workflow and enters your muscle memory, keep it, otherwise drop it.
Repeat this for some month, and you'll quickly learn the commands that increase your productivity the most.
Re: Just Use Sublime Text
#39I think many of these comments are failing to mention one of my primary reasons for using vim... the power of being able to use the same editor in a GUI and a shell. It takes me at least a day to setup my workstation for development but if my laptop crashes I can always SSH into my workstation VPS and get work done. It's also nice to be able to edit server configuration files with the same editor that I write code in.
Vim isn't for everyone but if you're a power user that wants to master one text editor and use it for the rest of your life then Vim is that text editor.
Re: Just Use Sublime Text
#40Read 2 books to use Vim?
Seriously, w.t.f?
Just give it 2 weeks using Vim.