Re: [dev] [wmii] Dualhead + tiling

2011-11-15 Thread Thomas Dahms
2011/11/14 Jonas H. :
> Is it possible to use tiling w/ dualhead? i.e. have a separate tiling area
> on each monitor - so that if you move a window from monitor 0 to monitor 1
> in floating mode and then move it to the tiling layer, it stays on monitor
> 1.  (The way it works for my setup right now is that it's moved back to
> monitor 0.)

wmii spans the tiling area over all monitors, but managed columns end
at screen boundaries.

-- 
Thomas Dahms



Re: [dev] [wmii] Dualhead + tiling

2011-11-15 Thread Jonas H.

On 11/15/2011 09:32 AM, Thomas Dahms wrote:

wmii spans the tiling area over all monitors, but managed columns end
at screen boundaries.


What's that "Xinerama support" that came with 3.9 then?



Re: [dev] [wmii] Dualhead + tiling

2011-11-15 Thread Thomas Dahms
2011/11/15 Jonas H. :
>
> What's that "Xinerama support" that came with 3.9 then?

It is Xinerama. One view just includes both monitors. That is
different from dwm and other window managers, but not necessarily
worse.

-- 
Thomas Dahms



Re: [dev] [dmenu] Readline Bindings

2011-11-15 Thread Bastien Dejean
Connor Lane Smith a écrit :

> On 14/11/2011, Bastien Dejean  wrote:
> > This is only true when the search string is empty which is extremely
> > rare: most of the times the first thing the user do is to type a few
> > characters to filter the results and hence, the cursor is then at the
> > end of the search string, C-f will move down in the search results and
> > C-b backward in the search string.
> 
> ... No. So long as you are not on the first item in the list, C-b will
> move back through the selected items, regardless of the length of the
> input. And so long as the cursor is at the end of the input, C-f will
> move forward through the selected items. The cursor basically
> continues from where the selector ends.

Now I understand what you're trying to do. Since C-b doesn't behave like
that in my experience, I wondered what particular option I might be using
that you're not: and I though about the number of lines.

So... we have a bug: just try with 'dmenu -l 2' or any number > 1.

Greetings,
-- 
Bastien