<?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 Rietta Cybersecurity</title>
    <link>https://rietta.com/tags/vim/</link>
    <description>Recent content in vim on Rietta Cybersecurity</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>1999-2026 Rietta Inc. All Rights Reserved.</copyright>
    <atom:link href="https://rietta.com/tags/vim/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Acknowledge Open-Source Contributors with Git Authorship</title>
      <link>https://rietta.com/blog/acknowledge-open-source-contributors-with-git-authorship/</link>
      <pubDate>Mon, 07 Oct 2019 10:00:00 -0600</pubDate>
      <guid>https://rietta.com/blog/acknowledge-open-source-contributors-with-git-authorship/</guid>
      <description>Even though Git has been around since 2005 and has definitely taken over as the primary VCS, some developers do not utilize git to the fullest of its ability. Some developers even intentionally execute commands to remove functionality, such as replacing commit authors with their own. Additionally, it&amp;rsquo;s shocking that some of these mishaps occur in popular repositories, such as vim, but often maintainers express no intention of changing. In modern times, Github has fortunately made the process of keeping git authors intact trivial.</description>
    </item>
    <item>
      <title>How to hide .gitignored Files from fzf.vim</title>
      <link>https://rietta.com/blog/hide-gitignored-files-fzf-vim/</link>
      <pubDate>Tue, 21 May 2019 10:30:00 -0400</pubDate>
      <guid>https://rietta.com/blog/hide-gitignored-files-fzf-vim/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://rietta.com/assets/blog/hide-gitignored-files-fzf-vim/phoenix_hello_world_fzf_deps.png&#34; alt=&#34;Messy Phoenix Fuzzy Finder&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Fuzzy finders find files that almost no developer would intentionally find via a fuzzy finder from paths&#xA;such as &lt;code&gt;node_modules/&lt;/code&gt;, &lt;code&gt;deps/&lt;/code&gt;, and &lt;code&gt;dist/&lt;/code&gt;. These tend to get in the way of the true power of fuzzy file&#xA;searching and ignoring these individually can be a pain. There are also files like &lt;code&gt;.circleci/config.yml&lt;/code&gt;,&#xA;&lt;code&gt;.gitignore&lt;/code&gt;, and &lt;code&gt;.rubocop.yml&lt;/code&gt; that are opened often enough to be included in the result set.&lt;/p&gt;&#xA;&lt;p&gt;Luckily when working in a git repository, developers typically only care about the files they commit.&#xA;When using &lt;a href=&#34;https://github.com/junegunn/fzf.vim&#34;&gt;fzf.vim&lt;/a&gt;, this technique returns&#xA;files based on the git tree leaving out irrelevant files, including the hidden files that were&#xA;shown before.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
