>doesn't work (note the relative path).
fixed, thanks. both files are updated in that Github issue.
Great editor; some questions/suggestions
I have now changed the ui theme in such a way that the line number highlighted in the gutter can't possibly be ignored, so this point can be disregarded.tmsg wrote:4. I am working with a big screen and the editor window is as large as I can make it. When using Find (Ctrl-F) and searching for a one or two character string the found item is not easily located on the screen. I've seen that the line number is also highlighted but would it be possible to temporarily also highlight the line in which the item was found?
So the only thing left from my initial "wish list" is now point 5 about incremental search I did look into the source code of the find-in-lines plugin mentioned by @Alexey but alas, it's over my head
1.101.5 beta
https://github.com/Alexey-T/CudaText/issues/2595
https://github.com/Alexey-T/CudaText/issues/2595
Alright, that's what I was assuming you meant. I am fine with that as the find-in-lines plugin does what I need. In fact, I'd rather have this as a plugin than in Cud's source because I can easily patch a plugin but can't easily patch the Cud Pascal sources.Alexey wrote:I mean that I will delay this feature (panel) for unknown future time.
This observation brings up an interesting design question: how much (and what parts) of a text editor should be written in something like C or Pascal and what should be done in a higher-level script language? There's an editor around (see https://foicica.com/textadept/ ) which has Scintilla as its editor component but virtually everything else is done in Lua.
I've noted the beta 101.5 beta and I may try to check this out later (I am currently wrestling with the find-in-lines plugin to make it work standalone and also to change some small usability bits).
As there's no mention of my regex search problem I assume that's on the back burner as well?