From: martin rudalics <rudalics@gmx.at>
To: "Paul W. Rankin" <hello@paulwrankin.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Adding olivetti to GNU ELPA
Date: Wed, 22 May 2019 10:32:06 +0200 [thread overview]
Message-ID: <622808ad-9a01-9ace-57a9-d3065c3a2daf@gmx.at> (raw)
In-Reply-To: <m2k1ejmfa0.fsf@paulwrankin.com>
>> I see it now. Where do you reinstall the 'split-window' parameter
>> after splitting?
>
> It's in the main function, olivetti-set-margins @ line 177.
OK. Then I'm afraid you have to do the following: Whenever olivetti
mode is active in at least _one_ live window on a frame you have to
use 'olivetti-split-window' on _all_ internal windows of that frame
too. You can use 'walk-window-tree' for setting and resetting this
parameter and the margins of all olivetti mode windows. It should not
be too much of a hassle (and tell me immediately when you encounter
any problems).
The reason is that 'split-window' may be called for internal windows
too. For example, if you want to make a new window on the left or
right side of a frame, Emacs may want to split the root window of that
frame. In this case it will check the sizes of all live subwindows of
the root window and if any of these windows has too large margins, the
split may fail because of insufficient space for the new window.
martin
next prev parent reply other threads:[~2019-05-22 8:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 8:32 Adding olivetti to GNU ELPA Paul W. Rankin
2019-04-25 8:56 ` Eli Zaretskii
2019-04-25 12:32 ` Paul W. Rankin
2019-04-25 12:43 ` Eli Zaretskii
2019-04-25 13:01 ` Paul W. Rankin
2019-04-25 14:30 ` Eli Zaretskii
2019-05-08 4:07 ` Paul W. Rankin
2019-05-08 6:20 ` Eli Zaretskii
2019-05-09 6:54 ` Paul W. Rankin
2019-05-09 7:53 ` Eli Zaretskii
2019-05-09 8:14 ` martin rudalics
2019-05-09 13:30 ` Stefan Monnier
2019-05-10 8:00 ` martin rudalics
2019-05-14 5:16 ` Paul W. Rankin
2019-05-14 7:04 ` Paul W. Rankin
2019-05-14 12:22 ` Stefan Monnier
2019-05-15 8:26 ` Paul W. Rankin
2019-05-14 16:05 ` Joost Kremers
2019-05-14 16:50 ` Stefan Monnier
2019-05-14 21:56 ` Joost Kremers
2019-05-15 1:29 ` Stefan Monnier
2019-05-20 8:24 ` martin rudalics
2019-05-20 13:14 ` Paul W. Rankin
2019-05-21 7:32 ` martin rudalics
2019-05-21 7:38 ` Paul W. Rankin
2019-05-21 7:45 ` martin rudalics
2019-05-21 9:05 ` Paul W. Rankin
2019-05-21 10:04 ` martin rudalics
2019-05-22 1:47 ` Paul W. Rankin
2019-05-22 8:32 ` martin rudalics [this message]
2019-05-22 9:14 ` Paul W. Rankin
2019-05-08 14:07 ` Stefan Monnier
2019-05-08 15:45 ` Stephen Leake
2019-05-08 17:50 ` Eli Zaretskii
2019-04-26 1:17 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=622808ad-9a01-9ace-57a9-d3065c3a2daf@gmx.at \
--to=rudalics@gmx.at \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hello@paulwrankin.com \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).