Open githububub opened 7 years ago
i wasn't aware that dvtm requires an own terminfo database entry. do i conclude correctly that dvm compiles a terminfo description with tic and installs that into a systemwide directory, assuming it will be automatically picked up ?
@rofl0r Yes, it does install its own terminfo with tic
, if this is what you meant.
From the Makefile:
tic -s dvtm.info
i had time to look at this issue in-depth and documented my findings here: https://github.com/sabotage-linux/netbsd-curses/issues/19 . as a temporary workaround or just to test that dvtm works theoretically as expected, @githububub could rename the generated dvtm.info.cdb to $HOME/.terminfo.cdb, and then we can find a satisfactory permanent solution.
dvtm.info.cdb to $HOME/.terminfo.cdb and dvtm.info.cdb to $(PREFIX)/share/terminfo.cdb both do not resolve the no-op terminal window issue.
i've tried it in xterm and there it worked. i started dvtm like this to find out where/if it picks up the terminfo files:
strace -f dvtm 2>&1 | grep open
(failure to find the file has an ENOENT return value) once it could find the .cdb with the dvtm entries in it, it worked correctly.
btw you can exit the no-op dvtm with CTRL-D
i've now added dvtm terminfos to netbsd-curses' terminfo db, so this should be a non-issue in the future (unless there will be major changes to the terminfo of dvtm). https://github.com/sabotage-linux/netbsd-curses/commit/396a9d047c6c8b9ae2aefa7ad3aa1641f511234d
Building against netbsd-curses appears to build successfully, but launching dvtm 0.15 as
dvtm
orDVTM_TERM=rxvt-unicode dvtm
(urxvt) orDVTM_TERM=st-256color dvtm
(st) results in a no-op terminal window that cannot accept any input and must be killed to exit.dvtm.info.cdb terminfo database is built un the source directory (expected). However, dvtm.info.cdb is not installed to
/usr/share/terminfo
automatically per the default config.mk (not expected). No problem. Modifying the dvtm PKGBUILD recipe to install dvtm.info.cdb to/usr/share/terminfo
and settingTERMINFO=/usr/share/terminfo
does not resolve the no-op issue (not expected). Modifying config.mk and the build recipe to install dvtm.info.cdb to $HOME with TERMINFO set accordingly does not resolve the issue either. How to get dvtm up and running?