[Vimperator] Disable vimperator on some domains

[Martin Stubenschrott]

On Tue, Nov 13, 2007 at 03:53:08PM +0200, Viktor Kojouharov wrote:
> > autocommand TabSelect * function() { if (/gmail|othersite/.test(vimperator.buffer.URL)) vimperator.options.setLocal("disablekeys", true) }
> We could just skip the function() {} and eval what's inside.

right, good point.

> > I know it differs from vim's behavior which autocommand is an
> > ex-command, but since we lack control statements in our
> > vimperator-script language, we have to fall back to using javascript,
> > which makes the code of course more verbose.
> I thought vimperator-script will just be javascript inside the
> vimperator namespace?

Yes, if we find out, how to have the vimperator namespace default, but
still being able to call methods in window. - Is it just so easy to
change a this to vimperator?

> > However, as much as i would really like autocommands, they are non
> > trival, and will take at least some months, unless a really brave one
> > stands up :)
> > 
> I'd really love to tackle autocommands, but this lack of free time is
> really troublesome. And I doubt it would take a couple of months. 

Autocommands itself don't take months, probably 2 afternoons, but i meant, that
i will implement other things first and only find time for them in a few
months. Actually we could start with just 2 autocommands TabSelect and
LocationChange, and add more gradually.

BTW: Do you like the new Hints system, or what do you think could be
improved (assuming you know how they are supposed to be used).

--
Martin