-actcolor parameter for /highlight is not always respected

[urbec-guest]

Hi,

while trying to set two differently colored highlights for my nickname,
depending on if it's the first word in the line or not,
I observed the following.
(as using a random word had the same results, I'll use the string "aaa" here)

Commands used:

/hilight -actcolor %G -color %G -regexp (?!^)aaa
/hilight -actcolor %M -color %M -regexp ^aaa

Expected behaviour:

• If "aaa" is at the beginning of a line (eg aaa is this),
  there is a magenta colored highlight,
  both in the status bar and in the channel where "aaa" was written.
• If "aaa" is somewhere else than the beginning of line (eg this is aaa),
  both highlights happen in green.

Actual behaviour:

• If "aaa" is at the beginning of a line (eg aaa is this),
  there is a magenta colored highlight in the channel where "aaa" was written,
  but the highlight in the status bar is green.
• If "aaa" is somewhere else than the beginning of line (eg this is aaa),
  both highlights happen in green as expected.

If /hilight -actcolor %M -color %M -regexp ^aaa
is used alone, the coloring is as expected,
so the two commands seem to interfere with each other;
though not sure how, because if one command just would falsely match both cases, I'd expect both colors being wrong.

[terminaldweller]

just a bit of extra info, but if you set the nick to no and just ask it to hilight the word itself(aaa in our example), then irssi will always match aaa both at the start or end as green. we never see magenta.