From: martin rudalics <rudalics@gmx.at>
To: "Paul W. Rankin" <hello@paulwrankin.com>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Adding olivetti to GNU ELPA
Date: Thu, 9 May 2019 10:14:15 +0200 [thread overview]
Message-ID: <875d1b0c-7f44-ba5d-4660-84637533b8f3@gmx.at> (raw)
In-Reply-To: <m27eb0w213.fsf@paulwrankin.com>
> (set-window-margins
> (current-window) (/ 2 (- (window-width) olivetti-body-width)))
What is 'current-window' and how does it relate to 'selected-window'?
> There are some other ancillary functions, but really it's just a
> case of running this function in all windows displaying the current
> buffer when olivetti-body-width changes or when the window width
> changes.
What does "current buffer" refer to here? I suppose you want to run
"this function" whenever the body width of a window showing a buffer
with olivetti mode enabled changes. So with Emacs 27 it should
suffice to add your function to `window-size-change-functions' for
each buffer where olivetti mode is enabled
> 1. Some users have complained of lagging input, which seems to be
> due to olivetti setting the margins too often, i.e. on too many
> hooks. So using the minimal number of hooks is preferable.
'set-window-margins' doesn't do much when margins don't change. So I
suppose that for some reason olivetti mode wants margins to change too
often. If so, could you try to find out why?
> 2. But I've experienced olivetti failing to set the margins during a few common cases, e.g.:
> - splitting window with icomplete "*Completions*" buffer
> - splitting window with ispell-word "*Choices*" buffer
> - splitting window with magit-status
> - splitting window vertically with any buffers in a side-window in the same frame (which results in window being too large to split -- I think this is a separate issue)
Too _large_ to split?
> It would be nice to achieve consistency with these.
Are these failures due to the fact that a releated hook is not run or
are there other issues?
martin
next prev parent reply other threads:[~2019-05-09 8:14 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875d1b0c-7f44-ba5d-4660-84637533b8f3@gmx.at \
--to=rudalics@gmx.at \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hello@paulwrankin.com \
/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.