Getting Started with Scrotwm?

muzieca · 2011-01-28 03:53:54

Umm, got a little problem here with ScrotWM. After using GIMP, ScrotWM is not responding any commands anymore.
I don't know what's wrong with it, it just hang. My .scrotwm.conf is pretty basic, just a little change with bar color and bar action to make my conky visible. Any idea?

gutterslob · 2011-01-28 13:38:34

I don't use GIMP on my netbook (where ScrotWM is installed), so I can't say for sure.
From what I've read elsewhere, you need to add a quirk to make GIMP work like it usually does on a floating WM.

Should be;

quirk[Gimp:gimp]            = FLOAT + ANYWHERE

You might need to be careful your stacking mode is not set to fullscreen "[]" when you start GIMP.

Last edited by gutterslob (2011-01-28 13:39:00)

muzieca · 2011-01-29 00:07:41

@gutterslob Thank you for your suggestion. I'll try this right away.

PackRat · 2011-03-08 19:29:33

muzieca wrote:

Umm, got a little problem here with ScrotWM. After using GIMP, ScrotWM is not responding any commands anymore.
I don't know what's wrong with it, it just hang. My .scrotwm.conf is pretty basic, just a little change with bar color and bar action to make my conky visible. Any idea?

I have that issue as well; it's not so bad if I close all images first, then exit the program.

Also, anybody know if there is a way in ScrotWM to have applications open on particular work spaces like you can with dwm and awesome?

muzieca · 2011-04-17 05:27:32

Another question here. Sorry smile
Is it possible to preserve original size of the opened apps without being maximized?
For example, maybe it some kind of floating layout in awesome wm or free layout in wmfs, where the .Xdefaults set the urxvt geometry set on 85x25, and i would like to have it opened according to .Xdefault setting, without being maximized in scrotwm?
It's okay if it's not possible, but if it possible, would you please tell me how to do it?
Thanks in advance.

PackRat · 2011-04-19 13:43:32

muzieca wrote:

Another question here. Sorry
Is it possible to preserve original size of the opened apps without being maximized?
For example, maybe it some kind of floating layout in awesome wm or free layout in wmfs, where the .Xdefaults set the urxvt geometry set on 85x25, and i would like to have it opened according to .Xdefault setting, without being maximized in scrotwm?
It's okay if it's not possible, but if it possible, would you please tell me how to do it?
Thanks in advance.

The only thing I can think of would be to:

1. Set up the quirk so that the program floats
2. Set up a key binding that will launch the program (or a script) with the appropriate geometry - for example

Keybinding

Ctrl+Alt+t

would launch:

uxterm -fg white -bg black -geom 80x32+0+0

and place a 80x32 uxterm in the upper left corner.

@gutterslob
Have you ever tried to use that python script that launches a full screen gimp (the toolbox and layer control are on the sides) in scrotwm? Sorry, can't remember the name of the script, but I believe that gimp 3.0 (or whatever) is going to incorporate something similar.

Edit - found it, gimpbox --> http://opensourceexcedio.wordpress.com/ … p-gimpbox/

Last edited by PackRat (2011-04-22 20:41:02)

muzieca · 2011-04-21 04:22:07

PackRat
Thank you for the info, i really appreciated it, gonna try it now. smile

anonymous · 2011-05-02 04:09:25

I tried using this color value in ScrotWM but the color was wrong.

rgb:83/93/108

Somehow I figured out that ScrotWM cannot accept values with three digits so the color I was seeing was 83/93/10. I want to report this bug but is scrotwm in active development? The bug tracker doesn't seem active at least.

BTW does anyone know if its possible to display the time on the very right-side of the bar?

dmhdlr · 2011-05-22 15:54:39

muzieca wrote:

Umm, got a little problem here with ScrotWM. After using GIMP, ScrotWM is not responding any commands anymore.
I don't know what's wrong with it, it just hang. My .scrotwm.conf is pretty basic, just a little change with bar color and bar action to make my conky visible. Any idea?

I had this issue as well.

anonymous wrote:

Somehow I figured out that ScrotWM cannot accept values with three digits so the color I was seeing was 83/93/10. I want to report this bug but is scrotwm in active development? The bug tracker doesn't seem active at least.

I stick with the X11 color names to take away the guesswork. All of these work:

http://critical.ch/xterm/

But if scrotwm is no longer developed, I may switch . . .

Last edited by dmhdlr (2011-05-22 15:55:50)

gutterslob · 2011-05-22 16:33:05

@PackRat and Muzi
Sorry, only just noticed your posts. I think you need to set up a quirk for Gimp in a specific way to get it to work ... I can't recall how I did it in the past (I don't need Gimp on this particular rig right now), but I'll try installing it in future and see if I can get it to work.

@Replicant
The main dev hasn't been on the #scrotwm irc channel much lately, though he does seem to reply some threads in the main forums as well as that thread they started in the ArchLinux forums... so who knows.
ScrotWM is more popular among FreeBSD and OpenBSD users, so It's best to check those forums or mailing lists for related news. Last contrib to CVS was 2 months ago, btw.

muzieca · 2011-05-22 23:42:23

gutterslob
Thanks for the reply. smile
It's okay, my question is just came out because of my curiosity.
I'm usually using Gimp in my #! install with OpenBox, but not on my GRML install which is using Scrotwm, so i try to install Gimp on my GRML install, and the problem occurred.

dmhdlr · 2011-05-28 05:09:46

replicant wrote:

muzieca wrote:
Umm, got a little problem here with ScrotWM. After using GIMP, ScrotWM is not responding any commands anymore.
I don't know what's wrong with it, it just hang. My .scrotwm.conf is pretty basic, just a little change with bar color and bar action to make my conky visible. Any idea?
I had this issue as well.
anonymous wrote:
Somehow I figured out that ScrotWM cannot accept values with three digits so the color I was seeing was 83/93/10. I want to report this bug but is scrotwm in active development? The bug tracker doesn't seem active at least.
I stick with the X11 color names to take away the guesswork. All of these work:
http://critical.ch/xterm/
But if scrotwm is no longer developed, I may switch . . .

Would you happen to know how to get a systray like stalonetray to coexist nicely with scrotwm? Right now I have to banish it to a distant workspace (9 or 10) in order to not see it. I need a systray for my nm-applet and dropbox applet. Ideally I could just get the systray overlaid over the right side of built-in status bar.

Last edited by dmhdlr (2011-05-28 05:10:39)

PackRat · 2011-05-31 21:05:28

replicant wrote:

Would you happen to know how to get a systray like stalonetray to coexist nicely with scrotwm? Right now I have to banish it to a distant workspace (9 or 10) in order to not see it. I need a systray for my nm-applet and dropbox applet. Ideally I could just get the systray overlaid over the right side of built-in status bar.

I got the tint2 systray working in scrotwm by making a quirk for tint2 so that it would float - I also needed it for nm-applet so I could connect to wireless. Then I made the tint2rc so that it would sit in the upper right corner. Used key bindings to start and stop tint2. I would connect to the wireless then close tint2.

I have yet to mind a way to have an actual system tray in the status bar of scrotwm.

gutterslob · 2011-05-31 22:44:41

>>Replicant
I think I remember Muzieca mentioning some success with stalonetray in ScrotWM. You might want to seek his guidance.

>> PackRat
Can't help you with the systray (the ScrotWM bar doesn't support applets in any form, as far as I know), but if all you need a systray for is NM, you could try this out;
http://packages.debian.org/sid/cnetworkmanager
http://vidner.net/martin/software/cnetworkmanager/
http://repo.or.cz/w/cnetworkmanager.git

There's also nmcli. Found a Ubuntu man page for it, so it might already be included in the Debian build of NM
http://manpages.ubuntu.com/manpages/mav … cli.1.html

Also;
http://mail.gnome.org/archives/networkm … 00145.html

Never used either personally, since I usually prefer wicd-curses, ceni or netcfg for my wireless connectivity.

Last edited by gutterslob (2011-05-31 22:47:18)

muzieca · 2011-05-31 23:27:49

gutterslob and replicant
For the truth, yes, i do try to use stalonetray in scrotwm (and still using it until now),
But the success is just to confirming on Unia question about stalonetray in scrotwm.
i'm using stalonetray is just only for nm-applet to connect to the internet, and after that i just close it. (Mod+x or Mod+shift+x) because the nm-applet will be keep running even you close the tray. smile
But if you like to keep it visible without having to banish it to another workspaces, i'm just adding this to .scrotwm.conf

quirk[stalonetray:stalonetray] = FLOAT + ANYWHERE

so you can move it anywhere you like and resize it. big_smile
I know this in not perfect, but i guess it will do the trick. smile
And i'm very sorry if i couldn't help you more than this as my knowledge is still very limited too.

gutterslob · 2011-06-05 10:38:42

I recall @anon asking about displaying time on the right side of the scrotbar a few posts prior. Also, some other have wondered if it's possible to have multiple colors in it as well.

The devs and ArchWiki often suggest dzen2 as an alternative to the default scrotbar, but the problem with that is you lose the small (but useful) workspace and tiling-layout display on the left.

A friend (PackRat/ddnev45) came up with a "Dang!!... it's so simple why didn't I think of this before?!!" idea.
The scrotbar can pipe scripts (like the default baraction.sh), which means you can actually pipe a dzen2-start-script into it.

It's not the cleanest of mods, since you'll actually be overlaying dzen2 on top of the scrotbar, so you'll have to adjust it's height, width, font and placement to get everything to align properly.

First we will need a basic Conky config. I've attached mine below to give you a rough idea how to set colors. If you don't want to overwrite your primary ~/.conkyrc, you can just create another one and name differently.
I'll use my own path as an example:

/home/geezer/bin/conkyrc_colorcli

# Conky configuration for Dzen2, to be piped into ScrotWM Bar

##############################################
#  Settings
##############################################
out_to_x no
background no
out_to_console yes
update_interval 1.0
total_run_times 0
use_spacer none
TEXT
^fg(\#6699cc)Processor ^fg()- ^fg(\#cc9966)${cpu cpu0}.00%^fg()  ^fg(\#666666)|  ^fg(\#6699cc)Memory ^fg()- ^fg(\#cc9966)${memperc}.00%^fg()  ^fg(\#666666)|  ^fg(\#6699cc)Swap ^fg()- ^fg(\#cc9966)${swapperc}.00%^fg()  ^fg(\#666666)|  ^fg(\#6699cc)Root ^fg()- ^fg(\#cc9966)${fs_used_perc /}.00%^fg()  ^fg(\#666666)|  ^fg(\#6699cc)Home ^fg()- ^fg(\#cc9966)${fs_used_perc /home}.00%^fg()  ^fg(\#666666)|  ^fg(\#6699cc)Temperature ^fg()- ^fg(\#cc9966)${hwmon temp 1}'C^fg()  ^fg(\#666666)|  ^fg(\#6699cc)Uploads ^fg()- ^fg(\#cc9966)${upspeedf eth0}kb/s^fg()  ^fg(\#666666)|  ^fg(\#6699cc)Downloads ^fg()- ^fg(\#cc9966)${downspeedf eth0}kb/s^fg()

Important: Make it a 1-liner conky (for obvious reasons)

Download dzen2 if you don't have it yet (it's a small download, don't worry), preferably the version from Unstable (if you're on Debian) or Git. Then create a script to start it. Here's mine;

/home/geezer/bin/scrotbar.sh

#!/bin/sh
exec conky -d -c "$HOME/bin/conkyrc_colorcli" | dzen2 -fg "#666666" -bg "#333333" -ta right -w 1100 -h 13 -x 333 -y 1 -fn -Misc-Fixed-Medium-R-Semicondensed-*-12-110-75-75-C-60-ISO10646-1 &
exit 0

Important: Remember to make the script executable!

Now you'll need to align you dzen2 bar against the scrotbar. See the launch command in in the script? The part after exec and before &, copy that and paste in a terminal. Press Enter and a dzen2 bar should pop up in top of your scrotbar. You can easily kill it with Ctrl + C. adjust the height, width x/y alignment, font...etc till it fits your monitor. Once done, put the values into the scrotbar.sh script above and save.

Finally, open up your ~/.scrotwm.conf and modify these bits (adjust path accordingly);

bar_action            = /home/geezer/bin/scrotbar.sh
bar_delay             = 2

Note: The conkyrc I included above does not have a clock set, since I'm using the one included in the scrotwm bar, but if you'd like a clock in your conky, make sure to disable the clock in your ~/.scrotwm.conf as well (clock_enabled = 0). I set the bar_delay to 2sec because having it at 1sec seemed to cause multiple instances of dzen2 (might have been leftover artefacts... dunno) and occasional flickering of the bar.

If all goes well, reloading ScrotWM (Mod + q) should have something like this appear;

Click to enlarge.

Like I said, it's not the absolute cleanest solution. If you hide the scrotbar (Mod + b), you'll see the actual dzen2 bar remaining, and unhiding the scrotbar again will block out dzen2 (restarting dzen2 or scrotwm is the only fix, afaik).
But the benefits are that you don't need to set regions in the scrotwm.conf and launching dmenu isn't affected.

Hope this helps.... Cheers smile

Last edited by gutterslob (2011-08-25 17:13:16)

muzieca · 2011-06-05 11:48:50

gutterslob
Thank you for posting this trick. This is going to be very useful.
There is slightly difference between your method with mine, but the result is still the same.
I'm adding the scrotbar.sh to autostart script for scrotwm. that's all. smile
Once again, thank you for sharing this, i really appreciated it. smile

PackRat · 2011-06-06 01:57:40

@gutterslob

Do you know if the version of dzen2 in the Debian unstable repos. is in sync with the git version of dzen2. When I installed dzen2 from git to use in Scrotwm, I did so because the git version has support for xft fonts. I don't know if dzen2 from the repos. allows for that. Just an FYI for anyone that will try this method.

skrite · 2011-06-06 13:51:34

Thanks for your help on this.. i just started with scrotwm last week. l really dig it.
btw, been a fan of your work since Rusticity, which i still use on my little netbook.

gutterslob · 2011-06-06 14:57:01

>> Muzi
That's what I was doing initially, till I recalled what Packrat/ddnev told me some time ago about piping it as a .sh to the Scrotbar. Seems better this way if you restart ScrotWM often.

>> PackRat
Don't think so, mate.
http://packages.debian.org/sid/dzen2
The changelog Debian provides is pretty vague, but the package page doesn't list libxft as a dependency, so it's probably a no-no.
I remember reading a rant somewhere about Debian not opting for a XFT-friendly build of dzen2 due to dmenu-xft not being quite ready yet (though this was early last year). Dunno for sure, but I'm pretty sure the Git version is at least 0.2 version numbers ahead of the Unstable package. Reason I suggested that was because dzen2 from a past Squeeze (when it was still Testing) install kept flickering in ScrotWM, and I just wanted to play safe with my suggestions (yeah, playing safe by recommending a package from Sid... the irony). I only have generic FreeSans, FreeMono and Bitstream Vera true-type fonts installed on this GRM-based machine (I mostly use pixel fonts for everything these days). Will test it out when I get home later and update this post.

>> Skrite
Heh. That's such an old theme, Rusticity. Surprised anyone even remembers it.
I'll get back to GTK theming eventually, but probably .css style GTK3 when it becomes more widespread (and more apps adopt it natively). Till then, you'll have to bear with my old junk, unfortunately.

Welcome to the #! forums, btw. :-)

pfh · 2011-06-11 14:52:34

Conky

out_to_x no
background no
use_xft yes
xftfont Terminus:size=8
xftalpha 1
update_interval 1
total_run_times 0
out_to_console yes
use_spacer none
no_buffers yes
override_utf8_locale yes

TEXT
  ^fg(\#e1e02a)Kernel:^fg() ^fg(\#e1e16e)${kernel}^fg()  ^fg(\#620909)|^fg()  ^fg(\#e1e02a)CPU: ^fg()^fg(\#e1e16e)${if_match ${cpu cpu1}<10}00${cpu cpu1}${else}${if_match ${cpu cpu1}<100}0${cpu cpu1}${else}${cpu cpu1}${endif}${endif}% | ${if_match ${cpu cpu2}<10}00${cpu cpu2}${else}${if_match ${cpu cpu2}<100}0${cpu cpu2}${else}${cpu cpu2}${endif}${endif}%^fg()  ^fg(\#620909)|^fg()  ^fg(\#e1e02a)RAM:^fg() ^fg(\#e1e16e)${memperc}.00%  ^fg(\#620909)|^fg()  ^fg(\#e1e02a)Temperature:^fg() ^fg(\#e1e16e)${hwmon 0 temp 1}C^fg()  ^fg(\#620909)|^fg()  ^fg(\#e1e02a)Battery:^fg() ^fg(\#e1e16e)${battery_percent BAT0}%^fg()  ^fg(\#620909)|^fg()  ^fg(\#e1e02a)WiFi:^fg() ^fg(\#e1e16e)${wireless_link_qual wlan0}%^fg()  ^fg(\#620909)|^fg()  ^fg(\#e1e02a)Uploads:^fg() ^fg(\#e1e16e)${upspeedf wlan0}kb/s^fg()  ^fg(\#620909)|^fg()  ^fg(\#e1e02a)Downloads:^fg() ^fg(\#e1e16e)${downspeedf wlan0}kb/s^fg()

scrotbar.sh

#!/bin/sh

exec conky -c "$HOME/conky_files/conky4scrot" | dzen2 -e '' -x '320' -y '4' -w '1360' -h 11 -ta c -fg '#a7a651' -bg '#8a3a0c' -fn terminus-cp1251-16 &

exit 0

muzieca · 2011-06-21 11:04:23

Just found out another problem. Sorry to ask again. smile
When i'm using irssi, i've just found out that the irssi keybindings are conflicting with scrotwm keybindings.
Then, i'm changing the Mod key in the .scrotwm.conf from Mod1 to Mod4, but nothing happened even i'm restarting the system.
All the keybindings are still using alt key, and not win key.
After that, i'm using xev, i just want to know if the win/super key is recognized or not in scrotwm, with the result that win key is recognized in scrotwm.
for your information, i'm installing scrotwm from the repo. Just apt-get and not installing from source.
Couldn't find something wrong in it, but i hope i was wrong.
this is my .scrotwm.conf.

# $scrotwm: scrotwm.conf,v 1.26 2010/07/15 14:03:04 marco Exp $
#
# colors for focussed and unfocussed window borders
color_focus             = rgb:77/AA/CC
color_unfocus           = rgb:88/88/88

# bar settings
bar_enabled             = 1
bar_border[1]           = rgb:50/50/50
bar_color[1]            = rgb:30/30/30
bar_font_color[1]       = rgb:66/99/CC
bar_font                = -*-fixed-medium-r-semicondensed-*-*-*-*-*-*-*-*-*
bar_action              = /home/muzieca/.scrotbar.sh
bar_delay               = 1
#bar_at_bottom          = 1
stack_enabled           = 1
clock_enabled           = 1
#clock_format           = %a %b %d %R %Z %Y
title_name_enabled      = 0
title_class_enabled     = 0
#focus_mode             = default
disable_border          = 1

# spawn app
program[term]           = urxvt
# program[screenshot_all]       = screenshot.sh full
# program[screenshot_wind]      = screenshot.sh window
# program[lock]         = xlock
# program[initscr]      = initscreen.sh
 program[menu]          = dmenu_run -fn $bar_font -nb $bar_color -nf $bar_font_color -sb $bar_border -sf $bar_color
spawn_term              = urxvt

# dialog box size ratio .3 >= r < 1
dialog_ratio            = 0.6

# Split a non-Xrandr dual head setup into one region per monitor
# (non-standard driver-based multihead is not seen by scrotwm)
# region                = screen[1]:1280x1024+0+0
# region                = screen[1]:1280x1024+1280+0

# mod key, (windows key is Mod4) (apple key on OSX is Mod2)
modkey = Mod4
# key bindings
# unbind with: bind[] = <keys>
bind[cycle_layout]      = MOD+space
bind[stack_reset]       = MOD+Shift+space
bind[master_shrink]     = MOD+h
bind[master_grow]       = MOD+l
bind[master_add]        = MOD+comma
bind[master_del]        = MOD+period
bind[stack_inc]         = MOD+Shift+comma
bind[stack_dec]         = MOD+Shift+period
bind[swap_main]         = MOD+Return
bind[focus_next]        = MOD+j
bind[focus_prev]        = MOD+k
bind[swap_next]         = MOD+Shift+j
bind[swap_prev]         = MOD+Shift+k
bind[spawn_term]        = MOD+Shift+Return
bind[menu]              = MOD+p
bind[quit]              = MOD+Shift+q
bind[restart]           = MOD+q
bind[focus_main]        = MOD+m
bind[ws_1]              = MOD+1
bind[ws_2]              = MOD+2
bind[ws_3]              = MOD+3
bind[ws_4]              = MOD+4
bind[ws_5]              = MOD+5
bind[ws_6]              = MOD+6
bind[ws_7]              = MOD+7
bind[ws_8]              = MOD+8
bind[ws_9]              = MOD+9
bind[ws_10]             = MOD+0
bind[ws_next]           = MOD+Right
bind[ws_prev]           = MOD+Left
bind[screen_next]       = MOD+Shift+Right
bind[screen_prev]       = MOD+Shift+Left
bind[mvws_1]            = MOD+Shift+1
bind[mvws_2]            = MOD+Shift+2
bind[mvws_3]            = MOD+Shift+3
bind[mvws_4]            = MOD+Shift+4
bind[mvws_5]            = MOD+Shift+5
bind[mvws_6]            = MOD+Shift+6
bind[mvws_7]            = MOD+Shift+7
bind[mvws_8]            = MOD+Shift+8
bind[mvws_9]            = MOD+Shift+9
bind[mvws_10]           = MOD+Shift+0
bind[bar_toggle]        = MOD+b
bind[focus_next]        = MOD+Tab
bind[focus_prev]        = MOD+Shift+Tab
bind[wind_kill]         = MOD+Shift+x
bind[wind_del]          = MOD+x
bind[screenshot_all]    = MOD+s
bind[screenshot_wind]   = MOD+Shift+s
bind[float_toggle]      = MOD+t
bind[version]           = MOD+Shift+v
bind[lock]              = MOD+Shift+Delete
bind[initscr]           = MOD+Shift+i

# quirks
# remove with: quirk[class:name] = NONE
#quirk[MPlayer:xv]                      = FLOAT + FULLSCREEN
#quirk[OpenOffice.org 2.4:VCLSalFrame]  = FLOAT
#quirk[OpenOffice.org 3.0:VCLSalFrame]  = FLOAT
#quirk[OpenOffice.org 3.1:VCLSalFrame]  = FLOAT
#quirk[Firefox-bin:firefox-bin]         = TRANSSZ
#quirk[Firefox:Dialog]                  = FLOAT
quirk[Gimp:gimp]                        = FLOAT + ANYWHERE
#quirk[XTerm:xterm]                     = XTERM_FONTADJ
#quirk[xine:Xine Window]                        = FLOAT + ANYWHERE
#quirk[Xitk:Xitk Combo]                 = FLOAT + ANYWHERE
#quirk[xine:xine Panel]                 = FLOAT + ANYWHERE
#quirk[Xitk:Xine Window]                        = FLOAT + ANYWHERE
#quirk[xine:xine Video Fullscreen Window] = FULLSCREEN + FLOAT
#quirk[pcb:pcb]                         = FLOAT
quirk[chromium-browser:chromium-browser] = FLOAT
quirk[vlc:vlc]                          = FLOAT
quirk[Firefox:firefox]                  = FLOAT
quirk[gcolor2:gcolor2]                  = FLOAT + ANYWHERE

# EXAMPLE: define firefox program and bind to key
# program[firefox]      = firefox http://scrotwm.org/
# bind[firefox]         = MOD+f

I believe that my .scrotwm.conf is still pretty basic.
Any help will be appreciated. Thanks in advance.

Last edited by muzieca (2011-06-21 11:35:52)

gutterslob · 2011-06-21 12:06:38

@Muzi

Strange..... I've experienced this behavior before in some newer versions on ScrotWM. Not the latest .30 release, but maybe 1 or 2 versions prior (.27 or .28, iirc). The one in the Debian repos is old, but is still the most stable version out there, I notice (if Debian insists on the same version in Stable, Testing and Sid repos, you can usually bet they have a very, very good reason for doing so), and it has never exhibited this sort of behavior on my setups.

Do you have any special keymaps set to load in your .xinitrc or the script used to start scrotwm? If not, that could be one reason. I have a "setxkbmap us &" line in mine. Sometimes, a "dpkg-reconfigure keyboard-configuration" or "dpkg-reconfigure console-data" might be needed as well (had to do this for GRML on one of my older comps)

Also, your config seems to be for a newer ScrotWM version, since the one from the Debian repos can't identify functions like "bat_at_bottom", but those related to the newer versions all seem to be commented out, so I'm not quite sure either. Make a backup of your current conf, and then copy the config from your /etc/scrotwm.conf and paste/overwrite ~/.scrotwm.conf ..... Modify that one to use your Mod4 key, and your terminal emulator and whatever keybindings and quirks, but don't add functions (bar settings).

Here's one I have lying around from a very old version I backed up (possibly 2 yrs old);
/etc/scrotwm.conf
http://pastebin.com/uZR0De19

One more thing I've noticed in the past. On an old Sidux install, I remember the Mod4 key not being recognized until I restarted (rebooted) a few times. Can't explain why, though (I was new to ScrotWM at the time).

I suspect it's either an issue with the conf file, or a keymap problem.

Last edited by gutterslob (2011-06-21 16:02:18)

muzieca · 2011-06-21 12:45:15

gutterslob
Thank you for your help. It works now, flawlessly.
Rolling back to the stable version, and copying the /etc/scrotwm.conf to ~/.scrotwm.conf.
Editing few "syntax" and voila, works like charm.
Enjoying scrotwm now, starting to getting used to it. smile
Thank you very much for your help, this is a very valuable experience in my tiling adventure. big_smile

aaro · 2011-06-22 10:14:02

Hi guys. Just started testing scrotwm. Have a noob question. When i set some windows to float in a workspace, put them in some position, when i switch workspace and get back, all the float windows are moved from the position i left them to the center of the screen. Can this be modified so the floating windows keep their position after a workspace switch?

CrunchBang Linux

SEARCH

#26 2011-01-28 03:53:54

Re: Getting Started with Scrotwm?

#27 2011-01-28 13:38:34

Re: Getting Started with Scrotwm?

#28 2011-01-29 00:07:41

Re: Getting Started with Scrotwm?

#29 2011-03-08 19:29:33

Re: Getting Started with Scrotwm?

#30 2011-04-17 05:27:32

Re: Getting Started with Scrotwm?

#31 2011-04-19 13:43:32

Re: Getting Started with Scrotwm?

#32 2011-04-21 04:22:07

Re: Getting Started with Scrotwm?

#33 2011-05-02 04:09:25

Re: Getting Started with Scrotwm?

#34 2011-05-22 15:54:39

Re: Getting Started with Scrotwm?

#35 2011-05-22 16:33:05

Re: Getting Started with Scrotwm?

#36 2011-05-22 23:42:23

Re: Getting Started with Scrotwm?

#37 2011-05-28 05:09:46

Re: Getting Started with Scrotwm?

#38 2011-05-31 21:05:28

Re: Getting Started with Scrotwm?

#39 2011-05-31 22:44:41

Re: Getting Started with Scrotwm?

#40 2011-05-31 23:27:49

Re: Getting Started with Scrotwm?

#41 2011-06-05 10:38:42

Re: Getting Started with Scrotwm?

#42 2011-06-05 11:48:50

Re: Getting Started with Scrotwm?

#43 2011-06-06 01:57:40

Re: Getting Started with Scrotwm?

#44 2011-06-06 13:51:34

Re: Getting Started with Scrotwm?

#45 2011-06-06 14:57:01

Re: Getting Started with Scrotwm?

#46 2011-06-11 14:52:34

Re: Getting Started with Scrotwm?

#47 2011-06-21 11:04:23

Re: Getting Started with Scrotwm?

#48 2011-06-21 12:06:38

Re: Getting Started with Scrotwm?

#49 2011-06-21 12:45:15

Re: Getting Started with Scrotwm?

#50 2011-06-22 10:14:02

Re: Getting Started with Scrotwm?

Board footer