| Summary: | [console] org.eclipse.ui.console.IOConsole - OutputStream-inserted text does not move caret, causing problems | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Simon L. <simon-jena> |
| Component: | Debug | Assignee: | Paul Pazderski <paul-eclipse> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jurgen.vinju, paul-eclipse, pawel.1.piech, pj, remy.suen |
| Version: | 3.6 | Keywords: | helpwanted |
| Target Milestone: | 4.14 M1 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 552030 | ||
|
Description
Simon L.
Hi all, Is there a workaround for this issue (e.g. a way to print to the console which the caret can deal correctly with)? Cheers, P. (In reply to comment #1) > Hi all, > > Is there a workaround for this issue (e.g. a way to print to the console which > the caret can deal correctly with)? > > Cheers, > P. I tried it quite a while (2-3 hours), but couldn't find any. The code where the exception is coming from is pretty inactive so I don't know if anyone has much expertise in it. A fix contribution would be much appreciated. I can not reproduce the exception part anymore but if the problem still exist there are high chances it is fixed with bug 548356. For the cursor movement I plan to add another change for 4.13 which should improve this situation. I'll close it as fixed. There should be no more exceptions regards input handling in console. The caret still don't move on output but it can now insert new input at its position where it jump to the end in the past. That means as long as the caret is not manually moved around (intentionally moved in a read-only position) the caret will not jump on user input no matter what output is appended meanwhile. (there is one case left where it can jump in fixed width console until bug 552014 is fixed) See also bug 550621 where I attached a video showing the changed input handling. |