==============================================================
	The Joy of Vim Splits - Oct. 14, 2019
==============================================================

I've been living in the terminal as much as I can for many
months now. I feel this affinity for the minimalist/suckless
cyber-lifestyle. I can be very Puritan in the way that I see
features.

If they're bloat, then cut them out, and if I need them, find
a stripped down workaround. If one doesn't exist, then I can
do without it.

I try to abide by this philosophy as much as possible, and I
feel it not only helps me with my productivity, but it also
keeps my knowledge and application of Unix commands and other
low-level fixtures fresh in my mind.

Having said that, I still don't find much use for terminal
multiplexers like tmux.

I'm perfectly comfortable using my various keybindings for i3
to open a separate terminal window, especially if the files
and apps I need to access are in completely different
directories. However, one case where I constantly find myself
needing to quickly peek at files in the same directory, or at
least in a close neighbor directory, is when programming in
vim.

I don't want to constantly open new windows for a single file,
and sometimes I just want to compare files side by side. But
why install a terminal mux when I can just use the built in
multiplexing in vim?

Yes, for those who aren't aware, vim has built in split
functions!

--------------
:split [FILE]
--------------
      or
--------------
:vsplit [FILE]
--------------

An example image of what I used vsplit for recently is linked
below this tech post.

Not only do I get the wonderous feature of file mux-ing, I
don't even have to install a separate application for it! I
don't have to close vim to look at different files, and my
single case of multiplexer need is satisfied.

vim users rejoice, go forth with another tool in your belt
that helps you reduce bloat, and suck less!