-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only blank window shown when launching #53
Comments
Same here. Using Windows 10 14352 insider build. |
Same problem here, too... except did you switch "expected" and "actual" behavior? I'm on OS X 10.11.5
|
Yeah. Whoops. Hope it's obvious from context |
FWIW I see this error in the devloper console (and nothing else):
|
I have the same problem, with the same error as noted by @gwerbin. Has anyone found a solution to this? Maybe reverting to an older version of Neovim? |
Any updates on this? |
Personally, the issue I had was related to my |
@gosukiwi I tried renaming/disabling both my |
I'm getting this issue in Ubuntu. I was able to print a stacktrace:
Renaming |
The error looks to occur here: I'll try this on Windows8 machine (I don't have Windows10 machine). |
I reproduced this although the error message is not the same:
|
I am having the same problem on Debian Jessie, using nvim 0.1.1 . |
Please upadte Neovim. Currently |
Confirmed on my Arch Linux x64 with Gnome.
Run it with
It seems that this bug is probably caused by deadlock. Single step result: |
I have the same issue.
Nyaovim package.json:
System info:
Issue persist with nyaovim 0.0.18, 0.0.16, 0.0.14. |
Same issue with Kubuntu 16.04. More details:
I try to provide as many details as possible that may be the cause of the bug, perhaps you guys can notice any patterns? maybe nvm, anyone with this issue uses nvm? |
Seeing the same behavior. It's also interesting that if I launch
|
Same issue with nvim 0.1.6 and nyaovim 0.0.21 under Windows 7 x64
|
Same issue with Mac OSX 10.11.6 + neovim 0.1.5
|
Reverting nyaovim to 0.0.20, both Windows 7 and Mac environment work now.
|
Correct. NyaoVim now works well with If you have some reason not to use nvim HEAD, please continue to use NyaoVim v0.0.20 until nvim v0.1.6 stable is released. |
Fixed after upgrading nyaovim from 0.0.20 to 0.0.21. |
@jordwalke Yes, as I commented in above, my
|
I think there's an issue between 0.1.6-104 to 0.1.6-14x. That's only different |
Let me organize 'white screen' issue here. There are two kinds of error in this issue.
So, @raacker, if you can reproduce the 'Cannot read property' error even if updating the latest version (v0.1.6-104-g22dfe69), could you create a new issue for it? |
Okay! I'l work on it today and if it still has that issue, I'll create one :) Thank you! |
@raacker Thank you so much for your confirmation. So some v0.1.6 doesn't work and need to be updated to the latest... I understood 😄 |
@rhysd Yeah, I have the exact same
|
Oh, I didn't get the log. It may be the root cause. Could you please try below?
|
That got rid of that message, thanks. It did not get rid of the white screen problem though. |
How do I try a different version of Electron to see if it works? |
Thank you for your try. Hmm...
It may dump many logs to stderr.
I guess:
|
|
You mean no log is output to stderr?
Maybe 1.3.5? 😃 |
Tried with |
I'm experiencing this problem, but DevTools can be launched and no errors at all in its console.
Isn't the correct env var Still no helpful logs on my mechine though. $ ELECTRON_ENABLE_LOGGING=true NODE_ENV=debug nyaovim --no-detach
[7500:0929/113819:ERROR:browser_main_loop.cc(239)] GTK theme error: Unable to locate theme engine in module_path: "murrine", (This error message seems unrelated - installing |
Thank you for confirmation. Hmm... So it's not dependent on Electron version. Anyway, we need to solve this for Electron v1.4.1 because we can't stay in v1.3 to catch up the latest Electron updates. Thank you for confirmation.
Oh, you're absolutely right.
is correct to gather all debug information for now. When |
I inserted if (browser_config.loaded_config.show_menubar === false) { // <===
win.setMenuBarVisibility(false);
} So the problem (on my machine, probably) is the configuration not loaded or something. I created $ echo '{}' > ~/.config/nyaovim/browser-config.json and NyaoVim worked 😄 |
Nice! Thank you so much for your debug. I'll fix this issue and release nyaovim v0.0.22 tonight! |
Hey, with my setup above (latest everything including nvim, electron, nyaovim) the |
You mean that white screen at first, then it shows the screen after enter key? If so, I guess some messages are echoed by |
I don't even have to press enter. I just wait a second and the white screen goes away. |
I think it's just a loading time. Electron is a customized Chromium browser. So it takes a bit to start up renderer process. In addition, NyaoVim spawn |
Yeah, I'm not super bothered by it. But it would be nice to be able to customize the color of the screen eventually (you could even read the bg color of the colorscheme at last application-quit time, and use that for the bg color at startup time while waiting for Chromium to load). Chances are, it's the color you want to see there (not 100% of the time, but most of the time). |
NyaoVim's entry point is a HTML file ( |
I fixed this bug and published new version of NyaoVim. Please update and confirm the fix. Thank you so much for reporting, confirming and debugging 😄 |
Confirmed, it works on Linux |
It works on
|
Wow... It really works! Thanks you for everyone in here :p |
Expected Behavior
When running nyaovim from the command prompt, only a blank window is launched. Does not respond to input.
Actual Behavior
NyaoVim launches as expected
Steps to Reproduce (including precondition)
Install NyaoVim using "npm install -g nyaovim". Open a command prompt and type nyaovim
Screenshot on This Problem (if possible)
{Please write here}
Your Environment
nvim
version: {0.1.5-dev}Additional Comments (if any)
Neovim-qt works as expected. Using the MSVC 2015 - compiled version of nvim (the MSYS version wouldn't work with neovim-qt or nyaovim)
The text was updated successfully, but these errors were encountered: