Community
Participate
Working Groups
I love the feature that you can press Ctrl+. to jump to the next annotation (or Ctrl-, for the previous). I mostly use it to jump from one compile error to the next. As there are usually not only compile errors, but also warnings, and possibly other annotations, it takes quite a few keypresses to jump to the next error. I know I could disable all the other annotation-types, but I'm wondering if some kind of priorization would help here. E.g. "error" annotations could have a higher priority than "warning" annotations, so that you would first jump from error to error and after the last error, jump to the first warning. From looking at the list, I could imagine the following order: Search Results > Occurrences > Error > Warning > Spelling Errors > Info Not sure about Tasks and Bookmarks, as I don't have them enabled for annotation jumping. What do you think?
Interesting idea. The question is how it fits in into the current mode. No plans to do this unless we get a good quality patch that works well together with the current approach.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
