I actually like this idea myself, and I've been using i3 exclusively for a
few months now, and i3 was my first entry into tiling wms. I still
consider myself a novice though - I think I've basically learned just
enough work fairly comfortably, but have no doubt acquired a few bad habits
and gaping holes in my understanding along the way. So excuse me if I
misuse terms or show any obvious signs of luser. (:
To use Sylvain's summary: "a sticky/protected container which can freeze its
structure and delegate it to the next container (or create a new one if
required)."
... is something I would be able to immediately put to use in my usual
workfow.
In particular, the IntelliJ Idea editor is difficult to work with due to
the way it opens new editor windows. I want to have the main application
window remain ever-present to the left-half portion of my screen in
stacking mode, while each new editor window I open should appear to the
right-half, also in stacking mode. So that each successive new editor
window opens to the right of the main application window, and is
stacked below one another.
I believe that the feature in question would really make the above
scenario convenient and straight-forward, and doesn't require extra
keystrokes/commands or configuration to utilize other than the single
'sticky/protected' command.
Kind regards!
On Tue, Oct 01, 2013 at 07:07:43AM +0200, Michael Stapelberg wrote:
Hi Sylvain,
Sylvain Benner <sylvain.benner@xxxxxxxxx> writes:
Let me rephrase your asking: If you have the focus on emacs and open anI don’t see that as a good feature for i3. It does not strike me as
application you want it to not resize the emacs window.
If this is correct then this is not possible in i3 without a patch or
script, there is no such thing as a sticky/protected container which can
freeze its structure and delegate it to the next container (or create a new
one if required).
Michael what do you think about such a feature ? It captures the feeling of
one property of slave/master in some other WM but still let the user to do
it when and where it wants it which fits the philosophy of i3 in my
opinion. The tricky part is the visual clue about such containers/windows.
particularly useful, and it is solving an issue that only exists for
newcomers to i3.
--
Best regards,
Michael