nixo
/
gri3-wm
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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.
This commit is contained in:
Michael Stapelberg 2010-03-22 23:22:42 +01:00
parent 1aac4d3f14
commit 45eef6bdf7
1 changed files with 0 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
lib/AnyEvent/I3.pm
View File

@ -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 IPC interface it provides (if enabled in the configuration file). You can
then subscribe to events or send messages and receive their replies. 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<NOT>
send any more messages as race conditions might occur. Instead, open another
connection for that.
use AnyEvent::I3 qw(:all); use AnyEvent::I3 qw(:all);
my $i3 = i3("/tmp/i3-ipc.sock"); my $i3 = i3("/tmp/i3-ipc.sock");