<?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: Lazy Reading for 2012/01/15	</title>
	<atom:link href="https://www.dragonflydigest.com/2012/01/15/lazy-reading-for-20120115/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2012/01/15/lazy-reading-for-20120115/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Wed, 18 Jan 2012 20:55:10 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.3</generator>
	<item>
		<title>
		By: dreamlarva		</title>
		<link>https://www.dragonflydigest.com/2012/01/15/lazy-reading-for-20120115/comment-page-1/#comment-44424</link>

		<dc:creator><![CDATA[dreamlarva]]></dc:creator>
		<pubDate>Wed, 18 Jan 2012 20:55:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=8976#comment-44424</guid>

					<description><![CDATA[A _lot_ of distributions leave info pages uninstalled so that &quot;info foo&quot; gives the exact same page as &quot;man foo&quot;. But I was very pleasantly surprised when I hit the info page for bash (short pages! navigable links!), as I had searched through the overlong man page (I think comes close to a hundred pages if printed out) for a bit of syntax dozens of times before, and that was hell.]]></description>
			<content:encoded><![CDATA[<p>A _lot_ of distributions leave info pages uninstalled so that &#8220;info foo&#8221; gives the exact same page as &#8220;man foo&#8221;. But I was very pleasantly surprised when I hit the info page for bash (short pages! navigable links!), as I had searched through the overlong man page (I think comes close to a hundred pages if printed out) for a bit of syntax dozens of times before, and that was hell.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Rahul		</title>
		<link>https://www.dragonflydigest.com/2012/01/15/lazy-reading-for-20120115/comment-page-1/#comment-44414</link>

		<dc:creator><![CDATA[Rahul]]></dc:creator>
		<pubDate>Tue, 17 Jan 2012 07:30:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=8976#comment-44414</guid>

					<description><![CDATA[Indeed, info pages never caught on outside the GNU project.  The main problems with info pages, it seems to me, are (1) they&#039;re too long and (2) they&#039;re too non-intuitive to navigate: most people don&#039;t want to learn an entire set of new keyboard commands just to get help.  And, recognising this, most unix systems / linux distros include manpages anyway, which are &quot;good enough&quot;.  Most people consult manpages just for a quick reminder, scroll down and eyeball (or search with /) until you find what you want.  Info actually slows that process down.]]></description>
			<content:encoded><![CDATA[<p>Indeed, info pages never caught on outside the GNU project.  The main problems with info pages, it seems to me, are (1) they&#8217;re too long and (2) they&#8217;re too non-intuitive to navigate: most people don&#8217;t want to learn an entire set of new keyboard commands just to get help.  And, recognising this, most unix systems / linux distros include manpages anyway, which are &#8220;good enough&#8221;.  Most people consult manpages just for a quick reminder, scroll down and eyeball (or search with /) until you find what you want.  Info actually slows that process down.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Justin Sherrill		</title>
		<link>https://www.dragonflydigest.com/2012/01/15/lazy-reading-for-20120115/comment-page-1/#comment-44413</link>

		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Tue, 17 Jan 2012 04:39:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=8976#comment-44413</guid>

					<description><![CDATA[Have info pages been useful for anyone, ever?  I&#039;ve never seen them referenced or quoted or used, other than included in packages.]]></description>
			<content:encoded><![CDATA[<p>Have info pages been useful for anyone, ever?  I&#8217;ve never seen them referenced or quoted or used, other than included in packages.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Rahul		</title>
		<link>https://www.dragonflydigest.com/2012/01/15/lazy-reading-for-20120115/comment-page-1/#comment-44412</link>

		<dc:creator><![CDATA[Rahul]]></dc:creator>
		<pubDate>Tue, 17 Jan 2012 04:19:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=8976#comment-44412</guid>

					<description><![CDATA[From the tar(1) manpage on my Ubuntu computer (which, I imagine, takes it from Debian):


BUGS
     The GNU folks, in general, abhor man pages, and create info documents
     instead.  Unfortunately, the info document describing tar is licensed
     under the GFDL with invariant cover texts, which makes it impossible to
     include any text from that document in this man page.  Most of the text
     in this document was automatically extracted from the usage text in the
     source.  It may not completely describe all features of the program.
]]></description>
			<content:encoded><![CDATA[<p>From the tar(1) manpage on my Ubuntu computer (which, I imagine, takes it from Debian):</p>
<p>BUGS<br />
     The GNU folks, in general, abhor man pages, and create info documents<br />
     instead.  Unfortunately, the info document describing tar is licensed<br />
     under the GFDL with invariant cover texts, which makes it impossible to<br />
     include any text from that document in this man page.  Most of the text<br />
     in this document was automatically extracted from the usage text in the<br />
     source.  It may not completely describe all features of the program.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
