<?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: Top 10 Emacs Commands</title>
	<atom:link href="http://nflath.com/2009/08/top-10-emacs-commands/feed/" rel="self" type="application/rss+xml" />
	<link>http://nflath.com/2009/08/top-10-emacs-commands/</link>
	<description>Technology-related ideas, mainly involving Emacs</description>
	<pubDate>Sat, 19 May 2012 07:11:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Trey Jackson</title>
		<link>http://nflath.com/2009/08/top-10-emacs-commands/comment-page-1/#comment-221</link>
		<dc:creator>Trey Jackson</dc:creator>
		<pubDate>Tue, 18 Aug 2009 18:20:38 +0000</pubDate>
		<guid isPermaLink="false">http://nflath.com/?p=310#comment-221</guid>
		<description>Nice analysis, I've got the command frequency running myself and look forward to seeing what I can learn (and compare to your usage as well).

Regarding 'redo', I think the problem boils down to Emacs's undo mechanism - namely that it stores everything (the whole undo an undo).  If the undo mechanism were changed to actually remove events from the history (and save them off to a redo list somewhere), then I think 'redo' could fit.

But, I imagine you'd then suffer the same limitation all the other undo/redo mechanisms seem to suffer, namely, when you do something other than 'redo' after an 'undo' you have to clear out the redo list.  And then you've lost the ability to get back to all the configurations the buffer had...

That's my thought at least.  Emacs' undo is confusing at first, but I like the power it holds.</description>
		<content:encoded><![CDATA[<p>Nice analysis, I&#8217;ve got the command frequency running myself and look forward to seeing what I can learn (and compare to your usage as well).</p>
<p>Regarding &#8216;redo&#8217;, I think the problem boils down to Emacs&#8217;s undo mechanism - namely that it stores everything (the whole undo an undo).  If the undo mechanism were changed to actually remove events from the history (and save them off to a redo list somewhere), then I think &#8216;redo&#8217; could fit.</p>
<p>But, I imagine you&#8217;d then suffer the same limitation all the other undo/redo mechanisms seem to suffer, namely, when you do something other than &#8216;redo&#8217; after an &#8216;undo&#8217; you have to clear out the redo list.  And then you&#8217;ve lost the ability to get back to all the configurations the buffer had&#8230;</p>
<p>That&#8217;s my thought at least.  Emacs&#8217; undo is confusing at first, but I like the power it holds.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Top 10 Emacs Commands &#124; time saving in business</title>
		<link>http://nflath.com/2009/08/top-10-emacs-commands/comment-page-1/#comment-214</link>
		<dc:creator>Top 10 Emacs Commands &#124; time saving in business</dc:creator>
		<pubDate>Mon, 17 Aug 2009 14:42:36 +0000</pubDate>
		<guid isPermaLink="false">http://nflath.com/?p=310#comment-214</guid>
		<description>[...] more here: Top 10 Emacs Commands  Tags: academics, autoindentation, buffer-control, completion, conclusions, deletion, editing, [...]</description>
		<content:encoded><![CDATA[<p>[...] more here: Top 10 Emacs Commands  Tags: academics, autoindentation, buffer-control, completion, conclusions, deletion, editing, [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

