If I have a command with the following Ruby code:
require ENV['TM_SUPPORT_PATH'] + '/lib/ui' result = [{ 'match' => 'foo', 'display' => 'foo' }] TextMate::UI.complete(result)
If I type "f" and then invoke the command the completion menu appears as expected, containing "foo". If I type a non-matching character, like "s" then it takes around three seconds for the menu to disappear and the "s" to appear in the editor.
Not sure if it's related, but if I select some other text in the meantime the "s" appears immediately.
— /Jacob Carlborg
On 6 Aug 2016, at 20:49, Jacob Carlborg wrote:
If I type "f" and then invoke the command the completion menu appears as expected, containing "foo". If I type a non-matching character, like "s" then it takes around three seconds for the menu to disappear and the "s" to appear in the editor.
100% reproducible? Not seeing it myself, neither with your code or the Objective-C completion.
Not sure if it's related, but if I select some other text in the meantime the "s" appears immediately.
What if you just move the mouse?
There are some edge cases where the event loop does not automatically wake up even though there is a pending event, here moving the mouse would wake the event loop.
On 07 Aug 2016, at 16:05, Allan Odgaard mailinglist@textmate.org wrote:
100% reproducible? Not seeing it myself, neither with your code or the Objective-C completion.
It was 100% reproducible on the computer (10.10) where I found the problem. On this computer (10.11) I cannot reproduce the issue. I can comeback to you when I have access to the 10.10 computer again.
— /Jacob Carlborg
It was 100% reproducible on the computer (10.10) where I found the problem. On this computer (10.11) I cannot reproduce the issue. I can comeback to you when I have access to the 10.10 computer again.
I can still reproduce it on the 10.10 computer, 100% reproducible. I also just updated to 2.0-beta.12.4 which did not help. Is there something I can do to debug the problem?
On 19 Aug 2016, at 21:20, Jacob Carlborg wrote:
I can still reproduce it on the 10.10 computer, 100% reproducible. I also just updated to 2.0-beta.12.4 which did not help. Is there something I can do to debug the problem?
How to debug it? Run sample when it hangs? Insert some NSLog statements with time stamp to figure out where the code hangs?
-
Allan Odgaard -
Jacob Carlborg