From e7b354e0dcf031b331c89f095fc81fcd1ce9fd9f Mon Sep 17 00:00:00 2001
From: Michael Stapelberg <michael@stapelberg.de>
Date: Sat, 27 Mar 2010 15:22:28 +0100
Subject: [PATCH] docs: update for new ipc socket path

---
 docs/ipc       | 4 ++--
 docs/userguide | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/ipc b/docs/ipc
index 4e46bc9e..f65ae484 100644
--- a/docs/ipc
+++ b/docs/ipc
@@ -12,7 +12,7 @@ The method of choice for IPC in our case is a unix socket because it has very
 little overhead on both sides and is usually available without headaches in
 most languages. In the default configuration file, no ipc-socket path is
 specified and thus no socket is created. The standard path (which +i3-msg+ and
-+i3-input+ use) is +/tmp/i3-ipc.sock+.
++i3-input+ use) is +~/.i3/ipc.sock+.
 
 == Establishing a connection
 
@@ -21,7 +21,7 @@ snippet illustrates this in Perl:
 
 -------------------------------------------------------------
 use IO::Socket::UNIX;
-my $sock = IO::Socket::UNIX->new(Peer => '/tmp/i3-ipc.sock');
+my $sock = IO::Socket::UNIX->new(Peer => '~/.i3/ipc.sock');
 -------------------------------------------------------------
 
 == Sending messages to i3
diff --git a/docs/userguide b/docs/userguide
index 5cb1fe58..c706c631 100644
--- a/docs/userguide
+++ b/docs/userguide
@@ -504,11 +504,11 @@ programs to get information from i3, such as the current workspaces
 (to display a workspace bar), and to control i3.
 
 To enable it, you have to configure a path where the unix socket will be
-stored. The default path is +/tmp/i3-ipc.sock+.
+stored. The default path is +~/.i3/ipc.sock+.
 
 *Examples*:
 ----------------------------
-ipc-socket /tmp/i3-ipc.sock
+ipc-socket ~/.i3/ipc.sock
 ----------------------------
 
 You can then use the +i3-msg+ application to perform any command listed in