From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: Emphasizing the top of the frame Date: Wed, 26 Oct 2016 14:31:18 +0200 Message-ID: <5810A216.9080304@gmx.at> References: <83zilsuvw4.fsf@gnu.org> <83y41cuvak.fsf@gnu.org> <581064F8.5060804@gmx.at> <83funjuxp8.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1477486737 18133 195.159.176.226 (26 Oct 2016 12:58:57 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 26 Oct 2016 12:58:57 +0000 (UTC) Cc: emacs-devel@gnu.org, john@yates-sheets.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 26 14:58:53 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 1bzNmh-0000iv-3p for ged-emacs-devel@m.gmane.org; Wed, 26 Oct 2016 14:58:23 +0200 Original-Received: from localhost ([::1]:34061 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzNmj-0001hc-Hr for ged-emacs-devel@m.gmane.org; Wed, 26 Oct 2016 08:58:25 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52954) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzNNE-00054D-KI for emacs-devel@gnu.org; Wed, 26 Oct 2016 08:32:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bzNNA-0007I1-NI for emacs-devel@gnu.org; Wed, 26 Oct 2016 08:32:04 -0400 Original-Received: from mout.gmx.net ([212.227.17.20]:65139) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1bzNN6-0007Ep-Sy; Wed, 26 Oct 2016 08:31:57 -0400 Original-Received: from [192.168.1.101] ([212.95.7.101]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MTwYX-1cQ5JY185J-00QjB4; Wed, 26 Oct 2016 14:31:29 +0200 In-Reply-To: <83funjuxp8.fsf@gnu.org> X-Provags-ID: V03:K0:LqkM+njz1C0MvAbTCsdOWvvamkCBkInkSdEzmDEUv1HkVtxXIFo Bbnzmar9PYh8WLgLNs8WMl595o9GbGHMLQSCM5R6hrYRDnBFBFP+2jaREuzn66bNpSgv0Zp Nrv0UcxJLnc5uMxilrxaSVgVHVODQ0PuRZbHSSBNh9H2gKQIWalTgf3r1pz1X/TSt+sbC9Q xlkErFuO+M+T/bMamu6XA== X-UI-Out-Filterresults: notjunk:1;V01:K0:uE0/KORBCFg=:MLsb1l+xqfTPBdDgg88cse C8RjmQTx2kFXG+BOeZ6xqzMfzdaqsfpsq9pT85OXMKK/9Og6GPPLGFzCj57Vo5fe40mgiMafr 692/ksbmVuL8inV6EJs/lUktiZMxopUpJ8m157bVMk+xymJ3FXYt77v9uj6bjDMwdxoFM/mDG gvnfWiZT4SqRwAI9d1iyHQemh2+Fq2rOtGKnSICoOppF8HGzMFni45kSeBOO3jnZ/OBjZyA2I VsWFav4lwPffZpHv/cHsdFb4wzTLQTK60gazzd6VDbdwjHEiAEzf3KYkztB/m3wN5WouzjUkx yg0GWWW+BT6QUitpnLyHU8+A8m2zARfdjOF14dMK/szjxPWg0PaF/ZWe4eA4V8PAvu0wnYMse 8A4JJKx7tadd8/XOR8sqfmMj8v+Aq74qgA1HJAzni6KaXWLSqtahgWwe9lebuMxjFlqnY1jdX WOJtX2UyxiyXKstnyUW/XexBSodBwM4f/1+8aAvGDLPJpiVUai0YxAE+r1PUgfBXfkBWQqoMZ /C9jkjXkwm9KyQlbnRHxcAGx0rb7gKkunbbJg77IAzQ3OKPCMKB/aRLaIkhcyBoXiIviGk+yx XLRd2X/yMAdeLLIgI6ZHX23AknJeyKICCQhnaEKW5uL1poPjO2ik0I6m3RBvro0K3xjbttvgY 7ClD2thQAbhEftz5Lmu2mJubmBOFtTfCqVKl8ZCJ1jD/HdDvtGMznAG2wqZMTjSjqQ4SVpJ19 BbvhqCVWQhgRoNgdOgtYkqx7Q6fKo3iZDi4bDTYVDmrr7ucvO2p5PatDgKiUz4OUgeL2+wt8 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 212.227.17.20 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:208835 Archived-At: >> Does the display engine anywhere rely on that order? > > Not that I've seen (by looking at all users of FRAME_MINIBUF_WINDOW), I thought about some implicit ordering within the TTY display code. Critical uses would be that of the next field of the root window - not easy to spot, though (window.c, which has the greatest share of them, can be disregarded, however). > but I could miss something. And there is init_xdisp, which you > mentioned, that hardcodes the top coordinate of the minibuffer window.= If we only talk about _coordinates_ I see no problem - these have to be adjusted anway. > But see below. > >> The frame/window code doesn't and conceptually should even tolerate >> the next window of the root window being nil all the time. > > But doesn't the frame's window tree have to start with the root > window? If it does, then how do we make the minibuffer window be its > "prev"? Both, a frame's root and minibuffer window, are accessible directly. There is no reliance on the prev and next fields of these windows, with one exception: The `window-tree' function would have to be modified accordingly if we decided to swap the root and minibuffer windows' order. But that function should not be used anyway. The more important function is =E2=80=98walk-window-tree=E2=80=99 and that one accesses the = minibuffer via =E2=80=98minibuffer-window=E2=80=99. >> Note, however, that enlarging the minibuffer window currently tries t= o >> "adjust the trailing edge" of the root window (see that comment in >> =E2=80=98window--resize-root-window-vertically=E2=80=99 >> >> ;; When shrinking the root window, emulate an edge drag in or= der >> ;; to not resize other windows if we can avoid it (Bug#12419)= =2E >> >> and the bug mentioned there for why that is important). > > And that is at least one implicit dependency on this in the display > engine. I wonder how many more are there. Where do you see an "implicit dependency" here? > IME, eventually there's no other way but to make the changes in the > places you find, fire up Emacs, see what stops working, and debug and > fix each feature that becomes broken. > > We probably should have a variable that tells where the minubuffer > window appears, and code which needs to know needs to examine its > value. An option, yes. Or a special value `top' for the minibuffer frame parameter. martin