public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pedro at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/9660] gdb can enter TUI in Emacs
Date: Mon, 19 Apr 2010 00:37:00 -0000	[thread overview]
Message-ID: <20100419003732.4242.qmail@sourceware.org> (raw)
In-Reply-To: <20081118170801.9660.tromey@redhat.com>


------- Additional Comments From pedro at codesourcery dot com  2010-04-19 00:37 -------
Maybe just forbit the TUI also when annotations are in use?

That is, add an `annotation_level' check here (tui/tui-interp.c):

/* True if enabling the TUI is allowed.  Example, if the top level
   interpreter is MI, enabling curses will certainly lose.  */

int
tui_allowed_p (void)
{
  /* Only if TUI is the top level interpreter.  Also don't try to
     setup curses (and print funny control characters) if we're not
     outputting to a terminal.  */
  return tui_is_toplevel && ui_file_isatty (gdb_stdout);
}

The `tui_is_toplevel' check means that the new emacs version
that has switched to MI no longer has this problem.  Only
current/older versions using annotations may still have to
be tended for, unless emacs doesn't run gdb with a tty,
in which case this is fixed already by the ui_file_isatty check
shown above.  Could you check if you can still reproduce this?


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |WAITING


http://sourceware.org/bugzilla/show_bug.cgi?id=9660

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


       reply	other threads:[~2010-04-19  0:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081118170801.9660.tromey@redhat.com>
2010-04-19  0:37 ` pedro at codesourcery dot com [this message]
     [not found] <bug-9660-4717@http.sourceware.org/bugzilla/>
2015-07-02 13:29 ` palves at redhat dot com

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=20100419003732.4242.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).