netbsd-curses
netbsd-curses copied to clipboard
libcurses and dependencies taken from netbsd and brought into a portable shape (at least to musl or glibc)
Is there a point to keep them separate? If they were merged a lot of things would build without manual intervention.
Some packages (e.g. `util-linux`) expect `libtinfo.so` to be available.
`curses.h` is full of identifiers in the `__`-prefixed namespace, many of which are things that could easily clash with system headers. I saw a report of it failing to build...
`toe` - table of (terminfo) entries With no options, toe lists all available terminal types by primary name with descriptions. File arguments specify the directories to be scanned; if no...
``` # Generate our man pages terminfo.5: genman terminfo.5.in term.h termcap_map.c @echo "Generating terminfo man pages" ${SCRIPT_ENV} ${HOST_SH} ${.ALLSRC} > ${.TARGET} CLEANFILES+= terminfo.5 man: terminfo.5 ```
maybe happens with ncurses as well. it doesn't with slang.
Unable to build dvtm against netbsd-curses... >==> Starting build()... cleaning cleaning dvtm build options: CC dvtm.c CC vt.c CFLAGS = -march=native -O2 -pipe -fstack-protector-all -fomit-frame-pointer -std=c99 -I. -DVERSION="0.15" -DNDEBUG -D_FORTIFY_SOURCE=2...
- open a linux terminal - run midnight commander - in midnight commander, run `nano inexistant_file` - nano opens, close it with CTRL-X now you get a black screen with...
depends on #10 and #9