Tim Pope

> @tpope There's a real UX issue hidden behind this issue, and that is if you have the Gstatus open, you press enter, you go to the file to review...

Oversight on my part. Don't let that stop you from looking in the doc directory. Action plan: steal the boilerplate from [dispatch.vim](/tpope/vim-dispatch), and use the description on vim.org for the...

First things first, I highly recommend using `origin/master` as your upstream, and setting `push.default` to current. This will give you an additional 2 sections based on your relation to `origin/master`...

The initial implementation is not the bottleneck, but if you wanna start prototyping and get a feel for what works and what doesn't, have at it. Shouldn't be much more...

What kind of Vim? On Tue, Apr 16, 2013 at 12:44 PM, fintelkai [email protected]: > I would love to figure out how to disable the mapping, so I can >...

You can `iunmap` in `after/plugin/rsi.vim`. Having an option to disable the meta maps wouldn't be a terrible idea.

To be more explicit, I'd accept a `g:rsi_no_meta` patch.

It's working as designed. I'm guessing changing it to add this special case would be pretty hard, and I'm not even sure it would be universally applicable?

I'm leaning towards doing `:echo "Binary file"` on attempting to expand, as I find putting stuff after the file name makes it a bit (just a bit) harder to scan.

You can do `inoremap ` now to preserve any built-in and prevent RSI from mapping it. This solves the readline.vim use case too.