I use Vim when editing code. It's been my favorite editor for a while. Anyone else here use Vim for game programming?
I use Vim when editing code. It's been my favorite editor for a while. Anyone else here use Vim for game programming?
I've used vim for about a decade, plan old vi for about a decade before that. Brain-dead editors like Wordstar and its progeny like Visual Studio pale in comparison. Where else can you do a quick ":%!sort -fu" to re-sort your .gitignore file to keep it in alphabetical order?
To be precise, I use gvim, one window per file, and use different colour schemes for different filetypes.
I use gvim with Buffers. I used to use Windows, but buffers work great for me. If I need to have two things open, then I still use windows.
Have you binded Ctrl+W (hjkl) to Ctrl+h, Ctrl+j, Ctrl+k, Ctrl+l? If you use windows a lot it saves you a lot of time. I'm thinking about binding Ctrl+H, Ctrl+J, Ctrl+K, Ctrl+L to Ctrl+W (HJKL).
Vim uses the "emacs philosophy" for it's windowed mode for some reason. I'm probably going to change Ctrl+W to my leader key.
I've found that over time, I rely less and less on quixotic tools and their exotic features. Sorting lines in a file is not a prominent feature of my software work... being flexible across platforms, machines, and configurations is. Whether it's VS, Eclipse, vim, emacs, or even cruder fare, I am perfectly capable of being highly productive. I am often surprised at how many things techie people think they absolutely need.
Apart from all of that, I maintain that vim is stupidly designed, albeit highly capable. Much prefer emacs when I'm living in that world, but vim is much more common and I often have no interest in adding more packages than needed. So I make do with vim. But the people who insist that working in vim is worlds apart from VS are a complete mystery to me. Parlor tricks aren't productivity.
It's a possibly interesting aside that I have no interest in swiss army knives/multitools, another random affectation of geeks.
I'm 41, not young by any means, but when it comes to tools, I hate the "old style stuff". I grew up with IDEs, and I find working with these archaic editors a total waste of my time. I don't want to spend 3 weeks trying to get vim or emacs or sublime text or atom to do the same things that Visual Studio, LiteIDE (the IDE I use for Go) and QT Creator do after 2 seconds I finish to install them.
I have no interest in writing makefiles, no interest in remembering the correct spelling of my functions or what the hell is the 4th parameters in an API call... when it comes to write code, I need all the help I can get from technology, cause what I do is already complicated enough, no need to shoot myself in the balls... and I am not willing to trade that for the chance to feel like the "cool dude" when it comes to write on the forums "I use Vim/Emacs".
.
Your post ( combined with other's )reminds me of the unwillingness to change - IE
" I did it this way for so long, why should I change ?"
It's perfectly fine to use whatever you you feel comfortable with - but when bringing something this awkward and outdated ...
The point is, while one person is still attempting to find 3rd party plugins and libraries for VIM, someone else already has a large chunk of an identical project up and running using a modern IDE.
As technology improves, so must the programmer - soon it could mean the difference between getting a job, or being kicked out of the industry .
This is what I have to deal with on my end of the "business" - there is no such thing as a "permanent job" - you are hired on for the duration of the project, than laid off and have to find another project.
You are hired based on your overall knowledge of both old, and new systems - and how much experience you have with them.
To make things more "fun", your boss has a computer generated time table on how long each stage of the project should take.
If you are too slow - yer' fired .
If you can't run the latest terminal communicators - yer fired.
If you can't write update code for a MUX that came out last year - yer fired.
If you can't write injection code for a 25 year old analog transmitter - yer fired.
If you are unable to figure out how to make manual or digital adjustments to anything you are assigned to - yer fired.