]> matita.cs.unibo.it Git - helm.git/blobdiff - helm/software/matita/help/C/sec_commands.xml
More commands documented.
[helm.git] / helm / software / matita / help / C / sec_commands.xml
index 0ea8c06f970ee618dd6e76510a39b81f1a6efd5c..7141d0ddffd1ff22dab3ded1fa43c6521f564fcf 100644 (file)
@@ -13,9 +13,9 @@
          <term>Synopsis:</term>
          <listitem>
            <para><emphasis role="bold">alias</emphasis>
-            [<emphasis role="bold">id</emphasis> <emphasis role="bold">&quot;</emphasis>&string;<emphasis role="bold">&quot;</emphasis> <emphasis role="bold">=</emphasis> <emphasis role="bold">&quot;</emphasis>&string;<emphasis role="bold">&quot;</emphasis>
-            | <emphasis role="bold">symbol</emphasis> <emphasis role="bold">&quot;</emphasis>&string;<emphasis role="bold">&quot;</emphasis> [<emphasis role="bold">(instance</emphasis> &nat;<emphasis role="bold">)</emphasis>] <emphasis role="bold">=</emphasis> <emphasis role="bold">&quot;</emphasis>&string;<emphasis role="bold">&quot;</emphasis>
-            | <emphasis role="bold">num</emphasis> [<emphasis role="bold">(instance</emphasis> &nat;<emphasis role="bold">)</emphasis>] <emphasis role="bold">=</emphasis> <emphasis role="bold">&quot;</emphasis>&string;<emphasis role="bold">&quot;</emphasis>
+            [<emphasis role="bold">id</emphasis> &qstring; <emphasis role="bold">=</emphasis> &qstring;
+            | <emphasis role="bold">symbol</emphasis> &qstring; [<emphasis role="bold">(instance</emphasis> &nat;<emphasis role="bold">)</emphasis>] <emphasis role="bold">=</emphasis> &qstring;
+            | <emphasis role="bold">num</emphasis> [<emphasis role="bold">(instance</emphasis> &nat;<emphasis role="bold">)</emphasis>] <emphasis role="bold">=</emphasis> &qstring;
             ]
            </para>
          </listitem>
  </sect1>
  <sect1 id="command_check">
    <title>check</title>
-   <para><userinput></userinput></para>
+   <para><userinput>check t</userinput></para>
    <para>
      <variablelist>
        <varlistentry role="tactic.synopsis">
          <term>Synopsis:</term>
          <listitem>
-           <para><emphasis role="bold">check</emphasis>
-           </para>
+           <para><emphasis role="bold">check</emphasis> &term;</para>
          </listitem>
        </varlistentry>
        <varlistentry>
          <term>Action:</term>
          <listitem>
-           <para>&TODO;</para>
+           <para>Opens a CIC browser window that shows <command>t</command>
+            together with its type. The command is immediately removed from
+            the script.</para>
          </listitem>
        </varlistentry>
      </variablelist>
  </sect1>
  <sect1 id="command_coercion">
    <title>coercion</title>
-   <para><userinput></userinput></para>
+   <para><userinput>coercion u</userinput></para>
    <para>
      <variablelist>
        <varlistentry role="tactic.synopsis">
          <term>Synopsis:</term>
          <listitem>
-           <para><emphasis role="bold">coercion</emphasis>
-           </para>
+           <para><emphasis role="bold">coercion</emphasis> &uri;</para>
          </listitem>
        </varlistentry>
        <varlistentry>
          <term>Action:</term>
          <listitem>
-           <para>&TODO;</para>
+           <para>Declares <command>u</command> as an implicit coercion
+            from the type of its last argument (source)
+            to its codomain (target). Every time a term <command>x</command>
+            of type source is used with expected type target, Matita
+            automatically replaces <command>x</command> with
+            <command>(u ? … ? x)</command> to avoid a typing error.</para>
+           <para>Implicit coercions are not displayed to the user:
+            <command>(u ? … ? x)</command> is rendered simply
+            as <command>x</command>.</para>
+           <para>When a coercion <command>u</command> is declared
+            from source <command>s</command> to target <command>t</command>
+            and there is already a coercion <command>u'</command> of
+            target <command>s</command> or source <command>t</command>,
+            a composite implicit coercion is automatically computed
+            by Matita.</para>
          </listitem>
        </varlistentry>
      </variablelist>
  </sect1>
  <sect1 id="command_hint">
    <title>hint</title>
-   <para><userinput></userinput></para>
+   <para><userinput>hint</userinput></para>
    <para>
      <variablelist>
        <varlistentry role="tactic.synopsis">
        <varlistentry>
          <term>Action:</term>
          <listitem>
-           <para>&TODO;</para>
+           <para>Displays a list of theorems that can be successfully
+            applied to the current selected sequent. The command is
+            removed from the script, but the window that displays the
+            theorems allow to add to the script the application of the
+            selected theorem.
+           </para>
          </listitem>
        </varlistentry>
      </variablelist>
  </sect1>
  <sect1 id="command_include">
    <title>include</title>
-   <para><userinput></userinput></para>
+   <para><userinput>include &quot;s&quot;</userinput></para>
    <para>
      <variablelist>
        <varlistentry role="tactic.synopsis">
          <term>Synopsis:</term>
          <listitem>
-           <para><emphasis role="bold">include</emphasis>
-           </para>
+           <para><emphasis role="bold">include</emphasis> &qstring;</para>
          </listitem>
        </varlistentry>
        <varlistentry>
          <term>Action:</term>
          <listitem>
-           <para>&TODO;</para>
+           <para>Every <link linkend="command_coercion">coercion</link>,
+            <link linkend="notation">notation</link> and
+            <link linkend="interpretation">interpretation</link> that was active
+            when the file <command>s</command> was compiled last time
+            is made active. The same happens for declarations of
+            <link linkend="command_default">default definitions and
+            theorems</link> and disambiguation
+            hints (<link linkend="command_alias">aliases</link>).
+            On the contrary, theorem and definitions declared in a file can be
+           immediately used without including it.</para>
+          <para>The file <command>s</command> is automatically compiled
+           if it is not compiled yet and if it is handled by a
+           <link linkend="developments">development</link>.
+          </para>
          </listitem>
        </varlistentry>
      </variablelist>
    </para>
  </sect1>
  <sect1 id="command_include_first">
-   <title>include'</title>
+   <title>include' &quot;s&quot;</title>
    <para><userinput></userinput></para>
    <para>
      <variablelist>
        <varlistentry role="tactic.synopsis">
          <term>Synopsis:</term>
          <listitem>
-           <para><emphasis role="bold">include'</emphasis>
-           </para>
+           <para><emphasis role="bold">include'</emphasis> &qstring;</para>
          </listitem>
        </varlistentry>
        <varlistentry>
          <term>Action:</term>
          <listitem>
-           <para>&TODO;</para>
+           <para>Not documented (&TODO;), do not use it.</para>
          </listitem>
        </varlistentry>
      </variablelist>
  </sect1>
  <sect1 id="command_set">
    <title>set</title>
-   <para><userinput></userinput></para>
+   <para><userinput>set &quot;baseuri&quot; &quot;s&quot;</userinput></para>
    <para>
      <variablelist>
        <varlistentry role="tactic.synopsis">
          <term>Synopsis:</term>
          <listitem>
-           <para><emphasis role="bold">set</emphasis>
-           </para>
+           <para><emphasis role="bold">set</emphasis> &qstring; &qstring;</para>
          </listitem>
        </varlistentry>
        <varlistentry>
          <term>Action:</term>
          <listitem>
-           <para>&TODO;</para>
+           <para>Sets to <command>s</command> the baseuri of all the
+            theorems and definitions stated in the current file.
+            The baseuri should be <command>a/b/c/foo</command>
+            if the file is named <command>foo</command> and it is in
+            the subtree <command>a/b/c</command> of the current
+            <link linkend="developments">development</link>.
+            This requirement is not enforced, but it could be in the future.
+           </para>
+           <para>Currently, <command>baseuri</command> is the only
+            property that can be set even if the parser accepts
+            arbitrary property names.</para>
          </listitem>
        </varlistentry>
      </variablelist>
        <varlistentry>
          <term>Action:</term>
          <listitem>
-           <para>&TODO;</para>
+           <para>Saves and indexes the current interactive theorem or
+            definition.
+            In order to do this, the set of sequents still to be proved
+            must be empty.</para>
          </listitem>
        </varlistentry>
      </variablelist>