bspwm — A tiling window manager based on binary space partitioning

psycho · 2013-09-17 14:05:41

earsplit wrote:

Do these return anything?
which panel
and
echo $PANEL_FIFO

Yes and yes.

http://s21.postimg.org/khft9giqd/2013_0 … _scrot.png

// Edit : upgraded to 3.11.1-1, rebooted, now works with

echo /tmp/panel-fifo | panel dzen2

I just have to modift the formatting and others. Thanks for your interest!

Last edited by psycho (2013-09-17 14:44:46)

Supplantr · 2013-09-17 15:20:13

The new --one-shot rule syntax was a good idea! However, the existence of multiple rules that match all clients causes bspwm to crash upon the creation of a new window. E.g.:

 1 * --floating
 2 * --unmanage

If multiple one-shot rules that match all clients exist, will they all be applied to the next window?
I think there could be some interesting possibilities in terms of "queuing" rules.

Also, if a one-shot rule is added (with a keybinding, for example), is there any way to remove it without knowing the uid?
It would be easy enough to awk the rule list, but maybe a --rm last option would be beneficial. (I assumed the long option counterpart to -r would be --remove. Is there a reason that's not the case?)

bloom · 2013-09-17 15:22:32

psycho wrote:

echo /tmp/panel-fifo | panel dzen2

This is equivalent to:

panel dzen2

Ploppz · 2013-09-17 18:23:03

Supplantr wrote:

Ploppz wrote:
~/.config/xinitrc
Doesn't look like you're executing bspwm...

aoba wrote:

[...]

Ohh, silly me! Fixed that and now when I run startx it doesn't go back to the bash shell but stays in xorg ( ? if that's correct use of words) - but it's all just black and I have no possibility of performing any action to get back to the shell. So don't know how to possibly troubleshoot this - please enlighten me

bloom · 2013-09-17 18:35:10

Supplantr wrote:

The new --one-shot rule syntax was a good idea! However, the existence of multiple rules that match all clients causes bspwm to crash upon the creation of a new window. E.g.:
 1 * --floating
 2 * --unmanage

Fixed, thanks for reporting.

Supplantr wrote:

If multiple one-shot rules that match all clients exist, will they all be applied to the next window?

Yes.

Supplantr wrote:

I think there could be some interesting possibilities in terms of "queuing" rules.

Could you elaborate?

Supplantr wrote:

Also, if a one-shot rule is added (with a keybinding, for example), is there any way to remove it without knowing the uid?

I've added the following keywords: tail, head.

Supplantr wrote:

I assumed the long option counterpart to -r would be --remove. Is there a reason that's not the case?

No, fixed.

Supplantr · 2013-09-17 21:14:37

Ploppz wrote:

Ohh, silly me! Fixed that and now when I run startx it doesn't go back to the bash shell but stays in xorg ( ? if that's correct use of words) - but it's all just black and I have no possibility of performing any action to get back to the shell. So don't know how to possibly troubleshoot this - please enlighten me

Did you follow @aoba's advice to add:

sxhkd &
exec bspwm

to .xinitrc? It really shouldn't be that difficult to get everything working. Look at the examples provided with bspwm and read sxhkd's documentation.

---

bloom wrote:

Could you elaborate?

Since every one-shot rule matching all clients will be removed when a new window is created, "queuing" rules isn't possible. It wouldn't be useful unless more window actions were supported, anyway.
Something similar to what I'm thinking of could probably be achieve using devilspie2.

bloom wrote:

I've added the following keywords: tail, head.

Thanks!
bspc rule -l \* doesn't work (which is the default behavior anyway, but <pattern> should probably support * everywhere).

Could a --locked rule be added? Maybe it would be a good idea to support all --toggle window options as rules, in which case perhaps their declaration should reflect the window command, i.e. bspc rule -a * -t locked.

Also, I'm assuming bspwm has no concept of minimized windows since xdotool getactivewindow windowminimize does nothing. Would this be difficult to implement? The utility of minimizing windows with a tiling WM might be questionable, but unmapping and remapping windows erases their locked (which is related to the above request), presel, etc. state. Plus, if the window were originally tiled, maybe a vacant node could be used to return it to its original position upon maximizing.

Stalafin · 2013-09-18 16:16:46

I have set up bspwm pretty much according to the example files in src/bspwm/examples/, and everything runs (nice WM btw). My only issue is: if I close bspwm, somehow the bar-aint-recursive process is not shut down correctly. The now orphaned (?) process is causing a CPU load of 100%. Restarting bspwm a new bar-instance is created which behaves fine, but the old one is still around causing said load. Any ideas how to check what's wrong?

The scripts are pretty much what was given in the examples, with the sole difference that I am using bar-aint-recursive-git, where the binary was changed to “bar-aint-recursive”. These are my configuration files:
$HOME/.xinitrc

#!/bin/zsh

if [ -d /etc/X11/xinit/xinitrc.d ]; then
  for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
  done
  unset f
fi

/usr/bin/xscreensaver -no-splash &
/home/janis/.local/bin/lightsOn.sh &
/usr/bin/xset r rate 250 30 &

xset +fp /usr/share/fonts/local 
xset fp rehash 

#exec xmonad

sxhkd &
[ -e "$PANEL_FIFO" ] && rm "$PANEL_FIFO"
mkfifo "$PANEL_FIFO"
exec bspwm -s "$PANEL_FIFO" -p W

$HOME/.config/bspwm/bspwmrc

#! /bin/sh

bspc desktop ^1 -n I
bspc monitor -a II III IV V VI VII VIII IX X

bspc rule -a Gimp -d ^8 --follow --floating
bspc rule -a Chromium -d ^2
bspc rule -a mplayer2 --floating
bspc rule -a Kupfer.py --focus
bspc rule -a Screenkey --unmanage

bspc config border_width        2
bspc config window_gap          12
bspc config split_ratio         0.52
bspc config borderless_monocle  true
bspc config gapless_monocle     true

panel &

$HOME/.local/bin/panel:

#! /bin/sh

trap 'trap - TERM; kill 0' INT TERM QUIT EXIT

flavor=${1:-bar}

bspc config top_padding $PANEL_HEIGHT
bspc control --put-status
xtitle -sf 'T%s' > "$PANEL_FIFO" &
clock -sf 'S%a %H:%M' > "$PANEL_FIFO" &

case "$flavor" in
    bar)
        cat "$PANEL_FIFO" | panel_bar | bar-aint-recursive &
        ;;
    dzen2)
        . panel_colors
        FONT_FAMILY='DejaVu Sans'
        FONT_SIZE=11
        cat "$PANEL_FIFO" | panel_dzen2 -f "$FONT_FAMILY" -s "$FONT_SIZE" | dzen2 -h $PANEL_HEIGHT -dock -ta l -title-name panel -fn "${FONT_FAMILY}:pixelsize=${FONT_SIZE}" -fg "$COLOR_FOREGROUND" -bg "$COLOR_BACKGROUND" &
        ;;
esac

wait

#! /bin/sh
#
# Example panel for LemonBoy's bar

while read -r line ; do
    case $line in
        S*)
            sys_infos="\\r\\f5${line#?}\\fr"
            ;;
        T*)
            title="\\c${line#?}"
            ;;
        W*)
            wm_infos=""
            IFS=':'
            set -- ${line#?}
            while [ $# -gt 0 ] ; do
                item=$1
                name=${item#?}
                case $item in
                    [OFU]*)
                        # active desktop
                        wm_infos="$wm_infos \\u5\\b2\\f9${name}\\fr\\br\\ur"
                        ;;
                    o*)
                        # inactive but occupied desktop
                        wm_infos="$wm_infos \\f7${name}\\fr"
                        ;;
                    f*)
                        # inactive desktop
                        wm_infos="$wm_infos ${name}"
                        ;;
                    u*)
                        # urgent desktop
                        wm_infos="$wm_infos \\b3\\f0${name}\\fr\\br"
                        ;;
                    L*)
                        # layout
                        layout=$(printf "%s" "${name}" | sed 's/\(.\).*/\U\1/')
                        wm_infos="$wm_infos \\b4\\f0$layout\\br\\fr"
                        ;;
                esac
                shift
            done
            ;;
    esac
    printf "%s\n" "$wm_infos $title $sys_infos"
done

bloom · 2013-09-18 18:57:59

Stalafin wrote:

My only issue is: if I close bspwm, somehow the bar-aint-recursive process is not shut down correctly.

How do you “close” bspwm?

F34R · 2013-09-18 19:03:20

Stalafin #607

Same thing i have , heavy load in one core of cpu . bar n process duplicate , after kill 2nd work as well. Other Issue: I spawn the terminal and doeasn't fit to bar, also other application show wrong.

effae · 2013-09-18 20:38:07

bloom wrote:

Stalafin wrote:
My only issue is: if I close bspwm, somehow the bar-aint-recursive process is not shut down correctly.
How do you “close” bspwm?

I have the exact same problem, and I'm closing it with the standard shortcut keys from the sxhkd git example config.

bloom · 2013-09-18 20:50:39

effae wrote:

bloom wrote:
Stalafin wrote:
My only issue is: if I close bspwm, somehow the bar-aint-recursive process is not shut down correctly.
How do you “close” bspwm?
I have the exact same problem, and I'm closing it with the standard shortcut keys from the sxhkd git example config.

You could try the following instead:

super + alt + Escape
    pkill -x panel; bspc quit

Supplantr · 2013-09-19 03:33:31

Commit afcbf47 causes problems with Skype. It seems like its chat windows are not updated unless the desktop containing said windows has focus. When I give that desktop focus, all unseen chat messages appear to "pop" into the window at the same time. The problem is that the chat windows are not requesting the urgent state to be set.

Hspasta · 2013-09-19 05:50:43

I took the most recent example of panel_bar and panel and the output for bspwm's internal state doesn't show besides what tiling mode it is: http://i.imgur.com/aqgExgg.png

I see these:

WMHDMI-0:d1:d2:D3:E4:E5:E6:E7:E8:E9:E0:Ltiled
WMHDMI-0:d1:d2:D3:E4:E5:E6:E7:E8:E9:E0:Ltiled

in the PANEL_FIFO which doesn't seem to correspond with the case statements in panel_bar.

Supplantr · 2013-09-19 07:08:01

@Hspasta
The state output syntax changed. Build the latest version of bspwm from git.

effae · 2013-09-19 09:06:33

bloom wrote:

effae wrote:
bloom wrote:
How do you “close” bspwm?
I have the exact same problem, and I'm closing it with the standard shortcut keys from the sxhkd git example config.
You could try the following instead:
super + alt + Escape
    pkill -x panel; bspc quit

This fixes it, thanks.

blue · 2013-09-19 11:33:47

Hi

how can i switch between the tags/workspaces .
In awesome wm i did "super+left/right"

andornaut · 2013-09-19 12:49:00

blue wrote:

how can i switch between the tags/workspaces .
In awesome wm i did "super+left/right"

Switch to desktop # 1:

bspc desktop -f ^1

Switch to the desktop/tag named "web":

bspc desktop -f web

Bind "switch to desktop # 0-9" to a shortcut key combination in sxhkd:

 mod4 + {1-9,0}
     bspc desktop -f ^{1-9,0}

All of this is documented

bloom · 2013-09-19 12:55:23

blue wrote:

Hi
how can i switch between the tags/workspaces .
In awesome wm i did "super+left/right"

super + {Left,Right}
    bspc desktop -f {prev,next}

bloom · 2013-09-19 12:57:40

andornaut wrote:

mod4 + {1-9,0}
    bspc desktop -f ^{1-9,0}

super + {1-9,0}
    bspc desktop -f ^{1-9,10}

jdarnold · 2013-09-19 13:15:31

I'm having the same problem as Ploppz - I've added sxhkd & bspwm to my .xinitrc and all I get is a black screen. The only slightly unusual setup for me is a dual monitor using nVidia's proprietary drivers.

I'm using the bspwm package, not -git, if it matters.

blue · 2013-09-19 13:32:25

bloom wrote:

blue wrote:
Hi
how can i switch between the tags/workspaces .
In awesome wm i did "super+left/right"
super + {Left,Right}
    bspc desktop -f {prev,next}

THX! Sometimes it is too easy....

Stalafin · 2013-09-19 13:52:27

bloom wrote:

effae wrote:
bloom wrote:
How do you “close” bspwm?
I have the exact same problem, and I'm closing it with the standard shortcut keys from the sxhkd git example config.
You could try the following instead:
super + alt + Escape
    pkill -x panel; bspc quit

That did it! Thanks.

I want to report another thing I noticed, which has to do with running two screens:
My Laptop is attached to an external monitor via a docking station. At start-up, the laptop's TFT shows a small portion (the top left part) of the external screen. Also, windows are not expanded to encompass the entire external screen, but only the part that fits the TFT is used. You can see this in the picture below:

After turning the laptop's screen off with xrandr, the enumeration of the virtual desktops gets changed: look at the bar in the top left. “Desktop02” (I don't know, why it's called that) is now accessible via Super+1, while “I” is accessible via Super+2, etc. Before xrandr, Super+1 corresponded to “1”, as it should. This is what I see right after issuing the command.

The now second virtual desktop called “I” now contains the terminal opened before:

Any ideas what's going on here?

Last edited by Stalafin (2013-09-19 16:13:26)

Nindwen · 2013-09-19 14:07:00

With sxhkd, is there a way to easily use one key to cycle through multiple actions? For example, if I wanted to bind key to toggle something.

I'm thinking something like this:

super + something
    { bspc desktop -f pad,
      bspc desktop -f last }

WonderWoofy · 2013-09-19 15:21:08

@Stalafin, you have been around here since 2007 and should know by now that those pictures are far, far too large for these threads. You need to post those on some kind of picture hosting site and then link to them from here. You can also create thumbnails and do some fancy tag nesting to make a thumbnail link to your image.

ewaller · 2013-09-19 15:29:12

WonderWoofy wrote:

@Stalafin, you have been around here since 2007 and should know by now that those pictures are far, far too large for these threads. You need to post those on some kind of picture hosting site and then link to them from here. You can also create thumbnails and do some fancy tag nesting to make a thumbnail link to your image.

Yes, they are. In general, I don't care about the size in pixels; I care about the size in Bytes. Please fix those, or convert them from img to url. Moderators often do that for newbies, but I think you can handle it

Arch Linux

#601 2013-09-17 14:05:41

Re: bspwm — A tiling window manager based on binary space partitioning

#602 2013-09-17 15:20:13

Re: bspwm — A tiling window manager based on binary space partitioning

#603 2013-09-17 15:22:32

Re: bspwm — A tiling window manager based on binary space partitioning

#604 2013-09-17 18:23:03

Re: bspwm — A tiling window manager based on binary space partitioning

#605 2013-09-17 18:35:10

Re: bspwm — A tiling window manager based on binary space partitioning

#606 2013-09-17 21:14:37

Re: bspwm — A tiling window manager based on binary space partitioning

#607 2013-09-18 16:16:46

Re: bspwm — A tiling window manager based on binary space partitioning

#608 2013-09-18 18:57:59

Re: bspwm — A tiling window manager based on binary space partitioning

#609 2013-09-18 19:03:20

Re: bspwm — A tiling window manager based on binary space partitioning

#610 2013-09-18 20:38:07

Re: bspwm — A tiling window manager based on binary space partitioning

#611 2013-09-18 20:50:39

Re: bspwm — A tiling window manager based on binary space partitioning

#612 2013-09-19 03:33:31

Re: bspwm — A tiling window manager based on binary space partitioning

#613 2013-09-19 05:50:43

Re: bspwm — A tiling window manager based on binary space partitioning

#614 2013-09-19 07:08:01

Re: bspwm — A tiling window manager based on binary space partitioning

#615 2013-09-19 09:06:33

Re: bspwm — A tiling window manager based on binary space partitioning

#616 2013-09-19 11:33:47

Re: bspwm — A tiling window manager based on binary space partitioning

#617 2013-09-19 12:49:00

Re: bspwm — A tiling window manager based on binary space partitioning

#618 2013-09-19 12:55:23

Re: bspwm — A tiling window manager based on binary space partitioning

#619 2013-09-19 12:57:40

Re: bspwm — A tiling window manager based on binary space partitioning

#620 2013-09-19 13:15:31

Re: bspwm — A tiling window manager based on binary space partitioning

#621 2013-09-19 13:32:25

Re: bspwm — A tiling window manager based on binary space partitioning

#622 2013-09-19 13:52:27

Re: bspwm — A tiling window manager based on binary space partitioning

#623 2013-09-19 14:07:00

Re: bspwm — A tiling window manager based on binary space partitioning

#624 2013-09-19 15:21:08

Re: bspwm — A tiling window manager based on binary space partitioning

#625 2013-09-19 15:29:12

Re: bspwm — A tiling window manager based on binary space partitioning

Board footer