Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313737 - [syntax highlighting] set task tag color and font style is ignored, when using symbols like !:? in tag name
Summary: [syntax highlighting] set task tag color and font style is ignored, when usin...
Status: CLOSED DUPLICATE of bug 58205
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-20 10:35 EDT by Jörgen Rapp CLA
Modified: 2010-05-25 11:53 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jörgen Rapp CLA 2010-05-20 10:35:58 EDT
Build Identifier: 20090920-1017 - 3.5 ganymede

go to preferences: java.editor.syntax coloring
select Comments.Task tags

change look to underlined red
Nothing happens in the decoration of user defined task tasks

Reproducible: Always

Steps to Reproduce:
1.go to preferences: java.editor.syntax coloring
2.select Comments.Task tags
3.change look to underlined red
4.Nothing happens in the decoration of user defined task tasks though predefined tasks are decorated (TODO, XXX, FIXME)
Comment 1 Dani Megert CLA 2010-05-25 03:07:30 EDT
This works fine for me in 3.6 RC2 using the Java editor with Task tags defined on the Java > Compiler > Task Tags preference or project properties page. Maybe you have project specific task tags and then of course changing them on the preference has no effect.
Comment 2 Jörgen Rapp CLA 2010-05-25 11:45:44 EDT
Ah, looks like it's my naming convention that breaks it, since I use priority markers that seems to act as separators in some parsing or similar.
I use {taskName}{priority-symbol}

so 
ACTION! - high
ACTION: - normal
ACTION? - low

if you name your task ACTION! it won't highlight anymore.

//BUG! this is crazy and we need to fix it NOW
//PERFORMANCE? not the best solution and we might have to fix it
//TEST: make sure it works when it's cold outside
//REFACTOR? could break out class A for this
//CONFIRM! check with Duke about closures

I suppose I could work around it by using 1,2,3 for prios, but I do like my syntax better since it tells me more than just the priority (a sense of urgency), and I use 8 or so of these tags.
Comment 3 Dani Megert CLA 2010-05-25 11:53:48 EDT
It only recognize 1 single word.

*** This bug has been marked as a duplicate of bug 58205 ***