<p dir="auto">I have a task defined that uses a problem matcher to create warnings.</p>
<p dir="auto">Assume it creates 5 warnings for file A and 2 warnings for file B. The total warning count shown in the status bar is now 7.</p>
<p dir="auto">Now follow these steps:</p>
<ul dir="auto">
<li>Open <code class="notranslate">View&gt;Show Errors and Warnings</code></li>
<li>Navigate to file A (do not fix any warnings)</li>
<li>Open <code class="notranslate">View&gt;Show Errors and Warnings</code> again</li>
<li>Navigate to file B</li>
</ul>
<p dir="auto">At this point the warning count in the status bar drops to 2. This is confusing since without doing  anything the 5 warnings have disappeared.</p>
<p dir="auto">The reason is that when I open file A from Errors and Warnings it isn't put into the working files. Then when I open file B, File A is closed and its markers get cleared.</p>
<p dir="auto">To avoid this confusion I suggest that opening a file from Errors and Warnings puts the file into the 'Working files' section, that is, the file is kept open and the warnings do not disappear.  So the effect would be the same as if I double clicked the file from the explorer.</p>
<p dir="auto">Assigning to Jo as the owner of diagnostics and the Errors and Warnings quick box. <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/dbaeumer/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/dbaeumer">@dbaeumer</a> fyi.</p>
<p dir="auto">Use Go To Definition (F12) on a function call to jump to its definition.  Then immediately use "Back" (Ctrl-minus).  Your cursor will not be back to where it was when you hit F12.  Sometimes it's just off a character, other times it's several lines away.</p>
<p dir="auto">It seems to be more consistently reproducible when jumping between files and jumping to a file that's not already in the "Working Files" area.  Even jumping within a file by repeatedly doing F12, Ctrl-minus will eventually jump to the wrong spot.</p>
<p dir="auto">This was happening while using the Go plugin with v0.10.1 on Mac OS X 10.10.5</p>