|
134 | 134 | </span></span></code></pre></div><p>Notice the subcommand can be nested:</p><div class=highlight><pre tabindex=0 class=chroma><code class=language-sh data-lang=sh><span class=line><span class=cl>eask clean workspace <span class=c1># Deletes your `.eask` folder</span> |
135 | 135 | </span></span></code></pre></div><p>Pass in option <code>--help</code> to look up more information regarding the command you |
136 | 136 | are using:</p><div class=highlight><pre tabindex=0 class=chroma><code class=language-sh data-lang=sh><span class=line><span class=cl>eask clean --help |
137 | | -</span></span></code></pre></div><p>The output, and it shows there are 7 subcommands supported:</p><pre tabindex=0><code>Delete various files produced during building |
138 | | - |
139 | | -Usage: eask clean <type> [options..] |
140 | | - |
141 | | -Commands: |
142 | | - clean all Do all cleaning tasks [aliases: everything] |
143 | | - clean autoloads Remove generated autoloads file |
144 | | - clean dist [destination] Delete dist subdirectory [aliases: distribution] |
145 | | - clean elc Remove byte compiled files generated by eask compile |
146 | | - clean log-file Remove all generated log files |
147 | | - clean pkg-file Remove generated pkg-file |
148 | | - clean workspace Clean up .eask directory [aliases: .eask] |
149 | | - |
150 | | -Positionals: |
151 | | - <type> type of the cleaning task |
152 | | - |
153 | | -... |
154 | | -</code></pre><p>Here is a list of known nested subcommands:</p><ul><li>eask create</li><li>eask clean</li><li>eask generate</li><li>eask generate workflow</li><li>eask link</li><li>eask lint</li><li>eask run</li><li>eask source</li><li>eask test</li></ul><div class="flex align-center gdoc-page__anchorwrap"><h2 id=-knowing-your-elpa-directory>📌 Knowing your <code>elpa</code> directory</h2><a data-clipboard-text=https://emacs-eask.github.io/Getting-Started/Basic-Usage/#-knowing-your-elpa-directory class="gdoc-page__anchor clip flex align-center" title="Anchor to: 📌 Knowing your elpa directory" aria-label="Anchor to: 📌 Knowing your elpa directory" href=#-knowing-your-elpa-directory><svg class="gdoc-icon gdoc_link"><use xlink:href="#gdoc_link"/></svg></a></div><p>Eask creates an isolated environment, so it won’t create any side effects after |
| 137 | +</span></span></code></pre></div><p>The output, and it shows there are 7 subcommands supported:</p><div class=highlight><pre tabindex=0 class=chroma><code class=language-text data-lang=text><span class=line><span class=cl>Delete various files produced during building |
| 138 | +</span></span><span class=line><span class=cl> |
| 139 | +</span></span><span class=line><span class=cl>Usage: eask clean <type> [options..] |
| 140 | +</span></span><span class=line><span class=cl> |
| 141 | +</span></span><span class=line><span class=cl>Commands: |
| 142 | +</span></span><span class=line><span class=cl> clean all Do all cleaning tasks [aliases: everything] |
| 143 | +</span></span><span class=line><span class=cl> clean autoloads Remove generated autoloads file |
| 144 | +</span></span><span class=line><span class=cl> clean dist [destination] Delete dist subdirectory [aliases: distribution] |
| 145 | +</span></span><span class=line><span class=cl> clean elc Remove byte compiled files generated by eask compile |
| 146 | +</span></span><span class=line><span class=cl> clean log-file Remove all generated log files |
| 147 | +</span></span><span class=line><span class=cl> clean pkg-file Remove generated pkg-file |
| 148 | +</span></span><span class=line><span class=cl> clean workspace Clean up .eask directory [aliases: .eask] |
| 149 | +</span></span><span class=line><span class=cl> |
| 150 | +</span></span><span class=line><span class=cl>Positionals: |
| 151 | +</span></span><span class=line><span class=cl> <type> type of the cleaning task |
| 152 | +</span></span><span class=line><span class=cl> |
| 153 | +</span></span><span class=line><span class=cl>... |
| 154 | +</span></span></code></pre></div><p>Here is a list of known nested subcommands:</p><ul><li>eask create</li><li>eask clean</li><li>eask generate</li><li>eask generate workflow</li><li>eask link</li><li>eask lint</li><li>eask run</li><li>eask source</li><li>eask test</li></ul><div class="flex align-center gdoc-page__anchorwrap"><h2 id=-knowing-your-elpa-directory>📌 Knowing your <code>elpa</code> directory</h2><a data-clipboard-text=https://emacs-eask.github.io/Getting-Started/Basic-Usage/#-knowing-your-elpa-directory class="gdoc-page__anchor clip flex align-center" title="Anchor to: 📌 Knowing your elpa directory" aria-label="Anchor to: 📌 Knowing your elpa directory" href=#-knowing-your-elpa-directory><svg class="gdoc-icon gdoc_link"><use xlink:href="#gdoc_link"/></svg></a></div><p>Eask creates an isolated environment, so it won’t create any side effects after |
155 | 155 | playing, testing, and running your elisp packages. But it’s important to know |
156 | 156 | what elpa directory (you can think of this as your <code>.emacs.d</code>) the current Eask |
157 | 157 | session is pointing to, so you can release the full potential of this tool!</p><p>Here is how Eask works behind the scene in different scenarios:</p><div class=table-wrap><table><thead><tr><th style=text-align:left>Name</th><th style=text-align:left>Description</th><th style=text-align:left>Options</th><th style=text-align:left>Path</th></tr></thead><tbody><tr><td style=text-align:left>local</td><td style=text-align:left>The default behavior, use Eask as package dev tool</td><td style=text-align:left>n/a</td><td style=text-align:left><code>./.eask</code></td></tr><tr><td style=text-align:left>config</td><td style=text-align:left>Use Eask as your package manager (It can be used as a test tool too)</td><td style=text-align:left><code>-c</code> or <code>--config</code></td><td style=text-align:left><code>~/.emacs.d</code></td></tr><tr><td style=text-align:left>global</td><td style=text-align:left>Use Eask as a general tool, it’s unrelated to other scopes</td><td style=text-align:left><code>-g</code> or <code>--global</code></td><td style=text-align:left><code>~/.eask</code></td></tr></tbody></table></div><p>You might think of why these rules are created.</p><p>It’s easy to understand <strong>config</strong> and <strong>local</strong> scopes since many other build |
|
0 commit comments