<?xml version="1.0" encoding="utf-8"?>
<!--
    This web page is actually a data file that is meant to be read by
    RSS reader programs.

    See http://interglacial.com/rss/about.html to learn more about
    RSS.
-->
<rss version="2.0"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
     xmlns:wfw="http://wellformedweb.org/CommentAPI/">
<channel>
  <title>Michael Olson - Blog - /Tech</title>
  <link>http://blog.mwolson.org</link>
  <atom:link href="http://blog.mwolson.org/tech/index.rss" rel="self" type="application/rss+xml" />
  <description><![CDATA[
<p>Michael Olson's blog.</p>
<p>Topics: personal entries, project-related stuff (Emacs Muse and ERC in particular), tech, quotes, cooking tips, and website updates.</p>
<p>Many of these topics have their own category.</p>
]]></description>
  <language>en</language>
  <copyright>Copyright 2004, 2005, 2006, 2007 Michael Olson</copyright>
  <lastBuildDate>Sun, 31 Jan 2010 19:35 GMT</lastBuildDate>
  <pubDate>Sun, 31 Jan 2010 19:35 GMT</pubDate>
  <managingEditor>mwolson@member.fsf.org (Michael Olson)</managingEditor>
  <generator>PyBlosxom http://pyblosxom.sourceforge.net/ 1.4.2 8/16/2007</generator>
<item>
  <title>[projects] Emacs Muse 3.20 released</title>
  <guid isPermaLink="true">http://blog.mwolson.org/tech/projects/emacs_muse_3.20_released</guid>
  <link>http://blog.mwolson.org/tech/projects/emacs_muse_3.20_released.html</link>
  <category domain="http://blog.mwolson.org">tech/projects</category>
  <author>mwolson@member.fsf.org (Michael Olson)</author>
  <comments>http://blog.mwolson.org/tech/projects/emacs_muse_3.20_released.html#comments</comments>
  <slash:comments></slash:comments>
  <wfw:comment>http://blog.mwolson.org/commentAPI/tech/projects/emacs_muse_3.20_released</wfw:comment>
  <wfw:commentRss>http://blog.mwolson.org/tech/projects/emacs_muse_3.20_released.rss</wfw:commentRss>
  <pubDate>Sun, 31 Jan 2010 19:35 GMT</pubDate>
  <description><![CDATA[
<p>Emacs Muse 3.20 is now available.</p>

<p>Emacs Muse is an authoring and publishing environment for Emacs. It
simplifies the process of writing documents and publishing them to
various output formats.  One of the principal aims in the development
of Muse is to make it very easy to produce good-looking,
standards-compliant documents.</p>

<p>This will be my last release as maintainer of Emacs Muse, and the
project will need a need maintainer effective immediately.</p>

<dl>
<dt><strong>Release info</strong></dt><dd>

<dl>
<dt><strong>Tarball</strong></dt>
<dd><a href="http://download.gna.org/muse-el/muse-3.20.tar.gz">http://download.gna.org/muse-el/muse-3.20.tar.gz</a></dd>
<dt><strong>Zip file</strong></dt>
<dd><a href="http://download.gna.org/muse-el/muse-3.20.zip">http://download.gna.org/muse-el/muse-3.20.zip</a></dd>
</dl></dd>
</dl>

]]></description>
</item>
<item>
  <title>[tech] Making annoying Emacs find-file completions go away</title>
  <guid isPermaLink="true">http://blog.mwolson.org/tech/making_annoying_emacs_find-file_completions_go_away</guid>
  <link>http://blog.mwolson.org/tech/making_annoying_emacs_find-file_completions_go_away.html</link>
  <category domain="http://blog.mwolson.org">tech</category>
  <author>mwolson@member.fsf.org (Michael Olson)</author>
  <comments>http://blog.mwolson.org/tech/making_annoying_emacs_find-file_completions_go_away.html#comments</comments>
  <slash:comments></slash:comments>
  <wfw:comment>http://blog.mwolson.org/commentAPI/tech/making_annoying_emacs_find-file_completions_go_away</wfw:comment>
  <wfw:commentRss>http://blog.mwolson.org/tech/making_annoying_emacs_find-file_completions_go_away.rss</wfw:commentRss>
  <pubDate>Tue, 02 Jun 2009 05:40 GMT</pubDate>
  <description><![CDATA[
<p>I had a guest over who ssh'd into a machine named similarly to one of
my top-level directories.  This caused <code>M-x find-file</code> to show his
machine every time I tried to tab-complete on that directory.  Very
annoying.  It turns out that tramp is to blame: it reads
<code>~/.ssh/known-hosts</code> every time <code>find-file</code> is run.  To make that bad
completion go away, just remove all mentions of the machine name from
<code>~/.ssh/known_hosts</code>.</p>

]]></description>
</item>
<item>
  <title>[tech] HCoop Sysadmin no longer</title>
  <guid isPermaLink="true">http://blog.mwolson.org/tech/stepping_down_from_hcoop_sysadmin_position</guid>
  <link>http://blog.mwolson.org/tech/stepping_down_from_hcoop_sysadmin_position.html</link>
  <category domain="http://blog.mwolson.org">tech</category>
  <author>mwolson@member.fsf.org (Michael Olson)</author>
  <comments>http://blog.mwolson.org/tech/stepping_down_from_hcoop_sysadmin_position.html#comments</comments>
  <slash:comments></slash:comments>
  <wfw:comment>http://blog.mwolson.org/commentAPI/tech/stepping_down_from_hcoop_sysadmin_position</wfw:comment>
  <wfw:commentRss>http://blog.mwolson.org/tech/stepping_down_from_hcoop_sysadmin_position.rss</wfw:commentRss>
  <pubDate>Mon, 01 Jun 2009 16:04 GMT</pubDate>
  <description><![CDATA[
<p>I don't think it has been announced elsewhere yet, so I thought I'd
mention this: I've stepped down from my responsibilities as an <a href="http://hcoop.net/">HCoop</a>
Sysadmin.  The primary reason is lack of motivation to work on remote
system administration, particularly without machines to stage changes
on before they hit prime time.  Programming as a day job has been very
good to me, to the extent that sysadmin work feels like drudgery.</p>

<p>It's been instructive.  I had to adapt a lot of essential utilities
like Mailman, Exim, and Courier to work with the <a href="http://openafs.org/">AFS filesystem</a>.
Hacking Exim was easily the most invasive AFS-related change, and
involved me grepping through the large Exim spec document numerous
times.  I also had to work on a cron script hack to deal with the mess
procmail makes when it can't write to AFS for whatever reason.</p>

<p>It has also been fun.  I've worked on a
<a href="http://wiki.hcoop.net/DebianPackaging">method for using git to work on custom changes to Debian packages</a>.
I've been impressed with the idea of directory-level ACL's, as
implemented by AFS.  I've been less than impressed with the idea of
tokens that expire, causing standard tools to display weird error
messages.  I've written and organized a major collaborative
documentation effort: <a href="http://wiki.hcoop.net/MemberManual">the HCoop Member Manual</a>.  I've automated much of
the work of signing and managing SSL certificates as a site-specific
certificate authority.</p>

]]></description>
</item>
<item>
  <title>[tech] Emacs Clipboard manager</title>
  <guid isPermaLink="true">http://blog.mwolson.org/tech/emacs_clipboard_manager</guid>
  <link>http://blog.mwolson.org/tech/emacs_clipboard_manager.html</link>
  <category domain="http://blog.mwolson.org">tech</category>
  <author>mwolson@member.fsf.org (Michael Olson)</author>
  <comments>http://blog.mwolson.org/tech/emacs_clipboard_manager.html#comments</comments>
  <slash:comments></slash:comments>
  <wfw:comment>http://blog.mwolson.org/commentAPI/tech/emacs_clipboard_manager</wfw:comment>
  <wfw:commentRss>http://blog.mwolson.org/tech/emacs_clipboard_manager.rss</wfw:commentRss>
  <pubDate>Tue, 30 Sep 2008 14:49 GMT</pubDate>
  <description><![CDATA[
<p>I had an idea for a new Emacs mode yesterday while talking with a
coworker: a clipboard manager for Emacs.  Think <code>M-x browse-kill-ring</code>,
but able to pick up on yanks and kills made by other X programs, and
set the current X (and Emacs) selection.  An initial search didn't
yield anything similar to this, so it might be interesting to
implement &mdash; don't think I'll do it myself, though, since XFCE's
Clipman is good enough for me.</p>

]]></description>
</item>
<item>
  <title>[tech] When not to use Gmane</title>
  <guid isPermaLink="true">http://blog.mwolson.org/tech/when_not_to_use_gmane</guid>
  <link>http://blog.mwolson.org/tech/when_not_to_use_gmane.html</link>
  <category domain="http://blog.mwolson.org">tech</category>
  <author>mwolson@member.fsf.org (Michael Olson)</author>
  <comments>http://blog.mwolson.org/tech/when_not_to_use_gmane.html#comments</comments>
  <slash:comments></slash:comments>
  <wfw:comment>http://blog.mwolson.org/commentAPI/tech/when_not_to_use_gmane</wfw:comment>
  <wfw:commentRss>http://blog.mwolson.org/tech/when_not_to_use_gmane.rss</wfw:commentRss>
  <pubDate>Fri, 19 Sep 2008 04:46 GMT</pubDate>
  <description><![CDATA[
<p><a href="http://gmane.org/">Gmane</a> is a handy way to follow mailing lists, especially those with a
large volume of messages.  There are cases when it is not a good idea
to use it, however.</p>

<p>Maintainers of a project should definitely <strong>not</strong> use it to follow
mailing lists for their projects.  The same goes for active
contributors.  The reasons are as follows.</p>

<ol>
<li>If your main computer breaks down and you have to rely on just
websites, you would have to visit the Gmane web interface for each
mailing list that you're a part of.  This would mean you can't
easily keep track of which messages have been seen, and becomes a
hassle if you're involved in several projects.</li>

<li>More things can go wrong.  Most people use something like leafnode
to download messages from Gmane.  I recently ran into a bug where
leafnode was not fetching messages for any newsgroups (after about
three weeks of being without internet access) until each newsgroup
was visited and had all of its messages read.  I just don't have
time to investigate such things.</li>

<li>If your mailing list has a policy of sending replies both to
individual senders and the list itself, this is nontrivial to do.</li>
</ol>

]]></description>
</item>
<item>
  <title>[tech] No more PGP signatures</title>
  <guid isPermaLink="true">http://blog.mwolson.org/tech/no_more_pgp_signatures</guid>
  <link>http://blog.mwolson.org/tech/no_more_pgp_signatures.html</link>
  <category domain="http://blog.mwolson.org">tech</category>
  <author>mwolson@member.fsf.org (Michael Olson)</author>
  <comments>http://blog.mwolson.org/tech/no_more_pgp_signatures.html#comments</comments>
  <slash:comments></slash:comments>
  <wfw:comment>http://blog.mwolson.org/commentAPI/tech/no_more_pgp_signatures</wfw:comment>
  <wfw:commentRss>http://blog.mwolson.org/tech/no_more_pgp_signatures.rss</wfw:commentRss>
  <pubDate>Thu, 07 Aug 2008 15:18 GMT</pubDate>
  <description><![CDATA[
<p>I'm going to stop using PGP signatures in email messages that I send.
While it can be satisfying to sign off on every email by entering a
PGP passphrase, it is just not worth the effort anymore.  Not enough
other people use them, and many of those who don't use them get
confused when they receive these messages, due to their email clients
sucking.</p>

]]></description>
</item>
<item>
  <title>[tech] The next big thing: sharing GUI windows</title>
  <guid isPermaLink="true">http://blog.mwolson.org/tech/the_next_big_thing__sharing_gui_windows</guid>
  <link>http://blog.mwolson.org/tech/the_next_big_thing__sharing_gui_windows.html</link>
  <category domain="http://blog.mwolson.org">tech</category>
  <author>mwolson@member.fsf.org (Michael Olson)</author>
  <comments>http://blog.mwolson.org/tech/the_next_big_thing__sharing_gui_windows.html#comments</comments>
  <slash:comments></slash:comments>
  <wfw:comment>http://blog.mwolson.org/commentAPI/tech/the_next_big_thing__sharing_gui_windows</wfw:comment>
  <wfw:commentRss>http://blog.mwolson.org/tech/the_next_big_thing__sharing_gui_windows.rss</wfw:commentRss>
  <pubDate>Thu, 07 Aug 2008 06:27 GMT</pubDate>
  <description><![CDATA[
<p>I think that the next big thing in GUI apps should be the ability to
take the exact contents of a window and send them to a remote machine.
The use case for this is: you start an app at home, go to work, ssh
(with X forwarding) into your home machine, and realize that you need
to use that app again.  Normally you'd kill the app and restart it.
But what if you could just &quot;clone&quot; the window so that it appeared on
your work machine, responsive to new input?  I'd love to see
functionality like this being added at the toolkit level (i.e. GTK,
Qt) so that application developers would not have to do any work to
activate it.</p>

<p>One of the nice things about running many apps in Emacs is that I
already have that ability.  I can just use the multi-tty support in
Emacs 23 to open up either a terminal window or a new GTK frame, and
then switch to the buffer that contains the app.</p>

]]></description>
</item>
</channel>
</rss>
