Mofi wrote:The line termination, comments, strings and delimiter characters are normally not letters and so case sensitivity is not important.

Mofi wrote:I looked on an issue reported by a user who failed to use rem as alternate line comment in a wordfile for syntax highlighting SQL files containing keyword Nocase in first line.

The issue reported below could be reproduced with UE v23.20.0.40 on Windows 7 SP1 x64.

I copied into a Test.sql file the following 5 lines:

Code: Select all

--  line comment 1
rem line comment 2
REM line comment 3
Rem line comment 4
rEM line comment 5

Next I opened %APPDATA%\IDMComp\UltraEdit\wordfiles\mysql.uew and made the line comment highlighting tests by replacing always just the first line, saving the wordfile and looking on highlighting of Test.sql.

The results are:

Highlighting all 5 lines as line comments works with:

Code: Select all

/L13"MySQL 5.1" SQL_LANG Nocase Line Comment = -- Block Comment On Alt = REM Block Comment On = /* Block Comment Off = */ Escape Char = \ String Chars = `' File Extensions = SQL
/L13"MySQL 5.1" SQL_LANG Nocase Line Comment = -- Block Comment On Alt = rem Block Comment On = /* Block Comment Off = */ Escape Char = \ String Chars = `' File Extensions = SQL
/L13"MySQL 5.1" SQL_LANG Nocase Line Comment = -- Block Comment On = REM Block Comment On Alt = /* Block Comment Off Alt = */ Escape Char = \ String Chars = `' File Extensions = SQL
/L13"MySQL 5.1" SQL_LANG Nocase Line Comment = -- Block Comment On = rem Block Comment On Alt = /* Block Comment Off Alt = */ Escape Char = \ String Chars = `' File Extensions = SQL

So using block comment or alternate block comment as case-insensitive line comment works well.


Just the lines 1, 3 and 4 are highlighted as line comments with:

Code: Select all

/L13"MySQL 5.1" SQL_LANG Line Comment = -- Block Comment On Alt = REM Block Comment On = /* Block Comment Off = */ Escape Char = \ String Chars = `' File Extensions = SQL
/L13"MySQL 5.1" SQL_LANG Line Comment = -- Block Comment On = REM Block Comment On Alt = /* Block Comment Off Alt = */ Escape Char = \ String Chars = `' File Extensions = SQL

And just the lines 1, 2 and 5 are highlighted as line comments with:

Code: Select all

/L13"MySQL 5.1" SQL_LANG Line Comment = -- Block Comment On Alt = rem Block Comment On = /* Block Comment Off = */ Escape Char = \ String Chars = `' File Extensions = SQL
/L13"MySQL 5.1" SQL_LANG Line Comment = -- Block Comment On = rem Block Comment On Alt = /* Block Comment Off Alt = */ Escape Char = \ String Chars = `' File Extensions = SQL

So using block comment or alternate block comment as case-sensitive line comment works also with the strange side effect that just the first character of the case-sensitive line comment starting string must match. In practice this should not matter as I suppose there is either REM or rem in SQL files, but never rEM, rEm, reM, REm, ReM or Rem.


Just the lines 1 and 2 are highlighted as line comments with:

Code: Select all

/L13"MySQL 5.1" SQL_LANG Line Comment = -- Line Comment Alt = rem Block Comment On = /* Block Comment Off = */ Escape Char = \ String Chars = `' File Extensions = SQL

And just the lines 1 and 3 are highlighted as line comments with:

Code: Select all

/L13"MySQL 5.1" SQL_LANG Line Comment = -- Line Comment Alt = REM  Block Comment On = /* Block Comment Off = */ Escape Char = \ String Chars = `' File Extensions = SQL

That is the absolutely correct behavior for case-sensitive alternate line comment.


But highlighted is only the line 1 as line comment with:

Code: Select all

/L13"MySQL 5.1" SQL_LANG Nocase Line Comment = -- Line Comment Alt = rem Block Comment On = /* Block Comment Off = */ Escape Char = \ String Chars = `' File Extensions = SQL

That is completely wrong and a definite bug. The alternate line comment highlighting is not working at all if the alternate line comment is of letters and the language is defined as being case-insensitive.

/L1"Oracle SQL" SQL_LANG Nocase Line Comment = -- Block Comment On = /* Block Comment Off = */ Block Comment On Alt = rem String Chars = ' DisableMLS File Extensions = SQL TQL PAK PKS PKG
/L1"Oracle SQL" SQL_LANG Nocase Line Comment = -- Block Comment On = rem Block Comment On Alt = /* Block Comment Off Alt = */ String Chars = ' DisableMLS File Extensions = SQL TQL PAK PKS PKG

Mofi wrote:There is a syntax highlighting issue with UE v24.00.0.53 with line comments starting with a string containing letters of a case-insensitive language on selecting the line comment starting string.

For reproducing this issue do following:

Open "%APPDATA%\IDMComp\UltraEdit\wordfiles\batch.uew" and change the first line from

Code: Select all

/L15"Batch" Nocase Line Comment Num = 4rem  Line Comment Alt = :: Line Comment Valid Columns Alt = [1] String Chars = " DisableMLS File Extensions = BAT CMD SYS

to

Code: Select all

/L15"Batch" Nocase Line Comment = rem String Chars = " DisableMLS File Extensions = BAT CMD SYS

Next copy and paste into a new file the following 3 lines:

rem Comment with command REM in lower case
REM Comment with command REM in upper case
Rem Comment with command REM with just first character in upper case

Save the file as Test.bat which activates case-insensitive highlighting.

Select now in first line the line comment starting string rem. The rest of the first line is still highlighted as comment as expected.

Select next in second line REM respectively in third line Rem. The rest of the second/third line is wrongly highlighted as normal text.

This happens also with using Line Comment Alt = rem in the wordfile. It does not matter if the wordfile contains rem, or REM or Rem.

But if Nocase keyword is removed and using line comment with then case-sensitive rem or REM or Rem there is no wrongly highlighting of rest of the line as normal text when selecting line comment string.

This issue does also not occur when using a block comment as line comment, i.e. use one of the two lines below in the wordfile.

Code: Select all

/L15"Batch" Nocase Block Comment On = rem String Chars = " DisableMLS File Extensions = BAT CMD SYS
/L15"Batch" Nocase Block Comment On Alt = rem String Chars = " DisableMLS File Extensions = BAT CMD SYS

So the issue with highlighting rest of the line comment as normal text on selecting line comment starting string containing letters occurs only with line comment or alternate line comment being defined in a case-insensitive syntax highlighting wordfile and selected line comment starting string in highlighted file is not completely written in lower case.

This issue was detected by forum member Miklos and reported with a post, see http://forums.ultraedit.com/topic4653.html#p58416

Mofi wrote:... impossible to get anything within /*+ and +*/ highlighted as alternate block comment as long as block comment starts with /* and ends with */.

Mofi wrote:I'm using currently 32-bit UE v24.00.0.56 on Windows 7 SP1.

UltraEdit changes the syntax highlighting of first line of a block comment on having selected the first character of the block comment with a specific combination of block comment and alternate block comment as forum member Miklos reported and I could also reproduce, see the forum post http://forums.ultraedit.com/topic4653.html#p58576

Following steps are necessary to reproduce this issue:

1. Start UltraEdit with default settings.
   
2. Copy and paste the following to block comments into the new file.
   

   Code: Select all

   /* C/C++ block comment */
   
   /*! Doxygen comment
   over multiple lines. !*/
   

3. Save the new file with Test.c as file name.
   
4. Open "Advanced - Settings - Editor Display - Syntax Highlighting", open the wordfile for C/C++ and close the configuration dialog with Cancel.
   
5. Replace in first line of c_cplusplus.uew the block comment definition
   

   Code: Select all

   Block Comment On = /* Block Comment Off = */

   by
   

   Code: Select all

   Block Comment On = /*! Block Comment Off = !*/ Block Comment On Alt = /* Block Comment Off Alt = */

6. Save modified wordfile c_cplusplus.uew and switch back to file Test.c.
   
7. Open Manage Themes dialog, switch to tab Syntax, select language C/C++ and change the settings for alternate block comment for example to dark blue as foreground color, yellow as background color and bold as font style to have a very clear difference to line and block comments.
   
8. The two block comments are highlighted now (with Slate theme) as it can be seen also on upper half of the attached image.
   
   Select now only the slash character at beginning of the Doxygen block comment highlighted with line/block comment color and style settings.

The first line of this block comment is displayed now with the settings set for alternate block comment as it can be seen also on lower half of the attached image BlockCommentHighlighting.png (not anymore attached to this post).

This strange effect disappears on increasing the selection to next character of the block comment. And this strange syntax highlighting effect occurs only on selecting just the first character of the block comment, not on selecting anything else within block comment.