mirror/nix-community.nixvim
1
0
Fork 0
mirror of https://github.com/nix-community/nixvim.git synced 2025-07-13 10:44:34 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
nix-community.nixvim/tests/flake.lock

173 lines
4.5 KiB
Text
Raw Normal View History

nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
{
"nodes": {
"flake-utils": {
"locked": {
lspkind: init plugin
2022-11-10 18:22:45 +00:00
"lastModified": 1667395993,
"narHash": "sha256-nuEHfE/LcWyuSWnS8t12N1wc105Qtau+/OdUAjtQ0rA=",
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"owner": "numtide",
"repo": "flake-utils",
lspkind: init plugin
2022-11-10 18:22:45 +00:00
"rev": "5aed5285a952e0b949eb3ba02c12fa4fcfef535f",
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"type": "github"
},
"original": {
"owner": "numtide",
"repo": "flake-utils",
"type": "github"
}
},
"flake-utils_2": {
"locked": {
lspkind: init plugin
2022-11-10 18:22:45 +00:00
"lastModified": 1667395993,
"narHash": "sha256-nuEHfE/LcWyuSWnS8t12N1wc105Qtau+/OdUAjtQ0rA=",
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"owner": "numtide",
"repo": "flake-utils",
lspkind: init plugin
2022-11-10 18:22:45 +00:00
"rev": "5aed5285a952e0b949eb3ba02c12fa4fcfef535f",
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"type": "github"
},
"original": {
"owner": "numtide",
"repo": "flake-utils",
"type": "github"
}
},
Allow using global config with hm and nixos (#48) * remove useless nixvim file * reorganize flake outputs * use global config file with home-manager and nixos
2022-10-17 15:08:17 +02:00
"flake-utils_3": {
"locked": {
lspkind: init plugin
2022-11-10 18:22:45 +00:00
"lastModified": 1667395993,
"narHash": "sha256-nuEHfE/LcWyuSWnS8t12N1wc105Qtau+/OdUAjtQ0rA=",
Allow using global config with hm and nixos (#48) * remove useless nixvim file * reorganize flake outputs * use global config file with home-manager and nixos
2022-10-17 15:08:17 +02:00
"owner": "numtide",
"repo": "flake-utils",
lspkind: init plugin
2022-11-10 18:22:45 +00:00
"rev": "5aed5285a952e0b949eb3ba02c12fa4fcfef535f",
Allow using global config with hm and nixos (#48) * remove useless nixvim file * reorganize flake outputs * use global config file with home-manager and nixos
2022-10-17 15:08:17 +02:00
"type": "github"
},
"original": {
"owner": "numtide",
"repo": "flake-utils",
"type": "github"
}
},
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"nixpkgs": {
"locked": {
lsp-lines test
2022-10-10 15:21:57 +01:00
"lastModified": 1663491030,
"narHash": "sha256-MVsfBhE9US5DvLtBAaTRjwYdv1tLO8xjahM8qLXTgTo=",
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"owner": "NixOS",
"repo": "nixpkgs",
lsp-lines test
2022-10-10 15:21:57 +01:00
"rev": "767542707d394ff15ac1981e903e005ba69528b5",
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"type": "github"
},
"original": {
"id": "nixpkgs",
"type": "indirect"
}
},
add nixos-22.05 test
2022-10-04 15:04:22 +01:00
"nixpkgs-stable": {
"locked": {
lspkind: init plugin
2022-11-10 18:22:45 +00:00
"lastModified": 1668016843,
"narHash": "sha256-ioBuF+IAhmJO7s4ewEij1LkMxJvCCNCKXxMto/DU02I=",
add nixos-22.05 test
2022-10-04 15:04:22 +01:00
"owner": "NixOS",
"repo": "nixpkgs",
lspkind: init plugin
2022-11-10 18:22:45 +00:00
"rev": "fa842715565307b7e05cdb187b08c05f16ed08f1",
add nixos-22.05 test
2022-10-04 15:04:22 +01:00
"type": "github"
},
"original": {
"owner": "NixOS",
"ref": "nixos-22.05",
"repo": "nixpkgs",
"type": "github"
}
},
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"nixpkgs_2": {
"locked": {
lsp-lines test
2022-10-10 15:21:57 +01:00
"lastModified": 1663491030,
"narHash": "sha256-MVsfBhE9US5DvLtBAaTRjwYdv1tLO8xjahM8qLXTgTo=",
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"owner": "NixOS",
"repo": "nixpkgs",
lsp-lines test
2022-10-10 15:21:57 +01:00
"rev": "767542707d394ff15ac1981e903e005ba69528b5",
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"type": "github"
},
"original": {
"id": "nixpkgs",
"type": "indirect"
}
},
"nixvim": {
"inputs": {
"flake-utils": "flake-utils_2",
"nixpkgs": "nixpkgs_2",
"nmdSrc": "nmdSrc"
},
"locked": {
"lastModified": 0,
trouble.nvim: init
2022-11-15 10:14:43 +00:00
"narHash": "sha256-b5FuoFQsTCgKsVTQS13qmFnMmVotIQWtcjPu+WT6ubo=",
"path": "/nix/store/m90wvnc3d4rci36q0r0j7d2i1sk35cgy-source",
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"type": "path"
},
"original": {
trouble.nvim: init
2022-11-15 10:14:43 +00:00
"path": "/nix/store/m90wvnc3d4rci36q0r0j7d2i1sk35cgy-source",
Allow using global config with hm and nixos (#48) * remove useless nixvim file * reorganize flake outputs * use global config file with home-manager and nixos
2022-10-17 15:08:17 +02:00
"type": "path"
}
},
"nixvim-stable": {
"inputs": {
"flake-utils": "flake-utils_3",
"nixpkgs": [
"nixpkgs-stable"
],
"nmdSrc": "nmdSrc_2"
},
"locked": {
"lastModified": 0,
trouble.nvim: init
2022-11-15 10:14:43 +00:00
"narHash": "sha256-b5FuoFQsTCgKsVTQS13qmFnMmVotIQWtcjPu+WT6ubo=",
"path": "/nix/store/m90wvnc3d4rci36q0r0j7d2i1sk35cgy-source",
Allow using global config with hm and nixos (#48) * remove useless nixvim file * reorganize flake outputs * use global config file with home-manager and nixos
2022-10-17 15:08:17 +02:00
"type": "path"
},
"original": {
trouble.nvim: init
2022-11-15 10:14:43 +00:00
"path": "/nix/store/m90wvnc3d4rci36q0r0j7d2i1sk35cgy-source",
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"type": "path"
}
},
"nmdSrc": {
"flake": false,
"locked": {
lspkind: init plugin
2022-11-10 18:22:45 +00:00
"lastModified": 1666190571,
"narHash": "sha256-Z1hc7M9X6L+H83o9vOprijpzhTfOBjd0KmUTnpHAVjA=",
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"owner": "rycee",
"repo": "nmd",
lspkind: init plugin
2022-11-10 18:22:45 +00:00
"rev": "b75d312b4f33bd3294cd8ae5c2ca8c6da2afc169",
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"type": "gitlab"
},
"original": {
"owner": "rycee",
"repo": "nmd",
"type": "gitlab"
}
},
Allow using global config with hm and nixos (#48) * remove useless nixvim file * reorganize flake outputs * use global config file with home-manager and nixos
2022-10-17 15:08:17 +02:00
"nmdSrc_2": {
"flake": false,
"locked": {
lspkind: init plugin
2022-11-10 18:22:45 +00:00
"lastModified": 1666190571,
"narHash": "sha256-Z1hc7M9X6L+H83o9vOprijpzhTfOBjd0KmUTnpHAVjA=",
Allow using global config with hm and nixos (#48) * remove useless nixvim file * reorganize flake outputs * use global config file with home-manager and nixos
2022-10-17 15:08:17 +02:00
"owner": "rycee",
"repo": "nmd",
lspkind: init plugin
2022-11-10 18:22:45 +00:00
"rev": "b75d312b4f33bd3294cd8ae5c2ca8c6da2afc169",
Allow using global config with hm and nixos (#48) * remove useless nixvim file * reorganize flake outputs * use global config file with home-manager and nixos
2022-10-17 15:08:17 +02:00
"type": "gitlab"
},
"original": {
"owner": "rycee",
"repo": "nmd",
"type": "gitlab"
}
},
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
"root": {
"inputs": {
"flake-utils": "flake-utils",
"nixpkgs": "nixpkgs",
add nixos-22.05 test
2022-10-04 15:04:22 +01:00
"nixpkgs-stable": "nixpkgs-stable",
Allow using global config with hm and nixos (#48) * remove useless nixvim file * reorganize flake outputs * use global config file with home-manager and nixos
2022-10-17 15:08:17 +02:00
"nixvim": "nixvim",
"nixvim-stable": "nixvim-stable"
nixvim: support standalone nixvim This represents a major rearchitecture for nixvim, so I'm leaving this up to track the progress for now, and to serve as a reference for any breaking changes during transition. The main change is, of course, being able to use nixvim standalone. To do this, you should use the new build function, which takes in two arguments: the system architecture (e.g. x86_64-linux) and the configuration. For the new configuration, do not use the programs.nixvim. prefix. For module development, the main change is that you should no longer prefix your modules with programs.nixvim..
2022-09-18 11:19:23 +01:00
}
}
},
"root": "root",
"version": 7
}
Reference in a new issue Copy permalink