babelfish.nvim
dotfiles
| babelfish.nvim | dotfiles | |
|---|---|---|
| 3 | 7 | |
| 49 | - | |
| - | - | |
| 1.0 | - | |
| over 2 years ago | - | |
| Scheme | ||
| MIT License | - |
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.
babelfish.nvim
- Feline.nvim version 0.1 released
-
luv documentation in vimdoc format
Nice! Someday I would love for babelfish to handle this, but I need to sit down and fix some of the parsing problems that cause it to skip over embedded lists and the like (Also blankspace is an issue).
-
LSP Trouble: A pretty diagnostics list to help your solve all the trouble your code is causing.
You might be interested in md2vim , babelfish.nvim :)
dotfiles
-
Need help creating Heirline component
wezterm has great documentation, I would start here. You can check out my dotfiles.
-
Can anyone share his dotfile ? I’m bored from mine
Aquí. Only thing that would need changing is the lspconfig server cmd paths, depending on where you installed your language servers
-
What's the NeoVim feature/bugfix you're craving for?
What issues are you having? I notice on some filetypes I need to make an ftplugin to assert my indentation rules. If you use spaces though, it could be a different experience. I prefer tabs.
-
It only took me a day to port from vimscript to lua. It's worth it.
My Lua dotfiles are shorter than my Vim ones (2210 vs 2523 lines, reported by tokei).
-
Feline.nvim version 0.1 released
I actually switched my config from galaxyline to feline recently. Took me longer than I'll admit to understand the syntax (the example configs really helped) but it actually felt very orthogonal in the end.
-
Neovim config noob question
I shave never used galaxy line before and I'm also kinda lost with the docs. I found this example of a status line using galaxy line . I guess you could try using that code (you have to source a .lua file, check this guide for more info about using lua) and find out if the problem was galaxy line not having a default config.
-
Neovim 0.5 is awesome
Feel free to also take a look at my dotfiles. Here is my packer config and here are most of my mappings. The rest are found with various plugins.
What are some alternatives?
lsp-trouble.nvim - 🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing. [Moved to: https://github.com/folke/trouble.nvim]
Shade.nvim - An Nvim lua plugin that dims your inactive windows
lspsaga.nvim - improve neovim lsp experience [Moved to: https://github.com/nvimdev/lspsaga.nvim]
vim-vsnip-integ - vim-vsnip integrations to other plugins.
nvim-lua
galaxyline.nvim - neovim statusline plugin written in lua
panvimdoc - Write documentation in pandoc markdown. Generate documentation in vimdoc.
lualine.nvim - A blazing fast and easy to configure Neovim statusline written in Lua
feline.nvim - A minimal, stylish and customizable statusline for Neovim written in Lua
neovim - Vim-fork focused on extensibility and usability
nvim-tree.lua - A file explorer tree for neovim written in lua