You are not logged in.
The focus_by_distance setting will probably become the default because:
It allows to reach windows in less steps.
It works with floating windows.
Example:
+-----------+-----------+
| | |
| | b |
| | |
| |___________|
| | |
| a | c |
| * | |
| |___________|
| | |
| | d |
| | |
+-----------+-----------+
Bellow is a summary of the number of steps required to reach b, c and d with a as a starting point:
focus_by_distance steps mean variance
---------------------------------------------------------------
false 1, 2, 3 2 2/3
true 2, 1, 2 5/3 2/9
Last edited by bloom (2013-07-12 09:44:11)
Offline
I'm having a strange problem with bspwm and browsers. If I try to insert some text in firefox, typing some letters clears out the text I've already written. I noticed this mainly in username and password or search input fields, not sure if this affects also othere input fields; the only way I have to write something there is to copy/paste .
Initially I thought it was a firefox/vimperator problem but then the same behavior occurred also with dwb and chromium. If I use i3wm instead of bspwm I don't have this problem.
Offline
If I try to insert some text in firefox, typing some letters clears out the text I've already written.
Sounds like this issue I experienced with sxhkd's chord mechanism. The same would happen in chromium, but only with certain input fields.
The issue was fixed in commit 903c6bb. My first question would be: are you using the latest git build?
I use linux and I dont understand nothing in this post.
Offline
I do have one issue to report so far: when bspc window last --swap focused is used to swap a window into a preselected area, the window that is moved (last) gains focus, but the window that was preselected (focused) keeps input focus, i.e. input still goes to this window. This is resolved after focusing the original window.
Fixed by 83a17bb.
Offline
The focus_by_distance setting will probably become the default
I think this is a good idea, especially considering the reasons you provided.
Fixed by 83a17bb.
It works.
This may be a foolish question, but are the commands listed below supposed to be equivalent?
bspc window last -f -s focused
bspc window last -s focused -f
bspc window -f last -s focused
Each has a different end result.
I use linux and I dont understand nothing in this post.
Offline
cippaciong wrote:If I try to insert some text in firefox, typing some letters clears out the text I've already written.
Sounds like this issue I experienced with sxhkd's chord mechanism. The same would happen in chromium, but only with certain input fields.
The issue was fixed in commit 903c6bb. My first question would be: are you using the latest git build?
Upgrading sxhkd solved the problem. Thank you
Offline
This may be a foolish question, but are the commands listed below supposed to be equivalent?
bspc window last -f -s focused bspc window last -s focused -f bspc window -f last -s focused
Each has a different end result.
The target of the command is specified by the optional first argument and defaults to the focused window.
The last two commands shall have the same end result.
Messages are parsed and executed from left to right, so the focused window selection is altered by the -f action.
Offline
The monitor_focus_fallback setting was removed: the following commands are sufficient:
monitor -f DIR
window -m DIR [-f]
The -s action now only swap nodes (as it should). If you need to transplant, use -w.
Last edited by bloom (2013-07-13 08:13:26)
Offline
The -s action now only swap nodes (as it should). If you need to transplant, use -w.
How is -w supposed to behave when the given window isn't preselected?
It seems to act strangely in some cases. For instance, if two windows exist side by side (and neither are preselected), using -w left on the right window achieves the same effect as -s left, but using -w right on the left window does nothing.
I use linux and I dont understand nothing in this post.
Offline
bloom wrote:The -s action now only swap nodes (as it should). If you need to transplant, use -w.
How is -w supposed to behave when the given window isn't preselected?
Here's what transplantation does: it removes the node from the tree and re-inserts it at the given node.
Not sure how useful it might be when the destination window is not in manual mode though.
But the point is: swapping and transplantation are different concepts and should not collide.
Offline
But the point is: swapping and transplantation are different concepts and should not collide.
This makes sense. It's a bit unfortunate that a new set a hotkeys is required to fully utilize preselections, though.
---
Neither monitor -f DIR nor window -m DIR are working for me. They both simply fail with an exit code of 1. However, I am able to cycle between monitors with next|prev.
Also, are the *_padding settings even necessary? Can't the same be achieved with monitor -p?
I use linux and I dont understand nothing in this post.
Offline
bloom wrote:But the point is: swapping and transplantation are different concepts and should not collide.
This makes sense. It's a bit unfortunate that a new set of hotkeys is required to fully utilize preselections, though.
Stebalien suggests:
bspc window -w last.manual
And also provides a squish script.
Last edited by bloom (2013-07-15 10:55:08)
Offline
Hey guys, I think I have not understood the desktops so right. Can I add that while I run bspwm? If that is so, then it does not work here. And if not, how can I define desktops before running?
Last edited by Neuromatic (2013-07-14 11:39:17)
/* No Comment */
Offline
Offline
Does this not work?
Oh nice yes . Thank you dude.
But there is one more problem. How do I use --put-status? If I want to print the FIFO, my bar is still empty…
Last edited by Neuromatic (2013-07-14 23:05:07)
/* No Comment */
Offline
But there is one more problem. How do I use --put-status? If I want to print the FIFO, my bar is still empty…
You don't need to do this, the internal state is automatically written to the FIFO whenever it changes.
bspc control --put-status is only used once, when launching the panel.
Have you checked out the examples in examples/panel?
What's your .xinitrc?
Last edited by bloom (2013-07-15 07:52:32)
Offline
bloom wrote:But the point is: swapping and transplantation are different concepts and should not collide.
This makes sense. It's a bit unfortunate that a new set of hotkeys is required to fully utilize preselections, though.
Stebalien suggests:
bspc window -w last.manual
And also provides a squish script.
Offline
.xinitrc
#!/bin/sh
#
# ~/.xinitrc
#
#makes Font useable
xset +fp /usr/share/fonts/local
xset fp rehash
#Starts rxct-unicode daemon for much better Performance
urxvtd -f &
#Set Wallpaer (if is wished)
feh --no-fehbg --bg-center /home/danny/bilder/Wallpaper/arch_blue_black.png
#Set Cursor theme
xsetroot -cursor_name left_ptr &
#Hide the Mouse-Cursor
unclutter -idle 1 &
#Adds a conky to dwm Statusbar
#conky -c /home/danny/.conkyrc.2 | while read -r; do xsetroot -name "$REPLY"; done &
#Executes monsterwm & bar
#exec /home/danny/projekt/anotherbar.sh
#Set the X keybindings
xbindkeys -f /home/danny/.xbindkeysrc &
#Execute wm
exec bspwm -s $PANEL_FIFO -p :
I think the Problem for me is, that I dont unterstanding why
echo "Something" > "$PANEL_FIFO"
cat "$PANEL_FIFO" | bar -p
is not working. If I want to write something in the Fifo then it will not going to output.This is a bit confusing. I hope you can blow the fog out of my mind.
/* No Comment */
Offline
@neuromatic: are you calling "mkfifo $PANEL_FIFO" somewhere?
Offline
The new mode modifiers are very useful.
What exactly is the --follow rule supposed to do? Currently it doesn't seem to do much of anything.
I use linux and I dont understand nothing in this post.
Offline
The new mode modifiers are very useful.
What exactly is the --follow rule supposed to do? Currently it doesn't seem to do much of anything.
When combined with '-d <desktop>', focus the desktop if it isn't the current (follow the window to its desktop).
Last edited by Stebalien (2013-07-15 13:23:40)
Offline
Offline