On 14-mrt-2006, at 19:00, Nicholas Cole wrote:
> I couldn't find anything in the archives related to this.
>
> Using both Apple's python and a build of python2.4.2, there seems to
> be a bug when using ncurses. curses.newwin() is supposed to give a
> new window filling the pysical terminal, but
> Terminal.app behaives particularly strangely -
crashing when the
> window is enlarged for the second time (xterm
crashes immediately),
> though not the first
For me, it crashes in Terminal.app the first time I
try to enlarge the window, not the second. I see no
difference between Terminal and xt
I'm still trying to investigate this problem with resizing terminals.
I've found a method which can reliably determine the size of the
terminal on OS X (not completely tested), which is to do the
following:
struct.unpack('hh', fcntl.ioctl(sys.stdout.fileno(),
termios.TIOCGWINSZ, ''))
However
On 14-mrt-2006, at 19:00, Nicholas Cole wrote:
> I couldn't find anything in the archives related to this.
>
> Using both Apple's python and a build of python2.4.2, there seems to
> be a bug when using ncurses. curses.newwin() is supposed to give a
> new window filling the pysical terminal, but
I couldn't find anything in the archives related to this.
Using both Apple's python and a build of python2.4.2, there seems to
be a bug when using ncurses. curses.newwin() is supposed to give a
new window filling the pysical terminal, but if the terminal has been
resized this does not seem to hap
