Thursday, July 7, 2011

Re: Announcing ri.vim interactive ri mode for Vim

On Thu, Jul 7, 2011 at 2:55 PM, Daniel Choi <dhchoi@gmail.com> wrote:
>
> I published a new Vim plugin / Ruby gem, ri.vim. It's an interactive
> ri mode for Vim. ri is the command line documentation printer for
> Ruby.
>
> http://danielchoi.com/software/ri_vim.html
>
> Beta-tester feedback would be great. Many thanks,

I would personally love to see nice ri integration, so thanks for
working on this.

Quick observations:

1. Installation

Requiring installation via Rubygems, then via `ri_vim_install' is
not very nice; if you look at Command-T, you'll see that the project
is laid out as a Vim plugin first, then as a ruby library, allowing
installation by extracting a tarball into a vim directory of your
choice.

That's the other problem; many vim users use Pathogen and the
like, and so wouldn't want to install to ~/.vim/plugin, which is
currently hard-coded.

2. Interface

It would be really nice if the `K' command didn't just work in the
ri buffer, but also in buffers with ft=ruby.

When you type in `inspect' in the ri buffer, you get `No matches!',
while `ri inspect' dutifully returns every match from every class
that explicitly defines #inspect. This seems like a good opportunity
to present a menu list.

The <Leader>r shortcut should be configurable.

3. Window handling

If your first ri search returns no matches, you are returned to the
original buffer with a horizontal split, when there should be none
at all.

The autoclosing behavior of the ri search window is confusing; I can
leave Insert mode by pressing Esc or Ctrl-C, and close the window
in Normal mode by pressing Esc, but not Ctrl-C. I think it might
be nice to never be able to leave insert mode (except for Ctrl-O
sequences).

Invoking <Leader>r while in the ri search window opens a new,
duplicate instance of the search window.


Those are my impressions after a few minutes of use. Hope that helps,
and I am looking forward to the evolution of this plugin!

Cheers,
guns

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

No comments: