sry, but how do you put your mrxvt translucent blue, when e define the option mrxvt*transparent: true and !mrxvt*background: darkblue my mrxvt becomes light gray translucent… i don’t understand this… if you can explain me, it will be nice, thanks
The exclamation point “!” comments out the line it preceeds. The grey backgound is certainly the default color. Just remove the “!” and that should to it.
no, not works at all
You should check if there’s no other background color defined under your ~/.Xdefaults after the one you’ve uncommented.
no, i don’t have another background color defined, if you can show me your mrxvt config, to see were is the mistake, i apreciate,
thanks!
You got it on the first page of this thread: here.
It reminds me that I use the transparency from xcompmgr (composition). To get this, you have to turn the opacity option on. It’s like having transet automatically aplied when the term is started up.
Hi @ all,
impressed by PEM`s graet Theme (and all the other Themes and Configs here in the Forum) I started a little “Tour through FVWM” last Week.
As an 100% Noob in Fvwm Ive tasted a lot of Things from all the Themes here and based on "PEMs Stuff" I`ve created my new Fvwm-Desktop on my LFS-System.
The Result as temporary “Snapshot” is visible here:
PEM, dont be angry that Ive destroyed your Theme so much 
It`s a Product of “looking here and there”, Impressions from all the other Themes in the Forum
Now, after one week using fvwm I`m absolutly happy to find this Forum here and my head is full of other Things which will be tried out (things like a Mountscript for my Camera-Device or a Mailchecker and much more:)
O.K., thanks to all!
@Slackman:
Well, I’m not angry at all. On the contrary, I’ve found your results quite appealing. I like the crytal look it gaves on your screenshot.
Allow me one thing: IMHO, I think that you should create a different menu style for the pixmap menu than for the basic ones. That would avoid the little white line crawling all over the pixmap. Have a look at my menu.fvwm2rc for some details 
(Hey, that’s an LFS distribution, may be the best one around there!)
@ PEM,
thanks for the reply!
Yes, thats right, I have to create a different menu style, Ill try to do that the next days.
LFS: Im using LFS for 5 month now. And youre right, maybe its the best Distribution of them all :slight_smile: Fast, small, clean and everything works fine! Building/Installing takes a lot of time but then LFS is running perfectly! On the same machine Im using Slack (a graet Distribution too) but …I`m in love with my Linux from Scratch lol 
Greatings
I need some help with the weather, volume, and wifi deals. I can’t get the weather to work at all. I don’t have anything in /dev/shm and not sure how to set the permissions. My wifi is not wlan0 but ath0 and I changed that in the script but it just shows full strength all the time even when I take out my wireless card. The volume shows full strength all the time too even if the sound is down or off?
If you could help that would be great.
Thanks
For the WifiSensor don’t bother, this script is a fake. I’ve just let it there in case I would have the time to implement something. Currently, it only draws an animation when you click on it and deactivates it if you re-click on it 
Not what you expect, I guess. The thing is that the rest is easy to inplement but I’ve never take the time to do it. As a beginning, to get the ‘Quality level’ of your wifi interface and if you only got one wifi card, get its value is straightforward:
cat /proc/net/wireless | tail -n1 | awk {'print $3'}For the VolumeLevel, it’s even worst. I just lanch gnome-alsamixer when this script received a mouse click. On the other hand, implementing something here is a bit tricky because there’s no nice interface to get the master volume value. Fortunately, I got a script able to modify it and to get its current value. I use it on my laptop through special keyboard keys with the help of xbindkey and I make it display its current value on screen via xosd. Coupling it with VolumeLevel script should be not too difficult. Here’s the script that I call ~/.fvwm/script/volume.sh:
[code]#!/bin/sh
get_vol() {
amixer sget ‘PCM’,0 | grep “Front Left: Playback” |
sed -e ‘s/%/ /’ | sed -e ‘s/[//’ | awk {‘print $5’}
}
inc_vol() {
VOL=$[volume.sh get + 10]
amixer sset ‘PCM’,0 ${VOL}%,${VOL}% unmute
}
dec_vol() {
VOL=$[volume.sh get - 10]
amixer sset ‘PCM’,0 ${VOL}%,${VOL}% unmute
}
case “$1” in
‘get’) get_vol;;
‘inc’) inc_vol;;
‘dec’) dec_vol;;
esac[/code]
To get the master tone value just:
~/.fvwm/script/volume.sh getFor the weather, this time, it’s fully implemented (though some dudes would have prefer a more complete release… time is not on my side, buddies ). So, the first thing is to check on the command line if the first perl script, ~/.fvwm/script/weather_log.plx, is able to get its necessary values from weather.com. For that just launch it and give me its results so that I can have a look at them:
~/.fvwm/script/weather_log.plxThis is what I get form that weather
Can't locate LWP/Simple.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.4 /usr/local/share/perl/5.8.4 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /home/brandon/.fvwm/components/scripts/weather_log.plx line 3.
BEGIN failed--compilation aborted at /home/brandon/.fvwm/components/scripts/weather_log.plx line 3.
Thanks for the help
It seems that the module I use is missing. LWP stands for the World Wide Web library for PERL 
. This module is generally called libwww-perl and should be easy to found on any distribution. If you are a Gentoo user, just:
emerge libwww-perlok so now I am getting this
31.png
16ºC
20 %
32.png
32º/16ºC
0 %
32.png
33º/17ºC
20 %
32.png
31º/16ºC
20 %
32.png
29º/14ºC
0 %
32.png
30º/15ºC
20 %
32.png
30º/16ºC
20 %
32.png
31º/16ºC
0 %
34.png
29º/15ºC
0 %
32.png
30º/15ºC
0 %
am I suppose to create the weather.log in /dev/shm because there is nothing there?
Before anything else, check your right on /dev/shm with a simple:
echo "toto" > /dev/shm/toto.txtNext, just have a look to this post and this one. This should lead you to some nice results
Cool I got the weather going now thanks, but still a couple questions. Does that regenerate every so often or just when you log in?
And can I change that to Fare. instead of Celsius?
Thanks alot will work on what you said about the volume later but really thanks for all your help and the wifi would be a cool deal. Does the battery script with the icons work?
Actually, weather.com provides its forecasts in Farenheit (despite the fact that scientific measurements are done in Celsius 
). So, you just have to remove my little calculation and update the displayed unit. This should give you for weather_log.plx:
#!/usr/bin/perl
use strict;
use LWP::Simple;
my $content = get("http://www.w3.weather.com/weather/print/FRXX0076");
$content =~ s/.*<!-- begin loop -->(.*)<!-- end loop -->.*/$1/s;
my @day = split /<TR>/, $content;
shift @day;
my ($day, $date, $img, $temp, $precip);
my $tomorrow;
foreach $_ (@day) {
($day) = /(\w+)<\/A>/s;
($date) = /<BR> (.+?)</s;
($img) = /(\d+)\.gif/s;
$img = $ARGV[0] . $img . '.png';
($temp) = /<B>(.*?)<\/B>/s;
$temp =~ s/°/chr(186)/eg;
$temp =~ s|(\d+)|sprintf "%d", $1|eg;
($precip) = /(\d+ %)/;
print $img . "\n" . $temp . "F\n" . $precip . "\n";
}
To refresh your value, I suggest to add a call to this script in your crontab. IMHO, that’s surely the best place.
The BatteryState and bat.sh are complete scripts that relies on the /proc/acpi value: no need for any acpi daemon. In addition, I’ve used festival for speech synthesis so that it gives you some warning when levels are reached 8) To avoid the sound server issue, I’ve used esddsp as a mixing client for the esd sound server (aka Esound).
Thanks for all the help so far but I am trying to incorporate the battery deal into the topbar and The icon doesn’t show. I have festival installed and esound with esound client installed not sure what to do from here?
Your calculations seem OK: it should display at least the TopBar itself. One thing though, in the FvwmScript calls, (for BatteryState, VolumeLevel and WifiSensor), I’ve seen that the state 0 was never displayed properly (I mean the display of bat0.png, volume0.png, wifi0.png). This is due to the argument parsing done in the FvwmScripts To avoid this behavior, I’ve added a space between the icon for the 0 state and the closing parenthesis. In your code, an example is always better than a long speech:
$[PemDock]/bat0.png)must become:
$[PemDock]/bat0.png )Anyway, I don’t think it’s the source of your issue here. To create, modify and debug an FvwmScript, I like to use the FvwmConsole. Could you check these FvwmScripts in an FvwmConsole and report me back your results? Don’t forget to call the FvwmScripts with their appropriate arguments (the whole list of them is mandatory but it’s not as difficult as it seems: you can do a simple copy and paste via text selection and middle click button )
Thanks a lot man you are a genius I love this stuff I have the battery wokring now also. I had the path to script wrong. I will probably have more questions though later. Thanks so much.