Pink underline on valid code
Migrated from http://lampsvn.epfl.ch/trac/scala/ticket/1277
Reporter sanity
I write a simple "Hello world" app, yet there is a pink underline under the opening quote on "Hello world" - even though this is a valid program. Screenshot attached.
Reporter sanity
I write a simple "Hello world" app, yet there is a pink underline under the opening quote on "Hello world" - even though this is a valid program. Screenshot attached.
Leave a comment
on 2008-08-22 13:51 *
By tracImporter
Trac author: sanity
Attachment: file:eclscalabug1.png
Attachment: file:eclscalabug1.png
on 2008-08-22 13:53 *
By tracImporter
Summary changed from pink underline on valid code to Pink underline on valid code
Trac author: sanity
Trac author: mcdirmid
Ya, Eclipse isn't removing the error when I tell it to. This isn't something we can fix ourselves. It will go away eventually.
Ya, Eclipse isn't removing the error when I tell it to. This isn't something we can fix ourselves. It will go away eventually.
on 2008-08-31 07:04 *
By tracImporter
Trac author: sanity
Is there an eclipse bug report for this problem?
Is there an eclipse bug report for this problem?
I'm reopening this because I don't see any evidence that this is an Eclipse bug.
on 2008-11-19 12:58 *
By tracImporter
Trac author: djb
See also #1522 (which was marked a dup of this bug). If this bug is fixed, please ensure that it fixes the scenario in #1522 also. Screenshot: https://lampsvn.epfl.ch/trac/scala/attachment/ticket/1522/window.png
See also #1522 (which was marked a dup of this bug). If this bug is fixed, please ensure that it fixes the scenario in #1522 also. Screenshot: https://lampsvn.epfl.ch/trac/scala/attachment/ticket/1522/window.png
Trac author: BenHutchison
Trac author: BenHutchison
In trunk build, Ive entered both the example given here and the one in #1522. Neither now show pink underline, save for correct error that method FOR defined twice.
Some change appears to have fixed this. Re-open if a failing example can be found.
In trunk build, Ive entered both the example given here and the one in #1522. Neither now show pink underline, save for correct error that method FOR defined twice.
Some change appears to have fixed this. Re-open if a failing example can be found.
on 2009-03-19 21:13 *
By tracImporter
Trac author: jaredjacobs
FYI, this exact issue still happens for me with the current latest release of the Scala Eclipse plugin, 2.7.3.
I'm using Eclipse 3.4.0 with JDK 1.6.0_07 on Windows Vista.
FYI, this exact issue still happens for me with the current latest release of the Scala Eclipse plugin, 2.7.3.
I'm using Eclipse 3.4.0 with JDK 1.6.0_07 on Windows Vista.
on 2009-03-19 21:20 *
By tracImporter
Trac author: jaredjacobs
Happens with the latest nightly, too. If there's any more info I can provide that might help others to reproduce the issue, please let me know.
Happens with the latest nightly, too. If there's any more info I can provide that might help others to reproduce the issue, please let me know.
on 2009-03-21 16:54 *
By tracImporter
Trac author: BenHutchison
Hi Jared,
I closed it well after 2.7.3 was released. If I can reproduce the problem on a recent nightly build I will re-open the bug and investigate.
To do this, please provide:
1. The shortest piece of code you have that shows the problem (as text please, rather than screenshot, so it can be copied easily). Mention also where you see the underline.
2. The version string of the Scala plugin you were running, as shown on Help->About->Plugin Details.
Hi Jared,
I closed it well after 2.7.3 was released. If I can reproduce the problem on a recent nightly build I will re-open the bug and investigate.
To do this, please provide:
1. The shortest piece of code you have that shows the problem (as text please, rather than screenshot, so it can be copied easily). Mention also where you see the underline.
2. The version string of the Scala plugin you were running, as shown on Help->About->Plugin Details.
on 2009-05-19 21:16 *
By
I don't understand why this was closed ... to the best of my knowledge it has never been fixed since opened, either on trunk or in a release.
I expect that it to be finally fixed in 2.8.0.
I expect that it to be finally fixed in 2.8.0.
on 2009-05-20 11:21 *
By tracImporter
Trac author: res1st
CC Change: res1st@…
CC Change: res1st@…
Trac author: ColinHowe
Looks to be fixed in 2.8.0.r18604
Looks to be fixed in 2.8.0.r18604
on 2009-09-01 21:57 *
By tracImporter
on 2009-09-01 22:38 *
By tracImporter
Closed As: fixed