-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
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
editors/nvim: fix missing example folder issue in remote testing #450
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix missing test folder issue in remote testing
What is 'remote testing' and what is exactly 'missing test folder' issue?
'remote testing': the nvim test environment defined by the remote repository When I pull the necessary definitions from the remote repository and create the nvim test environment I get the following problem: So I've added a way to handle this: when it can't find the example folder locally, it pulls this test example from the git repo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. However looks like you are trying to use the flake to setup nixos + home-manager options, why not write builtins.fetchTarball
-like expressions in the neovim, so thus you don't need to do such "fetching flake to /tmp" ugly stuff.
"expr": "builtins.fetchTarball ..."
Oh, I got it. |
Note that Document how to write home-manager configuration, and separate a new "devShell" dedicated for |
In terms of how to configure it, I don't think it's necessary to start another devShell on how to write a home-manager configuration. The purpose of the devShells.nvim configuration here is one thing: to experience the beauty of nixd in the easiest way possible for the user. Although the current way of pulling the examples directory from the repository is ugly, the fact that users can use our examples locally makes it very easy for them to experience the power of |
During the first time nixd lauches, the flake inputs will be fetched from the internet, this is rather slow. Run |
If so,then we can tell the user when we start the editor that nixd will be slow the first time we start it. |
Okay, I agree. |
No description provided.