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

Collision: *.comp extension is registered for both mason and glsl filetypes #841

Open
w23 opened this issue Jul 7, 2023 · 0 comments
Open

Comments

@w23
Copy link

w23 commented Jul 7, 2023

mason:

au BufNewFile,BufRead *.comp,*.mason,*.mhtml setf mason

glsl:

au BufNewFile,BufRead *.comp,*.fp,*.frg,*.fsh,*.fshader,*.geo,*.geom,*.glsl,*.glslf,*.glslv,*.gs,*.gshader,*.rchit,*.rmiss,*.shader,*.tesc,*.tese,*.vert,*.vrx,*.vsh,*.vshader setf glsl

I edit *.comp files as GLSL compute shaders, and was rather surprised when they were not highlighted properly due to having mason filetype.

The workaround is to add perl into polyglot_disable global variable, as mason registration happens under "perl is not disabled" condition.

But I wonder what is a proper way to fix it.

  1. Is *.comp even a valid/common file extension for mason, whatever that is?
  2. More collisions can be expected (e.g. racket scheme filetype collision #670). Is there a reasonable way to disambiguate those without disabling support for whole languages?
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

No branches or pull requests

1 participant