Great editor; some questions/suggestions
Posted: 20.05.2020 12:56
I am trying to find a replacement for an editor I've used for decades (called AkelPad). I've just discovered CudaText and WOW! I am impressed. It does almost everything I need and it does a whole lot more than AkelPad ever did (not least the support for Linux, one of the reasons why I am looking to replace AP).
So first of all A BIG THANK YOU to the developers and everybody involved in creating this editor. Great work.
However
of course there are some things that I am missing. Nothing save point 1 is especially important, so take this as a wish list for days when the developers have nothing else to do 
1. I'm editing loads of C/C++, Lua and Python files. I am also editing many free flow text files (written in a sort of private markdown) and I've already written a lite lexer for this file type (super easy, kudos!). My problem is simple: I want all programming files to open always with word wrap OFF and all files with my private markdown file extension to open always with word wrap ON. I've tried to google for this but failed. I'd think it should be easy to put something like this into the lexer logic.
2. Staying with my markdown files, long logical lines do wrap as they should. It would be nice if there was some visual hint at the beginning and end of physical continuation lines (ie when the logical line wraps into a few physical lines).
3. I love the changed/saved lines feature (ie the coloured marker in the gutter). A small niggle here is that if I change a line and then undo the change (Ctrl-Z) the changed marker stays there.
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?
5. Are there any plans to include an incremental search facility (ie a find-as-you-type )?
6. Windows: "cudatext *.c" tries to open "*.c" instead of opening all .c files in the current directory. I am not sure this warrants any work as it would require special command line handling for Windows. It's just something I am used to do.
Again, thanks for a fine tool.
So first of all A BIG THANK YOU to the developers and everybody involved in creating this editor. Great work.
However
of course there are some things that I am missing. Nothing save point 1 is especially important, so take this as a wish list for days when the developers have nothing else to do 1. I'm editing loads of C/C++, Lua and Python files. I am also editing many free flow text files (written in a sort of private markdown) and I've already written a lite lexer for this file type (super easy, kudos!). My problem is simple: I want all programming files to open always with word wrap OFF and all files with my private markdown file extension to open always with word wrap ON. I've tried to google for this but failed. I'd think it should be easy to put something like this into the lexer logic.
2. Staying with my markdown files, long logical lines do wrap as they should. It would be nice if there was some visual hint at the beginning and end of physical continuation lines (ie when the logical line wraps into a few physical lines).
3. I love the changed/saved lines feature (ie the coloured marker in the gutter). A small niggle here is that if I change a line and then undo the change (Ctrl-Z) the changed marker stays there.
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?
5. Are there any plans to include an incremental search facility (ie a find-as-you-type )?
6. Windows: "cudatext *.c" tries to open "*.c" instead of opening all .c files in the current directory. I am not sure this warrants any work as it would require special command line handling for Windows. It's just something I am used to do.
Again, thanks for a fine tool.
It also should focus on the left box, IMHO. (Additionally I found a problem with that plugin when I defined a keyboard shortcut for the find-in-lines function: I can define the shortcut and it works in the session... but after exiting the editor and restarting the shortcut is gone. NBD but perhaps worth looking into.)