*** empty log message ***

diff --git a/doc/rxvt.7.html b/doc/rxvt.7.html
index b133a13e19567f6bbc86e9c6b67147b0ede9ac68..d623e3f8eac015a87887d46aec4047412ee4f4e8 100644 (file)
--- a/doc/rxvt.7.html
+++ b/doc/rxvt.7.html
@@ -26,6 +26,7 @@
                        <li><a href="#how_do_i_know_which_rxvtunicode_version_i_m_using">How do I know which rxvt-unicode version I'm using?</a></li>
                        <li><a href="#rxvtunicode_uses_gobs_of_memory__how_can_i_reduce_that">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></li>
                        <li><a href="#how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></li>
+                       <li><a href="#how_can_i_start_urxvtd_automatically_when_i_run_urxvt_name__c">How can I start urxvtd automatically when I run URXVT_NAME@@c?</a></li>
                        <li><a href="#how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></li>
                        <li><a href="#how_do_i_set_the_correct__full_ip_address_for_the_display_variable">How do I set the correct, full IP address for the DISPLAY variable?</a></li>
                        <li><a href="#how_do_i_compile_the_manual_pages_on_my_own">How do I compile the manual pages on my own?</a></li>
@@ -208,6 +209,22 @@ rxvt-unicode then uses 8 bytes per screen cell.</p>
 display, create the listening socket and then fork.</p>
 <p>
 </p>
+<h3><a name="how_can_i_start_urxvtd_automatically_when_i_run_urxvt_name__c">How can I start urxvtd automatically when I run URXVT_NAME@@c?</a></h3>
+<p>If you want to start urxvtd automatically whenever you run
+urxvtc and the daemon isn't running yet, use this script:</p>
+<pre>
+   #!/bin/sh
+   urxvtc &quot;$@&quot;
+   if [ $? -eq 2 ]; then
+      urxvtd -q -o -f
+      urxvtc &quot;$@&quot;
+   fi</pre>
+<p>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.</p>
+<p>
+</p>
 <h3><a name="how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></h3>
 <p>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
index b3668ff990a5e6fab418ed20830c0f27758a2619..6ff1e0d4f51c284f941a410ae51c75ef0b3d0a9e 100644 (file)
--- 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
index 5c902195318a87446d86f83f2f30bb9bd0af1f4e..3a7e9664ad4f8b8d004a41d465af993d0dd0c5a1 100644 (file)
--- 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
index 955a363cefc75f37aa7a1892c371515e9bad7913..f6736453b79f4cfa4a6e67eb55a9978c16b3146c 100644 (file)
--- 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
index a86aa58a6d395135758df610d42587b43bb14f45..fe0337ff71628f7d8f77d61818327eae054316d5 100644 (file)
--- 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 ()