From mboxrd@z Thu Jan  1 00:00:00 1970
From: Todd Sabin <tastas@home.com>
To: tromey@cygnus.com
Cc: gdb@cygnus.com
Subject: Re: keeping commands out of the history 
Date: Thu, 01 Apr 1999 00:00:00 -0000
Message-id: <199903062105.QAA16766@banzai3.insignia.org>
References: <87u2vz2h5d.fsf@cygnus.com>
X-SW-Source: 1999-q1/msg00092.html

> >>>>> "Todd" == Todd Sabin <tastas@home.com> writes:
> 
> Todd> This sounds good, but I also want to do 'info registers',
> Todd> 'where', and probably 'info breakpoints' in the future, so I'm
> Todd> really looking for something a little more general.
> 
> I don't think any of these add to the value history.
> Or was that not what you were asking for?
> 

No, I'm talking about both the command and value history.  I want to
be able to send commands to and receive output from gdb without it
having any impact on what someone typing commands at the prompt sees.
Currently, if I type 'next' at the gdb prompt, it gets executed and my
hooks do, e.g., 'info registers', and put the output in a different buffer.
If I then type '<RET>' at the gdb prompt, it runs 'info registers' again,
not 'next'.  I want to it run 'next'.


Todd