<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>The lone C++ coder's blog - Emacs</title>
    <link>http://codeblog.bsdninjas.co.uk/</link>
    <description>Diary of a supposedly experienced C++ developer</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.4.1 - http://www.s9y.org/</generator>
    <pubDate>Wed, 27 Jan 2010 12:49:06 GMT</pubDate>

    <image>
        <url>http://codeblog.bsdninjas.co.uk/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: The lone C++ coder's blog - Emacs - Diary of a supposedly experienced C++ developer</title>
        <link>http://codeblog.bsdninjas.co.uk/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>Building cedet on Windows</title>
    <link>http://codeblog.bsdninjas.co.uk/index.php?/archives/141-Building-cedet-on-Windows.html</link>
            <category>Emacs</category>
    
    <comments>http://codeblog.bsdninjas.co.uk/index.php?/archives/141-Building-cedet-on-Windows.html#comments</comments>
    <wfw:comment>http://codeblog.bsdninjas.co.uk/wfwcomment.php?cid=141</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://codeblog.bsdninjas.co.uk/rss.php?version=2.0&amp;type=comments&amp;cid=141</wfw:commentRss>
    

    <author>nospam@example.com (Timo Geusch)</author>
    <content:encoded>
    &lt;p&gt;When building both cedet-1.0pre4 and -pre6 on Windows with cygwin and a fairly recent emacs 23.1-based Emacs-W32, a whole boatload of errors suddenly disappear when you make the following changes:&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;in Makefile, change &quot;EMACS=emacs&quot; to &quot;EMACS=runemacs&quot;&lt;/li&gt;&lt;li&gt;For good measure, also set &quot;SHELL=bash&quot;, which is usually commented out&lt;/li&gt;&lt;/ul&gt;

&lt;p&gt;It goes without saying that it&#039;s a really good idea to disable any Cygwin version of emacs if you want to use Emacs-W32, too.&lt;/p&gt; 
    </content:encoded>

    <pubDate>Wed, 27 Jan 2010 12:49:06 +0000</pubDate>
    <guid isPermaLink="false">http://codeblog.bsdninjas.co.uk/index.php?/archives/141-guid.html</guid>
    
</item>
<item>
    <title>A couple of useful Emacs modes</title>
    <link>http://codeblog.bsdninjas.co.uk/index.php?/archives/136-A-couple-of-useful-Emacs-modes.html</link>
            <category>Emacs</category>
    
    <comments>http://codeblog.bsdninjas.co.uk/index.php?/archives/136-A-couple-of-useful-Emacs-modes.html#comments</comments>
    <wfw:comment>http://codeblog.bsdninjas.co.uk/wfwcomment.php?cid=136</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://codeblog.bsdninjas.co.uk/rss.php?version=2.0&amp;type=comments&amp;cid=136</wfw:commentRss>
    

    <author>nospam@example.com (Timo Geusch)</author>
    <content:encoded>
    &lt;p&gt;highlight-changes-mode – as the name implies, it highlights changes that you make to a file. I do find it useful for the typical scenario of checking out a file, making a couple of smaller changes to it and then having to diff it to work out what you actually changed. As mentioned over at Emacswiki it doesn’t play too nicely with font-locking but I’ll try out some of the suggestions in the “Taming Highlight-Changes-Mode” section on &lt;a href=&quot;http://www.emacswiki.org/emacs/TrackChanges&quot;&gt;this page&lt;/a&gt;.&lt;/p&gt;  &lt;p&gt;&lt;a href=&quot;http://www.emacswiki.org/emacs/NxmlMode&quot;&gt;nxml-mode&lt;/a&gt; – my preferred mode for editing XML. Of course it would be better if I could be bothered to create schemas for some of the files I’m editing but even without them, it does a pretty good job. As it’s trying to parse the XML that you write, it’s very helpful when it comes to highlighting mismatched tags or auto complete tags.&lt;/p&gt;  &lt;p&gt;&lt;a href=&quot;http://www.emacswiki.org/emacs/InteractivelyDoThings&quot;&gt;ido-mode&lt;/a&gt; – I’ve only recently started to use it and I’m still trying to work out if it is useful enough for me or if the improved file finding capability does bother me more than it helps. Yes, I know it can do a lot more but so far I’m only using the improved file finding and buffer switching. I really rate the buffer switching which is the main reason I leave it turned on.&lt;/p&gt;  &lt;p&gt;Not really a mode, but I like using &lt;a href=&quot;http://www.nongnu.org/bm/&quot;&gt;bm.el&lt;/a&gt; for visible bookmarks. I don’t use bookmarks that often but the package is extremely useful when I do need them.&lt;/p&gt; 
    </content:encoded>

    <pubDate>Tue, 06 Oct 2009 18:40:29 +0100</pubDate>
    <guid isPermaLink="false">http://codeblog.bsdninjas.co.uk/index.php?/archives/136-guid.html</guid>
    
</item>
<item>
    <title>My emacs configuration file refactor</title>
    <link>http://codeblog.bsdninjas.co.uk/index.php?/archives/131-My-emacs-configuration-file-refactor.html</link>
            <category>Emacs</category>
    
    <comments>http://codeblog.bsdninjas.co.uk/index.php?/archives/131-My-emacs-configuration-file-refactor.html#comments</comments>
    <wfw:comment>http://codeblog.bsdninjas.co.uk/wfwcomment.php?cid=131</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://codeblog.bsdninjas.co.uk/rss.php?version=2.0&amp;type=comments&amp;cid=131</wfw:commentRss>
    

    <author>nospam@example.com (Timo Geusch)</author>
    <content:encoded>
    &lt;p&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 putting the configuration files (.emacs and .gnus.el) under version control. One of the approaches I really liked was described by &lt;a href=&quot;http://nflath.com/2009/07/refactoring-configurations/&quot;&gt;Nathaniel Flath&lt;/a&gt; but I figured that it was too heavyweight for my needs.&lt;/p&gt;&lt;br /&gt;&lt;br /&gt;&lt;p&gt;What I ended up doing was to move the configuration files into version control and then simply change the basic dot-files to load the file from the subdirectory that is under version control. My .emacs now reads like this:&lt;/p&gt;&lt;br /&gt;&lt;br /&gt;&lt;pre&gt;
&lt;code&gt;
(load-file &quot;~/emacs-lisp/dot-emacs.el&quot;)
&lt;/code&gt;
&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;&lt;p&gt;Not the most elegant and automated version but it works for me.&lt;/p&gt;&lt;br /&gt;&lt;br /&gt;&lt;div class=&quot;zemanta-pixie&quot;&gt;&lt;img class=&quot;zemanta-pixie-img&quot; alt=&quot;&quot; src=&quot;http://img.zemanta.com/pixy.gif?x-id=2ccb2a52-5b3e-8e72-962e-6ab7f8cb290c&quot; /&gt;&lt;/div&gt; 
    </content:encoded>

    <pubDate>Tue, 18 Aug 2009 13:27:35 +0100</pubDate>
    <guid isPermaLink="false">http://codeblog.bsdninjas.co.uk/index.php?/archives/131-guid.html</guid>
    
</item>
<item>
    <title>How to use emacs to get rid of those pesky ^M characters</title>
    <link>http://codeblog.bsdninjas.co.uk/index.php?/archives/124-How-to-use-emacs-to-get-rid-of-those-pesky-M-characters.html</link>
            <category>Emacs</category>
    
    <comments>http://codeblog.bsdninjas.co.uk/index.php?/archives/124-How-to-use-emacs-to-get-rid-of-those-pesky-M-characters.html#comments</comments>
    <wfw:comment>http://codeblog.bsdninjas.co.uk/wfwcomment.php?cid=124</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://codeblog.bsdninjas.co.uk/rss.php?version=2.0&amp;type=comments&amp;cid=124</wfw:commentRss>
    

    <author>nospam@example.com (Timo Geusch)</author>
    <content:encoded>
    &lt;p&gt;I had another of these annoying mixed-mode DOS/Unix text files that suffered from being edited in text editors that didn&#039;t agree which line ending mode they should use. Unfortunately Emacs defaults to Unix text mode in this case so I had an already ugly file that wasn&#039;t exactly prettified by random ^M characters all over the place.&lt;/p&gt;
&lt;p&gt;I also don&#039;t have the cygwin tools on the machine that I was seeing this problem on, I couldn&#039;t just run unix2dos or dos2unix over the file and be done with it, but at least I had emacs on that machine. So, emacs to the rescue again...&lt;/p&gt;
&lt;p&gt;First, I used &lt;em&gt;query-replace&lt;/em&gt; to get rid of the ^Ms in so the file was turned into a &quot;proper&quot; Unix text file. The trick here is that you need to use control-Q to quote the control character. In my case on a Windows box, the key sequence was &lt;em&gt;M-Shift-% Control-Q Control-M&lt;/em&gt; and then use the empty string as a replacement value. Job done, we&#039;ve now got a proper Unix mode text file. Well, after almost wearing out the &#039;Y&#039; key but of course you can use &lt;em&gt;replace-string&lt;/em&gt; instead.&lt;/p&gt;
&lt;p&gt;In order to turn the Unix mode text file into a Dos mode one, run the command &lt;em&gt;set-buffer-file-coding-system&lt;/em&gt; with the parameter &lt;em&gt;undecided-dos&lt;/em&gt; and save the resulting file. Job done.&lt;/p&gt; 
    </content:encoded>

    <pubDate>Fri, 03 Jul 2009 11:09:42 +0100</pubDate>
    <guid isPermaLink="false">http://codeblog.bsdninjas.co.uk/index.php?/archives/124-guid.html</guid>
    
</item>
<item>
    <title>Emacs lisp packages under version control</title>
    <link>http://codeblog.bsdninjas.co.uk/index.php?/archives/112-Emacs-lisp-packages-under-version-control.html</link>
            <category>Emacs</category>
    
    <comments>http://codeblog.bsdninjas.co.uk/index.php?/archives/112-Emacs-lisp-packages-under-version-control.html#comments</comments>
    <wfw:comment>http://codeblog.bsdninjas.co.uk/wfwcomment.php?cid=112</wfw:comment>

    <slash:comments>3</slash:comments>
    <wfw:commentRss>http://codeblog.bsdninjas.co.uk/rss.php?version=2.0&amp;type=comments&amp;cid=112</wfw:commentRss>
    

    <author>nospam@example.com (Timo Geusch)</author>
    <content:encoded>
    &lt;p&gt;I&#039;ve finally bit the bullet and stuck my various Emacs third-party
libraries under version control in subversion. I don&#039;t normally modify third-party packages that I use but this allows me to quickly sync my Emacs configurations between machines. In order to make this work as smoothly as I intend it to work, there is one job left to do and that
would be to create a common dot-emacs file that gets loaded by the local variants so I can have both some basic common customisations and machine-specific configurations at the same time.&lt;/p&gt;
&lt;p&gt; While collecting all the Emacs packages that I want to put under version control I&#039;ve also updated the weblogger mode that I use for my initial blog posting when I&#039;m posting out of Emacs - the workflow looks something like writing post in Emacs using weblogger.el, post to the blog as a draft, then do the final editing and cleaning up in Serendipity&#039;s built-in editor. The version of weblogger.el I&#039;m using is the version by Tom Robinson that&#039;s mentioned on EmacsWiki. I&#039;m not using weblogger mode exclusively - I&#039;ve also got the ScribeFire extension for Firefox installed, which is very handy if I just want to throw out a quick post linking to someone else&#039;s blog post - but I do like the combination of weblogger mode with Flyspell-mode and Auto-fill as they add up to a very useful text-only blogging solution.&lt;/p&gt; 
    </content:encoded>

    <pubDate>Sun, 03 May 2009 11:14:03 +0100</pubDate>
    <guid isPermaLink="false">http://codeblog.bsdninjas.co.uk/index.php?/archives/112-guid.html</guid>
    
</item>
<item>
    <title>Good article for CEDET beginners like me</title>
    <link>http://codeblog.bsdninjas.co.uk/index.php?/archives/96-Good-article-for-CEDET-beginners-like-me.html</link>
            <category>Emacs</category>
    
    <comments>http://codeblog.bsdninjas.co.uk/index.php?/archives/96-Good-article-for-CEDET-beginners-like-me.html#comments</comments>
    <wfw:comment>http://codeblog.bsdninjas.co.uk/wfwcomment.php?cid=96</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://codeblog.bsdninjas.co.uk/rss.php?version=2.0&amp;type=comments&amp;cid=96</wfw:commentRss>
    

    <author>nospam@example.com (Timo Geusch)</author>
    <content:encoded>
    &lt;p&gt;&lt;a href=&quot;http://alexott.blogspot.com/&quot; title=&quot;Link to Alex Ott&#039;s blog&quot;&gt;Alex Ott&lt;/a&gt; was kind enough to point me in the direction of an article he wrote on how to get started with CEDET. It&#039;s called &lt;a href=&quot;http://xtalk.msk.su/%7Eott/en/writings/emacs-devenv/EmacsCedet.html&quot;&gt;A Gentle introduction to Cedet&lt;/a&gt; and I would certainly recommend reading it if you&#039;re interested in massively improving your Emacs/C++ environment. Of course the same goes for the other languages supported by CEDET but being mainly a C++ developer, this is of course where my main interest lies.&lt;/p&gt;
&lt;p&gt;I guess I&#039;ll be downloading the development version of CEDET in the next couple of days then.&lt;/p&gt; 
    </content:encoded>

    <pubDate>Wed, 25 Feb 2009 11:02:50 +0000</pubDate>
    <guid isPermaLink="false">http://codeblog.bsdninjas.co.uk/index.php?/archives/96-guid.html</guid>
    
</item>
<item>
    <title>Looks like I unfairly blamed weblogger-mode</title>
    <link>http://codeblog.bsdninjas.co.uk/index.php?/archives/95-Looks-like-I-unfairly-blamed-weblogger-mode.html</link>
            <category>Emacs</category>
    
    <comments>http://codeblog.bsdninjas.co.uk/index.php?/archives/95-Looks-like-I-unfairly-blamed-weblogger-mode.html#comments</comments>
    <wfw:comment>http://codeblog.bsdninjas.co.uk/wfwcomment.php?cid=95</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://codeblog.bsdninjas.co.uk/rss.php?version=2.0&amp;type=comments&amp;cid=95</wfw:commentRss>
    

    <author>nospam@example.com (Timo Geusch)</author>
    <content:encoded>
    &lt;p&gt;Looks like I unfairly blamed my update of weblogger-mode for stripping
out &amp;lt; and &amp;gt; from my HTML-formatted blog posts when I submit them
using the xml-rpc interface and thus rendering any sort of HTML formatting more than
slightly useless.&lt;/p&gt;

&lt;p&gt;After some additional testing, it now seems that this is happening with
other clients as well, at least when I&#039;m submitting new posts to the
blog. I think I should bite the bullet and update &lt;a href=&quot;http://www.s9y.org/&quot; title=&quot;Serendipity homepage&quot;&gt;Serendipity&lt;/a&gt; to the
latest release and then test again. And if it still doesn&#039;t work some
PHP debugging might be in order. Oh well, looks like I blamed the wrong tool then...&lt;/p&gt; 
    </content:encoded>

    <pubDate>Wed, 25 Feb 2009 06:40:58 +0000</pubDate>
    <guid isPermaLink="false">http://codeblog.bsdninjas.co.uk/index.php?/archives/95-guid.html</guid>
    
</item>
<item>
    <title>Two more useful emacs modes</title>
    <link>http://codeblog.bsdninjas.co.uk/index.php?/archives/81-Two-more-useful-emacs-modes.html</link>
            <category>Emacs</category>
    
    <comments>http://codeblog.bsdninjas.co.uk/index.php?/archives/81-Two-more-useful-emacs-modes.html#comments</comments>
    <wfw:comment>http://codeblog.bsdninjas.co.uk/wfwcomment.php?cid=81</wfw:comment>

    <slash:comments>4</slash:comments>
    <wfw:commentRss>http://codeblog.bsdninjas.co.uk/rss.php?version=2.0&amp;type=comments&amp;cid=81</wfw:commentRss>
    

    <author>nospam@example.com (Timo Geusch)</author>
    <content:encoded>
    &lt;p&gt;Nothing really groundbreaking but something I found after reading &lt;a href=&quot;http://alexott.blogspot.com/2008/12/one-more-time-about-cedet.html&quot;&gt;Alex Ott&#039;s post on Cedet&lt;/a&gt; and looked at its website again. I had CEDET installed on several machines because &lt;a href=&quot;http://jdee.sourceforge.net/&quot; title=&quot;JDEE homepage&quot;&gt;JDEE&lt;/a&gt; requires &lt;a href=&quot;http://cedet.sourceforge.net/&quot;&gt;CEDET&lt;/a&gt; and Semantic is part of that, but apart from the occasional use of the speedbar, I pretty much ignore CEDET and all its goodies.&lt;/p&gt;

&lt;img src=&quot;http://www.bsdninjas.co.uk/blog/emacs-folding-and-which-fun.jpg&quot; alt=&quot;Emacs with semantic folding mode and which-func mode enabled&quot; /&gt;

&lt;p&gt;Anyway, the above screenshot shows Emacs with semantic-tag-folding-mode (that&#039;ll be the little tringluar markers - note the &#039;folded&#039; function) and which-func-mode (see modeline) enabled. Thanks to boost/iterator/iterator_adaptor.hpp for modelling the modes.&lt;/p&gt;

&lt;p&gt;semantic-tag-folding-mode is a mode that uses the semantic package to analyse the code and suggest appropriate code folding. Very useful and much better than the old &lt;a href=&quot;http://www.emacswiki.org/emacs-ja/FoldingMode&quot;&gt;folding-mode.el&lt;/a&gt; which required you to edit the code and insert &#039;{{{&#039; and &#039;}}}&#039; in order to enable the folding functionality. Not really possible if you&#039;re looking at a codebase that&#039;s several thousand files, each one of them consisting of hundreds if not thousands of lines. The only potential problem with this mode compared to the old folding mode is that it only works for those languages that are supported by semantic.&lt;/p&gt;
&lt;p&gt;which-func-mode, another of these little but very useful minor modes that displays the name of the current function in the modeline. Again, very useful when you&#039;re staring at files that are several thousand lines long and have functions whose length is measured in hundreds of lines.&lt;/p&gt; 
    </content:encoded>

    <pubDate>Sun, 18 Jan 2009 19:19:00 +0000</pubDate>
    <guid isPermaLink="false">http://codeblog.bsdninjas.co.uk/index.php?/archives/81-guid.html</guid>
    
</item>
<item>
    <title>Cool emacs tip over at emacs-fu</title>
    <link>http://codeblog.bsdninjas.co.uk/index.php?/archives/82-Cool-emacs-tip-over-at-emacs-fu.html</link>
            <category>Emacs</category>
    
    <comments>http://codeblog.bsdninjas.co.uk/index.php?/archives/82-Cool-emacs-tip-over-at-emacs-fu.html#comments</comments>
    <wfw:comment>http://codeblog.bsdninjas.co.uk/wfwcomment.php?cid=82</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://codeblog.bsdninjas.co.uk/rss.php?version=2.0&amp;type=comments&amp;cid=82</wfw:commentRss>
    

    <author>nospam@example.com (Timo Geusch)</author>
    <content:encoded>
    &lt;p&gt;If you and your colleagues use the famous &quot;TODO&quot;, &quot;FIXME&quot; tags in comments in your code, the code snippet described in the &lt;a href=&quot;http://emacs-fu.blogspot.com/2008/12/highlighting-todo-fixme-and-friends.html&quot;&gt;this blog post&lt;/a&gt; might come in very handy. It&#039;s certainly something that&#039;ll find its way into my .emacs later today...&lt;/p&gt; 
    </content:encoded>

    <pubDate>Wed, 17 Dec 2008 11:02:49 +0000</pubDate>
    <guid isPermaLink="false">http://codeblog.bsdninjas.co.uk/index.php?/archives/82-guid.html</guid>
    
</item>
<item>
    <title>Another hooray for emacs</title>
    <link>http://codeblog.bsdninjas.co.uk/index.php?/archives/78-Another-hooray-for-emacs.html</link>
            <category>Emacs</category>
    
    <comments>http://codeblog.bsdninjas.co.uk/index.php?/archives/78-Another-hooray-for-emacs.html#comments</comments>
    <wfw:comment>http://codeblog.bsdninjas.co.uk/wfwcomment.php?cid=78</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://codeblog.bsdninjas.co.uk/rss.php?version=2.0&amp;type=comments&amp;cid=78</wfw:commentRss>
    

    <author>nospam@example.com (Timo Geusch)</author>
    <content:encoded>
    &lt;p&gt;This morning I attacked a problem that had been annoying me for quite a while. One project I&#039;m working on has a rather big C++ code base with a large number of include files, strewn across a large number of subdirectories. So far, so good. Unfortunately the include statements didn&#039;t contain the partial paths of the form &quot;subdir/include&quot; which means that the compiler was passed include paths long enough to wrap a Christmas tree or two in. Not good.&lt;/p&gt;

&lt;p&gt;Originally I didn&#039;t think much of this but when I tried to speed up the compile and started measuring compile times, I noticed that supplying these partial paths made a measurable difference to the compile time, at least when using Microsoft Visual C++. Of course this does make sense simply because the compiler has to search fewer directories to identify the correct file, but I was still surprised that the difference could be measured and was actually within a margin that I&#039;d consider significant.&lt;/p&gt;
 &lt;br /&gt;&lt;a href=&quot;http://codeblog.bsdninjas.co.uk/index.php?/archives/78-Another-hooray-for-emacs.html#extended&quot;&gt;Continue reading &quot;Another hooray for emacs&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 05 Dec 2008 16:20:10 +0000</pubDate>
    <guid isPermaLink="false">http://codeblog.bsdninjas.co.uk/index.php?/archives/78-guid.html</guid>
    
</item>
<item>
    <title>Another reason why I'm not too keen on Aquamacs</title>
    <link>http://codeblog.bsdninjas.co.uk/index.php?/archives/71-Another-reason-why-Im-not-too-keen-on-Aquamacs.html</link>
            <category>Emacs</category>
    
    <comments>http://codeblog.bsdninjas.co.uk/index.php?/archives/71-Another-reason-why-Im-not-too-keen-on-Aquamacs.html#comments</comments>
    <wfw:comment>http://codeblog.bsdninjas.co.uk/wfwcomment.php?cid=71</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://codeblog.bsdninjas.co.uk/rss.php?version=2.0&amp;type=comments&amp;cid=71</wfw:commentRss>
    

    <author>nospam@example.com (Timo Geusch)</author>
    <content:encoded>
    
&lt;p&gt;Obviously the big advantage of &lt;a href=&quot;http://aquamacs.org/&quot;&gt;Aquamacs&lt;/a&gt; is that it visually integrates a lot better with Mac OS X than most of the other Emacs ports out there. Also, for better integration some of the keyboard bindings are changed out of the box, and this is where it falls apart for me. I am using a German keyboard layout on my Mac, which means that I need to use Option-something a lot to get at the special characters needed for programming, like &#039;[&#039; etc. Unfortunately these key bindings have been remapped in Aquamacs, which makes it a little problematic to use.&lt;/p&gt;
&lt;p&gt;Yes, I know I can go and remap the keys again but my point is that it works out of the box with the other Emacsen available for the Mac, namely the Apple-supplied port and Carbon Emacs. That is a bit of a pity, but maybe it would be possible to offer &#039;standard Emacs key bindings&#039; as an option when installing Aquamacs?&lt;/p&gt; 
    </content:encoded>

    <pubDate>Sun, 31 Aug 2008 08:14:32 +0100</pubDate>
    <guid isPermaLink="false">http://codeblog.bsdninjas.co.uk/index.php?/archives/71-guid.html</guid>
    
</item>
<item>
    <title>Weblogger Mode finally playing with Serendipity!</title>
    <link>http://codeblog.bsdninjas.co.uk/index.php?/archives/59-Weblogger-Mode-finally-playing-with-Serendipity!.html</link>
            <category>Emacs</category>
    
    <comments>http://codeblog.bsdninjas.co.uk/index.php?/archives/59-Weblogger-Mode-finally-playing-with-Serendipity!.html#comments</comments>
    <wfw:comment>http://codeblog.bsdninjas.co.uk/wfwcomment.php?cid=59</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://codeblog.bsdninjas.co.uk/rss.php?version=2.0&amp;type=comments&amp;cid=59</wfw:commentRss>
    

    <author>nospam@example.com (Timo Geusch)</author>
    <content:encoded>
    &lt;p&gt;Phew, that took a little while. After reading other people&#039;s stories as to how they got &lt;a href=&quot;http://www.emacswiki.org/cgi-bin/wiki/WebloggerMode&quot;&gt;weblogger mode&lt;/a&gt; to play with their blogging system of choice, I made another attempt at getting it working properly, in other words without it eating the title.&lt;/p&gt;
&lt;p&gt;After my Google mojo deserted me, I started looking at the code for both weblogger.el and &lt;a href=&quot;http://www.emacswiki.org/cgi-bin/wiki/XmlRpc&quot;&gt;xml-rpc.el&lt;/a&gt; to find what debugging helpers were available. Fortunately xml-rpc.el has a variable (xml-rpc-debug) that enables the user to view both the Lisp structure that is fed in and more importantly, the XML generated for the RPC call. This quickly pointed me in the right direction - for some reason, the entries sent didn&#039;t have a title node in the XML. Five minutes and some Lisp hacking later and it was clear that this was because the weblogger-capabilities setting (which weblogger.el fills in with the information retrieved from the server) was, well, empty, on account of getting no response from the server. And in that case, weblogger.el reverts back to the lowest common denominator (Blogger).&lt;/p&gt;
&lt;p&gt;A poke around the source code for &lt;a href=&quot;http://www.s9y.org/&quot;&gt;Serendipity&#039;s&lt;/a&gt; XML RPC handler plugin showed why - it doesn&#039;t support the &lt;em&gt;mt.supportedMethods&lt;/em&gt; calls that weblogger mode uses to determine what the server can and can&#039;t do. Of course this wasn&#039;t a problem with the other blog clients I used as they relied on the user to specify the type of XML RPC Api used to communicate with the server.&lt;/p&gt;
&lt;p&gt;A little bit of hacking and swearing (I don&#039;t really know PHP, so that didn&#039;t help) saw a handler for this call added and magically, the titles are now making it through OK. I&#039;ll try to email the maintainers of the plugin to see if they&#039;re interested in including the patch; depending on the outcome, I&#039;ll either put it up here for those interested or it&#039;ll come to Serendipity soon anyway.&lt;/p&gt; 
    </content:encoded>

    <pubDate>Fri, 15 Feb 2008 20:14:32 +0000</pubDate>
    <guid isPermaLink="false">http://codeblog.bsdninjas.co.uk/index.php?/archives/59-guid.html</guid>
    
</item>
<item>
    <title>Blogging with Emacs revisited - if you can read this, it worked</title>
    <link>http://codeblog.bsdninjas.co.uk/index.php?/archives/46-Blogging-with-Emacs-revisited-if-you-can-read-this,-it-worked.html</link>
            <category>Emacs</category>
    
    <comments>http://codeblog.bsdninjas.co.uk/index.php?/archives/46-Blogging-with-Emacs-revisited-if-you-can-read-this,-it-worked.html#comments</comments>
    <wfw:comment>http://codeblog.bsdninjas.co.uk/wfwcomment.php?cid=46</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://codeblog.bsdninjas.co.uk/rss.php?version=2.0&amp;type=comments&amp;cid=46</wfw:commentRss>
    

    <author>nospam@example.com (Timo Geusch)</author>
    <content:encoded>
    &lt;p&gt;I&#039;ve mentioned this before, after using &lt;a href=&quot;http://dropline.net/drivel/&quot;&gt;Drivel&lt;/a&gt; for a while I was looking for a way to post to my blog from inside (X)Emacs. I already use Emacs to post to newsgroups (using gnus) so why not use it to prepare posts to my blog as well? At the end of the day the majority of a blog posting is text, which should be spelled correctly and hopefully also include a few coherent thoughts, even though the latter may be conspicuously absent.&lt;/p&gt;&lt;p&gt;A recent posting on one of the Emacs newsgroups led me again to the &lt;a href=&quot;http://www.emacswiki.org/&quot;&gt;EmacsWiki&lt;/a&gt; and more specifically the &lt;a href=&quot;http://www.emacswiki.org/cgi-bin/wiki/CategoryJournaling&quot;&gt;Journal editing&lt;/a&gt; section. This in turn led to WebloggerMode, which does allow me to post via XML-RPC and supports posting to various blog systems. As &lt;a href=&quot;http://www.s9y.org/&quot;&gt;Serendipity&lt;/a&gt; uses the same format as Moveable Type, posting should work the same way as it does from Drivel. I am actually not using the &amp;quot;official&amp;quot; version of WebloggerMode, but the patched one from &lt;a href=&quot;http://jwickers.wordpress.com/2007/09/20/webloggerel-enhanced/&quot;&gt;here&lt;/a&gt;. So far, the setup has worked so let&#039;s hope the posting does, too.&lt;/p&gt;&lt;p&gt;One of the main attractions to this mode is that it does support publishing in draft mode, which Drivel doesn&#039;t seem to support, and neither seem most of the other (free) clients I tried. As I normally write blog entries somewhere offline, revise it several times and then upload the entries to the blog, I do my final editing in Serendipity&#039;s editor. Having the blog entry published and then immediately afterwards publishing a correction seems to me as a bit backwards.&lt;/p&gt;&lt;p&gt;And yes, posting to the blog did work because otherwise, you wouldn&#039;t be seeing this text. The only part that didn&#039;t make it was the title of the entry but that&#039;s easily fixed when doing the final editing in Serendipity. It also seems that I do need to do a full markup of the entry itself (paragraphs et al) but that&#039;s not exactly a big issue, either. Nevertheless, I find the experience a tad underwhelming as several features that you&#039;d hope/expect to work don&#039;t seem to. All I wasn&#039;t overly enamoured with weblogger mode, mainly because it didn&#039;t seem to be able to download the bodies of other entries when you&#039;re posting and asking it to retrieve the previous entry. Got the title alright, though, but that&#039;s a tad too asymmetric for my liking. Yes, I probably should have tried the unpatched version as well but life&#039;s a tad to short for trying all possible permutations. I also don&#039;t seem to be the only person having &lt;a href=&quot;http://sachachua.com/wp/2008/02/02/4728/&quot; target=&quot;_blank&quot;&gt;problems or issues with weblogger mode&lt;/a&gt;, so maybe it does need a bit more development.&lt;/p&gt;&lt;p&gt;More searching led me to &lt;a href=&quot;http://blogtk.sourceforge.net/&quot;&gt;BloGTK&lt;/a&gt; via this &lt;a href=&quot;http://andreasjaeger.blogspot.com/2006/07/searching-for-offline-blog-editors.html&quot;&gt;blog entry&lt;/a&gt;; It appears that I&#039;m not the only one looking for a decent offline blog editor then. Photo posting isn&#039;t that important to me as you&#039;ve probably noticed already, so it&#039;s something I could live without. It looks like it&#039;s possible to at least link to an image and that&#039;s good enough for me so far. Other than that it appears to be a relatively basic client, although in some respects it&#039;s less basic than Drivel. In others, it&#039;s possibly more basic as you have to mark up links by hand but that&#039;s something I can live with so far, especially as it supports the Extended entry bit that neither Drivel or most of the other clients I tried seem to support. Nevertheless it felt a bit basic, plus it&#039;s obviously Linux only, whereas I really would like to have a client that works in both Windows and Linux. Most of my machines are dual boot so only having to learn one client is a big advantage.&lt;/p&gt;&lt;p&gt;Enter my current editor of choice, &lt;a href=&quot;http://www.larryborsato.com/bleezer/&quot;&gt;Bleezer&lt;/a&gt;. It supports all the OSs I&#039;m likely to use, it does seem to have most of the features that I need - the few missing are the &amp;quot;two parts&amp;quot; feature I liked so much about BloGTK and the &#039;publish to Draft&#039; that weblogger mode allows for. Actually it can probably do the latter as I may have overlooked a config setting.&lt;/p&gt;&lt;p&gt;So, here you have it. A post that started out in Emacs, lost its title on the way, with some additions grafted on in BloGTK and the whole thing finalised in Bleezer.&lt;/p&gt;&lt;div class=&quot;bleezer-powered&quot;&gt;&lt;p style=&quot;font-size:10px;text-align:right;&quot;&gt;&lt;i&gt;Powered by &lt;a href=&quot;http://www.bleezer.com&quot;&gt;Bleezer&lt;/a&gt;&lt;/i&gt;&lt;/p&gt;&lt;/div&gt;
&lt;p&gt;Actually I was getting ahead of myself a little as I did end up having to edit the entry in Serendipity again. Unfortunately it appears that publishing via Bleezer doesn&#039;t turn on the comments and trackbacks functionality, so I had to go back in and edit the entry online anyway. Oh well. The search may well continue for a little while.&lt;/p&gt; 
    </content:encoded>

    <pubDate>Sun, 03 Feb 2008 21:38:57 +0000</pubDate>
    <guid isPermaLink="false">http://codeblog.bsdninjas.co.uk/index.php?/archives/46-guid.html</guid>
    
</item>
<item>
    <title>Tailing output in (X)Emacs</title>
    <link>http://codeblog.bsdninjas.co.uk/index.php?/archives/33-Tailing-output-in-XEmacs.html</link>
            <category>Emacs</category>
    
    <comments>http://codeblog.bsdninjas.co.uk/index.php?/archives/33-Tailing-output-in-XEmacs.html#comments</comments>
    <wfw:comment>http://codeblog.bsdninjas.co.uk/wfwcomment.php?cid=33</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://codeblog.bsdninjas.co.uk/rss.php?version=2.0&amp;type=comments&amp;cid=33</wfw:commentRss>
    

    <author>nospam@example.com (Timo Geusch)</author>
    <content:encoded>
    
&lt;p&gt;Today, I needed to watch and analyse the output of a compile run on Linux - that&#039;s easy, right?&lt;/p&gt;&lt;p&gt;Well, it would&#039;ve been if the build scripts for the project weren&#039;t so helpful as to automatically redirect the compiler output into a file, to preserve it for posterity. Not very helpful if you&#039;re trying to &amp;quot;just watch&amp;quot; the output. But as Emacs has a solution for just about everything, I had a poke around Google and the EmacsWiki to see if I could find something suitable.&lt;/p&gt;
 &lt;br /&gt;&lt;a href=&quot;http://codeblog.bsdninjas.co.uk/index.php?/archives/33-Tailing-output-in-XEmacs.html#extended&quot;&gt;Continue reading &quot;Tailing output in (X)Emacs&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Wed, 08 Aug 2007 14:18:23 +0100</pubDate>
    <guid isPermaLink="false">http://codeblog.bsdninjas.co.uk/index.php?/archives/33-guid.html</guid>
    
</item>

</channel>
</rss>