You are not logged in.
Splex wrote:Patching scrotwm-cvs fails with both aedit's patch and the prevws patch (switch to previous workspace with mod+a.) I combined the patches into one patch that currently works with scrotwm-cvs. Here it is:
Nice idea but I get 34 out of 36 hunks failed with your patch against cvs
Anyways there is nothing enthusiasming in CVS, while aedit patches are so nice (in particular borderless fullscreen and floating stack) that I can't understand why they get ignored. If there is no solid reason, perhaps a fork of scrotwm would be
a nice idea.
I just tried copying the 'code' block from my above post.. and I also got 34 out of 36 failures...'code' tags mutilated the patch.
I edited the post to point to pastebin.com... please let me know if that works.
Offline
I edited the post to point to pastebin.com... please let me know if that works.
Yes, that worked, thanks
Mortuus in anima, curam gero cutis
Offline
Scrotwm 0.9.24 released.
You can get it http://scrotwm.org/snapshot/scrotwm-0.9.24.tgz
Offline
This was 11 pages long, so I didn't read it, but just saying... i3 FTW... it's not the first tiling wm I've tried to use, but it is really sleek. This project looks (reads) like a good alternative, but the areas of support that it offers I don't use (multiple monitors for example). I'm glad there are so many choices! It's all about creating the niche (tiling WMs) and then populating it (i3, wmii, dwm, euclid-wm, scrotwm, etc.). Asking "Why make another?" is like saying "Why continue to support Gnome when there's KDE?" or "Why even have LXDE when there's XFCE?" or "Who even uses Fluxbox?" or "Openbox + tint2 + conky is l4m3!" or what have you. (Crunchbang is awesome lol)
Linux.. because you don't just want what the distributor will let you have.
Main Arch Setup: HP Pavillion p7-1209, Quad-Core i3-2120 3.3Ghz, 8GB RAM, 1TB HDD, Intel Graphics
Laptop Arch Setup: Gateway lt3103u Netbook, AMD Athlon64 1.2Ghz, 2GB RAM, 250GB HDD, ATI X1270 R600
Offline
AEdit, all of your patches should be in mainline later tonight. About half of them are in now.
Everyone: please build scrotwm-cvs and test away. New features include "Mod-a", better multihead support, removing the 1px border when appropriate, and floating memory.
That last one is probably the most complex. Float stuff, move it around, switch workspaces. Does it remember where you moved it to?
Looks like Marco is currently working on merging the colored status bar patch.
Offline
That's good news. I will take a look at it.
Offline
Hello,
First of all great window manager, I love it ! Thanks for the hard work.
Just one small question, any ideas why mplayer won't go full screen when I hit the 'f' key?
Additional info.:
- placed the default config in /etc/scrotwm.conf (no conf for scrotwm on my ~/ folder), then MOD+q
- $mplayer video.avi (tried various videos)
- video is 'floating' by default, centered, has red borders when mouse is over, normal size, I can change its size and move the window with MOD + Mouse buttons.
- hit 'f' key, video flickers, window/video size stays the same
- pacman -Q | grep scrotwm outputs: scrotwm 0.9.24-1 (installed via yaourt -S scrotwm)
- pacman -Q | grep mplayer outputs: mplayer 31428-1 (installed via pacman -S mplayer)
- tried the default:
#quirk[MPlayer:xv] = FLOAT + FULLSCREEN
then:
quirk[MPlayer:xv] = FLOAT + FULLSCREEN
then MOD+q
Thanks !
Offline
It looks like a nice dynamic tiler. I think it is right up my alley. I am using Awesome now, but I am not using Awesome to it's potential, so I think an even more minimal dynamic tiler may be more suited for me.
Offline
I am not sure about the color bar patch. I need to think about it some more.
Did I miss any others?
Offline
I am not sure about the color bar patch. I need to think about it some more
A particular problem with it or a more general rethink?
Did I miss any others?
Yes, the second bug described in message #162 above (in cyclescr()) and the patch in #163, (in main()). The operator precedence issue I mentioned is that a ? b : c is evaluated after p + q, so extra ()s are required.
Offline
marco_p wrote:I am not sure about the color bar patch. I need to think about it some more
A particular problem with it or a more general rethink?
Bit of both. Code is pretty ugly and I think if we go down that route we should implement like a graphical bar ala xstatbar. Opinions?
Did I miss any others?
Yes, the second bug described in message #162 above (in cyclescr()) and the patch in #163, (in main()). The operator precedence issue I mentioned is that a ? b : c is evaluated after p + q, so extra ()s are required.
Help a brother out, Do you have patches? If so email them to me at marco@peereboom.us
Offline
Aedit wrote:marco_p wrote:I am not sure about the color bar patch. I need to think about it some more
A particular problem with it or a more general rethink?
Bit of both. Code is pretty ugly and I think if we go down that route we should implement like a graphical bar ala xstatbar. Opinions?
I added just the minimal code to pass colors into the status bar without changing the way it works, but it's not the only way to do it of course. I don't see anyone making xstatbar work on Linux (it's quite BSD-centric) -- we already have plenty of ways to draw a bar: dzen2 (svn version has -dock), conky, xmobar, tint, i3status+dzen2. To use them you could
a) make the scrotwm-specific part of the bar ("1:2 [-]") available to external processes.
b) make scrotwm respect the bar's EWMH hints and place it correctly, dynamically reserving the required screen space.
See the dzen2 (svn) and i3 code. If you want to integrate more maybe provide keybindings for starting/stopping the bar process and config file entries.
Did I miss any others?
Yes, the second bug described in message #162 above (in cyclescr()) and the patch in #163, (in main()). The operator precedence issue I mentioned is that a ? b : c is evaluated after p + q, so extra ()s are required.
Help a brother out, Do you have patches? If so email them to me at marco@peereboom.us
I emailed you them in January and you applied half of one of them. We're only talking about a few lines here (-1/+1 and -5/+4) -- see the messages above if you can't find them.
Last edited by Aedit (2010-07-04 09:38:26)
Offline
Hello,
Any ideas why mplayer won't go full screen when I hit the 'f' key?
Running the same versions, works fine here. Did you accidentally leave an mplayer window open somewhere? (It acts oddly when there are two.) Have you tried forcing a different video output mode? Some can't fullscreen. "mplayer -vo help"
Offline
Firefox and probably other graphical applications look different in scrotwm than in Gnome.
Is it due to some gtk configuration or something?
Does anyone know how to make them look equal?
Offline
Aedit:
I cleaned up your color bar patch. Sending it to Marco now.
void
bar_print(struct swm_region *r, char *s)
// print s in the bar, parsing and applying any inline color tags
// formats include: ^fg(rgb:12/fa/43), ^fg(red), ^fg(#12fa43)
// Function modifies s, sprinkling it with \0
{
char *s2;
int xpos = 4; // starting x position
XClearWindow(display, r->bar_window);
XSetForeground(display, bar_gc, r->s->c[SWM_S_COLOR_BAR_FONT].color);
while (strstr(s, "^fg(")) { // more colors to parse
// extract/apply text before tag
s2 = strstr(s, "^fg(");
s[strlen(s) - strlen(s2)] = '\0';
XDrawString(display, r->bar_window, bar_gc, xpos, bar_fs->ascent, s, strlen(s));
xpos += XTextWidth(bar_fs, s, strlen(s));
s = s2 + 4;
// extract/apply color
if (strstr(s, ")") == NULL)
{break;}
s2 = strstr(s, ")");
s[strlen(s) - strlen(s2)] = '\0';
XSetForeground(display, bar_gc, name_to_color(s));
s = s2 + 1;
}
// and anything left over
XDrawString(display, r->bar_window, bar_gc, xpos, bar_fs->ascent, s, strlen(s));
}
Last edited by keenerd (2010-07-06 01:28:27)
Offline
Firefox and probably other graphical applications look different in scrotwm than in Gnome.
Is it due to some gtk configuration or something?
Does anyone know how to make them look equal?
Just define your gtk2 theme
Mortuus in anima, curam gero cutis
Offline
@keenerd: I like it, thanks.
Offline
dabd wrote:Firefox and probably other graphical applications look different in scrotwm than in Gnome.
Is it due to some gtk configuration or something?
Does anyone know how to make them look equal?Just define your gtk2 theme
Is there any scrotwm.conf option to change the gtk2 theme?
Last edited by dabd (2010-07-06 11:24:14)
Offline
Is there any scrotwm.conf option to change the gtk2 theme?
You can change the theme manually by altering the .gtkrc-2.0 file within your home directory, or you can use a gtk2 'theme changer' which does the job for you...
http://wiki.archlinux.org/index.php/Gtk#GTK.2B_2.x
Last edited by esodax (2010-07-06 12:21:53)
Offline
marco_p wrote:Aedit wrote:A particular problem with it or a more general rethink?
Bit of both. Code is pretty ugly and I think if we go down that route we should implement like a graphical bar ala xstatbar. Opinions?
I added just the minimal code to pass colors into the status bar without changing the way it works, but it's not the only way to do it of course. I don't see anyone making xstatbar work on Linux (it's quite BSD-centric) -- we already have plenty of ways to draw a bar: dzen2 (svn version has -dock), conky, xmobar, tint, i3status+dzen2. To use them you could
a) make the scrotwm-specific part of the bar ("1:2 [-]") available to external processes.
b) make scrotwm respect the bar's EWMH hints and place it correctly, dynamically reserving the required screen space.
See the dzen2 (svn) and i3 code. If you want to integrate more maybe provide keybindings for starting/stopping the bar process and config file entries.
I second making it easier to use external apps (like dzen2) to draw a bar. IMHO it would be more productive to do that than to make the scrotwm's internal bar handling code more complex. Especially when, like Aedit said, there are plenty of ways to draw bars.
Offline
Alright I have been screwing around with dzen2 but that really is an unnatural fit for scrotwm. I think I can make it work but at a cost of time (which I don't have too much of). A much simpler thing is to go ahead and implement EWMH (as per http://standards.freedesktop.org/wm-spe … -1.3.html) and create an empty spot for the external bar. What are the thoughts on this?
Offline
Aedit: Marco requests a ping from you. Related, I could use you email address too.
Offline
Found this the other day. Some here might be interested in it.
"witch Linux"
http://invariability.net/witch/
Based on Debian with ncurses and GTK apps. And ScrotWM. First distro I know of that uses it by default.
Edit: Also, there is an alpha Arch build. Virtualbox only, it seems.
Last edited by keenerd (2010-07-19 16:32:10)
Offline
How would i use 'urxvtcd -e tmux' as my spawn_term command, so that when I hit Mod+Shift+Return, urxvtcd opens and runs tmux? I put "urxvtcd -e tmux" in .scrotwm.conf, with and without quotes, but neither works.
Offline
First of all, I think scrotwm is a great window manager. It works really well out of the box, and configuring it has been relatively (compared with some of the other tiling WMs) easy.
The one question I have is about getting Totem to display fullscreen. I presume I need to write a 'quirk' entry for Totem, but I can't seem to get the syntax right (I can get it to float, but not to go fullscreen).
Any ideas?
Edit: I didn't realize I could hide the controls in Totem, so I can mimic fullscreen behavior, which is good enough for me.
Last edited by riverrun (2010-08-29 06:15:17)
Offline