01 May 2016

Adding "Run" options to Thunar

 Clicking on executable shell files no longer executes them in Thunar.

While there is a hidden option to revert to the old behavior, I decided in a new install to instead add right menu "Run" and "Run in terminal" custom actions. First create the custom actions from within Thunar to get valid unique-ids, and then open ~/.config/Thunar/uca.xml and edit the entries as needed:

<action>
    <icon>system-run</icon>
    <name>Run</name>
    <unique-id>xxxxxxxxxxxxxxxx-x</unique-id>
    <command>exec ./&apos;%n&apos;</command>
    <description>Execute this file</description>
    <patterns>*</patterns>
    <other-files/>
    <text-files/>
</action>
<action>
    <icon>xterm-color</icon>
    <name>Run in terminal</name>
    <unique-id>yyyyyyyyyyyyyyyy-y</unique-id>
    <command>xterm -T &apos;%n&apos; -e &quot;./&apos;%n&apos;; echo &apos;&apos;; read -p &apos;Press &lt;Enter&gt; to close...&apos;&quot;</command>
    <description>Execute this file in a terminal</description>
    <patterns>*</patterns>
    <other-files/>
    <text-files/>
</action>

26 April 2016

Concerns about Qt's increasing commercial focus


It's not just me. Phoronix is reporting on growing concerns in the Qt community about the project's increasing commercial focus and apparent deprecation of its open source core.

I have said many times in these pages and elsewhere that I really like Qt: it's the right tool for a lot of jobs. But increasingly I've been feeling that any contribution I make in educating users about Qt is benefiting a commercial enterprise and not a community tool. So much so that I am re-surveying other open source multi-platform libraries to use as an alternative to Qt.

If the community no longer has meaningful Qt ownership, a lot of users will no longer be interested.

25 April 2016

Fixing Debian sid touchpad with libinput

A recent sid update brought in Xorg's libinput package, which appears to make the old way of configuring touchpads (including synclient) obsolete.

One of the issues I had after the update was that my touchpad's tap-to-click stopped working. I fixed this using the info on this Stack Exchange post, namely I created a file
/usr/share/X11/xorg.conf.d/10-touchpad.conf containing:

Section "InputClass"
        Identifier "MyTouchpad"
        MatchIsTouchpad "on"
        Driver "libinput"
        Option "Tapping" "on"
EndSection

Note the different location from the one in the post. I also disabled the old 50-synaptics.conf, 50-vmmouse.conf, and 51-synaptics-aptosid.conf files (the latter two present possibly only in aptosid).

Apparently, Petter Hutterer has a post that goes into detail regarding what you can do with libinput, but I've not yet had time to read it.

Update (later the same day): With the above changes, my touchpad still had behavioral problems. I'll return to this later, but for now I re-enabled 50-synaptics.conf, 50-vmmouse.conf, and 51-synaptics-aptosid.conf and purged xserver-xorg-input-libinput (which removed xserver-xorg-input-all).

10 April 2016

Qt "Demerger"



Phoronix reports that Qt will be "demerged" from parent company Digia soon.

It seems there has always been interesting dynamics around Qt, and this I suppose is the latest chapter. I'm hoping this is more of a good sign than a bad one.

12 October 2015

Midori browser font rendering

I was having issues with Midori not rendering fonts the way I thought it should in aptosid XFCE. I set a default.css in ~/.local/share/midori/styles/default.css:
* {
    font-smooth:always !important;
    -webkit-font-smoothing: subpixel-antialiased !important;
    text-rendering: optimizeLegibility !important;
}
but that didn't fix what appeared to be wonky antialiasing. So I had a look in my ~/.Xresources and lo!:
Xft.dpi: 96
Xft.antialias: true
Xft.hinting: true
Xft.rgba: rgb
Xft.autohint: false
Xft.hintstyle: hintslight
Xft.lcdfilter: lcddefaul  !!! Typo here !!! Should be "lcddefault".
Things are much improved now. I'm not 100% certain that it's 100% right, but it's definitely mostly right.

The takeaway for you, dear reader, is not to ignore your display configuration in  ~/.Xresources.