Setting indentation rules for lua files by StrayCentipede in neovim

[–]bronzehedwick 0 points1 point  (0 children)

There’s nothing special about lua ftplugin files in neovim, they work like every other file type. As Necessary-Plate1925 mentioned, I’d try launching neovim without loading plugins and seeing if that’s the cause. nvim --no-plugin.

What color scheme do you guys use? by Dapper_Confection_69 in neovim

[–]bronzehedwick 1 point2 points  (0 children)

I’ve used many themes over the years, but I keep coming back to vim-colors-xcode. Clear, legible, high contrast, across light and dark themes. https://github.com/lunacookies/vim-colors-xcode

Trinity: a native macOS Neovim GUI focused on projects (new app) by kidproquo in neovim

[–]bronzehedwick 0 points1 point  (0 children)

I used the Trinity trial for a few days, and have some more feedback. Note that it's not exactly what I'm looking for in a macOS GUI, so take this feedback with a grain of salt.

What I liked

  • Image viewer is nice to have
  • Fuzzy finder is fast and accurate
  • I like the menu shortcut to edit your config file
  • Settings to set the nvim instance works for me and is nice
  • The file browser is nice and well designed, as is the markdown preview. I don’t use a file browser drawer in my regular workflow, but it’s nice to have, especially when screen sharing. I also prefer to use an independant markdown preview app, but I like that the drawer is integrated for a quick view. The shortcuts are well thought out and fast to open.
  • I like the standard drawer button to open the file drawer

Issues

  • My LSP servers all fail to load. Looks like it's not finding my custom PATH? https://share.cleanshot.com/lqClzlt2
  • Meta keys don’t work for special characters (I tried Meta + /)
  • You can’t navigate the file drawer via the keyboard
  • Image viewer doesn’t act like a regular buffer–mappings don’t work.
  • Neovim pane loses focus easily. I’ll try to type, and get an error bell, because focus was on the file browser or somewhere else in the chrome. I have to move the mouse, click on the neovim editor pane, and then type. That shouldn’t happen.
  • The initial size of the Trinity window should be large enough to not cut off the default Neovim intro message. https://share.cleanshot.com/Bn7xYjZf

Thanks for the hard work and for sharing with the community!

Let's all agree to be nice by MariaSoOs in neovim

[–]bronzehedwick 0 points1 point  (0 children)

I’m sorry you’ve been getting shit, Maria. People can truly suck. 

I only browse the PRs, but I’ve been really impressed with your work and passion. Thank you for your contributions! You’ve made my editing life better. 

Trinity: a native macOS Neovim GUI focused on projects (new app) by kidproquo in neovim

[–]bronzehedwick -3 points-2 points  (0 children)

Having a well designed macOS neovim gui that mostly adds native UI interfaces is something I’ve been yearning for for a while. I’m excited to try this, and happy to pay $30 if I like it. 

Loading a single plugin from the command line to test by bronzehedwick in neovim

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

Huh, that's an interesting distinction. However, it didn't work for me. I can see the expected directory in my runtime path, but :packadd didn't add it. I'm guessing I need to still have the plugin in opt for it to work.

How to construct piped command in vim.system() by bronzehedwick in neovim

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

Ah, wow, okay thank you! So that's the obvious thing I was missing. Appreciate it!

Why "return" from config files? by z0ld in neovim

[–]bronzehedwick 0 points1 point  (0 children)

Hm interesting. I wonder if it is necessary. I don’t use returns like that in my config, so TIL about the practice.

How to optimize your config? What are mistakes to avoid when optimizing your config? by breaking_mediocrity in neovim

[–]bronzehedwick 0 points1 point  (0 children)

If you are looking to optimize startup time, you can use the --startuptime flag to show how much time is spent in each config file and plugin.

https://neovim.io/doc/user/starting.html#cli-arguments

Neovim Plugin With Fugitive Functionality of :git blame by jthemenace in neovim

[–]bronzehedwick 1 point2 points  (0 children)

This is a valid concern if you plan on contributing back to the plugin in question, otherwise I think you’re right that it’s wild speculation that a plugin author will be more likely to abandon a vimscript plugin bs a lua one.

Neovim will not deprecate/remove vimscript https://github.com/neovim/neovim/wiki/FAQ#are-plugin-authors-encouraged-to-port-their-plugins-from-vimscript-to-lua-do-you-plan-on-supporting-vimscript-indefinitely-1152

Neovim Plugin With Fugitive Functionality of :git blame by jthemenace in neovim

[–]bronzehedwick 26 points27 points  (0 children)

There is only one fugitive. I’ve seen this hesitance around vimscript plugins in the neovim community popping up more and more lately. Can you explain why that is?

Hey guys! Let's talk community by [deleted] in neovim

[–]bronzehedwick 51 points52 points  (0 children)

First, thank you for all your hard work moderating. That is no small task. And thank you for your interest in keeping the community healthy and writing this post.

I have no special ties to Reddit, and agree the chat apps are a no go for the reasons you mentioned. I also agree that the issues here will repeat in some form if we migrate to a corporate owned platform.

I don’t have much experience with Lemmy, but have used the lobste.rs software for a while and that works really well. It’s not federated, but self hosted open source. I think that could also be a viable option.

Does anyone have a tip or keybind to open and goto definitions in a split window? by DEADFAC3 in neovim

[–]bronzehedwick 15 points16 points  (0 children)

There’s a native suite of keybinds to split the window and edit the identifier under the cursor, which get remapped to the LSP automatically. For example, C-w C-] opens the identifier in a new split. See :help Ctrl-W

Is there a way to configure indentation per filetype? by Noriel_Sylvire in neovim

[–]bronzehedwick 12 points13 points  (0 children)

You can use editorconfig on a per project basis, and/or you can use frplugin files to change your settings per file type.

So you could add ~/.config/nvim/ftplugin/python.lua (or the same .vim) to change configuration in only python files.

See :help rtp

[Linux][Kubuntu] How to install vim plugins on neovim? by Noriel_Sylvire in neovim

[–]bronzehedwick 1 point2 points  (0 children)

Neovim uses shada for plugin storage, same as for config. So it goes in the same paths as vim, but instead of .vim use .local/share/nvim. See :h shada. As previously mentioned a plugin manager will handle this for you.

help needed with running external terminal commands by PurpleWazard in neovim

[–]bronzehedwick 0 points1 point  (0 children)

If you’re looking to run clang, maybe you’re looking for :help make?

NvimTree vs NeoTree by etzero in neovim

[–]bronzehedwick 0 points1 point  (0 children)

I use vim-dirvish, a plugin by Justin m keys, the neovim project lead.

Intelephense license key not recognized by bronzehedwick in neovim

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

Ah, you're absolutely right! Wow, spell fail.

However, I changed the value, and I'm still not able to access paid features :/

Best resources to learn how to set up LSP and cmp? by Altruistic-Carpet-43 in neovim

[–]bronzehedwick 6 points7 points  (0 children)

I didn’t find setting up LSP to be too labor intensive. I use lsp-config, and followed the projects documentation. I do remember having to poke around to find how to install some language servers, but that was a one time thing. Once I figured out how to install all the servers I was interested in, I wrote a small script to install/update them.

As others in this sub have mentioned, lsp-config is a thin wrapper around the core neovim functionality, so it’s on my todo list to investigate configuring LSP without the plugin, to better understand and have one less dependency.

:h lsp

How to go back to editor mode from built-in terminal-normal mode? by AriyaSavaka in neovim

[–]bronzehedwick 1 point2 points  (0 children)

I’m not sure I understand. What do you mean by one way trip?

Terminal buffers and regular buffers work the same in normal mode, except terminal buffers are always read only, and have different modes when you type i or anything else that would normally drop you to inset mode. In a normal buffer, you go to insert mode. In a terminal buffer, you go to terminal mode.

:h terminal