emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] Changes to emacs/man/building.texi [emacs-unicode-2]


From: Miles Bader
Subject: [Emacs-diffs] Changes to emacs/man/building.texi [emacs-unicode-2]
Date: Sat, 04 Sep 2004 05:50:53 -0400

Index: emacs/man/building.texi
diff -c emacs/man/building.texi:1.31.2.2 emacs/man/building.texi:1.31.2.3
*** emacs/man/building.texi:1.31.2.2    Mon Jun 28 07:29:00 2004
--- emacs/man/building.texi     Sat Sep  4 09:14:25 2004
***************
*** 23,30 ****
                            with different facilities for running
                            the Lisp programs.
  * Libraries: Lisp Libraries.      Creating Lisp programs to run in Emacs.
- * Interaction: Lisp Interaction.  Executing Lisp in an Emacs buffer.
  * Eval: Lisp Eval.      Executing a single Lisp expression in Emacs.
  * External Lisp::         Communicating through Emacs with a separate Lisp.
  @end menu
  
--- 23,30 ----
                            with different facilities for running
                            the Lisp programs.
  * Libraries: Lisp Libraries.      Creating Lisp programs to run in Emacs.
  * Eval: Lisp Eval.      Executing a single Lisp expression in Emacs.
+ * Interaction: Lisp Interaction.  Executing Lisp in an Emacs buffer.
  * External Lisp::         Communicating through Emacs with a separate Lisp.
  @end menu
  
***************
*** 204,209 ****
--- 204,217 ----
  buffer and finds no more error messages to visit, it fails and signals
  an Emacs error.
  
+   You don't have to be in the compilation buffer in order to use
+ @code{next-error}.  If one window on the selected frame can be the
+ target of the @code{next-error} call, it is used.  Else, if a buffer
+ previously had @code{next-error} called on it, it is used.  Else,
+ if the current buffer can be the target of @code{next-error}, it is
+ used.  Else, all the buffers Emacs manages are tried for
+ @code{next-error} support.
+ 
    @kbd{C-u C-x `} starts scanning from the beginning of the compilation
  buffer.  This is one way to process the same set of errors again.
  
***************
*** 644,650 ****
  @menu
  * Layout::               Control the number of displayed buffers.
  * Breakpoints Buffer::   A breakpoint control panel.
! * Stack Buffer::         Select a frame from the call stack. 
  * Watch Expressions::    Monitor variable values in the speedbar.
  * Other Buffers::        Input/output, locals, registers and assembler 
buffers.
  @end menu
--- 652,658 ----
  @menu
  * Layout::               Control the number of displayed buffers.
  * Breakpoints Buffer::   A breakpoint control panel.
! * Stack Buffer::         Select a frame from the call stack.
  * Watch Expressions::    Monitor variable values in the speedbar.
  * Other Buffers::        Input/output, locals, registers and assembler 
buffers.
  @end menu
***************
*** 698,709 ****
  @node Breakpoints Buffer
  @subsubsection Breakpoints Buffer
  
! The breakpoints buffer shows the existing breakpoints and watchpoints 
  (@pxref{Breakpoints,,, gdb, The GNU debugger}).  It has three special
  commands:
  
  @table @kbd
! @item @key{SPC} 
  @kindex SPC @r{(GDB breakpoints buffer)}
  @findex gdb-toggle-breakpoint
  Enable/disable the breakpoint at the current line
--- 706,717 ----
  @node Breakpoints Buffer
  @subsubsection Breakpoints Buffer
  
! The breakpoints buffer shows the existing breakpoints and watchpoints
  (@pxref{Breakpoints,,, gdb, The GNU debugger}).  It has three special
  commands:
  
  @table @kbd
! @item @key{SPC}
  @kindex SPC @r{(GDB breakpoints buffer)}
  @findex gdb-toggle-breakpoint
  Enable/disable the breakpoint at the current line




reply via email to

[Prev in Thread] Current Thread [Next in Thread]