Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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: <199903062343.PAA12932@alabama.wrs.com> (raw)
In-Reply-To: <199903062326.SAA17173@banzai3.insignia.org>

> 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


  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 [this message]
     [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=199903062343.PAA12932@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