On 2014/01/13 12:41, Philip Guenther wrote:
> On Mon, 13 Jan 2014, Gregor Best wrote:
> > The patch below seems to fix that for me. resizeterm() does a
> > putchar(KEY_RESIZE), part of which then gets interpreted as a command
> > parameter in rundisplay().
>
> I think you meant "ungetch(KEY_RESI
On Mon, Jan 13, 2014 at 12:41:19PM -0800, Philip Guenther wrote:
> [...]
> I think you meant "ungetch(KEY_RESIZE)",
> [...]
You're right.
> [...]
> seems to fix the problem in my testing.
> [...]
Works for me too.
--
Gregor Best
On Mon, 13 Jan 2014, Gregor Best wrote:
> On Mon, Jan 13, 2014 at 05:04:28PM +, Stuart Henderson wrote:
> > If anyone is interested in looking at a signal problem in top,
> > here's a small but annoying bug..
> >
> > - run top in an xterm
> > - resize the window
> > - try to use an interactive
On 13/01/14 12:04 PM, Stuart Henderson wrote:
If anyone is interested in looking at a signal problem in top,
here's a small but annoying bug..
- run top in an xterm
- resize the window
- try to use an interactive command that takes an argument, e.g. "s"
or "g" (doesn't happen with commands like
On Mon, Jan 13, 2014 at 05:04:28PM +, Stuart Henderson wrote:
> If anyone is interested in looking at a signal problem in top,
> here's a small but annoying bug..
>
> - run top in an xterm
> - resize the window
> - try to use an interactive command that takes an argument, e.g. "s"
> or "g" (do
If anyone is interested in looking at a signal problem in top,
here's a small but annoying bug..
- run top in an xterm
- resize the window
- try to use an interactive command that takes an argument, e.g. "s"
or "g" (doesn't happen with commands like "S" or "H" that work immediately)
Often, pressi
