Date: Mon, 05 Aug 2024 18:40:21 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 280147] ~/.termcap ignored Message-ID: <bug-280147-227-xOGo2FyZXg@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280147-227@https.bugs.freebsd.org/bugzilla/> References: <bug-280147-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280147 --- Comment #4 from ov2k@yahoo.com --- That commit seems promising. It removes /lib/ncurses/ncurses/termcap.c and= I think uses /contrib/ncurses/ncurses/tinfo/read_termcap.c instead. If I understand correctly, read_termcap.c is the upstream file. If I'm reading things correctly, the problem is in _nc_tgetent(). When the environment variable TERMCAP is not set, it simply calls get_termpath(). T= hat doesn't do anything with ~/.termcap. If the environment variable TERMPATH = is not set, it simply falls back to the C macro TERMPATH defined in what is now /lib/ncurses/tinfo/ncurses_cfg.h. It looks like switching from the FreeBSD termcap.c to the upstream read_termcap.c has caused this change in behavior. Is this a code bug in FreeBSD? An upstream bug? A documentation bug in termcap(5)? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-280147-227-xOGo2FyZXg>