71–80 of 117 posts
Earlier quoted context omitted.
I don't think the initial difficulty of Vi is that much greater than that of Emacs. The real difficulty is in the fact that everything is completely different from what you are used to; perhaps this is more true in Vi, but the difference between Emacs and Vi in this regard pales in comparison to the difference between using a mouse and arrow keys and either of the text editors. Also, while my approach will certainly…
I use VIM and sometimes use the arrow keys. These come in really handy when you have a lot of small edits to make that can't be readily automated (not really that frequent). However the huge shift in mentality has to go from the idea that you are working with a "text editor" (which VIM and EMACS are not IMHO) and a text processor which I would argue these are. When you start thinking about processing rather than edit…
Time to remap that one too.
Earlier quoted context omitted.
What about changing hjkl movements to jkl;? I didn't try it yet... But hjkl bothers me. My index belongs on j, for homerow touch typing, not h. Wouldn't it be an improvement? Not having to move the hand for movements. I must be missing something because everyone stays with hjkl.
I'm much faster in vim since I gave up (for the most part) on hjkl (arrow keys are banned for obvious badness). / ? # * combined with f and t are so much faster. The only time I use j/k is 10j/10k for looking through files. Hence, your question is somewhat misguided ;)
Unless you mean you specifically use search for every motion...?
Earlier quoted context omitted.
I don't think the initial difficulty of Vi is that much greater than that of Emacs. The real difficulty is in the fact that everything is completely different from what you are used to; perhaps this is more true in Vi, but the difference between Emacs and Vi in this regard pales in comparison to the difference between using a mouse and arrow keys and either of the text editors. Also, while my approach will certainly…
I use VIM and sometimes use the arrow keys. These come in really handy when you have a lot of small edits to make that can't be readily automated (not really that frequent). However the huge shift in mentality has to go from the idea that you are working with a "text editor" (which VIM and EMACS are not IMHO) and a text processor which I would argue these are. When you start thinking about processing rather than edit…
As someone said, when programming typing isn't my bottleneck, thinking is.
Full touch-typing speed is a must for court clerks -- not for programmers, and also not even for writers.
"vim has two main modes, normal mode ... and the insert mode" i stopped reading here because i knew what was coming next. the omen was fulfilled by the next line: "in insert mode, now you type text as your normally would. Pressing exits back to normal mode." its command mode vs insert mode. any vi user should know that.. it's the very first thing vi bludgeons you with.
"vim has two main modes, normal mode ... and the insert mode" i stopped reading here because i knew what was coming next. the omen was fulfilled by the next line: "in insert mode, now you type text as your normally would. Pressing exits back to normal mode." its command mode vs insert mode. any vi user should know that.. it's the very first thing vi bludgeons you with.
Not really sure why the hate for nerdtree. "Don’t use the NERD tree plugin. It is clumsy, will hurt your workflow with split windows, and it’s not particulary pretty either. You never needed a file browser pane in the first place." "It is clumsy" We're talking about VIM, with dozens of keystrokes to invoke everything but emacs already. The whole thing is a bit clumsy! I use it every day and have for a decade but it's…
I'm not a VIM purist. I use the arrow keys, and I use the mouse a lot. I find NERDTree to be tremendously easy to use and helpful when on a local system.
On remote systems, though, I generally just edit 1 file at a time and don't need NERDTree. For multiple files, :e works just fine in those situations.
I've been using Vim more or less exclusively for the last year or so, and there is only one feature of Aptana Studio that I miss, and have not been able to find in any Vim plugins. In the directory/project tree in Aptana, files had different styles based on their git status. I think I just need to take a weekend and learn enough vim programming to make it happen as a Nerd Tree plugin.
Check out Steve Losh's Learn Vimscript the Hard Way[1].