community VS nvim-lua-guide

Check out how to create your own or feel free to borrow from Community Discussions’ templates.

Although GitHub did not have a plan to support this option, but AzureDevops and GitLab already supported this. https://github.com/community/community/discussions/8940 You can manually do it for now

[4]: https://github.com/community/community/discussions/37117

I think it's not about missing commands, but missing destination (package repo of "generic" type). Very same issue posted here: https://github.com/community/community/discussions/38083

btw - I know this exists, but it seems like the posts are responded to much: https://github.com/community/community/discussions/categories/copilot

It appears that you're using IPv6 (your ping is returning IPv6 addresses). A quick search shows some github services may not support IPv6 but that's just a guess

Yeah, Vundle's (presumably temporary) removal caught me off guard today on a fresh install. This, in turn, has caused me to take a hard look at the Vim plugins I was using. Turns out I only needed one...which I wrote. So I'm now just storing that one in the horrible "vanilla" Vim plugin scheme and putting that in my dotfile management.

Just a good reminder that dependencies will always let you down. It's just a matter of time. Oh, and never turn your back on a big company.

Here's the tracking on this issue:

https://github.com/community/community/discussions/48173

GitHub: "The VundleVim organization has been flagged. Because of that, your organization is hidden from the public."

It's a relatively new beta feature for GitHub.

Here's the support discussion ticket for this:

https://github.com/community/community/discussions/48173

>The VundleVim organization has been flagged.

Nvim Lua guide

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!

I have no guidance for the first point. For the second, checkout the neovim lua guide or : lua-guide

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.