X-Git-Url: https://git.dogcows.com/gitweb?a=blobdiff_plain;f=doc%2Fopenbox.1.sgml;h=70766ba468f9f3b4ba7e3c1bdf70f544fabb0c9f;hb=07a34428c0a03d322e725f315cde64d737967a57;hp=4ed2139e280e4a803e7ca8c435594be56416adbd;hpb=5a3154df0878e37d0af8fdd9077133283879b38f;p=chaz%2Fopenbox

diff --git a/doc/openbox.1.sgml b/doc/openbox.1.sgml
index 4ed2139e..70766ba4 100644
--- a/doc/openbox.1.sgml
+++ b/doc/openbox.1.sgml
@@ -63,36 +63,42 @@ manpage.1: manpage.sgml
       within GNOME or KDE, you can choose the appropriate entry, and it will
       launch GNOME or KDE with Openbox as the window manager.</para>
 
-    <para>If you don't want to run Openbox withing a desktop environment, then
-      it is recommended that you instead set up a ~/.xsession file and
-      use the <command>Default</command> session type. The ~/.xsession file
-      should any applications you want to run at startup, and then run
-      <command>&dhpackage;</command> at the end, such as:</para>
+    <para>The third option at log in, which is <command>Openbox</command>
+      without a session manager, uses the <command>openbox-session</command>
+      command to start Openbox. On log in, <command>&dhpackage;</command> will
+      run the ~/.config/openbox/autostart.sh script if it exists, and will run
+      the system-wide script @configdir@/openbox/autostart.sh otherwise. You
+      may place anything you want to run automatically in those files, for
+      example:
+      </para>
 
-      <blockquote><literallayout>
+    <blockquote><literallayout>
       xsetroot -solid grey &
-      gnome-settings-daemon &
-      exec <command>&dhpackage;</command></literallayout></blockquote>
+      gnome-settings-daemon &</literallayout></blockquote>
+
+    <para>Make sure that each line is followed by a "&" or else the script will
+      stop there and further commands will not be executed. You can use the
+      @configdir@/openbox/autostart.sh file as an example for creating your
+      own.</para>
+
+    <para>The default @configdir@/openbox/autostart.sh runs a number of things
+      with Openbox.</para>
 
     <para>Lastly, if you use <command>startx</command> to launch your X
-      session, you should set up a ~/.xinitrc file, exactly the same as the
-      above ~/.xsession file.</para>
+      session, you can set up a ~/.xinitrc file to run
+      <command>openbox-session</command> and follow the same directions as
+      above regarding the autostart.sh file.</para>
 
     <para>You can use the <command>obconf</command> tool to configure Openbox
       easily with a graphical interface, however more in-depth configuration
-      is possible by editing the configuration files by hand. The default
-      configuration files are installed in @configdir@/openbox/, and the
-      user configuration is placed in ~/.config/openbox/. You can copy
-      the default configuration to ~/.config/openbox and edit it to your
-      liking.</para>
-
-    <para>There are 3 default configuration files, <literal>rc.xml</literal>,
-      <literal>rc-gnome.xml</literal>, and <literal>rc-kde.xml</literal>. The
-      rc-gnome.xml is used when you run
-      <command>openbox-gnome-session</command> and the rc-kde.xml is used when
-      you run <command>openbox-kde-session</command>. The configuration
-      files should be named the same in ~/.config/openbox/.</para>
-
+      is possible by editing the configuration files by hand. Please note that
+      <command>obconf</command> older than version 2.0 may not work at all
+      for you.</para>
+
+    <para>The default configuration and menu files are installed in
+      @configdir@/openbox/, and the user configuration is placed in
+      ~/.config/openbox/. You can copy the default configuration and menus
+      to ~/.config/openbox and edit it to your liking.</para>
   </refsect1>
   <refsect1>
     <title>OPTIONS</title>
@@ -121,7 +127,7 @@ manpage.1: manpage.sgml
         <term><option>--reconfigure</option></term>
         <listitem>
           <para>If Openbox is already running on the display, tell it to
-            reload it's configuration.</para>
+            reload its configuration.</para>
         </listitem>
       </varlistentry>
       <varlistentry>