parent
dc98eade3b
commit
1adeef18a2
|
@ -512,7 +512,7 @@ function matcher:append_rules(source, rules)
|
|||
end
|
||||
end
|
||||
|
||||
--- Remove a new rule to the default set.
|
||||
--- Remove a new rule from the default set.
|
||||
-- @tparam string source The source name.
|
||||
-- @tparam string|table rule An existing rule or its `id`.
|
||||
-- @treturn boolean If the rule was removed.
|
||||
|
|
|
@ -139,7 +139,7 @@ gtable.crush(naughty, require("naughty.constants"))
|
|||
--
|
||||
-- When this is true, applications which query `naughty` feature support
|
||||
-- will see that animations are supported. Note that there is *very little*
|
||||
-- support for this and enabled it will cause bugs.
|
||||
-- support for this and enabling it will cause bugs.
|
||||
--
|
||||
-- @property image_animations_enabled
|
||||
-- @param[opt=false] boolean
|
||||
|
|
|
@ -419,7 +419,7 @@ local notification = {}
|
|||
--- The application name specified by the notification.
|
||||
--
|
||||
-- This can be anything. It is usually less relevant than the `clients`
|
||||
-- property, but can sometime to specified for remote or headless notifications.
|
||||
-- property, but can sometime be specified for remote or headless notifications.
|
||||
-- In these case, it helps to triage and detect the notification from the rules.
|
||||
-- @property app_name
|
||||
-- @param string
|
||||
|
|
Loading…
Reference in New Issue