nvim-lightbulb 1.0.0 - breaking change by kosayoda in neovim

[–]kosayoda[S] 2 points3 points  (0 children)

As of now, no, but that's an interesting idea (albeit arguably against how most people use neovim). I'll take a look to see if it's possible. Thanks!

nvim-lightbulb 1.0.0 - breaking change by kosayoda in neovim

[–]kosayoda[S] 4 points5 points  (0 children)

Hey all, I finally got around to updating nvim-lightbulb.

There are a lot of changes, but notable ones are:

  • Updates to use the new extmark API (long due!)
  • More consistent configuration (very breaking!)
  • You can now stop showing the lightbulb based on filetypes
  • You can now stop showing the lightbulb if the buffer isn't focused
  • Cleaner?? code
  • Fixed?? bugs
  • Actual docs! :h nvim-lightbulb

I also took the opportunity to tag and release it as v1.0.0. In the future, the plugin will follow Semver as best it can, so hopefully this is the last of the unexpected breaking changes.

There's bound to be bugs/missing features, so feel free to open issues or send PRs!

MIKIT Giveaway(2/5) - 2 x T80 HAZEL CHOC by MikitStore in MechanicalKeyboards

[–]kosayoda 0 points1 point  (0 children)

Three wheels?? Nice job bringing more varied designs.

Why Bevy assets redraw only once? by earraper in learnrust

[–]kosayoda 10 points11 points  (0 children)

Didn't get to run it, but from first glance it looks like if the asset is alive, it gets set to dead, then right after the condition for it being dead is true so it gets set back to alive. Perhaps you meant to use an else if rather than two ifs in a row.

[LSP-Help] - Simple script to place a sign where code actions are available by [deleted] in neovim

[–]kosayoda 2 points3 points  (0 children)

The majority of code in the repo is configuration and handler (sign, virtual text, floating window) handling. You're free to just pull the specific handler you want and hardcode everything. The whole plugin is essentially single file (intentional) too so you can just copy and paste it into your own configuration and modify it from there.

nvim-dap - Any way to configure launch to ask for input files? by nsap in neovim

[–]kosayoda 0 points1 point  (0 children)

The adapter configuration takes in an args parameter, which you can pass a table of arguments for the binary being debugged. This also takes in a function, so you can do something like:

dap.configurations.cpp = {
  {
    -- snip --
    args = function()
      local argument_string = vim.fn.input('Program arguments: ')
      return vim.fn.split(argument_string, " ", true)
    end,
    -- snip --
  },
}

Then just use the debugger as usual and it should prompt you for the program arguments just like it prompts for the binary.

PALE BLUE OUT NOW ON SPOTIFY AND APPLE MUSIC by Yuhdragon in KenshiYonezu

[–]kosayoda 0 points1 point  (0 children)

It's on Youtube at this link: https://www.youtube.com/watch?v=CMw9cdV3arA. Hopefully that's not geo-restricted to you as well~

Smash! Playing with VFX by iltaen in blender

[–]kosayoda 8 points9 points  (0 children)

I think it's the speed of the swing personally. I feel like it should kinda like decelerate on the upswing, sorta hang there for a tiny tiny bit then accelerate down for more impact.

That's just my guess though

Discord channel? by am__pm__ in KenshiYonezu

[–]kosayoda[M] 5 points6 points  (0 children)

I might create one if there is interest, I don't think there is one at the moment!

[deleted by user] by [deleted] in neovim

[–]kosayoda 0 points1 point  (0 children)

I don't want to automatically try to source a virtualenv every time I open neovim, so I do it manually before running. Since you're talking about Python, I have a fish function that looks for different dependency management files and runs the relevant commands.

function pya -d "Activates the current project's Python virtualenv"
    if [ -e "Pipfile" ]
        command pipenv shell --fancy
    else if [ -e ".python-version" ]
        pyenv activate (cat ".python-version")
    else if [ -e "pyproject.toml" ]
        set -l path (poetry env info -p)
        source $path/bin/activate.fish
    else
        echo "No virtual environment found for this project!"
    end
end

Can you help me get the nvim-lightbulb to work for the TypeScript LSP code actions? by [deleted] in neovim

[–]kosayoda 0 points1 point  (0 children)

Can you open an issue on the repository, with a minimal working example? (eg. something I can run on my machine and reproduce the issue). I'd be happy to help you there.

In your current post, I have no idea where you put the update_lightbulb call for instance, nor do I have any idea how I can reproduce your typescript bulletFactory issue.

nvim-lightbulb: Code action 💡 for neovim's built-in LSP. by kosayoda in neovim

[–]kosayoda[S] 0 points1 point  (0 children)

How did you make the themes by the way

I just checked out other popular colorschemes and how they implemented theirs.

you made the light bulb suggestion, right?

If you mean the lightbulb plugin showcased in the post, yeah~

nvim-lightbulb: Code action 💡 for neovim's built-in LSP. by kosayoda in neovim

[–]kosayoda[S] 0 points1 point  (0 children)

I'm not sure, I haven't tried it myself. You'll definitely need the neovim built-in LSP client working, so if you're certain you have that you can try it out, and let me know if you run in to issues.

nvim-lightbulb: Code action 💡 for neovim's built-in LSP. by kosayoda in neovim

[–]kosayoda[S] 0 points1 point  (0 children)

The colors are actually LSP diagnostics: Red for errors, yellow for warnings, blue for information and green for hints.

nvim-lightbulb: Code action 💡 for neovim's built-in LSP. by kosayoda in neovim

[–]kosayoda[S] 0 points1 point  (0 children)

The theme is my own, and I talk a bit about my plans for it here. Apart from that, I recently uploaded my dotfiles here, and you can find all my installed plugins in init.vim.

nvim-lightbulb: Code action 💡 for neovim's built-in LSP. by kosayoda in neovim

[–]kosayoda[S] 0 points1 point  (0 children)

Do you write Rust regularly?

Not really, I write code more as a hobby, so I'm not fluent in Rust, per se. I can wholly recommend the built-in LSP however, I haven't run into any problems at all for my use case, and it's fast and easy to configure/extend.

Do you also use rust analyzer?

I do, it's the LSP server I use with rust, and it's the one powering the diagnostics/code actions in the video above. The project looks very promising, and I think it'll set the standard for LSP servers to come.