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: <199903062343.PAA12932@alabama.wrs.com>
References: <199903062326.SAA17173@banzai3.insignia.org>
X-SW-Source: 1999-q1/msg00096.html

> Well, when I say hooks, I mean hooks in emacs; I'm not sure if that was clear.
> As far as gdb knows, they're normal commands.

Ah.

I'm not too familiar with the emacs/GDB hookup but I assume it involves
GDB's stdin being fed by emacs, or else you wouldn't have this problem.

The second input argument to command_line_input() (see gdb/top.c) is nonzero
to enable the return-repeat machinery. In 4.17 there is no set/show option.

You could define an escape sequence to be sent by emacs at the start of the
command, and slip some code into command_line_input() that searches for the
sequence, and if found deletes it while clearing the 'repeat' argument. That
would enable your emacs machinery to 'hide' any command that it wanted.

-- 
Todd Whitesel
toddpw @ wrs.com