[Top][All Lists]

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

Re: Understanding atomic window groups

From: martin rudalics
Subject: Re: Understanding atomic window groups
Date: Mon, 3 Jun 2019 11:12:31 +0200

> Okay, I do see that `quit-window' has a more complicated job to do, and
> multiple conditions are checked. I guess I was hoping/expecting that
> `quit-window' in a member of an atomic window group could somehow be
> altered to act on the whole group, rather than just the current window.

We would have to specify the respective semantics first.  Atomic
groups by default do not have main windows.  All its constituting live
windows are treated equal - as, for example, two side-by-side windows
showing the diffs of a file.  If we want to designate one constituent
of an atomic window as the "main" window and have 'quit-window' act on
the entire group as the 'quit-restore' parameter of that main window
says, we would have to write specific code for 'quit-restore-window'.

> I would at least add the fact that atomic groups can be nested,

When I first used the term "nested" I only meant that an atomic window
can comprise an arbitrary number of windows as long as the resulting
window has a rectangular shape.  That's why I asked you to act on the
root of the atomic window instead on the parent of one of its
constituents.  I'm not sure what to say more about this in the manual
- maybe you can propose the necessary change.

> and say
> something about how to get _rid_ of an atomic group. When I was first
> experimenting, I ended up having to reboot emacs, because I couldn't
> figure out how to un-atomic the frame.

I tried to say that now.

> It would be great to have more examples in the side windows section as
> well. The two features together feel like they could be very powerful,
> there's just a bit of a documentation gap.

I already devote an entire subsection to an example.

> I've had it in the back of my mind to try replacing Gnus' homemade
> windowing functionality with side windows, because they do pretty much
> the same thing, but I'm not sure where to start. In particular, the doc
> examples show a setup where certain buffers appear to _always_ be
> displayed in certain side buffers. My assumption is that in the vast
> majority of cases, people would want to display _this_ particular group
> of buffers in a certain way on _this_ frame, and not pollute the global
> config.

Which use case do you have in mind?  The people asking before for such
a feature wanted the layout apply to any frame - that is, side windows
should specify the global configuration.


reply via email to

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