Skip to content
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

Closed
RaafatTurki opened this issue Aug 4, 2022 · 7 comments
Closed

[New package]: tectonic #248

RaafatTurki opened this issue Aug 4, 2022 · 7 comments

Comments

@RaafatTurki
Copy link

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

@williambotman
Copy link
Collaborator

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.

@williamboman
Copy link
Owner

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).

@RaafatTurki
Copy link
Author

RaafatTurki commented Aug 5, 2022

@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.

@thanhvule0310
Copy link
Contributor

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.

@RaafatTurki
Copy link
Author

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 ~/.local/share/nvim/mason/bin/ to $PATH.

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 xxd, it's a hexdump utility that ships with vim and has the ability to convert its hex dump back to binary.

You can see how it could be used to essentially make vim a hex editor, and the only proper way to get this software is to either install vim or download its subtree and compile it yourself

You see how that blurs the line between what's nvim related and what's not, perhaps a Misc category is in order.

@williamboman
Copy link
Owner

however texlab supports compiling latex using it.

That's good enough for me!

You see how that blurs the line between what's nvim related and what's not, perhaps a Misc category is in order.

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 xxd use-case as an example; it enables translation of buffer <-> file contents via stdio, where Neovim will directly invoke the program.

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 git for example). Mason is a complement to more competent and established package managers, not a replacement!

@williamboman
Copy link
Owner

Added in #249!

vantaboard pushed a commit to vantaboard/mason.nvim that referenced this issue Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants