Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@cygnus.com>
To: gdb@cygnus.com
Subject: Re: keeping commands out of the history
Date: Thu, 01 Apr 1999 00:00:00 -0000	[thread overview]
Message-ID: <87ww0v2h6c.fsf@cygnus.com> (raw)
In-Reply-To: <199903060638.WAA29974.cygnus.gdb@alabama.wrs.com>

>>>>> "Todd" == Todd Whitesel <toddpw@wrs.com> writes:

Todd> It is easy for me to implement a whole new command that is like
Todd> 'print' or 'inspect' but does not add to the value history, and
Todd> submit the patches.  Would this work for you?

It's already been done:

    creche. gdb
    GNU gdb 4.17.2
    Copyright 1998 Free Software Foundation, Inc.
    GDB is free software, covered by the GNU General Public License, and you are
    welcome to change it and/or distribute copies of it under certain conditions.
    Type "show copying" to see the conditions.
    There is absolutely no warranty for GDB.  Type "show warranty" for details.
    This GDB was configured as "i686-pc-linux-gnu".
    (gdb) help output
    Like "print" but don't put in value history and don't print newline.
    This is useful in user-defined commands.

Tom


  parent reply	other threads:[~1999-04-01  0:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-01  0:00 Todd Sabin
1999-04-01  0:00 ` Todd Whitesel
1999-04-01  0:00   ` Todd Sabin
1999-04-01  0:00     ` Todd Whitesel
1999-04-01  0:00     ` Jim Blandy
1999-04-01  0:00       ` Todd Sabin
     [not found]   ` <199903060659.BAA13499.cygnus.gdb@banzai3.insignia.org>
1999-04-01  0:00     ` Tom Tromey
1999-04-01  0:00       ` Todd Sabin
1999-04-01  0:00         ` Todd Whitesel
1999-04-01  0:00           ` Todd Sabin
1999-04-01  0:00             ` Todd Whitesel
     [not found] ` <199903060638.WAA29974.cygnus.gdb@alabama.wrs.com>
1999-04-01  0:00   ` Tom Tromey [this message]
1999-04-01  0:00     ` Todd Whitesel

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=87ww0v2h6c.fsf@cygnus.com \
    --to=tromey@cygnus.com \
    --cc=gdb@cygnus.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