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
Sublime Text Files syntax error flooding #1510
Comments
I'm generally okay with errors for all files showing up when re-scanning resources, but ST should only open one message box with all of them instead of one for each. |
Would be nice to print them to the console, as I often to forgot what it was, on which file and line. I do not think that to show only one notice box for them all would be good because Sublime Text would take longer to show the error as it would have to wait for the scanning to finish, and such process could take long. A reasonable option is to show the first error and redirect the user to the console to seek for more, if they where found while the scanning is in progress. Once the scan finish and the user trigger a new scan by saving a file, the notice show box should be show again. The notice box should not be show immediately if the scan was not triggers by the user saving a file because if the files system is constantly changing it would trigger new file scans and would keep spamming the notice boxes. |
All error messages are also printed to the console, unless I'm mistaken? |
Actually they were, I didn't know it. So, would be welcome to tell it on the error message. |
Thanks. |
The issue #982 is a specif case of this for color schemes. This one, is emphasizing settings files. The general rule is the message dialog flood. |
there are error on them, we cannot show a error message dialog for each one of them immediately, otherwise we would flood the user with messages. See: Sublime Text Files syntax error flooding sublimehq/sublime_text#1510
there are error on them, we cannot show a error message dialog for each one of them immediately, otherwise we would flood the user with messages. See: Sublime Text Files syntax error flooding sublimehq/sublime_text#1510
Sublime Text Files syntax error flooding
When there are several Sublime Text files within syntax error, and some of the is updated, all the errors are triggered and spam/flood the user with too much/senseless notice boxes. Those boxes are too much and senseless because:
Steps to reproduce the error
Current Behavior
OK
button, as you cannot read them to do the fix, due they being several and block interaction with Sublime Text.Main.sublime-menu
file and save it. All the error on the last step will be triggered again, not just the current saved file.Expected behavior
OK
button.Sublime Text Build 3126
The text was updated successfully, but these errors were encountered: