Community
Participate
Working Groups
When the Stack Trace console view has a scrollbar because of the amount of text it contains, it does not redraw the text correctly. It is very difficult to edit the text in the view, and cursor navigation keys don't work as expected (e.g. PgDn then Up Arrow often doesn't move the cursor).
I revised the java stack trace console and found that all similar issues are based on the fact that the java stack trace console is an editable console. Let me allow to provide more details and examples: 1. Paste some text on a few lines. In the middle of the first line, type Enter and Backspace. -- effect: The last raw is not returned by backspace. -- reason: Actually, it is, but the control is not repainted. -- possible fix: add getTextWidget().redraw() to org.eclipse.ui.console.TextConsoleViewer.documentListener.new IDocumentListener() {...}.documentChanged(DocumentEvent) 2. In the middle of the link, type Enter and Backspace. Assume that 1. is fixed. -- effect: The link is broken and no more can be resumed as link (just a text). -- reason: The reason is very simple. org.eclipse.ui.internal.console.ConsolePatternMatcher.MatchJob.run(IProgressMonitor) matches only the last text raw (initially whole text). It works perfectly for consoles, when the prints come in a sequence. In case of random edit, just doesn't work. -- possible fix: In my opinion, it needs a general investigation of the problem. My suggestion is that the console should be read only. There is nice feature like auto-format. An edit operation in the console can be a source of bugs and performance problems. Event more, what is the behavior of windows cmd and linux shell? The same, the dumps are read only.
(In reply to comment #1) > My suggestion is that the console should be read only. I don't need real editing here either. But i like the ability to paste one stack trace, and later add some line breaks and paste another. So if that was no longer possible, i suggest to allow multiple independent stack trace consoles (as the plus icon in the open console button already suggests). Otherwise, the inconvenient workaround for appending would be: 1. switch to some scratch editor 2. paste new trace 3. switch to stack trace console 4. select all (old trace), copy 5. switch to scratch editor 6. paste (prepend old trace at beginning), select all, copy 7. switch to stack trace console 8. paste (both traces)
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
@Paul, Does this interest you?
