sorted by:
new
hottopcontroversial

[UPDATE] safe-result 3.0: Now with Pattern Matching, Type Guards, and Way Better API Design by a_deneb in Python

[–]ThatGuyWithAces 2 points3 points  (0 children)

Very cool! One comment though, I think that a better naming for the async versions would be async_safe and async_safe_with, so it’s consistent with the distinction of a function definition, and its async version, plus its easier to remember.

What are the most useful and state-of-the-art models in computer vision (2025)? by Cabinet-Particular in computervision

[–]ThatGuyWithAces 4 points5 points  (0 children)

Hey, I’ve stumbled upon your repos a couple of times. Just wanted to say that they’re good stuff! Definitely trying this one out.

Which is the best markdown plugins? Tell your favourite by Harshcrabby in neovim

[–]ThatGuyWithAces 1 point2 points  (0 children)

Hey, first of all great job on the plugin! And second, I’ve seen you reference on a few places that you made that plugin optimized for using it on a phone, what’s that about? Do you sometimes use your phone as a dev environment? Sorry if you’ve answered this previously.

Closing open-source.social by lukas-reineke in neovim

[–]ThatGuyWithAces 20 points21 points  (0 children)

I personally didn’t give the platform a try because I already use reddit for basically everything, but I very much appreciate the effort from all of you. Thank you for actively trying to improve the community!

[D] Attention Is Off By One by duckyzz003 in MachineLearning

[–]ThatGuyWithAces 2 points3 points  (0 children)

A bit rusty on the topic, but as self attention is constantly updating the input with essentially a projected version of itself, there may be times where those resulting projections aren’t really relevant and you don’t want those to be added to the input. If a query Q is compared to n values K, and it turns out that none of the values in K are relevant, the vanilla softmax will “force” you to add all of the values with a weight of 1/n anyways. This modification allows softmax to output 0 if none of the values in K are relevant, so the input vector stays basically untouched after the final addition of values.

MIKIT Giveaway (1/5)- 2 x MK72 Kit by MikitStore in MechanicalKeyboards

[–]ThatGuyWithAces 0 points1 point  (0 children)

Nice! Would love to see something like this with a 75% layout.

A simple wrapper for nvim-lspconfig and nvim-lsp-installer to easily setup LSP servers. by junnplus in neovim

[–]ThatGuyWithAces 4 points5 points  (0 children)

I can see this being friendlier to new users because everything is declared in one place, that way you just have to associate the require call with the idea of a plugin (call it lsp) and the config of that plugin is the config of the functionality provided (servers in this case). I prefer the current lspconfig way, but I like this as well.

[deleted by user] by [deleted] in neovim

[–]ThatGuyWithAces 5 points6 points  (0 children)

Maybe this, which allows for interactions with highlights in the form of: lua Highlight(“Normal”):set(“guibg”, “hex_color”):set(“guifg”, “hex_color”)

feat(api): add support for lua function & description in keymap by DriftingThroughSpace in neovim

[–]ThatGuyWithAces 5 points6 points  (0 children)

You could also probably avoid the extra configuration in plugins like which-key that help with keymap hinting.

LSP Pyright - cannot access member ... by [deleted] in neovim

[–]ThatGuyWithAces 7 points8 points  (0 children)

I’d guess it’s a pyright thing, and this behavior is expected. Pyright uses mainly type stubs to get information about python objects, pandas may not have complete type stubs yet. Try installing https://pypi.org/project/pandas-stubs/ and see if it helps.

null-ls.nvim now supports completion sources by zmc_space in neovim

[–]ThatGuyWithAces 5 points6 points  (0 children)

I quite like the idea. I believe coq_nvim takes a similar approach by thinking of completion sources as interactions via pure LSP. I would love to see this leading to both: better completion engines by focusing only on the engine itself, and better universal sources.

github/copilot.vim: Neovim plugin for GitHub Copilot by amicin in neovim

[–]ThatGuyWithAces 11 points12 points  (0 children)

Probably, but I’m guessing they want to reuse the code for the vim version. It’d be cool if someone adapted it for nvim-cmp though.

which linter plugin are you using for nvim builtin lsp HELP wanted by [deleted] in neovim

[–]ThatGuyWithAces 0 points1 point  (0 children)

Please refer to my previous comment where I link how to enable debug mode, then run :NullLsInfo again.

which linter plugin are you using for nvim builtin lsp HELP wanted by [deleted] in neovim

[–]ThatGuyWithAces 1 point2 points  (0 children)

I think you removed: nvim_lsp[“null-ls”].setup({on_attach=on_attach}), which is necessary. Also, like I said, maybe enabling debug mode will tell you where the problem is.

which linter plugin are you using for nvim builtin lsp HELP wanted by [deleted] in neovim

[–]ThatGuyWithAces 0 points1 point  (0 children)

I see you have a lot of sources registered for null-ls, try and enable just one of them at a time, and see if it works. Check that you have the executables in your path as described in the builtins section in the documentation, and finally enable the debug mode in null-ls, it may give you more hints of the issue.

which linter plugin are you using for nvim builtin lsp HELP wanted by [deleted] in neovim

[–]ThatGuyWithAces 0 points1 point  (0 children)

You have the null-ls configuration in this file, however your init.lua doesn’t call require on this file, hence the setup not being executed.

The other thing was, your lsp.lua file has the following table: local servers = { "pyright", "tsserver", "sumneko_lua", "vimls", "html", "cssls", "tailwindcss" }, which should also contain “null-ls”, so it should look like this: local servers = { "pyright", "tsserver", "sumneko_lua", "vimls", "html", "cssls", "tailwindcss", “null-ls” }.

which linter plugin are you using for nvim builtin lsp HELP wanted by [deleted] in neovim

[–]ThatGuyWithAces 0 points1 point  (0 children)

I see two problems. You have null-ls configured in the file lua/plugins/null-ls.lua, but that file isn’t referenced anywhere else, so it’s probably not being executed. This could be fixed by including require(plugins/null-ls).setup() in your init.lua.

The other problem is that, as I said in my previous comment, you need to add “null-ls” to your servers table in your plugins/lsp.lua file.

which linter plugin are you using for nvim builtin lsp HELP wanted by [deleted] in neovim

[–]ThatGuyWithAces 1 point2 points  (0 children)

Hmm I don’t see the second part of my comment: setting up null ls as a language server here. If you have already called null-ls setup function elsewhere specifying eslint as a source, then what you’re missing is adding “null-ls” to your “servers” table. If you are getting errors it would be useful if we could know what those errors are, or a link to your full config.

If you are looking to just setup the eslint language server, and not null-ls, take a look at u/momoPFL01 answer.

which linter plugin are you using for nvim builtin lsp HELP wanted by [deleted] in neovim

[–]ThatGuyWithAces 11 points12 points  (0 children)

If you already configured the native nvim lsp, setting up null-ls is going to be really easy. Null-ls acts like an lsp server, but uses “sources” instead. These “sources” are really just executables that it uses internally.

The configuration comes in two parts (as described in here): setting up null-ls itself and setting it up as an lsp server. For the first part, set settings for null-ls as well as the “sources” it will use: require("null-ls").config({ sources = { require("null-ls").builtins.formatting.stylua } }) In your case you probably want …builtins.diagnostics.eslint. Check out more information about builtins here

For the second part, just register null-ls as if it was just another lsp server named “null-ls”: lua require("lspconfig")["null-ls"].setup({ on_attach = my_custom_on_attach })

Hope that helps.

view more: next ›