<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nvim on Federico Ramacciotti</title><link>https://federama.dev/tags/nvim/</link><description>Recent content in nvim on Federico Ramacciotti</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 11 Nov 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://federama.dev/tags/nvim/index.xml" rel="self" type="application/rss+xml"/><item><title>My dev setup using VSCode and nvim</title><link>https://federama.dev/posts/2023-11-11-new-dev-setup/</link><pubDate>Sat, 11 Nov 2023 00:00:00 +0000</pubDate><guid>https://federama.dev/posts/2023-11-11-new-dev-setup/</guid><description>Back in January I made a post on how I was learning and configuring vim and neovim. After 10 months, during which I focused on University and didn&amp;rsquo;t write code 24/7, I found myself more and more going back to VSCode. So I decided to fine-tune VSCode to my likings, and simplify nvim to use it when I need to modify some files from the terminal.
In the last few months, I realized that in my 4 years of using VSCode I never customized it (aside changing theme) and I filled it with a lot of bloat.</description></item><item><title>Learning and configuring nvim</title><link>https://federama.dev/posts/2023-01-18-nvim-setup/</link><pubDate>Wed, 18 Jan 2023 00:00:00 +0000</pubDate><guid>https://federama.dev/posts/2023-01-18-nvim-setup/</guid><description>In my first blog post I want to document my journey learning vim and nvim.
Because of its steep learning curve, I have never really considered it. But after watching The Primeagen flying through the terminal with nvim, I decided to give it a try. I followed some of his videos to learn about vim motions and this video to learn how to configure nvim.
First attempt This journey started on my 23rd birthday, seeing a vim motions video explaining how vim works.</description></item></channel></rss>