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

WiP: Include all syntaxes in minimal syntaxes #38

Closed
wants to merge 6 commits into from

Conversation

Enselic
Copy link
Owner

@Enselic Enselic commented Sep 20, 2021

WARNING: This branch will be force pushed

The only thing left to do in terms of functionality as far as I know is to support creating custom assets with all integrated syntaxes included. This is currently tricky since syntaxes are split up in many syntax sets, but .into_builder() only operates on a single syntax set at a time. But I'm sure it is possible to make that work somehow.

@Enselic Enselic force-pushed the include-all-syntaxes-in-minimal-syntaxes branch 4 times, most recently from 2a702c1 to be1a62e Compare September 26, 2021 18:18
By forwarding the task to find the Plain Text syntax to assets. Not only does
the code become simpler; we also get rid of a call to `self.get_syntax_set()`
which is beneficial to the long term goal of replacing `syntaxes.bin` with
`minimal_assets.bin`.
To make the code easier to refactor further.
…tax_for_path()

We can do this since the file_name() of a file_name is file_name.
Each syntaxes is in minimal_syntaxes.bin once, so size is just slightly bigger
than syntaxes.bin.
@Enselic Enselic force-pushed the include-all-syntaxes-in-minimal-syntaxes branch from be1a62e to 3829135 Compare September 27, 2021 20:01
@Enselic
Copy link
Owner Author

Enselic commented Nov 25, 2021

This is a dead end. I have made syntect lazy load syntaxes instead. See trishume/syntect#398

@Enselic Enselic closed this Nov 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant