repo: rxvt-unicode-sixel
action: commit
revision: 
path_from: 
revision_from: 45ac388cf29c85f67786312ed0ddca83eb8f5811:
path_to: 
revision_to: 
git.thebackupbox.net
rxvt-unicode-sixel
git clone git://git.thebackupbox.net/rxvt-unicode-sixel
commit 45ac388cf29c85f67786312ed0ddca83eb8f5811
Author: Marc Lehmann 
Date:   Wed Jul 13 03:04:03 2005 +0000

    *** empty log message ***

diff --git a/doc/etc/rxvt-unicode.termcap b/doc/etc/rxvt-unicode.termcap
index 4303a20bc55abe3939e3b79108ed33dcfe8e8cab..
index ..bd689e35114ba523e54044e7ba5069f87ec5ba46 100644
--- a/doc/etc/rxvt-unicode.termcap
+++ b/doc/etc/rxvt-unicode.termcap
@@ -1,4 +1,4 @@
-#	Reconstructed via infocmp from file: /etc/terminfo/r/rxvt-unicode
+#	Reconstructed via infocmp from file: /usr/share/terminfo/r/rxvt-unicode
 # (untranslatable capabilities removed to fit entry within 1023 bytes)
 rxvt-unicode|rxvt-unicode terminal (X Window System):\
 	:am:bw:eo:km:mi:ms:xn:xo:\
diff --git a/doc/rxvt.7.pod b/doc/rxvt.7.pod
index bf3709900cb2f74f62b045f3e7787277f9668dcb..
index ..6fb6d1aa04b69833b5e687e20cb21425213ef9ca 100644
--- a/doc/rxvt.7.pod
+++ b/doc/rxvt.7.pod
@@ -577,14 +577,8 @@ me) as "pretty girly".

 =item How can I start @@RXVT_NAME@@d in a race-free way?

-Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a
-server that answers @@RXVT_NAME@@c's requests, so it doesn't background
-itself.
-
-To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the
-following method to wait for the startup message before continuing:
-
-  { @@RXVT_NAME@@d & } | read
+Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
+display, create the listening socket and then fork.

 =item What's with the strange Backspace/Delete key behaviour?

-----END OF PAGE-----