<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rpms :: Tag :: JP&#39;s Domain</title>
    <link>https://www.jpsdomain.org/tags/rpms/index.html</link>
    <description></description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://www.jpsdomain.org/tags/rpms/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux Resources</title>
      <link>https://www.jpsdomain.org/linux/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.jpsdomain.org/linux/index.html</guid>
      <description>Old Content This content is old! It’s still useful, but it’s old, and there may be bit rot, newer/better tools or ways to do things. Sanity check and do your research.&#xA;Bash (readline) Hints If you use bash, are as bad a typist as I am, and especially if you came up in the DOS/Windows world, there is one thing that probably drives you nuts—the way bash’s file/path completion works. I hate that bash either complains or just gives you a list of the possibilities on an ambiguous completion. I’d much rather have it cycle through the possibilities each time you hit TAB the way (shudder) cmd.exe/4NT.exe does. (See Windows Shell Scripting to enable this in cmd.exe.)</description>
    </item>
  </channel>
</rss>