 
 ;;;###autoload
 (defun rdebug (command-line)
-  "Run rdebug on program FILE in buffer *rdebug-cmd-FILE*.
-The directory containing FILE becomes the initial working directory
-and source-file directory for your debugger.
-
-The custom variable `gud-rdebug-command-name' sets the pattern used
-to invoke pydb.
-
-If `rdebug-many-windows' is nil (the default value) then pydb just
-starts with two windows: one displaying the GUD buffer and the
-other with the source file with the main routine of the inferior.
-
-If `rdebug-many-windows' is t, regardless of the value of the layout
-below will appear.
+  "Run the rdebug Ruby debugger and start the Emacs user interface.
+
+By default, the user interface looks like the following:
 
 +----------------------------------------------------------------------+
-|                               GDB Toolbar                            |
+|                                Toolbar                               |
 +-----------------------------------+----------------------------------+
-| GUD buffer (I/O of rdebug)        | Variables buffer                 |
-|                                   | RET rdebug-variables-edi         |
+| Debugger shell                    | Variables buffer                 |
+|                                   | RET rdebug-variables-edit        |
 |                                   |                                  |
 |                                   |                                  |
 +-----------------------------------+----------------------------------+
+|                                   |                                  |
 | Source buffer                     | Output buffer                    |
 |                                   |                                  |
 +-----------------------------------+----------------------------------+
 | Stack buffer                      | Breakpoints buffer               |
-| RET rdebug-goto-stack-frame       | SPC  rdebug-toggle-breakpoint    |
+| RET rdebug-goto-stack-frame       | t    rdebug-toggle-breakpoint    |
 |                                   | RET  rdebug-goto-breakpoint      |
 |                                   | DEL  rdebug-delete-breakpoint    |
 +-----------------------------------+----------------------------------+
-"
+
+The variable `rdebug-many-windows-layout-function' can be
+customized so that another layout is used. In addition to a
+number of predefined layouts it's possible to define a function
+to perform a custom layout.
+
+If `rdebug-many-windows' is nil, only a traditional debugger
+shell and source window is opened.
+
+The directory containing the debugged script becomes the initial
+working directory and source-file directory for your debugger.
+
+The custom variable `gud-rdebug-command-name' sets the command
+and options used to invoke rdebug."
   (interactive
    (list (gud-query-cmdline 'rdebug)))
 

  "Regular expression used to find a file location given by rdebug.

Program-location lines look like this:
   /tmp/gcd.py:29:  gcd
   /tmp/gcd.py:29
   \\sources\\capfilterscanner\\capanalyzer.py:3:  <module>
")

(defconst rdebug-marker-regexp-file-group 2


We look first to visit the file indicated in the trace.

Failing that, we look for the most recently visited ruby-mode buffer
with the same name or having having the named function.

If we're unable find the source code we return a string describing the
problem as best as we can determine."
