rustyline overwrites previously registered SIGWINCH handler

[PaulJuliusMartinez]

If an application registers a SIGWINCH handler prior to initializing rustyline, rustyline will override it when it installs its own SIGWINCH handler. Installation of the SIGWINCH handler takes place here.

The sigaction system call can return the function pointer for the previously registered signal handler. rustyline could store this value and call the function if it is non-NULL. (See this StackOverflow question.) The alternative for the application is to register their signal handler after initializing rustyline and either save the reference to rustyline's signal handler, or leave rustyline's signal handler abandoned, but people probably don't expect rustyline to install a SIGWINCH handler, so they'll only realize this once it causes a bug.

[gwenn]

Should we use signal-hook ?

[gwenn]

Version 10.0.0 released.