commit 05d191a4ad09cfc8c7876afa2088718b9a7532f0
parent 41696c10e61505f63913fb7f90c1d6a302bba314
Author: pyratebeard <root@pyratebeard.net>
Date: Sat, 1 Apr 2023 22:51:05 +0100
vim_-_buffer_me_up
Diffstat:
1 file changed, 9 insertions(+), 0 deletions(-)
diff --git a/entry/vim_-_buffer_me_up.md b/entry/vim_-_buffer_me_up.md
@@ -0,0 +1,9 @@
+This is the first entry in a three part series on [Vim](TK){target="_blank" rel="noreferrer"}. There are plenty of Vim guides and tutorials on the internet already, everything from first steps to hardcore power user tips. My entries are somewhat of a middle ground.
+
+I have been using Vim as my main (read _only_) text editor for many years, over which I have continuously learnt new ways of working, or really focused on using Vim's functions properly.
+
+The latter is what I am going to cover in three parts. In the past couple of years I have been working of enhancing my Vim workflow and the first step was to master [buffers](TK){target="_blank" rel="noreferrer"}.
+
+When I switched to Vim from [Sublime](https://www.sublimetext.com/){target="_blank" rel="noreferrer"} I had trouble getting over the use of tabs for open files. Sublime, like a lot of GUI text editors, would open files in tabs at the top of the window. Vim does have tabs but they are not used in the same way (more on this later TK).
+
+Opening a file in Vim creates a buffer.
