[csw-devel] SF.net SVN: gar:[9972] csw/mgar/pkg/xterm/trunk/files
skayser at users.sourceforge.net
skayser at users.sourceforge.net
Tue May 25 21:01:56 CEST 2010
Revision: 9972
http://gar.svn.sourceforge.net/gar/?rev=9972&view=rev
Author: skayser
Date: 2010-05-25 19:01:56 +0000 (Tue, 25 May 2010)
Log Message:
-----------
xterm: update changelog.CSW and README.CSW for release
Modified Paths:
--------------
csw/mgar/pkg/xterm/trunk/files/README.CSW
csw/mgar/pkg/xterm/trunk/files/changelog.CSW
Modified: csw/mgar/pkg/xterm/trunk/files/README.CSW
===================================================================
--- csw/mgar/pkg/xterm/trunk/files/README.CSW 2010-05-25 18:00:16 UTC (rev 9971)
+++ csw/mgar/pkg/xterm/trunk/files/README.CSW 2010-05-25 19:01:56 UTC (rev 9972)
@@ -1,14 +1,37 @@
-$TERM, ncurses and how to make xterm display colors
----------------------------------------------------
+$TERM, ncurses/terminfo and how to make xterm display colors
+------------------------------------------------------------
-The xterm distributed with Solaris is a basic xterm (xterm-r6), whereas this
-is a current xterm and supports a wider range of terminal capabilites.
-To keep CSWncurses compatible with the Solaris xterm, TERM=xterm refers
-to the basic xterm-r6 capabilities, which unfortunately also defeats
-color support in some ncurses-based applications.
+The xterm distributed with Solaris is a basic xterm (xterm-r6), whereas the
+xterm distributed by OpenCSW is a current xterm and supports a wider range of
+terminal capabilites. Both terminals, per default, identify as TERM=xterm.
-To make full use of the capabilities of this xterm (including color-support)
-set TERM=xterm-new. You might then however experience problems when
-SSH'ing to machines where xterm-new isn't known to terminfo ("terminal not
-fully functional" messages). That's the main reason TERM=xterm-new hasn't
-been compiled in as a default by the way.
+To stay compatible with the Solaris xterm, CSW's terminfo treats TERM=xterm as
+a basic xterm-r6, which unfortunately also defeats color support in some
+ncurses-based applications.
+
+If you have CSW's ncurses/terminfo installed and want to make full use of the
+capabilities of this xterm (including color-support) set
+
+ TERMINFO=/opt/csw/share/terminfo
+ TERM=xterm-new
+
+As a side effect, you might notice problems when SSH'ing to machines where
+xterm-new isn't known to terminfo ("terminal not fully functional" messages).
+That's the main reason TERM=xterm-new hasn't been compiled in as a default for
+CSW's xterm in the first place.
+
+
+Note: X resource files in /opt/csw/lib/X11/app-defaults
+-------------------------------------------------------
+
+Although this package delivers some X resource files in
+/opt/csw/lib/X11/app-defaults/ this folder is not evaluated by the
+Solaris libXt per default.
+
+Either treat them as example files and copy and paste what you need into
+your system / personal X resource files or set XFILESEARCHPATH /
+XUSERFILESEARCHPATH to honor this directory.
+
+ http://www.faqs.org/faqs/x-faq/part2/section-22.html
+
+
Modified: csw/mgar/pkg/xterm/trunk/files/changelog.CSW
===================================================================
--- csw/mgar/pkg/xterm/trunk/files/changelog.CSW 2010-05-25 18:00:16 UTC (rev 9971)
+++ csw/mgar/pkg/xterm/trunk/files/changelog.CSW 2010-05-25 19:01:56 UTC (rev 9972)
@@ -1,3 +1,11 @@
+xterm (258,REV=2010.05.25)
+
+ * Updated to 258. (Fixes #4186)
+ * Reverted to Sun's X11 now that libXft and libXrender are available
+ as Sun X11 versions again.
+
+ -- Sebastian Kayser <skayser at opencsw.org> Tue, 25 May 2010 20:49:18 +0200
+
xterm (251,REV=2009.11.23)
* Updated to 251. (Fixes #3937, #3856)
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
More information about the devel
mailing list