SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm curious. What does fvwm do that can't be done by configuring any of the *boxes?
(None of the following may sound especially vital to some folks but these just illustrate a general configurability that applies to most everything.)
For some examples, it has a very precise focusing model - I can focus on mouse hover and raise on click but not raise on drag-to-copy clicks. It has a very precise window placement model that I can't replicate anywhere else - e.g., the openbox guys in #openbox acknowledged openbox couldn't do it and that one of their goals was to improve there, where it does a smart placement called 'MinOverlapPercentPlacement' as one of many possibilities. It can do remarkable things with functions and positioning things down to the pixel, such as
# EWMHBaseStruts doesn't apply to this (or the corner snaps), so I need a
# pixel border here.
+ I Raise
+ I Current (!HasPointer) WarpToWindow 100 100
+ I ThisWindow Piperead "echo Move $(( $[vp.width]/2-$[w.width]/2 ))p -1p Warp"
The '-1p' in the arithmetic expansion puts a raised window 1 pixel above the bottom center of my display and snaps the mouse to the bottom right corner if it wasn't already in the window area. (Don't worry - this sort of thing is rarely necessary if you don't want to be bothered with this sort of precision.)
For even more over-the-top things, I can position how far to the left or right from the parent menu a child menu opens. I can set the text and color and size of tooltips in the pager if there are any tooltips at all. You can choose if you want an 'alt-tab' sort of menu but can pick which button to bind it to, pick which apps are shown, pick what data is displayed with them (such as geometry and desk), and define a max width to the whole menu/widget. Etc. It's just very nearly infinitely configurable.
Also, some people go way out with using its ability to read arbitrary scripts or use arbitrary programs (Read, PipeRead configuration commands, etc.) to create pseudo-real-time thumbnails for their desktop (I use no desktop icons at all on my primary config) and create menus containing weather reports (sort of like conky-in-a-menu) and so on. The possibilities are nearly endless.
-- Oh, and I forgot to mention that you can use m4 or cpp as a preprocessor to your configuration, creating a sort of conditional compilation of your config. So, for instance, you could use the same config to create two very different configs based on whether you were on your desktop or your laptop or whatever.
I've just been researching it. It actually looks like you can make it do wonders. Some screenshots/themes on the fvwm official site if you google for it. Just a shame they don't provide a better default setup. It really does it a disservice IMO.
I decided to give KDE some more time, to see if it grew on me, and it never did. I prefer the programs and overall feel of GNOME. Xfce is second, for me. Using FreeBSD and building everything from ports, I settled on Xfce and then GNOME programs to go with it. I like GNOME and Xfce the most, I'm using GNOME right now (Ubuntu), I've been thinking about using GNOME with even FreeBSD, even though it takes a long time to build, and I can't vote twice, so I voted for GNOME.