mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-08-03 22:35:43 +02:00
![]() The implementation of the read loop in the emulator can spin because it uses Reader.ready() to determine if there is more data to read. However the Reader contract does not specify that ready() means that read() will return a character, simply it means that read() won't block. As such, if a Reader won't block, but it has no characters, the inner read loop will spin constantly polling. The outer loop uses polling too - but it has a wait so that the CPU does not hit 100% and yields. Change-Id: Id9b2426c65e6c2a2c3ae817a78d2be435e568c1f |
||
---|---|---|
.. | ||
.settings | ||
icons | ||
META-INF | ||
schema | ||
src/org/eclipse/tm | ||
.classpath | ||
.gitignore | ||
.options | ||
.project | ||
about.html | ||
about.ini | ||
about.mappings | ||
about.properties | ||
build.properties | ||
cdt_logo_icon32.png | ||
HelpContexts.xml | ||
plugin.properties | ||
plugin.xml | ||
README.txt |
Terminal README =============== The Terminal is a UI-less model of a grid of characters, plus an SWT widget that's updated asynchronously for maximum performance. The widget can be hooked up to various ITerminalConnectors providing an InputStream, OutputStream, and a method for setting the Terminal Size. The widget processes ANSI control characters, including NUL, backspace, carriage return, linefeed, and a subset of ANSI escape sequences sufficient to allow use of screen-oriented applications, such as vi, Emacs, and any GNU readline-enabled application (Bash, bc, ncftp, etc.). This is not yet a fully compliant vt100 / vt102 terminal emulator!