ST or BEL but only actually used a single ESC. Hack to replace with BEL for
now while I report upstream.
The combination of the recent update to this port (which fixed a bug
that prevented urxvt from responding to colour queries other than OSC 4)
and a recent change in tmux (which started querying fg/bg colour with
OSC 10/11 respectively) resulted in this being particularly annoying.
Cause diagnosed by nicm, thanks!
(default package) = upstream's defaults plus enable 256-colour support
"everything" = upstream's "--enable-everything" build
"small" = reduce size/dep's - starting with upstream's "--disable-everything"
but --enable-frills is added to avoid a build failure
the default package no longer includes "--enable-unicode3" which
upstream recommends not to use "unless you really need a lot of non-BMP
characters" .. "can store and display unicode characters above 65535
even without this flag, but the number of such characters is limited to
a few thousand", if you need that then switch to "everything".
also: update DESCR, take maintainer
setting TERMINFO in the environment instead. Found when looking at
9.29 as this patch conflicts there. (Not updating yet as libptytty moved
to an external dependency).
Follow the upstream recommendations for packagers and switch to
multi-packages:
devel/gettext -> devel/gettext,-runtime
devel/gettext-tools -> devel/gettext,-tools
(new) devel/gettext,-textstyle
already does.
This fixes the build with ports-gcc-8. Thanks to jca@ who pointed out
that we could use libesupc++, and performed a simple test that showed
there is not much incentive to do so.
While here, remove trailing whitespaces in DESCR.
OK bcallah@ jca@
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
utmp recording) which was in my tree already and which wasn't in Daniel's
submitted diff for the previous commit, as pointed out by dcoppa@.
(add an XXX comment reminder; as an xterm alternative, this *should*
do utmp recording.)
