luv VS neovim

Hi, I had this issue and I solved it by building https://github.com/luvit/luv myself.

To answer the OP's question, you could tackle luv and libuv ecosystem, as a way to connect Lua to real-world systems (files, sockets, servers...). That's one way to put Lua skills to use, there are other great answers in the thread. Another recommendation is to go through Programming in Lua book, especially the later chapters where you learn how Lua talks to the host application.

Alternatively you can get into the weeds and play around with the in built vim.loop (which is really just luv, specifically spawn to run commands on the OS and handle stdout processing via stream.

Unfortunately I doubt they are able to use netrw, it interfaces with user facing buffers too much. Telescope uses plenary which uses lua's luv implementation (bound to vim.loop). Fzf-lua uses an external binary called fzf

Lua is still actively used so there is a great number of libraries that came out in last 9 years. A decent example is the luv library that is packed with great functionality. On the whole I'm quite satisfied with the ecosystem, but it all depends on the domain.

You should be able to find plenty of examples of asynchronous code at https://github.com/luvit/luv and translate it.

The first thing I would recommend is read the official documentation. Both libuv and luvit (or more specifically luv)

I spent some time converting the luv documentation to make it available in :help and make the vim.loop module more discoverable. Thought plugin authors might be interested.

I'm assuming this one.

As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads

There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.

All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.