<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Command Line on Holyarmy.org</title>
		<link>https://holyarmy.org/tags/command-line/</link>
		<description>Recent content in Command Line on Holyarmy.org</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Mon, 09 Nov 2009 05:46:53 +0000</lastBuildDate>
		
			<atom:link href="https://holyarmy.org/tags/command-line/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Killing “find” Errors</title>
				<link>https://holyarmy.org/2009/11/killing-find-errors/</link>
				<pubDate>Mon, 09 Nov 2009 05:46:53 +0000</pubDate>
				<guid>https://holyarmy.org/2009/11/killing-find-errors/</guid>
				<description>&lt;p&gt;I’ve used the unix filesystem search utility &lt;strong&gt;find&lt;/strong&gt; for many years. Though, like most things, until forced to learn its deeper secrets, I generally get by with only the most basic knowledge.&lt;/p&gt;&#xA;&lt;p&gt;One of the cool things about &lt;strong&gt;find&lt;/strong&gt; is that you can specify a search and then execute an action on the results, all in one command.&lt;/p&gt;&#xA;&lt;p&gt;This example is probably my most common use of &lt;strong&gt;find&lt;/strong&gt;:&lt;/p&gt;&#xA;&lt;pre&gt;find . -type d -name .svn -exec rm -fr {} \;&#xA;&lt;/pre&gt;&#xA;&lt;p&gt;This means: find, in the current directory (.), a directory (-type d), named .svn (-name .svn), and for every result (-exec) remove that directory (rm -fr {}) .  The “{}” represents the matched path string, and the “;” is required to end the “-exec” command.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Use vi key bindings in bash</title>
				<link>https://holyarmy.org/2008/12/use-vi-key-bindings-in-bash/</link>
				<pubDate>Thu, 04 Dec 2008 06:29:38 +0000</pubDate>
				<guid>https://holyarmy.org/2008/12/use-vi-key-bindings-in-bash/</guid>
				<description>&lt;p&gt;A long time ago I used ksh with vi key bindings, and life was good.&lt;/p&gt;&#xA;&lt;p&gt;Then I moved on to bash, but for some reason, I never investigated using vi key bindings. I simply lived with the defaults (which, for the record, are emacs-like key bindings).&lt;/p&gt;&#xA;&lt;p&gt;So, just the other day I said to myself, “Self, I want to use vi key bindings in bash. I want to again experience the joy of traversing and editing my command line in COMMAND MODE. I want the speed and the power of my precious vi (well, I use vim) at my finger tips. And I NO LONGER want to waste time holding arrow keys or to think about using emacs-like commands.”&lt;/p&gt;</description>
			</item>
			<item>
				<title>Fight Back! (When VPN Clients Mis-Behave)</title>
				<link>https://holyarmy.org/2008/07/fight-back-when-vpn-clients-mis-behave/</link>
				<pubDate>Wed, 23 Jul 2008 18:20:19 +0000</pubDate>
				<guid>https://holyarmy.org/2008/07/fight-back-when-vpn-clients-mis-behave/</guid>
				<description>&lt;p&gt;I have to use VPNs at work. Specifically, to access my production webservers (etc), I have to use a Cisco VPN client. Sadly, the VPN concentrator overrides my choice of allowing local LAN access. So, when I am on the VPN, I have my DNS options changed so I can’t use any local servers. This is a serious, serious pain. So painful in fact, that many times instead of fight with it, I simply would run a Windows session in VMware (on my Mac) and connect the VPN there. This has drawbacks too, but it’s better than not having local network access.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
