Ivan, Bernard, I could have a look at it next week, after I reinstalled FreeBSD and GNUstep, if I manage to get lldb working.
Currently, lldb is just showing what i suppose to be the unicodes of the keys I press, but is not reacting to <ENTER> [edwin@ottopedi ~]$ lldb38 Terminal.core (lldb) target create "Terminal.core" Current executable set to 'Terminal.core' (i386). (lldb) \U+7A662\U+7A674\U+7A60A\U+7A60A\U+7A60A\U+7A60A\U+7A60A\U+7A60A\U+7A608\U+7A608\U+7A608 gdb does not seem to work with the core files from clang. Mind you, I might have more questions than answers, being unexperienced with the tools. Kind regards, Edwin 2017-11-08 22:31 GMT+01:00 Ivan Vučica <[email protected]>: > > > On Wed, Nov 8, 2017 at 8:59 AM, Bertrand gmail < > [email protected]> wrote: > >> >> >> 2017-11-08 04:14:47.981 Terminal[1388:100275] Problem posting >> notification: <NSException: 0x2c7c5d10> NAME:NSInvalidArgumentException >> REASON:[Rik-fillRect:withTiles:background:fillStyle:] rect width is not >> positive INFO:(null ) >> >> >> This is a know bug with themes that don't use standard tabs (Rik, >> Nesedah, Narcissus). The only workaround I've found is not to use tabs in >> Terminal. >> > > Negative rect width seems pretty bad both on the side of -gui (should it > throw an exception?) and on the side of the app (should it be causing > things to create negative width rects?) > > E.g the above exception originates from: https://github.com/gnustep/ > libs-gui/blob/master/Source/GSThemeTools.m#L506 > > Something has been setting the width to negative before this exception. > > > >> >> You can change the ShowTabBar setting for Terminal with : >> >> defaults write Terminal ShowTabBar NO >> >> But then don't open any new tab in Terminal or don't hit the #t and #T >> shortkeys again. >> The latter one's are problematic because I often use #t in GWorkspace to >> open a new Terminal window. >> >> I don't know if this bug is in Terminal itself or in gui. But I don't >> have any problem in GWorkspace for instance. >> >> Maybe some smart fellow on this list could correct this bug. I'm not able >> to do this. >> > > What did you try so far to track this down? > > _______________________________________________ > Discuss-gnustep mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnustep > >
_______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
