RJ TextEd

Hi,
I used one of the scripts on <https://superuser.com/questions/1603763 ... windows-10>. The script generated a text file, but RJ TextEd gives an error when opening it: "Access violation at address 0000000002CBB77B in module 'rtl280.bpl'. Read of address <...>".

The problem sees to be that RJ TextEd can't manage files containing lines that are more than 108 spaces, plus CR+LF end-of-line. Files containing lines that are 109 or 110 spaces plus CR+LF can be opened by double-click, but not by the history drop-down list. Files containing lines that are more than 110 spaces plus either LF or CR-LF always give error.

I have attached an archive containing two one-line text files that illustrate the situation.

I am using the last version of Windows 11 and of RJ TextEd

Thanks for a great program and best regards

I can open both files -- from my file manager and from RJ TE's own file explorer -- without any problem.

I am using a proportional font (Lucida Sans, size 12) as main font. And a monospaced font (Consolas,size 12) as alternate font.

If I open the problematic file with the proportional font, everything is fine. I activate or deactivate "word wrap", no problem. I try a different proportional font (Arial, size 12), everything remains OK.

If I open the problematic file with the monospaced font, and no "word wrap", everything is fine. However, if I activate "word wrap", I get the error.

If I try a different monospaced font (Courier New, size 12), I get the same result. No "word wrap", no problem. "Word wrap", error.

My "word wrap" configuration is:
"Wordwrap at legal breakpoints..." no.
"Indent wrapped lines" yes.
"Word wrap at" window edge
"Always set word wrap for new documents" yes
"Turn on wordwrap" yes
"Save wordwrap state" yes.

I have followed your settings, yet still can open both files without any problem. However, this is how it looks (I have resized down my editor's window to show the effect):
I guess something is off here. I use only monospaced fonts. Btw I can't check "Save wordwrap state", as this option is dimmed.

Fixed in next version (15.60). Thanks!