repo: rxvt-unicode-sixel
action: commit
revision: 
path_from: 
revision_from: 14cde507eea341d0785acfa56cb127d041159112:
path_to: 
revision_to: 

commit 14cde507eea341d0785acfa56cb127d041159112
Author: Marc Lehmann 
Date:   Thu Feb 2 00:31:47 2006 +0000

    *** empty log message ***

diff --git a/doc/rxvt.7.html b/doc/rxvt.7.html

--- a/doc/rxvt.7.html
+++ b/doc/rxvt.7.html
@@ -26,6 +26,7 @@
 			
How do I know which rxvt-unicode version I'm using?
 			
Rxvt-unicode uses gobs of memory, how can I reduce that?
 			
How can I start urxvtd in a race-free way?
+			
How can I start urxvtd automatically when I run URXVT_NAME@@c?
 			
How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
 			
How do I set the correct, full IP address for the DISPLAY variable?
 			
How do I compile the manual pages on my own?
@@ -208,6 +209,22 @@ rxvt-unicode then uses 8 bytes per screen cell.

 display, create the listening socket and then fork.

 

 
+
How can I start urxvtd automatically when I run URXVT_NAME@@c?
+
If you want to start urxvtd automatically whenever you run
+urxvtc and the daemon isn't running yet, use this script:
+
+   #!/bin/sh
+   urxvtc "$@"
+   if [ $? -eq 2 ]; then
+      urxvtd -q -o -f
+      urxvtc "$@"
+   fi
+
This tries to create a new terminal, and if fails with exit status 2,
+meaning it couldn't connect to the daemon, it will start the daemon and
+re-run the command. Subsequent invocations of the script will re-use the
+existing daemon.
+

+
 
How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
 
The original rxvt and rxvt-unicode always export the variable ``COLORTERM'',
 so you can check and see if that is set. Note that several programs, JED,
diff --git a/doc/rxvt.7.man.in b/doc/rxvt.7.man.in

--- a/doc/rxvt.7.man.in
+++ b/doc/rxvt.7.man.in
@@ -129,7 +129,7 @@
 .\" ========================================================================
 .\"
 .IX Title "rxvt 7"
-.TH rxvt 7 "2006-01-31" "7.5" "RXVT-UNICODE"
+.TH rxvt 7 "2006-02-02" "7.5" "RXVT-UNICODE"
 .SH "NAME"
 RXVT REFERENCE \- FAQ, command sequences and other background information
 .SH "SYNOPSIS"
@@ -217,6 +217,26 @@ rxvt-unicode then uses 8 bytes per screen cell.
 Try \f(CW\*(C`@@URXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@URXVT_NAME@@d to open the
 display, create the listening socket and then fork.
 .PP
+\fIHow can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?\fR
+.IX Subsection "How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?"
+.PP
+If you want to start @@URXVT_NAME@@d automatically whenever you run
+@@URXVT_NAME@@c and the daemon isn't running yet, use this script:
+.PP
+.Vb 6
+\&   #!/bin/sh
+\&   @@URXVT_NAME@@c "$@"
+\&   if [ $? -eq 2 ]; then
+\&      @@URXVT_NAME@@d -q -o -f
+\&      @@URXVT_NAME@@c "$@"
+\&   fi
+.Ve
+.PP
+This tries to create a new terminal, and if fails with exit status 2,
+meaning it couldn't connect to the daemon, it will start the daemon and
+re-run the command. Subsequent invocations of the script will re-use the
+existing daemon.
+.PP
 \fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR
 .IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
 .PP
diff --git a/doc/rxvt.7.pod b/doc/rxvt.7.pod

--- a/doc/rxvt.7.pod
+++ b/doc/rxvt.7.pod
@@ -75,6 +75,23 @@ rxvt-unicode then uses 8 bytes per screen cell.
 Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the
 display, create the listening socket and then fork.

+=head3 How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?
+
+If you want to start @@URXVT_NAME@@d automatically whenever you run
+@@URXVT_NAME@@c and the daemon isn't running yet, use this script:
+
+   #!/bin/sh
+   @@URXVT_NAME@@c "$@"
+   if [ $? -eq 2 ]; then
+      @@URXVT_NAME@@d -q -o -f
+      @@URXVT_NAME@@c "$@"
+   fi
+
+This tries to create a new terminal, and if fails with exit status 2,
+meaning it couldn't connect to the daemon, it will start the daemon and
+re-run the command. Subsequent invocations of the script will re-use the
+existing daemon.
+
 =head3 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.

 The original rxvt and rxvt-unicode always export the variable "COLORTERM",
diff --git a/doc/rxvt.7.txt b/doc/rxvt.7.txt

--- a/doc/rxvt.7.txt
+++ b/doc/rxvt.7.txt
@@ -65,6 +65,22 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
     Try "urxvtd -f -o", which tells urxvtd to open the display, create the
     listening socket and then fork.

+   How can I start urxvtd automatically when I run URXVT_NAME@@c?
+    If you want to start urxvtd automatically whenever you run urxvtc and
+    the daemon isn't running yet, use this script:
+
+       #!/bin/sh
+       urxvtc "$@"
+       if [ $? -eq 2 ]; then
+          urxvtd -q -o -f
+          urxvtc "$@"
+       fi
+
+    This tries to create a new terminal, and if fails with exit status 2,
+    meaning it couldn't connect to the daemon, it will start the daemon and
+    re-run the command. Subsequent invocations of the script will re-use the
+    existing daemon.
+
    How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
     The original rxvt and rxvt-unicode always export the variable
     "COLORTERM", so you can check and see if that is set. Note that several
diff --git a/src/rxvttoolkit.C b/src/rxvttoolkit.C

--- a/src/rxvttoolkit.C
+++ b/src/rxvttoolkit.C
@@ -400,7 +400,6 @@ rxvt_display::ref_next ()
   // before affording re-loading/parsing
   XrmDestroyDatabase (XrmGetDatabase (display));
   XrmSetDatabase (display, get_resources ());
-  printf ("next\n");//D
 }

 rxvt_display::~rxvt_display ()

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