From: Joost Kremers <joostkremers@fastmail.fm>
To: Eli Zaretskii <eliz@gnu.org>
Cc: martin rudalics <rudalics@gmx.at>, emacs-devel@gnu.org
Subject: Re: Better handling of window margins
Date: Wed, 02 Dec 2015 20:52:51 +0100 [thread overview]
Message-ID: <87h9k0zkz0.fsf@fastmail.fm> (raw)
In-Reply-To: <838u5cka88.fsf@gnu.org>
On Wed, Dec 02 2015, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 02 Dec 2015 18:43:47 +0100
>> From: martin rudalics <rudalics@gmx.at>
>> CC: emacs-devel@gnu.org
>>
>> > . for splitting the window with "C-x 2" and "C-x 3", the mode could
>> > simply invoke the correct splitting function itself
>>
>> When two modes simultaneously use the margins, which splitting function
>> would be chosen?
>
> It's up to the mode that wants to support splitting in any non-trivial
> manner. The mode knows exactly what are its needs, so it is free of
> the guesswork.
>
> In any case, the same problem exists if this is somehow guessed. The
> infrastructure cannot know enough about the modes to make a decision.
Speaking as a minor-mode author, I would expect Emacs to provide a
default that handles the known cases in a reasonable manner, the known
cases IMHO being those I described. If someday someone comes up with a
use for the margins that cannot be handled properly, it makes sense to
allow the default to be overridden.
>> > . for splitting the window as result of some command calling
>> > display-buffer, we could expect the modes to customize the
>> > display-buffer-* variables to control how the window is split (if
>> > there are currently no features/variables to that effect, we should
>> > add them)
>>
>> When two modes simultaneously use the margins, which buffer display
>> function would be chosen?
>
> The same problem exists with the proposed solution, doesn't it?
If the value of `set-window-margins-function' is a single function, then
probably the function provided by the last mode to be activated in a
buffer.
Isn't that a potential problem?
--
Joost Kremers
Life has its moments
next prev parent reply other threads:[~2015-12-02 19:52 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 21:28 Better handling of window margins Joost Kremers
2015-12-02 8:23 ` martin rudalics
2015-12-02 13:41 ` Eli Zaretskii
2015-12-02 17:43 ` martin rudalics
2015-12-02 17:53 ` Eli Zaretskii
2015-12-02 18:11 ` martin rudalics
2015-12-03 6:49 ` Eli Zaretskii
2015-12-03 18:16 ` martin rudalics
2015-12-03 20:09 ` Eli Zaretskii
2015-12-03 20:43 ` Stefan Monnier
2015-12-04 8:14 ` Eli Zaretskii
2015-12-04 13:22 ` Stefan Monnier
2015-12-04 14:46 ` Eli Zaretskii
2015-12-04 17:30 ` Stefan Monnier
2015-12-04 18:45 ` Eli Zaretskii
2015-12-04 20:55 ` Stefan Monnier
2015-12-04 21:13 ` Eli Zaretskii
2015-12-04 21:33 ` Stefan Monnier
2015-12-05 7:56 ` Eli Zaretskii
2015-12-05 15:17 ` Stefan Monnier
2015-12-05 15:49 ` Eli Zaretskii
2015-12-06 4:27 ` Stefan Monnier
2015-12-06 5:02 ` John Wiegley
2015-12-06 16:10 ` Eli Zaretskii
2015-12-06 20:24 ` Yuri Khan
2015-12-07 3:32 ` Eli Zaretskii
2015-12-07 10:35 ` Yuri Khan
2015-12-07 16:39 ` Eli Zaretskii
2015-12-07 0:29 ` John Wiegley
2015-12-07 16:24 ` Eli Zaretskii
2015-12-07 17:35 ` John Wiegley
2015-12-07 17:38 ` Achim Gratz
2015-12-07 17:41 ` John Wiegley
2015-12-07 17:50 ` Achim Gratz
2015-12-07 17:36 ` Stefan Monnier
2015-12-07 17:39 ` John Wiegley
2015-12-07 18:42 ` Stefan Monnier
2015-12-07 19:14 ` John Wiegley
2015-12-04 8:07 ` martin rudalics
2015-12-04 9:42 ` Eli Zaretskii
2015-12-04 10:21 ` martin rudalics
2015-12-04 15:34 ` Eli Zaretskii
2015-12-04 16:56 ` martin rudalics
2015-12-04 18:34 ` Eli Zaretskii
2015-12-04 19:23 ` martin rudalics
2015-12-02 19:52 ` Joost Kremers [this message]
2015-12-03 7:17 ` Eli Zaretskii
2015-12-02 19:55 ` Joost Kremers
2015-12-03 7:21 ` Eli Zaretskii
2015-12-04 12:49 ` John Wiegley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9k0zkz0.fsf@fastmail.fm \
--to=joostkremers@fastmail.fm \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.