Closed ayamir closed 3 hours ago
cc @CharlesChiuGit could you kindly provide some insights on this? I'm currently doing some cleanup but I'm stuck and can't seem to find a clue for this. Thanks!
cc @CharlesChiuGit could you kindly provide some insights on this? I'm currently doing some cleanup but I'm stuck and can't seem to find a clue for this. Thanks!
sorry, i forgot to reply! let me take a look!
After #1235 is merged, we probably also need to:
Keybindings.md
(Wiki)Plugins.md
(Wiki)alpha.lua
dots.tutor
(Lesson 1.2)cc @ayamir @CharlesChiuGit Shall we proceed with merging this PR after we:
?
cc @ayamir @CharlesChiuGit Shall we proceed with merging this PR after we:
- Update all the wikis (see feat!: nvim v0.10 supportΒ #1260 (comment))
- Draft the release note
- Merge in feat&refactor: make format timeout configurable, refactor format-related options.Β #1275
?
Agree.
agree
https://github.com/ayamir/nvimdots/wiki/Plugins#scopes
plugin list updated, but the "internal relationship" graph haven't.
@Jint-lzxy how can i draw this plot?
@CharlesChiuGit Sry I don't have the time to explain this in detail right now (probably will tomorrow). Essentially, it's in Graphviz format, and u can find the source code in the Disclosure Summary, right below the Legend (search for "Source code in Graphviz format"). However, I don't recommend manual editing as it was generated with my YAML parser (which isn't public), so it might not be very user-friendly :( You'll need a functioning Graphviz compiler (or an online version) with the "dot" engine and "svg" as the output format (the DOT language specification is here). If this seems too complex, I can refactor that page tomorrow lol
If this seems too complex, I can refactor that page tomorrow lol
ok, i brain is melting :exploding_head: . i'll leave it to u loool
for Keybindings wiki
, i only need to update the keymaps i think it's important, right?
actucally, i think we should just put the links of keymap configs.
https://github.com/ayamir/nvimdots/wiki/Keybindings
done
@misumisumi can u update https://github.com/ayamir/nvimdots/wiki/NixOS-Support ? ref: #1250 #1252
OK. Work today.
I've rewritten the wiki, could you please check it?
I've rewritten the wiki, could you please check it?
tho i just casted an eye on it, but it looks great! tks for your effort!
lazy.nvim
just released it's 11.x version.
Maybe we need to take a look at it?
Especially this part:
Spec Resolution & Merging: the code that resolves a final spec from a plugin's fragments has been rewritten. This should be a tiny bit faster, but more importantly, fixes some issues and is easier to maintain.
I'm sorry it's so close to release...
Now, nixos support allows you to choose whether or not to place lazy-lock.json
under nix
management.
If you put it under management, it will be difficult for users to update it, but you can control it more strictly.
As an intermediate method for this, you can place lazy-lock.json
managed by nix
as lazy-lock.nix.json
in $XDG_CONFIG_DIR/nvim
, and use lazy-lock.json
when changing the configuration. I think it is possible to provide an option to copy to json.
The advantage is that lazy.nvim
makes it easy to update and add plugins.
The disadvantage is that even if you obtain a newer version locally, it will overwrite the lazy-lock.json
that is managed by nix.
Do you have any good thoughts on this?
Spec Resolution & Merging: the code that resolves a final spec from a plugin's fragments has been rewritten. This should be a tiny bit faster, but more importantly, fixes some issues and is easier to maintain.
At least the user settings part does not depend on lazy.nvim, so I don't think it will be a problem. I took a look at the relevant commit, and I think the reason for this is that maintenance has become easier because parts of the processing are now managed in separate files.,
I've finished revising the FAQ; it should now include more information for expert users π€
Finally made up my mind to redo the dependencies diagram lol it really sucks in its own way, given the MANY changes since my last update (thanks to my own laziness lmao π).
lazy.nvim
just released it's 11.x version. Maybe we need to take a look at it? Especially this part:Spec Resolution & Merging: the code that resolves a final spec from a plugin's fragments has been rewritten. This should be a tiny bit faster, but more importantly, fixes some issues and is easier to maintain.
@CharlesChiuGit Just checked it out, but I don't think we need to make any changes. It affects how lazy.nvim
internally merges plugin specs, whereas our merging happens even before lazy.nvim
is loaded lol
Do you have any good thoughts on this?
@misumisumi How about creating a sym / hard link?
How about creating a sym / hard link?
My idea is ...
Now,
.
βββ init.lua -> /nix/store/foobar-home-manager-files/.config/nvim/init.lua
βββ lazy-lock.json -> /nix/store/foobar-home-manager-files/.config/nvim/lazy-lock.json
βββ lua -> /nix/store/foobar-home-manager-files/.config/nvim/lua
βββ snips -> /nix/store/foobar-home-manager-files/.config/nvim/snips
βββ tutor -> /nix/store/foobar-home-manager-files/.config/nvim/tutor
change,
{
# actualy, provide as option
home.activation.lazyLockActivatioinAction = lib.hm.dag.entryAfter [ "writeBoundary" ] ''
cp ${config.xdg.configHome}/nvim/lazy-lock.nix.json ${config.xdg.configHome}nvim/lazy-lock.json
'';
}
.
βββ init.lua -> /nix/store/foobar-home-manager-files/.config/nvim/init.lua
βββ lazy-lock.nix.json -> /nix/store/foobar-home-manager-files/.config/nvim/lazy-lock.json
βββ lazy-lock.json
βββ lua -> /nix/store/foobar-home-manager-files/.config/nvim/lua
βββ snips -> /nix/store/foobar-home-manager-files/.config/nvim/snips
βββ tutor -> /nix/store/foobar-home-manager-files/.config/nvim/tutor
This is not something that is urgent, so there is no problem if you pass it up for now.
cp ${config.xdg.configHome}/nvim/lazy-lock.nix.json ${config.xdg.configHome}nvim/lazy-lock.json
lol i finally knew what u meant.
yeah, i think it's a nice way to keep track of the upstream changes while keeping the flexibility to lazy.nvim
.
it's just few line changes in the code and some in the doc. i think we can put this in before this pr got merged.
add #1310's discription to wiki
I'm currently drafting a release note lol
Do u guys accord to add our configuration to neovimcraft? It would help promote it as well lol
the link seems to be private?
the link seems to be private?
Oops, I thought collaborators should be able to view that. Anyway, here it is lol
```markdown
## SUMMARY
This release is **not** backwards-compatible since Neovim 0.10 [has been officially released](https://github.com/neovim/neovim/releases/tag/v0.10.0). While many changes have occurred since the last release, here are a few notable ones:
- The license has officially been changed to the [BSD 3-Clause License](https://www.tldrlegal.com/license/bsd-3-clause-license-revised). It allows you almost unlimited freedom with the software so long as you include the BSD copyright and license notice in it.
- The install scripts **no longer** support Neovim 0.7, and that branch is no longer maintained. The 0.8 branch is also deprecated.
- The [LSP inlay hints](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) feature has been implemented and is enabled by default. Disable it in your user settings by specifying `settings["lsp_inlayhints"] = false`.
- The wiki pages and `dotstutor` have been significantly updated. Check them out!
- NixOS support has been extensively refactored. Refer to the [wiki](https://github.com/ayamir/nvimdots/wiki/NixOS-Support) page [and](https://github.com/ayamir/nvimdots/pull/1250) [relevant](https://github.com/ayamir/nvimdots/pull/1212) [PRs](https://github.com/ayamir/nvimdots/pull/1310) for details.
- Performance restrictions for Treesitter have been relaxed, as incremental parsing is now supported in 0.10. Please kindly report any performance issues encountered, as testing has been limited to a few devices.
- The built-in completion engine has updated its completion parameters. See #1279 for details.
- [cmp-buffer](https://github.com/hrsh7th/cmp-buffer) will now provide completion results from the texts in all opened buffers.
- Go development experience has been greatly improved. See #1226 for details.
- Horizontal terminals will no longer obscure [nvim-tree](https://github.com/nvim-tree/nvim-tree.lua).
- `
i think this pr is ready to gooooo
Do u guys accord to add our configuration to neovimcraft? It would help promote it as well lol
Done! Check out https://github.com/rockerBOO/awesome-neovim/pull/1238 π₯³
There are few problems need to be solved.
[x] #1245
[x] use
vim.region
to get selection text.Nvim 0.10 changes are in here: https://neovim.io/doc/user/news-0.10.html