Closed ylecuyer closed 9 years ago
I have similar experience, just blank screen full of ~
but nothing happens when I press some keys.
I just updated nvim to the latest neovim and atom-shell to latest versions.
I'm getting same error about running without the SUID sandbox although I don't really know what it means:
[12516:0214/153759:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[12516:0214/153759:INFO:audio_manager_pulse.cc(258)] Failed to connect to the context. Error: Connection refused
[12545:0214/153759:INFO:renderer_main.cc(211)] Renderer process started
[12516:0214/153759:INFO:CONSOLE(20)] "child process spawned: 12556", source: /home/neo/neovim.as/src/nvim/nvim.js (20)
I debugged that a little bit and apparently it's just drawing white on white. @get_cur_fg_color
returns #ffffff
.
To play with it you can just make nv_update_fg
a noop. That's because nvim sends it's fg_color, which happens to be white, to hi neovim.as. And so it's painting white on white.
Thanks, I changed nv_update_fg to return black and I'm able to test neovim.as
Let me try with latest neovim, some things might have been changed.
OK, as in python-client, -1
means to use a default color, I've fixed this in the master branch.
After a raw install all I get is blank screen and there is nothing I can do nor write.
There is the log I'm getting: