It can be distracting the change in the alternate file caused by the creation of the result window. Despite it usually doesn't cause problems after the window is created, it can be unexpected after a compilation error, subsequent correction and result window is recreated:
vim has a single window containing fileA
:SCCompileRun successful --> fileA on the left window, __SINGLE_COMPILE_RUN_RESULT__ on the right window
open fileB on the left window
Ctrl+^ on the left window goes back to fileA
:SCCompileRun successful
Ctrl+^ on the left window goes back to fileB, repeating goes back to fileA
changes fileA, :SCCompileRun fails -> fileA on top window, compilation on quickfix ( __SINGLE_COMPILE_RUN_RESULT__ closed)
correct fileA, :SCCompileRun successful --> fileA on the left window, __SINGLE_COMPILE_RUN_RESULT__ on the right window
Ctrl+^ on the left window changes it to __SINGLE_COMPILE_RUN_RESULT__instead of going to fileB
It can be distracting the change in the alternate file caused by the creation of the result window. Despite it usually doesn't cause problems after the window is created, it can be unexpected after a compilation error, subsequent correction and result window is recreated:
__SINGLE_COMPILE_RUN_RESULT__
on the right window__SINGLE_COMPILE_RUN_RESULT__
closed)__SINGLE_COMPILE_RUN_RESULT__
on the right window__SINGLE_COMPILE_RUN_RESULT__
instead of going to fileB