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
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
For atom/atom#5472, first-mate could definitely include the grammar path in the exception message to make it easier to know which grammar has a bad pattern.
For those looking to validate grammars, I made a quick and dirty checker at https://www.npmjs.com/package/seaworthy, which just loads the grammar and then tries to parse all of the patterns.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Example issue where this would have been helpful: atom/atom#5472 (see atom/atom#5472 (comment)).
Perhaps we could include the extension of the file and the grammar which was used (just like in the status bar)?
EDIT: might be helpful to include some other file-related info, such as the total size, the number of lines, longest line, permissions, encoding?
The text was updated successfully, but these errors were encountered: