<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on GCGC website</title><link>https://gcanat.github.io/posts/</link><description>Recent content in Posts on GCGC website</description><generator>Hugo</generator><language>en-us</language><copyright>© [Guillaume Canat](https://github.com/gcanat)</copyright><lastBuildDate>Mon, 11 May 2026 23:00:45 +0200</lastBuildDate><atom:link href="https://gcanat.github.io/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Easy navigation in native Vim</title><link>https://gcanat.github.io/posts/vim-easy-nav/</link><pubDate>Mon, 11 May 2026 23:00:45 +0200</pubDate><guid>https://gcanat.github.io/posts/vim-easy-nav/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In the days of fancy plugins super charging vim to make it look like a fully
fledged IDE, I sometimes like to go back to the basics and (re)discover how
vim often already has something builtin to do things, albeit maybe in a
slightly different way.&lt;/p&gt;
&lt;p&gt;Before LSP was a thing, &lt;a href="https://vimhelp.org/tagsrch.txt.html#tags"&gt;tags&lt;/a&gt; were
already there to help us navigate a codebase and we also have the &lt;code&gt;:compiler&lt;/code&gt;
command to run linters and populate the quickfix list with errors.
Before fuzzy finders were all the rage, we already had &lt;code&gt;:edit&lt;/code&gt;, &lt;code&gt;:find&lt;/code&gt; and the
&lt;a href="https://vimhelp.org/editing.txt.html#arglist"&gt;argument list&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>