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.
I.e. implement TopComponent.Cloneable, so the user can select Clone View etc. Not trivial, since it seems that the TopComponent here includes a lot of stuff in the actual data model (text which has been printed), which is ugly. Proper model-view separation would store the entire model as a separate class somewhere, including some methods of InputOutput involving the I/O streams and closed status; and the TopComponent view would handle the display only. Then you could easily clone it by just making a new view over the same model.
Currently prevents one implementation of full-screen mode from working with Output Window tabs. Other implementations might not require cloneability however.
FWIW, I just removed the Clone View action from OutputTabTerm to fix another issue. IMO cloning the output window is a bad idea - useless for the user, potentially inefficient if used programmatically for things like full screen mode. The output window is for transient output. I can't think of any use case for needing a duplicate that would not indicate a UI design problem somewhere else. Surely it must be possible to implement full screen mode using the original output window component - just dock it someplace else.
Tim is right - verifying, closing.
moving terminal emulator issues to terminalemulator component. To see the correct version and target milestone of this issue look at Issue Activity table.