bspwm — A tiling window manager based on binary space partitioning

bloom · 2013-01-05 09:50:48

findus28 wrote:

I cannot simply refocus the window below the cursor by moving the mouse.

Unfortunately, focus_follows_mouse is based on enter notify events and not on motion notify events.

I'll see if I can fix this once I'm done with sxhkd.

findus28 · 2013-01-05 19:19:35

Alright. Thank you for having a look a it.

One more question: On the root window the cursor always appears as a black cross. Is this the intended behavior or is there a problem with my configuration?

bloom · 2013-01-05 19:39:49

findus28 wrote:

One more question: On the root window the cursor always appears as a black cross. Is this the intended behavior or is there a problem with my configuration?

You can change the aspect of the pointer over the root window with xsetroot.

You could add this line in you ~/.xinitrc for example:

xsetroot -cursor_name left_ptr

cippaciong · 2013-01-06 10:40:37

I'm trying to use bspwm but whenever I run bspc I get this error:

failed to connect to socket

This obviously affects also sxhkd wm-related shortcuts which are not working at all.

bloom · 2013-01-06 11:26:50

cippaciong wrote:

I'm trying to use bspwm but whenever I run bspc I get this error:
failed to connect to socket

What's the output of

    ls -l /tmp/bspwm-socket "$BSPWM_SOCKET"

?

cippaciong · 2013-01-06 13:43:41

bloom wrote:

cippaciong wrote:
I'm trying to use bspwm but whenever I run bspc I get this error:
failed to connect to socket
What's the output of
    ls -l /tmp/bspwm-socket "$BSPWM_SOCKET"
?

ls: cannot access /tmp/bspwm-socket: No such file or directory
ls: cannot access /tmp/bspwm-socket: No such file or directory

P.S. BSPWM_SOCKET is set to /tmp/bspwm-socket in my .xinitrc just to avoid the relative warning.

Last edited by cippaciong (2013-01-06 14:24:48)

bloom · 2013-01-06 17:40:10

cippaciong wrote:

ls: cannot access /tmp/bspwm-socket: No such file or directory

I've added some error checking code to the server: normally bspwm should now fail with a socket related error if you try to run it.

Last edited by bloom (2013-01-06 17:47:51)

bloom · 2013-01-06 17:47:19

I have removed the code related to the mouse bindings. You now have to define those bindings via sxhkd.

Example:

super + @button{1,2,3}
    bspc mouse {move,focus,resize}

The mouse actions are entered and left by mouse released events.

cippaciong · 2013-01-06 18:26:06

bloom wrote:

cippaciong wrote:
ls: cannot access /tmp/bspwm-socket: No such file or directory
I've added some error checking code to the server: normally bspwm should now fail with a socket related error if you try to run it.

I think the problem was that xinit actually started X (wallpaper too) but not bspwm. I managed to open a terminal and run bspwm manually. How should I run bspwm from .xinitrc? I used

exec bspwm

but I saw in your dotfiles that you use the "wm" script

bloom · 2013-01-06 20:26:06

cippaciong wrote:

exec bspwm

That should work fine.

I mentioned the wm script and its purpose here.

bloom · 2013-01-08 17:28:58

sxhkd is now required to be able to trigger the track_pointer message.

You might want to use the following hotkeys in sxhkdrc:

super + button{1,2,3}
    bspc grab_pointer {move,focus,resize}

super + !button{1,3}
    bspc {track_pointer,track_pointer} %i %i

super + @button{1,3}
    bspc {ungrab_pointer,ungrab_pointer}

focus_follows_mouse is now known as focus_follows_pointer and is based on pointer motion events, which should fix the last reported issue regarding this setting.

findus28 · 2013-01-10 15:29:03

bloom wrote:

You can change the aspect of the pointer over the root window with xsetroot.
You could add this line in you ~/.xinitrc for example:
xsetroot -cursor_name left_ptr

Thank you, that’s really useful information.

I have just updated bspwm and started to use sxhkd. The new "focus_follows_pointer" setting works perfectly e.g. for multiple rxvt-unicode windows, but it behaves like the old "focus_follows_mouse" setting e.g. with a Thunderbird window and the corresponding address book. Apart from that, I love to see bspwm impoving so fast.

bloom · 2013-01-21 10:51:53

findus28 wrote:

The new "focus_follows_pointer" setting works perfectly e.g. for multiple rxvt-unicode windows, but it behaves like the old "focus_follows_mouse" setting e.g. with a Thunderbird window and the corresponding address book.

As stated in the commit comment, I'm aware of that problem.

It can be reproduced with zenity:

Launch a terminal window.
Issue zenity --question.
Put the pointer inside the zenity window.
Give the focus back to the terminal window (by using the keyboard).
Move the pointer inside the zenity window.

What happens is that zenity is not allowing other clients to receive pointer events (i.e. the owner_events of the grab is 0), and no enter notify events are generated.

There might also be a bug in X itself:
https://bugs.freedesktop.org/show_bug.cgi?id=54238

bloom · 2013-01-21 10:58:42

The compton-shadow branch was merged into master.

The apply_shadow_property will only have an effect if compton is launched with the --respect-prop-shadow option.

I recommend to use the richardgv-dev branch of compton.

rennis250 · 2013-01-25 21:28:31

I'm very intrigued by bspwm, but I'm have a lot of difficulty with starting it. Here is my setup:

-Using your default bspwm_autostart (saved as /home/rje/.config/bspwm/autostart). I commented any lines that called applications that I do not have installed.

-Using your wm script (called in .xinitrc like so: "exec /home/rje/bin/wm")

-Using your default sxhkdrc.

bspwm and sxhkdrc are installed via owl.

When I start X, I am left with a blank screen, aside from my background that is set with bgs, and there is no mouse pointer to be seen.

BTW, I really like your work. Very well designed and pleasant to use. Awesome job! (Nice website, too!)

--Rob

taylorchu · 2013-01-25 23:05:10

@rennis250
same problem here.

@bloom
great work. but bspwm really needs a good documentation and manual.

bloom · 2013-01-26 10:21:36

@rennis250 and @taylorchu:

Please try with

An empty autostart.
A simple .xinitrc:
```
sxhkd &
exec bspwm
```

taylorchu · 2013-01-26 19:08:23

still does not work
what is default keybind that I should test on?
what will see if one starts bspwm?

bloom · 2013-01-26 19:27:19

taylorchu wrote:

still does not work

No mouse pointer?

taylorchu wrote:

what is default keybind that I should test on?

You should make your own based on the one mentioned in bspwm's README.

taylorchu wrote:

what will see if one starts bspwm?

Nothing besides your mouse pointer.

rennis250 · 2013-01-26 19:35:12

It must have been working all along, but I was pressing the wrong key combo to start my terminal. All good here! Thanks, bloom!

@taylorchu, make sure to edit the following line in sxhkdrc:

super + ctrl + Return
{urxvtc, urxvtc cd $incoming}

This should be changed to your default terminal. For example,

super + ctrl + Return
{xterm}

Then, make sure that sxhkdrc is in ~/.config/sxhkd and autostart is in ~/.config/bspwm. The sxhkdrc and autostart files should NOT have a "." at the beginning of their filenames.

I've found that when bspwm is started, I receive a blank screen with no mouse pointer, but once a terminal is opened, the mouse pointer appears. This might lead others to believe that the window manager isn't working.

NOTE: Also, make sure that the XDG_CONFIG_HOME envirnoment variable is properly defined and exported at login.

--Rob

Last edited by rennis250 (2013-01-26 19:36:27)

bloom · 2013-01-26 20:01:42

rennis250 wrote:

@taylorchu, make sure to edit the following line in sxhkdrc:
super + ctrl + Return
{urxvtc, urxvtc cd $incoming}

Actually:

super + ctrl + {slash,shift + slash}
    {urxvtc,urxvtc -cd "$HOME/incoming"}

rennis250 wrote:

This should be changed to your default terminal. For example,
super + ctrl + Return
{xterm}

This should be:

super + ctrl + Return
    xterm

taylorchu · 2013-01-26 20:39:01

@bloom
super + ctrl + Return
xterm
saves me.

btw, how do you use manual mode by default?

rennis250 · 2013-01-26 21:59:55

Curious... using {xterm} works here. Although, I corrected it and removed the curly brackets (apologies for the typos). Perhaps curly brackets around a single term should be registered as a syntax error, since it's an ambiguity to the parser?

--Rob

bloom · 2013-01-27 09:57:08

taylorchu wrote:

btw, how do you use manual mode by default?

I don't see how the manual mode could be used by default: it is entered by specifying where the next window should appear.

bloom · 2013-01-27 10:01:17

rennis250 wrote:

Perhaps curly brackets around a single term should be registered as a syntax error

No they shouldn't:

bash -c 'echo {0..10}'

Arch Linux

#51 2013-01-05 09:50:48

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

#52 2013-01-05 19:19:35

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

#53 2013-01-05 19:39:49

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

#54 2013-01-06 10:40:37

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

#55 2013-01-06 11:26:50

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

#56 2013-01-06 13:43:41

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

#57 2013-01-06 17:40:10

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

#58 2013-01-06 17:47:19

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

#59 2013-01-06 18:26:06

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

#60 2013-01-06 20:26:06

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

#61 2013-01-08 17:28:58

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

#62 2013-01-10 15:29:03

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

#63 2013-01-21 10:51:53

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

#64 2013-01-21 10:58:42

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

#65 2013-01-25 21:28:31

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

#66 2013-01-25 23:05:10

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

#67 2013-01-26 10:21:36

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

#68 2013-01-26 19:08:23

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

#69 2013-01-26 19:27:19

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

#70 2013-01-26 19:35:12

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

#71 2013-01-26 20:01:42

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

#72 2013-01-26 20:39:01

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

#73 2013-01-26 21:59:55

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

#74 2013-01-27 09:57:08

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

#75 2013-01-27 10:01:17

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

Board footer