commit: c5569346191b6427d7e5099896104b4d8b54d6e4
parent 2134ab846f1fd75bb6d2870bc6affc19ffa8f1d1
Author: Drew DeVault <sir@cmpwn.com>
Date: Sat, 12 Dec 2020 13:03:25 -0500
Correct typos
Diffstat:
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/blog/Shell-literacy.gmi b/content/blog/Shell-literacy.gmi
@@ -1,4 +1,4 @@
-Shell literacy is one of the most important skills you ought to possess as a programmer. The Unix shell is one of the most powerful ideas ever put to code, and should be second nature to you as a programmer. No other tool is nearly as effective at commanding your computer to complex tasks quickly — or at storing them as scripts you can use later.
+Shell literacy is one of the most important skills you ought to possess as a programmer. The Unix shell is one of the most powerful ideas ever put to code, and should be second nature to you as a programmer. No other tool is nearly as effective at commanding your computer to perform complex tasks quickly — or at storing them as scripts you can use later.
In my workflow, I use Vim as my editor, and Unix as my “IDE”. I don’t trick out my vimrc to add a bunch of IDE-like features — the most substantial plugin I use on a daily basis is Ctrl+P, and that just makes it easier to open files. Being Vim literate is a valuable skill, but an important detail is knowing when to drop it. My daily workflow involves several open terminals, generally one with Vim, another to run builds or daemons, and a third which just keeps a shell handy for anything I might ask of it.
diff --git a/content/blog/Shell-literacy.md b/content/blog/Shell-literacy.md
@@ -7,8 +7,8 @@ outputs: [html, gemtext]
Shell literacy is one of the most important skills you ought to possess as a
programmer. The Unix shell is one of the most powerful ideas ever put to code,
and should be second nature to you as a programmer. No other tool is nearly as
-effective at commanding your computer to complex tasks quickly — or at
-storing them as scripts you can use later.
+effective at commanding your computer to perform complex tasks quickly —
+or at storing them as scripts you can use later.
In my workflow, I use Vim as my editor, and Unix as my "IDE". I don't trick out
[my vimrc](https://git.sr.ht/~sircmpwn/dotfiles/tree/master/.vimrc) to add a
