I will mention just created lexers in this topic
-
- Posts: 2236
- Joined: 25.08.2021 18:15
Re: I will mention just created lexers in this topic
this new Mojo lexer has very big download counter. 120 per week (others have 5-10 per week). i don't know why! is the link published on some other site? is editor having Mojo users? other reason? it is interesting why counter is big. some troll clicked it?
-
- Posts: 2236
- Joined: 25.08.2021 18:15
Re: I will mention just created lexers in this topic
Lexer EdgeQL (includes ESDL too) was published. language from EdgeDB project.
-
- Posts: 2236
- Joined: 25.08.2021 18:15
Re: I will mention just created lexers in this topic
lexer SystemTap is published now.
its code-tree finds nodes
"function xx(...)"
and
"function xx:yy (...)"
I hope it's enough.
its code-tree finds nodes
"function xx(...)"
and
"function xx:yy (...)"
I hope it's enough.
-
- Posts: 2236
- Joined: 25.08.2021 18:15
Re: I will mention just created lexers in this topic
I wanted to make the lexer for 'Salesforce Apex'.
VSCode site gives 2 packages: 50 K downloads one, and 1M downloads another.
i got the VSCode lexer for .apex files. it was updated only in 2017.
https://github.com/celador/vscode-apex-extension
repo writes that we must migrate to another repo for VSCode.
https://github.com/forcedotcom/salesforcedx-vscode
another repo gives no lexer for .apex files , only for .log and .html files and maybe some others. so as I get it the .apex files are no longer used in the work.
now Sublime Text package.
https://github.com/SublimeText/Apex
it has lexer for .apex files. but it seems lexer shares lot of content with Java lexer,
so CudaText users can install Java lexer and assign it to .apex files, all ok.
VSCode site gives 2 packages: 50 K downloads one, and 1M downloads another.
i got the VSCode lexer for .apex files. it was updated only in 2017.
https://github.com/celador/vscode-apex-extension
repo writes that we must migrate to another repo for VSCode.
https://github.com/forcedotcom/salesforcedx-vscode
another repo gives no lexer for .apex files , only for .log and .html files and maybe some others. so as I get it the .apex files are no longer used in the work.
now Sublime Text package.
https://github.com/SublimeText/Apex
it has lexer for .apex files. but it seems lexer shares lot of content with Java lexer,
so CudaText users can install Java lexer and assign it to .apex files, all ok.
-
- Posts: 2236
- Joined: 25.08.2021 18:15
Re: I will mention just created lexers in this topic
lexer Todo.txt was publushed.
it is for format of www.todotxt.org .
some trolls clicked very many times on SystemTap lexer downloads. it is not real downloads.
it is trolls. go no, click more. it is parallel to me.
it is for format of www.todotxt.org .
some trolls clicked very many times on SystemTap lexer downloads. it is not real downloads.
it is trolls. go no, click more. it is parallel to me.
-
- Posts: 2236
- Joined: 25.08.2021 18:15
Re: I will mention just created lexers in this topic
lexer 'Structured Text' (IEC 61131) is published today.
it shows some items in code-tree (functions, programs, some others).
from next CudaText update, Markdown fenced-blocks with "iecst" Id will be highlighted too.
i've read only small pieces of PDF docs (about string literals, number literals, comments, numbers in 2/8/16 bases). bugs are possible.
it shows some items in code-tree (functions, programs, some others).
from next CudaText update, Markdown fenced-blocks with "iecst" Id will be highlighted too.
i've read only small pieces of PDF docs (about string literals, number literals, comments, numbers in 2/8/16 bases). bugs are possible.
-
- Posts: 2236
- Joined: 25.08.2021 18:15
Re: I will mention just created lexers in this topic
found the SublimeText syntax for 'B2 Jam'.
but CudaText has already the syntax for 'Perforce Jam'.
both syntaxes have .jam extension. Perforce is the old base for B2.
ready lexer 'Perforce Jam' works for .jam files from B2 Jam SublimeText repo, as I see by fast looking. if anyone wants more complete lexer for B2 Jam, write - what are the differences in 2 syntaxes.
but CudaText has already the syntax for 'Perforce Jam'.
both syntaxes have .jam extension. Perforce is the old base for B2.
ready lexer 'Perforce Jam' works for .jam files from B2 Jam SublimeText repo, as I see by fast looking. if anyone wants more complete lexer for B2 Jam, write - what are the differences in 2 syntaxes.
-
- Posts: 2236
- Joined: 25.08.2021 18:15
Re: I will mention just created lexers in this topic
at the 2023-dec-31 new year day, i found the Sublime Text package for 'Heta' (language).
i see it is not popular.
5-8 stars at github.
VSCode syntax file has 395 downloads.
but language is usefull for biology and science.
so i want to add lexer anyway.
EDITED
lexer added.
i see it is not popular.
5-8 stars at github.
VSCode syntax file has 395 downloads.
but language is usefull for biology and science.
so i want to add lexer anyway.
EDITED
lexer added.
-
- Posts: 2236
- Joined: 25.08.2021 18:15
Re: I will mention just created lexers in this topic
another biology-related file format, called FastA.
SublimeText has lexer for it.
it is very easy to highlight this format in CudaText. but now I think it's not worth it.
look at the format: screenshots:
https://packagecontrol.io/packages/FASTA
screenshot shows that lexer needs to parse only lines starting with '>' (1st color),
find first word after '>' (2nd color), find text description without [] brackets
(3rd color), find comment in [] brackets (4th color).
only 3-4 colors for entire lexer (first '>' can be colored together with 1st word).
it is very primitive format which don't need to be highligted.
almost no need to highlight it. 3-4 colors. not for all lines.
SublimeText has lexer for it.
it is very easy to highlight this format in CudaText. but now I think it's not worth it.
look at the format: screenshots:
https://packagecontrol.io/packages/FASTA
screenshot shows that lexer needs to parse only lines starting with '>' (1st color),
find first word after '>' (2nd color), find text description without [] brackets
(3rd color), find comment in [] brackets (4th color).
only 3-4 colors for entire lexer (first '>' can be colored together with 1st word).
it is very primitive format which don't need to be highligted.
almost no need to highlight it. 3-4 colors. not for all lines.
-
- Posts: 2236
- Joined: 25.08.2021 18:15
Re: I will mention just created lexers in this topic
Lexer 'VimL' was improved and renamed to 'Vimscript' in AddonsManager.