<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Package on Amit Agarwal Linux Blog</title>
    <link>/tags/package/</link>
    <description>Recent content in Package on Amit Agarwal Linux Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 23 Mar 2010 03:29:09 +0000</lastBuildDate>
    
	<atom:link href="/tags/package/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>unbound variable – bash completion not working and having issues with other stuff like command not found.</title>
      <link>/2010/03/23/unbound-variable-bash-completion-not-working-and-having-issues-with-other-stuff-like-command-not-found/</link>
      <pubDate>Tue, 23 Mar 2010 03:29:09 +0000</pubDate>
      
      <guid>/2010/03/23/unbound-variable-bash-completion-not-working-and-having-issues-with-other-stuff-like-command-not-found/</guid>
      <description>&lt;!--[ad#ad-2]--&gt;
&lt;p&gt;I generally use vi/vim for all my practical purposes of working with text files. And I have all the vi/vim plugins required to work with the files. This causes the following to be in the skeleton for all the bash scripts that I create:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;set -o nounset                              # Treat unset variables as an error&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;With this all the unbound variables as errors and was problem with all the shell scripts that was being sourced in the startup of bash. So all I had to do was remove this from all the startup scripts and then from the skeleton of the bash script in vim :).&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
