* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-13 7:45 ` martin rudalics
@ 2018-09-13 13:07 ` N. Jackson
2018-09-14 8:31 ` martin rudalics
2018-09-13 16:33 ` Eric Abrahamsen
2018-09-14 5:17 ` Roland Winkler
2 siblings, 1 reply; 31+ messages in thread
From: N. Jackson @ 2018-09-13 13:07 UTC (permalink / raw)
To: martin rudalics
Cc: Eric Abrahamsen, emacs-devel, Roland Winkler, Stefan Monnier
At 09:45 +0200 on Thursday 2018-09-13, martin rudalics wrote:
>
>> If there was a function (frame-split-biggest-window FRAME SIZE SIDE
>> PIXELWISE) to split the "biggest" [*] window in the frame, then
>> neither BBDB nor any other Elisp code would need to keep reinventing
>> this wheel.
>>
>> (The other two functions, more for interactive use, would be
>> `frame-split-biggest-window-below' and
>> `frame-split-biggest-window-right'.)
>>
>> [*] To find the "biggest" window when splitting below, find the
>> tallest window or windows and split the widest of them; when
>> splitting right, find the widest window or windows and split the
>> tallest of them.
>
> We have a number of options for that. One of them is the option
> 'split-window-preferred-function' (a misnomer) which is by default set
> to 'split-window-sensibly'. Consult their definitions first. The
> latter's behavior is guided by the options 'split-height-threshold'
> and 'split-width-threshold' (two more misnomers) . Together, these
> should provide a boilerplate for writing your own function which you
> can then put into 'display-buffer-alist'.
What's missing with these functions is that they start from a given
window. What's needed is functionality that looks at all the windows
on (in?) the frame and chooses which one to split.
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-13 13:07 ` N. Jackson
@ 2018-09-14 8:31 ` martin rudalics
0 siblings, 0 replies; 31+ messages in thread
From: martin rudalics @ 2018-09-14 8:31 UTC (permalink / raw)
To: N. Jackson; +Cc: Eric Abrahamsen, emacs-devel, Roland Winkler, Stefan Monnier
>> We have a number of options for that. One of them is the option
>> 'split-window-preferred-function' (a misnomer) which is by default set
>> to 'split-window-sensibly'. Consult their definitions first. The
>> latter's behavior is guided by the options 'split-height-threshold'
>> and 'split-width-threshold' (two more misnomers) . Together, these
>> should provide a boilerplate for writing your own function which you
>> can then put into 'display-buffer-alist'.
>
> What's missing with these functions is that they start from a given
> window. What's needed is functionality that looks at all the windows
> on (in?) the frame and chooses which one to split.
Specifying such heuristics is non-trivial - 'display-buffer' tries to
first split the largest and then the least recently used window.
Maybe we should refine 'get-largest-window' in the spirit of
'split-window-sensibly'. But when the latter was introduced, there
were a number of complaints because the behavior of 'display-buffer'
changed in an unexpected way - people were surprised to suddenly see a
window split horizontally. So any changes should be done carefully.
Also, some buffer display action functions roughly try to split the
window as one at the top or bottom of the frame or the selected one in
order to show the buffer there. And you can put a window on any side
of a frame by using side windows. All these try to reconcile window
splitting and reusing to achieve the intended effect.
martin
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-13 7:45 ` martin rudalics
2018-09-13 13:07 ` N. Jackson
@ 2018-09-13 16:33 ` Eric Abrahamsen
2018-09-14 8:33 ` martin rudalics
2018-09-14 5:17 ` Roland Winkler
2 siblings, 1 reply; 31+ messages in thread
From: Eric Abrahamsen @ 2018-09-13 16:33 UTC (permalink / raw)
To: martin rudalics; +Cc: N. Jackson, Roland Winkler, Stefan Monnier, emacs-devel
martin rudalics <rudalics@gmx.at> writes:
>> If there was a function (frame-split-biggest-window FRAME SIZE SIDE
>> PIXELWISE) to split the "biggest" [*] window in the frame, then
>> neither BBDB nor any other Elisp code would need to keep reinventing
>> this wheel.
>>
>> (The other two functions, more for interactive use, would be
>> `frame-split-biggest-window-below' and
>> `frame-split-biggest-window-right'.)
>>
>> [*] To find the "biggest" window when splitting below, find the
>> tallest window or windows and split the widest of them; when
>> splitting right, find the widest window or windows and split the
>> tallest of them.
>
> We have a number of options for that. One of them is the option
> 'split-window-preferred-function' (a misnomer) which is by default set
> to 'split-window-sensibly'. Consult their definitions first. The
> latter's behavior is guided by the options 'split-height-threshold'
> and 'split-width-threshold' (two more misnomers) . Together, these
> should provide a boilerplate for writing your own function which you
> can then put into 'display-buffer-alist'.
>
> One functionality Emacs is sadly lacking is that of orderly setting up
> and saving compositions of windows in form of a rectangle. Eclipse
> calls these "perspectives", in Emacs the concept of "window state"
> comes most closely. Currently, you have to set up such a state by
> using a sequence of 'split-window' calls which requires to know the
> intrinsics of window splitting, the relationship of parent and child
> windows, window combinations and the like. Using 'display-buffer' for
> setting up states will hardly produce good results.
>
> It would be nice to have some sort of basic, prefabricated layouts
> like the ones you sketched and choose from them (though a four window
> layout with a different window in each corner of them frame would
> still require to know whether the root window is a vertical or
> horizontal combination). But I have no good idea yet which layout
> types are really needed and how to provide a suitable interface for
> accessing them. IIRC the "Emacs IDE" had provisions for them but I
> have not heard from its developers for years.
I thought this is what side windows are for? Maybe it would be tricky to
save and restore whole-frame window configurations (though there are
other tools for that), but side windows, combined perhaps with atomic
windows, seem like the right tool for making rectangular compositions.
The docs even say something about making Emacs look like a traditional
IDE, etc...
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-13 16:33 ` Eric Abrahamsen
@ 2018-09-14 8:33 ` martin rudalics
2018-09-14 16:56 ` Eric Abrahamsen
0 siblings, 1 reply; 31+ messages in thread
From: martin rudalics @ 2018-09-14 8:33 UTC (permalink / raw)
To: Eric Abrahamsen; +Cc: N. Jackson, emacs-devel, Roland Winkler, Stefan Monnier
>> It would be nice to have some sort of basic, prefabricated layouts
>> like the ones you sketched and choose from them (though a four window
>> layout with a different window in each corner of them frame would
>> still require to know whether the root window is a vertical or
>> horizontal combination). But I have no good idea yet which layout
>> types are really needed and how to provide a suitable interface for
>> accessing them. IIRC the "Emacs IDE" had provisions for them but I
>> have not heard from its developers for years.
>
> I thought this is what side windows are for? Maybe it would be tricky to
> save and restore whole-frame window configurations (though there are
> other tools for that), but side windows, combined perhaps with atomic
> windows, seem like the right tool for making rectangular compositions.
> The docs even say something about making Emacs look like a traditional
> IDE, etc...
The intention of side windows was to provide a framework for ECB (the
Emacs Code Browser) to embed such layouts without the need to advice
basic window functions. Unfortunately, work on ECB seems to have
stalled a decade ago and nobody seems very interested in continuing
it.
martin
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-14 8:33 ` martin rudalics
@ 2018-09-14 16:56 ` Eric Abrahamsen
2018-09-15 8:17 ` martin rudalics
0 siblings, 1 reply; 31+ messages in thread
From: Eric Abrahamsen @ 2018-09-14 16:56 UTC (permalink / raw)
To: emacs-devel
martin rudalics <rudalics@gmx.at> writes:
>>> It would be nice to have some sort of basic, prefabricated layouts
>>> like the ones you sketched and choose from them (though a four window
>>> layout with a different window in each corner of them frame would
>>> still require to know whether the root window is a vertical or
>>> horizontal combination). But I have no good idea yet which layout
>>> types are really needed and how to provide a suitable interface for
>>> accessing them. IIRC the "Emacs IDE" had provisions for them but I
>>> have not heard from its developers for years.
>>
>> I thought this is what side windows are for? Maybe it would be tricky to
>> save and restore whole-frame window configurations (though there are
>> other tools for that), but side windows, combined perhaps with atomic
>> windows, seem like the right tool for making rectangular compositions.
>> The docs even say something about making Emacs look like a traditional
>> IDE, etc...
>
> The intention of side windows was to provide a framework for ECB (the
> Emacs Code Browser) to embed such layouts without the need to advice
> basic window functions. Unfortunately, work on ECB seems to have
> stalled a decade ago and nobody seems very interested in continuing
> it.
Huh, thanks for the background. But in my experimentation, at least,
side windows seem to work perfectly well (especially in combination with
atomic windows). Is there any particular reason not to use them?
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-13 7:45 ` martin rudalics
2018-09-13 13:07 ` N. Jackson
2018-09-13 16:33 ` Eric Abrahamsen
@ 2018-09-14 5:17 ` Roland Winkler
2018-09-14 8:33 ` martin rudalics
2 siblings, 1 reply; 31+ messages in thread
From: Roland Winkler @ 2018-09-14 5:17 UTC (permalink / raw)
To: martin rudalics; +Cc: Eric Abrahamsen, N. Jackson, Stefan Monnier, emacs-devel
On Thu Sep 13 2018 martin rudalics wrote:
> One functionality Emacs is sadly lacking is that of orderly setting up
> and saving compositions of windows in form of a rectangle. Eclipse
> calls these "perspectives", in Emacs the concept of "window state"
> comes most closely. Currently, you have to set up such a state by
> using a sequence of 'split-window' calls which requires to know the
> intrinsics of window splitting, the relationship of parent and child
> windows, window combinations and the like. Using 'display-buffer' for
> setting up states will hardly produce good results.
Much agreed!
How is it possible that (as confirmed on this list)
gnus-window-to-buffer and gnus-add-configuration can be used to make
BBDB interact with Gnus windows as expected, while BBDB's function
bbdb-pop-up-window for creating BBDB windows does not know anything
about Gnus' mechanism for managing window layouts? When I first
heard of gnus-window-to-buffer and gnus-add-configuration I thought
this cannot work with BBDB because Gnus will bring its own
hand-crafted functions to create windows, functions that obey the
customizations using gnus-window-to-buffer and gnus-add-configuration.
> It would be nice to have some sort of basic, prefabricated layouts
> like the ones you sketched and choose from them.
Again: much agreed!
Can `display-buffer-alist' mentioned by Stefan do that (at least: in
principle)? I looked at its documentation in the elisp manual (not
the Emacs manual!), and I could not figure out how to use this
variable to achieve the goals discussed here. Does
`display-buffer-alist' provide the same functionality as the Gnus
code discussed in this thread?
Certainly, it would be nice if different packages like Gnus and
other MUAs could use the same code for the generic problem of
defining window layouts so that a package like BBDB can interact
with this, too.
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-14 5:17 ` Roland Winkler
@ 2018-09-14 8:33 ` martin rudalics
2018-09-14 12:01 ` Stefan Monnier
2018-09-15 0:46 ` Richard Stallman
0 siblings, 2 replies; 31+ messages in thread
From: martin rudalics @ 2018-09-14 8:33 UTC (permalink / raw)
To: Roland Winkler; +Cc: Eric Abrahamsen, N. Jackson, Stefan Monnier, emacs-devel
> Can `display-buffer-alist' mentioned by Stefan do that (at least: in
> principle)? I looked at its documentation in the elisp manual (not
> the Emacs manual!), and I could not figure out how to use this
> variable to achieve the goals discussed here. Does
> `display-buffer-alist' provide the same functionality as the Gnus
> code discussed in this thread?
The purpose of 'display-buffer-alist' is to set up a window for one
single buffer. It already fails miserably to make sure that two
buffers get displayed simultaneously as the thread of Bug#32607 shows.
martin
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-14 8:33 ` martin rudalics
@ 2018-09-14 12:01 ` Stefan Monnier
2018-09-15 4:12 ` Roland Winkler
2018-09-15 12:24 ` N. Jackson
2018-09-15 0:46 ` Richard Stallman
1 sibling, 2 replies; 31+ messages in thread
From: Stefan Monnier @ 2018-09-14 12:01 UTC (permalink / raw)
To: martin rudalics; +Cc: Eric Abrahamsen, N. Jackson, Roland Winkler, emacs-devel
>> Can `display-buffer-alist' mentioned by Stefan do that (at least: in
>> principle)? I looked at its documentation in the elisp manual (not
>> the Emacs manual!), and I could not figure out how to use this
>> variable to achieve the goals discussed here. Does
>> `display-buffer-alist' provide the same functionality as the Gnus
>> code discussed in this thread?
> The purpose of 'display-buffer-alist' is to set up a window for one
> single buffer. It already fails miserably to make sure that two
> buffers get displayed simultaneously as the thread of Bug#32607 shows.
Exactly. So for the purpose of "orderly setting up
and saving compositions of windows", it's of no use, but in the specific
case of BBDB (which just needs to (temporarily) pop up a single buffer),
it should be sufficient.
Stefan
^ permalink raw reply [flat|nested] 31+ messages in thread* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-14 12:01 ` Stefan Monnier
@ 2018-09-15 4:12 ` Roland Winkler
2018-09-15 4:58 ` Drew Adams
2018-09-15 8:18 ` martin rudalics
2018-09-15 12:24 ` N. Jackson
1 sibling, 2 replies; 31+ messages in thread
From: Roland Winkler @ 2018-09-15 4:12 UTC (permalink / raw)
To: Stefan Monnier; +Cc: Eric Abrahamsen, martin rudalics, emacs-devel, N. Jackson
On Fri Sep 14 2018 Stefan Monnier wrote:
> > The purpose of 'display-buffer-alist' is to set up a window for one
> > single buffer. It already fails miserably to make sure that two
> > buffers get displayed simultaneously as the thread of Bug#32607 shows.
>
> Exactly. So for the purpose of "orderly setting up and saving
> compositions of windows", it's of no use, but in the specific case
> of BBDB (which just needs to (temporarily) pop up a single
> buffer), it should be sufficient.
The current discussion of 'display-buffer-alist' in the elisp manual
appears rather technical, suited only for expert users. On the
other hand, the variable is declared with defcustom, as if
individual users should customize it to their personal liking.
Phrased differently: a package like BBDB should not hijack this
variable for its needs (but at best it could contribute to its value
via a user option), correct?
If that's the case, then it would really help to extend the
documentation for this variable, stating not only that it works only
for a single buffer, but also adding one or two real-world examples
similar to what we have been discussing here.
I believe it is quite common that users may want to customize how
emacs pops up new windows. Having a unified customization scheme
for that would be much nicer than having different approaches
implemented in different packages.
^ permalink raw reply [flat|nested] 31+ messages in thread
* RE: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-15 4:12 ` Roland Winkler
@ 2018-09-15 4:58 ` Drew Adams
2018-09-15 8:18 ` martin rudalics
1 sibling, 0 replies; 31+ messages in thread
From: Drew Adams @ 2018-09-15 4:58 UTC (permalink / raw)
To: Roland Winkler, Stefan Monnier
Cc: Eric Abrahamsen, martin rudalics, N. Jackson, emacs-devel
> The current discussion of 'display-buffer-alist' in the elisp manual
> appears rather technical, suited only for expert users. On the
> other hand, the variable is declared with defcustom, as if
> individual users should customize it to their personal liking.
> Phrased differently: a package like BBDB should not hijack this
> variable for its needs (but at best it could contribute to its value
> via a user option), correct?
>
> If that's the case, then it would really help to extend the
> documentation for this variable, stating not only that it works only
> for a single buffer, but also adding one or two real-world examples
> similar to what we have been discussing here.
>
> I believe it is quite common that users may want to customize how
> emacs pops up new windows. Having a unified customization scheme
> for that would be much nicer than having different approaches
> implemented in different packages.
+1
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-15 4:12 ` Roland Winkler
2018-09-15 4:58 ` Drew Adams
@ 2018-09-15 8:18 ` martin rudalics
2018-09-15 16:34 ` Roland Winkler
1 sibling, 1 reply; 31+ messages in thread
From: martin rudalics @ 2018-09-15 8:18 UTC (permalink / raw)
To: Roland Winkler, Stefan Monnier; +Cc: Eric Abrahamsen, N. Jackson, emacs-devel
> The current discussion of 'display-buffer-alist' in the elisp manual
> appears rather technical, suited only for expert users. On the
> other hand, the variable is declared with defcustom, as if
> individual users should customize it to their personal liking.
> Phrased differently: a package like BBDB should not hijack this
> variable for its needs (but at best it could contribute to its value
> via a user option), correct?
I think so. No package should hijack this variable for its needs -
it's entirely left to the user. Packages like BBDB should only use
the ACTION argument of 'display-buffer'. Only in a few, special and
well documented cases, 'display-buffer-overriding-action' may be used
to override a user's customization of 'display-buffer-alist'.
> If that's the case, then it would really help to extend the
> documentation for this variable, stating not only that it works only
> for a single buffer, but also adding one or two real-world examples
> similar to what we have been discussing here.
>
> I believe it is quite common that users may want to customize how
> emacs pops up new windows. Having a unified customization scheme
> for that would be much nicer than having different approaches
> implemented in different packages.
There is an example at the end of section 28.14. If you want it to
say things differently, say more, or whether to put it somewhere else
please tell us.
martin
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-15 8:18 ` martin rudalics
@ 2018-09-15 16:34 ` Roland Winkler
2018-09-15 18:34 ` Stefan Monnier
0 siblings, 1 reply; 31+ messages in thread
From: Roland Winkler @ 2018-09-15 16:34 UTC (permalink / raw)
To: martin rudalics; +Cc: Eric Abrahamsen, N. Jackson, Stefan Monnier, emacs-devel
On Sat Sep 15 2018 martin rudalics wrote:
> I think so. No package should hijack this variable for its needs -
> it's entirely left to the user. Packages like BBDB should only use
> the ACTION argument of 'display-buffer'.
Thanks for the clarification! So BBDB can use the ACTION argument
of 'display-buffer'. Then it can also just provide a default for
ACTION which users can customize if they do not like it (via some
BBDB user variable). Such a working default may help users that
want to customize this, but they feel overwhelmed by how this works.
> There is an example at the end of section 28.14.
Great, this was exactly what I was looking for.
> If you want it to say things differently, say more, or whether to
> put it somewhere else please tell us.
- As `display-buffer-alist' is the variable that users want to
customize (hence: it is the entry point for people wanting to
customize these things), I suggest that the description of
`display-buffer-alist' in the elisp manual should include a link
to the example in section 28.14.
- If I understand correctly, the example in Sec. 28.14 is slightly
outdated:
window-height is an outdated alias for window-total-height
and window-width is an outdated alias for window-body-width
(as described in the node Window sizes of the elisp manual).
This applies also to the description of
`display-buffer-below-selected' and possibly other spots in the
elisp manual.
- Is there a possibility to specify, using an ACTION, that a new
window should take over a certain fraction of an existing window
in a vertical split? I believe this is a common case. (I may be
missing that this is described somewhere.)
(I thought that `display-buffer-alist' was only mentioned in the
elisp manual but not in the emacs manual. Yet this was my mistake
due to my configuration of info-lookup that jumps straight to the
elisp manual.)
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-15 16:34 ` Roland Winkler
@ 2018-09-15 18:34 ` Stefan Monnier
2018-09-15 19:21 ` Roland Winkler
0 siblings, 1 reply; 31+ messages in thread
From: Stefan Monnier @ 2018-09-15 18:34 UTC (permalink / raw)
To: Roland Winkler; +Cc: Eric Abrahamsen, martin rudalics, N. Jackson, emacs-devel
> - Is there a possibility to specify, using an ACTION, that a new
> window should take over a certain fraction of an existing window
> in a vertical split? I believe this is a common case. (I may be
> missing that this is described somewhere.)
ACTION can be any function you like, so the answer is obviously yes.
But I don't think there's currently a pre-existing function which does
that, no.
Stefan
^ permalink raw reply [flat|nested] 31+ messages in thread* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-15 18:34 ` Stefan Monnier
@ 2018-09-15 19:21 ` Roland Winkler
0 siblings, 0 replies; 31+ messages in thread
From: Roland Winkler @ 2018-09-15 19:21 UTC (permalink / raw)
To: Stefan Monnier; +Cc: Eric Abrahamsen, martin rudalics, N. Jackson, emacs-devel
On Sat Sep 15 2018 Stefan Monnier wrote:
> > - Is there a possibility to specify, using an ACTION, that a new
> > window should take over a certain fraction of an existing window
> > in a vertical split? I believe this is a common case. (I may be
> > missing that this is described somewhere.)
>
> ACTION can be any function you like, so the answer is obviously yes.
> But I don't think there's currently a pre-existing function which does
> that, no.
To make the ACTION arg attractive for a wider range of use cases, I
believe it would be helpful to provide a function that can help with
this. Yet currently my understanding of the ACTION machinery is too
limited for more specific suggestions of how such a function should
work and hook into this machinery. (Certainly it is not desirable
if multple packages wanting to use such an approach had to invent
the wheel repeatedly.)
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-14 12:01 ` Stefan Monnier
2018-09-15 4:12 ` Roland Winkler
@ 2018-09-15 12:24 ` N. Jackson
2018-09-15 14:56 ` Stefan Monnier
1 sibling, 1 reply; 31+ messages in thread
From: N. Jackson @ 2018-09-15 12:24 UTC (permalink / raw)
To: Stefan Monnier
Cc: Eric Abrahamsen, martin rudalics, Roland Winkler, emacs-devel
At 08:01 -0400 on Friday 2018-09-14, Stefan Monnier wrote:
>
>> The purpose of 'display-buffer-alist' is to set up a window for
>> one single buffer. It already fails miserably to make sure that
>> two buffers get displayed simultaneously as the thread of
>> Bug#32607 shows.
>
> Exactly. So for the purpose of "orderly setting up and saving
> compositions of windows", it's of no use, but in the specific case
> of BBDB (which just needs to (temporarily) pop up a single
> buffer), it should be sufficient.
The BBDB window isn't as ephemeral as a completions window is (for
example) which just needs to pop up temporarily. Here I have the
BBDB window displayed at all times when I'm reading mail and news --
it displays the records for the sender and/or recipients of the
message.
Perhaps `display-buffer-alist' is sufficient for the BBDB case. As
its documentation is a little unclear (while recursive code is okay,
recursive documentation is a little bit trying), it would be nice to
see an example of how this might be done.
It seems to me that it requires the developer or the user to write
code (to iterate through all the windows in the frame) that will be
almost identical to the code that the OP of this thread suggested
should not need to be reinvented by every developer/user wanting to
do essentially the same thing; rather the functionality should be
provided by the Emacs infrastructure.
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-15 12:24 ` N. Jackson
@ 2018-09-15 14:56 ` Stefan Monnier
0 siblings, 0 replies; 31+ messages in thread
From: Stefan Monnier @ 2018-09-15 14:56 UTC (permalink / raw)
To: N. Jackson; +Cc: Eric Abrahamsen, martin rudalics, Roland Winkler, emacs-devel
> Perhaps `display-buffer-alist' is sufficient for the BBDB case. As
> its documentation is a little unclear (while recursive code is okay,
> recursive documentation is a little bit trying), it would be nice to
> see an example of how this might be done.
^^^^
I don't know what this "this" refers to.
If you mean "customize the location and shape", then I think currently
the answer will depend a lot on what "location" and what "shape"
you want.
But I think "side window" is part of the answer.
Stefan
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-14 8:33 ` martin rudalics
2018-09-14 12:01 ` Stefan Monnier
@ 2018-09-15 0:46 ` Richard Stallman
2018-09-15 8:17 ` martin rudalics
1 sibling, 1 reply; 31+ messages in thread
From: Richard Stallman @ 2018-09-15 0:46 UTC (permalink / raw)
To: martin rudalics; +Cc: eric, nljlistbox2, emacs-devel, winkler, monnier
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> The purpose of 'display-buffer-alist' is to set up a window for one
> single buffer.
Perhaps the doc string and/or the manual should explicitly clarify
this point.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-15 0:46 ` Richard Stallman
@ 2018-09-15 8:17 ` martin rudalics
2018-09-16 3:14 ` Richard Stallman
0 siblings, 1 reply; 31+ messages in thread
From: martin rudalics @ 2018-09-15 8:17 UTC (permalink / raw)
To: rms; +Cc: eric, nljlistbox2, winkler, monnier, emacs-devel
> > The purpose of 'display-buffer-alist' is to set up a window for one
> > single buffer.
>
> Perhaps the doc string and/or the manual should explicitly clarify
> this point.
My sentence above is misleading: It's a sloppy abbreviation for the
two sentences
"The purpose of 'display-buffer' is to set up a window for one single
buffer. Hence 'display-buffer-alist' can only be used for customizing
the setup of a window for one single buffer - the one specified by the
first argument of 'display-buffer'."
So if anything would have to be clarified here, it's the doc of
'display-buffer'. Now conceptually, 'display-buffer' can be called
multiple times in a row and should do something reasonable in that
case - if programmed correctly. But it cannot be used for setting up
windows for two or more buffers in one single call and that should be
evident from its doc-string.
martin
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-15 8:17 ` martin rudalics
@ 2018-09-16 3:14 ` Richard Stallman
2018-09-16 19:05 ` John Yates
0 siblings, 1 reply; 31+ messages in thread
From: Richard Stallman @ 2018-09-16 3:14 UTC (permalink / raw)
To: martin rudalics; +Cc: eric, nljlistbox2, emacs-devel, winkler, monnier
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> My sentence above is misleading: It's a sloppy abbreviation for the
> two sentences
If the actual text is already clear enough, that's fine with me.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-16 3:14 ` Richard Stallman
@ 2018-09-16 19:05 ` John Yates
2018-09-16 19:22 ` Eli Zaretskii
2018-09-16 20:30 ` Drew Adams
0 siblings, 2 replies; 31+ messages in thread
From: John Yates @ 2018-09-16 19:05 UTC (permalink / raw)
To: Richard Stallman
Cc: nljlistbox2, eric, winkler, Emacs developers, martin rudalics,
Stefan Monnier
Having struggled unsuccessfully in the past with display-buffer
I can state that for me the current text is insufficient. I found
Martin's recent clarification helpful. I have bookmarked it for
my own purposes and vote for incorporating something along
those lines into the official manual.
/john
On Sat, Sep 15, 2018 at 11:16 PM Richard Stallman <rms@gnu.org> wrote:
>
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> > My sentence above is misleading: It's a sloppy abbreviation for the
> > two sentences
>
> If the actual text is already clear enough, that's fine with me.
>
>
> --
> Dr Richard Stallman
> President, Free Software Foundation (https://gnu.org, https://fsf.org)
> Internet Hall-of-Famer (https://internethalloffame.org)
>
>
>
--
John Yates
505 Tremont St, #803
Boston, MA 02116
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-16 19:05 ` John Yates
@ 2018-09-16 19:22 ` Eli Zaretskii
2018-09-16 20:30 ` Drew Adams
1 sibling, 0 replies; 31+ messages in thread
From: Eli Zaretskii @ 2018-09-16 19:22 UTC (permalink / raw)
To: John Yates
Cc: nljlistbox2, rms, eric, winkler, emacs-devel, rudalics, monnier
> From: John Yates <john@yates-sheets.org>
> Date: Sun, 16 Sep 2018 15:05:19 -0400
> Cc: nljlistbox2@gmail.com, eric@ericabrahamsen.net, winkler@gnu.org,
> Emacs developers <emacs-devel@gnu.org>, martin rudalics <rudalics@gmx.at>,
> Stefan Monnier <monnier@iro.umontreal.ca>
>
> I can state that for me the current text is insufficient. I found
> Martin's recent clarification helpful. I have bookmarked it for
> my own purposes and vote for incorporating something along
> those lines into the official manual.
I'm sure Martin will do that.
Thanks.
^ permalink raw reply [flat|nested] 31+ messages in thread
* RE: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
2018-09-16 19:05 ` John Yates
2018-09-16 19:22 ` Eli Zaretskii
@ 2018-09-16 20:30 ` Drew Adams
1 sibling, 0 replies; 31+ messages in thread
From: Drew Adams @ 2018-09-16 20:30 UTC (permalink / raw)
To: John Yates, Richard Stallman
Cc: nljlistbox2, eric, winkler, Emacs developers, martin rudalics,
Stefan Monnier
> Having struggled unsuccessfully in the past with display-buffer
> I can state that for me the current text is insufficient. I found
> Martin's recent clarification helpful. I have bookmarked it for
> my own purposes and vote for incorporating something along
> those lines into the official manual.
+1
^ permalink raw reply [flat|nested] 31+ messages in thread