Bug#347774: does not handle resize on startup properly (same as #146210?)

2006-01-12 Thread Simon Richter
Package: xterm Version: 208-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, it appears as if that old bug has reappeared. When the windowmanager gives back a different ConfigureNotify than what was initially requested, the shell process needs to be sent a SIGWINCH. Simon

Bug#347774: does not handle resize on startup properly (same as #146210?)

2006-01-12 Thread Thomas Dickey
On Thu, Jan 12, 2006 at 05:20:30PM +0100, Simon Richter wrote: > Package: xterm > Version: 208-1 > Severity: normal > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > it appears as if that old bug has reappeared. When the windowmanager > gives back a different ConfigureNotify than w

Bug#347774: does not handle resize on startup properly (same as #146210?)

2006-01-13 Thread Simon Richter
Hi, Thomas Dickey wrote: it appears as if that old bug has reappeared. When the windowmanager gives back a different ConfigureNotify than what was initially requested, the shell process needs to be sent a SIGWINCH. That put a different thought in my head than the similar ion3 report. But jus

Bug#347774: does not handle resize on startup properly (same as #146210?)

2006-01-13 Thread Thomas Dickey
On Fri, Jan 13, 2006 at 12:10:28PM +0100, Simon Richter wrote: > Hi, > > Thomas Dickey wrote: > > >>it appears as if that old bug has reappeared. When the windowmanager > >>gives back a different ConfigureNotify than what was initially > >>requested, the shell process needs to be sent a SIGWINCH.

Bug#347774: does not handle resize on startup properly (same as #146210?)

2006-01-23 Thread Thomas Dickey
On Thu, Jan 12, 2006 at 05:20:30PM +0100, Simon Richter wrote: > Package: xterm > Version: 208-1 > Severity: normal > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > it appears as if that old bug has reappeared. When the windowmanager > gives back a different ConfigureNotify than w