Skip to content
This repository has been archived by the owner on Apr 17, 2020. It is now read-only.

hilighting not triggered in a /msg window #598

Closed
irssibot opened this issue May 29, 2008 · 3 comments
Closed

hilighting not triggered in a /msg window #598

irssibot opened this issue May 29, 2008 · 3 comments

Comments

@irssibot
Copy link
Collaborator

Greetings,

By adding the MSGS level to the hilight_level setting like this:

hilight_level = PUBLIC DCCMSGS MSGS

One would expect irssi to hilight text matching regular expressions or hilight keywords sent by other people over MSGS, but unfortunately it does not seem to and just treats the line of text normally.

This behaviour is often quite frustrating as people sending MSGS are unable to trigger irssi's hilighting and attract one's attention, meaning there can be long delays in responding to urgent MSGS from people. Unfortunately I am not aware of any relevant information that might cause the unexpected hilighting behaviour, whether or not it is an isolated issue I am experiencing, or how it might be resolved.

Thank you in advance for your time and consideration.

@irssibot
Copy link
Collaborator Author

Strange, I'm testing with a clean config, and sometimes it works, and sometimes it doesn't.
I think it doesn't notice immediately that the setting changed.
For example, startup from a clean config:
/hilight pom
/set hilight_level PUBLIC MSGS

  • send msg with "pom" in it => no hilight
    /hilight somethingelse
  • send same msg again => pom hilights.

If setting hilight_level before doing "/hilight pom", it does work correctly.

Does adding another (unrelated) hilight fix it for you too?

@irssibot
Copy link
Collaborator Author

irssibot commented Jun 1, 2008

Hi Coekie,

Thanks for taking a look and getting back to me. Yeah, I believe I am experiencing the same thing. Adding a new hilight to irssi's hilight list caused the new and existing hilights in MSGS to start triggering as they should. So yeah it seems that something has to be done in order for irssi to notice the change.

Do we know if this is by design, or if it is just an undesirable by-product of how it works?

@irssibot
Copy link
Collaborator Author

irssibot commented Sep 1, 2008

fixed in r4857

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

1 participant