VimR – Refined Vim Experience for OS X
51–60 of 69 posts
Re: VimR – Refined Vim Experience for OS X
#52Re: VimR – Refined Vim Experience for OS X
#53I love this idea! I've wanted to get into MacVIM but I am just too addicted to the file browser sidebar that Sublime and Atom have. I'll have to give this a shot.
Re: VimR – Refined Vim Experience for OS X
#54Re: VimR – Refined Vim Experience for OS X
#55Earlier quoted context omitted.
Thanks for the feedback! ⌘1 is what you want to focus the sidebar, and will take you back to your buffer. We're working on some improvements to the View menu.
That works! Thanks! Looking forward to the next round of improvements.
Re: VimR – Refined Vim Experience for OS X
#56I am missing a "Why should I use this instead of MacVim?" section on that website.
Re: VimR – Refined Vim Experience for OS X
#57As a MacVim user, I find this intriguing. It seems to work very well for my needs. I particularly like the built-in Markdown preview. My only gripe so far is that I'd like to be able to configure additional filtering for the fuzzy file find to, for example, make it automatically ignore node_modules folders.
Re: VimR – Refined Vim Experience for OS X
#58For those confused, this project uses a fork of macvim that the author himself turned into a framework(osx library) to be used in third party programs. [1] (Kinda how some linux projects used xembed to embed gvim into their apps, eclim also used to have a mode to embed gvim into eclipse) Think of it as a proof of concept implementation for a vim editor based on the macvim framework version. At worst, you don't really…
Re: VimR – Refined Vim Experience for OS X
#59Thank you for your comments. Please bear in mind that VimR is still very much work in progress: it's got still rough edges here and there. With your comments and feedback we will try to polish it and add new features. Stay tuned. :)
So, no problem, vim lets you remap your keys, which takes care of the problem. Many of us remap the "arrowkeys on the home row" to the standard inverted-T of ijkl (and remap i, for insert left, to h, reach left instead of reaching up), so that both sets of arrowkeys on the keyboard match each other and match their arrangement in every other app we use. Those with other keyboards, such as Dvorak, will often map to different keys that make more sense on their own keyboards. The ability to do so has always been one of the features of "real vi(m)".
I hope that for your file browser, you'll pass the keypresses through the (g)vimrc map, so that whatever keys a user has chosen for up, down, left, right, escape, and whatever else the file browser handles, will work the same way in both the editor and the file browser, which is to say, the way their "real vim" works.