I kind of like it. I can understand where it start and end.

Also, highlighted the way you expect when you click next to braces works too.

Here’s my opinion, a well-developed DSL could even be arguably more flexible than say Python even with existing libraries on their specific domains. So, if one is just limited to domains, they may be very well be preferable to general languages.

I have coded in C#, Python, C++, and currently nearly everyday, G’MIC. Which one of those are a DSL? The last one. What it is? It’s a Domain-Specific Language that has been geared toward raster graphics image processing. Why do I use it? Looking at the stack-based processing, commands, built-in mathematical functions. It seems that it has a lot more things that are built-in than say Pillow library for Python and other things. And I only do create images with code, so I am happy with this, and I even did things like Python itertools combinatorics with more things like rank2list/list2rank variation of those combinatorics which aren’t image processing by themselves, but can aid to it.

If I feel that it is way too limited for that Domain, then I wouldn’t use it. DSLs are only good if the other options are much more difficult to build with and their flexibility are often enough to entice their audience which is one with limited use cases. Of course, generic languages are usually better even than most DSL even within their domains because of wider support, and wider audience. More DSLs would be better than generics given enough time and support for their domains in my opinion.

Depends. I use G’MIC (Interpretative language for image processing largely inspired by bash) in CLI.

ig “C:\Users\User.…”

If I need something with ‘$’ in CLI, I’d be using $_path_rc\something_something. Sometimes with “” in case of spaces.

Other than that, I would be just running my own coded command in most case.

deleted by creator

What do you mean? I’m pretty new to making syntax highlighting for KDE Kate, so I’m just now fixing my other thing before I get into much more advanced concept of it.

So far, the most challenging part was highlighting things that counts as comment rather than pointers to image pixels or accessible variables. That’s not the end of my trouble though.

I do want to figure out how to highlight “expr” including newlines inside expr. expr is basically any mathematical expression that is utilized on JIT compilation.

• if expr
• repeat expr
• variable={expr}
• variable:=expr <- : can be replaced with operator and it will still apply.
• eval expr
• eval “expr”
• check “expr”
• fill expr
• fill “expr”
• eval>expr
• eval >“expr”
• fill >expr
• fill >“expr”
• {expr}
• for expr
• {“expr”}
• while expr

Along with that to set up regex inside it to highlight section of expr.

While still maintaining priority of regex. So, if one regex is more important, it’ll overwrite whatever highlighted.

I have a update for you, I am finally pulling it off!

https://media.discordapp.net/attachments/880256029705773099/1138887510710308904/image.png

There will be problems down the road, but I will worry about that later.

There’s no standard regarding G’MIC scripting. That being said, here’s a representative G’MIC script - https://pastebin.com/cEPW31HJ .

The first one is basically a example script for testing syntax highlighting. The second one is a real world case study. The second one can be found in https://github.com/GreycLab/gmic-community/blob/master/include/reptorian.gmic .

I haven’t included some concepts in the example_cli as you can see that reptorian.gmic introduces some concepts not seen in both. Basically, writing a syntax highlighter for G’MIC would be a nightmare. But doable if I can figure things out.

Getting highlighting for regex-based selection to work. That seems confusing. I have 7 criterias which is recommended for the G’MIC language.

Note:

1. Strings that matches #( |$|(#)+).* gets treated as if it was a comment.
2. Strings that matches #@cli.* are treated as if they’re a header for CLI codes.
3. Strings that matches \$(-\d+|\w+|\d+) gets treated as if they’re accessed variables.
4. Strings that matches \w+: are treated as if they’re commands names.
5. Any texts under control-flow item list gets highlighted as long as they’re outside any characters between 2 quotation marks and of course, taking into account of / being used as escape character.
6. #@gui gets bolded.
7. Anything between 2 quotation marks gets highlighted though escape characters would be considered.

I know there’s a lot of downvotes because there are people reading this as hate toward Python. On one hand, one can make the case that it is overused and this doesn’t bold well for those that simply can never like it’s syntax. On the other hand, Python is perfect for small scripts that isn’t tailored for a Domain or just quick codes.

I actually did that, but it was not satisfactory. And I had hard time making it work like how I want to.

Maybe I should use a XML editor or something to make it easier. I’ll give it another try (I just found the file again). Maybe from scratch even.

EDIT: To make it clear, I have hard time getting “contexts” working.

I’m using G’MIC for raster-graphic image-processing, but I can do other things in it too with ease. I feel this post so much.

Feel free to delete this post if you don’t feel that this fits though I think the language I use is very similar to bash in some ways (G’MIC). Here’s a real-world example of my own code in G’MIC that’s pretty much painful to parse:

command "out2display : skip ${""1=},${""2=},${""3=},${""4=1},${""5=1},${""6=},${""7=},${""8=},${""9=},${""10=} if narg($""1) if $""1 $__bg rv blend alpha fi fi xalp if narg($""6) if narg($""2)&&narg($""3)&&narg($""4)&&narg($""5) {$""4},{$""5},1,{s#0},i(#-1,$""2+x,$""3+y) f. begin(ww=w-1;hh=h-1;);(x<(2+narg($""7))||x>ww-2)||(y<(2+narg($""7))||y>hh-2)?(xor($""6,i)>128?0:255):i j[0] [-1],$""2,$""3 rm. if narg($""8)&&narg($""9)&&narg($""10) if $""8==0||$""8>2 {$""4},{$""5},1,{s#0},i(#0,$__nw+($__min_tile*$""9)-$""2+x-$""4,$""3+y) f. begin(ww=w-1;hh=h-1;);(x<(2+narg($""7))||x>ww-2)||(y<(2+narg($""7))||y>hh-2)?(xor($""6,i)>128?0:255):i j[0] [-1],{$__nw+($__min_tile*$""9)-$""2-$""4},$""3 rm. fi if $""8==1||$""8>2 {$""4},{$""5},1,{s#0},i(#0,$""2+x,$__nh+($__min_tile*$""10)-$""3+y-$""5) f. begin(ww=w-1;hh=h-1;);(x<(2+narg($""7))||x>ww-2)||(y<(2+narg($""7))||y>hh-2)?(xor($""6,i)>128?0:255):i j[0] [-1],$""2,{$__nh+($__min_tile*$""10)-$""3-$""5} rm. fi if $""8==2||$""8>2 {$""4},{$""5},1,{s#0},i(#0,$__nw+($__min_tile*$""9)-$""2+x-$""4,$__nh+($__min_tile*$""10)-$""3+y-$""5) f. begin(ww=w-1;hh=h-1;);(x<(2+narg($""7))||x>ww-2)||(y<(2+narg($""7))||y>hh-2)?(xor($""6,i)>128?0:255):i j[0] [-1],{$__nw+($__min_tile*$""9)-$""2-$""4},{$__nh+($__min_tile*$""10)-$""3-$""5} rm. fi fi fi fi if narg($""7) f[0] begin(ww=w-1;hh=h-1;);(x%$__min_tile==0||y%$__min_tile==0)||(x==ww||y==hh)?$""7:i fi"

That was before I figured out how to properly code in local commands.