From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emphasizing the top of the frame Date: Wed, 26 Oct 2016 21:40:46 +0300 Message-ID: <83shrjt0lt.fsf@gnu.org> References: <83zilsuvw4.fsf@gnu.org> <83y41cuvak.fsf@gnu.org> <581064F8.5060804@gmx.at> <83funjuxp8.fsf@gnu.org> <5810A216.9080304@gmx.at> <83bmy7uuc5.fsf@gnu.org> <5810BC6B.6020003@gmx.at> <834m3zupgm.fsf@gnu.org> <5810EE37.70703@gmx.at> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1477507266 24688 195.159.176.226 (26 Oct 2016 18:41:06 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 26 Oct 2016 18:41:06 +0000 (UTC) Cc: emacs-devel@gnu.org, john@yates-sheets.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 26 20:41:02 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bzT8A-0004kx-6U for ged-emacs-devel@m.gmane.org; Wed, 26 Oct 2016 20:40:54 +0200 Original-Received: from localhost ([::1]:36799 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzT8B-00023b-O6 for ged-emacs-devel@m.gmane.org; Wed, 26 Oct 2016 14:40:55 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51956) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzT86-00023R-Ml for emacs-devel@gnu.org; Wed, 26 Oct 2016 14:40:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bzT83-0002Sh-Eu for emacs-devel@gnu.org; Wed, 26 Oct 2016 14:40:50 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:40495) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzT83-0002ST-BA; Wed, 26 Oct 2016 14:40:47 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2561 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bzT82-0005R2-7c; Wed, 26 Oct 2016 14:40:47 -0400 In-reply-to: <5810EE37.70703@gmx.at> (message from martin rudalics on Wed, 26 Oct 2016 19:56:07 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:208851 Archived-At: > Date: Wed, 26 Oct 2016 19:56:07 +0200 > From: martin rudalics > CC: john@yates-sheets.org, emacs-devel@gnu.org > > >> But for that it (1) has to "walk the window tree as well" and (2) know > >> where to draw the minibuffer window. > > > > No, it doesn't. The window glyph matrices on TTY frames are actually > > portions of the frame glyph matrix, so whenever a window's glyphs are > > updated by xdisp.c, the corresponding glyphs of the frame are > > automagically updated as well. > > Looks like changing the minibuffer position is harder for TTY frames. I'm not sure. I don't see any signs of that, but it's always possible that I'm missing something. > As a matter of fact, there are a few more in window.c - foreach_window, > mark_window_cursors_off, window_set_before_size_change_sizes, > window_size_changed and get_leaf_windows. So I suppose that John should > try hard to _not_ change the relative order of the root and minibuffer > window and hope that interchanging the coordinates (something he has to > do anyway) will suffice. Isn't it a requirement that the "next" window shall be always below or to the right of its "prev"?