-
-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[New package]: tectonic #248
Comments
Hello! Pull requests are always very welcomed to add new packages. If the distribution of the package is simple, the installation will most likely be so as well. See CONTRIBUTING.md and the API reference for more details! You may also use existing packages as reference. |
Hey @RaafatTurki! I’m struggling a bit to see how tectonic relates to Neovim. For now I only intend to support packages that have some clear connection with Neovim (LSP server, DAP server, formatter, linter). |
@williamboman my bad, I should've explained this part earlier. Tectonic doesn't relate directly to neovim, however texlab supports compiling latex using it. One feature of tectonic is the auto downloading of ctan packages as needed which is very appealing since that means any user can turn their nvim into a latex editor on any environment. With that said I can understand if packaging it isn't in scope yet. |
This package is simple to add. However, it appears that this project's objectives do not include it. So that you may use it in cli when necessary, I believe you should install it globally. |
Thanks to how mason works, every package installed is usable through the nvim terminal. furthermore if globalizing mason packages is desired one could always add On a side note I believe mason will eventually add packages that don't strictly relate to nvim simply because nvim is so modular. for instance an another package of interest is You can see how it could be used to essentially make You see how that blurs the line between what's nvim related and what's not, perhaps a |
That's good enough for me!
I'm not sure I agree with the overall sentiment. What I'm primarily looking for when considering a package that doesn't fit one of the existing categories are usage examples where Neovim somehow directly interfaces with the tool. Taking the This principle is loosely applied though, there will be cases where a package ticks all the boxes but it wouldn't make sense to include it (take |
Added in #249! |
Package name
tectonic
Package homepage
https://tectonic-typesetting.github.io/en-US/
Languages
latex
How is this package distributed?
Prebuilt binaries can be obtained from the github releases files
The text was updated successfully, but these errors were encountered: