From bc8aa9a1ed5911eb2c963dae2a6d349e402850c9 Mon Sep 17 00:00:00 2001
From: Dante Catalfamo
Date: Mon, 26 Feb 2024 14:42:18 -0500
Subject: openbsd-weechat-fix: Clarify wording on TERM env

---
 content/posts/openbsd-weechat-separator-fix/index.org | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/content/posts/openbsd-weechat-separator-fix/index.org b/content/posts/openbsd-weechat-separator-fix/index.org
index ef11fd1..35446e8 100644
--- a/content/posts/openbsd-weechat-separator-fix/index.org
+++ b/content/posts/openbsd-weechat-separator-fix/index.org
@@ -37,14 +37,14 @@ It looks like the reason was that =weechat= had saved
 doesn't support the character it wanted to use. The fix was to run
 =/unset weechat.look.prefix_suffix= after setting the correct locale.
 
-I also plan on keeping =weechat= open in a =tmux= buffer, so I need to
-set the =$TERM= environment variable to allow 256 colours.
-
-To do that, I need to set the =$TERM= environment variable to
-=tmux-256color= instead of the default =screen= so that =weechat= can
-use a richer selection of colors when displaying information.
-
-To do that, edited =~/.tmux.conf= and added the following line.
+I also plan on keeping =weechat= open in a =tmux= buffer. By default,
+=tmux= on OpenBSD uses =TERM=screen=, which only supports a very
+limited set of colors. To let =weechat= use a richer color pallet, I
+have to let it know the terminal support 256 colors. I can do this by
+using the =tmux-256color= =TERM= environment variable when inside of a
+session.
+
+To do that, I add the following line to my =~/.tmux.conf= file.
 
 #+begin_src conf
 set -g default-terminal "tmux-256color"
-- 
cgit v1.2.3