output stalls unless user refreshes (ctrl-l)

[eMBee]

i am still investigating this, trying different ncurses versions, but i am reporting it incase someone else has seen that and has an idea:

sup seems to stall waiting for me to refresh the screen before it outputs anything. i'll investigate some more though (like building the gem for ncueses 5.9 properly and also looking into applying the fedora or debian patches to ncurses 5.9 to see if they make that problem go away)

this happens only on the debian 6 (squeeze) machine, but not on fedora (which also has ncurses 5.9, but with some patches applied)

[eMBee]

i switched to the use-mail branch because i am interested in the RMail to Mail switch, and to my astonishment the refresh problem went away. this suggests that ncurses is not at fault here as i suspected but something else is...

at the moment this makes the use-mail branch actually more usable compared to stable or develop branches, so i'll stick with that for now.

[gauteh]

Cool that you are testing it :) It could be that this bug was introduced with: #183.

[gauteh]

Note that the ncurses patches needed for the functionality in #183 to take effect was only recently developed as part of that PR: http://lists.gnu.org/archive/html/bug-ncurses/2013-12/msg00010.html

Debian or Fedora (probably) neither has it included yet. Did you check if upstream ncurses accepted has included the Fedora patches? So that they will eventually reach Debian?

[eMBee]

i didn't check upstream, but what's for certain is that i don't have those patches, so that's something i'll have to test, thanks!

[eMBee]

i did a pairing with @jamesotron today, and we tested that.

both backing out #183 with git revert 7e7858, and using ftp://invisible-island.net/ncurses/current/ncurses-5.9-20131207.tgz which has the ncurses patches, did not make the refresh problem go away.

i'll have to manually bisect the history to find out where the issue gets introduced. (can't think of any way to test this issue in a script)

[eMBee]

i only needed to test 5 commits to narrow it down and verify that the problem does come from #183 after all!
i tried reverting again, and this time it worked.
must have done something wrong before.

so your guess was right.

next to clean up the environment and make sure the ncurses patches are applied, as maybe we didn't do that properly either.

[gauteh]

Any progress on this?

[agorf]

I get the same behavior (having to refresh for any messages to show up) only when using an after-poll hook to trigger a bell.

[gauteh]

need info, possibly fixed.