Re: [documancer] broken pipe problem

[Vaclav S. <vac...@ma...>]

Hi,

arn...@we... wrote:
> with the following I can produce a broken pipe
> (see the traceback at the end):
>   - Book: Python 2.3 Docs
>   - Search String: AF_UNIX
>   - Results:
>     a) 1000 socket
>     b)  889 7.2.1 Socket Objects
>     c)  889 Index
>     d)  873 11.15 SocketServer
>   - wait until page a) is displayed
>   - click on d), wait until it is displayed, everything is ok
>   - click on c), do _not_ wait until it is displayed (it takes
>     a little while because it is a long text)
>     and click e.g. on a) =3D=3D> "broken pipe"

This is harmless (the exception is catched, it only polutes stderr),=20
but thanks anyway ;) It's now fixed, Documancer's HTTP server now=20
handles all (HTTP) errors silently.

> Two more things:
> - For b) there seems to be no AF_UNIX in the text (at least none is
>   highlighted) ?!

Thanks! This was because SWISH-E treats _ as word deliminer. I fixed=20
this by adding _ and ~ to the list of word characters, are there any=20
other characters that can be part of identifier? Note that you have=20
to reindex the book for the fix to kick in.

>   ((BTW: do you think it is easy to enable a CTRL-f search
>     in the presently visible document ?))

=46rankly, I don't know because I didn't look into it yet. I _think_=20
there's something like that in wxMozilla, but I use type-ahead all=20
the time myself.

> - Even type-ahead find works to some extent,
>   presently only for the text of links (!?).
>   Do you think this is just a wxMozilla configuration issue ?

Yes, it is -- set "accessibility.typeaheadfind.linksonly" to "false"=20
in prefs.js.

Regards,
Vaclav

=2D-=20
PGP key: 0x465264C9, available from http://pgp.mit.edu/