I don't use rxvt-unicode but it is fine by me, I suggest you talk to the
maintainer though.
Neither of rxvt or xterm seems to be a perfect fit for rxvt-unicode but
rxvt looks closer, particularly for common keys like home and end.
On Tue, May 18, 2010 at 02:48:29PM +0200, David Coppa wrote:
> On Tue, 18 May 2010, Nicholas Marriott wrote:
>
> > On Tue, May 18, 2010 at 07:00:01AM -0400, Brynet wrote:
> > > In anything >= 4.7, the 'xterm' termcap entry supports 256 colours, if
> >
> > Not true.
> >
> > $ TERM=xterm tput colors
> > 8
> > $ TERM=xterm tput setaf 100|cat -v
> > ^[[3100m
> >
> > > I'm reading this patch correctly, this will hardcode the TERM
> > > environment variable to 'xterm-color256' which isn't required.
> >
> > It should be xterm-256color or more likely rxvt-256color.
>
> Oh, so I was right ;)
>
> Ok with this?
>
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/x11/rxvt-unicode/Makefile,v
> retrieving revision 1.1.1.1
> diff -u -p -r1.1.1.1 Makefile
> --- Makefile 3 May 2010 16:35:20 -0000 1.1.1.1
> +++ Makefile 18 May 2010 12:44:57 -0000
> @@ -3,6 +3,7 @@
> COMMENT = clone of rxvt with Unicode and Xft support
>
> DISTNAME = rxvt-unicode-9.07
> +PKGNAME = ${DISTNAME}p0
> CATEGORIES = x11
>
> EXTRACT_SUFX = .tar.bz2
> @@ -26,7 +27,7 @@ CONFIGURE_STYLE = autoconf
> AUTOCONF_VERSION = 2.61
> CONFIGURE_ARGS = --enable-perl \
> --disable-afterimage \
> - --with-term=xterm \
> + --with-term=rxvt-256color \
> --enable-xterm-colors=256
> # missing locale support
> CONFIGURE_ARGS += --disable-xim
