<?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: Refactoring Configurations</title>
	<atom:link href="http://nflath.com/2009/07/refactoring-configurations/feed/" rel="self" type="application/rss+xml" />
	<link>http://nflath.com/2009/07/refactoring-configurations/</link>
	<description>Technology-related ideas, mainly involving Emacs</description>
	<pubDate>Wed, 22 May 2013 21:20:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The lone C++ coder's blog</title>
		<link>http://nflath.com/2009/07/refactoring-configurations/comment-page-1/#comment-218</link>
		<dc:creator>The lone C++ coder's blog</dc:creator>
		<pubDate>Tue, 18 Aug 2009 12:32:32 +0000</pubDate>
		<guid isPermaLink="false">http://nflath.com/?p=246#comment-218</guid>
		<description>&lt;strong&gt;My emacs configuration file refactor...&lt;/strong&gt;

In a previous post I described that a few months ago, I moved the third party elisp code under version control to make it easier to move it between machines and ensure a consistent configuration across them. The one remaining problem to solve was putti...</description>
		<content:encoded><![CDATA[<p><strong>My emacs configuration file refactor&#8230;</strong></p>
<p>In a previous post I described that a few months ago, I moved the third party elisp code under version control to make it easier to move it between machines and ensure a consistent configuration across them. The one remaining problem to solve was putti&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://nflath.com/2009/07/refactoring-configurations/comment-page-1/#comment-152</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Fri, 31 Jul 2009 11:26:45 +0000</pubDate>
		<guid isPermaLink="false">http://nflath.com/?p=246#comment-152</guid>
		<description>Ive just refactored my .emacs file using your two functions above (hoping you dont mind), the only problem ive hit so far is with downloaded .el files, such as browse-kill-ring.el. Im trying in my customizations folder to call things by the same name (as the source file) which leads to a recursive load, but its a non-issue for intergrated things like ido.el. my tempory solution has been to rename the files in custimizations to allow them to load, just wondering if you have a better solution.

Thanks Ive been quite likeing your emacs posts recently</description>
		<content:encoded><![CDATA[<p>Ive just refactored my .emacs file using your two functions above (hoping you dont mind), the only problem ive hit so far is with downloaded .el files, such as browse-kill-ring.el. Im trying in my customizations folder to call things by the same name (as the source file) which leads to a recursive load, but its a non-issue for intergrated things like ido.el. my tempory solution has been to rename the files in custimizations to allow them to load, just wondering if you have a better solution.</p>
<p>Thanks Ive been quite likeing your emacs posts recently</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Hudson</title>
		<link>http://nflath.com/2009/07/refactoring-configurations/comment-page-1/#comment-151</link>
		<dc:creator>Phil Hudson</dc:creator>
		<pubDate>Fri, 31 Jul 2009 11:23:15 +0000</pubDate>
		<guid isPermaLink="false">http://nflath.com/?p=246#comment-151</guid>
		<description>How about:

&lt;code&gt;
(defun load-directory (dir)
  (mapc 'load-file (directory-files dir t "\\.el\\'")))
&lt;/code&gt;

* mapc: for side effects only, doesn't accumulate results (unlike mapcar).
* No lambda wrapper required for load-file, since it takes exactly one argument anyway.
* Better to terminate file extension patterns with backslash-quote rather than dollar. It means you don't accidentally match files that (perversely) include the newline character in their names.

Useful function though, thanks for sharing it.</description>
		<content:encoded><![CDATA[<p>How about:</p>
<p><code><br />
(defun load-directory (dir)<br />
  (mapc 'load-file (directory-files dir t "\\.el\\'")))<br />
</code></p>
<p>* mapc: for side effects only, doesn&#8217;t accumulate results (unlike mapcar).<br />
* No lambda wrapper required for load-file, since it takes exactly one argument anyway.<br />
* Better to terminate file extension patterns with backslash-quote rather than dollar. It means you don&#8217;t accidentally match files that (perversely) include the newline character in their names.</p>
<p>Useful function though, thanks for sharing it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Hudson</title>
		<link>http://nflath.com/2009/07/refactoring-configurations/comment-page-1/#comment-150</link>
		<dc:creator>Phil Hudson</dc:creator>
		<pubDate>Fri, 31 Jul 2009 10:59:44 +0000</pubDate>
		<guid isPermaLink="false">http://nflath.com/?p=246#comment-150</guid>
		<description>I have this, with some macros for facilitating host- and OS-specific customizations:
&lt;code&gt;
- .emacs.d
 -- lisp
  --- mode1setup.el
  --- mode2setup.el
  --- os1
   ---- mode1setup.os1.el
   ---- mode2setup.os1.el
  --- os2
   ---- mode1setup.os2.el
   ---- mode2setup.os2.el
  --- host1
   ---- mode1setup.host1.el
   ---- mode2setup.host1.el
  --- host2
   ---- mode1setup.host2.el
   ---- mode2setup.host2.el
 -- site-lisp
  --- nxml
  --- org
  --- dvc
  --- traverse
  --- etc
&lt;/code&gt;

Easily extensible to other kinds of per-something customizations: DNS domain, window system, processor architecture... haven't needed any of those myself yet.</description>
		<content:encoded><![CDATA[<p>I have this, with some macros for facilitating host- and OS-specific customizations:<br />
<code><br />
- .emacs.d<br />
 -- lisp<br />
  --- mode1setup.el<br />
  --- mode2setup.el<br />
  --- os1<br />
   ---- mode1setup.os1.el<br />
   ---- mode2setup.os1.el<br />
  --- os2<br />
   ---- mode1setup.os2.el<br />
   ---- mode2setup.os2.el<br />
  --- host1<br />
   ---- mode1setup.host1.el<br />
   ---- mode2setup.host1.el<br />
  --- host2<br />
   ---- mode1setup.host2.el<br />
   ---- mode2setup.host2.el<br />
 -- site-lisp<br />
  --- nxml<br />
  --- org<br />
  --- dvc<br />
  --- traverse<br />
  --- etc<br />
</code></p>
<p>Easily extensible to other kinds of per-something customizations: DNS domain, window system, processor architecture&#8230; haven&#8217;t needed any of those myself yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rafal</title>
		<link>http://nflath.com/2009/07/refactoring-configurations/comment-page-1/#comment-147</link>
		<dc:creator>Rafal</dc:creator>
		<pubDate>Thu, 30 Jul 2009 09:01:29 +0000</pubDate>
		<guid isPermaLink="false">http://nflath.com/?p=246#comment-147</guid>
		<description>It's a matter of taste. 2 years ago I did a splitting of my .emacs file but after some days I come back to a single file because many times I had problems finding customizations for specific libraries. I made nice comments in my .emacs file and I can easily jump to places I need with C-s. My emacs file has over 7000 lines and I had no problems to manage it so far.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a matter of taste. 2 years ago I did a splitting of my .emacs file but after some days I come back to a single file because many times I had problems finding customizations for specific libraries. I made nice comments in my .emacs file and I can easily jump to places I need with C-s. My emacs file has over 7000 lines and I had no problems to manage it so far.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
