The triggers do not follow a specific order and there is no option to stop processing further triggers

By sorin.sbar... on November 22, 2012 17:27 (imported from Google Code)

---

The triggers do not follow a specific order and there is no option to stop processing further triggers

I do have many triggers, most of them being used to color the screen output. One of the major problems is that when they overlap (which is something quite normal), there is no way to obtain a consistent behaviour.

Other problems related to the same area:

• unable to reorder triggers
• unable to resize the window, which can prove to be too small
• no way to restore or cancel any change, once made, you cannot undo, and when it's about a big regex this can be really painful
• editing the triggers is too painful, much harder than editing a text file

---

Comment 1 by gnach... on December 01, 2012 23:27

---

(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

Commit 905e9faa adds drag-drop for triggers.

The window is resizable and triggers appear to be applied in order.

Remaining issues are:

• Undo support
• Easier editing
• Stop processing further triggers
• Options to change only fg or bg color while leaving the other alone
• Color-sensitive triggering conditions

Undo support added in commit 493112f8

If you have a giant regex, copy-paste is the most sensible way to edit it. Not sure it's worth reworking the UI in a big way for this when there's an easy alternative.

Options to change only fg/bg were added a long while ago.

Added Stop Processing Triggers in 6e6e52d8.

Status changed to closed

Regarding UI-rework: keeping all these settings in UI slows down iTerm considerably. I would see migration to text config files (for most options) as a great benefit that would only improve the overall product experience. You can always keep most of the current UI for not so savvy users.