commit c71aa37095f797531c6483b844b6cee97c657e25
parent f82512090d20990c254baae5f59a5625379ebc7d
Author: Jake Bauer <jbauer@paritybit.ca>
Date: Wed, 5 Aug 2020 17:30:18 -0400
Draft new blog post
Diffstat:
1 file changed, 45 insertions(+), 0 deletions(-)
diff --git a/pages/blog/use-st-term-variable.md b/pages/blog/use-st-term-variable.md
@@ -0,0 +1,45 @@
+## Use TERM=st-256color For Better ls Output
+
+[//]: # "META_TEXT"
+
+[//]: # "main.min.css"
+
+[//]: #
+
+<div class="byline">
+<b>Written By:</b> Jake Bauer |
+ <b>Posted:</b> [DATE] |
+ <b>Last Updated:</b> [DATE]
+</div>
+
+In [switching to alacritty](/blog/switching-to-alacritty.md), I noticed
+something off about my `ls` output. Previously, when I was using st, ls would
+highlight different files in different colours. For example, image files would
+be bold and purple and other files like `.deb.` or `.zip` files would be bold
+and red. Here is an example:
+
+<figure>
+ <a href="/img/ls-highlights.png"><img src="/img/ls-highlights.png" alt="A
+ screenshot of a terminal where ls shows pictures highlighted in purple and
+ .zip files in red."/></a>
+</figure>
+
+As opposed to the default:
+
+<figure>
+ <a href="/img/ls-highlights.png"><img src="/img/ls-highlights.png" alt="A
+ screenshot of a terminal where ls shows pictures highlighted in purple and
+ .zip files in red."/></a>
+</figure>
+
+Which is what you get if you use a `TERM` variable set to `alacritty` or
+`xterm-256color` in your `alacritty.yml`. Since changing that variable in my
+`alacritty.yml` file to `st-256color`, the highlights have returned.
+
+Also, [Alacritty 5.0 is out](https://github.com/alacritty/alacritty/releases)
+which includes a new Vi mode!
+
+_This is my eighty-fifth post for the
+[#100DaysToOffload](https://social.paritybit.ca/tags/100DaysToOffload)
+challenge. You can learn more about this challenge over at
+[https://100daystooffload.com](https://100daystooffload.com)._
