<?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/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	
	>
<channel>
	<title>
	Comments on: Gedit With It.	</title>
	<atom:link href="https://gregladen.com/blog/2008/06/29/gedit-with-it/feed/" rel="self" type="application/rss+xml" />
	<link>https://gregladen.com/blog/2008/06/29/gedit-with-it/</link>
	<description></description>
	<lastBuildDate>Mon, 30 Jun 2008 09:02:43 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.4.8</generator>
	<item>
		<title>
		By: Virgil Samms		</title>
		<link>https://gregladen.com/blog/2008/06/29/gedit-with-it/#comment-10544</link>

		<dc:creator><![CDATA[Virgil Samms]]></dc:creator>
		<pubDate>Mon, 30 Jun 2008 09:02:43 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/06/29/gedit-with-it/#comment-10544</guid>

					<description><![CDATA[Nedit is one of my favorites. If you edit large files, say a few thousand lines, the speed advantage of Nedit over Gedit is appreciable.]]></description>
			<content:encoded><![CDATA[<p>Nedit is one of my favorites. If you edit large files, say a few thousand lines, the speed advantage of Nedit over Gedit is appreciable.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Tristram Brelstaff		</title>
		<link>https://gregladen.com/blog/2008/06/29/gedit-with-it/#comment-10543</link>

		<dc:creator><![CDATA[Tristram Brelstaff]]></dc:creator>
		<pubDate>Mon, 30 Jun 2008 08:22:59 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/06/29/gedit-with-it/#comment-10543</guid>

					<description><![CDATA[I recently changed over to SciTE for all my editing.  I particularly like to use it in a &#039;no distractions&#039; full-screen minimalist configuration.  It also has the advantage that it can be installed on Windows.]]></description>
			<content:encoded><![CDATA[<p>I recently changed over to SciTE for all my editing.  I particularly like to use it in a &#8216;no distractions&#8217; full-screen minimalist configuration.  It also has the advantage that it can be installed on Windows.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jeff Darcy		</title>
		<link>https://gregladen.com/blog/2008/06/29/gedit-with-it/#comment-10542</link>

		<dc:creator><![CDATA[Jeff Darcy]]></dc:creator>
		<pubDate>Sun, 29 Jun 2008 20:06:06 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/06/29/gedit-with-it/#comment-10542</guid>

					<description><![CDATA[I like the &quot;crapbook&quot; play on words too.  So apropos, so much of the time.For a long time, I could reasonably claim to be the only person who wrote kernel code for AIX, Solaris, UnixWare, and Linux using a Windows text editor (EditPlus).  Then for a long time I was one of the few who&#039;d use emacs and vi &quot;ambidextrously&quot; without becoming a hyper-zealot for either one.  I&#039;d use emacs for writing big chunks of new code at my desk, and vi for short hacks on test systems or in the field.  The nice thing about vi is that it&#039;s likely to be available sooner when you&#039;re bringing up *N*X on a new kind of system, and it&#039;s more likely to be available at a customer site.Nowadays I mainly use Kate, which I consider to have three advantages over gedit.  First, it seems to be in the smaller class of editors that I consider reasonably well-behaved when it comes to indentation and tabs; gedit is in the larger class of editors that I feel I have to fight with to get correct results.  Second, it&#039;s KDE instead of GNOME, and I generally find KDE&#039;s kioslave interface (which I use e.g. to edit files directly on my website via FTP) to be of better quality than GNOME&#039;s copy of it.  Third, Kate integrates seamlessly with cscope to produce &lt;a href=&quot;http://kscope.sourceforge.net/&quot; rel=&quot;nofollow&quot;&gt;kscope&lt;/a&gt;, which I find absolutely invaluable in my line of work and for which no GNOME equivalent seems to exist.I still use vi for quick edits, but for code navigation or writing that I expect to take more than few minutes I fire up kscope.]]></description>
			<content:encoded><![CDATA[<p>I like the &#8220;crapbook&#8221; play on words too.  So apropos, so much of the time.For a long time, I could reasonably claim to be the only person who wrote kernel code for AIX, Solaris, UnixWare, and Linux using a Windows text editor (EditPlus).  Then for a long time I was one of the few who&#8217;d use emacs and vi &#8220;ambidextrously&#8221; without becoming a hyper-zealot for either one.  I&#8217;d use emacs for writing big chunks of new code at my desk, and vi for short hacks on test systems or in the field.  The nice thing about vi is that it&#8217;s likely to be available sooner when you&#8217;re bringing up *N*X on a new kind of system, and it&#8217;s more likely to be available at a customer site.Nowadays I mainly use Kate, which I consider to have three advantages over gedit.  First, it seems to be in the smaller class of editors that I consider reasonably well-behaved when it comes to indentation and tabs; gedit is in the larger class of editors that I feel I have to fight with to get correct results.  Second, it&#8217;s KDE instead of GNOME, and I generally find KDE&#8217;s kioslave interface (which I use e.g. to edit files directly on my website via FTP) to be of better quality than GNOME&#8217;s copy of it.  Third, Kate integrates seamlessly with cscope to produce <a href="http://kscope.sourceforge.net/" rel="nofollow">kscope</a>, which I find absolutely invaluable in my line of work and for which no GNOME equivalent seems to exist.I still use vi for quick edits, but for code navigation or writing that I expect to take more than few minutes I fire up kscope.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: llewelly		</title>
		<link>https://gregladen.com/blog/2008/06/29/gedit-with-it/#comment-10541</link>

		<dc:creator><![CDATA[llewelly]]></dc:creator>
		<pubDate>Sun, 29 Jun 2008 19:22:47 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/06/29/gedit-with-it/#comment-10541</guid>

					<description><![CDATA[Face it. If you don&#039;t use emacs, you&#039;re headed for the big blue screen at the bottom of the pit.]]></description>
			<content:encoded><![CDATA[<p>Face it. If you don&#8217;t use emacs, you&#8217;re headed for the big blue screen at the bottom of the pit.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Andrew		</title>
		<link>https://gregladen.com/blog/2008/06/29/gedit-with-it/#comment-10540</link>

		<dc:creator><![CDATA[Andrew]]></dc:creator>
		<pubDate>Sun, 29 Jun 2008 17:21:55 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/06/29/gedit-with-it/#comment-10540</guid>

					<description><![CDATA[No, just little things like &quot;format page&quot; being under &quot;file&quot; while &quot;format anything else&quot; is under &quot;format&quot;]]></description>
			<content:encoded><![CDATA[<p>No, just little things like &#8220;format page&#8221; being under &#8220;file&#8221; while &#8220;format anything else&#8221; is under &#8220;format&#8221;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: rpenner		</title>
		<link>https://gregladen.com/blog/2008/06/29/gedit-with-it/#comment-10539</link>

		<dc:creator><![CDATA[rpenner]]></dc:creator>
		<pubDate>Sun, 29 Jun 2008 16:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/06/29/gedit-with-it/#comment-10539</guid>

					<description><![CDATA[Lucifer is but one of the many contractors who contributed to the Office application suite. He is not solely to blame for the mess that is Word.]]></description>
			<content:encoded><![CDATA[<p>Lucifer is but one of the many contractors who contributed to the Office application suite. He is not solely to blame for the mess that is Word.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
