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
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
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
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.
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
5 matches
Mail list logo