I made a vector version of the vim logo a while back. I proposed to MacVim that they use it but they didn't seem interested. I since it was vector, it is easy to modify. So I made a blue version. I have been using it for VimR since I first downloaded it.

Here is the .icns file incase you want to use it.

Thanks for the app. It is very cool!

I really like how the quickopen has ctrl+p/n to move up and down the results. That's consistent with Mac OS (try searching for a file in finder - ctrlp/n moves up and down the results). But it would be nice to use keymappings in the file explorer that resemble vim (and maybe a bit of NERDTree influence).

• j/k to move up and down the file tree.
• l (or o) to open a directory.
• <cr> to open a file (not a directory). (Same modifier scheme as quick open perhaps).
• Some shortcut to shift focus. between the editor and the file explorer.

I'm sure you'd love to allow customization of the keymappings, but some reasonable defaults would make the file explorer ready for serious use in day-day work until keyboard mappings are implemented.

It would be great to have some option to hide the status bar below.

copy, cut, paste

#14 only did it for the file browser (and open quickly window with the mouse, not with CR)

I tried my .vimrc setup which has normal and normal<Shift+Space> mapped to tabn/tabprev respectively. It seems shift+Space doesn't work in VimR.

(Admittedly low priority).

Just an enhancement I would love to see on Vimr...
I really like to have folders first when I'm browsing file (just like github does), and I think an option would find its place in preferences.

Hi,

I really like the idea behind vimr. I was wondering if it wouldn't be easier to play with neovim and create an UI on top of it, rather than fiddling with MacVim.

I'm not an expert, so I don't know if this is feasible/convenient. What do you think?

I accidentally find this bug, when I was opening/closing multiple times in a row the sidebar.
In the beginning the windows is some pixel smaller but after the windows' size is divided by 2.

Ok, not a bug bug as I don't often show/hide the sidebar, but worth tell you I guess.

How do I do that? The canonical ⇧⌘[ and ⇧⌘] doesn't seem to work.

make it work first, then prettify it...

to a certain degree... and write more tests...

Is there a preference to stop Open Quickly putting files in new tabs?

I noticed that Vimr may be leaving behind processes after quitting. I opened up several tabs via the Quick Open and then when cmd+qing the app, something from Vimr was getting left behind.

• Launch VimR
• modify any buffer
• Cmd-Q
• You are not asked whether to save the unmodified buffer

This is just something longer term to consider, to keep in mind.

There's some good options for allowing configurability of the windowing environment. That means people can script their own plugins to script the UI that don't do a lot of interaction with the main editing view. (The main editing view will likely need to be a different scripting/plugin API/paradigm for the foreseeable future until NeoVim is done).

• Clojurescript
  -- Pros: There already exists a clojurescript to VimL compiler so you could write the same language for regular vim plugins and VimR UI plugins.
  -- Cons: Not as popular as JS.
• JavaScript
  -- Pros: Easy to embed. Supported on Mac OS out of the box. Everyone knows it at least a little bit. Hugely popular language.
  -- Cons: Different language than scripts written for standard Vim plugins. (But someone could make a JS -> VimL compiler much like we have for clojurescript).

The upside of having an entirely different scripting environment for window/UI management is that it's so much easier to start from scratch and the tasks are usually pretty separate from the core editing experience. The downside is that it's removed from the standard Vim scripting environment so orchestrating between the two will be tougher - maybe a blessing in disguise though.

Looks like some really exciting stuff is happening in the side-bar branch. Any chance you could upload prebuilt binaries for that work?

The Vico project is a really, really excellent editor. There's so many good things to say about it (awesome scripting language, beautiful dialogs/navigation, truly faithful Vim mode) - those engineers are awesome for doing what they did. Vimr's approach is to allow you to use all of the same Vim plugins/colors/integrations that you already have, but has the goal of adding a beautiful experience on top of it. Would you consider repurposing some of Vico's UI elements for the left nav and project find? I think they're spectacularly done (serious compliments to the developers who built and maintain it). There's a ton of code in there for configuring the keyboard mappings for UI elements which is done in an obscure language (but a good language) so I don't know how much of that could be reused, but at least a lot of the code for fetching files and displaying them/searching them could be used.

Thoughts?

It would be good to have some simple instructions on how to use a master build of MacVimFramework in the README.

instead of ⌘ use ⌃⌥

• enter = open in a new tab
• modifier1 + enter = open in a horizontal split
• modifier2 + enter = open in a vertical split

Instead of index all /~, Open Quickly should start at pwd.

I really like MacVim's fullscreen support. Can we still achieve it while using MacVim framework? It's great how MacVim lets you bypass Mac OS X's extremely long full screen animation. How could anyone get work done while waiting that long for an animation!

The application loads, but I cannot open any windows.