<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vim on Hillel Wayne</title>
    <link>https://www.hillelwayne.com/tags/vim/</link>
    <description>Recent content in Vim on Hillel Wayne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 13 Mar 2023 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.hillelwayne.com/tags/vim/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>A Neovim Task Runner in 30 lines of Lua</title>
      <link>https://www.hillelwayne.com/post/task-runner-neovim/</link>
      <pubDate>Mon, 13 Mar 2023 00:00:00 +0000</pubDate>
      
      <guid>https://www.hillelwayne.com/post/task-runner-neovim/</guid>
      <description>I like how easy it is to configure neovim. Last month I wanted a task runner for a very particular use-case that none of the available plugins handled. So I wrote my own.
Show CodeThis is not good code.
vim.g.global_task = {} function LoadTask(cmd, num, silent) local tmp = vim.g.global_task -- (a) if not num then num = vim.tbl_count(vim.g.global_task) + 1 end tmp[tonumber(num)] = cmd -- (a) vim.</description>
    </item>
    
    <item>
      <title>There&#39;s Always More History</title>
      <link>https://www.hillelwayne.com/post/always-more-history/</link>
      <pubDate>Tue, 08 Dec 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.hillelwayne.com/post/always-more-history/</guid>
      <description>Last month I researched two historical questions. I originally posted summaries on Twitter and am reproducing both here.1
Why Vim Uses hjkl Question: Why does Vim use hjkl and not the arrow keys for navigation?
Common Explanation: It keeps your fingers on the home row.
Historical Explanation: Bill Joy developed vi on the ADM-3A, which didn&amp;rsquo;t have dedicated arrow keys. If you look at the ADM keyboard, it put the arrow keys on the hjkl keys.</description>
    </item>
    
    <item>
      <title> At least one Vim trick you might not know </title>
      <link>https://www.hillelwayne.com/post/intermediate-vim/</link>
      <pubDate>Fri, 31 May 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.hillelwayne.com/post/intermediate-vim/</guid>
      <description>I&amp;rsquo;ve been using Vim for eight years and am still discovering new things. This is usually seen as a Good Thing About Vim. In my head, though, it&amp;rsquo;s a failing of discoverability: I keep discovering new things because Vim makes it so hard to know what&amp;rsquo;s available.
While people often talk about the beauty of modal editing or text objects, I don&amp;rsquo;t think that gets at the essence of Vim.</description>
    </item>
    
    <item>
      <title>Vim Macro Trickz</title>
      <link>https://www.hillelwayne.com/post/vim-macro-trickz/</link>
      <pubDate>Tue, 26 Dec 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.hillelwayne.com/post/vim-macro-trickz/</guid>
      <description>Vim has one of the best macro systems of any text editor out there.
Here&amp;rsquo;s why: Macros are just stored keystrokes. When you record a macro, it&amp;rsquo;s saved to the appropriate register, and it can be pasted and appended like any other saved string. When you run the macro, Vim simulates you typing every single character in the register. There are a couple of quirks to this (you can&amp;rsquo;t have a macro record another macro), but for the most part, macros have complete access to everything in vim.</description>
    </item>
    
    <item>
      <title>Hate Your Tools</title>
      <link>https://www.hillelwayne.com/hate-your-tools/</link>
      <pubDate>Tue, 27 Dec 2016 19:48:18 -0600</pubDate>
      
      <guid>https://www.hillelwayne.com/hate-your-tools/</guid>
      <description></description>
    </item>
    
  </channel>
</rss>