[skip ci]

api/index.html

@@ -3050,6 +3050,7 @@ <h3 id="replonoutputlogged"><code>repl.onOutputLogged()</code><a class="headerli
 <span class="w">  </span><span class="nx">replSessionKey?</span><span class="o">:</span><span class="w"> </span><span class="kt">string</span><span class="p">;</span><span class="w"> </span><span class="c1">// The REPL session key (e.g. &quot;clj&quot;, &quot;cljs&quot;), when applicable</span>
 <span class="p">}</span>
 </code></pre></div>
+<p>Calva emits exactly one <code>evaluatedCode</code> message per evaluation. For <code>repl.evaluate()</code>, that message is independent of <code>calva.evaluationSendCodeToOutputWindow</code>, and the visible copy of the evaluated code goes to the configured eval-results destination. The setting now only controls the extra REPL Window echo used by manual/UI evaluations.</p>
 <h3 id="replevaluatecode-deprecated"><code>repl.evaluateCode()</code> <em>(deprecated)</em><a class="headerlink" href="#replevaluatecode-deprecated" title="Permanent link">#</a></h3>
 <div class="admonition warning">
 <p class="admonition-title">Deprecated</p>

custom-commands/index.html

@@ -2292,7 +2292,7 @@ <h1 id="custom-repl-commands">Custom REPL Commands<a class="headerlink" href="#c
 <li><code>key</code>: A key can be used to reference the snippet from <strong>Run Custom REPL Command</strong> keyboard shortcut arguments. It will also be used in the quick-pick menu.</li>
 <li><code>ns</code>: A namespace to evaluate the command in. If omitted the command will be executed in the namespace of the current editor.</li>
 <li><code>repl</code>: Which repl session to use for the evaluation. Either <code>"clj"</code> or <code>"cljs"</code>. Omit if you want to use the session of the current editor.</li>
-<li><code>evaluationSendCodeToOutputWindow</code>: (default <code>true</code>) Whether the evaluated code should be echoed to the Output/REPL window.</li>
+<li><code>evaluationSendCodeToOutputWindow</code>: (default <code>true</code>) Whether the evaluated code should also be echoed to the configured output destination for results.</li>
 </ul>
 <p>There are also substitutions available, which will take elements from the current state of Calva and splice them in to the text of your command before executing it. They are</p>
 <ul>

getting-started/index.html

@@ -425,15 +425,21 @@
     </span>
   </a>
 
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#create-a-mini-clojure-project" class="md-nav__link">
+    <nav class="md-nav" aria-label="Clojure Resources">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#create-a-try-clojure-starter-project" class="md-nav__link">
     <span class="md-ellipsis">
-      Create a mini Clojure project
+      Create a Try Clojure starter project
     </span>
   </a>
 
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
 
         <li class="md-nav__item">
@@ -2292,15 +2298,21 @@
     </span>
   </a>
 
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#create-a-mini-clojure-project" class="md-nav__link">
+    <nav class="md-nav" aria-label="Clojure Resources">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#create-a-try-clojure-starter-project" class="md-nav__link">
     <span class="md-ellipsis">
-      Create a mini Clojure project
+      Create a Try Clojure starter project
     </span>
   </a>
 
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
 
         <li class="md-nav__item">
@@ -2390,8 +2402,13 @@ <h2 id="clojure-resources">Clojure Resources<a class="headerlink" href="#clojure
 <li><a href="https://clojurescript.org/guides/quick-start">ClojureScript Quick Start</a></li>
 </ul>
 <p>There are also many great books on Clojure. <a href="https://www.braveclojure.com/clojure-for-the-brave-and-true/">Clojure for the Brave and True</a> can be read for free online. It is a great resource for beginners.</p>
-<h2 id="create-a-mini-clojure-project">Create a mini Clojure project<a class="headerlink" href="#create-a-mini-clojure-project" title="Permanent link">#</a></h2>
-<p>When you are more familiar with Calva, and want a standalone REPL, there is a separate command: <strong>Calva: Create a mini Clojure project</strong>. It will ask for folder to create the project in, and open this project for you, connecting the REPL. This project only contains one source file and has no build tooling. For creating more “real” project starters, we recommend using <a href="https://github.com/seancorfield/deps-new">deps-new</a>, by sSean Corfield.</p>
+<h3 id="create-a-try-clojure-starter-project">Create a Try Clojure starter project<a class="headerlink" href="#create-a-try-clojure-starter-project" title="Permanent link">#</a></h3>
+<p>If you want a minimal local project to poke around in (rather than the guided REPL above), use the command <strong>Calva: Create a </strong>Try Clojure<strong> project</strong>.</p>
+<ul>
+<li>It stages the “official” <a href="https://github.com/clojure/try-clojure">https://github.com/clojure/try-clojure</a> project and adds some few Calva settings.</li>
+<li>Only Java required</li>
+</ul>
+<p>For creating more “real” project starters, we recommend using <a href="https://github.com/seancorfield/deps-new">deps-new</a>, by Sean Corfield.</p>
 <h2 id="dram-where-the-guides-live">Dram - Where the Guides Live<a class="headerlink" href="#dram-where-the-guides-live" title="Permanent link">#</a></h2>
 <p>The command for starting the Getting Started REPL will download the files from <a href="https://github.com/BetterThanTomorrow/dram">this repository</a>. It is very much work in progress, and there is not even a finished Clojure Beginner's Guide there yet. When you run the command again, and from then on, you will get the option to download new files or keep using your existing. Downloading new ones will not overwrite your existing ones, because they will be downloaded to a new temp directory. You can find the directory easily using VS Codes context menu command for revealing a file in the Explorer/Finder.</p>
 <h2 id="one-last-thing">One Last Thing<a class="headerlink" href="#one-last-thing" title="Permanent link">#</a></h2>

output/index.html

@@ -2292,10 +2292,10 @@ <h2 id="output-destinations">Output Destinations<a class="headerlink" href="#out
 </ul>
 <p>With the setting <code>calva.outputDestinations</code>, you can configure where each category of output should go to. These are the allowed values and their descriptions:</p>
 <ul>
-<li><code>"repl-window"</code> - The <a href="../repl-window/">REPL Window</a> (an editor-based read/write output view). This is the default value.</li>
-<li><code>"output-view"</code> - The <a href="../output-view/">output view</a> (a read-only view that is much more performant than the REPL Window)</li>
-<li><code>"output-channel"</code> - The <em>Calva Says</em> Output Channel</li>
-<li><code>"terminal"</code> - The <em>Calva Output</em> (pseudo) Terminal</li>
+<li><code>"terminal"</code> - The <em>Calva Output</em> (pseudo) Terminal. This is the default value.</li>
+<li><code>"repl-window"</code> - The <a href="../repl-window/">REPL Window</a> (an editor-based read/write output view).</li>
+<li><code>"output-view"</code> - The <a href="../output-view/">output view</a> (a read-only view that is much more performant than the REPL Window).</li>
+<li><code>"output-channel"</code> - The <em>Calva Says</em> Output Channel.</li>
 </ul>
 <p>The reason there are several options for this is partly legacy and partly because VS Code restricts the placement of
 different views in different ways. We hope you will find a combination of output destinations that suits you.</p>

repl-window/index.html

@@ -2486,6 +2486,7 @@ <h1 id="the-repl-windowfile">The REPL Window/File<a class="headerlink" href="#th
 <p>The first prompt is from when the <code>clj</code> REPL is connected, and the second from <code>cljs</code>. The first <em>part</em> of the prompt tells you which REPL type the window is currently connected to.</p>
 <h2 id="using-the-repl-window-for-output">Using the REPL Window for output<a class="headerlink" href="#using-the-repl-window-for-output" title="Permanent link">#</a></h2>
 <p>By default the REPL Window doubles as the place where Calva sends output like stdout/stderr and other messages. See <a href="../output/">Calva Output</a> for more about this and how to change this behaviour.</p>
+<p>If you want manual evaluations to also echo the code itself there, use the <code>calva.evaluationSendCodeToOutputWindow</code> setting.</p>
 <h2 id="finding-the-repl-window">Finding the REPL Window<a class="headerlink" href="#finding-the-repl-window" title="Permanent link">#</a></h2>
 <p>If you quickly want to open and/or switch to the REPL Window there is the command <strong>Calva: Show/Open REPL Window</strong>, <code>ctrl+alt+o r</code>.</p>
 <p>To sync the REPL window namespace with the current file before switching, use the <strong>Switch Namespace of the REPL Window to Current Namespace</strong> command, <code>ctrl+alt+c alt+n</code>.</p>