From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Carlos Pita Newsgroups: gmane.emacs.bugs Subject: bug#38181: Actual height of mode-line not taken into account Date: Sat, 16 Oct 2021 16:57:33 -0300 Message-ID: References: <87eeyd3ul0.fsf@bernoul.li> <2a0bf8c7-69df-0532-c6d8-5315ee9fee28@gmx.at> <67bcd8c4-2028-46bb-7971-244304bb7c0a@gmx.at> <776a35b7-1920-2987-88ae-6dcab958a8e4@gmx.at> <0dff07fa-b56f-1227-9f17-94e9b9b4c296@gmx.at> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15801"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 38181@debbugs.gnu.org To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Oct 16 21:58:12 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mbpop-0003yK-Ra for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 16 Oct 2021 21:58:11 +0200 Original-Received: from localhost ([::1]:46230 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mbpon-0007zv-T9 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 16 Oct 2021 15:58:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56106) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mbpog-0007zX-Ch for bug-gnu-emacs@gnu.org; Sat, 16 Oct 2021 15:58:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:59816) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mbpog-0004v2-4J for bug-gnu-emacs@gnu.org; Sat, 16 Oct 2021 15:58:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mbpog-0006lU-4G for bug-gnu-emacs@gnu.org; Sat, 16 Oct 2021 15:58:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Carlos Pita Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 16 Oct 2021 19:58:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 38181 X-GNU-PR-Package: emacs Original-Received: via spool by 38181-submit@debbugs.gnu.org id=B38181.163441427225988 (code B ref 38181); Sat, 16 Oct 2021 19:58:02 +0000 Original-Received: (at 38181) by debbugs.gnu.org; 16 Oct 2021 19:57:52 +0000 Original-Received: from localhost ([127.0.0.1]:43129 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mbpoW-0006l6-GL for submit@debbugs.gnu.org; Sat, 16 Oct 2021 15:57:52 -0400 Original-Received: from mail-yb1-f176.google.com ([209.85.219.176]:46035) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mbpoU-0006kr-96 for 38181@debbugs.gnu.org; Sat, 16 Oct 2021 15:57:50 -0400 Original-Received: by mail-yb1-f176.google.com with SMTP id i84so102758ybc.12 for <38181@debbugs.gnu.org>; Sat, 16 Oct 2021 12:57:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JVFjakPY/ubSfshZgpqaNqLvcgAfS7al7lF0aoDNvFI=; b=Ysz6YKKmKj3wEQQooP7+h+5j35qgUGhh5MB8a+pf9yZpf7A2IQNHzPp8b08Wh+TXG/ tuaES0yBJ6nOftI2SsXUblg+l3hs8K5FZ1JgxFwVfkA3LBw32a0Kh9hyRhmc/mT+UnX/ NfKBlEaFQ6HU/OFl/oLkpfKEM7Wpr/EHbsd+11MQUKzeXR4EpzvPDlGpOecPCOc9tp0m 1IrhZWSz1AtImEsz9B+OhOr5lw5Tnk5W8Y2XMJADkCwhvZJ+n381nuTcOf1poea+6IMS FuKWqeGICNBRPEY4jNHRdJuuLueYFVAJj+kwiuS7IDOhySa2+al5d5TEkZfQqgaJj8hI +mpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JVFjakPY/ubSfshZgpqaNqLvcgAfS7al7lF0aoDNvFI=; b=FBodjciYNwOpbYSYofUDDwsvxIoCup4nFN2Hmz13srN+cbYdjm37XUQ+kY6bb/l3GU lcGLHhRGp/ePjF5rFNtNwGAQq0G6QI6q+Ua+1diAORqvOpY07mwH26LcG2gob5N1O+Rv SZdi0/S55U2Pswf92ZZw1mvsT8tEKY0Q8EjiNzOpi2NWki5wgysLwxyTNb540ZkSh7BO 45Oxg9d8DZPnaM2mtIhLvWbAysiZYLtScs9yWp+v79FviQhjIYW7DrY94+9AGqKVhf+i dAs69Z3CNw0xh+AGOsmse1r6G71zvwvMWesvoqaSlefznno6pkW+fDDcVG+1o5v4Brte Nb5g== X-Gm-Message-State: AOAM530iN5tlYU8owiloJISPsLXPE/8ZFWlKapqCxdYGtrjK3RKqlIrN 0IImCCEoEbdEcY87+saaBWpfTOa8FAZIYGEx6SBdnZt5OwE= X-Google-Smtp-Source: ABdhPJxu8rui7HzwwHWn5wjgLhOzQuJMukyIPxbqAD+GpmGC0F/kE8VVwBhRPsx7DDX6MV4EMkYebYsxnJORGC+nPfc= X-Received: by 2002:a25:49c3:: with SMTP id w186mr21171245yba.429.1634414264553; Sat, 16 Oct 2021 12:57:44 -0700 (PDT) In-Reply-To: <0dff07fa-b56f-1227-9f17-94e9b9b4c296@gmx.at> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:217395 Archived-At: I was just about to email you with some questions that you now have answered to some extent. Anyway, I'm copying my original questions with some annotations. > > I think you mean with every set_window_buffer? And probably with every > > set_window_configuration too. Did you try it? > > I still need to refine my concept of "on window creation". Well, any relevant window hook in [1] is advertised as "called during redisplay", so that surely isn't the place to trigger that same redisplay to begin with... Let's go back to advising then. Here are some questions I have: 1. Is there a primitive function that is like the mother of all windows? There is no window-create nor create-window alikes, so maybe split-window-internal? > Window creation means 'split-window' which assigns the new window a > buffer that appears in the window that was split. So this more or less settles the question, but to be more precise: do you see any difference of relevance between advicing split-window and split-window-internal? 2. Or is it better to advise set-window-buffer/configuration for whatever reasons? Any or both of them? 3. If advising set-window-buffer/configuration is the preferred method, I'm still assuming that we will keep a window parameter in order to disable the forced redisplay after its first execution for the window. Is there any reason not do so (taking into account what I said before of the target use case: a single modeline height for every modeline during the entire session). > Or do the mode lines of _all_ your windows have > the same height? That indeed would simplify things a lot. Yes, this is by far the usual case and I believe it's a fact that favours the "advise window creation" strategy over the "advise window buffer/config change events" (with or without the "just once per window" clause) strategy. Thanks again, Carlos