You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Consider minified JS/CSS files that consist of a few lines, but each line is hundreds to thousands of lines long, amounting to 100KB. Loading these minified files (with LSP, highlighting, and more enabled) take much longer than a regular 100 KB file split into a hundred lines. Therefore enabling bigfile based solely on file size is insufficient - it needs to consider line length.
Describe the solution you'd like
Enable the bigfile filetype if the max column length exceeds a configurable number. It may be slow to find and count the max line length, in which case we could also allow configuring the maximum number of lines to search. Note that we can't always assume the first line will be long (e.g. it could be a license comment).
Describe alternatives you've considered
Another option is to enable this based on a match on the absolute file path. It'd be up to the user to find a common pattern match for their minified files (e.g. everything under a "dist/" directory, or file names that match "*.min.js").
Additional context
No response
The text was updated successfully, but these errors were encountered:
cngu
changed the title
feature: configure bigfile based on max column length
feature: configure bigfile based on max column length or path
Dec 22, 2024
Did you check the docs?
Is your feature request related to a problem? Please describe.
Consider minified JS/CSS files that consist of a few lines, but each line is hundreds to thousands of lines long, amounting to 100KB. Loading these minified files (with LSP, highlighting, and more enabled) take much longer than a regular 100 KB file split into a hundred lines. Therefore enabling bigfile based solely on file size is insufficient - it needs to consider line length.
Describe the solution you'd like
Enable the bigfile filetype if the max column length exceeds a configurable number. It may be slow to find and count the max line length, in which case we could also allow configuring the maximum number of lines to search. Note that we can't always assume the first line will be long (e.g. it could be a license comment).
Describe alternatives you've considered
Another option is to enable this based on a match on the absolute file path. It'd be up to the user to find a common pattern match for their minified files (e.g. everything under a "dist/" directory, or file names that match "*.min.js").
Additional context
No response
The text was updated successfully, but these errors were encountered: