From mboxrd@z Thu Jan  1 00:00:00 1970
From: toddpw@wrs.com (Todd Whitesel)
To: tastas@home.com (Todd Sabin)
Cc: gdb@cygnus.com
Subject: Re: keeping commands out of the history
Date: Thu, 01 Apr 1999 00:00:00 -0000
Message-id: <199903062315.PAA12479@alabama.wrs.com>
References: <199903062105.QAA16766@banzai3.insignia.org>
X-SW-Source: 1999-q1/msg00093.html

> 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'.

Perhaps what you really want is for _hooks_ to be kept out of the value
history. That sounds to me like a good thing, if it isn't already true.

-- 
Todd Whitesel
toddpw @ wrs.com