Re: [bug-ncurses] API change with macro KEY_EVENT?

[Dr. Werner Fink]

On 2020/08/17 04:57:02 -0400, Thomas Dickey wrote:
> On Mon, Aug 17, 2020 at 09:56:17AM +0200, Dr. Werner Fink wrote:
> > 
> > Hmmm .... those packages do fail in staging test:
> > 
> >  apparmor   failed
> >  ceph       failed
> >  dpkg       failed
> >  grantlee5  failed
> >  kbuild     failed
> >  kdelibs4support    failed
> >  libappindicator:gtk3       failed
> >  libarchive failed
> >  memcached  failed
> >  meson:test failed
> >  python-pytest-django       failed
> >  speech-dispatcher  failed
> >  tcpd       failed
> >  zsh        failed
> 
> I see - lots of copy/paste going on.  Aside from zsh, none of those
> appear to have a reason to use ncurses.
>  
> > ... do I've revert the change for Visual C++ for OpenSUSE to get
> > then to compile again?
> 
> That seems to be the initial fix.  I don't see a reason why ncurses
> should provide a definition for a return value which is not supported
> by the configuration you've built :-(
> 
> fwiw, there's no known users of the wgetch_events feature.
> 
> I could probably replace that definition by any integer constant without
> altering the behavior of those programs.
> 

AFAICS from source of both dpkg and zsh: it seems that those packages uses
scripts (perl/awk) to seek for KEY_* macros to generate the header files
used later in the sources.  That seems to be a common method to grep
through /usr/include/ncurses.h :/

Werner

-- 
  "Having a smoking section in a restaurant is like having
          a peeing section in a swimming pool." -- Edward Burr

signature.asc
Description: PGP signature