<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>hatsuseno&#039;s blog &#187; awesome</title>
	<atom:link href="http://blog.hatsuseno.org/index.php/tag/awesome/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hatsuseno.org</link>
	<description>rantings on tech</description>
	<lastBuildDate>Tue, 12 Jul 2011 09:26:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Porting Windows behaviour to Linux :)</title>
		<link>http://blog.hatsuseno.org/index.php/porting-windows-behaviour-to-linux/</link>
		<comments>http://blog.hatsuseno.org/index.php/porting-windows-behaviour-to-linux/#comments</comments>
		<pubDate>Wed, 07 Jul 2010 17:33:54 +0000</pubDate>
		<dc:creator>hatsuseno</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[awesome]]></category>
		<category><![CDATA[custom-scripts]]></category>
		<category><![CDATA[gui]]></category>
		<category><![CDATA[scripts]]></category>

		<guid isPermaLink="false">http://blog.hatsuseno.org/?p=214</guid>
		<description><![CDATA[In the olden days when I still used Windows, I loved having the ALT+PrintScreen keycombo around, it makes a screen capture of only the currently active window, nicely cropped and everything. This saves you the hassle of aligning it pixel-perfect in Paint. On Linux, at least using awesome, I haven&#8217;t been able to do this, [...]]]></description>
			<content:encoded><![CDATA[<p>In the olden days when I still used Windows, I loved having the ALT+PrintScreen keycombo around, it makes a screen capture of only the currently active window, nicely cropped and everything. This saves you the hassle of aligning it pixel-perfect in Paint. On Linux, at least using awesome, I haven&#8217;t been able to do this, so I wrote a quick script that allows me to do that and a bit more.</p>
<p><strong>grabw</strong> is a bash script that allows you to</p>
<ol>
<li>Take a screenshot of a window by X window ID</li>
<li>Take a screenshot of a window the user first has to click, using xwininfo</li>
<li>The above two with or without asking for a filename using Zenity&#8217;s file selection dialogue window</li>
</ol>
<p>Combine this with awesome&#8217;s ability to spawn processes on the fly and pass parameters (such as window IDs, *hint hint*) this is one feature I&#8217;m glad to have back</p>
<p><strong>grabw 0.2</strong> has been released into public domain, you can find it on my <a href="http://projects.hatsuseno.org">projects</a> page.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.hatsuseno.org/index.php/porting-windows-behaviour-to-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Gentoo, awesome and themes</title>
		<link>http://blog.hatsuseno.org/index.php/gentoo-awesome-and-themes/</link>
		<comments>http://blog.hatsuseno.org/index.php/gentoo-awesome-and-themes/#comments</comments>
		<pubDate>Thu, 25 Feb 2010 03:53:23 +0000</pubDate>
		<dc:creator>hatsuseno</dc:creator>
				<category><![CDATA[Gentoo errors]]></category>
		<category><![CDATA[awesome]]></category>
		<category><![CDATA[custom-scripts]]></category>
		<category><![CDATA[gentoo]]></category>
		<category><![CDATA[themes]]></category>
		<category><![CDATA[wallpaper]]></category>

		<guid isPermaLink="false">http://blog.hatsuseno.org/?p=126</guid>
		<description><![CDATA[I&#8217;ve been a Gentoo user since forever, and for some time I&#8217;ve been using awesome for a window manager instead of the desktop environments Gnome or KDE. One thing I never got around to change was the wallpaper. My terminals are pseudo-transparent, and I never disliked the default &#8216;awesome&#8217; wallpaper. @ZackLeonhart&#8216;s bitching and moaning changed [...]]]></description>
			<content:encoded><![CDATA[<p><img alt="" src="http://hammerfest.hatsuseno.org/~crashmatrix/awesome_logo.png" title="Awesome logo" class="alignleft" width="64" height="64" />
<p>I&#8217;ve been a Gentoo user since forever, and for some time I&#8217;ve been using awesome for a window manager instead of the desktop environments Gnome or KDE. One thing I never got around to change was the wallpaper. My terminals are pseudo-transparent, and I never disliked the default &#8216;awesome&#8217; wallpaper. <a href='http://twitter.com/ZackLeonhart'>@ZackLeonhart</a>&#8216;s bitching and moaning changed that.</p>
<p>Turns out that aside from editing the system-wide theme script, by default located in <code>/usr/share/awesome/themes/*</code> (which I consider to be a BadThink&#8482;), there is no straight forward way of doing it nicely in the Gentoo provided default setup. So here&#8217;s what you do.</p>
<p><ol>
<li>Create yourself a lua.rc in <code>${HOME}/.config/awesome</code><br /><code>$ cp /etc/xdg/awesome/rc.lua ~/.config/awesome</code></li>
<li>Recursively copy all themes from the system-wide dirs to your local configdir.<br /><code>$ cp -rvf /usr/share/awesome/themes ~/.config/awesome</code></li>
<li>In your copy of lua.rc you will find a variable called <code>theme_path</code>, change it to <code>theme_path = os.getenv("HOME") .. "/.config/awesome/themes/path/to/theme.lua"</code></li>
<li>Edit the variable <code>theme.wallpaper_cmd</code> to contain the string <code>"eval `cat ~/.fehbg`"</code></li>
<li>Choose a wallpaper you like, execute <code>$ feh --bg-scale /path/to/wallpaper.jpg</code></li>
</ol>
<p>And you&#8217;re done! If you want to change your wallpaper, simply use <code>feh</code> again with a random other file, and make sure the file is readable when awesome is starting up, and it&#8217;ll set it up automagically. Basically, awesome&#8217;s &#8216;beautiful&#8217; library takes your typed out command and executes that in order to set the wallpaper, feh has a convenient way of storing the default wallpaper by simply dumping the command that was used to set it up in the first place in a configuration file in your home directory, hence the <code>eval `cat whatever`</code> trick.
</p>
<div class="wp-caption alignnone" style="width: 450px"><a href='http://hammerfest.hatsuseno.org/~crashmatrix/screencap_250210.jpg'><img alt="Screenshot of my new wallpaper in Awesome" src="http://hammerfest.hatsuseno.org/~crashmatrix/screencap_250210.jpg" title="Screenshot" width="440" /></a><p class="wp-caption-text">Screenshot of my new wallpaper in Awesome</p></div>
<p>P.S.: Don&#8217;t think you can leave out the call to os.getenv() in step 3, awesome doesn&#8217;t expand the tilde (&#8216;~&#8217;), so the path it&#8217;ll try to access will be invalid.</p>
<p>P.P.S.: This is more of a note for me, in case I ever lose my epic new wallpaper. It can be found <a href='http://upload.wikimedia.org/wikipedia/commons/e/ec/LodalenPano.jpg'>here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.hatsuseno.org/index.php/gentoo-awesome-and-themes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>gnome-terminal gconfd bullshit</title>
		<link>http://blog.hatsuseno.org/index.php/gnome-terminal-gconfd-bullshit/</link>
		<comments>http://blog.hatsuseno.org/index.php/gnome-terminal-gconfd-bullshit/#comments</comments>
		<pubDate>Tue, 19 May 2009 12:32:53 +0000</pubDate>
		<dc:creator>hatsuseno</dc:creator>
				<category><![CDATA[Gentoo errors]]></category>
		<category><![CDATA[awesome]]></category>
		<category><![CDATA[gconfd]]></category>
		<category><![CDATA[gnome]]></category>
		<category><![CDATA[gnome-terminal]]></category>
		<category><![CDATA[roxterm]]></category>

		<guid isPermaLink="false">http://blog.hatsuseno.org/?p=12</guid>
		<description><![CDATA[So I&#8217;ve been a long time proponent of GNOME and all, but I recently switched to awesome instead. Even so I like gnome-terminal a bit too much, and decided to keep it around until I found a new terminal that doesn&#8217;t pull the rest of GNOME with it when I install it. The problem Enter [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_13" class="wp-caption alignleft" style="width: 138px"><a href="http://blog.hatsuseno.org/wp-content/uploads/2009/05/gnome-terminal.png"><img class="size-full wp-image-13" title="gnome-terminal" src="http://blog.hatsuseno.org/wp-content/uploads/2009/05/gnome-terminal.png" alt="bad gnome-terminal" width="128" height="128" /></a><p class="wp-caption-text">bad gnome-terminal</p></div>
<p>So I&#8217;ve been a long time proponent of <a href="http://www.gnome.org"><acronym title='GNU Network Object Model Environment'>GNOME</acronym></a> and all, but I recently switched to <a title="awesome" href="http://awesome.naquadah.org">awesome</a> instead.</p>
<p>Even so I like gnome-terminal a bit too much, and decided to keep it around until I found a new terminal that doesn&#8217;t pull the rest of GNOME with it when I install it.</p>
<h3>The problem</h3>
<p>Enter <code>emerge -uDNvat</code> and all of a sudden gnome-terminal complains about <code>Failed to contact GConf daemon; exiting.</code>. So I ask around, people reply with something along the lines of &#8220;is gconfd-2 started&#8221;, &#8220;have you installed gconfd?&#8221; and &#8220;you dumb fuck, why do you use gnome-terminal when you&#8217;re not using gnome!&#8221;.</p>
<h3>The solution</h3>
<p>Seems in the end it was a version mismatch, I was using gnome-terminal 2.26.x and my gnome-light package was still 2.24.x. Downgraded gnome-terminal and all was well again.</p>
<p>P.S. I switched to <a href="http://roxterm.sourceforge.net/">ROXTerm</a> instead, it&#8217;s almost a clone, without all the GConf bullshit, or pulling the rest of GNOME in.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.hatsuseno.org/index.php/gnome-terminal-gconfd-bullshit/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

