<?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 Pradeepa Senanayake</title><link>https://www.pradeepas.com/tags/vim/</link><description>Recent content in vim on Pradeepa Senanayake</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Sat, 10 Oct 2020 12:26:13 +1100</lastBuildDate><atom:link href="https://www.pradeepas.com/tags/vim/index.xml" rel="self" type="application/rss+xml"/><item><title>Let's link vi and chrome using vimscript</title><link>https://www.pradeepas.com/posts/vimscript_to_link_browser_and_editor/</link><pubDate>Sat, 10 Oct 2020 12:26:13 +1100</pubDate><guid>https://www.pradeepas.com/posts/vimscript_to_link_browser_and_editor/</guid><description>It has been almost an year since I started using vi (or vim). It is one of those decisions that really changed the way I perceived development environments. I feel that, in terms of possibilities vi dwarfs every other editor in the market and the vi community is really helpful and cool!
In my current work, I spend a lot of time looking at tests to understand the intent. Most of the time, I need to navigate from the test to the specification in order to understand the context.</description></item></channel></rss>