stumpwm-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [STUMP] Paulownia, aka StumpWM 2.0.0


From: Mikael Jansson
Subject: Re: [STUMP] Paulownia, aka StumpWM 2.0.0
Date: Wed, 7 Oct 2015 15:40:49 +0200


On Wed, Oct 7, 2015 at 3:16 PM, Michael Raskin <address@hidden> wrote:
>> My setup via frame tagging is most close to 4 no-permanent-splits
>> «groups» inside a single physical display, and one or four more when
>> I attach an external display to my notebook.
>>
>
>Is this similar to having one "sticky" group that's always on the one same
>head (= display), and have all other displays have changing groups?
>That's one feature I'd really like. IRC/e-mail/etc always open on one
>monitor, then the other content changes depending on which group I have
>active.

Yes, just a bit more generic (and works on top of current StumpWM).

One of them is for my xterm-based modeline, one for notifications, one
is often IM+email (very like your sticky group).

Sometimes I switch to code+view (LaTeX+PDF or backend+website) usage of
the two large areas.


Right. 

I both like the current way, where the group is at top-level, and the other way where I'd have something like nested groups.

To be clear on what I mean, this is hopefully a better explanation:

Given
A, B = monitors
[A], [B] = the frame on an empty head/monitor, i.e. with no splitted frames, on monitors A and B.
{[A] [B]} = group containing said frames
{X}+ = group that's stuck to a head

Then {[A] [B]} is what we have now, and { {[A]}+ {[B]} } is what I'd like to have. Then a command to unstick a group to a head, which causes a merge of {[A]} + {[B]} into {[A] [B]}.

- Micke




reply via email to

[Prev in Thread] Current Thread [Next in Thread]