Thunar is one of the best graphical file managers I’ve used, and I say that even while I own a Directory Opus license for Windows. I have some minor quibbles like very sparsely populated default actions on files and folders, but the biggest flaw is doubtless that the breadcrumb navigation doesn’t feature all of the regular folder interactions. In any case, in this blog post I intend to show how I improve on both Thunar and GNOME Search in one fell swoop.
I’ll start with a screenshot of the desired end result. You right click on a folder, and you’re presented with the option to search for files in it.
In order to add this custom action, you’ll have to configure custom actions.
Then you click + to add a new one, or you can edit an existing action.
You can type the name that will show up in the context menu, a little description for yourself, choose a fancy icon, and under appearance conditions you can choose whether this custom action applies to a specific type of files or folders. Unfortunately this dialog can’t be resized, but since you can copy and paste it’s not too bad.
gnome-search-tool --path=%f --contains=
Finally, here is the result. Note that since I started gnome-search-tool with --contains=, the option to search for files containing specific text will show by default.
You can perform similar tricks with any of these other options.
$ gnome-search-tool --help
gnome-search-tool [OPTION...] - the GNOME Search Tool
-h, --help Show help options
--help-all Show all help options
--help-gtk Show GTK+ Options
--help-sm-client Show session management options
--version Show version of the application
--named=STRING Set the text of "Name contains" search option
--path=PATH Set the tet of "Look in folder" search option
--sortby=VALUE Sort files by one of the following: name, folder, size, type, or date
--descending Set sort order to descending, the default is ascending
--start Automatically start a search
--contains=STRING Select and set the "Contains the text" search option
--mtimeless=DAYS Select and set the "Date modified less than" search option
--mtimemore=DAYS Select and set the "Date modified more than" search option
--sizemore=KILOBYTES Select and set the "Size at least" search option
--sizeless=KILOBYTES Select and set the "Size at most" search option
--empty Select the "File is empty" search option
--user=USER Select and set the "Owned by user" search option
--group=GROUP Select and set the "Owned by group" search option
--nouser Select the "Owner is unrecognized" search option
--notnamed=STRING Select and set the "Name does not contain" search option
--regex=PATTERN Select and set the "Name matches regular expression" search option
--hidden Select the "Show hidden and backup files" search option
--follow Select the "Follow symbolic links" search option
--mounts Select the "Exclude other filesystems" search option
--display=DISPLAY X display to use
To deal with the inferior FAT file system, it would seem that consumer-level Sony video cameras write video files of a maximum of about 2.1 GB. A sensible approach, but annoying to work with. Luckily they can be concatenated without any concerns or side effects for easier viewing and editing.
Over the past few years I acquired a bad habit of using search engines for basic calculations and conversions. I’m not talking about the stuff you should just do in your head — not quite that bad, but about the fact that several Linux distros, including my favorite of Debian Xfce, don’t seem to ship with a calculator by default. So I finally got around to testing some programs and Qalculate! does all I want. You can install it on Debian using sudo apt install qalculate-gtk. There’s a list of features on the website. Enjoy a few screenshots.
After some update or other, Broken Age refused to start.
Running Broken Age
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 91
Current serial number in output stream: 92
This loads the included libraries before any others, in order to override the incompatible libraries shipped with the program in question. The same trick also works for Steam. If gaming is your goal, you should probably stick to whatever version of Ubuntu is supported best. I’m just pleased that I can play the occasional game like Oxenfree (no preloading required, mind you) or Broken Age on my workhorse without having to install any stability-reducing binary blobs.
I run Debian Stretch (testing) as my daily driver, and at some point I stopped being able to start programs like start Synaptic, Gparted, Synaptic etc. without manually typing gksu(do). The solution is as simple as it is seemingly unnecessary and stupid:
sudo apt install policykit-1-gnome
The problem is apparent upon reading the description:
This implementation was originally designed for GNOME 2, but most
GNOME-based desktop environments, including GNOME 3, GNOME Flashback,
MATE and Cinnamon, have their own built-in PolicyKit agents and no
longer use this one. The remaining users of this implementation
are XFCE and Unity.
Sometimes you jot down a few quick notes for yourself without bothering to turn them into a blogpost that might be useful to others. This is one of those notes. First, I’ll introduce my computer monitor workflow as it’s been since time immemorial, also known as ’95 or ’96. Just like how I turn off lights I don’t use, I’ve always turned off my monitor when I wanted it. This has never been a problem, until in early 2015 I had to use DisplayPort for the first time. If you want an UltraHD monitor, which you do if you care even the tiniest bit about sharpness and clarity, you have to use DisplayPort.
But DisplayPort isn’t nice. Turning off your monitor is treated the same as disconnecting it. In Windows this means everything resets itself to some absurdly low resolution, whereas in Linux the consequences can be even worse (like having to SSH in from another computer to run an xrandr command to reactivate the monitor). This means you either face a colossal waste of energy or continuous annoyance at the fact that your monitor has turned itself off yet again. In my view monitor timeouts should be at least twenty minutes, just as a failsafe in the extremely unlikely event that you forgot to turn it off. Luckily I found two reasonable workarounds within the first week or two of having acquired my UHD monitor.
xset dpms force off
This has the same effect as your monitor timeout, only at your volition. I tend to find the blinking light on the monitor somewhat annoying, but this nevertheless remains your best bet to quickly turn the screen off as part of your regular workflow.
The second method consists of actually turning the monitor off. Besides getting rid of the blinking light I figure it saves just a tiny bit more electricity to boot. Which is useful if you want to keep your computer active, but not your monitor. For this method you have to switch to TTY (Ctrl + Alt + F1-6) before turning your monitor off. Then when you turn your monitor back on, X won’t know it’s been missing. Switch back with Ctrl + Alt + F7.
I’m still hopeful that there might simply be an xorg.conf setting I’ve overlooked, but in any case these workarounds serve their purpose. Note that xset dpms force off is also tremendously useful on laptops that don’t have a function key for turning off the screen. Standby often just isn’t what you want.