From 6941e9cc5ef436f2759a56a10daa7f21652a1c18 Mon Sep 17 00:00:00 2001
From: Patrick Ziegler
Date: Sun, 13 Mar 2022 15:48:07 +0100
Subject: [PATCH] Revert
8574bdc10050d9e4003cb0cad6699ce588232acf...bede6e5f872415b06e4f7e81d60afd4e107596a0
on Inter process messaging
---
Inter-process-messaging.md | 91 +-------------------------------------
1 file changed, 1 insertion(+), 90 deletions(-)
diff --git a/Inter-process-messaging.md b/Inter-process-messaging.md
index 07df7d9..029f116 100644
--- a/Inter-process-messaging.md
+++ b/Inter-process-messaging.md
@@ -1,90 +1 @@
-Polybar supports controlling parts of the bar and its modules from the outside
-through inter-process-messaging (IPC).
-
-IPC is disabled by default and can be enabled by setting ``enable-ipc = true``
-in the bar section.
-
-By default polybar ships with the ``polybar-msg`` tool that is needed to send
-messages to polybar.
-
-Note
-
-Starting with version 3.6.0, the underlying IPC mechanism has been completely changed.
-
-Writing directly to the named pipe to send IPC messages has been deprecated, ``polybar-msg`` should be used exclusively Everything you could do by directly writing to the named pipe, you can also do using ``polybar-msg``. In addition, hook messages are also deprecated; they are replaced by actions on the :ref:`ipc module `.
-
-Unless noted otherwise, everything in this guide is still valid for older versions.
-
-Sending Messages
-----------------
-
-``polybar-msg`` can be called on the commandline like this:
-
-```
-polybar-msg [-p ]
-```
-
-If the ``-p`` argument is specified, the message is only sent to the running polybar instance with the given process ID. Otherwise, the message is sent to all running polybar processes that have IPC enabled.
-
-Note
-
-IPC messages are only sent to polybar instances running under the same user as ``polybar-msg`` is running as.
-
-Concretely, ``polybar`` and ``polybar-msg`` use the ``$XDG_RUNTIME_DIR`` environment variable in accordance with the [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html) to determine where to find the socket to communicate.
-
-If ``polybar`` and ``polybar-msg`` don't have the same value for ``$XDG_RUNTIME_DIR``, they will likely not be able to communicate. The variable may not be set if you use ``su`` or ``sudo`` to execute ``polybar-msg`` as a different user, often a full user session is required.
-
-
-The ```` argument is either :ref:`action ` or
-:ref:`cmd `.
-The allowed values for ```` depend on the type.
-
-Message Types
--------------
-
-Commands
-
-Using ``cmd`` for ````, you can control certain aspects of the bar.
-
-Available values for ```` are:
-
-* ``quit``: Terminates the bar
-* ``restart``: Restarts the bar in-place
-* ``hide``: Hides the bar
-* ``show``: Makes the bar visible again, if it was hidden
-* ``toggle``: Toggles between the hidden and visible state.
-
-.. _ipc-actions:
-
-Module Actions
-
-For the ```` ``action``, ``polybar-msg`` can execute :doc:`module actions ` in the bar.
-
-An action consists of the name of the target module, the name of the action and an optional data string:
-
-```
-#.[.]
-```
-
-More information about action strings and available actions can be found in :doc:`actions`
-
-For example, if you have a date module named ``date``, you can toggle between the regular and alternative label with:
-
-```
-polybar-msg action "#date.toggle"
-```
-
-As an example for an action with data, say you have a menu module named ``powermenu``, you can open the menu level 0 using:
-
-```
-polybar-msg action "#powermenu.open.0"
-```
-
-Note
-
-For convenience, ``polybar-msg`` also allows you to pass the module name, action name, and data as separate arguments:
-
-```
-polybar-msg action date toggle
-polybar-msg action powermenu open 0
-```
\ No newline at end of file
+**❗️❗️❗️This page has moved. Please find the newest version of this document [here](https://polybar.readthedocs.io/en/stable/user/ipc.html).❗️❗️❗️**