All good suggestions ! Unfortunately I don't use the mouse with Vim except in a few odd cases.
Interesting. Its probably my compromise with the ui.
If they DID, I would probably use Ctrl-1 .. Ctrl-3 as a quick way to switch between buffer 1, 2, 3. (or the 3 current open files)
That is a good idea. :rew, ^, :wn is about the limit I could find to get close to that.
The problem is once you have more then 3+ bookmarks it becomes hard to remember "where" each bookmark takes you.
I see what you mean. My approach maybe odd, I use conceptual references. So 'D or some other letter might be an abstract of something and the lowercase 'd maybe a concrete implementation. other odd games too help.
Generally when I code though I try to limit the size of the files I create.
See which one is easier to remember? I no longer have to play the guessing game of "Where is bookmark X located again?"
You're right - it's a pita.
I think that's where I get the GUI to take over. Generally a combination of screens, workspaces, bash/vim terminal sessions, IDE. 4-8 workspaces and in my set up the terminal tabs hotkey with Alt-1 Alt-n. That generally gets me huge task bandwidth, about 4-400 vim/bash sessions per workspace.
Also I use workspaces named that define tasks in layers, so on my DAW for example I have Mix-Master-Monitor-subsystem, for code I generally use UI-Domain-Persist-DB and just increment whatever needs expansion. That's my workflow management, you probably have different challenges.
I think there maybe a way for you though, maybe multiple vims open on a single file - whaaaa? I hear you say. Well I think the new messaging part of vim may provide a way for multi-vim sessions on a single file by passing messages (which can be edits) between each other. I'm not sure yet (I still have a fair bit of recovery and exercise in from of me) but this could be a possible use-case that this new feature *might* support if you wanted to check it out.
The curiosity is killing me, as soon as I get a chance to figure out how this works I'm going to have to try it on something. Generally I just rack my brains making new regexs. I clearly am still learning vim!
(At the time we worked on a C++ compiler but that's another story.)
In the process of understanding Vim I tore into the source code and literally made a map of what EVERY key does in Vim.
Cool. I've probably been using vim longer than you, actually, it was vi for a long time on sco, sun, hp. But ripping into the source code to learn it is pretty hard core. I'm certain you've gone beyond me with it.
Damn man, that's awsome work. I doubt I know how to use vim as well as you do. I'll be laminating a copy of this for my wall - my colleague will want one as well, he only just got hooked on vim about a year or two ago.
That's really the best functional breakdown of vim I've seen and I'll spend some time studying it. Thank you for doing that.
Vim felt like an extension of my mind !
Obviously, this reply was constructed with vim - it's great for getting thoughts collated pre post.
I posit this is because Vi (and Vim) was designed by a programmer for a programmer. Every key feels like it belongs there. There is no wasted key. Sure Vim's learning curve is like a vertical cliff, but man, what a view from the plateau ! You'll never view another editor the same way one you've seen and tasted the power of Vim.
Absolutely! I suspect it maybe some time before we get everything out of the new features, and I'll probably be trying to figure out what I am missing with vim from your work - thanks.