Skip to content
Discussion options

You must be logged in to vote

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:

  1. Configure xcodebuild.nvim to be lazy loaded (for example when you open first swift file).
  2. Use some dashboard plugin, make sure that it supports projects - you could use snacks.

This way, when you open Neovide,…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by craig-miller
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants