Migrate to Nfnl #8
Conversation
Notable changes: - Migrates away from Aniseed - Update a few examples to use the latest Neovim APIs - Check-in generated files - Remove the sync script, lazy.nvim doesn't need it to update the plugins - Introduce a projections file to ease navigation and define common templates
The "goto file" command looks for relative paths, since we're transpiling lua from fennel, we want to consider fennel the source of truth when available. To do that, we need to update the `path`, `suffixesadd` and `includeexpr` options to help vim understand how to read fennel paths with lua fallbacks. See `:h gf`
| (lsp.pylsp.setup {}) | ||
| (lsp.bashls.setup {}) | ||
| (lsp.lua_ls.setup | ||
| {:settings {:Lua {:telemetry {:enable false}}}}))}) |
There was a problem hiding this comment.
I'm thinking about adding mason and mason-lspconfig to ensure these dependencies are installed. Thoughts?
There was a problem hiding this comment.
Yep I think that's a good pattern! I'm doing that over here + some other nice automatic things:
|
Oh nice, this is a great initiative, thanks! It definitely needed some love to bring it up to speed with all the modern plugins and ideas. This looks great and I'll take a proper look as soon as I can. I guess the only guiding principal I can give is this: This repo should be a jumping off point that handles a bunch of the fiddly early bootstrapping and essential decisions for the user. But it should not aim to be a distribution like Astro or Lazy etc, it's not a kitchen sink, it's a minimal starter pack 😄 So whatever you feel like doing that you think fits into that idea, I say go for it. I'll be happy to garden and merge it into this repo. Alternatively, if you want to fork and continue this under your own repo I'll also happily send people your way from this readme. |
I think I can trim out a few more plugins. Separately, the common feedback I hear from peers when looking at starter kits is feeling like they don't know where to start, I would love to bake a guided tour, in the same spirit as I'll give it some thought, maybe that can be its own plugin that "ejects" itself at the end of the tour. |
|
Agreed, they can be overwhelming. So keeping this minimal and a guided tour of some kind sounds fantastic. I suppose automating the traversal of something like oil.nvim could also be a good way to show the directory structure. And personally I lean away from automated ejection things because there's so much risk around accidentally overwriting or deleting something a user cared about. Also have to handle all the OS differences which might become quite a burden. I'd personally lean towards a demo mode that activates without install for the tour (like Conjure does) while also telling you where to drop the files to make it your own. Like with https://github.com/Olical/clojure-giants-shoulders/ - I personally like telling people to copy this code or fork and modify rather than having it be something more magical than that. I've run into issues with things that "eject" in the past and I've struggled to find the source I wanted to read because it wasn't where I thought it'd be or it was some sort of template that would eventually generate files on disk. That disconnect can be confusing. If the repo is instead exactly what you'll have in your own copy at the starting point, you can just browse exactly what you're going to get, not a thing that will generate your config. Hope that makes sense! I'm still open to being swayed, I just think a directory you put in the right place is simpler for everyone involved. |
|
Yeah, that's a good point, I'll do some more cleanup soon, maybe having the general structure defined in the README is enough. |
2 participants
Hi @Olical, I've been using Aniseed/Nfnl + Conjure for a while, it's been an absolute game changer for my personal development flow, thanks!
I noticed that this starter kit is still using Aniseed, so I figured you could be interested in migrating it to Nfnl.
I took a few liberties like adopting lazy.nvim as the plugin manager, and defining plugins in their own files. Hopefully nothing too different from what you had.
See individual plugins for details and let me know what you think.