[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Reducing the sit-for time in w3m-process-wait-process
- From: TSUCHIYA Masatoshi <tsuchiya@xxxxxxxxxx>
- Date: Fri, 05 Dec 2008 17:58:18 +0900
- X-ml-name: emacs-w3m
- X-mail-count: 10511
- References: <87vdu5tscu.fsf@xxxxxxxx> <8763m1j5xy.fsf@xxxxxxxx> <b4m4p1jauok.fsf@xxxxxxx>
(B>> On Fri, 05 Dec 2008 17:32:43 +0900
(B>> yamaoka@xxxxxxx (Katsumi Yamaoka) said as follows:
(B>>> I'm using the encapsulate-images feature from the shimbun package, and I
(B>>> noticed that when an article contains many images, it takes pretty long
(B>>> for w3m to fetch them. It seems to me this time is almost entirely spend
(B>>> on the '(sit-for 1)' in w3m-process-wait-process, while the actual w3m
(B>>> process is already finished. When I change this to '(sit-for 0.1)',
(B>>> fetching the images is much faster. It also seems to me that this speeds
(B>>> up refreshing shimbun groups in general.
(B>> To followup on this: I sometimes got parsing errors with '(sit-for
(B>> 0.1)', because the buffer didn't contain the whole output from the w3m
(B>> binary. However, I could fix this by using accept-process-output in the
(B>> w3m sentinel. Now everything works without problems, and the reduced
(B>> sit-for time makes working with emacs-w3m faster. Before, a w3m call
(B>> would at least take one second, even when w3m just received a redirect
(B>> or was fetching a small picture for a shimbun article. I attached the
(B>> two-lines patch to this mail.
(B>Great! I verified that the patch makes shimbun fast beyond
(B>recognition for fetching articles containing many images. David,
(B>could you provide the ChangeLog entry?
(BI worry that the following change causes hang-up.
(BI had tried various values when implementing w3m-proc.el, and adpoted
(Bthe smalest value that did not cause hang-up of emacs.
(BOf course, the ideal value may depend on users' own enviroments.
(BI have no idea to decide the ideal value in safe way.