Closed kopischke closed 3 years ago
It seems to be that the Atom window can never get the focus? Try clicking on it maybe?
Ha, yeah, should have mentioned I did that as a matter of course :). I can click the window into the foreground, I can resize it, and the OS X window management bubbles respond to hover, but even with the window in the apparent foreground, all issues described in my original post are still present.
Is there any way I can get a log of what happens? The two console messages depicted in the screenshot aren’t very helpful…
You can log the event by changing these event handlers: https://github.com/coolwanglu/neovim.as/blob/master/src/nvim/ui.coffee#L120
I didn't find relevant issues in Atom Shell repo, can you run other Atom Shell apps?
can you run other Atom Shell apps?
I’d be happy to test, but I’m not aware of any (assuming you don’t means Atom itself, which runs fine) – do you happen to have a suggestion for me?
Oh in fact I don't know other Atom Shell apps.
I quickly reviewed the code again but did not find anything wrong, it might be about os x 10.10? (I'm using 10.9 which works fine).
Maybe you can try to hack the event listeners first, if there's nothing printed, it'll be more likely a bug of Atom Shell.
OK, so it seems to be a generic issue with Atom Shell, at least with my setup. I updated Atom Shell to the latest release (0.21.2) and tested again with another shell app. That turned out to be responsive to mouse input, but also ignores keyboard input and has the same activation / focus issues as Neovim.AS. It looks like something blocks Atom Shell from detaching properly, as I cannot start an Atom Shell instance via the app bundle once the shell app runs...
I’ve also tried disabling keyboard input hacks (specifically, Seil and Karabiner) and switching to US keyboard input, but none of that helped.
As I know diddly-squat about the Atom Shell API and only a little more than that about CoffeeScript, I’ll give up on getting Neovim.AS to run.
@kopischke You might file an issue for Atom Shell, the developers might be able to fix it.
I filed an issue; you’ll see I have narrowed it down to Atom Shell apps launched via the CLI.
@kopischke Thanks!
@coolwanglu the base issue has been narrowed down to atom-shell
being a symlink (see https://github.com/atom/atom-shell/issues/1151#issuecomment-92085514).
@kopischke Thanks! That sounds like a really tricky bug.
I’ve run into an odd issue where I can start Neovim.AS, but cannot get its window to accept keyboard input; instead, all keyboard input goes to the terminal in which Neovim.AS was started.
I also can’t switch to the window with
Cmd-Tab
, its OS X menu does not display, and the only way to quit it is issuing^C
in the originating shell.Configuration:
grunt -v
inside the neovim.as directory gives no errors