It continues to seem to me like #Neovim plugin authors haven't yet fully understood the power of #treesitter. I wish I had the time to explore the possibilities more thoroughly.
It continues to seem to me like #Neovim plugin authors haven't yet fully understood the power of #treesitter. I wish I had the time to explore the possibilities more thoroughly.
I am definitely not alright rn
I haven't touch my #neovim configuration for two weeks
So this doesn’t work because neither `vim.fn.{chdir,execute}` nor `vim.cmd` trigger `DirChanged` 😭 If I manually type `:cd <directory>` it works. What options do I have? Pleas don’t tell me `vim.fn.feedkeys` #Neovim
https://social.vivaldi.net/@RosaCtrl/114688787761288378
Sure, I got that sentiment. But your original post was a bit misleading:
"I got Ruby/CSS/JavaScript LSPs working with #NeoVim and so can you..."
You should've mentioned docker right away :P
- New #Neovim users: writing plug-ins with scroll bars all over the place
- Me: trying to remove the scroll bar from the native popup menu
Not the same
A potentially interesting method of applying spellchecking suggestions -- use Ctrl+Q in normal mode to cycle through them: https://gist.github.com/Konfekt/9f141a8e21a864d43181dbb712b4ea90
An intern I interacted with briefly started at my company recently. He sent me a message saying he was really awed by how quickly I moved around the codebase in #neovim #nvim when I shared my screen while pairing with him a year ago.
Since that year, he got really into neovim and he wanted to thank me for introducing him to it.
It's funny because I had exactly the same experience about 15 years ago, when I was a grad student. It's so cool to be that "awe" moment for another person, and to now be an author of a plugin that I think will be key to continuing the legacy of neovim through the AI age.
Continue to spread the joy of neovim everyone :)
Wow, seems overly complicated.
kickstart.nvim is a great starting point for a general #NeoVim setup (LSP setup included).
It's one file and has a lot of comments and explanations included.
Lazy.nvim is more complete, but more opinionated. There are other frameworks out there as well.
#neovim Development News
The 0.12 version will start to use Zig language to build Neovim itself.
This should improve overall Neovim development and should not have visible effect on users.
Thanks, @bfredl.bsky.social!
PRs (so far):
- github.com/neovim/neovi...
- github.com/neovim/neovi...
feat(build): build.zig MVP: bu...
Ça y est j'ai pas mal de trucs qui marchent sur Neovim. J'ai juste un bug dans netrw, qui apparemment est connu. Assez insupportable mais bon… on va espérer que ça soit vite fix.
Et sinon je dois comprendre pourquoi pyls avec memestra ne me dit pas pour les fonctions dépréciées de Python. Genre datetime.utcnow(), il ne me dit pas que c'est déprécié. Par contre si je marque une fonction dans mon code comme dépréciée, oui il va me le signaler.
Peut-être que c'est pas le bon outil, peut-être que je fais n'importe quoi, je ne sais pas !
Есть вот такая штука, https://github.com/glacambre/firenvim. Она запускает nvim в поле ввода прямо в браузере. Гляжу я на неё, на стандартную веб-морду mastodon, и прикидываю, как это будет выглядеть.
I recorded myself developing a feature for magenta (my #nvim #neovim #ai plugin) using the plugin: https://youtu.be/W_YctNT20NQ?si=fQ6y4g3M2U-7PSLl
I officially stated my project. I know exactly how I want to build it and I only use things I'm not familiar with. Yes, I like pain. For the back end I use #elixir with #phoenix and #absinthe. The last one is to use #graphql. I'm more familiar with #rest but I decided to go proper. The reason for using elixir is that while it's not the fastest it's also the most robust to handle heavy loads. I also subscribe to the idea that back end is usually a problem that functional solves better. For the front end I will go with #dart using #flotter. The reason is that my front end will be a mobile, desktop and web app. I'm also doing all of this with a #tmux / #neovim kind of work flow. I start to get good at it. I was thinking of maybe go with #liveview but I really like the flexibility that flotter gives.
Hello #neovim #nvim enjoyers. magenta.nvim now supports sub-agents. The sub-agents come with customized prompts for learning and planning.
This allows more focused context windows for subtasks and parallel execution. Check it out: https://github.com/dlants/magenta.nvim
I just updated my plugin for Vim and Neovim. The purpose is copy the file or directory paths of the file you are currently editing. I give you suggested leader key mappings. If you're a Vim or Neovim user, I'd love to hear your thoughts on it. https://github.com/andrewwoods/vim-copy-path-reference
I resurrected CodeGPT - a minimalist command based LLM plugin for fast workflows with a template system
Getting NeoVIM to not read anything VIM finds seems impossible, but it is easy to make the vimscript a noop with `if has('nvim') | finish | endif`. The similar Lua versions don't get read by VIM, so that direction isn't a problem.
I implemented Decasify in a single repo as a #vimscript plugin that loads in #vim and a #lua plugin that leads in #neovim, the former depending on the CLI and the latter depending on the Lua Rock. Also there is now an override so NeoVIM can go the other way too.
#neovim Development News
The 0.12 version will have a better 'smartcase' support during filtering candidates of built-in Insert mode completion.
PR (Vim patch):
- github.com/neovim/neovi...
vim-patch:9.1.{1373,1374} by z...
@davetron5000 having struggled (multiple times) to setup ruby-lsp in #neovim on macOS directly, seeing your post title that adds docker to the mix triggered outright schadenfruede. i had to read immediately. much respect 🙇♂️. bookmarked for future me bored with things running too smoothly