<?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 on: A GMail Annoyance</title>
	<atom:link href="http://www.sebruiz.net/257/feed" rel="self" type="application/rss+xml" />
	<link>http://www.sebruiz.net/257</link>
	<description></description>
	<lastBuildDate>Sun, 14 Mar 2010 23:15:18 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Trever Fischer</title>
		<link>http://www.sebruiz.net/257/comment-page-1#comment-6421</link>
		<dc:creator>Trever Fischer</dc:creator>
		<pubDate>Thu, 28 Jun 2007 22:26:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.sebruiz.net/257#comment-6421</guid>
		<description>If you use google reader, the J/K keys move up and down just as in Vi. It only seems natural that they keep a consistent setup across all their applications.</description>
		<content:encoded><![CDATA[<p>If you use google reader, the J/K keys move up and down just as in Vi. It only seems natural that they keep a consistent setup across all their applications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas</title>
		<link>http://www.sebruiz.net/257/comment-page-1#comment-6406</link>
		<dc:creator>Andreas</dc:creator>
		<pubDate>Thu, 28 Jun 2007 11:07:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.sebruiz.net/257#comment-6406</guid>
		<description>Mmmm, Siemens keyboard. I like. Got my fingers on one by accident and kept it.</description>
		<content:encoded><![CDATA[<p>Mmmm, Siemens keyboard. I like. Got my fingers on one by accident and kept it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kapat</title>
		<link>http://www.sebruiz.net/257/comment-page-1#comment-6393</link>
		<dc:creator>Kapat</dc:creator>
		<pubDate>Thu, 28 Jun 2007 03:48:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.sebruiz.net/257#comment-6393</guid>
		<description>I use GMail daily, but there is one fundamental thing that GMail is doing wrong and this is my &quot;pet peeve&quot;:

When replying using gmail, if you edit the subject, they (gmail&#039;s MTA?) start a new conversation/thread and REMOVE the &quot;In Reply To&quot; reference from the header completely, which messes up the conversation even at the MUA end.

This to me is bothersome especially in mailing lists. I had ranted over this on the debian-user list a while back and even notified gmail&#039;s support team. No response though, as expected.</description>
		<content:encoded><![CDATA[<p>I use GMail daily, but there is one fundamental thing that GMail is doing wrong and this is my &#8220;pet peeve&#8221;:</p>
<p>When replying using gmail, if you edit the subject, they (gmail&#8217;s MTA?) start a new conversation/thread and REMOVE the &#8220;In Reply To&#8221; reference from the header completely, which messes up the conversation even at the MUA end.</p>
<p>This to me is bothersome especially in mailing lists. I had ranted over this on the debian-user list a while back and even notified gmail&#8217;s support team. No response though, as expected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Whelan</title>
		<link>http://www.sebruiz.net/257/comment-page-1#comment-6391</link>
		<dc:creator>Tony Whelan</dc:creator>
		<pubDate>Thu, 28 Jun 2007 02:52:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.sebruiz.net/257#comment-6391</guid>
		<description>Wow you have way to much time on your hands seb, really...</description>
		<content:encoded><![CDATA[<p>Wow you have way to much time on your hands seb, really&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benjamin Reed</title>
		<link>http://www.sebruiz.net/257/comment-page-1#comment-6390</link>
		<dc:creator>Benjamin Reed</dc:creator>
		<pubDate>Thu, 28 Jun 2007 02:20:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.sebruiz.net/257#comment-6390</guid>
		<description>Those bindings come from oldskool vi, where j was down and k was up.  It feels fine to me, but then, I learned to use an editor before there were any other choices (and none of those fancy &quot;vim&quot; editors with support for arrow keys).</description>
		<content:encoded><![CDATA[<p>Those bindings come from oldskool vi, where j was down and k was up.  It feels fine to me, but then, I learned to use an editor before there were any other choices (and none of those fancy &#8220;vim&#8221; editors with support for arrow keys).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stefan</title>
		<link>http://www.sebruiz.net/257/comment-page-1#comment-6389</link>
		<dc:creator>stefan</dc:creator>
		<pubDate>Thu, 28 Jun 2007 02:09:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.sebruiz.net/257#comment-6389</guid>
		<description>Your entry doesn&#039;t make it clear whether you already know this, but...

J and K are the keys that VI (and more importantly, VIM) uses for moving down and up, respectively. I believe that Google set up its keyboard shortcuts to be familiar to VIM users. I couldn&#039;t guess why, but... Yeah.

Oh my. I almost posted this having got my directions wrong.</description>
		<content:encoded><![CDATA[<p>Your entry doesn&#8217;t make it clear whether you already know this, but&#8230;</p>
<p>J and K are the keys that VI (and more importantly, VIM) uses for moving down and up, respectively. I believe that Google set up its keyboard shortcuts to be familiar to VIM users. I couldn&#8217;t guess why, but&#8230; Yeah.</p>
<p>Oh my. I almost posted this having got my directions wrong.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
