title: remote emacs client connects, but doesn't create new frame in terminal
body: <p>I configured and started an emacs server in TCP mode:</p>
  
  <ol>
  <li>Added <code>(setq server-host "10.16.184.33")</code> and <code>(setq server-use-tcp t)</code> to .emacs</li>
  <li>ran <code>emacs --daemon</code></li>
  </ol>
  
  <p>On the same host, running <code>emacsclient -t</code> brings up an emacs frame in the current terminal, and running <code>emacsclient -c</code> brings up a new graphical client frame, as expected.</p>
  
  <p>On a different host, running <code>emacsclient -t -f ~/.emacs.d/server/server</code> appears to successfully connect to the remote emacs server, but no frame is created in the terminal:</p>
  
  <pre><code>$ emacsclient -t -f ~/.emacs.d/server/server
  emacsclient: connected to remote socket at 10.16.184.33
  </code></pre>
  
  <p>At this point, emacsclient is running in the foreground, and a Ctrl-c stops it with a SIGTERM.</p>
  
  <p>the value of the <code>server-client</code> variable shows that remote emacs client is connected:</p>
  
  <pre><code>server-clients's value is
  (#&lt;process server &lt;10.16.184.33:52710&gt;&gt; #&lt;process server &lt;10.16.177.8:59460&gt;&gt;)
  </code></pre>
  
  <p>Things that I've checked:</p>
  
  <ul>
  <li>versions of Emacs and emacsclient: all 24.3</li>
  <li>when swapping which machines are the server and the remote client, the same problem occurs, except...</li>
  <li><p>emacsclient prints an extra error message</p>
  
  <pre><code>emacsclient: connected to remote socket at 10.16.177.8
  *ERROR*: Could not open file: /dev/pts/26
  </code></pre></li>
  </ul>
  
  <p>Any ideas of what else to check or configure?</p>