summaryrefslogtreecommitdiffstats
path: root/2022/talks/eshell.md
blob: 99150d577e55d7581fa16515df5ddfd6da265fda (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
[[!sidebar content=""]]
[[!meta title="Top 10 reasons why you should be using Eshell"]]
[[!meta copyright="Copyright © 2022 Howard Abrams"]]
[[!inline pages="internal(2022/info/eshell-nav)" raw="yes"]]

<!-- Initially generated with emacsconf-generate-talk-page and then left alone for manual editing -->
<!-- You can manually edit this file to update the abstract, add links, etc. --->


# Top 10 reasons why you should be using Eshell
Howard Abrams (he/him)

[[!inline pages="internal(2022/info/eshell-before)" raw="yes"]]

While Eshell is this quick and dirty way to run external commands, its
*dirtiness* plays into the Lisp’s *malleable* big ball of mud metaphor,
and I have a number of quick hacks that will make you want to play in
this puddle.

This will be a lightning talk that I will pre-record to show off some
features in eshell I found while diving into the source code &#x2026; stuff
you can’t do in another terminals. Did you know that \`$$\` is a special
variable that contains the output from the last command?



[[!inline pages="internal(2022/info/eshell-after)" raw="yes"]]

[[!inline pages="internal(2022/info/eshell-nav)" raw="yes"]]