When using color highlighting triggers, high volume of test makes iterm unresponsive.

By bruce.e... on October 31, 2013 15:49 (imported from Google Code)

---

When more than a couple of highlight regexps are in use and there is a lot of text scrolling continuously, iterm2 stops responding to the keys until the text output stops.
It appears to be that iterm is falling behind in the text output processing because of the colorization load and is not getting to the check for input method until it is caught up.
That may be an oversimplification, but it describes the perception from the user side.

osx Build 1.0.0.20130624

---

com.googlecode.iterm2.plist

Comment 1 by bruce.e... on November 04, 2013 16:28

---

I think this may be a tmux problem and not related to iterm.
It appears that all keys going through tmux are not responsive. All iterm controls are still functional.

Comment 2 by gnach... on December 17, 2013 19:31

---

Unfortunately, regex matching is slow. This interacts badly with tmux, which lacks flow control.

One possible solution is to perform regex matching in a separate thread.

Comment 3 by gnach... on December 17, 2013 22:41

---

(No comment has been entered for this change)

---

Labels: Milestone: Release3.0

Milestone changed to Temporary Milestone

Milestone changed to Ship 3.0

Reassigned to @gnachman

Status changed to closed

Highlight triggers sped up in commit 13b94dee