non-nil if the buffer is to be saved), and any other non-@code{nil}
value means that all buffers should be saved without asking.
- In addition to the normal compilation mode commands (for
-next/previous match and so on), two additional commands are available
-for accessing the @command{grep} command history. @kbd{l}
-(@code{grep-backward-history}) will re-run successively the previous
-@command{grep} commands, and @kbd{r} (@code{grep-forward-history}
-will go ``forward'' in the command history.
-
@findex grep-find
@findex find-grep
The command @kbd{M-x grep-find} (also available as @kbd{M-x
@cindex fringes, for debugging
@table @asis
-@item @kbd{Mouse-1} (in fringe)
+@item @kbd{mouse-1} (in fringe)
Set or clear a breakpoint on that line.
-@item @kbd{C-Mouse-1} (in fringe)
+@item @kbd{C-mouse-1} (in fringe)
Enable or disable a breakpoint on that line.
-@item @kbd{Mouse-3} (in fringe)
+@item @kbd{mouse-3} (in fringe)
Continue execution to that line.
-@item @kbd{C-Mouse-3} (in fringe)
+@item @kbd{C-mouse-3} (in fringe)
Jump to that line.
@end table
- On a graphical display, you can click @kbd{Mouse-1} in the fringe of
+ On a graphical display, you can click @kbd{mouse-1} in the fringe of
a source buffer, to set a breakpoint on that line (@pxref{Fringes}).
A red dot appears in the fringe, where you clicked. If a breakpoint
-already exists there, the click removes it. A @kbd{C-Mouse-1} click
+already exists there, the click removes it. A @kbd{C-mouse-1} click
enables or disables an existing breakpoint; a breakpoint that is
disabled, but not unset, is indicated by a gray dot.
A solid arrow in the left fringe of a source buffer indicates the
line of the innermost frame where the debugged program has stopped. A
hollow arrow indicates the current execution line of a higher-level
-frame. If you drag the arrow in the fringe with @kbd{Mouse-1}, that
+frame. If you drag the arrow in the fringe with @kbd{mouse-1}, that
causes execution to advance to the line where you release the button.
-Alternatively, you can click @kbd{Mouse-3} in the fringe to advance to
-that line. You can click @kbd{C-Mouse-3} in the fringe to jump to
+Alternatively, you can click @kbd{mouse-3} in the fringe to advance to
+that line. You can click @kbd{C-mouse-3} in the fringe to jump to
that line without executing the intermediate lines. This command
allows you to go backwards, which can be useful for running through
code that has already executed, in order to examine its execution in
Visit the source line for the current breakpoint
(@code{gdb-goto-breakpoint}).
-@item Mouse-2
-@kindex Mouse-2 @r{(GDB Breakpoints buffer)}
+@item mouse-2
+@kindex mouse-2 @r{(GDB Breakpoints buffer)}
Visit the source line for the breakpoint you click on.
@end table
@vindex gdb-show-threads-by-default
When @code{gdb-many-windows} is non-@code{nil}, the GDB Breakpoints
buffer shares its window with the GDB Threads buffer. To switch from
-one to the other click with @kbd{Mouse-1} on the relevant button in
+one to the other click with @kbd{mouse-1} on the relevant button in
the header line. If @code{gdb-show-threads-by-default} is
non-@code{nil}, the GDB Threads buffer is the one shown by default.
debugged program. @xref{Threads, Threads, Debugging programs with
multiple threads, gdb, The GNU debugger}. To select a thread, move
point there and press @key{RET} (@code{gdb-select-thread}), or click on
-it with @kbd{Mouse-2}. This also displays the associated source
+it with @kbd{mouse-2}. This also displays the associated source
buffer, and updates the contents of the other GDB buffers.
You can customize variables under @code{gdb-buffers} group to select
arrow in the fringe. On text terminals, or when fringes are disabled,
the selected stack frame is displayed in reverse contrast. To select
a stack frame, move point in its line and type @key{RET}
-(@code{gdb-frames-select}), or click @kbd{Mouse-2} on it. Doing so
+(@code{gdb-frames-select}), or click @kbd{mouse-2} on it. Doing so
also updates the Locals buffer
@ifnottex
(@pxref{Other GDB Buffers}).
This buffer displays the values of local variables of the current
frame for simple data types (@pxref{Frame Info, Frame Info,
Information on a frame, gdb, The GNU debugger}). Press @key{RET} or
-click @kbd{Mouse-2} on the value if you want to edit it.
+click @kbd{mouse-2} on the value if you want to edit it.
Arrays and structures display their type only. With GDB 6.4 or later,
you can examine the value of the local variable at point by typing
-@key{RET}, or with a @kbd{Mouse-2} click. With earlier versions of
-GDB, use @key{RET} or @kbd{Mouse-2} on the type description
+@key{RET}, or with a @kbd{mouse-2} click. With earlier versions of
+GDB, use @key{RET} or @kbd{mouse-2} on the type description
(@samp{[struct/union]} or @samp{[array]}). @xref{Watch Expressions}.
@item Registers Buffer
@findex toggle-gdb-all-registers
This buffer displays the values held by the registers
(@pxref{Registers,,, gdb, The GNU debugger}). Press @key{RET} or
-click @kbd{Mouse-2} on a register if you want to edit its value. With
+click @kbd{mouse-2} on a register if you want to edit its value. With
GDB 6.4 or later, recently changed register values display with
@code{font-lock-warning-face}.
@item Memory Buffer
The memory buffer lets you examine sections of program memory
(@pxref{Memory, Memory, Examining memory, gdb, The GNU debugger}).
-Click @kbd{Mouse-1} on the appropriate part of the header line to
+Click @kbd{mouse-1} on the appropriate part of the header line to
change the starting address or number of data items that the buffer
displays. Alternatively, use @kbd{S} or @kbd{N} respectively. Click
-@kbd{Mouse-3} on the header line to select the display format or unit
+@kbd{mouse-3} on the header line to select the display format or unit
size for these data items.
@end table
When @code{gdb-many-windows} is non-@code{nil}, the locals buffer
shares its window with the registers buffer, just like breakpoints and
threads buffers. To switch from one to the other, click with
-@kbd{Mouse-1} on the relevant button in the header line.
+@kbd{mouse-1} on the relevant button in the header line.
@node Watch Expressions
@subsubsection Watch Expressions
address as a tooltip to help identify the frame in which they were
defined.
- To expand or contract a complex data type, click @kbd{Mouse-2} or
+ To expand or contract a complex data type, click @kbd{mouse-2} or
press @key{SPC} on the tag to the left of the expression. Emacs asks
for confirmation before expanding the expression if its number of
immediate children exceeds the value of the variable
@findex gdb-edit-value
To edit a variable with a simple data type, or a simple element of a
complex data type, move point there in the speedbar and type @key{RET}
-(@code{gdb-edit-value}). Or you can click @kbd{Mouse-2} on a value to
+(@code{gdb-edit-value}). Or you can click @kbd{mouse-2} on a value to
edit it. Either way, this reads the new value using the minibuffer.
@vindex gdb-show-changed-values