วีดีโอ

Look at teej and Prime being impressed with ChatGPT lmao. Thanks for the video! I've been wanting to write a simple plug-in for learning purposes.

my neovim exploded after I updated it ;-;

Thanks a lot for these videos! First thing I check for when I learn there's a new release!

I’m not a fan of the new default color scheme. There are far fewer colors

Is it possible to hide and reopen a tab or see a list of already answered options?

it is much better now then 2years ago. Im using it for a couple month now, with config of just 7 lines with no plugins I have all the LSP setup the same as my previous neovim setup with absolutely same experience. Love it. No clumsy lua/vimscript configs in my life, never more.

Great talk, help me to understand how to create a new plugin

Thank you for the awesome plugin. Installation of the plugin with Lazyvim worked without a hitch and when I use “Enhance Grammar Spelling” function with a selected sentence, it offered a suggestion as expected. But how can I get it to accept the suggested spelling? Simply by pressing the return key doesn’t do anything. Is there a vim key binding that I have to set for that? Any suggestions would be much appreciated. TIA PS. I also get this message from nvim “^I.../r2d2/.local/share/nvim/lazy/gen.nvim/ lua/gen/ init.lua:336: in function .. /r2d2/-local/share/prim/lazy/gen.nvim/lua/gen/init.lua:317>]”

Thank you so much, i've been looking for how to resolve config using lazygit and you explain it best 👍💯

When I try GCI Curly Brace it doesnt work. just goes into insert mode. Anyone know what went wrong?

Ey, how do you make <D-l> work on kitty? is there something you should configure in the kitty conf?

DO NOT name your inner directory '{something}.nvim', as it will not work. DevOnDuty named his 'luaPlugin' so it was fine. luaPlugin.nvim/lua/luaPlugin -- fine luaPlugin.nvim/lua/luaPlugin.nvim --not fine took me too long to figure out that one

native osc52 support for clipboard copying is a must. especially when working with remote tmux sessions.

Awesome thanks for that !

Thanks for the review, for me the color scheme is also a big question update. There is no support anything but bold text and some keywords in lua, but for Golang it is unusable at all

<c-w>d / <c-w><c-d> opens a float window with the diagnostic information, that is set by default in nvim 0.10

Built-in query editor for :InspectTree is amazing! Great overview.

The ugliest :CheckHealth ever? I so went back to 0.9.x

new commenting feature is cool

Cool, I can now remove 2 plugins XD.

builtin comment feature seems not to be working well for JSX files

Thanks for review, David! Small question, do you think neovim LSP support is good enough to transite from CoC? I'm too lazy to veryfy it myself )

Thanks so much for this. I reused the code you showed for inlay hints and it works great! Cheers

Spent 30 minutes yesterday choosing my first commenting plugin. Bye bye!

Nice to see Nvim catching up to Helix.

no more color scheme or comment plugin for me :)

I'm already using, best feature for me is the builtin inlay hints support, it's working nice with gopls.

Had no idea. Curious to see what has changed.

comment is builtin ?

Me having just setup my neovim config yesterday 💀

stuff like gcc has been there for a while no? or is that something that was originally a plugin, that is now native?

Bruh ... Zoom in

Maybe I am old but I can’t read the small text. The echo in the room also makes it harder to understand your voice, and I would sacrifice the facecam and instead show your key presses. Had to give up on the video halfway through.

I really like it but I'm so used to nvim, and I have a work flow in vim that I can replicate in Helix yet.

Will it ever hit 1.0?

I didn't even realize v0.10 was here, thanks!

was expecting this video, thank you :)

wow v0.10.0 is here!!!!!!

wow that was fast!

Command Keymap is very nice to have

im trying to set it up with my packer so that it writes the node output to a file. I spend quite some time on this but i cannot figure it out. I have the loop in the nvim-dap for _, language in ipairs(js_based_languages) do dap.configurations[language] = { { type = "pwa-node", request = "launch", name = "Launch file", program = "${file}", cwd = vim.fn.getcwd(), sourceMaps = true, trace = true, console = 'externalTerminal', outputCapture = "std", }, but i dont know if there is a way to redirect the output from terminal to a file?

this video very neat so much information i can learn from this video thank you very much DevOnDuty!

Great explanation, very clear - thanks!

Nice vid, although still a hard sell for me without plugins

You don't need a mouse in VSCode to make a commit. There are keys eg to focus Ctrl+0. Learn them instead of telling that in VSCode you need mouse for something lol

btw you can automatically create error types using thiserror crate.

Thanks for this fantastic video. So how do you attach the debugger to a CAP application? I recreated your setup, which works fine for a simple express server (node --inspect server.js), but for a CAP server, do you invoke `node --inspect node_modules/@sap/cds-dk/bin/cds.js watch`? With this approach unfortunately I get rejected breakpoints for some reason. Is there a way to attach the debugger to a `cds watch` process?

Just tried llama 3 on my Mac m2, seems to work pretty well.

Do you use any local model instead of Copilot or Codeium?

Amazing video, I wish I could have watched it the first time I got to work with treesitter