bug-ncurses
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Two issues with using ncurses with "gdb -tui" on Windows


From: Thomas Dickey
Subject: Re: Two issues with using ncurses with "gdb -tui" on Windows
Date: Fri, 2 Jan 2015 10:40:54 -0500
User-agent: Mutt/1.5.20 (2009-06-14)

On Wed, Dec 31, 2014 at 08:08:55PM +0200, Eli Zaretskii wrote:
> Well, I actually am not sure these are ncurses problems, they could
> well be application-level issues in GDB.  But I have to start
> somewhere, so I figured this place is as good as any ;-)
> 
> I've built GDB 7.8.1 with the Text-mode User Interface (TUI) support
> on MS-Windows, using ncurses 5.9 as the curses library.  The result is
> working quite well, but I bumped into 2 issues:
> 
>  . When GDB displays a string with embedded TAB characters, ncurses
>    displays an IBM graphics character instead of an appropriate number
>    of spaces.  Is this a problem to be solved in ncurses, and if so,
>    is there any existing feature to request such a TAB expansion?  Or
>    is this an unportable assumption in GDB, and should be handled
>    there?

From the context, and your followup email to mingw-users, I think you're
talking about the case when ncurses isn't running, e.g,. gdb is using
stdio directly.  If gdb were using ncurses, the tab would be converted
to spaces.
 
>  . The arrow and other keypad keys do not work in the GDB command
>    window.  When that window is active, GDB calls the 'keypad'
>    function with the 2nd argument FALSE.  As result, it looks like
>    ncurses stops sending any valid code for these special keys (other
>    keys, like ASCII characters, and control characters, like Ctrl-p,
>    continue to work).  Does ncurses support disabling the keypad mode
>    on MS-Windows, and if so, what should the application do to ensure
>    this support?

Normally (unless some application does something), those keys do not send
characters.  I've thought about providing dummy strings (e.g., to match some
existing terminal), but arguably it's correct as is, and without knowing how an
application might use the strings, I don't see a need to change ncurses.

-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]