From: Eli Zaretskii <eliz@gnu.org>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: emacs-devel@gnu.org
Subject: Re: `min-margins' window parameter.
Date: Fri, 06 Nov 2020 15:11:18 +0200 [thread overview]
Message-ID: <83mtzu8wax.fsf@gnu.org> (raw)
In-Reply-To: <878sbevjtp.fsf@fastmail.fm> (message from Joost Kremers on Fri, 06 Nov 2020 13:37:24 +0100)
> From: Joost Kremers <joostkremers@fastmail.fm>
> Date: Fri, 06 Nov 2020 13:37:24 +0100
>
> In Emacs 25, the window parameter `min-margins' was added, after several
> discussions here and on bug-gnu-emacs about vertically splitting windows with
> wide margins.
>
> I've now finally started converting my code to use this parameter,[1] but it
> doesn't seem to be working as expected.
>
> When I invoke `C-x 3` (`split-window-right`) on a window with
> `visual-fill-column-mode` enabled, the split sometimes works as expected, but
> most of the time it doesn't. What I expect is for the window to be split in to
> side-by-side windows of equal size. What happens most of the time is that the
> window is split into two unevenly-sized windows, with the left window about as
> wide as the text area before the split and the right window taking up the rest
> of the original window.
>
> Twice during my tests Emacs actually hung, driving one of the CPU cores to 100%.
>
> I haven't been able to determine when the split works right and when it doesn't.
> It seems to be fairly random. Since all the relevant code runs during redisplay,
> Edebug doesn't seem to work. (At least ISTR that being the case.)
Please submit a full bug report with the details, using "M-x
report-emacs-bug". Bonus points for showing a recipe for reproducing
the problems without loading visual-fill-column, if possible.
Thanks in advance.
next prev parent reply other threads:[~2020-11-06 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 12:37 `min-margins' window parameter Joost Kremers
2020-11-06 13:11 ` Eli Zaretskii [this message]
2020-11-06 14:19 ` Joost Kremers
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=83mtzu8wax.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joostkremers@fastmail.fm \
/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).