unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Paul W. Rankin" <pwr@bydasein.com>
Cc: 24193@debbugs.gnu.org, Paul Rankin <hello@paulwrankin.com>
Subject: bug#24193: 25.1; `window-min-size' fails for horizontal width when margins >= body text
Date: Sat, 05 Sep 2020 14:28:48 +0200	[thread overview]
Message-ID: <87ft7w76gv.fsf@gnus.org> (raw)
In-Reply-To: <2263fe3a9530eb4f7f1b5cc82848f663@bydasein.com> (Paul W. Rankin's message of "Sat, 05 Sep 2020 00:54:21 +1000")

"Paul W. Rankin" <pwr@bydasein.com> writes:

> On 2020-09-04 23:09, Lars Ingebrigtsen wrote:
>> Paul Rankin <hello@paulwrankin.com> writes:
>>> Turns out there is a better solution, so the patch can be removed
>>> before stable 25.1 release if you prefer :)
>> Skimming this thread, Martin's patch was applied (which seemed to
>> fix
>> the issue?), but then Paul said there's a better solution?  (But not
>> what it was.)
>> So I'm not sure whether there's more to do here, or whether the bug
>> report should be closed.  Anybody?
>
> I was mistaken. The min-margins parameter is still required. Sorry for
> the confusion.

OK, then I guess everything discussed here was fixed, and I'm closing
this bug report.  If there's any more to be done here, please respond to
the debbugs address, and we'll reopen the bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-09-05 12:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09  9:14 bug#24193: 25.1; `window-min-size' fails for horizontal width when margins >= body text Paul Rankin
2016-08-09  9:49 ` martin rudalics
2016-08-09 10:01   ` Paul Rankin
2016-08-09 10:15     ` martin rudalics
2016-08-09 10:37       ` Paul Rankin
2016-08-09 14:57         ` Eli Zaretskii
2016-08-09 15:18           ` Paul Rankin
2016-08-09 15:53             ` Eli Zaretskii
2016-08-14  5:11               ` Paul Rankin
2016-08-14 14:32                 ` Eli Zaretskii
2016-08-15  8:28                   ` martin rudalics
2016-08-15 10:02                     ` Paul Rankin
2016-08-16  7:35                       ` martin rudalics
2016-08-15 15:03                     ` Eli Zaretskii
2016-08-16  7:35                       ` martin rudalics
2016-08-16 14:19                         ` Eli Zaretskii
2016-09-02  4:06                           ` Paul Rankin
2016-09-02  6:29                             ` martin rudalics
2020-09-04 13:09                             ` Lars Ingebrigtsen
2020-09-04 13:41                               ` Eli Zaretskii
2020-09-04 14:54                               ` Paul W. Rankin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-05 12:28                                 ` Lars Ingebrigtsen [this message]
2016-08-09 16:08         ` martin rudalics
2016-08-14  5:24           ` Paul Rankin
2016-08-09 14:56 ` Eli Zaretskii

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=87ft7w76gv.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=24193@debbugs.gnu.org \
    --cc=hello@paulwrankin.com \
    --cc=pwr@bydasein.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 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).