unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 4534@emacsbugs.donarmstrong.com
Subject: bug#4534: assertion failure at window.c:grow_mini_window
Date: Fri, 25 Sep 2009 13:30:38 +0200	[thread overview]
Message-ID: <f7ccd24b0909250430u254667d5qd84f91bf47af20d2@mail.gmail.com> (raw)
In-Reply-To: <831vlvv2u8.fsf@gnu.org>

On Fri, Sep 25, 2009 at 10:35, Eli Zaretskii <eliz@gnu.org> wrote:

> Does this code cause an immediate redisplay?  I think it doesn't,
> which means shrink_mini_window does not actually shrink the window, it
> just prepares the glyph matrices for that.  The next redisplay will
> actually change how things are shown on the screen.

Hmm. The "else" part of shrink_mini_window (which works, in this case,
if you force it to go that route) definitely shrinks the window:

      Lisp_Object window;
      XSETWINDOW (window, w);
      enlarge_window (window, 1 - XFASTINT (w->total_lines), 0);

As for the "if" part, I think you're right.

Anyway, the last patch by Martin worked as expected, at least for this
bug. Is there any downside to it?

    Juanma





  reply	other threads:[~2009-09-25 11:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f7ccd24b0910260305i10204d17hbdbfe72251d740f1@mail.gmail.com>
2009-09-23  3:02 ` bug#4534: assertion failure at window.c:grow_mini_window Juanma Barranquero
2009-09-23  7:28   ` martin rudalics
2009-09-23  9:50     ` Juanma Barranquero
2009-09-23 10:51       ` Juanma Barranquero
2009-09-23 12:21         ` martin rudalics
2009-09-23 13:42           ` Juanma Barranquero
2009-09-24  6:49             ` martin rudalics
2009-09-23 12:21       ` martin rudalics
2009-09-23 13:41         ` Juanma Barranquero
2009-09-24  6:49           ` martin rudalics
2009-09-24 12:58             ` Juanma Barranquero
2009-09-24 15:32               ` martin rudalics
2009-09-24 15:53                 ` Juanma Barranquero
2009-09-24 16:10                   ` martin rudalics
2009-09-24 16:22                     ` Juanma Barranquero
2009-09-24 17:35                       ` martin rudalics
2009-09-24 17:45                         ` Juanma Barranquero
2009-09-24 22:03                         ` Stefan Monnier
2009-09-25 18:02                           ` Juanma Barranquero
2009-10-16  8:32                             ` Juanma Barranquero
2009-10-24 15:37                               ` Juanma Barranquero
2009-09-24 17:36                   ` Stefan Monnier
2009-09-25  8:35               ` Eli Zaretskii
2009-09-25 11:30                 ` Juanma Barranquero [this message]
2009-09-25 13:14                   ` Eli Zaretskii
2009-09-25 14:08                     ` Juanma Barranquero
2009-10-26 10:10   ` bug#4534: marked as done (assertion failure at window.c:grow_mini_window) Emacs bug Tracking System

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=f7ccd24b0909250430u254667d5qd84f91bf47af20d2@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=4534@emacsbugs.donarmstrong.com \
    --cc=eliz@gnu.org \
    /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).