Bug 563605 - Important comment highlight
Summary: Important comment highlight
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.16   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-26 14:05 EDT by Wojtek Bok CLA
Modified: 2022-05-26 01:38 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wojtek Bok CLA 2020-05-26 14:05:28 EDT
I set the normal comment coloring to a light grey. This keeps comments from hitting my eyes, yet I can read them if needed.

I also use comments to block out code sections, such as:

// *******************
// read section
// *******************

or

// recursive method
private void foo(int bar)
{
.
.
.
  // recurse here
  foo(bar++);
}

and so on.

It would be really nice to be able have these comments jump out a bit with their own color. I can do this now, sort of, by creating a new Task Tags entry.

However this creates a Task, which shows up in the Task view, and will never go away.

If an new entry in Syntax Coloring/ Comments could be created for important comments?

An important comment could start with:
//!

so

//! recurse here

Any comment line starting with //! would then have its own coloring and I could make it pop-out of the code
Comment 1 Rolf Theunissen CLA 2020-06-01 07:03:25 EDT
Comments are language specific, therefore moving to JDT. Probably related to Bug 63808 too.
Comment 2 Wojtek Bok CLA 2020-06-01 12:12:10 EDT
I wasn't thinking of any actual action being taken by the IDE, just simply applying syntax coloring to a line which has the //! on it.

It could also be added to other languages as each has a single line comment syntax, for instance PHP uses the same comment characters as C, C++ C#, Java, etc.

Property files use #, so #! could be used.
Comment 3 Eclipse Genie CLA 2022-05-26 01:38:56 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.