nvim-luapad
nvim-lua-guide
nvim-luapad | nvim-lua-guide | |
---|---|---|
13 | 152 | |
505 | 4,992 | |
- | - | |
0.0 | 6.3 | |
over 1 year ago | over 1 year ago | |
Lua | sed | |
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nvim-luapad
- In-editor lua REPL: nvim-luadev vs neorepl.nvim
-
Where to learn about Neovim and it's plugins? (Deeply)
there is this plugin: https://github.com/rafcamlet/nvim-luapad
- Is there an 'ielm' mode equivalent in neovim for lua?
-
How do I attach a language server to a nofile buffer?
Ah yes, finally a question I can answer. There is no easy way to do this. This was the first big problem when I started working on: luapad, and I dealt with it, by creating a temporary files, attaching lsp to them, and removed them right away from the file system. But later on it started to cause some problems (can't remember what they were now) so ultimately the temp files are not deleting until neovim is restarted.
- What are some plugins for interactive programming in nvim-lua
-
New Neo-tree feature: right aligned symbols and character fading
I was wondering how the hell you did it. There are no autocmds for window resizing. I was trying to figure this out for preview win for nvim-luapad and I gave up. But this timer idea... aren't there any performances issues?
-
leap.nvim: Lightspeed for everyone
This is a work in progress, but for 'mini.indentscope' I currently settled on using 'plenary.nvim' with helper for creating full child Neovim processes and testing directly extmarks (source; original idea is from rafcamlet/nvim-luapad). Eventually I plan to convert these helpers and 'plenary.test_harness' into something like 'mini.testing' (but only after yet another ready but being alpha-tested jumping module 'mini.jump2d' :) ). Hope that'll help now.
-
Simple examples of neovim integration tests?
Hi! I think I have exactly what you are looking for. Check the spec directory in the luapad dev branch https://github.com/rafcamlet/nvim-luapad/tree/dev/specs. I am using RPC to send instructions to another nvim instance and then check the results, restarting it between each test for clear env. It may be a bit messy, but I'm currently working on extracting this logic to a separated plugin.
-
Lua pattern for a luasnip autosnippet condition
Here's the other lua/neovim dev plugin I was thinking of that might help testing smaller portions of your code https://github.com/rafcamlet/nvim-luapad
-
scratch.nvim - emacs' scratch buffer alternative for neovim
Dude, I like your plugin, but please: do a gif or a video about what this plugin does (nvim-luapad do this and I know exactly what this plugin does)
nvim-lua-guide
-
Any guide to start writing plugins?
Nvim Lua guide
- I'm fairly new to Neovim, and I want to configure my neovim setup.
-
Advice/Resources for creating/debugging a Neovim Plugin?
My main struggles beyond a simple problem are just the inability to find a way to easily debug things and the general process for setting up a plugin. I mostly work with Python/Jupyter, some C and Lua/Bash scripts, and usually you can either write tests/print debug for smaller scale things or get some stack trace if you have an error. With Neovim development, it just feels like there's nothing more besides update plugin, try on neovim, fail, bash head against wall, and repeat, and that doesn't quite seem efficient or correct - I'm sure there's something out there that should make the process easier. I tried looking online but I haven't found many that really fit my needs (most of the resources here seem more targeted towards creating your own init.lua, and Luadev plugin's commands are all broken (:Luadev-RunLine and any other command keeps telling me I got some trailing space). I'm really just looking to see how to make a snippet library, but there doesn't seem to be much that helps me. If someone could let me know how they debug their plugin or point me to any external resources, please let me know!
-
[help] use neovim to edit files at remote - server?
I have no guidance for the first point. For the second, checkout the neovim lua guide or : lua-guide
- Is there a vim/neovim equivalent to something like "Mastering Emacs"?
- [Neovim] Puis-je obtenir un guide sur la façon d’installer Packer pour les nuls absolus ?
- New to NeoVim, looking to learn
- Where to learn about Neovim and it's plugins? (Deeply)
-
Where would be a good place to start trying to learn lua with no previous programming experience. Trying to learn it as it’s the main language used in a project I’m apart of and want to help out
A quick google search turned up this codeacademy class on learning to program in Javascript. I didn't vet the whole thing, but it appears to assume you know nothing, which is what you need. If you go through that, you can then consume one of the resources that /u/luascriptdev post to equate that back to Lua. Again, the concepts translate.
- how to understand lua config
What are some alternatives?
neo-tree.nvim - Neovim plugin to manage the file system and other tree like structures.
kickstart.nvim - A launch point for your personal nvim configuration
neovim - Vim-fork focused on extensibility and usability
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
leap.nvim - Neovim's answer to the mouse 🦘
vim-test - Run your tests at the speed of thought
plenary.nvim - plenary: full; complete; entire; absolute; unqualified. All the lua functions I don't want to write twice.
nvim-lua
tree-sitter-svelte - Tree sitter grammar for Svelte
nvim-luadev - REPL/debug console for nvim lua plugins
which-key.nvim - 💥 Create key bindings that stick. WhichKey is a lua plugin for Neovim 0.5 that displays a popup with possible keybindings of the command you started typing.