Copyright 1997-2005,2006 by Thomas E. Dickey

Contents

This file contains a list of the changes that I have made for xterm, from the notes that I add when submitting a patch.

You should note that other changes have been made as well, by other people, to fix bugs and correct ifdef's for portability. Most of these are summarized in the XFree86 CHANGELOG (found in the unbundled tree, xc/programs/Xserver/hw/xfree86). Here is the latest version of this file.

A new version (upgraded to an beta as of 2.6.PRE3, however, since it no longer dumps core in vttest) is reported to fix the ech bug. However, it is less VT100-compatible than the earlier versions such as 2.21b because it does not render reverse video (DECSCNM) properly. All versions do not update the screen frequently enough, making animation ineffective. See vttest, tests 1 and 2.

XGTERM link

It has some features which are also in color_xterm:(non-bce ANSI color, colorBD and colorUL resources, cursor warping, etc. The main feature is its Tektronix graphics emulation, which is the main reason for this particular program. Neither program has a change-log, so it is not easy to say which influenced the other.

That is from reading the source code. However testing under Debian Linux, something is wrong with the resource processing (neither popup menus nor colors work).

XITERM link

This appears to be rxvt 2.20, lightly reformatted, with a few ifdef's changed.

That is, it was. The name was later appropriated by a different program, which also uses the name iterm. Like gnome-terminal, iterm aims to be an xterm-emulator rather than a VT102- or VT220-emulator.

An earlier attempt by the same author (the "CSI-xterm") incorporates some of the changes I made for XFree86 xterm via cut and paste (but does not mention this in its README). It is said to be the basis for Solaris 10 xterm.

Both have similar problems running vttest.

How do I build XTERM?

Building a copy of xterm is simple, provided that you have a development configuration for X11: If you have a working xmkmf script (or correctly configured imake utility), all you need to do is type 

	xmkmf
	make
I have written a simple configure script for xterm which uses imake (or xmkmf) to generate a Makefile from the Makefile.in. I plan to restructure xterm to eliminate the hardcoded #ifdef's, replacing them with definitions that can be derived with the configuration script. The configure script is more flexible than xmkmf, since it allows you to enable or disable a variety of features. Type 
	configure --help
to get a list of options.

Though I plan to replace the hardcoded ifdef's with autoconfigured values, it will still continue to build properly with the imake environment, since that is how large distributions incorporate xterm.

How do I report bugs?

You should report bugs to me. I also respond to bug reports in a number of bug-tracking systems, though some are less open to searches than others. See also Analyzing problems with configure scripts

Additional Information

There appears to be no comprehensive source of information on xterm better than the documentation which comes with the source code. I have found Richard Shuford's archive to be invaluable for notes on the DEC VT220 and related terminals. Though not available at the time that I was collecting most of my notes, VT100.net is also a good source of primary information.

The command-line options, X resources and similar configurable options of xterm are documented in the manual page. Control sequences, i.e., programming information are in the ctlseqs.ms file which I bundle with the program source. (It used to be in the same directory in the X distribution, but was moved to a difference part of the tree some time ago). Note that you must format this file with different options than a manpage, e.g., 


	tbl ctlseqs.ms | nroff -ms >ctlseqs.txt
	tbl ctlseqs.ms | groff -ms >ctlseqs.ps
As a PostScript file, the individual letters of the control sequences are all boxed, for emphasis, but I find the text file equally readable.

Ongoing/future work

./usr/share/doc/xterm/copyright0000644000000000000000000000475510506313551016735 0ustar rootroot00000000000000$Id$ This package was debianized by first time by David Martinez Moreno on Tue, 27 Sep 2005 01:45:34 +0200. Upstream sources: http://invisible-island.net/xterm/xterm.html Until I have a proper answer from Thomas Dickey (upstream maintainer of xterm), the following terms for copyright and license apply to this package: Copyright 1999-2004,2005 by Thomas E. Dickey All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of the above listed copyright holder(s) not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. THE ABOVE LISTED COPYRIGHT HOLDER(S) DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL THE ABOVE LISTED COPYRIGHT HOLDER(S) BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Copyright 1989 The Open Group Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE OPEN GROUP BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of The Open Group shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from The Open Group. ./usr/share/doc/xterm/xterm.log.html0000644000000000000000000105370310405145237017607 0ustar rootroot00000000000000 XTERM - Change Log
Copyright 1997-2005,2006 by Thomas E. Dickey

Contents

This file contains a list of the changes that I have made for xterm, from the notes that I add when submitting a patch.

You should note that other changes have been made as well, by other people, to fix bugs and correct ifdef's for portability. Most of these are summarized in the XFree86 CHANGELOG (found in the unbundled tree, xc/programs/Xserver/hw/xfree86). Here is the latest version of this file.

A new version (upgraded to an beta as of 2.6.PRE3, however, since it no longer dumps core in vttest) is reported to fix the ech bug. However, it is less VT100-compatible than the earlier versions such as 2.21b because it does not render reverse video (DECSCNM) properly. All versions do not update the screen frequently enough, making animation ineffective. See vttest, tests 1 and 2.

XGTERM link

It has some features which are also in color_xterm:(non-bce ANSI color, colorBD and colorUL resources, cursor warping, etc. The main feature is its Tektronix graphics emulation, which is the main reason for this particular program. Neither program has a change-log, so it is not easy to say which influenced the other.

That is from reading the source code. However testing under Debian Linux, something is wrong with the resource processing (neither popup menus nor colors work).

XITERM link

This appears to be rxvt 2.20, lightly reformatted, with a few ifdef's changed.

That is, it was. The name was later appropriated by a different program, which also uses the name iterm. Like gnome-terminal, iterm aims to be an xterm-emulator rather than a VT102- or VT220-emulator.

An earlier attempt by the same author (the "CSI-xterm") incorporates some of the changes I made for XFree86 xterm via cut and paste (but does not mention this in its README). It is said to be the basis for Solaris 10 xterm.

Both have similar problems running vttest.

How do I build XTERM?

Building a copy of xterm is simple, provided that you have a development configuration for X11: If you have a working xmkmf script (or correctly configured imake utility), all you need to do is type 

	xmkmf
	make
I have written a simple configure script for xterm which uses imake (or xmkmf) to generate a Makefile from the Makefile.in. I plan to restructure xterm to eliminate the hardcoded #ifdef's, replacing them with definitions that can be derived with the configuration script. The configure script is more flexible than xmkmf, since it allows you to enable or disable a variety of features. Type 
	configure --help
to get a list of options.

Though I plan to replace the hardcoded ifdef's with autoconfigured values, it will still continue to build properly with the imake environment, since that is how large distributions incorporate xterm.

How do I report bugs?

You should report bugs to me. I also respond to bug reports in a number of bug-tracking systems, though some are less open to searches than others. See also Analyzing problems with configure scripts

Additional Information

There appears to be no comprehensive source of information on xterm better than the documentation which comes with the source code. I have found Richard Shuford's archive to be invaluable for notes on the DEC VT220 and related terminals. Though not available at the time that I was collecting most of my notes, VT100.net is also a good source of primary information.

The command-line options, X resources and similar configurable options of xterm are documented in the manual page. Control sequences, i.e., programming information are in the ctlseqs.ms file which I bundle with the program source. (It used to be in the same directory in the X distribution, but was moved to a difference part of the tree some time ago). Note that you must format this file with different options than a manpage, e.g., 


	tbl ctlseqs.ms | nroff -ms >ctlseqs.txt
	tbl ctlseqs.ms | groff -ms >ctlseqs.ps
As a PostScript file, the individual letters of the control sequences are all boxed, for emphasis, but I find the text file equally readable.

Ongoing/future work

./usr/share/doc/xterm/copyright0000644000000000000000000000475510506313551016735 0ustar rootroot00000000000000$Id$ This package was debianized by first time by David Martinez Moreno on Tue, 27 Sep 2005 01:45:34 +0200. Upstream sources: http://invisible-island.net/xterm/xterm.html Until I have a proper answer from Thomas Dickey (upstream maintainer of xterm), the following terms for copyright and license apply to this package: Copyright 1999-2004,2005 by Thomas E. Dickey All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of the above listed copyright holder(s) not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. THE ABOVE LISTED COPYRIGHT HOLDER(S) DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL THE ABOVE LISTED COPYRIGHT HOLDER(S) BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Copyright 1989 The Open Group Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE OPEN GROUP BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of The Open Group shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from The Open Group. ./usr/share/doc/xterm/xterm.log.html0000644000000000000000000105370310405145237017607 0ustar rootroot00000000000000 XTERM - Change Log
Copyright 1997-2005,2006 by Thomas E. Dickey

Contents

This file contains a list of the changes that I have made for xterm, from the notes that I add when submitting a patch.

You should note that other changes have been made as well, by other people, to fix bugs and correct ifdef's for portability. Most of these are summarized in the XFree86 CHANGELOG (found in the unbundled tree, xc/programs/Xserver/hw/xfree86). Here is the latest version of this file.

A new version (upgraded to an beta as of 2.6.PRE3, however, since it no longer dumps core in vttest) is reported to fix the ech bug. However, it is less VT100-compatible than the earlier versions such as 2.21b because it does not render reverse video (DECSCNM) properly. All versions do not update the screen frequently enough, making animation ineffective. See vttest, tests 1 and 2.

XGTERM link

It has some features which are also in color_xterm:(non-bce ANSI color, colorBD and colorUL resources, cursor warping, etc. The main feature is its Tektronix graphics emulation, which is the main reason for this particular program. Neither program has a change-log, so it is not easy to say which influenced the other.

That is from reading the source code. However testing under Debian Linux, something is wrong with the resource processing (neither popup menus nor colors work).

XITERM link

This appears to be rxvt 2.20, lightly reformatted, with a few ifdef's changed.

That is, it was. The name was later appropriated by a different program, which also uses the name iterm. Like gnome-terminal, iterm aims to be an xterm-emulator rather than a VT102- or VT220-emulator.

An earlier attempt by the same author (the "CSI-xterm") incorporates some of the changes I made for XFree86 xterm via cut and paste (but does not mention this in its README). It is said to be the basis for Solaris 10 xterm.

Both have similar problems running vttest.

How do I build XTERM?

Building a copy of xterm is simple, provided that you have a development configuration for X11: If you have a working xmkmf script (or correctly configured imake utility), all you need to do is type 

	xmkmf
	make
I have written a simple configure script for xterm which uses imake (or xmkmf) to generate a Makefile from the Makefile.in. I plan to restructure xterm to eliminate the hardcoded #ifdef's, replacing them with definitions that can be derived with the configuration script. The configure script is more flexible than xmkmf, since it allows you to enable or disable a variety of features. Type 
	configure --help
to get a list of options.

Though I plan to replace the hardcoded ifdef's with autoconfigured values, it will still continue to build properly with the imake environment, since that is how large distributions incorporate xterm.

How do I report bugs?

You should report bugs to me. I also respond to bug reports in a number of bug-tracking systems, though some are less open to searches than others. See also Analyzing problems with configure scripts

Additional Information

There appears to be no comprehensive source of information on xterm better than the documentation which comes with the source code. I have found Richard Shuford's archive to be invaluable for notes on the DEC VT220 and related terminals. Though not available at the time that I was collecting most of my notes, VT100.net is also a good source of primary information.

The command-line options, X resources and similar configurable options of xterm are documented in the manual page. Control sequences, i.e., programming information are in the ctlseqs.ms file which I bundle with the program source. (It used to be in the same directory in the X distribution, but was moved to a difference part of the tree some time ago). Note that you must format this file with different options than a manpage, e.g., 


	tbl ctlseqs.ms | nroff -ms >ctlseqs.txt
	tbl ctlseqs.ms | groff -ms >ctlseqs.ps
As a PostScript file, the individual letters of the control sequences are all boxed, for emphasis, but I find the text file equally readable.

Ongoing/future work

./usr/share/doc/xterm/copyright0000644000000000000000000000475510506313551016735 0ustar rootroot00000000000000$Id$ This package was debianized by first time by David Martinez Moreno on Tue, 27 Sep 2005 01:45:34 +0200. Upstream sources: http://invisible-island.net/xterm/xterm.html Until I have a proper answer from Thomas Dickey (upstream maintainer of xterm), the following terms for copyright and license apply to this package: Copyright 1999-2004,2005 by Thomas E. Dickey All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of the above listed copyright holder(s) not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. THE ABOVE LISTED COPYRIGHT HOLDER(S) DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL THE ABOVE LISTED COPYRIGHT HOLDER(S) BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Copyright 1989 The Open Group Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE OPEN GROUP BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of The Open Group shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from The Open Group. ./usr/share/doc/xterm/xterm.log.html0000644000000000000000000105370310405145237017607 0ustar rootroot00000000000000 XTERM - Change Log
Copyright 1997-2005,2006 by Thomas E. Dickey

Contents

This file contains a list of the changes that I have made for xterm, from the notes that I add when submitting a patch.

You should note that other changes have been made as well, by other people, to fix bugs and correct ifdef's for portability. Most of these are summarized in the XFree86 CHANGELOG (found in the unbundled tree, xc/programs/Xserver/hw/xfree86). Here is the latest version of this file.

A new version (upgraded to an beta as of 2.6.PRE3, however, since it no longer dumps core in vttest) is reported to fix the ech bug. However, it is less VT100-compatible than the earlier versions such as 2.21b because it does not render reverse video (DECSCNM) properly. All versions do not update the screen frequently enough, making animation ineffective. See vttest, tests 1 and 2.

XGTERM link

It has some features which are also in color_xterm:(non-bce ANSI color, colorBD and colorUL resources, cursor warping, etc. The main feature is its Tektronix graphics emulation, which is the main reason for this particular program. Neither program has a change-log, so it is not easy to say which influenced the other.

That is from reading the source code. However testing under Debian Linux, something is wrong with the resource processing (neither popup menus nor colors work).

XITERM link

This appears to be rxvt 2.20, lightly reformatted, with a few ifdef's changed.

That is, it was. The name was later appropriated by a different program, which also uses the name iterm. Like gnome-terminal, iterm aims to be an xterm-emulator rather than a VT102- or VT220-emulator.

An earlier attempt by the same author (the "CSI-xterm") incorporates some of the changes I made for XFree86 xterm via cut and paste (but does not mention this in its README). It is said to be the basis for Solaris 10 xterm.

Both have similar problems running vttest.

How do I build XTERM?

Building a copy of xterm is simple, provided that you have a development configuration for X11:
  • Header files and libraries. If you do not have the header files (usually under /usr/include/X11) for your system, you are better off building the libraries yourself. Xterm can be built with either X11R5 or X11R6 libraries; however X11R6 requires much more data to be installed before xterm will run. Xterm uses the Xaw library for popup menus.
  • imake and xmkmf. These utilities produce a Makefile from the Imakefile. They are not essential, but useful, particularly on systems with unusual configurations.
If you have a working xmkmf script (or correctly configured imake utility), all you need to do is type 

	xmkmf
	make
I have written a simple configure script for xterm which uses imake (or xmkmf) to generate a Makefile from the Makefile.in. I plan to restructure xterm to eliminate the hardcoded #ifdef's, replacing them with definitions that can be derived with the configuration script. The configure script is more flexible than xmkmf, since it allows you to enable or disable a variety of features. Type 
	configure --help
to get a list of options.

Though I plan to replace the hardcoded ifdef's with autoconfigured values, it will still continue to build properly with the imake environment, since that is how large distributions incorporate xterm.

How do I report bugs?

You should report bugs to me. I also respond to bug reports in a number of bug-tracking systems, though some are less open to searches than others. See also Analyzing problems with configure scripts

Additional Information

There appears to be no comprehensive source of information on xterm better than the documentation which comes with the source code. I have found Richard Shuford's archive to be invaluable for notes on the DEC VT220 and related terminals. Though not available at the time that I was collecting most of my notes, VT100.net is also a good source of primary information.

The command-line options, X resources and similar configurable options of xterm are documented in the manual page. Control sequences, i.e., programming information are in the ctlseqs.ms file which I bundle with the program source. (It used to be in the same directory in the X distribution, but was moved to a difference part of the tree some time ago). Note that you must format this file with different options than a manpage, e.g., 


	tbl ctlseqs.ms | nroff -ms >ctlseqs.txt
	tbl ctlseqs.ms | groff -ms >ctlseqs.ps
As a PostScript file, the individual letters of the control sequences are all boxed, for emphasis, but I find the text file equally readable.

Ongoing/future work

  • soft (downloadable) fonts
  • search scrollback It would be nice to be able to search the scrollback buffer.
  • printer interface

    Done, except for the corresponding support in the VT52 emulation. It would be nice to have a dialog to control this.

  • allow alternate libraries for popup-menus and dialogs

    My configure script currently provides tests for the variations of Athena widgets (Xaw3D, neXtaw). I intend to make additional changes to support Motif scrollbars and menus. Motif requires a different style of interface for the menus: binding a popup menu to control right mouse may cause the server to hang. As an intermediate step, I implemented a toolbar for the Athena widgets. In turn, that works well enough except with XFree86 4.x: the Xaw library geometry management is broken. (Other implementations of the Athena widgets work well enough).

  • popup window that shows hex code for content of a character cell and hexadecimal keyboard entry for all Unicode characters (ISO 14755)
  • correct cut&paste of TAB character
./usr/share/doc/xterm/copyright0000644000000000000000000000475510506313551016735 0ustar rootroot00000000000000$Id$ This package was debianized by first time by David Martinez Moreno on Tue, 27 Sep 2005 01:45:34 +0200. Upstream sources: http://invisible-island.net/xterm/xterm.html Until I have a proper answer from Thomas Dickey (upstream maintainer of xterm), the following terms for copyright and license apply to this package: Copyright 1999-2004,2005 by Thomas E. Dickey All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of the above listed copyright holder(s) not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. THE ABOVE LISTED COPYRIGHT HOLDER(S) DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL THE ABOVE LISTED COPYRIGHT HOLDER(S) BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Copyright 1989 The Open Group Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE OPEN GROUP BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of The Open Group shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from The Open Group. ./usr/share/doc/xterm/xterm.log.html0000644000000000000000000105370310405145237017607 0ustar rootroot00000000000000 XTERM - Change Log
Copyright 1997-2005,2006 by Thomas E. Dickey

Contents

This file contains a list of the changes that I have made for xterm, from the notes that I add when submitting a patch.

You should note that other changes have been made as well, by other people, to fix bugs and correct ifdef's for portability. Most of these are summarized in the XFree86 CHANGELOG (found in the unbundled tree, xc/programs/Xserver/hw/xfree86). Here is the latest version of this file.

A new version (upgraded to an beta as of 2.6.PRE3, however, since it no longer dumps core in vttest) is reported to fix the ech bug. However, it is less VT100-compatible than the earlier versions such as 2.21b because it does not render reverse video (DECSCNM) properly. All versions do not update the screen frequently enough, making animation ineffective. See vttest, tests 1 and 2.

XGTERM link

It has some features which are also in color_xterm:(non-bce ANSI color, colorBD and colorUL resources, cursor warping, etc. The main feature is its Tektronix graphics emulation, which is the main reason for this particular program. Neither program has a change-log, so it is not easy to say which influenced the other.

That is from reading the source code. However testing under Debian Linux, something is wrong with the resource processing (neither popup menus nor colors work).

XITERM link

This appears to be rxvt 2.20, lightly reformatted, with a few ifdef's changed.

That is, it was. The name was later appropriated by a different program, which also uses the name iterm. Like gnome-terminal, iterm aims to be an xterm-emulator rather than a VT102- or VT220-emulator.

An earlier attempt by the same author (the "CSI-xterm") incorporates some of the changes I made for XFree86 xterm via cut and paste (but does not mention this in its README). It is said to be the basis for Solaris 10 xterm.

Both have similar problems running vttest.

How do I build XTERM?

Building a copy of xterm is simple, provided that you have a development configuration for X11:
  • Header files and libraries. If you do not have the header files (usually under /usr/include/X11) for your system, you are better off building the libraries yourself. Xterm can be built with either X11R5 or X11R6 libraries; however X11R6 requires much more data to be installed before xterm will run. Xterm uses the Xaw library for popup menus.
  • imake and xmkmf. These utilities produce a Makefile from the Imakefile. They are not essential, but useful, particularly on systems with unusual configurations.
If you have a working xmkmf script (or correctly configured imake utility), all you need to do is type 

	xmkmf
	make
I have written a simple configure script for xterm which uses imake (or xmkmf) to generate a Makefile from the Makefile.in. I plan to restructure xterm to eliminate the hardcoded #ifdef's, replacing them with definitions that can be derived with the configuration script. The configure script is more flexible than xmkmf, since it allows you to enable or disable a variety of features. Type 
	configure --help
to get a list of options.

Though I plan to replace the hardcoded ifdef's with autoconfigured values, it will still continue to build properly with the imake environment, since that is how large distributions incorporate xterm.

How do I report bugs?

You should report bugs to me. I also respond to bug reports in a number of bug-tracking systems, though some are less open to searches than others. See also Analyzing problems with configure scripts

Additional Information

There appears to be no comprehensive source of information on xterm better than the documentation which comes with the source code. I have found Richard Shuford's archive to be invaluable for notes on the DEC VT220 and related terminals. Though not available at the time that I was collecting most of my notes, VT100.net is also a good source of primary information.

The command-line options, X resources and similar configurable options of xterm are documented in the manual page. Control sequences, i.e., programming information are in the ctlseqs.ms file which I bundle with the program source. (It used to be in the same directory in the X distribution, but was moved to a difference part of the tree some time ago). Note that you must format this file with different options than a manpage, e.g., 


	tbl ctlseqs.ms | nroff -ms >ctlseqs.txt
	tbl ctlseqs.ms | groff -ms >ctlseqs.ps
As a PostScript file, the individual letters of the control sequences are all boxed, for emphasis, but I find the text file equally readable.

Ongoing/future work

  • soft (downloadable) fonts
  • search scrollback It would be nice to be able to search the scrollback buffer.
  • printer interface

    Done, except for the corresponding support in the VT52 emulation. It would be nice to have a dialog to control this.

  • allow alternate libraries for popup-menus and dialogs

    My configure script currently provides tests for the variations of Athena widgets (Xaw3D, neXtaw). I intend to make additional changes to support Motif scrollbars and menus. Motif requires a different style of interface for the menus: binding a popup menu to control right mouse may cause the server to hang. As an intermediate step, I implemented a toolbar for the Athena widgets. In turn, that works well enough except with XFree86 4.x: the Xaw library geometry management is broken. (Other implementations of the Athena widgets work well enough).

  • popup window that shows hex code for content of a character cell and hexadecimal keyboard entry for all Unicode characters (ISO 14755)
  • correct cut&paste of TAB character