<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Lf on Technical Notes</title><link>http://luispa.com/en/tags/lf/</link><description>Recent content in Lf on Technical Notes</description><generator>Hugo -- 0.148.0</generator><language>en-US</language><lastBuildDate>Sat, 28 Sep 2024 00:00:00 +0000</lastBuildDate><atom:link href="http://luispa.com/en/tags/lf/index.xml" rel="self" type="application/rss+xml"/><item><title>CRLF vs LF</title><link>http://luispa.com/en/posts/2024-09-28-crlf-vs-lf/</link><pubDate>Sat, 28 Sep 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-09-28-crlf-vs-lf/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-crlf.svg" alt="CRLF Logo" width="150px" style="float:left; padding-right:25px" />
&lt;p>When working in software development, one of the most subtle yet crucial aspects you need to be aware of is the difference between line endings in text files between Windows (CRLF &lt;code>\r\n&lt;/code>) and Linux/MacOS (LF &lt;code>\n&lt;/code>).&lt;/p>
&lt;p>This small detail can cause big problems if not handled correctly, especially when working in mixed environments &amp;ndash; &lt;strong>version control conflicts&lt;/strong>, &lt;strong>script incompatibilities&lt;/strong>, &lt;strong>compilation or execution issues&lt;/strong>. I wrote this post to have a handy reference for dealing with this topic, including a few tricks.&lt;/p>
&lt;br clear="left"/></description></item></channel></rss>