[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: macros for w3m-attributes
On 2018-09-03 13:30, TSUCHIYA Masatoshi wrote:
> >> On Mon, 03 Sep 2018 07:28:48 +0900
> >> yamaoka@xxxxxxx (Katsumi Yamaoka) said as follows:
>
> >Hi Tsuchiya-san, could you follow this subject up? (I'm not so versed
> >in the asynchronous operation of emacs-w3m, sorry.)
>
> However, these parts are quite fragile parts of emacs-w3m. I need much
> time to evalute Boruch's patch.
Thank you for the information and the attention. What occurred to me may
be desirable to make the code less fragile and easier to debug may be to
'flatten' out the asynchronous operations so that the handler-queue for
any async process only has one item. Possibly this can be done by
passing the handler object as is done now, but using it only as a
boolean test to see if the operation is currently running async, and
only if not to create an async at that point.
In the meantime, I do seem to have fixed the bug that I discussed in
message [12926] (2018-02-23); however, there are a number of other
things that will show in a simple patch, so to isolate it for submission
may be some more work. For instance, I converted the code in w3m.el to
be lexically-bound throughout). Also, in the course of the work, I found
that the code was not following the promised documentation in how it
deals with the data structures `w3m-content-type-alist' and
`w3m-doc-view-content-types', and my current state of code seems to fix
those issues as well.
If there is interest in my current working version of the code, it would
probably be best to post it in entirety instead of as a patch; I can do
that offlist for anyone who asks, or onlist if that is appropriate.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0