<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for I Hope Solution</title>
	<atom:link href="http://ihopesolution.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://ihopesolution.com</link>
	<description>IT tips, tricks and rants from the trenches</description>
	<lastBuildDate>Wed, 30 Dec 2009 22:08:14 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Book Review: Time Management for Systems Administrators by Tudor</title>
		<link>http://ihopesolution.com/2009/11/book-review-time-management-for-systems-administrators/comment-page-1/#comment-166</link>
		<dc:creator>Tudor</dc:creator>
		<pubDate>Wed, 30 Dec 2009 22:08:14 +0000</pubDate>
		<guid isPermaLink="false">http://ihopesolution.com/?p=79#comment-166</guid>
		<description>Thanks for the recomm. !
I&#039;d give you a latte for it.</description>
		<content:encoded><![CDATA[<p>Thanks for the recomm. !<br />
I&#8217;d give you a latte for it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Distributed Python Development and Deployment with Git and Virtualenv by Jim</title>
		<link>http://ihopesolution.com/2009/07/distributed-python-development-git-virtualenv/comment-page-1/#comment-165</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Fri, 04 Dec 2009 21:57:31 +0000</pubDate>
		<guid isPermaLink="false">http://ihopesolution.com/?p=4#comment-165</guid>
		<description>shouldn&#039;t 

$ pip -E projectname -r requirements.txt

be

$ pip install -E projectname -r requirements.txt</description>
		<content:encoded><![CDATA[<p>shouldn&#8217;t </p>
<p>$ pip -E projectname -r requirements.txt</p>
<p>be</p>
<p>$ pip install -E projectname -r requirements.txt</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Book Review: Time Management for Systems Administrators by anon</title>
		<link>http://ihopesolution.com/2009/11/book-review-time-management-for-systems-administrators/comment-page-1/#comment-38</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Fri, 06 Nov 2009 19:36:19 +0000</pubDate>
		<guid isPermaLink="false">http://ihopesolution.com/?p=79#comment-38</guid>
		<description>I&#039;m sure it beats the One Minute Manager.</description>
		<content:encoded><![CDATA[<p>I&#8217;m sure it beats the One Minute Manager.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Disabling Update Notifier Pop-up in Ubuntu 9.04 by ronelM</title>
		<link>http://ihopesolution.com/2009/07/disabling-update-notifier-pop-up-in-ubuntu-9-04/comment-page-1/#comment-37</link>
		<dc:creator>ronelM</dc:creator>
		<pubDate>Thu, 15 Oct 2009 13:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://ihopesolution.com/?p=50#comment-37</guid>
		<description>great one!</description>
		<content:encoded><![CDATA[<p>great one!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Paid per email and why it won&#8217;t work by Erin</title>
		<link>http://ihopesolution.com/2009/08/paid-per-email-and-why-it-wont-work/comment-page-1/#comment-36</link>
		<dc:creator>Erin</dc:creator>
		<pubDate>Fri, 02 Oct 2009 21:02:36 +0000</pubDate>
		<guid isPermaLink="false">http://ihopesolution.com/?p=65#comment-36</guid>
		<description>Nice article. I agree with you, it won&#039;t work. Email as a protocol is a very broken system. It should be overhauled or completely done away with.</description>
		<content:encoded><![CDATA[<p>Nice article. I agree with you, it won&#8217;t work. Email as a protocol is a very broken system. It should be overhauled or completely done away with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Emacs vs. VI Keybindings by Christopher Humphries</title>
		<link>http://ihopesolution.com/2009/08/emacs-vs-vi-keybindings/comment-page-1/#comment-35</link>
		<dc:creator>Christopher Humphries</dc:creator>
		<pubDate>Thu, 24 Sep 2009 14:43:14 +0000</pubDate>
		<guid isPermaLink="false">http://ihopesolution.com/?p=74#comment-35</guid>
		<description>This is definitely true. 

Only a fool would be blind to only use one or the other. While I prefer Emacs for editing code (it is much more than an editor, it&#039;s a LISP machine that has file editing functionality by default), vi is suitable for small edits and will always be on any UNIX system.

Also, how can one say they prefer one or the other without learning both to come to a sound conclusion? I tend to ignore people that make seemingly biased judgements on one side but are ignorant of the other.

In my opinion, the arguments most have with &quot;emacs vs vi&quot; have nothing to do with technical matters but is a &quot;my team vs your team&quot; mentality issue. Some seem to want to have this desire to belong to a &quot;team&quot;. 

But as for vi keybindings, I&#039;ve never had to use them outside of vi. Emacs keybindings I use everywhere all the time.

I agree vi is worth learning, yet I disagree with the misleading title of learning due to keybindings. Emacs keybindings are in everything by default, vi keybindings are not. Since I started UNIX in 1996, I don&#039;t think I&#039;ve used vi keybindings in anything other than vi or vim.</description>
		<content:encoded><![CDATA[<p>This is definitely true. </p>
<p>Only a fool would be blind to only use one or the other. While I prefer Emacs for editing code (it is much more than an editor, it&#8217;s a LISP machine that has file editing functionality by default), vi is suitable for small edits and will always be on any UNIX system.</p>
<p>Also, how can one say they prefer one or the other without learning both to come to a sound conclusion? I tend to ignore people that make seemingly biased judgements on one side but are ignorant of the other.</p>
<p>In my opinion, the arguments most have with &#8220;emacs vs vi&#8221; have nothing to do with technical matters but is a &#8220;my team vs your team&#8221; mentality issue. Some seem to want to have this desire to belong to a &#8220;team&#8221;. </p>
<p>But as for vi keybindings, I&#8217;ve never had to use them outside of vi. Emacs keybindings I use everywhere all the time.</p>
<p>I agree vi is worth learning, yet I disagree with the misleading title of learning due to keybindings. Emacs keybindings are in everything by default, vi keybindings are not. Since I started UNIX in 1996, I don&#8217;t think I&#8217;ve used vi keybindings in anything other than vi or vim.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Emacs vs. VI Keybindings by David Schroeder</title>
		<link>http://ihopesolution.com/2009/08/emacs-vs-vi-keybindings/comment-page-1/#comment-32</link>
		<dc:creator>David Schroeder</dc:creator>
		<pubDate>Sun, 13 Sep 2009 02:08:20 +0000</pubDate>
		<guid isPermaLink="false">http://ihopesolution.com/?p=74#comment-32</guid>
		<description>As an in-progress vim-to-emacs convert, there&#039;s another reason to know both sets of bindings (or more accurately, to know vi bindings even if you always use emacs): There are systems out there where the most advanced editor is vi. Not vim, but vi. I&#039;ve needed to do some work on systems like that, and it was difficult enough as a vim user. I can&#039;t imagine how difficult it would be not knowing any bindings at all.</description>
		<content:encoded><![CDATA[<p>As an in-progress vim-to-emacs convert, there&#8217;s another reason to know both sets of bindings (or more accurately, to know vi bindings even if you always use emacs): There are systems out there where the most advanced editor is vi. Not vim, but vi. I&#8217;ve needed to do some work on systems like that, and it was difficult enough as a vim user. I can&#8217;t imagine how difficult it would be not knowing any bindings at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Emacs vs. VI Keybindings by Alex Schröder</title>
		<link>http://ihopesolution.com/2009/08/emacs-vs-vi-keybindings/comment-page-1/#comment-31</link>
		<dc:creator>Alex Schröder</dc:creator>
		<pubDate>Fri, 11 Sep 2009 08:26:46 +0000</pubDate>
		<guid isPermaLink="false">http://ihopesolution.com/?p=74#comment-31</guid>
		<description>Just &lt;a href=&quot;http://www.emacswiki.org/emacs/EmacsChannelTabu&quot; rel=&quot;nofollow&quot;&gt;don&#039;t use them in the wrong IRC channel&lt;/a&gt;!</description>
		<content:encoded><![CDATA[<p>Just <a href="http://www.emacswiki.org/emacs/EmacsChannelTabu" rel="nofollow">don&#8217;t use them in the wrong IRC channel</a>!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Emacs vs. VI Keybindings by Travis B. Hartwell</title>
		<link>http://ihopesolution.com/2009/08/emacs-vs-vi-keybindings/comment-page-1/#comment-30</link>
		<dc:creator>Travis B. Hartwell</dc:creator>
		<pubDate>Wed, 02 Sep 2009 14:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://ihopesolution.com/?p=74#comment-30</guid>
		<description>I definitely agree, and I regularly use both vi and Emacs.  I also think the opposite is true -- you should know basic Emacs keybindings.  If you are on any Linux system or any system that uses bash or a program that uses GNU Readline, you will have basic Emacs keystrokes at your disposal.

Just the other day, I overheard someone on my ops team tell another, &quot;I figured out how to go back one word in bash, it&#039;s control-b.&quot;  It didn&#039;t occur to me that people didn&#039;t know that, it was natural to me because I use Emacs.</description>
		<content:encoded><![CDATA[<p>I definitely agree, and I regularly use both vi and Emacs.  I also think the opposite is true &#8212; you should know basic Emacs keybindings.  If you are on any Linux system or any system that uses bash or a program that uses GNU Readline, you will have basic Emacs keystrokes at your disposal.</p>
<p>Just the other day, I overheard someone on my ops team tell another, &#8220;I figured out how to go back one word in bash, it&#8217;s control-b.&#8221;  It didn&#8217;t occur to me that people didn&#8217;t know that, it was natural to me because I use Emacs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Paid per email and why it won&#8217;t work by aglenn</title>
		<link>http://ihopesolution.com/2009/08/paid-per-email-and-why-it-wont-work/comment-page-1/#comment-29</link>
		<dc:creator>aglenn</dc:creator>
		<pubDate>Wed, 02 Sep 2009 14:21:17 +0000</pubDate>
		<guid isPermaLink="false">http://ihopesolution.com/?p=65#comment-29</guid>
		<description>Let&#039;s not forget the ever so huge mail queue&#039;s we run into in Support. The Hall of Fame comes to mind, where the &#039;usual suspects&#039; have been witnessed to have 6 million or more messages in the server queue at one given time. While we can go on for hours about if these emails are or are not actually SPAM, that&#039;s not the point I&#039;m making here...

At some point or another an account is going to be compromised with DarkMailer and an unsuspecting person (probably our customer) is going to get an enormous bill. This assumes this happens on a Virtual Private or a Dedicated Server. How will web hosting companies deal with this clutch when they&#039;re faced with this situation on their shared servers?</description>
		<content:encoded><![CDATA[<p>Let&#8217;s not forget the ever so huge mail queue&#8217;s we run into in Support. The Hall of Fame comes to mind, where the &#8216;usual suspects&#8217; have been witnessed to have 6 million or more messages in the server queue at one given time. While we can go on for hours about if these emails are or are not actually SPAM, that&#8217;s not the point I&#8217;m making here&#8230;</p>
<p>At some point or another an account is going to be compromised with DarkMailer and an unsuspecting person (probably our customer) is going to get an enormous bill. This assumes this happens on a Virtual Private or a Dedicated Server. How will web hosting companies deal with this clutch when they&#8217;re faced with this situation on their shared servers?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
