[Vimperator] help with resetting my firefox

[Martin Stubenschrott]

On Fri, Jan 18, 2008 at 08:12:42AM -0800, Hari Krishna Dara wrote:
> Do you mean, installing firefox 3 might reset the relevant settings? I
> am not sure but it might work, however I don't know if all my add-ons
> are already supported in 3 and it might have other problems of its
> own.

I don't think that FF3 will reset the settings. He meant, when you
install firefox, and vimperator 0.6pre in it, the problem might go away
(or it might not, just guessing).

But even if you don't have a backup, try to start with a clean profile
and see if there is a problem (you can create as many profiles as you
want in parallel with firefox -P)

> I am noticing in general that uninstallation of vimperator is not
> clean. E.g., for me after the uninstall, <Esc> no longer works
> properly in the address bar. Normally when I press <Esc> after typing
> something new in address bar, the previous address gets restored, but
> this is no longer working. I searched in the forums for "uninstall",
> in case the cleanliness of the uninstall was ever discussed and I
> didn't find any.

Strange, after an uninstall (and restart), that should really be back to
normal.

> I am thinking my original problem is stemming from the fact that
> vimperator tries to modify the status bar such that it looks like the
> Vim status bar and in addition *creates* space underneath for the
> purpose of displaying the command-line string. I am thinking that
> whatever the setting that vimperator tinkers with (e.g., the amount of
> space that needs to be reserved for the command-line) is what is
> messed up and if I can get some hints on where to find it it would be
> helpful. Of course, the author of this addon would be the best person
> to know how this works, but any help from anyone would be appreciated.

You are right, that vimperator modifies the statusbar, so *some*
extensions which rely on that *might* have problems. Also the space
below the statusbar actually is a normal textbox. but some extension
might not expect that, causing a problem.

--
Martin (the author)