Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix in features/Makefile
Date: Mon, 25 Aug 2008 12:12:00 -0000	[thread overview]
Message-ID: <20080825121201.GA17122@caradoc.them.org> (raw)
In-Reply-To: <m3myj1bv28.fsf@fleche.redhat.com>

On Sun, Aug 24, 2008 at 10:03:11PM -0600, Tom Tromey wrote:
> >>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
> 
> Daniel> stdout isn't a tty... dubious we should be doing this if it is.  I'm
> Daniel> not sure why you get tui here, though, I don't think I do.  Do you
> Daniel> have the gdbtui binary installed as gdb?
> 
> I passed the full path to the just-built gdb to make.
> 
> I looked at config.status and I didn't pass any argument to configure
> that would affect this.  I believe my build takes the enable_tui=auto
> branch and then finds all the prereqs.  So, I think this could affect
> anybody, depending on what devel packages they have installed.

Huh, you're right.  I get tui_init called too.

Ah, it's _rl_term_mm.  If your terminal has a meta character enable
sequence it will be output by tputs (smm/rmm).  Some versions of xterm
do.

Guess we shouldn't be initializing readline when stdout / stderr are
not a terminal...

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-08-25 12:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-24 18:12 Tom Tromey
2008-08-24 22:38 ` Daniel Jacobowitz
2008-08-25  0:03   ` Tom Tromey
2008-08-25  2:36     ` Daniel Jacobowitz
2008-08-25  4:04       ` Tom Tromey
2008-08-25 12:12         ` Daniel Jacobowitz [this message]
2008-10-06 20:39           ` Tom Tromey

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=20080825121201.GA17122@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.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