From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: joostkremers@fastmail.fm, emacs-devel@gnu.org
Subject: Re: Window splitting issues with margins
Date: Fri, 13 Nov 2015 20:34:17 +0200 [thread overview]
Message-ID: <83io55g34m.fsf@gnu.org> (raw)
In-Reply-To: <5645F982.30506@gmx.at>
> Date: Fri, 13 Nov 2015 15:53:54 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: joostkremers@fastmail.fm, emacs-devel@gnu.org
>
> > I thought
> > the original problem was with splitting a wide window in which the
> > margins were set to a large size in order to keep the body text at a
> > smaller width. I'm asking whether we could pass this information to
> > the code which splits the window, so that its decisions would take
> > that information into consideration.
>
> This would have to be done in ‘split-window’ then. More precisely it
> would have to be done in the function ‘window--sanitize-window-sizes’
> which tries to make sure that all windows have reasonable sizes
> according to the sizes of their margins, fringes, ...
Something like that, yes.
> Note one aspect though: When you shrink margins while splitting or
> shrinking windows you usually won't get back their old size after
> deleting the other or enlarging this window. That's why I think that
> it's much easier when packages manage their preferred size of margins in
> ‘window-size-change-functions’ and ‘window-configuration-change-hook’.
Yes, that would perhaps be preferable.
Is there any reason why dark-room mode couldn't do that?
next prev parent reply other threads:[~2015-11-13 18:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 13:04 Window splitting issues with margins Joost Kremers
2015-11-12 14:31 ` martin rudalics
2015-11-12 16:28 ` Eli Zaretskii
2015-11-12 21:38 ` Joost Kremers
2015-11-13 8:04 ` martin rudalics
2015-11-13 8:40 ` Eli Zaretskii
2015-11-13 10:01 ` martin rudalics
2015-11-13 13:54 ` Eli Zaretskii
2015-11-13 14:53 ` martin rudalics
2015-11-13 18:34 ` Eli Zaretskii [this message]
2015-11-12 22:14 ` Joost Kremers
2015-11-13 8:04 ` martin rudalics
2015-11-13 8:43 ` Eli Zaretskii
2015-11-13 10:02 ` martin rudalics
2015-11-14 20:34 ` Joost Kremers
2015-11-16 15:53 ` Eli Zaretskii
2015-11-16 16:56 ` Joost Kremers
2015-11-16 18:56 ` martin rudalics
2015-11-16 20:11 ` Joost Kremers
2015-11-17 8:35 ` martin rudalics
2015-11-19 13:46 ` Joost Kremers
2015-11-20 8:21 ` martin rudalics
2015-11-25 13:10 ` Joost Kremers
2015-11-24 12:59 ` Joost Kremers
2015-11-24 19:26 ` martin rudalics
2015-11-25 19:53 ` Joost Kremers
2015-11-26 8:23 ` martin rudalics
2015-11-26 15:46 ` Eli Zaretskii
2015-11-26 16:58 ` martin rudalics
2015-11-26 17:13 ` Eli Zaretskii
2015-11-26 18:04 ` martin rudalics
2015-11-26 18:32 ` Eli Zaretskii
2015-11-27 8:26 ` martin rudalics
2015-11-27 9:00 ` Eli Zaretskii
2015-11-28 10:22 ` martin rudalics
2015-11-28 11:13 ` Eli Zaretskii
2015-11-14 20:47 ` Joost Kremers
2015-11-16 17:02 ` John Wiegley
2015-11-16 10:51 ` Yuri Khan
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=83io55g34m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joostkremers@fastmail.fm \
--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.