Delay in trigger highlight
ciscohack opened this issue · comments
ChromaTerm version
v0.10.3
Terminal
Alacritty
What's happening?
Hi hSaria,
I have upgraded to the latest CT code and observed a delay in trigger, especially with the telnet/ssh session and normal log will test later
Please describe how you’re using ChromaTerm (i.e whether you’re running it using
ssh | ctor using terminal-wide highlighting. Also, where is the output coming from? A console connection?
…
On 9 May 2022, at 7:30 am, ciscohack @.***> wrote: ChromaTerm version v0.10.3 Terminal Alacritty What's happening? Hi hSaria, I have upgraded to the latest CT code and observed a delay in trigger, especially with the telnet/ssh session and normal log will test later — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.
I am using terminal wide highlighting above output is coming from telnet session but having issues with ssh sessions and sometimes with local log file also but very minimal. the major issue is with the telnet/ssh session. console connection not tried but that might also have an issue
Based on what you're describing, that behaviour is to be expected. To support interactive applications, this cannot change. It'll continue to happen whenever the output freezes for a brief period.
@hSaria if they delay can we optimize anyhow to avoid impact a little less and trigger show up with less delay would be good. Anyway thanks
@hSaria can you help me to know how can I go back to 0.10.2 release trigger on 0.10.2 is much better than the latest 0.10.3 ..- I still feel there is room to improve if we explore anyway just help me to know how do I roll back the update to 0.10.2
I wanted to go back to the 0.10.2 code. the issue I am highlighting I raised last year also and you and I worked and improved but that issue seems to come back with the 0.10.3 release so I want to go back to 0.10.2
pip3 install chromaterm==0.10.1
…
On 10 May 2022, at 4:16 pm, ciscohack @.***> wrote: @hSaria can you help me to know how can I go back to 0.10.1 release trigger on 0.10.1 is much better than the latest 0.10.3 ..- I still feel there is room to improve if we explore anyway just help me to know how do I rollback the update to 0.10.1 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.
Yes, I already tried this but due to some reason it's not working ..seems the default path for ct in this way not pointing to /usr/local/bin. I downloaded the source code and installed ct 0.10.1 and 0.10.2 trigger much much better than 0.10.3