#17401: emacs make-term: eterm-color not found due to new ncurses version ---------------------------------+------------------------------------------ Reporter: vinc17@… | Owner: imajes@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | Port: emacs,ncurses,ncursesw ---------------------------------+------------------------------------------ Comment(by vinc17@…): I've found the cause: under Mac OS X, emacs needs the eterm-color entry from ncurses. However ncursesw only provides Eterm-color (with a capital E). With ncursesw 5.6_1, the terminfo data were stored under the pathname {{{/opt/local/share/terminfo/e/Eterm-color}}}, but since HFS+ is case- insensitive, the file was read and the terminfo data for eterm-color came from this file (as a side effect?). Now, with ncursesw 5.7_0, the file is stored under the pathname {{{/opt/local/share/terminfo/45/Eterm-color}}}, i.e. the first letter has been replaced by its ASCII code. And since 'E' and 'e' don't have the same ASCII code, ncurses searches for the file {{{65/eterm-color}}} and infocmp gives the error: {{{ prunille:~> infocmp eterm-color infocmp: couldn't open terminfo file /opt/local/share/terminfo/65/eterm- color. }}} I've tried by adding a file {{{$HOME/.terminfo/65/Eterm-color}}} and this workaround solves the problem: {{{ prunille:~> infocmp eterm-color # Reconstructed via infocmp from file: /Users/vinc17/.terminfo/65 /eterm-color Eterm|Eterm-color|Eterm with xterm-style color support (X Window System), [...] }}} Note: there's no such problem under Debian though it has a case-sensitive file system, because it solves the problem in another way: emacs defines a $TERMCAP environment variable containing the eterm-color definition. -- Ticket URL: <http://trac.macports.org/ticket/17401#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS