|
2641 | 2641 |
|
2642 | 2642 | <h1 id="connect-calva-to-your-project">Connect Calva to Your Project<a class="headerlink" href="#connect-calva-to-your-project" title="Permanent link">#</a></h1> |
2643 | 2643 | <p>When connected to your project's REPL Calva lets you evaluate code, supporting Interactive Programming. The REPL connection is also used to provide IDE functionality through the dynamic knowledge about the project that the REPL enables. The REPL communication depends on that your project has an <a href="https://github.com/nrepl/nrepl">nREPL</a> server running, and that the <a href="https://github.com/clojure-emacs/cider-nrepl">cider-nrepl</a> middleware is enabled.</p> |
| 2644 | +<p><img alt="alt text" src="../images/connections-menu.png" /></p> |
2644 | 2645 | <p>For the easiest way to provide your project with these dependencies, the recommended way to connect is to use the so called <strong>Jack-in</strong> command.</p> |
2645 | 2646 | <h2 id="jack-in-let-calva-start-the-repl-for-you">Jack-in: Let Calva Start the REPL For You<a class="headerlink" href="#jack-in-let-calva-start-the-repl-for-you" title="Permanent link">#</a></h2> |
2646 | 2647 | <p>This way Calva can make sure it is started with the dependencies needed for a working Clojure and/or ClojureScript session. This is often referred to as <strong>Jack in</strong> (because that is what it is called in CIDER).</p> |
@@ -2688,7 +2689,7 @@ <h3 id="how-it-works">How It Works<a class="headerlink" href="#how-it-works" tit |
2688 | 2689 | <li>You connect the browser to the same port (e.g. via Epupp, or by loading a page with Scittle nREPL)</li> |
2689 | 2690 | <li>Calva picks up the connection — you can evaluate code, get completions, look up docs</li> |
2690 | 2691 | </ol> |
2691 | | -<p>If the browser disconnects (tab reload, navigation, tab close), Calva keeps the server running and waits for a reconnection. When the browser comes back, Calva resumes automatically.</p> |
| 2692 | +<p>If the browser disconnects (tab reload, navigation, tab close), Calva keeps the server running and waits for a reconnection. When the browser comes back, Calva resumes automatically. You can stop the server from the <strong>Disconnect REPL Connection...</strong> menu.</p> |
2692 | 2693 | <div class="admonition note"> |
2693 | 2694 | <p class="admonition-title">One browser client at a time</p> |
2694 | 2695 | <p>Calva's WebSocket server accepts one client connection. If a new browser or browser tab connects, Calva switches to the new client. This means Calva is always connected to whichever browser client most recently connected to its server.</p> |
@@ -2749,7 +2750,7 @@ <h3 id="configuration">Configuration<a class="headerlink" href="#configuration" |
2749 | 2750 | <span class="w"> </span><span class="p">]</span> |
2750 | 2751 | <span class="p">}</span> |
2751 | 2752 | </code></pre></div> |
2752 | | -<p>See <a href="../connect-sequences/">Connect Sequences</a> for the full <code>webSocketPort</code> reference.</p> |
| 2753 | +<p>See also: <a href="../connect-sequences/">Connect Sequences</a>.</p> |
2753 | 2754 | <h3 id="port-conflicts">Port Conflicts<a class="headerlink" href="#port-conflicts" title="Permanent link">#</a></h3> |
2754 | 2755 | <p>WebSocket ports are shared across the OS. If the port is already in use (by another VS Code window or another process), Calva will prompt you with the port pre-filled so you can either enter a different port or free the existing one and retry.</p> |
2755 | 2756 | <h3 id="using-with-scittle">Using with Scittle<a class="headerlink" href="#using-with-scittle" title="Permanent link">#</a></h3> |
|
0 commit comments