| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
It was possible to be highlighted in the core.weechat buffer, and that
would trigger an AnyBar message and colour change. We don't want that to
happen, so move the 'core.weechat' check earlier to completely ignore
it.
|
|
|
|
We really only care about messages from other people, so don't bother
notifying when messages are added to the WeeChat core buffer.
|
|
|
|
If you've received a highlight and a normal message comes in, or if you
have a private message and get highlighted, then the AnyBar colour
should not change. We should keep the AnyBar colour of the highest
priority message.
|
|
After using the plugin for a couple days, I decided that orange is too
insistent a colour to describe messages I probably don't need to read
immediately.
Swap the blue and orange colours so that now blue means regular message
and orange means private message. This feels better in terms of message
priority.
|
|
If a message comes in on a buffer whose notify level is set to
highlights and higher, then don't update AnyBar activity.
We should only be changing the AnyBar colour when we receive messages
that we want to be notified of based on our configuration.
|
|
|
|
|
|
|
|
|
|
The `enable` subcommand should be a no-op if the hook is already
enabled.
|
|
|
|
Add new commands that enable and disable the print hook. We can use
these commands in terminal focus handlers, to turn on activity
monitoring when WeeChat is not focused, and turn it off once it is
focused.
|
|
Command to clear the activity notification colour from AnyBar and turn
it hollow.
|
|
|
|
Register a `hook_print` to get notified of activity in buffers. This
prints the message to the WeeChat core buffer.
|
