<?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: Cleanly adding sysctl entries on DragonFly	</title>
	<atom:link href="https://www.dragonflydigest.com/2019/01/16/cleanly-adding-sysctl-entries-on-dragonfly/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2019/01/16/cleanly-adding-sysctl-entries-on-dragonfly/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Thu, 17 Jan 2019 14:24:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Justin Sherrill		</title>
		<link>https://www.dragonflydigest.com/2019/01/16/cleanly-adding-sysctl-entries-on-dragonfly/comment-page-1/#comment-487886</link>

		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Thu, 17 Jan 2019 14:24:00 +0000</pubDate>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=22415#comment-487886</guid>

					<description><![CDATA[The new editor in Wordpress apparently does HTML entity translation on links, so it will see an ampersand linking together query string elements and attempt to treat it as an HTML entity code.

That&#039;s a surprisingly bad mistake; the 5.0 upgrade for Wordpress has been a step backward from an interface point of view for me, as there&#039;s been a bunch of other issues with input I&#039;ve had to manually fix over and over, since upgrading.  Hopefully this will be updated soon; I don&#039;t think I can complain it into working.]]></description>
			<content:encoded><![CDATA[<p>The new editor in WordPress apparently does HTML entity translation on links, so it will see an ampersand linking together query string elements and attempt to treat it as an HTML entity code.</p>
<p>That&#8217;s a surprisingly bad mistake; the 5.0 upgrade for WordPress has been a step backward from an interface point of view for me, as there&#8217;s been a bunch of other issues with input I&#8217;ve had to manually fix over and over, since upgrading.  Hopefully this will be updated soon; I don&#8217;t think I can complain it into working.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: wordpressing		</title>
		<link>https://www.dragonflydigest.com/2019/01/16/cleanly-adding-sysctl-entries-on-dragonfly/comment-page-1/#comment-487885</link>

		<dc:creator><![CDATA[wordpressing]]></dc:creator>
		<pubDate>Thu, 17 Jan 2019 08:35:44 +0000</pubDate>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=22415#comment-487885</guid>

					<description><![CDATA[why do you keep linking the manpages in that manner? It adds a section sigh[0] just after the manentry/command [0]=[section sign (U+00A7)] right into the url. I believe it is automated, you just write it and wordpress forms the hyperlink, but even then, at least go poorly for &#039;sysctl&#039;-link and &#039;(8)&#039;-unlinked and a manpage with section=any will be resolved. I&#039;d use mdoc.su/d/ if I&#039;d be you though, and I&#039;d just write sysctl(8) as sysctl.8]]></description>
			<content:encoded><![CDATA[<p>why do you keep linking the manpages in that manner? It adds a section sigh[0] just after the manentry/command [0]=[section sign (U+00A7)] right into the url. I believe it is automated, you just write it and wordpress forms the hyperlink, but even then, at least go poorly for &#8216;sysctl&#8217;-link and &#8216;(8)&#8217;-unlinked and a manpage with section=any will be resolved. I&#8217;d use mdoc.su/d/ if I&#8217;d be you though, and I&#8217;d just write sysctl(8) as sysctl.8</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
