On Sun, Jun 12, 2022 at 03:16:40AM +0300, mark zaharov wrote: > here is the solution which my friend provides. He said it works well with > slang and this bug exists for ncurces only. > --- lynx-2.9.0dev.10.orig/src/LYStrings.c 2021-10-24 12:05:19.000000000 > +0300 > +++ lynx-2.9.0dev.10/src/LYStrings.c 2022-06-11 23:58:18.946192456 +0300 > @@ -2250,7 +2250,7 @@ > recent_sizechange)); > #endif /* HAVE_SIZECHANGE || USE_SLANG */ > if (!recent_sizechange) { > -#if defined(NCURSES) > +#if defined(NCURSES) && 0 > /* > * Work-around for scenario (Linux libc5) where we got a > * recent sizechange before reading KEY_RESIZE. If we do
Perhaps this would be reproducible if the version of lynx were identified, as well as which platform. I don't see it using - xterm 372, - ncurses 6.1 and 6.3, - lynx 2.8.9rel.1 and 2.9.0dev.10 -- Thomas E. Dickey <dic...@invisible-island.net> https://invisible-island.net ftp://ftp.invisible-island.net
signature.asc
Description: PGP signature