We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've used it on all platforms , but mainly on my Mac M1
Common Issues that you guys will face
neovide
Solution: create Alias neovide , paste it on your zshrc/bashrc
function neovide(){ ARG="${1:-.}" CUR="$(pwd)" FILE="${CUR}/${ARG}" PATH=$(env) NEOVIDE_CWD=$(pwd) open -a Neovide.app --args $(pwd) }
This happens since Neovide runs on Sandbox on MacOS
The above snippets only fixes half of the problem.
CWD gets initialized is nil , you can check by running this
:lua print(vim.fn.getcwd())
So Most Plugins , Like Neo-Tree, Terminal etc that uses the vim.fn.getcwd() have issues your opening on the root folder
If using neovim with lua scripts, add the snippet on your initialization of the script , ie. lazy.lua
lazy.lua
-- only set if NEOVIDE_CWD is set if vim.fn.getenv("NEOVIDE_CWD") then vim.api.nvim_set_current_dir(vim.fn.getenv("NEOVIDE_CWD")) end
For normal vim/nvim script
if !empty($NEOVIDE_CWD) " Change the current working directory to the value of NEOVIDE_CWD execute "cd" $NEOVIDE_CWD endif
If your Rust users like me on mac, you can simple use my Nvim Configuration...
https://github.com/codeitlikemiley/nvim
That allows you to move quickly around panes, test and debug with Rust at ease...
Note all those Extra key bindings on rust only triggers if on rust project.
I think my config is 100% Better than with VSCODE with Rust :)
Hope you like it and Star thanks
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Solution on related issue: https://github.com/neovide/neovide/issues/1982
Ive been Using Neovide for Rust DevelopmentI've used it on all platforms , but mainly on my Mac M1
Common Issues that you guys will face
neovide
cliSolution: create Alias neovide , paste it on your zshrc/bashrc
This happens since Neovide runs on Sandbox on MacOS
The above snippets only fixes half of the problem.
CWD gets initialized is nil , you can check by running this
:lua print(vim.fn.getcwd())
So Most Plugins , Like Neo-Tree, Terminal etc that uses the vim.fn.getcwd() have issues your opening on the root folder
For us to fix that issue...
neovide
aliasIf using neovim with lua scripts, add the snippet on your initialization of the script , ie.
lazy.lua
For normal vim/nvim script
If your Rust users like me on mac, you can simple use my Nvim Configuration...
https://github.com/codeitlikemiley/nvim
That allows you to move quickly around panes, test and debug with Rust at ease...
Note all those Extra key bindings on rust only triggers if on rust project.
I think my config is 100% Better than with VSCODE with Rust :)
Hope you like it and Star thanks
The text was updated successfully, but these errors were encountered: