bspwm — A tiling window manager based on binary space partitioning

bloom · 2013-07-30 13:08:02

ict wrote:

bloom wrote:
No.
It's due to the rough approach I've taken for the implementation of the z-order.
OK thanks, it's not a big deal.
Still, do you have plans to support this one day?

Yes.

bloom · 2013-07-30 13:14:14

Supplantr wrote:

Three things I've noticed:
bspc {restore,control,pointer,rule} don't exit with status 1 when called without options, while the other commands do.
When bspc rule -a fails (and no rule is actually added), the UID counter is still incremented.
In the documentation for WINDOW_SEL, the automatic and manual modifiers are missing.

Fixed.

Supplantr wrote:

Just wondering, has any more thought been put into/progress been made regarding the possible tagging implementations?

Not really, but if I had to implement tags, I'd go for the tags on top of desktops approach.

bloom · 2013-07-30 13:18:39

One user reached me by email to report an issue: he can't make bspwm work with LXDM.

Has anyone manage to do so?

Supplantr · 2013-07-31 01:08:12

bloom wrote:

Not really, but if I had to implement tags, I'd go for the tags on top of desktops approach.

You don't have to implement tags, but I can't be alone in thinking they'd be quite useful. Plus, bspwm could then be touted as "the only manual/hybrid tiling window manager with a tagging mechanism."

One more single-line documentation fix: the overlapping borders example uses the old syntax for monitor padding.

Ypnose · 2013-08-02 13:55:21

bloom: My question seems to be precipitate, but do you plan to support Wayland when it'll be out? I mean you're using xcb, (which seems to be supported by wayland), that's why I was curious.

bloom · 2013-08-03 07:26:03

Ypnose wrote:

My question seems to be precipitate, but do you plan to support Wayland when it'll be out?

Yes, I'm interested in Wayland. It has a slim API compared to X and it might solve the aesthetic bug present in every tiler: flickering.

Ypnose wrote:

you're using xcb, (which seems to be supported by wayland)

What do you mean by supported by?

bloom · 2013-08-03 08:08:31

Supplantr wrote:

One more single-line documentation fix: the overlapping borders example uses the old syntax for monitor padding.

Fixed.

Ypnose · 2013-08-03 09:38:37

bloom wrote:

What do you mean by supported by?

Hum sorry, that was ambiguous. I'm not involved in X development but it appears to me that Xlib calls are "incompatible" or problematic with Wayland.
Many Xlib applications are moving to XCB (I'm thinking to KWin).

Earnestly · 2013-08-03 10:04:46

bloom wrote:

Yes, I'm interested in Wayland.

You might be interested in Forney's work:
http://lists.freedesktop.org/archives/w … 10375.html

Iao · 2013-08-04 04:10:21

bloom wrote:

Ypnose wrote:
My question seems to be precipitate, but do you plan to support Wayland when it'll be out?
Yes, I'm interested in Wayland. It has a slim API compared to X and it might solve the aesthetic bug present in every tiler: flickering.

I was actually just about to ask the same thing. This is great to know!

tbuck153 · 2013-08-06 12:43:55

What happened to being able to move a window into the preselected area? I just updated bspwm and sxhkd and it seems that I can't do this anymore.

If I'm not making sense - What I'm talking about is when you swap a window with a window that has a presel, instead of swapping it used to insert the window into the presel area.

Let me know if I'm just missing something. Also, I love this window manager. Good work man. As far as the dwm style tagging... that would be AWESOME.

Last edited by tbuck153 (2013-08-06 12:46:47)

bloom · 2013-08-06 17:20:07

tbuck153 wrote:

What happened to being able to move a window into the preselected area?

The new way for doing this is:

bspc window -w last.manual

earsplit · 2013-08-06 22:14:08

Just got this up and running. I already know it will be replacing XMonad for me. I'll be back with questions I'm sure, but my workflow is already exactly the same. Great work. This program is most unix-like WM i've ever used.

Ledti · 2013-08-10 00:41:21

This is a very nice window manager. I've been messing around with it and I have a few questions.

Is there a way to apply settings to windows/desktops specifically with rules? For instance, I would like to apply these options only to Chromium/the desktop which Chromium resides:

borderless_monocle true
gapless_monocle true

And on that note, is there a way to more accurately define the <pattern> for rules? i3 has this nailed with its syntax which is described here.

edit: Also, is there a way to sticky windows across all/multiple desktops? In my use case if would be for a floating mplayer window.

Last edited by Ledti (2013-08-10 01:56:52)

bloom · 2013-08-10 12:03:09

Ledti wrote:

Is there a way to apply settings to windows/desktops specifically with rules?

Right now, all settings are global.

Ledti wrote:

And on that note, is there a way to more accurately define the <pattern> for rules?

There isn't and it's intended: applying rules is a separate task and should be accomplished by a separate program.

Please checkout devilspie2.

Ledti wrote:

Also, is there a way to sticky windows across all/multiple desktops?

Not yet, but the feature is scheduled.

china · 2013-08-11 12:46:10

I'm loving this wm, but I'm having a few issues on my laptop's install; it seems like sxhkd isn't quite function as it should. I'm using the example config, but pretty much all the binds seem to not work and I'm not sure how to start looking for what's wrong.
a binding to open dwb with super + BackSpace is working for sure, anything else doesn't seem to register.

Edit: I seem to have fixed it by removing the 4 spaces prefixing commands in sxhkdrc, and substituting them with my own 4 spaces. I've no idea why that happened.

Last edited by china (2013-08-11 13:48:32)

Ypnose · 2013-08-11 20:32:11

bloom wrote:

Yes, I'm interested in Wayland. It has a slim API compared to X and it might solve the aesthetic bug present in every tiler: flickering

I forgot to tell you it's a good news, because I was a bit worried to find a WM which supports natively Wayland (without using XWayland I mean).
I'll also probably switch to bspwm (from dwm) in the following weeks.

Last edited by Ypnose (2013-08-11 20:32:54)

bloom · 2013-08-12 09:54:02

Kaustic wrote:

bloom wrote:
Yes, I'm interested in Wayland.
You might be interested in Forney's work:
http://lists.freedesktop.org/archives/w … 10375.html

Thanks, in fact, I had heard about this on the suckless mailing list.

After having read the discussion that followed, I've come to the following conclusions:

A wm is called a shell in the Wayland terminology.
I must find/modify/write a compositor because I need to have a fine grained control upon the window borders.

I found clayland and I will probably have a close look at it.

Ypnose · 2013-08-12 10:04:01

baskerville: I would be very interested to "follow" the development. I found nothing on your personal blog, do you write something elsewhere?

Earnestly · 2013-08-12 12:23:29

There's quite a few misnomers with Wayland[1].

Just like we call it (XFree86 ->) Xorg and not X. We call it Xephyr and not X.
Both of those (and many more) are implementations of the X protocol[2].
Just like Wayland is a protocol[3], thus Weston is an implementation.

The concept of "Window Managers" while still possible with some middleman
wl_shell proxy, is mostly vestigial.

Even "Window Managers" in Xorg was a bit of an oddity at the time.
Window Managers as you think of them today would be loosely translated to a
"Compositor" which implements the Wayland protocol.

The reference compositor, Weston, can accept plugins to change the desktop[4]
paradigm which controls how the things are arranged and laid out (yes, in
theory a tiling plugin .so can be created for Weston).

The default Weston plugin is called desktop-shell.so[5][6].
There is also another plugin I am sure you've all heard of as well: xwayland.so
which runs a rootless X server under Weston[7].

[1] https://www.youtube.com/watch?v=RIctzAQOe44
[2] http://www.x.org/docs/XProtocol/proto.pdf
[3] http://wayland.freedesktop.org/docs/htm … tocol.html
[4] http://vignatti.com/2013/03/05/ui-custo … n-wayland/
[5] http://cgit.freedesktop.org/wayland/wes … rc/shell.c
[6] http://cgit.freedesktop.org/wayland/wes … /notes.txt
[7] http://cgit.freedesktop.org/wayland/wes … c/xwayland

Useful links:
https://plus.google.com/100409717163242445476/posts (Kristian Høgsberg)
https://plus.google.com/112891790407866414198/posts (Daniel Stone)
https://plus.google.com/104877287288155269055/posts (David Airlie)
http://cgit.freedesktop.org/wayland (The source code is fairly wonderful, very
clean and easy to read in my opinion.)

Last edited by Earnestly (2013-08-12 12:40:29)

Mindstormscreator · 2013-08-14 22:58:45

I'm trying to get the Kupfer launcher to work in bspwm. In my .xinitrc, I preload it:

kupfer --no-splash &

I have it bound to a shortcut with sxhkd:

alt + r
        kupfer

And yet when I launch it, the window must be focused with the mouse in order to accept keyboard input. I tried using xdo to manually focus it:

xdo activate -n kupfer

and

xdo activate -n Kupfer

but I still can't focus it.

In openbox, kupfer is focused on launch.

Is this a bug?

Last edited by Mindstormscreator (2013-08-14 23:00:36)

bloom · 2013-08-15 07:59:55

Add this to your bspwmrc:

bspc rule -a Kupfer.py --focus

Mindstormscreator · 2013-08-15 14:29:15

bloom wrote:

Add this to your bspwmrc:
bspc rule -a Kupfer.py --focus

Thanks, worked great.

verm1n · 2013-08-15 15:08:00

Hello Baskerville,
I am trying to use your wm. I have set up sxhkd and those bindings work but I am unable to get my bspwm config to execute (tt1 shows error message: "couldn't execute configuration file") though the wm starts fine.

alxndr@alxndr-e420:~/.config/bspwm$ ls -l
total 0
-rw-r--r-- 1 alxndr alxndr 0 Aug 14 13:55 bspwmrc

my bspwmrc is empty just to be safe(besides sh of course):

#! /bin/sh

My xinitrc

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)



if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
	eval 'dbus-launch --sh-syntax --exit-with-session'
fi

export XDG_CONFIG_HOME="$HOME/.config"

eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)
export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT SSH_AUTH_SOCK

/usr/bin/gnome-keyring-daemon --start --components=gpg
/usr/bin/gnome-keyring-daemon --start --components=pkcs11
/usr/bin/gnome-keyring-daemon --start --components=secrets
/usr/bin/gnome-keyring-daemon --start --components=ssh

# exec gnome-session
# exec startkde
# exec startxfce4
# exec wmaker
# exec icewm
# exec blackbox
# exec
sxhkd & 
exec bspwm
#exec ck-launch-session dbus-launch openbox-session
#exec bspwm -s /tmp/bspwm-sock
# ...or the Window Manager of your choice

#exec ratpoison

finally my .profile

# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022

export XDG_CONFIG_HOME="$HOME/.config"
export XDG_DATA_HOME="$HOME/.local/share"

export BSPWM_SOCKET=/tmp/bspwm-socket
export BSPWM_TREE="$XDG_DATA_HOME/bspwm.tree"
export BSPWM_HISTORY="$XDG_DATA_HOME/bspwm.history"



# if running bash
if [ -n "$BASH_VERSION" ]; then
    # include .bashrc if it exists
    if [ -f "$HOME/.bashrc" ]; then
	. "$HOME/.bashrc"
    fi
fi

# include sbin in PATH
if [ -d "/sbin" ] ; then
    PATH="/sbin:$PATH"
fi
if [ -d "/usr/sbin" ] ; then
    PATH="/usr/sbin:$PATH"
fi
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

bloom · 2013-08-15 18:54:59

verm1n wrote:

I am unable to get my bspwm config to execute (tt1 shows error message: "couldn't execute configuration file") though the wm starts fine.

chmod 755 ~/.config/bspwm/bspwmrc

Arch Linux

#401 2013-07-30 13:08:02

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

#402 2013-07-30 13:14:14

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

#403 2013-07-30 13:18:39

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

#404 2013-07-31 01:08:12

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

#405 2013-08-02 13:55:21

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

#406 2013-08-03 07:26:03

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

#407 2013-08-03 08:08:31

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

#408 2013-08-03 09:38:37

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

#409 2013-08-03 10:04:46

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

#410 2013-08-04 04:10:21

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

#411 2013-08-06 12:43:55

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

#412 2013-08-06 17:20:07

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

#413 2013-08-06 22:14:08

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

#414 2013-08-10 00:41:21

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

#415 2013-08-10 12:03:09

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

#416 2013-08-11 12:46:10

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

#417 2013-08-11 20:32:11

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

#418 2013-08-12 09:54:02

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

#419 2013-08-12 10:04:01

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

#420 2013-08-12 12:23:29

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

#421 2013-08-14 22:58:45

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

#422 2013-08-15 07:59:55

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

#423 2013-08-15 14:29:15

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

#424 2013-08-15 15:08:00

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

#425 2013-08-15 18:54:59

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

Board footer