nixvim
nixvim copied to clipboard
plugins/cord-nvim: init
Adds the cord-nvim plugin.
For more info view the plugin homepage: https://github.com/vyfor/cord.nvim.
fixes: #2373
Note: It's work in progress as I need to do most of the options
don't feel obligated to add all the options, you can simply add options that are likely to be used by all users of this plugin
error: build of '/nix/store/d7pw4yq7y1bc28l12kf8lkmms7nr8pkr-defaults.drv' on 'ssh-ng://[email protected]' failed: builder for '/nix/store/d7pw4yq7y1bc28l12kf8lkmms7nr8pkr-defaults.drv' failed with exit code 1;
last 9 log lines:
> ERROR: Error detected while processing /nix/store/80ylygcwnlkhbmwysfpygb01sbs10p6z-init.lua:
> E5113: Error while calling lua chunk: /nix/store/80ylygcwnlkhbmwysfpygb01sbs10p6z-init.lua:9: module 'cord-nvim' not found:
> no field package.preload['cord-nvim']
> no file '/nix/store/h25v2irfigii5xby44ff7jwfj5sfh06d-luajit-2.1.1713773202-env/share/lua/5.1/cord-nvim.lua'
> no file '/nix/store/h25v2irfigii5xby44ff7jwfj5sfh06d-luajit-2.1.1713773202-env/share/lua/5.1/cord-nvim/init.lua'
> no file '/nix/store/h25v2irfigii5xby44ff7jwfj5sfh06d-luajit-2.1.1713773202-env/lib/lua/5.1/cord-nvim.so'
> stack traceback:
> [C]: in function 'require'
> /nix/store/80ylygcwnlkhbmwysfpygb01sbs10p6z-init.lua:9: in main chunk
For full logs, run 'nix log /nix/store/d7pw4yq7y1bc28l12kf8lkmms7nr8pkr-defaults.drv'.
error: build of '/nix/store/d7pw4yq7y1bc28l12kf8lkmms7nr8pkr-defaults.drv' on 'ssh-ng://[email protected]' failed: builder for '/nix/store/d7pw4yq7y1bc28l12kf8lkmms7nr8pkr-defaults.drv' failed with exit code 1; last 9 log lines: > ERROR: Error detected while processing /nix/store/80ylygcwnlkhbmwysfpygb01sbs10p6z-init.lua: > E5113: Error while calling lua chunk: /nix/store/80ylygcwnlkhbmwysfpygb01sbs10p6z-init.lua:9: module 'cord-nvim' not found: > no field package.preload['cord-nvim'] > no file '/nix/store/h25v2irfigii5xby44ff7jwfj5sfh06d-luajit-2.1.1713773202-env/share/lua/5.1/cord-nvim.lua' > no file '/nix/store/h25v2irfigii5xby44ff7jwfj5sfh06d-luajit-2.1.1713773202-env/share/lua/5.1/cord-nvim/init.lua' > no file '/nix/store/h25v2irfigii5xby44ff7jwfj5sfh06d-luajit-2.1.1713773202-env/lib/lua/5.1/cord-nvim.so' > stack traceback: > [C]: in function 'require' > /nix/store/80ylygcwnlkhbmwysfpygb01sbs10p6z-init.lua:9: in main chunk For full logs, run 'nix log /nix/store/d7pw4yq7y1bc28l12kf8lkmms7nr8pkr-defaults.drv'.
Yeah still can't figure out how to fix the issue.
Ops.
Sorry, I edited my suggestion, Didn't mean to remove the originalName
Dropped the commit.
don't feel obligated to add all the options, you can simply add options that are likely to be used by all users of this plugin
Well I am trying to add all of the options but it shouldn't be too hard to manage as options hasn't been changed in ages.
I will work on more of the options tmr I need to sleep.
I didn't have time today but I will look into add more options asap.
don't feel obligated to add all the options, you can simply add options that are likely to be used by all users of this plugin
Well I am trying to add all of the options but it shouldn't be too hard to manage as options hasn't been changed in ages.
Just to clarify, the reason we don't need to declare all upstream options is that settings is a "freeform" option.
That means users can configure anything under plugins.*.settings even if we don't declare a corresponding option.
In fact, any options declared actually add additional restrictions due to their type checking. So when we do declare options we must ensure the type is permissive enough to allow users to configure anything upstream may allow.
Hey @khaneliman Is it normal for docs not building manual using the docs & serve-docs command in shell?
Logs:
warning: ignoring untrusted substituter 'https://nix-community.cachix.org', you are not a trusted user.
Run `man nix.conf` for more information on the `substituters` configuration option.
error: builder for '/nix/store/hk274n3racxlcxzs635c09wz2qd2lxka-nuscht-search-pnpm-deps.drv' failed with exit code 1;
last 10 log lines:
> at ClientRequest.emit (node:events:519:28)
> at emitErrorEvent (node:_http_client:108:11)
> at TLSSocket.socketErrorListener (node:_http_client:511:5)
> at TLSSocket.emit (node:events:531:35)
> at emitErrorNT (node:internal/streams/destroy:169:8)
> at emitErrorCloseNT (node:internal/streams/destroy:128:3)
> at processTicksAndRejections (node:internal/process/task_queues:82:21)
> at runNextTicks (node:internal/process/task_queues:64:3)
> at listOnTimeout (node:internal/timers:545:9)
> Progress: resolved 946, reused 0, downloaded 944, added 944
For full logs, run 'nix-store -l /nix/store/hk274n3racxlcxzs635c09wz2qd2lxka-nuscht-search-pnpm-deps.drv'.
error: 1 dependencies of derivation '/nix/store/rjam0130s3wsas7sdyyr7pjlcyvzm639-nuscht-search-0.0.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/1fwhi44fv1ksqbkc5j92jpnxmn8r80dh-nuscht-search.drv' failed to build
error: 1 dependencies of derivation '/nix/store/vy73i7z7fgqvq10nnb7brwfnxiv82l7s-nixvim-docs.drv' failed to build
Cause I am building docs manually to see where I need to improve. I am also doing this to clarify for myself this comment
Is it normal for docs not building manual using the
docs&serve-docscommand in shell?
If you're on darwin (OSX) then we disable the docs because mdbook has an upstream issue. Otherwise no, that could be a bug.
- Are you on darwin?
- Do you only see this issue on your branch, or is it on
maintoo?
Is it normal for docs not building manual using the
docs&serve-docscommand in shell?If you're on darwin (OSX) then we disable the docs because mdbook has an upstream issue. Otherwise no, that could be a bug.
* Are you on darwin? * Do you only see this issue on your branch, or is it on `main` too?
I am on x86_64-linux I just pulled the changes from main and rebased my branch so this is a bug.
Is it normal for docs not building manual using the
docs&serve-docscommand in shell?If you're on darwin (OSX) then we disable the docs because mdbook has an upstream issue. Otherwise no, that could be a bug.
* Are you on darwin? * Do you only see this issue on your branch, or is it on `main` too?
but also what issue is on darwin cause I want to debug the issue as I have a darwin machine.
You can see in docs/default.nix where we disable it using optionalAttrs (!pkgs.stdenv.isDarwin):
https://github.com/nix-community/nixvim/blob/3c7b6ae5d1524c691a1b65f7290facd0dc296e40/docs/default.nix#L68-L90
I'm not too familiar, but it's an upstream issue. If you do want to look into that, let's deal with it in another issue as I don't want it to distract from landing the changes here.
Is it normal for docs not building manual using the
docs&serve-docscommand in shell?If you're on darwin (OSX) then we disable the docs because mdbook has an upstream issue. Otherwise no, that could be a bug.
* Are you on darwin? * Do you only see this issue on your branch, or is it on `main` too?I am on
x86_64-linuxI just pulled the changes from main and rebased my branch so this is a bug.
Also would that be a bug?
I'm able to serve-docs on main and this branch.
Weird for some reason it fails.
I'm able to serve-docs on main and this branch.
Both this branch and upstream are not working on x86_64-linux.
I'm able to serve-docs on main and this branch.
I have made an issue on their end to see if they can fix it.
I am going to work on getting the options finished then sqrash then it will be ready to review.
I am about to start squashing my commits and provide settings that I only need.
I might wait until v2 comes out before merging this as a lot of options change.
I will start implementing v2 options.
As this PR was stalling for the past few months, I took the initiative to go and finish it up.
As we tend to avoid explicitly declaring plugin options, I have chosen to only add settingsExample.
@mergifyio queue
queue
✅ The pull request has been merged automatically
The pull request has been merged automatically at 8ffda5afb163ff9604e34c0af552693dc76ed4e0
This pull request, with head sha 8ffda5afb163ff9604e34c0af552693dc76ed4e0, has been successfully merged with fast-forward by Mergify.
This pull request will be automatically closed by GitHub.
As soon as GitHub detects that the sha 8ffda5afb163ff9604e34c0af552693dc76ed4e0 is part of the main branch, it will mark this pull request as merged.
It is possible for this pull request to remain open if this detection does not happen, this usually happens when a force-push is done on this branch plugins/cord-nvim, this means GitHub will fail to detect the merge.