public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/16138] layout asm when run from emacs exits gdb complaining "Error opening terminal: emacs"
Date: Tue, 12 Nov 2013 10:17:00 -0000	[thread overview]
Message-ID: <bug-16138-4717-oMEOqr4xBS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16138-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16138

--- Comment #6 from Pedro Alves <palves at redhat dot com> ---
initscr is actually documented to do that.

  http://pubs.opengroup.org/onlinepubs/7908799/xcurses/initscr.html

Should be using newterm directly instead of initscr.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-11-12 10:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 16:33 [Bug tui/16138] New: " xdje42 at gmail dot com
2013-11-11 11:36 ` [Bug tui/16138] " palves at redhat dot com
2013-11-11 11:36 ` palves at redhat dot com
2013-11-12  4:47 ` xdje42 at gmail dot com
2013-11-12  9:49 ` palves at redhat dot com
2013-11-12  9:52 ` palves at redhat dot com
2013-11-12 10:17 ` palves at redhat dot com [this message]
2013-11-23 20:28 ` xdje42 at gmail dot com
2013-11-25  9:26 ` palves at redhat dot com
2013-11-25  9:26 ` [Bug tui/16138] TUI commands when run from emacs exit " palves at redhat dot com
2013-12-15 21:40 ` b.r.longbons at gmail dot com
2013-12-16  9:54 ` palves at redhat dot com
2013-12-18  1:42 ` b.r.longbons at gmail dot com
2014-10-29 14:34 ` cvs-commit at gcc dot gnu.org
2014-10-29 14:52 ` cvs-commit at gcc dot gnu.org
2014-10-29 14:53 ` palves at redhat dot com
2014-12-25  0:46 ` cvs-commit at gcc dot gnu.org

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=bug-16138-4717-oMEOqr4xBS@http.sourceware.org/bugzilla/ \
    --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).