Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
The event will be displayed in the most recently used window which belongs to the same server.
The event will be displayed in all windows which belong to the same server.
Syntax: channel:channelName [fallback]
The event will be displayed in the channel named channelName. If there is no such channel on the relevant server, the fallback parameter will be checked and if present, will be used as the target instead. If the fallback parameter doesn't exist in this case, the event is displayed in the parent window and a DMDirc user error is raised.
Syntax: comchans:userName [fallback]
The event will be displayed in any channel which userName is also present in. If there are no such common channels on the relevant server, the fallback parameter will be checked and if present, will be used as the target instead. If the fallback parameter doesn't exist in this case, the event is displayed in the parent window and a DMDirc user error is raised.
Allows multiple notification targets to be executed for the same event. Any number of notification targets may be specified, separated by the pipe character (|), but these targets may not contain pipes themselves. If you require pipes in a forked target, you can use the group: target as a work around.
Changes the format which will be used for the event in question to the one specified by formatName. The actual notification target is then determined by notificationTarget.
Uses the notification target defined in the setting named “notification.groupName”. The target within this group setting may be any notification target except for group or format.
Each window associated with the server is checked to find the last one which executed the command command. If no window executed a matching command, the target is treated as though it were “self”. The following rules apply to command:
It does not include the command or silence characters (e.g., 'foo' will match the user entering /foo and /.foo) It is treated as a regular expression It may reference arguments to the event in the same style as formatters - e.g. %1$s, %2$s, etc.
The event is not displayed.
The event will be displayed in the window that owns it, i.e. the channel window for channel events, server window for server events, etc.
The event will be displayed in the server window which owns the window that the event belongs to.
The event will be displayed in a window called windowName, belonging to the server. If the window does not exist, it will be opened when the first event is received.