Great editor; some questions/suggestions

tmsg
Posts: 120
Joined: 20.05.2020 12:08

Great editor; some questions/suggestions

Post by tmsg »

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 :D 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 :o

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.
Alexey
Posts: 1633
Joined: 05.10.2012 22:10

Post by Alexey »

Thanks, these sound like valid wishes/reports.
About 1: confirmed that it is some bug here, seems.
recorrded it to Github https://github.com/Alexey-T/CudaText/issues/2575

About 6 (file masks in command line): valid wish. Sublime supports this.
https://github.com/Alexey-T/CudaText/issues/2576
Alexey
Posts: 1633
Joined: 05.10.2012 22:10

Post by Alexey »

2. how that visual hint may look? give me a hint, maybe screenshot from other editors?
5. plugin CudaExt support this - command "Find in lines". but I see some issues in it
https://github.com/kvichans/cuda_ext/issues/143
tmsg
Posts: 120
Joined: 20.05.2020 12:08

Post by tmsg »

Alexey, thanks for looking into this.

Re 2. See the attached image for the end-of-line visuals (this is from AkelPad). Beginning of line is not as imported as the missing line number gives a hint that this is a continuation line.
1.jpg
1.jpg (5.34 KiB) Viewed 1233 times
Re 5. I'll have a look into the plugin you mentioned. EDIT: So I did and as you said, it's buggy ;) 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.)

And guess what...? I do have a point #7 :D A command line switch to load a user-specified user.json file instead of the default (ie "cudatext -u c:\some\path\to\myuser.json") would be nice.

I also have something that may or may or not be a bug. If I set "ui_one_instance" to true and load a file I get the first instance. If I load a second file with "cudatext -ns test.txt" I get the attached error. It seems the second instance just hands over all command line arguments to the first instance and the first doesn't filter command line switches. (I could leave off the -ns but this is really part of a collection of command line aliases to start my text editor for various editing tasks, some requiring sessions while others are just quick-and-dirty edit jobs.)
2.jpg
2.jpg (8.14 KiB) Viewed 1233 times
Alexey
Posts: 1633
Joined: 05.10.2012 22:10

Post by Alexey »

command line issue - recorded, thanks.

render marks for wrapped lines- done now, as on picture,
Attachments
Screenshot from 2020-05-20 19-02-02.png
Alexey
Posts: 1633
Joined: 05.10.2012 22:10

Post by Alexey »

>(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.

I didn't repeat it on Linux. maybe you defined the hotkey with [x]for current lexer?
pls, post here your file 'settings/keys.json'.
tmsg
Posts: 120
Joined: 20.05.2020 12:08

Post by tmsg »

Alexey wrote:render marks for wrapped lines- done now, as on picture,
Wow. That was fast :D
Alexey wrote:>I didn't repeat it on Linux. maybe you defined the hotkey with [x]for current lexer?
No, I didn't. I tried it twice and the error persisted.
Alexey wrote:>pls, post here your file 'settings/keys.json'.
Can't as I have already removed both the plugin and all its changes. But I will define many more shortcuts for various plugins in the coming days and if this crops up again, I'll let you know.

So far so good :!:
Alexey
Posts: 1633
Joined: 05.10.2012 22:10

Post by Alexey »

yes, if you set some plugin hotkey, and it don't work, post your file keys.json.
Alexey
Posts: 1633
Joined: 05.10.2012 22:10

Post by Alexey »

Alexey
Posts: 1633
Joined: 05.10.2012 22:10

Post by Alexey »

@tmsg
just fixed that lexer-specific configs were not able to apply several editor opts (wrap mode, font scale, show ruler/minimap/micromap....).
it's about your wish point 1.
just use lexer-specific configs
https://wiki.freepascal.org/CudaText#Configs
Post Reply