[Info-vax] Newsreaders, was (long ago): Re: HP stopping VMS paper

[George Cook]

In article <085704d6-a18b-4f3b-acf6-d49516711a8a at o14g2000vbo.googlegroups.com>, AEF <spamsink2001 at yahoo.com> writes:
> On Dec 29, 12:08=A0pm, VAXman-  @SendSpamHere.ORG wrote:
>> In article <jdhmvt$dd... at news.albasani.net>, Jan-Erik Soderholm <jan-erik=
> .soderh... at telia.com> writes:
>> >VAXman- @SendSpamHere.ORG wrote 2011-12-29 12:56:
>> >> In article<9e7a3758-83c9-40e2-b119-5f8ad4ca0... at m7g2000vbc.googlegroup=
> s.com>, AEF<spamsink2... at yahoo.com> =A0writes:
>> >>> On Dec 27, 9:11=3DA0pm, Simon Clubley<clubley at remove_me.eisner.decus.=
> org-
>> >>> Earth.UFP> =A0wrote:
>> >>>> On 2011-12-27, Kenneth Fairfield<ken.fairfi... at gmail.com> =A0wrote:
>>
>> >>>>> On Friday, December 23, 2011 7:13:13 PM UTC-8, AEF wrote:
>> >>>>>> On Dec 22, 2:55 pm, Kenneth Fairfield<ken.fa... at gmail.com> =A0wrot=
> e:
> [...]
>> >>> Think of Firefox having the oozing tabs. And it's font control panel.
>> >>> What a nightmare! And making addresses grayed out except for the
>> >>> domain name. Yes, just what I need: a near impossible to read URL.
>>
>> >> This occurred with FF9.
>>
>> >FF8. Including the fix below.
>>
>> When I installed FF8 (not on WEENDOZE), all of my custom configuration
>> was maintained. =A0This FF9, the install COMPLETELY ignored anything that
>> I had previously configured. =A0Thus, like I said, it occurred with FF9.
> 
> Thanks. I actually dug up the cures for the oozing tabs (what a stupid
> idea -- interrupts your train of thought -- and seems ridiculous in
> that the hardware people are making faster and faster hardware and
> here we have some geeky a-huh a-huh a-huh programmer finding a way to
> waste time for something whose cool effect, if there is any, wears out
> on the second occurrence) and the url graying, on my own. A near
> miracle but I was very persistent!
> 
> FF9? They'll be the highest version number of any software in a few
> years!
> 
> Here's another thing I'd like a cure for with FF: It seems to me to be
> a memory leaker. I haven't checked carefully, but I know in some
> instances several years ago it clearly was. I think it does so on my
> Mac. And if you leave it open too long and with too many tabs, things
> start getting real slow. Closing it and reopening it work wonders! Can
> anyone shed some light on this? I think this also happens with IE. Is
> this just a browser thing?

After supporting the original NCSA Mosaic code on VMS for some years, I
decided it was actually a memory leak disguised as a browser.  I suspect
Marc carried on the same at Netscape, so it should be no surprise that
FF is a major memory leaker.


George Cook