This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[dev sep 26] The autoscrolling behavior of the terminal emulator is much better than that of the old Output Window. However there is a minor annoyance. If there is a llot of output and is continuing to be produced, and you are currently at the end, it will continue to scroll down to keep you at the end. This is good. However if you see something higher up that you want to look at, and scroll back up to it, as more output is produced at the end, the displayed area scrolls to match. This is not very useful because you are not even looking at the end of the file and you would like the currently displayed area to not move.
#16803 might be exactly what is needed here.
Reassigning to Ivan, it's his area.
The problem with 16803 is that it forces a dependency from terminalemulator to core, which is not a good idea given that terminalemulator is a library and is intended to be useful outside the context of NB. Also Term doesn't use JScrollPane so I"m not sure Gilis code would do the right thing. It shouldn't be hard to do though.
Added a new properties boolean scrollOnOutput boolean trackCursor to complement the existing scrollOnInput. When 'scrollOnOutput' is set to 'false', you can use the scrollbar to look at some text higher up w/o it moving from underneath you as more output is produced. This feasture is "smart" in the sense that if the cursor is visible (i.e. the user hasn't scrolled away from the cursor) Term will scroll to track the cursor even if scrollOnOutput is set to false. However the smarts only kick in if 'trackCursor' is set to true. Adjsuted in netbeans/core/output/OutputTabTerm.java as well by adding term.setScrollOnOutput( false ) etc.
Resolved for 3.4.x or earlier, no new info since then -> verified.
Resolved for 3.4.x or earlier, no new info since then -> closing.
moving terminal emulator issues to terminalemulator component. To see the correct version and target milestone of this issue look at Issue Activity table.