Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Jim Blandy <jimb@codesourcery.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sourceware.org
Subject: Re: $_ and info breakpoint [PATCH: doco]
Date: Wed, 11 Jul 2007 22:56:00 -0000	[thread overview]
Message-ID: <18069.24580.179474.972686@kahikatea.snap.net.nz> (raw)
In-Reply-To: <m3bqei24dj.fsf@codesourcery.com>

 > > This shouldn't affect existing use and we can put a caveat in the
 > > documentaion in the manual:
 > >
 > >                        The convenience variable `$_' and the default
 > >      examining-address for the `x' command are set to the address of
 > >      the last breakpoint listed unless the command is prefixed with
 > >      'server ' (see Command History).
 > 
 > I have no warlord M-DEL patch, but I just wanted to point out that
 > 'server' should be documented more clearly than it is.

How about this?  (adapted fron the "Server Prefix" node in annotate.texinfo)

-- 
Nick                                           http://www.inet.net.nz/~nickrob


2007-07-12  Nick Roberts  <nickrob@snap.net.nz>

	* gdb.texinfo (Server Prefix): New node.  Adapt from existing node
        in annotate.texinfo.
        (Command History): Link to new node.


*** gdb.texinfo	04 Jul 2007 17:37:49 +1200	1.420
--- gdb.texinfo	12 Jul 2007 10:50:38 +1200	
*************** package, to provide the history facility
*** 15436,15442 ****
  Interactively}, for the detailed description of the History library.
  
  To issue a command to @value{GDBN} without affecting certain aspects of
! the state which is seen by users, prefix it with @samp{server }.  This
  means that this command will not affect the command history, nor will it
  affect @value{GDBN}'s notion of which command to repeat if @key{RET} is
  pressed on a line by itself.
--- 15436,15443 ----
  Interactively}, for the detailed description of the History library.
  
  To issue a command to @value{GDBN} without affecting certain aspects of
! the state which is seen by users, prefix it with @samp{server }
! (@pxref{Server Prefix}).  This
  means that this command will not affect the command history, nor will it
  affect @value{GDBN}'s notion of which command to repeat if @key{RET} is
  pressed on a line by itself.
*************** This is Edition @value{EDITION}, @value{
*** 21241,21246 ****
--- 21242,21248 ----
  
  @menu
  * Annotations Overview::  What annotations are; the general syntax.
+ * Server Prefix::       Issuing a command without affecting user state.
  * Prompting::           Annotations marking @value{GDBN}'s need for input.
  * Errors::              Annotations for error messages.
  * Invalidation::        Some annotations describe things now invalid.
*************** Here @samp{quit} is input to @value{GDBN
*** 21319,21324 ****
--- 21321,21340 ----
  denotes a @samp{control-z} character) are annotations; the rest is
  output from @value{GDBN}.
  
+ @node Server Prefix
+ @section The Server Prefix
+ @cindex server prefix for annotations
+ 
+ If you prefix a command with @samp{server } then it will not affect
+ the command history, nor will it affect @value{GDBN}'s notion of which
+ command to repeat if @key{RET} is pressed on a line by itself.  This
+ means that commands can be run behind a user's back by a front-end in
+ a transparent manner.
+ 
+ The server prefix does not affect the recording of values into the value
+ history; to print a value without recording it into the value history,
+ use the @code{output} command instead of the @code{print} command.
+ 
  @node Prompting
  @section Annotation for @value{GDBN} Input
  


  reply	other threads:[~2007-07-11 22:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18064.7905.924535.720690@kahikatea.snap.net.nz>
     [not found] ` <20070709115647.GC3095@caradoc.them.org>
2007-07-10  0:22   ` $_ and info breakpoint [PATCH] Nick Roberts
2007-07-10  1:43     ` Daniel Jacobowitz
2007-07-10  3:20       ` Eli Zaretskii
2007-07-10 11:20         ` Daniel Jacobowitz
2007-07-10 23:11           ` Nick Roberts
2007-07-10 23:51             ` Daniel Jacobowitz
2007-07-11  0:35               ` Nick Roberts
2007-07-11 11:32                 ` Daniel Jacobowitz
2007-07-11 18:15     ` Jim Blandy
2007-07-11 22:56       ` Nick Roberts [this message]
2007-07-12  3:19         ` $_ and info breakpoint [PATCH: doco] Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18069.24580.179474.972686@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox