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 16:23:39 +0200 Message-ID: <5810BC6B.6020003@gmx.at> 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> 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 1477491911 26382 195.159.176.226 (26 Oct 2016 14:25:11 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 26 Oct 2016 14:25:11 +0000 (UTC) Cc: john@yates-sheets.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 26 16:25:06 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 1bzP8Q-00052n-Pa for ged-emacs-devel@m.gmane.org; Wed, 26 Oct 2016 16:24:54 +0200 Original-Received: from localhost ([::1]:34979 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzP8T-0000H7-7X for ged-emacs-devel@m.gmane.org; Wed, 26 Oct 2016 10:24:57 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43930) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzP7V-0000GK-5l for emacs-devel@gnu.org; Wed, 26 Oct 2016 10:23:58 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bzP7R-0002WY-UB for emacs-devel@gnu.org; Wed, 26 Oct 2016 10:23:57 -0400 Original-Received: from mout.gmx.net ([212.227.17.20]:50440) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1bzP7R-0002W4-LN; Wed, 26 Oct 2016 10:23:53 -0400 Original-Received: from [192.168.1.101] ([212.95.7.33]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MLj5z-1c0ESs3il9-000uup; Wed, 26 Oct 2016 16:23:50 +0200 In-Reply-To: <83bmy7uuc5.fsf@gnu.org> X-Provags-ID: V03:K0:cccntBL506wr7nPkPWsc4PfGh10+Ve3l0HI07scbOFbbNi0wmsR xBcCOpRYtugDy1aeuc8CvP9Au+UNtxmKvCb0/zcFGblNLnxHJbLEMInN888iGPgftswpeTH Yj0YbGssc9dl5nVKPKnyP45HCmYkH4QtM7TPp4RHmCQNiG3wYlL0WzmRVNbf8r8FYBIBp9f wVK0mKrpn1hc9L+oU+5fA== X-UI-Out-Filterresults: notjunk:1;V01:K0:9uqdODbHu/Q=:GnA3pYBYcR/r0zf+6XyNaC IixuOXJp5CNcDKULUOd/Rw2TdiwB1IR3o3mAOS2FDtmCwyHnYW7+5BIUhmwe+cV3PjDdrfYhh tE7QT07pVjYqbFm3/wKvtaQi2z6qLsL5heiuZnXmKYl7KWRR/20hXCt/bj+c3133lnG0QYXj3 9FeFl0aS6582+JhfJ7iUOnjFWFrqnE+A9Qf1qqVdjwDp/CJpf0mq0Qp6Lb5kvKDhX+Qncg0VS vgeYXdrUTflB2sn/XNcyUKlo3NGCnxZ+xfn5iSFWxbETFaC+i+hIZS9PW7ln3aKhQ6o8ca1kp 6uVIhKjhyNhQl3Wzzh5+JRcQ5bj02TdlGDVnNn3/yBJYuhZmdANivEHMun0+wm7lfaV/tEvmK OcuiAm9Vx87GLx8zlaRbvIABK9AD65bPaBQoUfbBynTOu13LkmqZfCRoV9nEZuKNBhHFpOFdA h9NPnUBypEDC5DGnG/lgqopm/72ER26Lbb/01+YimE772OyPPLh70OekcQXelBJLZ/rnl795j XmbXiVchproSNQpAVT6fHo4H9hkP8HuRwayh9g61AqbqWijJsS2g3WWRIHeE7AcDSRFaIdLgD DWlP/sl2cr+Yqzw8E/+o+Z2xarBIegBXfASRlPGf29qZFF3s78zVPq0Ii/3t415+A9sSxX9R6 IcB1yfUp7zu9jLcCd9u8JeKDmAsVBFbUeMyGuIdBX1957hIp7ZGrztmWckUvQxsS77c+m9uLt 65ud0WrvN5GUzhL5h34KSqHvJ1Ogy12Y8ZXWwPwFY83/WzO0Q1XNxyjlHw39QnQ4eXfRvSME 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:208841 Archived-At: > The TTY display code is frame-based, and for a good reason. IOW, it > updates the entire frame, not each window separately. But for that it (1) has to "walk the window tree as well" and (2) know where to draw the minibuffer window. >> Both, a frame's root and minibuffer window, are accessible directly. >> There is no reliance on the prev and next fields of these windows > > There are at least two functions in the display engine that walk the > window tree, Which ones are that? > so I'm not sure what you mean by "no reliance on prev and > next"). I meant the prev and next fields of the root window and the minibuffer window. The next field leading from the root window to the minibuffer window is conceptually redundant - but might be still in use somewhere as, for example, in =E2=80=98window-tree=E2=80=99. The window tree proper is the tree rooted at the root window. The root window and the minibuffer window of a "normal" frame do not form a tree - they have no common ancestor. > That AFAIU the display engine knows that it can resize the minibuffer > window by moving the lower edge of the root window. All the display engine should know is that it can resize the minibuffer up to a certain extent. Deciding who pays for that operation and to what extent should be left to the window code. Think of a one line high window bordering the minibuffer window. martin