RJ TextEd

It's been fixed. I'll release a new beta so please check when available.

They all contain a "C" which is used as a line comment. It seems using an alphanumeric character as line comment can interfere with keyword identification. I'll look into it.

Well, I added the ability to add several values to both LineCommentA and B. Values are separated by |.

So

LineCommentA=C|D|c|d|!

works fine in the next release.

I'll see if I can come up with something...but 5 different ways to make a line comment seems a bit much. An array of different values is probably the best solution e.g. =C|D|c|d|!|.

Seems you have an extra space after "C"

LineCommentA=C<space>

Just remove it and it should work.

It seems to work on my end using

LineCommentA=C
OnlyLineCommentIfFirstCharA=2

Could you recheck?

I've made a small change in the draw function and it seems to be working now.

I can't reproduce it using the find dialog so that seems to work, but I'll try to fix the syntax highlighting issue.

Added 3 new methods to the document object in v7.63:

IsColumnModeActive(): Boolean
SetColumnMode(const bActivate: Boolean)
SetSelection(const startx,starty,endx,endy: Integer)

Using regular expressions for code folding may seem like a good idea, but it actually doesn't help that much. You still need to match the { } characters to find the correct fold ending. So you still need to know the fold start "{" in plain text to match it properly. It might be helpful wit...

Fixed in v7.63. Also added 3 new methods to the "Document" object:

CopyToClipboard()
CutToClipboard()
PasteFromClipboard()

YAML highlighting may be difficult to accomplice. Using external highlighters is probably not an option. Any external script need an API to work with and that API just doesn't exist.

The syntax option "OnlyLineCommentIfFirstChar" can now have 3 values in v7.63.

OnlyLineCommentIfFirstChar=2 means the line comment start character has to be the first character on the line.

Added to v7.63. Please test it in the upcoming beta release.

pjj

Rickard, what do you think?

The memo component in RJ TextEd is not a standard text component (like Rich Text Edit Control). Adding script support for highlighting would probably require some work...

I'll see if I can add support for regex in keyword identifying.

Maybe something like:

Code: Select all

[Keywords]
Normal keywords=AND|break|case|...
#Key/Value pair=[A-Z]+[0-9.\-]+
#M codes=M[0-9]+

Search found 1045 matches

Re: FORTRAN keyword issues

Re: FORTRAN keyword issues

Re: FORTRAN syntax file

Re: FORTRAN syntax file

Re: FORTRAN syntax file

Re: FORTRAN syntax file

Re: Another interesting syntax highlighting challenge

Re: Another interesting syntax highlighting challenge

Re: Scripted selections and current selection mode

Re: FORTRAN syntax file

Re: GetMethodAtCursor

Re: FORTRAN syntax file

Re: FORTRAN syntax file

Re: Another interesting syntax highlighting challenge

Re: Another interesting syntax highlighting challenge