Behavioral change in Perl 5.30?

Llew_Llaw_Gyffes has asked for the wisdom of the Perl Monks concerning the following question:

Brethren,

I am experiencing a sudden behavioral change in a Perl/ncurses application. The application itself (icbm, an ICB client, which I maintain) was last updated on October 8; the terminal emulator it runs in (alacritty), on November 27. However, Perl was recently updated from v5.28.2 to v5.30.1. I am uncertain precisely when the behavioral change occurred, but it is definitely more recent than the alacritty update.

What APPEARS to me to be happening is that something that I have not yet identified is now "helpfully" auto-translating mouse-wheel up/down events into Up/Down KEY events. This is causing the mousewheel to scroll through my input history instead of scrolling my terminal window, which is Bad because it means I no longer have a way to scroll the terminal in this application.

Is anyone aware of any behavioral change in Perl 5.30 which would account for this?

Comment on Behavioral change in Perl 5.30?

Replies are listed 'Best First'.
Re: Behavioral change in Perl 5.30? by jcb (Parson) on Jan 01, 2020 at 00:09 UTC
That almost has to be a change in ncurses or the Perl bindings to ncurses. Most terminal emulators have settable modes to determine whether to handle mouse events internally or pass escape codes to the program running on the terminal. Your change is from the terminal emulator processing mouse wheel events itself to passing them to the user program. Check your terminfo database and be prepared to dig into the alacritty sources — in my experience, the mouse-related escape codes tend to be under-documented.	[reply]
Re: Behavioral change in Perl 5.30? by ikegami (Patriarch) on Dec 31, 2019 at 20:21 UTC
This has nothing to do with Perl, but with changes to Perl modules and/or C libraries being used (which ones are used, which versions are used, etc.)	[reply]