You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>Default shortcut for evaluating the current top level form: <code>alt+enter</code>.</p>
2372
2372
<p>The <strong>current top-level form</strong> means top-level in a structural sense. It is <em>not</em> the topmost form in the file. Typically in a Clojure file you will find <code>def</code> and <code>defn</code> (and <code>defwhatever</code>) forms at the top level, which also is one major intended use for evaluating top level form: <em>to define and redefine variables</em>. However, Calva does not check the contents of the form in order to determine it as a top-level forms: <em>all forms not enclosed in any other form are top level forms</em>.</p>
2373
2373
<p>An ”exception” is introduced by the <code>comment</code> form. It will create a new top level context, so that any forms immediately inside a <code>(comment ...)</code> form will be considered top-level by Calva. This is to support a workflow with what is often referred to the <ahref="../rich-comments/">Rich Comments</a>.</p>
2374
+
<p>A special case is ignored forms (using the <code>#_</code> marker) at the top level. They will always be selected as top level forms separately from their ignore marker, enabling evaluating them as top level forms. Similar to Rich Comments.</p>
2374
2375
<p>At the top level the selection of which form is the current top level form follows the same rules as those for <ahref="#current-form">the current form</a>.</p>
<p>Default shortcut for evaluating the current top level form: <code>alt+enter</code>.</p>
2372
2372
<p>The <strong>current top-level form</strong> means top-level in a structural sense. It is <em>not</em> the topmost form in the file. Typically in a Clojure file you will find <code>def</code> and <code>defn</code> (and <code>defwhatever</code>) forms at the top level, which also is one major intended use for evaluating top level form: <em>to define and redefine variables</em>. However, Calva does not check the contents of the form in order to determine it as a top-level forms: <em>all forms not enclosed in any other form are top level forms</em>.</p>
2373
2373
<p>An ”exception” is introduced by the <code>comment</code> form. It will create a new top level context, so that any forms immediately inside a <code>(comment ...)</code> form will be considered top-level by Calva. This is to support a workflow with what is often referred to the <ahref="../rich-comments/">Rich Comments</a>.</p>
2374
+
<p>A special case is ignored forms (using the <code>#_</code> marker) at the top level. They will always be selected as top level forms separately from their ignore marker, enabling evaluating them as top level forms. Similar to Rich Comments.</p>
2374
2375
<p>At the top level the selection of which form is the current top level form follows the same rules as those for <ahref="#current-form">the current form</a>.</p>
0 commit comments