fredizzimo
fredizzimo
To expand on that, I think the move behaviour is only visible due to the fact that we use animations, the sporadic moves are mostly just one or two frames...
I'm going to merge this to get more feedback before the release.
@9mm, I think the idiomatic way of doing it would be to provide multiple entry points in the homebrew scripts like `macVim` does: * https://github.com/neovide/neovide/issues/2147#issuecomment-1934204719
@9mm, I think it should be `/Users/zesty/.cargo/bin/neovide -- -c ':cd ~/Desktop'`
@falcucci, do you have any ideas? For me on Linux the cd command works correctly.
@halostatue, if you really want it to fork by default you can set the environment variable `NEOVIDE_FORK=1`. As discussed in https://github.com/neovide/neovide/issues/2147, programs that fork are the exception, not the rule....
And I don't want to maintain and tie any homebrew scripts to the release cycle of Neovide. They are totally independent and should be maintained elsewhere. We could consider a...
The Neovide command is *not* provided by us, we only provide `Neovide.dmg`. The neovide executable is provided through homebrew, and this formula https://github.com/Homebrew/homebrew-core/blob/451533c52463b62ba5c56c1c761bc704337f7ef1/Formula/n/neovide.rb. I have no idea who maintains it.
@9mm, I don't really know what's being asked for either. But here's my attempt to explain, how I think it should work. There can be several entrypoints in homebrew, and...
@9mm, I will check if there's some bug with the environment variable parsing or something