texmagic.nvim
LunarVim
texmagic.nvim | LunarVim | |
---|---|---|
3 | 272 | |
55 | 17,550 | |
- | 1.1% | |
0.0 | 6.9 | |
3 months ago | 8 days ago | |
Lua | Lua | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
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.
texmagic.nvim
-
Lua plugin for writing latex like vimtex?
If you go the LSP route, just FYI, I have a small plug-in called TeXMagic that enhances the functionality of TexLab in one particular way: currently with TexLab you must specify a build engine globally and must edit this global build engine every time you need a different build engine for a different project. My plug-in will help you define any number of arbitrarily-named build engines that you can call in a magic comment (e.g. %! TEX program = dvipspdf) and will pass your requested build engine to TexLab if you point the build key in the TexLab lspconfig table to the global variable my plug-in initializes.
-
[plugin] nvim_texlabconfig: Forward and Inverse Search with Texlab
Hi! I made a small plug-in a while ago to augment a small bit of Texlab’s functionality (pass info from magic comments into Texlab’s compiler config settings). Is this functionality something you’d be interested in including in your plug-in? (See https://github.com/jakewvincent/texmagic.nvim)
-
TeXMagic.nvim (new plugin for defining LaTeX build engines referenced in magic comments)
I wrote this because I had started setting up my workflow in Neovim 0.5.0 and wanted to use the TexLab LSP server with Neovim's LSP client. TexLab has a build service but only provides for a single user-defined build engine (without hacks). TeXMagic.nvim provides a global variable with which you can value the build key in your TexLab config. The variable references a table which is selected by finding the program/build engine name (provided in a magic comment) in either the default latexmk build engines (pdflatex, xelatex, or dvipspdf) or a user-defined build engine.
LunarVim
-
Every Neovim, Every Config, All At Once
LunarVim
- LunarVIM: An IDE Layer for Neovim
-
Tools to achieve a 10x developer workflow on Windows
I would suggest to start getting into vim by first trying out popular vim keybinding plugins available on your favorite code editor and get used to those first. Then, if you want to dive deeper into the power of Neovim, try out popular configs like LazyVim, LunarVim, NvChad... Taking Neovim from a mere text editor to a full-featured IDE with features like intellisense, debugging, testing, etc... on your own takes quite a lot of work and configuration.
-
Helix 23.10 Highlights
I used Helix for a while due to its support for LSP out-of-the-box, which my Vim config at the time couldn't live up to. I switched back to NeoVim after finding LunarVim[1] which had everything I was trying to get setup in my own config.
[1] https://www.lunarvim.org/
- How to Transform Vim to a Complete IDE?
-
Mastering Emacs
I'll admit I didn't look into it, but Helix sounds like something like LunarVim (https://www.lunarvim.org/)
Personally I much prefer that the editor NOT ship with something like that by default, especially when it's so easy to set up. I have several different vim config I use, including a pretty bare-bones one for headless systems, and I much prefer the ability to customize something very specifically.
Build tools that can compose together, rather than a single do-it-all tool. That is the power of the low level editors vs IDE's.
- No inline errors in Python unless I add and delete a line
-
LazyVim
I can't comment on any implementation details, but at least with LunarVim (which I use for daily coding), a slowdown when interacting with LSP is very noticeable. Some others have attested to this on a GitHub issue.
I'm not doubting your experiences with the lack of a slowdown, but there is truth that others do experience it. That might be more of a problem with LunarVim itself rather than Vim, but how likely am I (as someone who would like to avoid what he calls "config hell") or other newcomers to avoid whatever pitfalls there are, if a distribution designed for ease of use by people who know better fall into them?
https://github.com/LunarVim/LunarVim/discussions/3359
- Should Neovim now release a standard official configuration so that people who want an editor that just works out of the box get onboarded easily ?
-
neovim config
Anyways, although i have not used them, LazyVim and LunarVim comes highly recommended. You can try these and see what suits you .
What are some alternatives?
knap - Neovim plugin for creating live-updating-as-you-type previews of LaTeX, markdown, and other files in the viewer of your choice.
AstroNvim - AstroNvim is an aesthetic and feature-rich neovim config that is extensible and easy to use with a great set of plugins
nvim-typora - Bindings for Typora's Markdown in Neovim
SpaceVim - A community-driven modular vim/neovim distribution - The ultimate vimrc
texlab - An implementation of the Language Server Protocol for LaTeX
NvChad - An attempt to make neovim cli as functional as an IDE while being very beautiful , blazing fast. [Moved to: https://github.com/NvChad/NvChad]
nvim-texlabconfig - nvim-texlabconfig: Forward and Inverse Search for Texlab and neovim
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
nvim-lspconfig - Quickstart configs for Nvim LSP
Neovim-from-scratch - 📚 A Neovim config designed from scratch to be understandable
vimtex - VimTeX: A modern Vim and neovim filetype plugin for LaTeX files.
LazyVim - Neovim config for the lazy