neovide: doesn't start on Win10 with nvim-nightly
Hi, I wanted to check neovide but it doesn’t start for me.
I use neovim-nightly, installed via scoop (it works ok as a standalone and embedded as a firenvim in firefox)
NVIM v0.5.0-330-g71ee46acc
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe /DW...ects/neovim/src -IC:/projects/nvim-deps/usr/include -IC:/projects/neovim/build/src/nvim/auto -IC:/projects/neovim/build/include
Compiled by appveyor@APPVYR-WIN
Features: -acl +iconv +tui
See ":help feature-compile"
system vimrc file: "$VIM\sysinit.vim"
fall-back for $VIM: "C:/Program Files/nvim/share/nvim"
Run :checkhealth for more info
When I start neovide.exe
nothing pops up, I can see a process of neovide but that is it.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 69 (39 by maintainers)
I will definitely do this, but I also think its important the init script errors don’t freeze things. I will look into it. Probably won’t get to it tonight though (its late here)
Hello @Kethku i am having a prbl that is when i try run neovide it just pop’s a window for a second then it disapperes
Can you pls help me out
i tried running neovide --log the output is
thread ‘main’ panicked at ‘called
Result::unwrap()
on anErr
value: NoAvailablePixelFormat’, src\window\mod.rs:290:10 note: run withRUST_BACKTRACE=1
environment variable to display a backtracei have build neovide form source
waiting for your reply
Closing as stale. If you get back to this, please upload the file created when you run neovide with --log and reopen.
I had the same problem with pre-built binary on Windows 10 with scoop neovim. I worked around by building from source.
On Wed, 29 Jan 2020 at 13:34, Keith Simmons notifications@github.com wrote:
– Aravind
Hmmm thats interesting… That might be causing the problem. I will try this soon. I’m putting out other fires atm 😉