[Vimperator] un[let]

Martin Stubenschrott stubenschrott at gmx.net
Tue Sep 18 13:52:32 PDT 2007


On Tue, Sep 18, 2007 at 11:29:46PM +0300, Виктор Кожухаров wrote:
> I considered that, but I wasn't sure whether it could handle shorthand
> option names (I tested it and I think the answer was a no here). 

Right.

> for now eval is used to evaluate a simple expression. currently, it can
> eval strings ("fofo", 'bar', "foo\"aaa\"", etc), numbers (1,2, etc),
> variables (foobar, g:foobar), and options (&guioptions). It is mainly
> used by let to evaluate the right hand side of the assignment. But it
> can (and I'm planning on doing this soon) be used with the 'echo'
> command, for a more vim-ish echo, other vim commands most likely use it
> too.

Great, that was on the todo list anyway to have such a kind of :echo
I think we even should check for type == object, and then do echo the
vimperator.logObject'ized string. Now with a well working multiline
output widget this could look really cool, and help a lot when
developing.

> variableReference obtains a reference (pointer) for a variable. imho it
> shouldn't be called getVariable, since it gets a reference to it. This
> allows for the modification of the variable, as well as obtaining it's
> value.

Ok, right.

> Already committed. It should be rather trivial now to replace the
> <Leader> string in a lhs map assignment with the string contained within
> mapleader (or '/' if mapleader hans't been defined yet).

You mean '\' i suppose ;)

Do you also have a patch for <Leader> in the works, as i am quite busy
with other (vimperator- and non-vimperator) things right now?

Thanks for the patch, btw.

--
Martin


More information about the Vimperator mailing list