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 [thread overview]
Message-ID: <199903060638.WAA29974@alabama.wrs.com> (raw)
In-Reply-To: <199903060607.BAA11685@banzai3.insignia.org>
> I'm playing with emacs's gud.el to make it display some stuff from
> gdb in other buffers. The problem is that the commands used to get the
> data go into gdb's history, which is not intended. I looked for some
> option for temporarily bypassing command history, but didn't find anything.
>
> It seems that DDD is able to do this. I looked at its source for a bit,
> but didn't see anything special it's doing.
>
> Does anyone know if there's a way to do what I'm talking about, or how
> DDD seems to manage to do it?
I have the code you need, but it is currently tied to a custom command we
use here.
It is easy for me to implement a whole new command that is like 'print' or
'inspect' but does not add to the value history, and submit the patches.
Would this work for you?
--
Todd Whitesel
toddpw @ wrs.com
next prev 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 [this message]
[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
1999-04-01 0:00 ` Todd Sabin
1999-04-01 0:00 ` Jim Blandy
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
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=199903060638.WAA29974@alabama.wrs.com \
--to=toddpw@wrs.com \
--cc=gdb@cygnus.com \
--cc=tastas@home.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