Currently, it's not possible to specify persistent policy for individual output
tabs. For example, search results and compiler tabs are good candidates to be
serialized even in closed state, so that they are opened where they were closed.
Some method setPersistenceType(type) is needed.
Also, new persistence type items in popup menu will allow user to
modify persistence policy of individual output tabs.
Decreased priority - planning resources for 3.4
Target milestone was changed from '3.4' to TBD.
reassigne to Tim, new owner of terminal emulator
IMO, the output window is specifically for transient data; if a
module wants data persisted across sessions, it should supply an
appropriate component to do that. I'm afraid the result of this
enhancement would be a build up of stale output windows across
sessions - let's not go there.
Dafe, when you said "go ahead and close some things as wontfix",
you probably didn't mean your issues ;-) But I'm closing this
as wontfix. :-(
moving terminal emulator issues to terminalemulator component.
To see the correct version and target milestone of this issue look at Issue