Bug 75994 - C Editor bugs
C Editor bugs
Status: CLOSED CURRENTRELEASE
Product: Red Hat Developer Suite
Classification: Retired
Component: eclipse (Show other bugs)
1.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tom Tromey
Tom Tromey
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-15 12:42 EDT by Need Real Name
Modified: 2014-08-11 01:46 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-10-15 12:42:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2002-10-15 12:42:34 EDT
I am editing a file using the C editor.

- The header comment, starting with a /* can be entered properly. It is syntax
highlighted in green and multiple lines can also be entered, but each line
doesn't automatically begin with a *. As soon as the user hits backspace while
entering the comment, the green bar that highlights the entire line goes away
and no more text can be entered.

- After the header comment is entered successfully, the  "#include..." is
entered reversed as I type it. Basically, after every key stroke, the cursor
moves to the front of the line instead of staying in the current position. Even
if I keep moving the cursor manually and type in the right thing, there is no
syntax highlighting. Hitting Enter causes the current line to move down and
typing (still reversed) starts on a line above the previous one entered. The
editor is also very slow as errors are output at each key and mouse stroke onto
the terminal window from which Eclipse was started.

The errors look like:
"Unhandled exception caught in event loop. Reason: ... " with different Reason
numbers in different scenarios.
Comment 1 Tom Tromey 2002-10-15 15:52:34 EDT
I checked in a fix for this.
It solves the C editor problems you mentioned.
So, I'm closing the report.

Note You need to log in before you can comment on or make changes to this bug.