Page 3 of 4
Posted: 22.05.2020 13:32
by Alexey
>doesn't work (note the relative path).
fixed, thanks. both files are updated in that Github issue.
Posted: 25.05.2020 15:43
by tmsg
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?
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.
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

Posted: 26.05.2020 08:33
by kvichans
5. Incremental search - FIXED. Update the plugin CudaExt.
Posted: 26.05.2020 08:36
by Alexey
yes, CudaExt FindInLines is fixed.
Posted: 26.05.2020 17:12
by tmsg
kvichans wrote:5. Incremental search - FIXED. Update the plugin CudaExt.
Alexey wrote:yes, CudaExt FindInLines is fixed.
I can confirm that it works now.
Thanks a lot for that, I am really using incremental search a lot.
Posted: 26.05.2020 17:52
by Alexey
BTW the API allows to create different instant-srch panel. it can be a) themed with Cud theme, b) buttons can be themed (like Find dlg). I postpone that your wish for instant-srch panel.
Posted: 26.05.2020 20:02
by tmsg
@Alexey: I am not sure what you mean with postponing. Are you planning to do an incremental search panel within Cud? I think for the time being the plugin is fine

Posted: 26.05.2020 20:05
by Alexey
I mean that I will delay this feature (panel) for unknown future time.
Posted: 26.05.2020 20:49
by Alexey
Posted: 27.05.2020 09:54
by tmsg
Alexey wrote:I mean that I will delay this feature (panel) for unknown future time.
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.
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?