home | changes | index | login
WareLogging. Also MozillaProfileInUseBug, MozillaFirefox. ThingsWhichSuck.
<Brennen> This may be fixed in recent iterations, but most of the Mozilla versions I've used contain an ugly little bug whereby a lock file (stored I think in ~/.mozilla/profilename/XXXXXXXX.slt/lock) will be left in place after a crash, which leaves Mozilla assuming the given profile is in use. The only time the whole "profiles" concept has ever impacted my use of Mozilla is via this bug, which leads me to suspect that it's not that necessary a thing. It's at least redundant on a multiuser system.
<Brennen> I guess that is the obvious one. Maybe it could be the basis for a little pr0n/non-work mode toggle bound to a key combo. Tighten up the popup blocking as much as possible & throw in a quick switch to a cached version of some innocuous page every time you drop out of it.
<alan> so i was compiling firefox today (whilst clean installing FreeBSD 6.0) and i happened to see a modules/libpr0n directory in the src tree. looks like its just a shed for image decoders...a legacy name i guess? maybe not so legacy :)
anyway, i'm sitting around waiting for this thing to compile only because, at some point, i got a hosed firefox under FreeBSD 5.0 and in this magical web 2.0 age a browserless laptop is, you know, so unhip. the first thing i checked of course was the profile lock bug you mention here. i was able to gdb my way down to a mutex deadlock probably involving gconfd but that's as far as i got before i peed in my pants. repeatedly. really, i'd like to avoid this sort of embarassment. i wish i could toss firefox out entirely, but lynx (which i'm using to write this) is just too damn annoying.
recently i've started thinking a www vim plugin might be more tolerable. yeah, i know about lynx's vim key bindings. they leave a lot to be desired though. vim63/plugin/explorer.vim has some good ideas. you could use html2text to render the pages to the buffer, and turn links into vim tags like what you find in the help system. not sure how you'd handle inputs and textareas.
<Brennen> If you want a quasi-vim web browser, what about w3m? The rendering is fairly modern & the keybindings are mostly vim with some influence (I think) from mutt. Text input handling is primitive, but more robust than Lynx - uses vim as an external editor for textareas, does line inputs for everything else. This is probably what I'd use to render pages if I were going to do an in-vim browser.
There's already pretty good basic hypertext stuff in vim; you can easily navigate a flat wiki namespace like this one with just builtin commands... All the tools are here to become a vim-specific version of Shane, the CoffeeHouse guy with his life in Emacs.
Links is mostly a better Lynx than Lynx these days. With a fairly unfortunate name.
pick a name (required to comment or edit a page)
last edited January 11, 2006