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

[Feat Request] Project level configuration #530

Closed
Eric-Song-Nop opened this issue Aug 14, 2024 · 2 comments
Closed

[Feat Request] Project level configuration #530

Eric-Song-Nop opened this issue Aug 14, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@Eric-Song-Nop
Copy link
Collaborator

Motivation

It seems that whenever I restart the Neovim, I need to re-pin the main file, thus I hope that tinymist can have some sort of project level configuration.

Description

tinymist can read some project level configuration file, either typst.toml or other private configuration file, to determine stuffs like main file, root_dir, exclude file, compilation arguments, or other configurations. For now, some editors can handle some of them, but it might be good to be handled by tinymist to make it more corss-editor.

Examples/Questions

not really any good examples for now

@Myriad-Dreamin
Copy link
Owner

Myriad-Dreamin commented Aug 14, 2024

From discussion, the configuration should be in typst.toml, and it can be not hod reloaded in first implementation. A minimal setting is only allow a single entry:

[[tinymist.input]]
entry = "project/main.typ"

For auto pinning: when you are seeing or editing some file is related to this main file, the main file is used, otherwise it is unpinned and set the seeing or editing file as main implicitly. This has lower priority than explicit pin. How do you think of it?

@Eric-Song-Nop
Copy link
Collaborator Author

Close as this discussion is moved to another issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants