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

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Thu, 24 Sep 2009 14:58:07 +0200
> Cc: 4534@emacsbugs.donarmstrong.com
> 
> > Now if I replace the check
> >
> >              if (height)
> >
> > by
> >
> >              if (height > WINDOW_TOTAL_LINES (w))
> >
> > I should be able to avoid the delta = -1 assertion failure in
> > grow_mini_window.  Can you confirm my reasoning so far?
> 
> It's correct. Except that, as shrink_mini_window didn't shrink the
> window, it remains at 6 lines.

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.





  parent reply	other threads:[~2009-09-25  8:35 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 [this message]
2009-09-25 11:30                 ` Juanma Barranquero
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=831vlvv2u8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=4534@emacsbugs.donarmstrong.com \
    --cc=lekktu@gmail.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).