<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  
  
  <channel>
    <title>chrisjrob: pekwm</title>
    <link>https://chrisjrob.com</link>
    <atom:link href="https://chrisjrob.com/tag/pekwm/feed/index.xml" rel="self" type="application/rss+xml" />
    <description>GNU Linux, Perl and FLOSS</description>
    <language>en-gb</language>
    <pubDate>Fri, 13 Feb 2026 17:22:31 +0000</pubDate>
    <lastBuildDate>Fri, 13 Feb 2026 17:22:31 +0000</lastBuildDate>
    
    <item>
      <title>Default Applications Launched From Terminal</title>
      <link>https://chrisjrob.com/2013/03/05/default-applications-launched-from-terminal/</link>
      <pubDate>Tue, 05 Mar 2013 00:00:00 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2013/03/05/default-applications-launched-from-terminal</guid>
      <description>
       <![CDATA[
         
         <p>For some time it has irritated me that launching URLs from my terminal
would always launch Iceweasel/Firefox, rather than my default browser
Chromium. If you’re running KDE or Gnome, then I accept that this would
be governed from somewhere in the desktop environment’s control panel or
settings, but I run <a href="http://www.pekwm.org" title="PekWM">PekWM</a>, and assumed
that setting the default browser in update-alternatives should be
enough:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code># update-alternatives --config x-www-browser
</code></pre></div></div>

<!--more-->

<p>Unfortunately of course many of the applications that I am using are
native to KDE or Gnome and probably are still respecting their
environment’s settings. In the end it was simply a case of editing:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>~/.local/share/applications/defaults.list
</code></pre></div></div>

<p>And adding the following lines:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>x-scheme-handler/http=chromium.desktop
x-scheme-handler/https=chromium.desktop
</code></pre></div></div>

<p>Now opening links from my terminal is correctly opening a new tab in
Chromium, or running Chromium if it isn’t already.</p>

<p>Joy.</p>


       ]]>
      </description>
    </item>
    
    <item>
      <title>Three Things I Love About Pekwm</title>
      <link>https://chrisjrob.com/2011/03/07/three-things-i-love-about-pekwm/</link>
      <pubDate>Mon, 07 Mar 2011 00:00:00 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2011/03/07/three-things-i-love-about-pekwm</guid>
      <description>
       <![CDATA[
         
         <p>Three things I love about <a href="http://www.pekwm.org/" title="PekWM">pekwm</a>:</p>

<p><strong>Window grouping:</strong> I love the fact that you can middle click on a
window’s titlebar and drop it onto another window and the two
windows join together - with the titlebar split in segments. You can
switch between the applications by clicking on the relevant part of
the titlebar, or use the Windows key with TAB - so just as Alt+Tab
switches between windows, Windows+Tab switches between the
applications grouped inside the current window.</p>

<!--more-->

<p><strong>Double-click to fill available space:</strong> I love the fact that you
can open an application and just double-click on its titlebar to
fill the available space. This feels so intuitive and just so damned
right, that I struggle to understand why it is not the standard
behaviour in all window managers and desktop environments.</p>

<p><strong>Clicking on the desktop edge moves you to the next workspace:</strong>
I’ve never really got on with multiple desktops/workspaces - it is
difficult enough to keep track of multiple applications inside a
single workspace, but pekwm has converted me. I find it just so
intuitive that, by clicking on the edge of the desktop, that it it
progresses you to the next desktop.</p>

<p>So what do <strong>you</strong> love about pekwm?</p>


       ]]>
      </description>
    </item>
    
    <item>
      <title>Pekwm With Tint2 Panel</title>
      <link>https://chrisjrob.com/2011/03/07/pekwm-with-tint2-panel/</link>
      <pubDate>Mon, 07 Mar 2011 00:00:00 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2011/03/07/pekwm-with-tint2-panel</guid>
      <description>
       <![CDATA[
         
           <img src="https://chrisjrob.com/assets/pekwm-snapshot_300.png" align="right" alt="Featured Image">
         
         <p>I have just been recommended to try the “tint2” panel. It looks lovely
and minimalist, and has happily taken the kwalletmanager system tray
icon; so hopefully will work on my laptop with battery and wireless
monitors.</p>

<!--more-->

<p>Whilst you’re looking at my screenshot, note the Window grouping between
Google Chrome and Iceweasel and the two terminal windows grouped
together. The window grouping feature really is very, very handy.</p>

<p>Installing tint2 is simple:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo apt-get install tint2
</code></pre></div></div>

<p>And then add tint2 to your <code class="language-plaintext highlighter-rouge">~/.pekwm/startup</code> file:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>tint2 &amp;
</code></pre></div></div>

<p>If you need to configure it, then edit <code class="language-plaintext highlighter-rouge">~/.config/tint2/tint2rc</code>; so far
I have found the defaults to be okay.</p>

<h2 id="update-battery-monitor">Update: Battery monitor</h2>

<p>To get the built in tint2 battery monitor, simply edit</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>~/.config/tint2/tint2rc:
battery = 1 battery_hide = never
</code></pre></div></div>


       ]]>
      </description>
    </item>
    
    <item>
      <title>KDE Power Management In Pekwm</title>
      <link>https://chrisjrob.com/2011/03/06/kde-power-management-in-pekwm/</link>
      <pubDate>Sun, 06 Mar 2011 00:00:00 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2011/03/06/kde-power-management-in-pekwm</guid>
      <description>
       <![CDATA[
         
         <p>After my laptop spontaneously switched off on <strong>two</strong> separate
occasions, because I had failed to switch on the mains socket, I decided
that something had to be done about the lack of power management in
<a href="http://www.pekwm.org/">pekwm</a>.</p>

<!--more-->

<p>Hunting the ‘net for anything to do with pekwm is a frustrating
business. You can’t help thinking that there are only a handful of us
that use it. I may post something about why I think pekwm is great, but
that is a topic for another day.</p>

<p>As my laptop’s primary desktop environment is KDE, I wanted to use the
KDE power management with pekwm, rather than install the Gnome Power
Manager, which would bring in a load of Gnome dependencies. If you
already have Gnome installed, then I suspect the Gnome Power Manager is
for you.</p>

<p>There seem to be three parts to this:</p>

<ol>
  <li>Getting the power management daemon to run</li>
  <li>Adding a power meter</li>
  <li>Adding the configuration tool to the menu</li>
</ol>

<p>Whilst these instructions are primarily for pekwm, I am sure that
openbox, fluxbox and other *box window managers could use them with a
little adjustment.</p>

<h2 id="power-management-daemon">Power Management Daemon</h2>

<p>In the <code class="language-plaintext highlighter-rouge">~/.pekwm/start</code> file, add the lines:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>kded4 &amp; qdbus org.kde.kded /kded loadModule powerdevil &amp;
</code></pre></div></div>

<p>If you do not want to restart pekwm to test, just run those two commands
live.</p>

<h2 id="battery-meter">Battery Meter</h2>

<p>Update: Since writing this post <a href="/2011/03/07/pekwm-with-tint2-panel/">I have discovered tint2</a> 
which includes a simple battery monitor.</p>

<p>What I really want is a battery level meter that will sit happily in
<a href="http://icculus.org/openbox/2/docker/">Docker</a>, but I failed in this
quest. If you have any suggestions, please do let me know and I will
update this post. In the meantime I have installed xbattbar, which gives
a full thin width line at the bottom of your screen.</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo apt-get install xbattbar
</code></pre></div></div>

<p>In the <code class="language-plaintext highlighter-rouge">~/.pekwm/start</code> file, add the line:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>xbattbar &amp;
</code></pre></div></div>

<h2 id="power-management-configuration">Power Management Configuration</h2>

<p>It is quite possible that you will wish to configure your power
management from within pekwm. To do this, add the following to your
<code class="language-plaintext highlighter-rouge">~/.pekwm/menu</code> file:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Entry = "Configure Powerdevil" { Actions = "Exec kcmshell4 powerdevilconfig &amp; " }
</code></pre></div></div>

<p>And that appears to be a working solution for me, I hope it works for
you too!</p>


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