UVviewsoft forums

ok thank you.

main Alexey wrote:I wrote this info to the wiki today, https://wiki.freepascal.org/CudaText#Le ... tyles_only

Just seen this, thanks for the explanation. Good to know I can adjust colours in CT

You are welcome.

Hi, I've just updated CT to v1.155 and copied the lexers to the lexlib folder, which I have been doing for some time now without issues, but I'm currently noticing issues with the HTML and INI lexers showing as what can be described as a plain text file. In other words without any highlighting. Yet if I open an older INI file, it shows ok. Here's what happened.

First I updated CT, then copied the lexer files to the Data/lexlib folder, which has worked fine til now.

Then, I used DirLister to create an TXT and HTML from a list of files in a folder then renamed it, including the extension, and opened it. The syntax highlighting was plain text. I created a new INI file and copy pasted the content to it from the previous file. Highlighting works. Renamed the new INI file to the previous and deleted the old one. Now the Highlighting has gone again. Opening this file in SynWrite works fine.

Both the HTML and INI files are affected. Although I've only tried these file types, it could be affecting all those I have imported from SynWrite?

Any ideas what has happened?

Thank you

Maybe the reason is little changes to .cuda-proj format (it now saves relative paths with {somemacro})?
Maybe format of .cuda-session is changed (it was not changed in last months)?
What if you click the statusbar and choose the lexer in menu - will it persist after Cud restart?

If it don't help-- how can I repeat the issue? you can give me the 'old settings' dir / 'old lexlib' dir + 'new settings' dir / 'new lexlib'. Email support(at)uvviewsoft.com

I don't know what .cuda-proj format or .cuda-session are, so I cannot comment on those. I am not aware of using these if that is what you are asking, so that cannot be the cause. Unless it is something used by CT in the background that I am unaware of?

According to the status bar, the Lexer language is NONE. I R-clicked that and had the single choice of ini files, so I selected that, but nothing changed. Restarted CT, no change.

I am using Dir-Lister to create a txt file of a folder's content, then changing the file extension to INI. I've done this for years with other apps, but mostly with SynWrite, which still works ok in this regard.

One thing I have noticed though, small files tend to work ok, but the large files seem to have a problem. I tried to search for an answer to this, but only got this. Is there some limit to INI file sections that could be causing this?

If you are having issues repeating this. then let me know and I'll email my setup and the affected INI files to you.

Thanks Alexey.

I just don't understand how to see the issue here.
Pls mail me your

- py folder (all plugins)
- data folder
- settings folder
https://wiki.freepascal.org/CudaText#Lo ... .27data.27

- custom files which you test (on which you see 'plain text' but it must be not 'plain text')

and write the steps - what do you do. I need to repeat the steps to see the issue.
support(at)uvviewsoft.com

Email sent.

I have described the steps in the post above. But to make it clearer, here it is again...
1. Using DirLister to create a TXT file listing a folders content. Preferably a folder with thousands of files. Small folder content works, large folder contents don't.
2. Change the extension of this file from TXT to INI.
3. Open the INI file in CudaText. It still displays as a TXT file, ignoring all syntax highlighting.

here I see that when I opened your ini files

DirLister.2022-01-23_17-11-26.D_Documents_Games.ini
Games.ini
Hardware.ini

they are opened OK in 'ini files' lexer. you have the 'ini files' lexer in zip. so it must work...

your 2 ini files have size of 2.0 and 2.1 mb.
option "ui_max_size_lexer" allows 'ini files' lexer only for file size <2 mb. you can change it. to 3.