[Solved] dwm status bar

I am learning about DWM...slowly...
So, I have conky piped to dzen2 as per the screenshot;
But how do I now remove the 'dwm-6.0' from the status bar?
Thanks for your patience.
Last edited by ancleessen4 (2013-04-13 11:05:17)

dzconky;
#!/bin/sh
FG='#aaaaaa'
BG='#333333'
FONT='-*-inconsolata-*-r-normal-*-*-90-*-*-*-*-iso8859-*'
conky | dzen2 -e - -h '14' -w '1100' -ta r -x '750' -fg $FG -bg $BG -fn $FONT &
conky;
out_to_console yes
#out_to_x no
background no
update_interval 2
total_run_times 0
use_spacer none
TEXT
#Arch 64 :: $kernel :: $uptime_short :: ^fg(\#60B48A)$mpd_smart ^fg():: ${cpu cpu1}% / ${cpu cpu2}% :: cpu0 ${execi 5 sensors | grep "Core 0" | cut -d "+" -f2 | cut -c1-2}C cpu1 ${execi 5 sensors | grep "Core 1" | cut -d "+" -f2 | cut -c1-2}C :: ^fg(\#DC8CC3)$memperc% ($mem) ^fg():: ${downspeed enp0s20} ${upspeed enp0s20} :: ${time %a %b %d %H:%M}
$kernel :: Updates: ${if_match ${execi 1800 (checkupdates | wc -l)} == 0}${color2}up to date${color}${else}${color3}${execi 1800 (checkupdates | wc -l)} new packages${color}${endif} :: ^fg(\#60B48A)$mpd_smart ^fg():: ^fg(\#DC8CC3)$memperc% = $mem ^fg():: ${time %H:%M} :: ^fg(\#8CD0D3)${execi 300 /home/neil/bin/weather.sh "EUR|LU|LU001|Luxembourg"}
I have tried changing '-x' and '-w' but no change to the layout...
Just tried to recompile with '-x=850'...to try and push dzen output to the right but no change...
makepkg -efi --skipinteg
I am sure this is a simple solution that I am missing...

Similar Messages

Greek letters in dwm status bar? How?

Is there a change in config.h that I could do to show Greek letters normally?
Thank you

Sorry..
The problem exists when Here is my config.h:
/* See LICENSE file for /* appearance */
static const char font[] static const char normbordercolor[] static const char normbgcolor[] static const char normfgcolor[] static const char selbordercolor[] static const char selbgcolor[] static const char selfgcolor[] static const unsigned int borderpx = 1; static const unsigned int snap static const Bool showbar static const Bool topbar /* tagging */
static const char *tags[] static const Rule rules[] = {
/* class instance title { "Gimp", NULL, /* { "Firefox", NULL, /* layout(s) */
static const float mfact static const int nmaster static const Bool resizehints static const Layout layouts[] = {
/* symbol arrange { "[]=", tile }, { "><>", { "[M]", /* key definitions */
#define MODKEY Mod4Mask
#define TAGKEYS(KEY,TAG) \
{ MODKEY, { MODKEY|ControlMask, { MODKEY|ShiftMask, { MODKEY|ControlMask|ShiftMask, KEY, /* helper for spawning #define SHCMD(cmd) { .v /* commands */
static const char *dmenucmd[] static const char *termcmd[] static const char *rebcmd[] static const char *shutcmd[] static const char *dwbcmd[] static Key keys[] = {
/* modifier { MODKEY, { MODKEY|ShiftMask, { MODKEY|ShiftMask, { MODKEY, { MODKEY, { MODKEY, { MODKEY, { MODKEY, { MODKEY, { MODKEY, { MODKEY, { MODKEY, { MODKEY|ShiftMask, { MODKEY, { MODKEY, { MODKEY, { MODKEY, { MODKEY|ShiftMask, { MODKEY, { MODKEY|ShiftMask, { MODKEY, { MODKEY, { MODKEY|ShiftMask, { MODKEY|ShiftMask, TAGKEYS( TAGKEYS( TAGKEYS( TAGKEYS( TAGKEYS( TAGKEYS( TAGKEYS( TAGKEYS( TAGKEYS( { MODKEY|ShiftMask, { MODKEY|ShiftMask, { MODKEY|ShiftMask, /* button definitions */
/* click can be ClkLtSymbol, static Button buttons[] = {
/* click event mask { ClkLtSymbol, 0, { ClkLtSymbol, 0, { ClkWinTitle, 0, { ClkStatusText, 0, { ClkClientWin, MODKEY, { ClkClientWin, MODKEY, { ClkClientWin, MODKEY, { ClkTagBar, 0, { ClkTagBar, 0, { ClkTagBar, MODKEY, { ClkTagBar, MODKEY, Last edited by hariskar I open a Greek web page in a browser. In dwm status bar the Greek characters of the title of the web page are not displayd correctly.
copyright and license details. */
= "-*-terminus-medium-r-*-*-16-*-*-*-*-*-*-*";
= "#444444";
= "#222222";
= "#bbbbbb";
= "#005577";
= "#005577";
= "#eeeeee";
/* border pixel of windows */
= 32; /* snap pixel */
= True; /* False means no bar */
= True; /* False means bottom bar */
= { "1", "2", "3", "4", "5", "6", "7", "8", "9" };
tags mask isfloating monitor */
NULL, 0, True, -1 },
NULL, 1 << 8, False, -1 },*/
= 0.55; /* factor of master area size [0.05..0.95] */
= 1; /* number of clients in master area */
= True; /* True means respect size hints in tiled resizals */
function */
/* first entry is default */
NULL }, /* no layout function means floating behavior */
monocle },
KEY, view, {.ui = 1 << TAG} }, \
KEY, toggleview, {.ui = 1 << TAG} }, \
KEY, tag, {.ui = 1 << TAG} }, \
toggletag, {.ui = 1 << TAG} },
shell commands in the pre dwm-5.0 fashion */
= (const char*[]){ "/bin/sh", "-c", cmd, NULL } }
= { "dmenu_run", "-fn", font, "-nb", normbgcolor, "-nf", normfgcolor, "-sb", selbgcolor, "-sf", selfgcolor, NULL };
= { "st", NULL };
= { "systemctl", "reboot", NULL };
= { "systemctl", "poweroff", NULL };
= { "dwb", NULL };
key function argument */
XK_p, spawn, {.v = dmenucmd } },
XK_Return, spawn, {.v = termcmd } },
XK_d, spawn, {.v = dwbcmd } },
XK_b, togglebar, {0} },
XK_j, focusstack, {.i = +1 } },
XK_k, focusstack, {.i = -1 } },
XK_i, incnmaster, {.i = +1 } },
XK_d, incnmaster, {.i = -1 } },
XK_h, setmfact, {.f = -0.05} },
XK_l, setmfact, {.f = +0.05} },
XK_Return, zoom, {0} },
XK_Tab, view, {0} },
XK_c, killclient, {0} },
XK_t, setlayout, {.v = &layouts[0]} },
XK_f, setlayout, {.v = &layouts[1]} },
XK_m, setlayout, {.v = &layouts[2]} },
XK_space, setlayout, {0} },
XK_space, togglefloating, {0} },
XK_0, view, {.ui = ~0 } },
XK_0, tag, {.ui = ~0 } },
XK_comma, focusmon, {.i = -1 } },
XK_period, focusmon, {.i = +1 } },
XK_comma, tagmon, {.i = -1 } },
XK_period, tagmon, {.i = +1 } },
XK_1, 0)
XK_2, 1)
XK_3, 2)
XK_4, 3)
XK_5, 4)
XK_6, 5)
XK_7, 6)
XK_8, 7)
XK_9, 8)
XK_q, quit, {0} },
XK_r, spawn, {.v = rebcmd } },
XK_s, spawn, {.v = shutcmd } },
ClkStatusText, ClkWinTitle, ClkClientWin, or ClkRootWin */
button function argument */
Button1, setlayout, {0} },
Button3, setlayout, {.v = &layouts[2]} },
Button2, zoom, {0} },
Button2, spawn, {.v = termcmd } },
Button1, movemouse, {0} },
Button2, togglefloating, {0} },
Button3, resizemouse, {0} },
Button1, view, {0} },
Button3, toggleview, {0} },
Button1, tag, {0} },
Button3, toggletag, {0} },
(2013-10-02 13:46:57)

Dstatus - dwm status bar

Hey guys,
for quite some time I've been working on dstatus for my own desktop. To share and improve dstatus I'd like to introduce it to the ArchLinux community now. dstatus is a small but expandable status application designed for use with dwm. While it certainly doesn't fit the suckless approach due to its use of plugins it now works rather nice.
Features:
- dstatus features a plugin system. This makes it easy to add new plugins that add information not accessible right now.
- dstatus features groups. Groups bind together parts of your status line. If a dynamic part of that group becomes undisplayable (muted volume for example) the whole group will be hidden.
- dstatus' format can be configured via config.h. It's syntax is described in the project's README.
- dstatus' plugins can be configured via config.mk. It enables to exclude certain plugins from compilation and installation
Currently there aren't many plugins, just some basic stuff for time, volume, mpd and battery. I'd be happy to accept contributions for new plugins.
If you're interested compile and try this small application and provide some feedback. The project can be found at Bitbucket.
Here's a link to the dstatus AUR package.
Regards,
Patrick
Last edited by pks (2013-06-06 17:15:03)

mauritiusdadd wrote:
derrickcope wrote:What I am asking is shouldn't it be able to do it already without patching? Bash can output color so why do I have to patch?
No. Bash can show colours because it can parse and interpret the escape sequences. Dwm code lacks of that feature and for this reason you have to apply a patch.
Thanks, that's what I was asking. If xsetroot -name can accept bash sequences then wouldn't it be simple just to use this to show color. @jasonwryan is right, I do need to read up more on dwm. Since I am in China it is problematic to search for things on the web even with a vpn and the suckless website is sparse on infomation.
Seems that this would be the easiest way to add color to the status bar but maybe "xsetroot -name" doesn't output in color even though it does have "-fg -bg" switches.

[SOLVED] dwm-status.sh, possible to include scripts within the script?

I have 'dwm-status.sh' printing some basic info (mpd, vol, date) into the status bar. Is it possible to make it include eg. gmail, weather, and battery scripts in a similar way that conky would? (execpi 60 python ~/.scripts/gmail.py)
Also, off topic: How can I see which other special characters represent which icons in Ohsnap font? e.g. "Ñ" "Î" "¨" "¹" "ê" "í" "È represent cpu, memory, hdd, vol, clock.... how about the rest?
dwm-status.sh:
#!/bin/sh
icons=("Ñ" "Î" "¨" "¹" "ê" "í" "È")
getMusic() {
msc="$(ncmpcpp --now-playing '{%a - %t}|{%f}')"
if [ ! $msc ]; then
echo -ne "\x0A${icons[4]}\x01 music off"
else
echo -ne "\x0A${icons[4]}\x01 ${msc}"
fi
getVolume() {
vol="$(amixer get Master | egrep -o "[0-9]+%" | head -1 | egrep -o "[0-9]*")"
echo -ne "\x0A${icons[5]}\x01 ${vol}"
getDate() {
dte="$(date '+%b %d %a')"
echo -ne "\x0A${icons[1]}\x01 ${dte}"
getTime() {
tme="$(date '+ %H:%M')"
echo -ne "\x0A${icons[6]}\x01 ${tme}"
while true; do
xsetroot -name "$(getMusic) $(getVolume) $(getDate) $(getTime)"
sleep 1
done
Last edited by Winston-Wolfe (2013-06-26 13:10:11)

Thanks guys, I've managed to get my notification scripts printing by simply not using execpi:
getMail() {
mai="$(~/.scripts/gmail.py)"
echo -ne "\x0A${icons[3]}\x01 ${mai}"
But like you said, I now have a calling frequency challenge.
Trilby, that looks great. I've got it partially working, but I'm at a loss on how to go about printing the variables in the loop for those blocks that happen periodically.
otherwise your email indicator (for example) will only pop up for one second every 5 minutes.
^ exactly what's currently happening.
Is there something that just prints the variable without calling for an update like $(getMail) does that I could put into the loop?
let loop=0
while true; do
# stuff that happens every second here
xsetroot -name "$(getMusic) $(getVolume) $(getDate) $(getTime)"
if [[ $loop%60 -eq 0 ]]; then
#stuff that happens every minute here
xsetroot -name "$(getMusic) $(getMail) $(getVolume) $(getDate) $(getTime)"
fi
if [[ $loop%300 -eq 0 ]]; then
# stuff that happens every 5 minutes here
xsetroot -name "$(getMusic) $(getMail) $(getWeather) $(getVolume) $(getDate) $(getTime)"
let loop=0 #this prevents an eventual overflow
fi
let loop=$loop+1
sleep 1
done
Last edited by Winston-Wolfe (2013-06-26 08:54:47)

DWM status bar

Why doesn't this show color status in the dwm bar?
red="echo -e \033[34;41mColor Text\033[0m"
xsetroot -name $red
Is my code wrong? or is DWM or Xsetroot removing the color?
Last edited by derrickcope (2015-05-04 04:09:49)

mauritiusdadd wrote:
derrickcope wrote:What I am asking is shouldn't it be able to do it already without patching? Bash can output color so why do I have to patch?
No. Bash can show colours because it can parse and interpret the escape sequences. Dwm code lacks of that feature and for this reason you have to apply a patch.
Thanks, that's what I was asking. If xsetroot -name can accept bash sequences then wouldn't it be simple just to use this to show color. @jasonwryan is right, I do need to read up more on dwm. Since I am in China it is problematic to search for things on the web even with a vpn and the suckless website is sparse on infomation.
Seems that this would be the easiest way to add color to the status bar but maybe "xsetroot -name" doesn't output in color even though it does have "-fg -bg" switches.

[SOLVED] Problem with adding package update count to dwm's status bar

Following http://www.andreascarpino.it/blog/posts … s-part-ii/, I added:
$ crontab -l
*/10 * * * * ~/bin/tempdb
Along with
#!/bin/bash
# ~/bin/tempdb
fakedb=/dev/shm/fakepacdb
realdb=/var/lib/pacman
[[ ! -d $fakedb ]] && { mkdir -p "$fakedb/sync" || exit 1; }
[[ ! -L $fakedb/local ]] && { ln -s "$realdb/local" "$fakedb" || exit 2; }
exec fakeroot pacman --dbpath "$fakedb" -Sy
pkgs=$(pacman --dbpath "$fakedb" -Qqu | wc -l)
aurpkgs=$(cower -udf 2> /dev/null | wc -l)
unset msg1
unset msg2
unset packages
msg1="pacman: 0"
msg2="aur: 0"
if [[ ${pkgs} -gt 0 ]]; then
msg1="pacman: ${pkgs}"
fi
if [[ ${aurpkgs} -gt 0 ]]; then
msg2="aur: ${aurpkgs}"
fi
updb="UPDB: ${msg1}, ${msg2}"
export updb
The problems is with being able to export the variable updb, because exporting only exports to subshells. I also have my ~/bin/dwmstatus script:
#!/bin/bash
sep=" | "
volsep="VOL"
datesep="DATE"
timesep="TIME"
vol=$(amixer get Master | tail -1 | sed 's/.*\[$[0-9]*%$\].*/\1/')
volstat=$(amixer get Master | tail -n 1 | cut -d' ' -f 8-)
sdate=$(date +"%B %d")
stime=$(date +"%r")
if [[ ${volstat} == "[off]" ]];
then
vol="--%"
fi
out="${updb} ${sep} ${volsep} ${vol} ${sep} ${datesep} ${sdate} ${sep} ${timesep} ${stime}"
xsetroot -name "${out}"
I only want the checking of updates to occur every few minutes (for now I tried 10), and just using the exported variable that contains the whole
"UPDB: pacman:3, aur:1",..
I'm not exactly sure how to fix my hacked-together scripts. When I simply run the tempdb script, it doesn't do much exept for updating to the fake database, but being able to use the updb variable has not worked yet. I also tried sourcing the script, but that just quits urxvt when running in dwm, and it logs me out when sourcing from plain X.
I guess my main question is: what is the best way to show updates from the dwm status bar, or how can I fix what I am trying to do now?
Last edited by wolfcore (2012-03-17 00:21:47)

jasonwryan wrote:
I use this:
crontab -e
@hourly /home/jason/Scripts/checkupdates
grep ups Scripts/dwm-status
ups(){
ups="$(/tmp/aurupdates | wc -l)"
if [ $ups = 0 ]; then
echo "0"
else echo -en "$ups"
fi
Script is keenerd's from here: http://www.mail-archive.com/pacman-dev@ … 08405.html
Okay, I see it. But your ups() function checks /tmp/aurupdates; how do you check for AUR updates? I looked at your repos, and saw
pac()
pup="$(pacman -Qqu --dbpath /tmp/checkup-db-jason/ | wc -l)"
if [ $pup == 0 ]; then
echo "0"
else
echo -en "\x05$pup\x01"
fi
This is what you use along with keenerd's checkupdates, right?

Dstatus: Yet another status bar for dwm

I decided to fix up my custom dwm status bar that I've hacked on for awhile into something a bit more presentable. Therefore, I give you dstatus!
So what makes this different from the rest? For starters, it's somewhat laptop specific. Things like battery, backlight, and possibly SSID aren't of much use to a desktop. However, these bits can be turned off at compile time if you don't want them. In fact, all the elements can be toggled and rearranged however you like it.
In addition, the main loop polls as little as necessary; just time, cpu usage, and battery are polled. Other elements are updated by threads listening to events.
Configuration:
config.mk defines which elements will be compiled into the binary. Turn any of them off by commenting out the appropriate line.
config.h defines the look of everything. Elements can be formatted (in a limited fashion) according to printf. Some elements can display either a percentage or a bar.
I've also provided an AUR package.
The source is UNLICENSED so feel free to hack away. :-)

Thanks @jasonwryan, I just don't know where to post it

[SOLVED] dwm + dzen2 + conky-cli misconfigured

I have been trying to pipe conky status to dzen2 and it is doing my head in.
My .xinitrc
#!/bin/sh
# ~/.xinitrc
setxkbmap -option terminate:ctrl_alt_bksp &
eval `cat ~/.fehbg` &
numlockx &
xscreensaver -no-splash &
# Dzen & conky
conky | dzen2 -fg '#dcdcdc' -bg '#3f3f3f' -ta r -fn '-*-terminus-*-r-normal-*-*-120-*-*-*-*-iso8859-*' &
# Start dwm
exec ck-launch-session ~/Scripts/dwm-start
.conkyrc
background no
out_to_console yes
update_interval 2
total_run_times 0
use_spacer none
double_buffer yes
TEXT
${if_existing /sys/class/power_supply/BAT0/present}^fg(#999999)BAT^fg()${battery_percent}%${else}AC${endif} * CPU ${cpu cpu1}% RAM ${memperc}% * / ${fs_used_perc /}% /home ${fs_used_perc /home}% * PKG ${execpi 900 ~/Scripts/pacman-up.pl} * ${if_existing /proc/net/route ra0}Down ${downspeedf ra0}K/s Up ${upspeedf ra0}K/s ${else} ${if_existing /proc/net/route eth0} Down ${downspeedf ra0}K/s Up ${upspeedf ra0}K/s${endif} ${endif}* ${time %I:%M%P}
Start dwm script
conky | while read line; do
xsetroot -name "$line";
done | while true; do
dwm > /dev/null; done;
Could anyone point me at what I am doing wrong? I have tried following examples in the forums, including this one and this one -- but I either end up with dwm 5.7.2 in the corner, or conky prints out the ^fg etc...
Any help would be appreciated at this point...
Last edited by jasonwryan (2009-11-20 06:11:51)

Thanks for the suggestions Skanky. The broken line in conky was a copy/paste error into the browser - it is a single line conky (I've edited the OP to reflect that).
I think it is a problem with the way conky-cli and dzen work together. If I run:
echo "testing" | dzen2 -fg '#dcdcdc' -bg '#3f3f3f' -ta r -fn '-*-terminus-*-r-normal-*-*-120-*-*-*-*-iso8859-*' -p
it prints as expected.
Similarly, if I comment the conky | dzen2 line in .xinintrc and just run conky-cli from the start script it works...
Trying to get then to work together, however, is another matter.
/edit
Some progress: it seems that it is being drawn - if I Mod-Shift-q the dwm status bar briefly disappears and I can see conky momentarily. I tried starting conky | dzen2 after dwm but that didn't work.
I have also added some options, which seem to have helped, my .xinintrc entry now looks like:
conky | dzen2 -x '500' -e '' -fg '#dcdcdc' -bg '#3f3f3f' -ta r -fn '-*-terminus-*-r-normal-*-*-120-*-*-*-*-iso8859-*' -p &
Last edited by jasonwryan (2009-11-19 16:57:13)

[SOLVED]Gnome: No network icon in the status bar

So fresh install and no networking icon in the status bar.
I also opened the network connections program and it didnt show any connections. I am using eth0 to write this.
This suggests to me that a daemon hasnt been started (but doesnt necessarily explain no icon in status bar)
here is the daemon section of my rc.conf
DAEMONS=(hwclock syslog-ng network netfs crond networkmanager dbus gdm)
i added network manager as a previous attempt (on advise of someone elsewhere on the internet(cannot remember where lol))
Thanks.. I have nearly got my system how I want it (minus software i havent installed yet)
Sorry if i have created a duplicate thread
Last edited by olig1905 (2012-01-21 17:33:47)

Thanks to both of you.
I had already noticed the redundancy of network which was added in the install however hadnt considered the ordering
wonder wrote:Did you really read the wiki?
This is pretty much all i have seen people saying at the end of their posts on here. I agree with the point you have made, however i have been on the wiki all day, conisdering this is a newbie forum it is to be presumed that it is a pretty new installation. Therefore the user does not have time to read the entire wiki. As i said i have been on the wiki all day and used it countless times and have found it invaluable, so im only posting here when i am unable to find answers there.
That aside this is a wonderfully helpful community so HI

[SOLVED] Vimperator 2.0 CSS file to colorize the status bar

With Vimperator's new stable release of 2.0, the old CSS file that controls the status line doesn't work anymore.
I had a lot of trouble fixing it. I looked up the names of a lot of items and converted the old scheme. That wasn't enough, so I copied the default css into my css file (at the top) and changed everything in there too.
Now I have a css file that is huge and has lots of duplicate data. It also has a white line between status bar and command line that I can't get rid of, and when you enter a : command the : is black on white, instead of red on gray like the rest of the line (there must be more items, I think I used an old CSS scheme (there wasn't one in the trunk)).
Anyway, I wonder if this can be made simpler and it'd be awesome if the missing stuff above can be added too. And hopefully someone can benefit of the below CSS anyway.
What it does: make the background light gray, give the status (top) line a dark gray top border, give status bar regular weight black text, and the command bar bold red text.
#liberator-completions {
-moz-user-focus: ignore;
overflow: -moz-scrollbars-none !important; /* does not seem to work fully */
border-width: 0px !important;
/*-moz-appearance: none !important; /* prevent an ugly 3D border */
margin: 0px !important;
padding: 0px !important;
/* the selected item in listboxes is hardly readable without this */
#liberator-completion > listitem[selected="true"] > listcell,
#liberator-bufferwindow > listitem[selected="true"] > listcell,
#liberator-previewwindow > listitem[selected="true"] > listcell {
color: black !important;
background-color: rgb(230,230,230) !important;
margin: 0px !important;
padding: 0px !important;
/* fixes the min-height: 22px from firefox */
#status-bar, statusbarpanel {
-moz-appearance: none !important;
min-height: 18px !important;
border: none !important;
font-weight: bold;
font-family: monospace;
margin: 0px !important;
padding: 0px !important;
background-color: rgb(230,230,230) !important;
color: black !important;
#status-bar
border-top: thin solid rgb(100,100,100) !important;
#liberator-statusline {
font-family: monospace;
margin: 0px !important;
padding: 0px !important;
background-color: rgb(230,230,230) !important;
#liberator-statusline > label {
margin: 0px 5px 0px 5px !important;
padding: 0px !important;
background-color: rgb(230,230,230) !important;
#liberator-statusline > label:first-child {
margin: 0px 5px 0px 5px !important;
padding: 0px !important;
background-color: rgb(230,230,230) !important;
#liberator-statusline-field-url {
color: black;
background-color: rgb(230,230,230) !important;
margin: 0px !important;
padding: 0px !important;
/* no longer at the window's bottom right corner */
.statusbar-resizerpanel {
display: none;
margin: 0px !important;
padding: 0px !important;
background-color: rgb(230,230,230) !important;
#statusbar-display, #statusbar-progresspanel {
display: none;
margin: 0px !important;
padding: 0px !important;
background-color: rgb(230,230,230) !important;
#liberator-commandline {
margin: 0px !important;
padding: 0px !important;
font-family: monospace;
background-color: rgb(230,230,230) !important;
color: red !important;
#liberator-commandline-prompt {
margin: 0px !important;
padding: 0px !important;
background-color: rgb(230,230,230) !important;
color: red !important;
#liberator-commandline-command {
background-color: rgb(230,230,230) !important;
color: red !important;
margin: 0px !important;
padding: 0px !important;
#liberator-visualbell {
border: none;
margin: 0px !important;
padding: 0px !important;
background-color: rgb(230,230,230) !important;
color: red !important;
#sidebar {
max-width: 90% !important;
min-width: 10% !important;
margin: 0px !important;
padding: 0px !important;
background-color: rgb(230,230,230) !important;
/* highlight groups */
.hl-Normal {
background-color: rgb(230,230,230) !important;
color: black;
margin: 0px !important;
padding: 0px !important;
.hl-ErrorMsg {
background-color: red;
color: black;
font-weight: bold;
margin: 0px !important;
padding: 0px !important;
.hl-InfoMsg {
background-color: rgb(230,230,230) !important;
color: magenta;
margin: 0px !important;
padding: 0px !important;
.hl-ModeMsg {
background-color: rgb(230,230,230) !important;
color: black;
margin: 0px !important;
padding: 0px !important;
.hl-MoreMsg {
background-color: rgb(230,230,230) !important;
color: green;
margin: 0px !important;
padding: 0px !important;
.hl-Question {
background-color: rgb(230,230,230) !important;
color: green;
margin: 0px !important;
padding: 0px !important;
.hl-Title {
background-color: rgb(230,230,230) !important;
color: magenta;
margin: 0px !important;
padding: 0px !important;
font-weight: bold;
.hl-Warning {
background-color: rgb(230,230,230) !important;
color: red;
margin: 0px !important;
padding: 0px !important;
.hl-StatusLine {
background: none !important;
background-color: rgb(230,230,230) !important;
color: white !important;
margin: 0px !important;
padding: 0px !important;
.hl-StatusLineSecure {
background: none !important;
background-color: #B0FF00 !important; /* light green */
color: black !important;
margin: 0px !important;
padding: 0px !important;
.hl-StatusLineBroken {
background: none !important;
background-color: #FF6060 !important; /* light red */
color: black !important;
margin: 0px !important;
padding: 0px !important;
.hl-URL {
background-color: rgb(230,230,230) !important;
color: green;
text-decoration: none;
margin: 0px !important;
padding: 0px !important;
/* NOTE: .aClass:hover not supported in quirks mode: http://developer.mozilla.org/en/docs/Mozilla_Quirks_Mode_Behavior */
a.hl-URL:hover {
text-decoration: underline;
cursor: pointer;
margin: 0px !important;
padding: 0px !important;
#liberator-completions, #liberator-multiline-output {
overflow: hidden;
background-color: rgb(230,230,230) !important;
color: black;
margin: 0px !important;
padding: 0px !important;
#liberator-completions-content, #liberator-multiline-output-content {
white-space: pre;
font-family: -moz-fixed;
margin: 0px !important;
padding: 0px !important;
background-color: rgb(230,230,230) !important;
#liberator-completions-content *, #liberator-multiline-output-content * {
font: inherit;
margin: 0px !important;
padding: 0px !important;
background-color: rgb(230,230,230) !important;
/*#liberator-commandline-prompt,#liberator-commandline,#liberator-commandline-command,#liberator-message */
/*, #liberator-message,#liberator-container,#liberator-bufferwindow, #liberator-completion, #liberator-previewwindow */
#liberator-container
background: none !important;
background-color: rgb(230,230,230) !important;
-moz-appearance: none !important;
margin: 0px !important;
padding: 0px !important;
#liberator-commandline, #liberator-commandline-prompt, #liberator-commandline-command, #liberator-message,
#liberator-commandline *, #liberator-commandline-prompt *, #liberator-commandline-command *, #liberator-message *
background: None !important;
background-color: rgb(230,230,230) !important;
color: rgb(255,44,44) !important;
padding: 0px !important;
margin: 0px !important;
font-weight: bold !important;
border: none !important;
#liberator-statusline-field-inputbuffer,#liberator-statusline-field-progress,#liberator-statusline-field-tabcount,#liberator-statusline-field-bufferposition,#liberator-statusline,
#liberator-statusline-field-inputbuffer *,#liberator-statusline-field-progress *,#liberator-statusline-field-tabcount *,#liberator-statusline-field-bufferposition *,#liberator-statusline *
background: none !important;
background-color: rgb(230,230,230) !important;
color: black !important;
font-weight: normal !important;
margin: 0px !important;
padding: 0px !important;
#liberator-statusline
background: none !important;
background-color: rgb(230,230,230) !important;
color: black !important;
font-weight: normal !important;
margin: 0px !important;
padding: 0px !important;
.hl-StatusLine
background-color: rgb(230,230,230) !important;
margin: 0px !important;
padding: 0px !important;
Last edited by Procyon (2009-04-04 22:45:25)

@anrxc: I see, thanks!
I didn't notice any speed difference between 2.0 and 1.2.
Here is the colorscheme I used to get the same effect as above, everything works now:
I changed some unrelated things and it gave some warning so I commented those out.
" ==Vimperator_Color_Scheme==
" name: my
" ==Defult_Colorscheme_Settings==
hi Bell border: 0 none; background-color: black;
hi Boolean color: red;
hi CmdLine font-family: monospace; padding: 0px;
hi CmdOutput white-space: pre;
hi CompDesc color: black; width: 50%;
"hi CompGroup
"hi CompGroup:not(:first-of-type) margin-top: 0px; "margin-top: .5em;
hi CompIcon width: 16px; min-width: 16px; display: inline-block; margin-right: .5ex;
hi CompIcon>img max-width: 16px; max-height: 16px; vertical-align: middle;
"hi CompItem
"hi CompItem>* padding: 0 0; ".5ex;
"hi CompItem[selected] background: yellow;
hi CompLess text-align: center; height: 0; line-height: .5ex; padding-top: 1ex;
hi CompLess::after content: "3" /* Unicode up arrowhead */
hi CompMore text-align: center; height: .5ex; line-height: .5ex; margin-bottom: -.5ex;
hi CompMore::after content: "4" /* Unicode down arrowhead */
hi CompMsg font-style: italic; margin-left: 16px;
hi CompResult width: 45%; overfloaw: hidden;
hi CompTitle color: magenta; background: white; font-weight: bold;
hi CompTitle>* padding: 0 .5ex;
hi ErrorMsg color: white; background: red; font-weight: bold;
hi Filter font-weight: bold;
hi FrameIndicator background-color: red; opacity: 0.5; z-index: 999; position: fixed; top: 0; bottom: 0; left: 0; right: 0;
hi Function color: navy;
hi Gradient height: 1px; margin-bottom: -1px; margin-top: -1px;
hi GradientLeft background-color: magenta;
hi GradientRight background-color: white;
hi Hint font-family: monospace; font-size: 10px; font-weight: bold; color: white; background-color: red; border-color: ButtonShadow; border-width: 0px; border-style: solid; padding 0px 1px 0px 1px;
hi Hint::after content: attr(number);
hi HintActive background: #88FF00; color: black;
hi HintElem background-color: yellow; color: black;
hi HintImage opacity: .5;
hi Indicator color: blue;
hi InfoMsg color: rgb(255,44,44); background: rgb(230,230,230); font-weight: bold;
hi LineNr color: orange; background: rgb(230,230,230);
hi Message white-space: normal; min-width: 100%; padding-left: 2em; text-indent: -2em; display: block;
hi ModeMsg color: rgb(255,44,44); background: rgb(230,230,230); font-weight: bold;
hi MoreMsg color: green; background: rgb(230,230,230);
hi NonText color: blue; min-height: 16px; padding-left: 2px;
hi Normal color: rgb(255,44,44); background: rgb(230,230,230); font-weight: bold;
hi Null color: blue;
hi Number color: blue;
hi Object color: maroon;
hi Preview color: gray;
hi Question color: green; background: rgb(230,230,230); font-weight: bold;
hi Search font-size: inherit; padding: 0; color: blue; background-color: rgb(230,230,230); padding: 0;
hi StatusLine color: black; background: rgb(230,230,230); border-top: thin solid rgb(100,100,100); border-width: 1px; font-weight: normal;
hi StatusLineBroken color: black; background: #FF6060; /* light-red */
hi StatusLineSecure color: black; background: #B0FF00; /* light-green */
hi String color: green;
"hi TabClose
"hi TabIcon
"hi TabIconNumber font-weight: normal; color: black; text-align: center; text-shadow: black -1px 0 1px, black 0 1px 1px, black 1px 0 1px, black 0 -1px 1px;
hi TabNumber font-weight: bold; margin: 0; padding-right: .3ex;
"hi TabText
hi Tag color: blue;
hi Title color: magenta; background: white; font-weight: bold;
hi URL text-decoration: none; color: green; background: inherit;
hi URL:hover text-decoration: underline; cursor: pointer;
hi WarningMsg color: red; background: white;

[SOLVED] dwm config

[SOLVED]
Hi,
I am asking for help with my dwm config. What I want it to do is, instead of snapping directly to the edge of the screen, I want it to snap a certain distance away from it (and maybe other windows). Can someone point me in the right direction?
Also, this is less relevant, but I want to include the system time in the title bar of dwm. Any help there?
Last edited by latenitekid (2013-03-12 00:43:30)

The time is included in the example status bar on the wiki page: https://wiki.archlinux.org/index.php/Dw … _statusbar
The snapping thing sounds like a variant of useless gaps...

The status bar on my Palm TX no longer is working

The status bar on my Palm TX no longer is functional with the stylus. I have tried realigning the screen with the Pref/Touchscreen app; doing soft resets; and doing hard resets. I have, also, removed the screen protector. All with the same result: The status bar will not function. Any suggestions of how I can try to repair it myself.
Post relates to: Tungsten TX
Post relates to: Tungsten T

Is it just the status bar only, or the bottom of the screen? Are all the icons present, or have some disappeared? There are some files for the T3 only that will remove some of the icons from the TX. You might try searching for AppSlipRotate.prc, and StatusBarLib.prc on your device. If present, delete them!
It also sounds like your digitizer might be failing. Repairs at fair prices can be found at usedpdaparts.com and directfix.com.
WyreNut
I am a Volunteer here, not employed by HP.
You too can become an HP Expert! Details HERE!
If my post has helped you, click the Kudos Thumbs up!
If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

Weird message below status bar - icons move down and almost touch dock

Ever since installing 3.0 on my 3g iphone I've had a weird problem. Roughly around an hour or so after the phone is on, the icons on the page move down (about an 1/8 of an inch) and the words "Revisar ADN" appear below the status bar. A little bit later the message will go away but the icons will remain shifted down. The only way to fix it is to turn the phone off and back on again, but again, roughly an hour later it happens again.
I have restored several times but to no avail.
Some more info about the situation: I purchased and activated the phone in Guatemala (where I live) and my carrier is Claro. The words "revisar ADN" mean "check DNA" in english. The phone is not jailbroken or anything like that. Even though the carrier is Claro, the international settings are in English with the exception of the spanish language added to the keyboard. I've had the phone for about 6 months and on 2.2.1 never got this message.
Any help would be appreciated.

Thanks so much for the information and the investigation on this (I saw you posting in other forums as well). Through some trial and error I think things are working finally. Here is the story for anyone else that might suffer from the same problem.
I originally tried the SIM trick and took the SIM out, put it into another phone, added a contact, and then put the SIM back in. This unfortunately did not work. A few hours later the icons had moved again. I then noticed that the contact that I had added to the SIM was not in my iphone address book, so I imported the contacts from the SIM (Settings>Mail, Contact, Calendars>Import Sim Contact), hoping that this would fix the problem. That didn't work either. I turned the phone off and on again, and that didn't work either.
Then I began to look into the "Claro Contactos" issue, and went looking for the SIM Applications (Settings>Phone). Now, I am almost positive that when I looked here earlier that day the SIM Applications button was not there. Maybe it was, but I'm thinking that by putting the chip into another phone and then putting it back into the iphone, this "unlocked" this feature. Or maybe it was the simple act of taking it out and putting it back in. Either way it was there now. I had never heard (or turned on) Claro Contactos so I went hunting for where to turn it off. After finding it "Utilidades Claro" it popped up a message asking if I wanted to turn it on. Obviously I had not used the feature before so I couldn't turn it off like the previous post had suggested. So I did the opposite and turned it on. I then touched the button "Respaldo Contactos" to back up that one contact to this service and then touched the button "Respaldo Automatico" and told it NOT to back up automatically. After doing all of this, I turned the phone off and on again, and now everything has been fine. It's been a full day and my icons are right where they should be.
I mention the process because I'm not totally convinced that just by turning the Claro Contactos on was the issue. I think the whole process is the solution. Maybe someone else that has the same issue can try the process, but backwards and see if just switching the Claro Contactos on (or off) solves the problem.
Thanks for the help and I hope this helps whoever else might have the same problem.

Form path in call_form and compilation error and status bar.

Dear all,
what should be the path in the call_form?
my forms (developed in form 6i) give error when i run it in forms 9i. i have already compiled. with the form 9i.
the status bar is invisible when running in the browser.
i am new to developer 9i.
thanks
Muhammad Nadeem

Hi:
When you call the forms in the subdirectories, you need to use the full path. Example:
CALL_FORM('c:\forms\D1\some_form');
Of course, you realize that this makes your forms less portable and could in the future cause more problems than it solves. Is there any reason you cannot just keep all your forms in one directory and possibly use a prefix to manage them if they belong to different sub-applications?
Thomas

Pages 5.0 - Status bar current page & page count?

How do I show the status bar showing current page and page count? I do not need to see the full thumbnail bar.
In all prior versions of pages, I could look at the bottom of my window and see my current page and how many pages are in my document. Now, I glance to the bottom, and I have no idea. I cannot find any way to turn this on and turning on the thumbnails view does not show this to me at-a-glance because I have to scroll all the way down (through documents hundreds of pages long) to find out how many pages I currently have.
Please, what am I missing here, how can I make this show up again?
I mean a quick display here, not adding the page count and numbers to a documents footer. Although, that would be one way for me to solve this issue, but I do not always want that.

I wrote a short AppleScript solution that informs about the current document page as a pop-up dialog. This is for Pages v5+ only. I created and saved an Automator Application named CurrentPage to my Desktop. Providing that Pages is running, it will produce the dialog shown in subsequent Automator screen shot.
Double-click /Applications/Automator and choose New Document, Application, and Choose. Follow the Utilities > Run AppleScript (not Shell Script as shown), and drag Run AppleScript over into the larger window and drop it. Select all of its contents and remove them -- this is just boilerplate.
Copy and paste the following AppleScript into the now vacant Run AppleScript workflow window. Click the hammer, and File > Save... pick a name, and location to save the application where it is handy. Quit Automator.
Code:
-- P
-- Produce formatted dialog of document name, current page, and page count
-- Pages v5+ only. Works whether typing in document or scrolling pages.
-- VikingOSX, June 2014, Apple Support Community - Pages for Mac.
if not ApplicationIsRunning("Pages") then
display dialog "Pages must be running to use this utility."
return quit
end if
tell application "Pages"
activate
tell front document
set diagTitle to "Current Document Page"
set docName to (name as text)
set thePage to current page
set curPage to 0
set pageCnt to page count
set pnList to its page
repeat with ndx from 1 to count of pnList
if thePage is equal to item ndx of pnList then
set curPage to ndx
end if
end repeat
set vformat to "Document: " & tab & tab & docName & return ¬
& "Current Page: " & tab & curPage & return ¬
& "Total Pages: " & tab & tab & pageCnt
end tell
end tell
display dialog (vformat as text) giving up after 15 with title diagTitle
on ApplicationIsRunning(appName)
tell application "System Events" to set appNameIsRunning to exists (processes where name is appName)
return appNameIsRunning
end ApplicationIsRunning

[Solved] dwm status bar

Similar Messages

Maybe you are looking for