search

atom / notifications

User notifications
MIT License
74 stars 36 forks source link

Include file type in issues created from exceptions #39

Open izuzak opened 9 years ago

izuzak commented 9 years ago

Example issue where this would have been helpful: https://github.com/atom/atom/issues/5472 (see https://github.com/atom/atom/issues/5472#issuecomment-73757295).

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?

kevinsawicki commented 9 years ago

For https://github.com/atom/atom/issues/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.

forivall commented 8 years ago

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.