<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Emacs Muse Aliases</title>
	<atom:link href="http://curiousprogrammer.wordpress.com/2009/03/12/emacs-muse-aliases/feed/" rel="self" type="application/rss+xml" />
	<link>http://curiousprogrammer.wordpress.com/2009/03/12/emacs-muse-aliases/</link>
	<description>Leveraging Perl and Emacs</description>
	<lastBuildDate>Sat, 15 Jun 2013 02:12:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Jared</title>
		<link>http://curiousprogrammer.wordpress.com/2009/03/12/emacs-muse-aliases/#comment-7355</link>
		<dc:creator><![CDATA[Jared]]></dc:creator>
		<pubDate>Sat, 14 Mar 2009 16:32:37 +0000</pubDate>
		<guid isPermaLink="false">http://curiousprogrammer.wordpress.com/?p=356#comment-7355</guid>
		<description><![CDATA[&lt;blockquote&gt;
Since your comment I’ve been taking a look through the documentation...
&lt;/blockquote&gt;

&lt;blockquote&gt;
Yes, take a look at the Muse manual
&lt;/blockquote&gt;

Oops, looks like I need to learn to read properly.  Cheers Peter :)]]></description>
		<content:encoded><![CDATA[<blockquote><p>
Since your comment I’ve been taking a look through the documentation&#8230;
</p></blockquote>
<blockquote><p>
Yes, take a look at the Muse manual
</p></blockquote>
<p>Oops, looks like I need to learn to read properly.  Cheers Peter <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Jones</title>
		<link>http://curiousprogrammer.wordpress.com/2009/03/12/emacs-muse-aliases/#comment-7352</link>
		<dc:creator><![CDATA[Peter Jones]]></dc:creator>
		<pubDate>Fri, 13 Mar 2009 21:36:01 +0000</pubDate>
		<guid isPermaLink="false">http://curiousprogrammer.wordpress.com/?p=356#comment-7352</guid>
		<description><![CDATA[Yes, take a look at the Muse manual, see section 10.5 &quot;Parameters used for defining styles&quot;.]]></description>
		<content:encoded><![CDATA[<p>Yes, take a look at the Muse manual, see section 10.5 &#8220;Parameters used for defining styles&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared</title>
		<link>http://curiousprogrammer.wordpress.com/2009/03/12/emacs-muse-aliases/#comment-7351</link>
		<dc:creator><![CDATA[Jared]]></dc:creator>
		<pubDate>Fri, 13 Mar 2009 20:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://curiousprogrammer.wordpress.com/?p=356#comment-7351</guid>
		<description><![CDATA[No worries Peter :)  Since your comment I&#039;ve been taking a look through the documentation and examples.  Is there a definitive list of keyword parameters that muse-derive-style takes?]]></description>
		<content:encoded><![CDATA[<p>No worries Peter <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   Since your comment I&#8217;ve been taking a look through the documentation and examples.  Is there a definitive list of keyword parameters that muse-derive-style takes?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Jones</title>
		<link>http://curiousprogrammer.wordpress.com/2009/03/12/emacs-muse-aliases/#comment-7350</link>
		<dc:creator><![CDATA[Peter Jones]]></dc:creator>
		<pubDate>Fri, 13 Mar 2009 20:53:11 +0000</pubDate>
		<guid isPermaLink="false">http://curiousprogrammer.wordpress.com/?p=356#comment-7350</guid>
		<description><![CDATA[Here is how I create a new LaTeX based style, but with a different header than the default:

(muse-derive-style &quot;pdf-logo-article&quot; &quot;pdf&quot; 
                    :header &quot;/path/to/file&quot;)

I do the same trick for HTML:

(muse-derive-style &quot;printable-xhtml&quot; &quot;xhtml&quot;
                   :header &#039;pmade-muse-html-header)

Sorry I didn&#039;t include this in my first comment.]]></description>
		<content:encoded><![CDATA[<p>Here is how I create a new LaTeX based style, but with a different header than the default:</p>
<p>(muse-derive-style &#8220;pdf-logo-article&#8221; &#8220;pdf&#8221;<br />
                    :header &#8220;/path/to/file&#8221;)</p>
<p>I do the same trick for HTML:</p>
<p>(muse-derive-style &#8220;printable-xhtml&#8221; &#8220;xhtml&#8221;<br />
                   :header &#8216;pmade-muse-html-header)</p>
<p>Sorry I didn&#8217;t include this in my first comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared</title>
		<link>http://curiousprogrammer.wordpress.com/2009/03/12/emacs-muse-aliases/#comment-7347</link>
		<dc:creator><![CDATA[Jared]]></dc:creator>
		<pubDate>Fri, 13 Mar 2009 20:33:07 +0000</pubDate>
		<guid isPermaLink="false">http://curiousprogrammer.wordpress.com/?p=356#comment-7347</guid>
		<description><![CDATA[Hi Peter,

Would you like to share that 1 line of elisp with my readers and I?

Thanks]]></description>
		<content:encoded><![CDATA[<p>Hi Peter,</p>
<p>Would you like to share that 1 line of elisp with my readers and I?</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Jones</title>
		<link>http://curiousprogrammer.wordpress.com/2009/03/12/emacs-muse-aliases/#comment-7345</link>
		<dc:creator><![CDATA[Peter Jones]]></dc:creator>
		<pubDate>Fri, 13 Mar 2009 18:25:35 +0000</pubDate>
		<guid isPermaLink="false">http://curiousprogrammer.wordpress.com/?p=356#comment-7345</guid>
		<description><![CDATA[Muse does allow you to derive new styles from existing ones.  In this case, your new style inherits all the variables and functions from the parent style, and you can override them for customization.

I use this technique all the time, e.g. different styles use different LaTeX headers and footers.  It also very clean, a new style with a different LaTeX header is only 1 line of elisp.]]></description>
		<content:encoded><![CDATA[<p>Muse does allow you to derive new styles from existing ones.  In this case, your new style inherits all the variables and functions from the parent style, and you can override them for customization.</p>
<p>I use this technique all the time, e.g. different styles use different LaTeX headers and footers.  It also very clean, a new style with a different LaTeX header is only 1 line of elisp.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
