From 8debe6a97fe8eb92ac9fb296df9e405bc1be2647 Mon Sep 17 00:00:00 2001 From: Michael Stapelberg Date: Mon, 22 Mar 2010 23:22:42 +0100 Subject: [PATCH] Remove obsolete paragraph about the need for a second connection Due to the event-based handling of incoming data from i3 we do not suffer from this problem. --- lib/AnyEvent/I3.pm | 4 ---- 1 file changed, 4 deletions(-) diff --git a/lib/AnyEvent/I3.pm b/lib/AnyEvent/I3.pm index 310fa5ef..d763357c 100644 --- a/lib/AnyEvent/I3.pm +++ b/lib/AnyEvent/I3.pm @@ -27,10 +27,6 @@ This module connects to the i3 window manager using the UNIX socket based IPC interface it provides (if enabled in the configuration file). You can then subscribe to events or send messages and receive their replies. -Note that as soon as you subscribe to some kind of event, you should B -send any more messages as race conditions might occur. Instead, open another -connection for that. - use AnyEvent::I3 qw(:all); my $i3 = i3("/tmp/i3-ipc.sock"); -- 2.39.5