In the output view, if I use the up or down arrow key to move to the next error, that error is immediately shown in the source editor.
If, however, I use the mouse to click on something other than the hyperlink, the error gets highlighted as if it is the current error, but the source editor
window doesn't get updated to show the offending line. It seems to me that the two should have the same effect. (I'm not sure which is "better"
Reassign to me.
This is as designed behaviour.
CCing Chris, because I implemented this (not update editor
after clinking on no-hyperlinked part of error) on his request.
agreed. this is as designed. if we start letting the user click on
'unclickable' parts of the error then it makes no sense to mark some
parts as a link...
with the keyboard navigation it might be better to have 'space'
indicate that the current error should be focused in the editor window
but i think this would only make sense if it was clear that the link
had focus and i'm not sure that is available.
So, I'm changing this to an enhancement request, because I do think this behavior isn't good.
One of the reasons it isn't good is that if the "current" error is the first, and the user wants to
look at error 73, for example, and she uses the keyboard to do this, she must pass over every error
in between (which will potentially open a bunch of files unnecessarily).
Also, by analogy with web browsers (which is an applicable analogy since this is using hyperlinks),
moving the focus to a hyperlink shouldn't automatically activate/follow the link.
Because this is a custom component, it should be quite possible to provide hyperlinks with a
distinct keyboard focus which is then activated with the space bar, just as other components are
activated with the space bar. (but, I agree that this is out of scope for 3.3!)
*** Issue 17313 has been marked as a duplicate of this issue. ***
Target milestone was changed from '3.4' to TBD.
Maybe this could be closed because of new Ivan's implementation of
does the new implementation provide the behavior described here? if
yes then close the bug.
reassigne to Tim, new owner of terminal emulator
The core team has not been responsible for terminal emulator for long time, so
reassigne all opened issues to responsible person.
The overall issue peratained to the days when output was based on Term,
but a lot of water has passed under that bridge.
This is likely still an issue in the re-introduction of Term
where we need to pay more attention to keyboard navigability
*** Issue 20522 has been marked as a duplicate of this issue. ***