Neovide #373
-
|
I have Xcodebuild-nvim working great inside of the terminal. When I run it inside of Neovide, it doesn't find the xcodebuild config files in my project directory. If I open a terminal inside Neovide, it is in the correct project directory. It tells me to rerun XcodebuildSetup again. If I then run XcodebuildSetup, it finds my xcproject file, but doesn't find my devices. It seems to be looking for my devices inside of /Users/Craig/.nvim/xcodebuild/devices.json which doesn't exist because they are in the .nvim/xcodebuild directory of my current project path. Is there an xcodebuild-nvim config parameter that I can set to insure that it is looking in my current project directory for these config files? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Hi, I've just checked what's the problem. The thing is that xcodebuild.nvim initializes everything when the plugin is loaded, so the path already needs to be set to your project path. If you change it later, many things won't work properly. However, if you really need to do that you can reload the plugin with this command: #7 I'm not sure how you launch your neovide instance, but I'm quite sure that you could start it in a specific path. Alternatively, another solution also works:
This way, when you open Neovide, you should see the dashboard, the plugin shouldn't be loaded yet. Then you select your project, the dashboard changes your path and the plugin is loaded after that. In my case it works well. |
Beta Was this translation helpful? Give feedback.
-
|
I'm using Lazy.nvim, so as you suggested above, I just changed my keymaps to be under keys = {} and temporarily removed nvim-dap dependency on it. Checked with :Lazy to insure xcodebuild.nvim wasn't being loaded. Once I did that, I am able to build both when starting gvim (aliased to Neovide) from the terminal, or by launching Neovide via Raycast. I'll sort out the the rest of the keymaps for nvim-dap and I should be all set. I manage my projects through "coffebar/neovim-project". Which works great for bringing up the project with this setup. Thanks so much for the assist! |
Beta Was this translation helpful? Give feedback.
Hi, I've just checked what's the problem.
The thing is that xcodebuild.nvim initializes everything when the plugin is loaded, so the path already needs to be set to your project path. If you change it later, many things won't work properly. However, if you really need to do that you can reload the plugin with this command: #7
I'm not sure how you launch your neovide instance, but I'm quite sure that you could start it in a specific path.
Alternatively, another solution also works:
This way, when you open Neovide,…