<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bash on Thaddeus Koenig</title><link>https://www.thaddeuskoenig.com/tags/bash/</link><description>Recent content in Bash on Thaddeus Koenig</description><generator>Hugo</generator><language>en-US</language><copyright>© 2026 Thaddeus Koenig</copyright><lastBuildDate>Thu, 16 Jan 2025 06:06:24 -0500</lastBuildDate><atom:link href="https://www.thaddeuskoenig.com/tags/bash/index.xml" rel="self" type="application/rss+xml"/><item><title>/bin/bash^M: bad interpreter</title><link>https://www.thaddeuskoenig.com/blog/00_legacy_bash_bad_interpreter/</link><pubDate>Thu, 23 Nov 2023 00:00:00 -0500</pubDate><guid>https://www.thaddeuskoenig.com/blog/00_legacy_bash_bad_interpreter/</guid><description>&lt;p&gt;Bash scripts are very sensitive to line endings which can cause some portability issues between windows and unix-like systems (depending on how the text editor encodes line breaks). If you would like to see the invisible characters that are making your life confusing simply type:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;cat -v &amp;lt;FILE&amp;gt;
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The easiest solution to this issue is a simple sed replace line:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;sed -i -e &amp;#39;s/\r$//&amp;#39; &amp;lt;FILE&amp;gt;
&lt;/code&gt;&lt;/pre&gt;</description></item></channel></rss>