-
Notifications
You must be signed in to change notification settings - Fork 426
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
Improve tmbundle support #6690
Comments
I think GitHub doesn't use tmbundle anymore, I never saw the "in", "throws", etc. changes turn up even though I updated the repo and it looked like they were referencing the chapel-lang one instead of the bholt one. |
Related to #5908. And I agree with lydia, I think github moved to something else. Linguist or something like that? |
@ronawho && @lydia-duncan -- linguist still uses Chapel's tmbundle, as shown here (ctrl-f chapel) |
Looking at linguist's collection of tmbundle grammars, https://github.com/github/linguist/tree/master/vendor/grammars it looks like each grammar is imported as a submodule, including |
From the README on Linguist:
That seems to imply to me that they should get fixes automatically. |
That's not to say that @cassella's interpretation is incorrect, just that maybe they should know about it and update their documentation if it is. |
Is there any way to determine when Linguist was last rebuilt and which version GitHub is using -- essentially see whether it's been updated since our last edits to tmbundle? |
They update every release, and their last release was on May 25th: https://github.com/github/linguist/releases Unfortunately, our most recent tmbundle changes went in on June 16th, so we won't see these changes until the next linguist release. I assume GitHub is using the latest version, but couldn't find that info anywhere. Here's the latest PR that updated submodules: https://github.com/github/linguist/pull/3642/files |
That would explain it, my changes were in June. |
Progress! linguist 5.1.0 includes the latest chapel-tmbundle, https://github.com/github/linguist/pull/3725/files That picks up the exception handling keywords, but chapel-tmbundle proc tically(in solvent, out rageous, ref lective, var nish, inout terspace) throws {
try { ptophan(); }
catch n: ReleaseError {
throw n;
}
} |
Hi @victor-ludorum : I'm not aware of keywords other than 'ref' that are missing, though I wouldn't be surprised if there are some. I'm not sure what people would consider the most definitive list of Chapel keywords these days. Anybody else on this thread have a suggestion? |
I believe those should be highlighted, thanks Victor! |
@bradcray Okay sir I will submit a PR resolving this issue . |
This issue is meant to track Chapel syntax that isn't highlighted properly by tmbundle which, as I understand it, is what GitHub uses for syntax coloring.
ref
is not highlighted as being a keyword, for example in:The text was updated successfully, but these errors were encountered: