summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2016-05-09 20:39:33 +0200
committerwm4 <wm4@nowhere>2016-05-09 20:39:33 +0200
commit73aa7484f23b5fc006d930200b366d5193af9fe3 (patch)
tree2fa181db032e9742570727d12222b8b4d6d660f3
parent46fff8d31af0b79fe3de4aaee93bb66c248118a0 (diff)
downloadmpv-73aa7484f23b5fc006d930200b366d5193af9fe3.tar.bz2
mpv-73aa7484f23b5fc006d930200b366d5193af9fe3.tar.xz
manpage: fix some script_message references to preferred name
-rw-r--r--DOCS/man/input.rst8
-rw-r--r--DOCS/man/lua.rst6
-rw-r--r--DOCS/man/osc.rst4
3 files changed, 9 insertions, 9 deletions
diff --git a/DOCS/man/input.rst b/DOCS/man/input.rst
index 7b525d7aa8..2c434b17bb 100644
--- a/DOCS/man/input.rst
+++ b/DOCS/man/input.rst
@@ -634,10 +634,10 @@ Input Commands that are Possibly Subject to Change
Send a message to all clients, and pass it the following list of arguments.
What this message means, how many arguments it takes, and what the arguments
mean is fully up to the receiver and the sender. Every client receives the
- message, so be careful about name clashes (or use ``script_message_to``).
+ message, so be careful about name clashes (or use ``script-message-to``).
``script-message-to "<target>" "<arg1>" "<arg2>" ...``
- Same as ``script_message``, but send it only to the client named
+ Same as ``script-message``, but send it only to the client named
``<target>``. Each client (scripts etc.) has a unique name. For example,
Lua scripts can get their name via ``mp.get_script_name()``.
@@ -651,8 +651,8 @@ Input Commands that are Possibly Subject to Change
separator, e.g. ``script_binding scriptname/bindingname``.
For completeness, here is how this command works internally. The details
- could change any time. On any matching key event, ``script_message_to``
- or ``script_message`` is called (depending on whether the script name is
+ could change any time. On any matching key event, ``script-message-to``
+ or ``script-message`` is called (depending on whether the script name is
included), with the following arguments:
1. The string ``key-binding``.
diff --git a/DOCS/man/lua.rst b/DOCS/man/lua.rst
index 6b2c5af031..35124a788f 100644
--- a/DOCS/man/lua.rst
+++ b/DOCS/man/lua.rst
@@ -454,9 +454,9 @@ are useful only in special situations.
The level is a string, see ``msg.log`` for allowed log levels.
``mp.register_script_message(name, fn)``
- This is a helper to dispatch ``script_message`` or ``script_message_to``
- invocations to Lua functions. ``fn`` is called if ``script_message`` or
- ``script_message_to`` (with this script as destination) is run
+ This is a helper to dispatch ``script-message`` or ``script-message-to``
+ invocations to Lua functions. ``fn`` is called if ``script-message`` or
+ ``script-message-to`` (with this script as destination) is run
with ``name`` as first parameter. The other parameters are passed to ``fn``.
If a message with the given name is already registered, it's overwritten.
diff --git a/DOCS/man/osc.rst b/DOCS/man/osc.rst
index 587b8104d2..c737d2e898 100644
--- a/DOCS/man/osc.rst
+++ b/DOCS/man/osc.rst
@@ -266,6 +266,6 @@ Example
You could put this into ``input.conf`` to hide the OSC with the ``a`` key and
to set auto mode (the default) with ``b``::
- a script_message osc-visibility never
- b script_message osc-visibility auto
+ a script-message osc-visibility never
+ b script-message osc-visibility auto