lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev can't interrupt "LIST" command


From: Klaus Weide
Subject: Re: lynx-dev can't interrupt "LIST" command
Date: Thu, 30 Dec 1999 19:03:11 -0600 (CST)

On Thu, 30 Dec 1999, Bela Lubkin wrote:

> [Hi, everyone.  I've been off the list for several months because the

Welcome back.

> listserv software won't subscribe me as "address@hidden", claims
> that the subscription request will be reviewed by a human, but that
> human is apparently asleep at the wheel.

Maybe a mail to majordomo-owner would help?

> Using Lynx 2.8.3dev.9, which I realize is a bit out of date.  Tell me if
> this has already been fixed...

No releant change I am aware of.

> I'm looking at a page that has about 48000 links on it.  I hit the 'L' =
> "LIST" command, just out of curiousity.  Lynx handles it very well
> (process grows to 27MB in core, gets progressively slower, but doesn't

The "progressivlely slower" during generation of the file is easy to
understand - showlist() uses an inefficient meothod for traversing the
list, it calls HText_childNumber() for each link which traverses the list
from the beginning for each call.  It could be changed.  But maybe it's
a feature - it makes it damage somewhat self-limiting, so you have time to
watch...

> fail).  However, I get bored with watching the growth of the temp file
> from another window, and try to abort out.  Lynx ignores both 'z' and
> '^G' = "INTERRUPT" keys.

All it should take is a HTCheckForInterrupt() in the
        for (cnt = 1; cnt <= refs; cnt++) {
loop in showlist() in LYList.c, plus some sensible action in case it
returns TRUE.  A prompt would make sense, asking whether to show the
partial file (return 0) or not (return -1).

> So anyway, it seems that "LIST" should have an explicit user interrupt
> check -- maybe once every hundred links or so.

If you care about it, you'll send a patch. :)

   Klaus


reply via email to

[Prev in Thread] Current Thread [Next in Thread]