+Text viewer: Ctrl+End doesn't go to the end of the text

[RRPq0t]

Hello,

in the 8.5 betas (and below), if a viewed text file doesn't have CRLF at the end of the text:

-The above mentioned keyboard shortcut takes the cursor to the beginning of the last line, and not to the end of it.

-So, the cursor is at the beginning of the last line. Shift+End doesn't select the last line. It stays at the beginning of the last line.

I've installed v8.01 and v7.57, tested on both x32 and x64 versions of TC, the results are the same.

-By the way, does TC handle CR or LF line endings? Because it displays dots (like this: . )instead of breaking lines at those.

The problem is, I don't know, on what config worked the viewer well, as I think it should work well.

Os.: Win7 x64 Hun

Thanks.
Best Regards: RRP"

[sqa_wizard]

text file doesn't have CRLF at the end of the text:
- Ctrl+End doesn't go to the end of the text
- Shift+End doesn't select the last line.

Sorry, I cannot reproduce this behavior.

Internal Lister just goes to the end of the last line with Ctrl+End and marks the whole line with Shift+End.
Tried with CRLF and LF at whole text but last line.

May you use a lister plugin (shows up in the header line of the viewer)?

[RRPq0t]

OK, I've found the solution: Uniscribe was disabled in the [Viewer] section in wincmd.ini.
Enabling it made the problem disappear.

From HISTORY.TXT:
...
28.01.09 Release Total Commander 7.50 Beta 8
...
27.01.09 Fixed: Lister, Uniscribe (e.g. Unicode or UTF-8): Couldn't put cursor behind last character of last line if no line break present, also caused selection problems
...

Maybe that fix didn't solve the root of the problem?

BR.
RRP"

[Dalai]

I disabled Uniscribe in my TC a few years ago and never had a problem in any text file, ANSI, UTF-8, with or without BOM. I just tested it with TC 8.01 and TC 8.5 beta 14 with an UTF-8 Bash script (with and without BOM) and couldn't see any issue with Ctrl+End.

BTW: Did you mean [Lister] section instead of [Viewer]?

And most importantly: Did you try a clean wincmd.ini?

EDIT: OK, I did some more tests and I can partially reproduce the issue in binary files if Uniscribe=0 and Lister is set to Unicode or UTF-8 view. Text files are fine, though. So, my guess is you have different line endings in your text file.

Regards
Dalai

[RRPq0t]

@Dalai: Yes, you are right [Lister] was the section.

Yes, I've tried a completely clean new install (I use a dedicated folder to save TC settings, so I've selected a new folder during install to be the new settings folder).

After copying the old [Lister] section to the new (vanilla) wincmd.ini, the problem appeared.
Enabling Uniscribe solved it.

Maybe the problem appears only, if Uniscribe is disabled, and some more settings are interfering.

My [Lister] section:

Code: Select all

[Lister]
AutoRotate=1
; 0: turns off automatic rotation of JPG images according to the EXIF orientation value
BgColor=0
BinWidth=75
BmpStartup=1
CenterBitmap=1
Codepage=0
Contextmenu1=A kijelölt szöveg keresése a Google-val|https://www.google.com/search?q=%s
; New right click menu entry to search for the selected text with Google. Can be customized (%s will be replaced by the search string) 
FgColor=12632256
HTMLasText=1
IView=1
IViewPath=e:\TotalCommanderSettings\utils\XnView\xnview.exe
LinkBraces=1
LinkColor=16747146
Maximized=0
Multimedia=1
RTF=1
SearchGoBack=3
Startup=16
TextWidth=81
Uniscribe=1
Wrap=0
dx=712
dy=726
x=233
y=48
ShrinkBitmap=1

Edit:
I think I've found it:
When Codepage=0 AND Uniscribe=0: the problem appears.
What means Codepage=0? AutoSelect?

BR.
RRP"

[ghisler(Author)]

I could reproduce the problem, it should be fixed now. Codepage can be any value >=0 (the default is -1).

[RRPq0t]

Thank you, I really appreciate your software support!

[ghisler(Author)]

So does it work correctly now for you?