You are not logged in.
Wouldn't it kind of make sense to allow some kind of externalization of borders? For those wanting bit of eye-kindy, it would be interesting to be able to do fancy decorations and window titles and such? I'm not exactly sure if I'm being serious, but it's interesting idea I think.
Imho, at a certain point, the modularity just becomes painful micromanagement. To be honest, I would have jumped ship already if bloom wouldn't offer the excellent example-scripts and configs. But I can't take much more.. On the other hand, externalizing border-drawing (which really isn't window-managing) to something like a enhanced compton sounds more reasonable than the rules_command stuff.
Offline
milomouse wrote:Small price to pay but are there any current alternatives to the "optional" external rule commands provided? I suppose I could try to make my own but was just curious to see if any exist right now. Otherwise, I guess I could revert to earlier git commit of bspwm but I really don't like going backwards unless it's absolutely necessary.
Look at this and this. You don't have to use rul{c,d}, any script can do rule handling.
Ah, thanks. Sorry for not seeing this earlier, these larger threads become intimidating to search through after a while. I will give them a try!
Wouldn't it kind of make sense to allow some kind of externalization of borders? For those wanting bit of eye-kindy, it would be interesting to be able to do fancy decorations and window titles and such? I'm not exactly sure if I'm being serious, but it's interesting idea I think.
Sounds interesting.. although I'm on-board with ~ict when I like to keep SOME functionality in the window manager. Yes, borders seem less window management than eye-candy but then we would need to look into specialty programs that simply add window decoration or lines of colors or whatnot? Maybe.. But I agree that window rules seem more like a window manager job than decoration. That's part of the reason I liked bspwm as it was one a few managers that offered this capability natively.
Anyway, I too would have jumped ship a little while ago if not for Bloom and friends' tips and scripts. But there is a certain point when I feel like it becomes too extended and starts to feel hackish with all these scripts. You can only lose so much to gain so much before it becomes a frankenstein like `uzbl'. Right now, I think I can stick with it, though! Thanks, everyone. I will continue to monitor this thread as much as I can and github for any other changes.
Edit: So I've tried scripts and still do not like.. but I guess that's just me. I'm reverting to commit "de281a4356814e701994c1fdd96df1c79ced7e4d" for now. Thanks, and I apologize for being difficult -- I just don't get whey we're taking this great functionality OUT of bspwm.
Last edited by milomouse (2013-12-11 22:56:58)
Offline
@milomouse made me change my mind: the rule command is back!
Please note that the syntax changed slightly compared to the previous rule command: see the manual and the example bspwmrc.
It is still possible to use a script to apply rules via external_rules_command (the script now receives the class and instance names as $2 and $3).
Last edited by bloom (2013-12-12 14:02:28)
Offline
Thanks for understanding, bloom! I updated to the newer syntax and everything works great. Cannot say how much I enjoy this window manager and all the hard work put into it.
Offline
@bloom: I didn't want to spam the screenshot-thread so this question relates to your suggestion of using the "private" toggle to get a "master area". Is there some documentation what the different toggles do exactly? The man page says that there is private, locked and sticky, but no explanation is given?
Offline
@bloom: I didn't want to spam the screenshot-thread so this question relates to your suggestion of using the "private" toggle to get a "master area". Is there some documentation what the different toggles do exactly? The man page says that there is private, locked and sticky, but no explanation is given?
The window states documentation is brought by 8eb5994.
Offline
Hi bloom,
is it not supposed to restore only part of the tree?
There where different results, sometimes X got killed, but that was probably my fault.
How would you load the layout of one tag?
Thank you.
What I did:
$ bspc query -T
MONITOR01 944x1040+0+0 0,0,0,0 *
I 2 2 T -
m URxvt 0x400006 2 640x384+0+0 R --------- *
II 2 2 T -
III 2 2 T -
IV 2 2 T -
V 2 2 T -
VI 2 2 T -
VII 2 2 T -
VIII 2 2 T -
IX 2 2 T -
X 2 2 T -
1 1 6 T - *
H m 0.52
a luakit 0x100001F 1 800x600+0+0 R ---------
V m 0.48
m URxvt 0xE00006 1 640x384+0+0 R ---------
m URxvt 0xC00006 1 640x384+0+0 R --------- *
$ cat bspwm.tree
MONITOR01 944x1040+0+0 0,0,0,0 *
1 1 6 T - *
H m 0.52
a URxvt 0xC00006 1 640x384+0+0 R ---------
V m 0.48
m URxvt 0xE00006 1 640x384+0+0 R --------- *
m luakit 0x100001F 1 800x600+0+0 R ---------
$ bspc restore -T bspwm.tree
Restore tree: can't open file
Offline
Quick feature request: Is there any way to implement a next-floating-position toggle? When I'm working in a floating program, almost all the windows start at 0,0. This would at least allow me to write a script that queries the window positions and places the next floating windows at an empty space.
If you do find a way to float windows in empty spaces, I will pay you $50 and this window manager will become as powerful as any of the floaters.
For example, the default would turn into
bspc window -t floating 0,0
This could be super extensible through scripts:
bspc window -t floating $(~/scripts/emptyspace x),$(~/scripts/emptyspace y)
If this isn't possible, then at least a "place floating windows in center" would be nice.
Offline
How would you load the layout of one tag?
bspwm has desktops, not tags.
Although the tree for desktop foo can be saved with:
bspc query -T -d foo > foo.tree
I have no idea what purpose it would serve.
The real question is: what are you trying to do?
Offline
Quick feature request: Is there any way to implement a next-floating-position toggle?
I'm afraid it would fail as soon as you try to rotate the tree...
Therefore, I'd rather implement a pseudo-floating state.
And I will.
Offline
tonk wrote:Don't get me wrong, bspwm is a great wm (and sxhkd a wonderfull hotkey daemon), but i need my master area.
The following might give you what you're aiming for:
bspc window biggest -t private
tonk wrote:Haven't looked further into it, is it possible to push/pull e.g 10px in bspwm?
It is, as of 1379e6f.
Thanks! Currently trying it out. ...next time i'll just ask or make a suggestion
Offline
bspwm has desktops, not tags.
I'm sorry I meant desktop, maybe workspace but not tag
The real question is: what are you trying to do?
It's the impossible thing:
bloom wrote:
Impossible.
You can do that:
bspc query -T > saved_layout bspc restore -T saved_layout
However, this won't work across restarts as the window IDs, the only reliably distinct way to identify windows, will change.
Thanks to Stebalien for kicking my ass with those window IDs.
You don't like my script but here is it anyway https://github.com/ctx/ws-session .
It works on a desktop or workspace basis, so I have to load the layout of one desktop.
Most of it was there for a long time but now it 'sometimes' really loads the old layout.
But not with bspwm; should I replace the desktop in the actual output of
bspc query -T
with the old layout and then reload the whole tree?
Offline
You don't like my script but here is it anyway https://github.com/ctx/ws-session.
It works on a desktop or workspace basis, so I have to load the layout of one desktop.
Then you should be doing this in wm/bspwm.sh:
s_save_layout_bspwm() {
bspc query -T -d "$1"
}
shouldn't you?
Offline
Almost, $S_SEL_TAG.. Thanks for the first bug report
Offline
tonk wrote:Haven't looked further into it, is it possible to push/pull e.g 10px in bspwm?
It is, as of 1379e6f.
Works fine, only 2 minor issues. There seems to be a rounding error? After 4-5 resizes à 20px it looks like this. Workaround is to set bottom_padding -1 (Edit: split_ratio is set to 0.5)
The other issue is probably my own fault.
Works fine:
super + alt + j
bspc window -e down +20 || bspc window -e up +20
super + alt + k
bspc window -e down -20 || bspc window -e up -20
Whereas this doesn't work as (I) expected. Only one value from the last {} is recognized
super + alt + {j,k}
bspc window -e down {+,-}20 || \
bspc window -e up {+,-}20
Last edited by tonk (2013-12-21 19:35:04)
Offline
After 4-5 resizes à 20px it looks like this.
I can't reproduce.
What's the output of bspc query -T -d for the given screenshot?
And the output of xwininfo | grep Height on one of the two windows?
super + alt + {j,k} bspc window -e down {+,-}20 || \ bspc window -e up {+,-}20
The last two sequences are nested: it won't work.
Offline
bspc query -T -d
DVI-I-2 1920x1200+0+0 0,0,0,0 *
3 2 40 T - *
V m 0.500000
a st-256color 0x2600001 2 816x496+0+0 R --------- *
H m 0.500000
m st-256color 0x2400001 2 816x496+0+0 D ---------
m st-256color 0x2200001 2 816x496+0+0 R ---------
And the output of xwininfo | grep Height ; bspc query -T -d | grep H of the bottom window until the error occurs. After the +-1px, it stays that way. Resizing with:
super + alt + j
bspc window -e down +20 || bspc window -e up +20
Height: 536
H m 0.500000
Height: 516
H m 0.517241
Height: 496
H m 0.534483
Height: 476
H m 0.551724
Height: 456
H m 0.568966
Height: 437
H m 0.586207
Offline
Could someone help me with the bitmap fonts? I am using the uushi font for the BAR: https://github.com/phallus/fonts
Although I've installed it and am able to use it in my terminal (termite), and SE the glyphs in gbdfed. I am unable to use the glyphs that are in the high 2xxx hex codes, such as the battery and the headphones icon.
any ideas? (also using infinality bundle, don't know if that affect things)
Offline
Would anyone know why panel isn't displaying a panel when I startx, however when I go to run panel via cli, it says "The panel is already running."? When I killall panel and start it again, the panel shows up. Not sure what's going on here...
Offline
Would anyone know why panel isn't displaying a panel when I startx, however when I go to run panel via cli, it says "The panel is already running."? When I killall panel and start it again, the panel shows up. Not sure what's going on here...
check to see you actually have the font as described in config.h
Offline
Would anyone know why panel isn't displaying a panel when I startx, however when I go to run panel via cli, it says "The panel is already running."? When I killall panel and start it again, the panel shows up. Not sure what's going on here...
I had the same problem when installing bspwm yesterday. After you startx, quit BSPWM and you might see an error written after the Xorg stuff. For me, the problem was that the panel script had relative references to other scripts, which depended on the location you executed it from.
If there's no error, post your panel script(s) and bspwmrc.
Offline
id0827502 wrote:Would anyone know why panel isn't displaying a panel when I startx, however when I go to run panel via cli, it says "The panel is already running."? When I killall panel and start it again, the panel shows up. Not sure what's going on here...
check to see you actually have the font as described in config.h
I believe I do.
id0827502 wrote:Would anyone know why panel isn't displaying a panel when I startx, however when I go to run panel via cli, it says "The panel is already running."? When I killall panel and start it again, the panel shows up. Not sure what's going on here...
I had the same problem when installing bspwm yesterday. After you startx, quit BSPWM and you might see an error written after the Xorg stuff. For me, the problem was that the panel script had relative references to other scripts, which depended on the location you executed it from.
If there's no error, post your panel script(s) and bspwmrc.
Nothing when I quit bspwm. Just to be sure, I did a
cat /var/log/Xorg.0.log | grep EE
but nothing stood out.
Panel scripts and bspwmrc are stock standard from the examples folder except my bspwmrc file has
panel &
at the end of it.
Offline