grabInput permanently changes the behavior of the term emulator. about terminal-kit

[cronvel]

Hi, can you provide me some code so I can test that?
What is your gnome version? Your distro?

I'm afraid, it works fine on mine.

You can test using the program: sample/all-event-test.js,
Also try using Ctrl-D during the test to switch from one mouse reporting to another.

[ashnur]

I tried all-event-test, it was working better than what I tried before, because there were no issues until I got to motion. But then this happened:

I only have part of gnome installed (so no overall gnome version), but my gnome-terminal is 3.16.2-1
I am using ArchLinux.

However, given the fact that your test is clearly working for me (at least the button and drag modes, which I need), I started thinking what else did I differently. Turns out, using nodemon causes the issue I was talking about. If I don't use nodemon, the issue goes away (apart from the breakages with the motion mode).

Now, I am not sure if this is a problem with terminal-kit or nodemon or neither, just bad luck, but I think we can close this issue for now.
Thanks for the help :).

[cronvel]

There are some chances that nodemon does not pass STDIN and STDOUT data as they are (i.e. performs some formatting, or spawn its own PTY, or whatever), thus interferes with escape sequences written back and forth.

However your screenshot is clearly a bug I should squash ;)

[ashnur]

Tell me if I can help you with that.

[cronvel]

I can't reproduce it but I made some improvement to avoid the whole app to crash if that happens again.
If you can reproduce it again, it should give us more informations.

[ashnur]

I did a pull and tried all-events again. Now, it didn't crash and quit the process, it just shows this:

[ashnur]

And in gnome-terminal, it doesn't happen, there it works. So it's probably terminology being broken in some way, if you could tell me what (as in, what standard or something) is not implemented or broken, I could make a request to the authors of terminology.

[cronvel]

Ok, I got it. The minus was ruining the parser. I don't know why they report a negative code here, it is supposed to be an unsigned integer. However, there isn't any real spec for mouse reporting, even invisible island does not give precise pointer.

I fixed that, assuming -1 is used by Terminology instead of the more common code 32 for mouse motion.

Now it should work accordingly.

Thank you for helping me fixing bug!

[ashnur]

It works well, thank you for fixing it.