From: Stefan Kangas <stefan@marxist.se>
To: martin rudalics <rudalics@gmx.at>
Cc: Joost Kremers <joostkremers@fastmail.fm>, 44483@debbugs.gnu.org
Subject: bug#44483: 27.1.50; Window parameter `min-margins' doesn't split window in half
Date: Mon, 11 Oct 2021 05:35:37 -0700 [thread overview]
Message-ID: <CADwFkmkdF9r4mWrEC6xjJ3aFM3z7eDfx0avS3M+BdxFkYyQrkw@mail.gmail.com> (raw)
In-Reply-To: <d9dd4e28-b103-297e-1dc4-548985889668@gmx.at> (martin rudalics's message of "Mon, 9 Nov 2020 09:31:20 +0100")
martin rudalics <rudalics@gmx.at> writes:
>> AFAIR, the first time I heard about the `min-margins' parameter was when I
>> looked at the release notes of Emacs 25 after it came out. I don't remember why
>> I didn't try it out immediately, but after that, I probably forgot about it,
>> until a bug report I got a week ago.
>>
>> Paul Rankin did add `min-margins' to his `olivetti' package, but he didn't
>> remove the pre-25 workaround that uses the `split-window' window parameter, so
>> the problem probably never showed up.
>
> You're right. It was Paul, who said that he didn't need 'min-margins'
> and never reported whether they worked at all. Sorry for the confusion
> but I lost my recordings of past conversations.
>
>>> In Emacs 28 I intend to remove sanity checks entirely and always
>>> auto-shrink margins when they don't fit into a window any more. Windows
>>> will also have a configurable minimum body width so the behavior seen
>>> now where the entire buffer text disappears can be easily avoided.
>>
>> OK, so yet another way of doing things. :-) Sounds like it would make my life a
>> little easier, though.
>
> It's pretty hard to accommodate all expectations here. Consider a user
> who wants line numbers to remain visible even if everything else has
> disappeared after a window has shrunk: With line numbers displayed in
> margins, margins should prevail. With display-line-numbers, buffer text
> should prevail. A minimum body width will help users to make that
> decision. Yet users still have to interfere "manually" in order to
> communicate their intentions to Emacs.
>
>> Feel free to let me know when you implement it. I don't normally follow
>> development that closely, but in this case I'd be interested to test the new way
>> of doing things before the official release.
>
> I'll send you a patch as soon as I consider it stable enough.
That was in November last year. Any news here?
next prev parent reply other threads:[~2021-10-11 12:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 14:09 bug#44483: 27.1.50; Window parameter `min-margins' doesn't split window in half Joost Kremers
2020-11-06 14:41 ` Eli Zaretskii
2020-11-06 16:25 ` Joost Kremers
2020-11-06 18:29 ` Eli Zaretskii
2020-11-06 18:12 ` martin rudalics
2020-11-06 20:36 ` Joost Kremers
2020-11-07 9:00 ` martin rudalics
2020-11-08 15:00 ` Joost Kremers
2020-11-09 8:31 ` martin rudalics
2021-10-11 12:35 ` Stefan Kangas [this message]
2021-10-11 17:18 ` martin rudalics
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=CADwFkmkdF9r4mWrEC6xjJ3aFM3z7eDfx0avS3M+BdxFkYyQrkw@mail.gmail.com \
--to=stefan@marxist.se \
--cc=44483@debbugs.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.