Scrolling up does not apply all Regexes

[aaronols]

Description

1. ssh some-server | ct
2. open log file with less on remote server
3. find some colorized lines
4. scroll down until the lines are out of view
5. scroll back up
6. Only some regexes are applied again

Scrolling down seems to always apply all regexes correctly while scrolling up fails to apply some of the more complicated ones..
It appears that the regexes applied when scrolling up are only the most simple ones.

Environment

• Terminal: zsh in tmux on wsltty
• OS: [Ubuntu 18.04.3 LTS @ WSL @ Win10 1803 build 17134.1039]
• ChromaTerm: [0.5.1]

Configuration

This happens with the default configuration.
One pattern I observed not to be reapplied when scrolling up in the remote logs is the date Pattern in the format YYYY-MM-DD.
The time pattern was correctly reapplied when scrolling up though.

[hSaria]

Thanks for raising this.

It seems like less uses the REVERSE LINE FEED (\eM) sequence which ct doesn't currently understand as a movement sequence.

I've only used the Wiki page for ANSI codes as my initial reference for movement sequences, like those that move the cursor around in vim. Clearly, I need to go straight to the standard. Should be finished in a bit.

I wanted to error on the safe side and only put the sequences that I know perform movements which are then used as a separators when processing the input; most programs would just line-buffer and use new-line as a separator, but as that wouldn't work here (need to support interactive programs), I had to separate based on a lot what I consider as "movement" sequences.

Update: less is actually using REVERSE LINE FEED \eM, not to be confused with DELETE LINE \e[M.

[hSaria]

Fixed in 6c1a79f. v0.5.2 will be published soon (tomorrow probably).

[aaronols]

Thank you very much for fixing this too. It works marvellously 👍

[hSaria]

And thank you for raising the issue. I greatly appreciate it.

…

On 21 Oct 2019, at 9:27 am, aaronols ***@***.***> wrote:  Thank you very much for fixing this too. It works marvellously 👍 — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.