oni-bot[bot]
commented
6 years ago Hello and welcome to the Oni repository! Thanks for opening your first issue here. To help us out, please make sure to include as much detail as possible - including screenshots and logs, if possible.
jaawerth
Love the editor - it's great to see a project that's come this far in taking advantage of Neovim's remote capabilities! I generally go back and forth between this and regular Neovim in the shell, but I've noticed the following problem:
The issue
When launching in the background from the shell (to, say, open it in the current directory) without blocking the tty),
oni &causes the editor to open stuck on a blank screen.topshows one or more runaway shell processes using 100% CPU. It remains this way until I either kill the runaway processes orfg %onito bring it back into the foreground, at which point oni is able to fully initialize and starts working normally. I can then pause from the shell withctrl-zand background + disown it, I simply can't open + background + disown it in a single command, at least without waiting a bit.Further exploration
I've tried a few variations on this (including
nohupand redirecting stderr/stdout) without any luck, as well as disabling the use of myinit.vimand using stock oni configuration. The same thing does not seem to occur in plain neovim.I've heard a couple people mention similar issues in other electron apps, so I thought it might be an electron issue, but I tried starting a base electron app in the background and that didn't seem to have any trouble... though it's possible an electron app that doesn't really do anything isn't going to reproduce the issue.
Environment
0.3.1(also experienced with previous versions, though I don't believe I've had this behavior since I first started using the editor)Thanks!