Display disabled code in a different color in SciTE

[Guest]

Hello,

I do not like to see a disabled code in the same color as the comments.

I am looking for a way to display disabled code in a gray color in  SciTE but I didn't found how to do it.

If I could, for example, set that everything after ";;" will be show in gray color then this will do the trick.

 Is there such a possibility?

[BrewManNH]

What is disabled code if not commented out code?

[Jos]

Any line starting with a Semicolon is a comment line, hence shown with the comment line color.
The comment blocks have their own color setting.

Jos

 

Edited October 23, 2015 by Jos

[Guest]

"commented out code" is disabled code.
But I want it to be displayed in a different color from green and I want it only for disabled code.

Is it possible to set gray color for ";~" so everything after ";~" will be gray while everything after ";" will be green?

Edited October 23, 2015 by Guest

[BrewManNH]

No.

But you could use #CS (#comments-start) and #CE (#comments-end) and use a different color for that than what is used for ;

 

[Guest]

No.

But you could use #CS (#comments-start) and #CE (#comments-end) and use a different color for that than what is used for ;

 

Thank you for the answer.
Anyway, please take my suggestion and make this option in the next releases. I think it's a great idea
(Different color for ";~" and different color for ";").

Is there key shortcut (like Ctrl+Q for ';~') for #CS (#comments-start) and #CE (#comments-end)  ?
I would love to know the keyboard shortcut for this if exist.

[BrewManNH]

CTRL-SHIFT-Q will give you the #CS and #CE.

[Jos]

 

Thank you for the answer.
Anyway, please take my suggestion and make this option in the next releases. I think it's a great idea
(Different color for ";~" and different color for ";").

,, and why is this such a great idea?
I already told you how it works and really can't see why this would be a big benefit.

Jos

[Guest]

,, and why is this such a great idea?

... really can't see why this would be a big benefit.

Take a look at the following demonstration (made with paint windows)

In which image it is easier to see important information?
In which image it looks less messy?

This is the big benefit

Edited October 23, 2015 by Guest

[Jos]

I did understood what you wanted but honestly do not see the big benefit.
Just the 2 available comment options for this purpose and you should be good.

Jos 

[Guest]

I did understood what you wanted but honestly do not see the big benefit.
Just the 2 available comment options for this purpose and you should be good.

Jos 

The benefit is that you see the important information (comments) much more easily without distraction that caused by the disabled code because it's gray.

The second benefit is that in this case you don't get extra line (#CE , #CS requires unnecessary line for getting color separation)

The third  benefit is that it is easier to  Press CTRL+Q then CTRL+SHIFT+Q

Edited October 23, 2015 by Guest

[Jos]

I have to admit you are pretty persistent, but it will not be something I will be working on.

Jos

 

[Guest]

I do not demand it (maybe I sound like that) I'm just asking to be such an option exists.

I can live without it ..
Is there an option to change the CTRL+SHIFT+Q to something else?

Edited October 23, 2015 by Guest

[Jos]

Add a shortcut for IDM_BLOCK_COMMENT to  user.shortcuts. Copy the below lines into your SciTEUSer.properties and make the changes.

Jos
 

# User defined key commands
user.shortcuts=\
Ctrl+Shift+V|IDM_PASTEANDDOWN|\
Ctrl+PageUp|IDM_PREVFILE|\
Ctrl+PageDown|IDM_NEXTFILE|\
KeypadPlus|IDM_EXPAND|\
KeypadMinus|IDM_BLOCK_COMMENT|\
Ctrl+F1|IDM_HELP_SCITE|

 

[nitekram]

Any line starting with a Semicolon is a comment line, hence shown with the comment line color.
The comment blocks have their own color setting.

Jos

 

May I ask where you see the difference in color? It appears the same to me, unless I use #CE to start the line, then it appear to be a different color, but once I change that to #CS, it goes back to the same color as using the semicolon. If it is something I can change, I would like to, but have never diverted from the defaults, except for recently when I changed the way it comments errors in the script...I removed that, as I was having issues with Ctrl T (tidy) removing the remarks.

 

PS...I actually like the idea, but understand that it can be a pain to make changes

Edited October 23, 2015 by nitekram

[Jos]

Commentlines (;) use style 1 
CommentBlocks (#cs..#cs) use style 2

# Comment line
style.au3.1=fore:#008000,italics
# Comment block
style.au3.2=fore:#008000,italics

Change it to what you like to see. The default is similar colors, but the old SciTE color settings were having a slight difference

# Comment line
style.au3.1=fore:#009933,italics,back:#F0F4F9
# Comment block
style.au3.2=fore:#669900,italics,back:#F0F4F9

Jos

[mLipok]

Or simply using SciTEConfig  and in "Edit Colors" tab there is nice GUI to change this colors.

EDIT:
to use SciTEConfig you need to press CTRL+1 in SciTE4AutoIt

Edited October 23, 2015 by mLipok

[nitekram]

Commentlines (;) use style 1 
CommentBlocks (#cs..#cs) use style 2

# Comment line
style.au3.1=fore:#008000,italics
# Comment block
style.au3.2=fore:#008000,italics

Change it to what you like to see. The default is similar colors, but the old SciTE color settings were having a slight difference

# Comment line
style.au3.1=fore:#009933,italics,back:#F0F4F9
# Comment block
style.au3.2=fore:#669900,italics,back:#F0F4F9

Jos

I thank you for this, but I do wonder why mine were the same color.

[nitekram]

Or simply using SciTEConfig  and in "Edit Colors" tab there is nice GUI to change this colors.

 

This is the cats meow...I like this and will remember this!

[Guest]

PS...I actually like the idea, but understand that it can be a pain to make changes

I think I should open a poll for this and If we will see that many want it then maybe he will decide to work on it even though it's big deal.  I think it's worth to develop it but this is my personal opinion.

In addition, I am aware of the alternative - #CE , #CS
But the drawback is that it add 2 extra lines.

This drawback does not sound serious, but it is.
 

This example easily show why and when it's serious:

With #CE , #CS:

 

And my idea:

 

 That's what I tried to say in my previous post - post 9 (about the second benefit)
 

 

Edited October 23, 2015 by Guest