On Sun, Oct 2, 2011 at 8:22 AM, Nicholas Marriott
nicholas.marri...@gmail.com wrote:
This seems fine to me, but I'm not a perl guru. Have you talked to
upstream?
I'm having big difficulties trying to report the bug on rt.cpan.org.
It seems they do all the best to make you feel uncomfortable :(
I can't really follow what it is trying to do. Won't your change always
call infocmp if TERMCAP is not set instead of searching through the
files?
It looks like currently infocmp is only used if there are no termcap
files at all, not if the entry is missing from the files it does
find. So
On Thu, Oct 06, 2011 at 04:00:21PM +0100, Nicholas Marriott wrote:
I can't really follow what it is trying to do. Won't your change always
call infocmp if TERMCAP is not set instead of searching through the
files?
It looks like currently infocmp is only used if there are no termcap
files at
This seems fine to me, but I'm not a perl guru. Have you talked to
upstream?
Cheers
On Thu, Sep 29, 2011 at 10:49:36AM +0200, David Coppa wrote:
Hi,
The patch to ncurses nicm@ commited some days ago, exposes a bug
in perl's cpan/Term-Cap/Cap.pm. So, when you use rxvt-unicode on
a recent
Hi,
The patch to ncurses nicm@ commited some days ago, exposes a bug
in perl's cpan/Term-Cap/Cap.pm. So, when you use rxvt-unicode on
a recent -current, you will hit this bug with pkg_* tools:
# pkg_delete -v xclip
failed termcap lookup on rxvt-unicode-256color at
