<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>TheOneTrueEditor on UberMongoose</title>
		<link>http://localhost:1313/tags/theonetrueeditor/</link>
		<description>Recent content in TheOneTrueEditor on UberMongoose</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sun, 04 Jan 2015 10:42:12 +0530</lastBuildDate>
		
			<atom:link href="http://localhost:1313/tags/theonetrueeditor/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Emacs - Debugging Code under Linux with GDB</title>
				<link>http://localhost:1313/post/emacs-debugging-code-under-linux-with-gdb/</link>
				<pubDate>Sun, 04 Jan 2015 10:42:12 +0530</pubDate>
				<guid>http://localhost:1313/post/emacs-debugging-code-under-linux-with-gdb/</guid>
				<description>&lt;p&gt;Visual Studio provides a very nice developer experience when debugging code. Emacs, on the other hand, doesn&amp;rsquo;t really shine in this area. It relies heavily the on strong debugging tools that ship with Linux, particularly GDB. While GDB is powerful and extensive, it&amp;rsquo;s command line interface is dated, and can come as a shock to a developer used to the Visual Studio way of doing things. Let&amp;rsquo;s take the play program below, which introduces an obvious bug involving an array overflow which causes stack corruption.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Emacs - Frames, Windows and Buffers</title>
				<link>http://localhost:1313/post/emacs-frames-windows-buffers/</link>
				<pubDate>Mon, 29 Jul 2013 16:10:20 +0530</pubDate>
				<guid>http://localhost:1313/post/emacs-frames-windows-buffers/</guid>
				<description>&lt;p&gt;First for some terminology. What Emacs called “frames” is what everyone else now calls windows. This is because Emacs started out as a full screen terminal tool and GUI’s came along later and because of that what Emacs calls windows is now what most visual studio programmers would know as split views. You can experiment with creating new frames, which are by default bound to &lt;code&gt;[C-x 5 2]&lt;/code&gt; and deleting the created frame by selecting it and pressing &lt;code&gt;[C-x 5 0]&lt;/code&gt;. It’s like opening a new instance of visual studio except that your on the same project as you were when you opened it.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The Configuration of Emacs</title>
				<link>http://localhost:1313/post/the-configuration-of-emacs/</link>
				<pubDate>Wed, 08 May 2013 16:14:33 +0530</pubDate>
				<guid>http://localhost:1313/post/the-configuration-of-emacs/</guid>
				<description>&lt;p&gt;Emacs can only be configured naked by moonlight.&lt;/p&gt;&#xA;&lt;p&gt;I kid, I kid – the moonlight is optional.&lt;/p&gt;&#xA;&lt;p&gt;Emacs has a number of “modes”. Much has been said about them on the interwebs so &lt;a href=&#34;http://jeremy.zawodny.com/emacs/emacs-3.html&#34;&gt;I’ll take the easy way out and link to a such an article&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;There are as you would have seen two kinds of modes, major modes and minor modes. Major modes change what Emacs believes is the content, for example there’s a major mode for C and a major mode for Python. Minor modes allow small changes in behavior in any content. CUA-Mode is a minor mode that does some trickery to allow C-c and C-v copy and paste like on the venerable Microsoft Word. It can be enabled by the command M-x followed by typing cua-mode in the mini buffer at the bottom of Emacs. However you don’t want to be manually typing that in every time you start emacs so you put some initialization settings in your &lt;a href=&#34;http://www.gnu.org/software/emacs/manual/html_node/emacs/Init-File.html&#34;&gt;Emacs init file&lt;/a&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Emacs Key Bindings</title>
				<link>http://localhost:1313/post/emacs-key-bindings/</link>
				<pubDate>Wed, 01 May 2013 16:14:33 +0530</pubDate>
				<guid>http://localhost:1313/post/emacs-key-bindings/</guid>
				<description>&lt;p&gt;Emacs is like your average dragon, very cranky before breakfast and set in its ways. Take for instance the key bindings. For you to do anything – and I mean anything at all you need to type in an arcane set of shortcut keys, like for instance the basic &lt;code&gt;Control Meta X, Control Sacrifice Goat, Enter Enter, Control F&lt;/code&gt; command which launches the built in dishwasher. You might be tempted to change the key bindings to better suite the feel of your windows environment but that is not a very good idea for the vast majority of cases.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The Bumpy Road to Emacs</title>
				<link>http://localhost:1313/post/the-bumpy-road-to-emacs/</link>
				<pubDate>Sat, 20 Apr 2013 16:14:33 +0530</pubDate>
				<guid>http://localhost:1313/post/the-bumpy-road-to-emacs/</guid>
				<description>&lt;p&gt;&lt;em&gt;The Road goes ever on and on&lt;/em&gt;&lt;br&gt;&#xA;&lt;em&gt;Down from the door where it began.&lt;/em&gt;&lt;br&gt;&#xA;&lt;em&gt;Now far ahead the Road has gone,&lt;/em&gt;&lt;br&gt;&#xA;&lt;em&gt;And I must follow, if I can,&lt;/em&gt;&lt;br&gt;&#xA;&lt;strong&gt;-Bilbo Baggins, The Fellowship of the Ring&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Sometimes the completely respectable Visual Studio programmer is called upon to follow the arduous road to places unknown where danger and dragons await him at every turn. One such dragon is called Emacs the Keybinder and subduing this beast requires a great deal of effort to those who have lived in the relative comfort of Visual Studio land.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
