Permalink
Browse files

original rxvt-unicode source

  • Loading branch information...
0 parents commit aba25ad81ca367f46f531924694dc918c9aab2a3 Patrick Mullen committed Feb 17, 2009
Showing with 121,877 additions and 0 deletions.
  1. +340 −0 COPYING
  2. +19 −0 CVS/Entries
  3. +5 −0 CVS/Entries.Log
  4. +1 −0 CVS/Repository
  5. +1 −0 CVS/Root
  6. +1,401 −0 Changes
  7. +234 −0 INSTALL
  8. +181 −0 MANIFEST
  9. +88 −0 Makefile.in
  10. +1,115 −0 README.FAQ
  11. +255 −0 README.configure
  12. +1 −0 W11/CVS/Entries
  13. +3 −0 W11/CVS/Entries.Log
  14. +1 −0 W11/CVS/Repository
  15. +1 −0 W11/CVS/Root
  16. +1 −0 W11/X11/CVS/Entries
  17. +1 −0 W11/X11/CVS/Repository
  18. +1 −0 W11/X11/CVS/Root
  19. +1 −0 W11/w32/CVS/Entries
  20. +1 −0 W11/w32/CVS/Repository
  21. +1 −0 W11/w32/CVS/Root
  22. +1 −0 W11/wrap/CVS/Entries
  23. +1 −0 W11/wrap/CVS/Repository
  24. +1 −0 W11/wrap/CVS/Root
  25. +2 −0 aclocal.m4
  26. +1 −0 autoconf/CVS/Entries
  27. +1 −0 autoconf/CVS/Repository
  28. +1 −0 autoconf/CVS/Root
  29. +18 −0 autogen.sh
  30. +1,516 −0 config.guess
  31. +461 −0 config.h.in
  32. +1,626 −0 config.sub
  33. +13,022 −0 configure
  34. +784 −0 configure.ac
  35. +6 −0 doc/.cvsignore
  36. +21 −0 doc/CVS/Entries
  37. +3 −0 doc/CVS/Entries.Log
  38. +1 −0 doc/CVS/Repository
  39. +1 −0 doc/CVS/Root
  40. +104 −0 doc/Makefile.in
  41. +171 −0 doc/README.xvt
  42. +1,787 −0 doc/changes.txt
  43. +30 −0 doc/embed
  44. +16 −0 doc/embed-tk
  45. +3 −0 doc/etc/CVS/Entries
  46. +1 −0 doc/etc/CVS/Repository
  47. +1 −0 doc/etc/CVS/Root
  48. +22 −0 doc/etc/rxvt-unicode.termcap
  49. +164 −0 doc/etc/rxvt-unicode.terminfo
  50. +1 −0 doc/menu/CVS/Entries
  51. +1 −0 doc/menu/CVS/Repository
  52. +1 −0 doc/menu/CVS/Root
  53. +95 −0 doc/podtbl
  54. +22 −0 doc/pty-fd
  55. +147 −0 doc/rxvt-tabbed
  56. +1,630 −0 doc/rxvt.1.man.in
  57. +1,683 −0 doc/rxvt.1.pod
  58. +2,690 −0 doc/rxvt.7.man.in
  59. +2,537 −0 doc/rxvt.7.pod
  60. +184 −0 doc/rxvtc.1.man.in
  61. +63 −0 doc/rxvtc.1.pod
  62. +212 −0 doc/rxvtd.1.man.in
  63. +90 −0 doc/rxvtd.1.pod
  64. +1,766 −0 doc/rxvtperl.3.man.in
  65. +437 −0 doc/urxvt-8.2-256color.patch
  66. +254 −0 doc/wcwidth.patch
  67. +1 −0 doc/yodl/CVS/Entries
  68. +1 −0 doc/yodl/CVS/Repository
  69. +1 −0 doc/yodl/CVS/Root
  70. +507 −0 install-sh
  71. +30 −0 libev/CVS/Entries
  72. +1 −0 libev/CVS/Repository
  73. +1 −0 libev/CVS/Root
  74. +193 −0 libev/Changes
  75. +36 −0 libev/LICENSE
  76. +18 −0 libev/Makefile.am
  77. +58 −0 libev/README
  78. +3 −0 libev/README.embed
  79. +62 −0 libev/Symbols.ev
  80. +21 −0 libev/Symbols.event
  81. +6 −0 libev/autogen.sh
  82. +18 −0 libev/configure.ac
  83. +786 −0 libev/ev++.h
  84. +4,019 −0 libev/ev.3
  85. +3,138 −0 libev/ev.c
  86. +647 −0 libev/ev.h
  87. +3,941 −0 libev/ev.pod
  88. +215 −0 libev/ev_epoll.c
  89. +194 −0 libev/ev_kqueue.c
  90. +140 −0 libev/ev_poll.c
  91. +163 −0 libev/ev_port.c
  92. +296 −0 libev/ev_select.c
  93. +164 −0 libev/ev_vars.h
  94. +128 −0 libev/ev_win32.c
  95. +150 −0 libev/ev_wrap.h
  96. +399 −0 libev/event.c
  97. +158 −0 libev/event.h
  98. +226 −0 libev/event_compat.h
  99. +131 −0 libev/import_libevent
  100. +40 −0 libev/libev.m4
  101. +19 −0 libev/update_ev_wrap
  102. +7 −0 libev/update_symbols
  103. +70 −0 my-minimal-config-flags.txt
  104. +508 −0 ptytty.m4
  105. +14 −0 src/.cvsignore
  106. +62 −0 src/CVS/Entries
  107. +4 −0 src/CVS/Entries.Log
  108. +1 −0 src/CVS/Repository
  109. +1 −0 src/CVS/Root
  110. +236 −0 src/Makefile.in
  111. +1,578 −0 src/background.C
  112. +142 −0 src/background.h
  113. +420 −0 src/callback.h
  114. +4,026 −0 src/command.C
  115. +72 −0 src/command.h
  116. +315 −0 src/encoding.C
  117. +92 −0 src/encoding.h
  118. +3 −0 src/ev_cpp.C
  119. +16 −0 src/ev_cpp.h
  120. +105 −0 src/fdpass.C
  121. +387 −0 src/feature.h
  122. +63 −0 src/gencompose
  123. +350 −0 src/genlinedraw
  124. +307 −0 src/gentables
  125. +1 −0 src/graphics/CVS/Entries
  126. +1 −0 src/graphics/CVS/Repository
  127. +1 −0 src/graphics/CVS/Root
  128. +54 −0 src/hookinc.h
  129. +1,624 −0 src/init.C
  130. +93 −0 src/init.h
  131. +127 −0 src/iom_perl.h
  132. +220 −0 src/iom_perl.xs
  133. +488 −0 src/keyboard.C
  134. +105 −0 src/keyboard.h
  135. +70 −0 src/libptytty.h
  136. +434 −0 src/logging.C
  137. +1,609 −0 src/main.C
  138. +342 −0 src/misc.C
  139. +65 −0 src/optinc.h
  140. +19 −0 src/perl/CVS/Entries
  141. +1 −0 src/perl/CVS/Repository
  142. +1 −0 src/perl/CVS/Root
  143. +25 −0 src/perl/block-graphics-to-ascii
  144. +21 −0 src/perl/digital-clock
  145. +47 −0 src/perl/example-refresh-hooks
  146. +52 −0 src/perl/kuake
  147. +88 −0 src/perl/macosx-clipboard
  148. +198 −0 src/perl/matcher
  149. +56 −0 src/perl/option-popup
  150. +61 −0 src/perl/overlay-osc
  151. +61 −0 src/perl/readline
  152. +103 −0 src/perl/remote-clipboard
  153. +172 −0 src/perl/searchable-scrollback
  154. +152 −0 src/perl/selection
  155. +58 −0 src/perl/selection-autotransform
  156. +84 −0 src/perl/selection-pastebin
  157. +100 −0 src/perl/selection-popup
  158. +381 −0 src/perl/tabbed
  159. +139 −0 src/perl/urxvt-popup
  160. +73 −0 src/perl/xim-onthespot
  161. +364 −0 src/proxy.C
  162. +412 −0 src/ptytty.C
  163. +92 −0 src/ptytty.h
  164. +9 −0 src/ptytty_conf.h
  165. +120 −0 src/rsinc.h
  166. +62 −0 src/rxvt.C
  167. +1,475 −0 src/rxvt.h
  168. +151 −0 src/rxvtc.C
  169. +278 −0 src/rxvtd.C
  170. +125 −0 src/rxvtdaemon.C
  171. +21 −0 src/rxvtdaemon.h
  172. +1,709 −0 src/rxvtfont.C
  173. +102 −0 src/rxvtfont.h
  174. +63 −0 src/rxvtperl.h
  175. +1,838 −0 src/rxvtperl.xs
  176. +904 −0 src/rxvttoolkit.C
  177. +366 −0 src/rxvttoolkit.h
  178. +105 −0 src/rxvtutil.C
  179. +471 −0 src/rxvtutil.h
  180. +99 −0 src/salloc.C
  181. +27 −0 src/salloc.h
  182. +3,862 −0 src/screen.C
  183. +301 −0 src/scrollbar-next.C
  184. +71 −0 src/scrollbar-plain.C
  185. +228 −0 src/scrollbar-rxvt.C
  186. +89 −0 src/scrollbar-xterm.C
  187. +285 −0 src/scrollbar.C
  188. +197 −0 src/scrollbar.h
  189. +41 −0 src/table/CVS/Entries
  190. +1 −0 src/table/CVS/Repository
  191. +1 −0 src/table/CVS/Root
  192. +2,436 −0 src/table/big5.h
  193. +2,312 −0 src/table/big5_ext.h
  194. +2,337 −0 src/table/big5_plus.h
  195. +26 −0 src/table/category.h
  196. +2,015 −0 src/table/cns11643_1992_1.h
  197. +2,015 −0 src/table/cns11643_1992_2.h
  198. +2,644 −0 src/table/cns11643_1992_3.h
  199. +2,438 −0 src/table/cns11643_1992_4.h
  200. +735 −0 src/table/cns11643_1992_5.h
  201. +414 −0 src/table/cns11643_1992_6.h
  202. +284 −0 src/table/cns11643_1992_7.h
  203. +411 −0 src/table/cns11643_1992_f.h
  204. +1,142 −0 src/table/compose.h
  205. +2,229 −0 src/table/gb2312_1980_0.h
  206. +2,671 −0 src/table/gbk_0.h
  207. +17 −0 src/table/iso8859_1.h
  208. +40 −0 src/table/iso8859_10.h
  209. +28 −0 src/table/iso8859_11.h
  210. +43 −0 src/table/iso8859_13.h
  211. +58 −0 src/table/iso8859_14.h
  212. +35 −0 src/table/iso8859_15.h
  213. +46 −0 src/table/iso8859_16.h
  214. +44 −0 src/table/iso8859_2.h
  215. +41 −0 src/table/iso8859_3.h
  216. +42 −0 src/table/iso8859_4.h
  217. +31 −0 src/table/iso8859_5.h
  218. +29 −0 src/table/iso8859_6.h
  219. +38 −0 src/table/iso8859_7.h
  220. +31 −0 src/table/iso8859_8.h
  221. +36 −0 src/table/iso8859_9.h
  222. +20 −0 src/table/jis0201_1976_0.h
  223. +2,260 −0 src/table/jis0208_1990_0.h
  224. +2,138 −0 src/table/jis0212_1990_0.h
  225. +2,548 −0 src/table/jis0213_1.h
  226. +2,376 −0 src/table/jis0213_2.h
  227. +59 −0 src/table/koi8_r.h
  228. +63 −0 src/table/koi8_u.h
  229. +3,494 −0 src/table/ksc5601_1987_0.h
  230. +198 −0 src/table/linedraw.h
  231. +63 −0 src/table/viscii.h
  232. +1 −0 src/test/CVS/Entries
  233. +1 −0 src/test/CVS/Repository
  234. +1 −0 src/test/CVS/Root
  235. +22 −0 src/typemap
  236. +36 −0 src/typemap.iom
  237. +2,190 −0 src/urxvt.pm
  238. +3 −0 src/version.h
  239. +812 −0 src/xdefaults.C
  240. +8 −0 update_ptytty
340 COPYING

Large diffs are not rendered by default.

Oops, something went wrong.
@@ -0,0 +1,19 @@
+/.cvsignore/1.1/Mon Nov 24 17:28:07 2003//
+/COPYING/1.2/Tue Apr 26 00:34:59 2005//
+/Changes/1.909/Thu Dec 4 00:23:55 2008//
+/INSTALL/1.6/Sat Nov 24 19:03:15 2007//
+/MANIFEST/1.106/Fri Oct 10 13:23:56 2008//
+/Makefile.in/1.35/Fri Feb 22 16:09:52 2008//
+/README.FAQ/1.56/Tue Nov 4 23:00:43 2008//
+/README.configure/1.63/Sun Jun 15 13:54:15 2008//
+/aclocal.m4/1.6/Thu Aug 2 00:09:54 2007//
+/autogen.sh/1.2/Sun Nov 11 04:08:00 2007//
+/config.guess/1.2/Fri Jul 27 09:37:07 2007//
+/config.h.in/1.27/Sat Nov 8 16:49:46 2008//
+/config.sub/1.2/Fri Jul 27 09:37:08 2007//
+/configure/1.128/Sat Nov 8 16:49:46 2008//
+/configure.ac/1.105/Sun Jan 27 22:48:31 2008//
+/install-sh/1.2/Tue Jun 26 09:14:11 2007//
+/ptytty.m4/1.12/Mon May 5 16:51:52 2008//
+/update_ptytty/1.5/Wed Oct 31 15:21:22 2007//
+D
@@ -0,0 +1,5 @@
+A D/W11////
+A D/autoconf////
+A D/doc////
+A D/src////
+A D/libev////
@@ -0,0 +1 @@
+rxvt-unicode
@@ -0,0 +1 @@
+:pserver:anonymous@cvs.schmorp.de/schmorpforge
1,401 Changes

Large diffs are not rendered by default.

Oops, something went wrong.
234 INSTALL
@@ -0,0 +1,234 @@
+Installation Instructions
+*************************
+
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006 Free Software Foundation, Inc.
+
+This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+
+Basic Installation
+==================
+
+Briefly, the shell commands `./configure; make; make install' should
+configure, build, and install this package. The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package.
+
+ The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation. It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions. Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+ It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring. Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.
+
+ If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release. If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+ The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'. You need `configure.ac' if
+you want to change it or regenerate `configure' using a newer version
+of `autoconf'.
+
+The simplest way to compile this package is:
+
+ 1. `cd' to the directory containing the package's source code and type
+ `./configure' to configure the package for your system.
+
+ Running `configure' might take a while. While running, it prints
+ some messages telling which features it is checking for.
+
+ 2. Type `make' to compile the package.
+
+ 3. Optionally, type `make check' to run any self-tests that come with
+ the package.
+
+ 4. Type `make install' to install the programs and any data files and
+ documentation.
+
+ 5. You can remove the program binaries and object files from the
+ source code directory by typing `make clean'. To also remove the
+ files that `configure' created (so you can compile the package for
+ a different kind of computer), type `make distclean'. There is
+ also a `make maintainer-clean' target, but that is intended mainly
+ for the package's developers. If you use it, you may have to get
+ all sorts of other programs in order to regenerate files that came
+ with the distribution.
+
+Compilers and Options
+=====================
+
+Some systems require unusual options for compilation or linking that the
+`configure' script does not know about. Run `./configure --help' for
+details on some of the pertinent environment variables.
+
+ You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment. Here
+is an example:
+
+ ./configure CC=c99 CFLAGS=-g LIBS=-lposix
+
+ *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory. To do this, you can use GNU `make'. `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script. `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+
+ With a non-GNU `make', it is safer to compile the package for one
+architecture at a time in the source code directory. After you have
+installed the package for one architecture, use `make distclean' before
+reconfiguring for another architecture.
+
+Installation Names
+==================
+
+By default, `make install' installs the package's commands under
+`/usr/local/bin', include files under `/usr/local/include', etc. You
+can specify an installation prefix other than `/usr/local' by giving
+`configure' the option `--prefix=PREFIX'.
+
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
+
+ In addition, if you use an unusual directory layout you can give
+options like `--bindir=DIR' to specify different values for particular
+kinds of files. Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+
+ If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+Optional Features
+=================
+
+Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System). The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+ For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+Specifying the System Type
+==========================
+
+There may be some features `configure' cannot figure out automatically,
+but needs to determine by the type of machine the package will run on.
+Usually, assuming the package is built to be run on the _same_
+architectures, `configure' can figure that out, but if it prints a
+message saying it cannot guess the machine type, give it the
+`--build=TYPE' option. TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+ CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+ OS KERNEL-OS
+
+ See the file `config.sub' for the possible values of each field. If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+ If you are _building_ compiler tools for cross-compiling, you should
+use the option `--target=TYPE' to select the type of system they will
+produce code for.
+
+ If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+Sharing Defaults
+================
+
+If you want to set default values for `configure' scripts to share, you
+can create a site shell script called `config.site' that gives default
+values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists. Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+Variables not defined in a site shell script can be set in the
+environment passed to `configure'. However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost. In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'. For example:
+
+ ./configure CC=/usr/local2/bin/gcc
+
+causes the specified `gcc' to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
+an Autoconf bug. Until the bug is fixed you can use this workaround:
+
+ CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+`configure' Invocation
+======================
+
+`configure' recognizes the following options to control how it operates.
+
+`--help'
+`-h'
+ Print a summary of the options to `configure', and exit.
+
+`--version'
+`-V'
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+
+`--cache-file=FILE'
+ Enable the cache: use and save the results of the tests in FILE,
+ traditionally `config.cache'. FILE defaults to `/dev/null' to
+ disable caching.
+
+`--config-cache'
+`-C'
+ Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+ Do not print messages saying which checks are being made. To
+ suppress all normal output, redirect it to `/dev/null' (any error
+ messages will still be shown).
+
+`--srcdir=DIR'
+ Look for the package's source code in directory DIR. Usually
+ `configure' can determine that directory automatically.
+
+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
+
Oops, something went wrong.

0 comments on commit aba25ad

Please sign in to comment.