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

Editing cc.sublime_settings doesn't cause build errors/warnings to update for a file until the contents of that file are changed. #62

Open
hazmatsuitor opened this issue Aug 21, 2017 · 0 comments

Comments

@hazmatsuitor
Copy link

This caused me a bit of confusion when I was trying to fix some missing includes. Steps:

  1. Create file with build errors due to #includeing a missing file
  2. Add the path to the #includeed file to "include_options" in cc.sublime_settings
  3. Go back to the file with build errors and save it again (e.g. with cmd+S)
  4. Build errors should be gone, but they're still there
  5. Make an edit to the file, and save again
  6. Build errors are now gone

Or if this is a limitation of Sublime Text and not something you can change, can you say what the limitation is so I can file a useful issue at https://github.com/SublimeTextIssues/Core/issues?

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