* Jonas Fonseca <[EMAIL PROTECTED]> [2005-04-17 15:02+0200] > > Elinks seems to be pausing when starting up: > > > > [EMAIL PROTECTED] ~% time /usr/bin/elinks -no-connect 1 -force-html -dump > > /dev/null > > /usr/bin/elinks -no-connect 1 -force-html -dump /dev/null 0.02s user > > 0.00s system 1% cpu 1.038 total > > > > It always takes more than a second to start. > > > > When doing an strace, I see that it waits on: > > > > nanosleep({1, 0}, {1, 0}) = 0 > > Has this something to do with configuration file error parsing? In > src/config/conf.c sleep() is used to make it possible to see the printed > errors: > 436 if (error_occured) { > 437 fputc(7, stderr); > 438 sleep(1); > 439 } > > As a side note, maybe it doesn't make sense to sleep() when -dump or -source > is > passed since the motivation for calling sleep() is that switching to an > alternate screen doesn't work in all terminals and errors output will be > ``overwritten'' when ELinks starts drawing to the screen.
I see. Yes, I think it could be dropped for -dump and -source. > > This makes the program difficult to use, for example, in Mutt to dump > > HTML to text. For example, running a search on a large folder with > > emails containing HTML files can take a *long* time. > > If this started occurring after 0.10.4 was accepted into debian try to > pass the `-verbose 0' to get the previous behaviour where no config file > parse error are displayed. Thanks. An easy way to fix this problem for now then is to fix the configuration errors mentioned in #305004. Cheers, Hugo -- Hugo Haas - http://larve.net/people/hugo/
signature.asc
Description: Digital signature