Clock Configuration

People become accustomed to seeing certain information displayed in their panels, and one of those is always a clock of some kind.

I like to configure that to my preference in whichever GUI I’m using in Linux, be it Fluxbox, Cinnamon, Xfce, or whatever.

A lot of times the default options available don’t have what I prefer, but nearly all Linux-friendly window managers and desktop environments offer the opportunity to enter a “custom” string for how time and date are displayed, and that’s the subject of this little writeup.

Continue reading

Xfce: Stop workspace hopping by browser

I’ve been using the Xfce desktop environment again lately, for the first time in years, because I was curious to see how it has changed over time.

As an overall, I’ve been enjoying this experiment; I was never very satisfied with it before for a variety of reasons, but its flexibility and stability are still attractive to me, and I’ve discovered that it’s better this time around than when I last gave it a shot.

That said, I’ve encountered an annoyance or two, and in figuring out the solution to one of the biggest ones, I thought I’d do a which howto and share it for reference.

Continue reading

Anatomy of a .desktop File

One of the beautiful things about Linux is that developers tend to be conscientious about the use of technical standards. Freedesktop.org maintains a wide series of standards for X Window System desktops, which apply to Gnome, KDE, LXDE and XFCE (I’m not sure whether Fluxbox implements these standards.) The standard for “desktop entries” is still technically a draft, but is generally accepted by the larger X community.

The .desktop file fills two primary functions: first, it informs the desktop environment how the file is to be handled by the desktop environment with regard to menu placement, display, environmental variables, and similar. In this function, it resides globally in /usr/share/applications/ and for specific users in $HOME/.local/applications. The second function is the direct shortcut on the desktop itself. In this function, it resides in $HOME/Desktop. The same file fills both functions, so if you want to have an application both in the menu and on your desktop, you’ll need to put the .desktop file in two places. Let’s take a closer look, shall we?
Continue reading

Up Close and Personal with LXDE

Regular visitors to this site will know that Fluxbox is Trent’s and Patrick’s preferred window manager. I, too, am impressed with its speed and customizability, and its low overhead. Fluxbox’s biggest drawbacks are that customization is somewhat less intuitive and significantly more labor-intensive than the full-featured environments’, and that the interface as a whole is foreign and unintuitive to those whose only other computer experience has been Windows.
Continue reading

The first time I’ve ever been disappointed by Slackware

DISCLAIMER: Be prepared. There is whining ahead. I want to preface this by saying that I’m not interested in having a discussion about why I don’t gush with love over KDE 4, and I’m not particularly interested in suggestions for forcing it to work for me. This post is more about me wrapping my head around planning for how my use of Linux is going to change now that I’m going to have to re-think a lot of things about what has been my favorite Linux distro for years.

Why I’m disappointed

I guess I probably shouldn’t be too surprised, because I knew that Pat Volkerding has been working with my least favorite desktop environment and it’s been in /current for a while now.

But I guess a part of me still was holding out a childish hope that KDE4 was going to be included in /testing only, and that the default version of KDE for the Slackware 13.0 release would be KDE 3.5.10, the last decent release of that desktop environment. Given Patrick’s tendency to play it safe in regular Slackware releases and stick with only stable, fully-developed and thoroughly tested applications and desktop environments, I would have thought that something like KDE 4 — a desktop environment that’s still easily a year’s worth of hard development away from being a suitable replacement for KDE 3 — would be back-burnered in Slackware in favor of what is known to work and work well.

I probably shouldn’t be upset about this; it’s Linux… if I don’t like it, I can just make my own distro, right? If I want to spend the hours and hours it’ll take for that, sure. Well, I’m not to the point of making my own distro yet. But this does mean I’m going to have to significantly change my Linux usage, starting with replacing a bunch of stuff.

Continue reading