On Sat, Jun 11, 2005 at 12:53:38AM -0400, Daniel Jacobowitz <[EMAIL PROTECTED]>
wrote:
> I have to agree with Thomas on one thing - jed doesn't use libncurses,
> even in Debian.
ldd /usr/bin/jed
libncurses.so.5 => /usr/lib/libncurses.so.5 (0x00002aaaab40e000)
(this is on my amd64 machine with debian unstable)
ii jed 0.99.16-5 editor for
programmers (textmode version)
I have no idea to what extent jed uses ncurses, but it's linked against it
in debain for sure.
> At that point in time (last year), jed's GPM
> dependency may have caused libncurses to be loaded and initialized, but
> it doesn't today, so I can't check that.
Unfortunately, I can not reproduce this problem with jed anymore, but as
this was a very time-sensitive race condition and I upgraded my machine
recently this isn't very conclusive.
I am happy to disregard jed, however, if it is just linked against ncurses
and doesn't use it for screen sizing purposes.
> So I don't think there's anything we can do about the jed problem, if
> that still exists. It looks like the change that Thomas made would
> handle this problem, whether or not it's overkill.
>
> Is there still an ncurses bug here?
I am not sure, the only thing in the changelog of ncurses seems to be this
change:
+ fake a SIGWINCH in newterm() to accommodate buggy terminal
emulators and window managers (Debian #265631).
however, this seems unrelated as there it's not a bug in any terminal
emulator or window manager, but in ncurses. As such, I cannot verify that the
fix actually fixes the ncurses bug instead of sth. else.
I think I clearly documented the bug in ncurses, and as I understand the
mechanism well, so I can elaborate further if anything is still unclear.
Unfortunately, reproducing this is a bit difficult, as it depeQnds on
external timing factors and the race is very short.
--
The choice of a
-----==- _GNU_
----==-- _ generation Marc Lehmann
---==---(_)__ __ ____ __ [EMAIL PROTECTED]
--==---/ / _ \/ // /\ \/ / http://schmorp.de/
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
